[Touch-packages] [Bug 299838] Re: /etc/cron.daily/find should be deleted when upgrading or it should use ionice -n instead of -p

Wheee this bug manifested on my server after I upgraded Ubuntu 10.04 to 12.04 to 14.04. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to findutils in Ubuntu. https://bugs.launchpad.net/bugs/299838 Title:

[Touch-packages] [Bug 1387328] [NEW] apport-gtk: clicking on the details tree jumps the scroll position to top

Public bug reported: 1. Wait for a crash or run apport-bug /var/crash/something.crash 2. Click Show Details 3. Scroll down the tree view until you see something interesting like Stacktrace 4. Click 'Stacktrace' to expand it What happens: - tree view gets focus, 1st (i.e. topmost) item in it gets

[Touch-packages] [Bug 960219] Re: Crash detail window should allow copy of contents to clipboard

Err, I meant bug 1133184. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/960219 Title: Crash detail window should allow copy of contents to clipboard Status in “apport”

[Touch-packages] [Bug 960219] Re: Crash detail window should allow copy of contents to clipboard

Duplicate of upstream bug 960219? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/960219 Title: Crash detail window should allow copy of contents to clipboard Status in

[Touch-packages] [Bug 1387328] Re: apport-gtk: clicking on the details tree jumps the scroll position to top

This error goes away if I comment out the code that putting the treeview inside a Gtk.Overlay(). Bug in GTK+? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1387328 Title:

[Touch-packages] [Bug 1387328] Re: apport-gtk: clicking on the details tree jumps the scroll position to top

What breaks this is inserting the overlay between the treeview and it's scrolledwindow. Putting the overlay outside makes it work. I tried to fix this in the code by adding one more level of .getparent() in add_spinner_over_treeview, but simply removing the scrolledwindow and adding it back

[Touch-packages] [Bug 1424622] Re: Something missing in the sudoers(5) manual page

This bug also affects trusty but not precise. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1424622 Title: Something missing in the sudoers(5) manual page Status in sudo

[Touch-packages] [Bug 1424622] [NEW] Something missing in the sudoers(5) manual page

Public bug reported: $ man sudoers ... passpromptThe default prompt to use when asking for a password; can be overridden via the -p option or the SUDO_PROMPT ... The default value is “[sudo] password for %p:”. The

[Touch-packages] [Bug 1449389] [NEW] Python Exception class 'TypeError' iter() returned non-iterator of type '_iterator'

Public bug reported: I tried to gdb a gnome-shell segfault: (gdb) bt #0 0x7f8cad51f638 in g_slice_alloc (magazine_chunks=0xf879b0) at /build/buildd/glib2.0-2.44.0/./glib/gslice.c:535 #1 0x7f8cad51f638 in g_slice_alloc (tmem=optimized out, ix=1) at

[Touch-packages] [Bug 1449389] Re: Python Exception class 'TypeError' iter() returned non-iterator of type '_iterator'

gdb in Ubuntu links against libpython3.4. The Python scripts in /usr/share/glib-2.0/gdb haven't been fully ported to Python 3: the custom iterators should define a '__next__' method alias pointing to 'next'. ** Also affects: glib2.0 (Ubuntu) Importance: Undecided Status: New **

[Touch-packages] [Bug 1449389] Re: Python Exception class 'TypeError' iter() returned non-iterator of type '_iterator'

The command to list Python scripts that have been autoloaded is: (gdb) info auto-load python-scripts I'm guessing /usr/share/gdb/auto-load/lib/x86_64-linux-gnu/libglib-2.0.so.0.4400.0-gdb.py is the one that causes my problem. It's a small script that adds /usr/share/glib-2.0/gdb to

[Touch-packages] [Bug 1449389] Re: Python Exception class 'TypeError' iter() returned non-iterator of type '_iterator'

Somewhat-related upstream bug: https://bugzilla.gnome.org/show_bug.cgi?id=720635 ** Bug watch added: GNOME Bug Tracker #720635 https://bugzilla.gnome.org/show_bug.cgi?id=720635 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed

[Touch-packages] [Bug 1453011] Re: SegvAnalysis: Failure: invalid literal for int() with base 16: '='

A simple fix would be to modify apport.report.Report.add_gdb_info() to use _command_output(..., stderr=subprocess.PIPE ) if we don't mind ignoring gdb's stderr. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in

[Touch-packages] [Bug 1453011] Re: SegvAnalysis: Failure: invalid literal for int() with base 16: '='

You can see the Disassembly: field contains $2 = -99Python Exception class 'TypeError' iter() returned non- iterator of type '_iterator': which is missing a newline. This breaks apport's output splitting logic. The TypeError shows up because of bug 1449389. I think it gets printed into

[Touch-packages] [Bug 1449389] Re: Python Exception class 'TypeError' iter() returned non-iterator of type '_iterator'

Upstream bug with a patch: https://bugzilla.gnome.org/show_bug.cgi?id=749092 ** Bug watch added: GNOME Bug Tracker #749092 https://bugzilla.gnome.org/show_bug.cgi?id=749092 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to

[Touch-packages] [Bug 1453011] Re: SegvAnalysis: Failure: invalid literal for int() with base 16: '='

** Attachment added: the strange apport crash file https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1453011/+attachment/4393424/+files/gnome-shell.crash -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in

[Touch-packages] [Bug 1453011] [NEW] SegvAnalysis: Failure: invalid literal for int() with base 16: '='

Public bug reported: Apport sometimes gets confused when analyzing a core dump: SegvAnalysis: Failure: invalid literal for int() with base 16: '=' I'm attaching the crash file (sans base64-encoded core dump) that contains this and some other wonderful examples, like Registers: $6 = 0x0

[Touch-packages] [Bug 1453011] Re: SegvAnalysis: Failure: invalid literal for int() with base 16: '='

I think I got a better fix in the linked Bazaar branch. I'm not sure how to test it: I have the crash file with the base64-encoded core and incorrectly-decoded fields, how can I convince apport (in a bzr checkout) re-interpret it? ** Branch linked: lp:~mgedmin/apport/fix-lp1453011 -- You

[Touch-packages] [Bug 1487740] Re: /usr/share/apport/apport-gtk:16: PyGIWarning: Wnck was imported without specifying a version first. Use gi.require_version('Wnck', '3.0') before import to ensure tha

*** This bug is a duplicate of bug 1502173 *** https://bugs.launchpad.net/bugs/1502173 ** This bug has been marked a duplicate of bug 1502173 Python warnings: modules imported without specifying a version first -- You received this bug notification because you are a member of Ubuntu

[Touch-packages] [Bug 1418771] Re: gjs-console assert failure: *** Error in `/usr/bin/gjs-console': free(): invalid next size (fast): 0x00007f74a804b240 ***

** Also affects: tracker (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1418771 Title: gjs-console assert failure:

[Touch-packages] [Bug 1512622] [NEW] Valgrind suppressions don't work on 64-bit systems

Public bug reported: Hello! The Python package helpfully ships /usr/lib/valgrind/python.supp, which is basically the upstream Valgrind suppressions file with some suppressions uncommented so they work on standard Python builds. Unfortunately those suppressions are tailored for 32-bit systems

[Touch-packages] [Bug 1511720] Re: fails to identify what program left a core file

objdump -h core shows this: core: file format elf64-x86-64 Sections: Idx Name Size VMA LMA File off Algn 0 note0 7cd4 6588 2**0 CONTENTS, READONLY 1 .reg/2241200d8

[Touch-packages] [Bug 1511720] Re: fails to identify what program left a core file

Workaround: 'readelf -n core' and look at the first mapped file. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to file in Ubuntu. https://bugs.launchpad.net/bugs/1511720 Title: fails to identify what program left a core

[Touch-packages] [Bug 1511720] [NEW] fails to identify what program left a core file

Public bug reported: Steps to reproduce: - 'ulimit -c unlimited' so you get core files - get a program to crash - run 'file core' to see what program it was that crashed Expected results: - file tells me the name of the program Actual results: - "core: ELF 64-bit LSB core file x86-64,

[Touch-packages] [Bug 1513364] [NEW] valgrind-python.supp is outdated

Public bug reported: While investigating bug 1512622 I decided to look if there's a /usr/lib/valgrind/python3.supp, and if it suffers from the same problem. I found it in python3-defaults, and it suffers from worse: - talks about python2.4 - doesn't have all the suppressions from upstream - the

[Touch-packages] [Bug 1512622] Re: Valgrind suppressions don't work on 64-bit systems

Oh, I'm sorry, I got terribly confused! Upstream Python ships a Valgrind suppressions file that requires you to do one of two things: - use a debugging build of Python, or - uncomment the suppressions for PyObject_Free and PyObject_Realloc. /usr/lib/valgrind/python.supp on wily has this bit

[Touch-packages] [Bug 1453011] Re: SegvAnalysis: Failure: invalid literal for int() with base 16: '='

I think this output parsing bug bit me again today: SegvAnalysis: Skipped: missing required field "Disassembly" SourcePackage: gdm Stacktrace: => 0x417010: mov0x8(%r15),%rcx 0x417014: test %rcx,%rcx 0x417017: je 0x41709f 0x41701d: mov(%rcx),%rbx 0x417020:

[Touch-packages] [Bug 1453011] Re: SegvAnalysis: Failure: invalid literal for int() with base 16: '='

Bug 1374544 might be a duplicate of this one. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1453011 Title: SegvAnalysis: Failure: invalid literal for int() with base 16:

[Touch-packages] [Bug 1541730] [NEW] all cron.daily scripts are skipped on a day when unattended-upgrades triggers a reboot

Public bug reported: When unattended-upgrades is configured to apply updates and Unattended- Upgrade::Automatic-Reboot is set to "true", and there's an update that requires a reboot, you'll find that none of the scripts in /etc/cron.daily were executed on that day. (To be more precise, none that

[Touch-packages] [Bug 1554365] Re: UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 2886: ordinal not in range(128)

I got this error email from four different OpenVZ-based VPSes, but not from any other servers. I wonder what's peculiar about their configuration. Locale used by cron? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to

[Touch-packages] [Bug 1554365] [NEW] UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 2886: ordinal not in range(128)

Public bug reported: I got this in the mail: From: Cron Daemon To: root@... Subject: Cron test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily ) Date: Thu, 25 Feb 2016 02:11:47 +0200 (EET) /etc/cron.daily/apt: Traceback (most

[Touch-packages] [Bug 1554365] Re: UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 2886: ordinal not in range(128)

/var/log/unattended-upgrades/unattended-upgrades- dpkg_2016-02-25_02:06:20.971350.log contains this line: Adding debian:TÜRKTRUST_Elektronik_Sertifika_Hizmet_Sağlayıcısı_H5.pem the Ü is at byte position 2888 of 10432 according to vim (which uses a 1-based offset and probably points to the

[Touch-packages] [Bug 1573586] [NEW] package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo-progs 1.3.0-0ubuntu2

Public bug reported: The GUI upgrade crashed because of LP: #1573558. I resumed with apt-get install -f apt-get dist-upgrade and got this error in the middle of the dist-upgrade. It's probably a duplicate of LP: #1571195. ProblemType: Package DistroRelease: Ubuntu 16.04 Package:

[Touch-packages] [Bug 1582629] Re: mutt does not properly restore console colors on exit

The Debian bug filed for Mutt traces this change to a bug in ncurses: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816887 ** Also affects: ncurses (Ubuntu) Importance: Undecided Status: New ** Bug watch added: Debian Bug tracker #816887

[Touch-packages] [Bug 1582629] Re: mutt does not properly restore console colors on exit

Short summary of the ncurses bug: - when you call start_color() and then endwin() twice without calling use_default_colors() in the middle, endwin() resets the color to grey on black (and then clears to end of line, which leaves an ugly black bar in my gnome-terminal which uses a white

[Touch-packages] [Bug 1541730] Re: all cron.daily scripts are skipped on a day when unattended-upgrades triggers a reboot

This appears to be fixed in 16.04 LTS, where unattended-reboots are scheduled by a systemd timer unit instead of /etc/cron.daily/apt. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu.

[Touch-packages] [Bug 1624836] [NEW] ubuntu-bug refuses to file upgrade bug, thinks it's a dupe from 2012

Public bug reported: I wanted to file https://bugs.launchpad.net/ubuntu/+source/ubuntu-release- upgrader/+bug/1624835https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1624835 so I ran ubuntu-bug and selected 'ubuntu-release-upgrader'. ubuntu-bug decided instead that my

[Touch-packages] [Bug 1624836] Re: ubuntu-bug refuses to file upgrade bug, thinks it's a dupe from 2012

** Description changed: I wanted to file https://bugs.launchpad.net/ubuntu/+source/ubuntu-release- upgrader/+bug/1624835https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1624835 so I ran ubuntu-bug and selected 'ubuntu-release-upgrader'. + I expected the usual

[Touch-packages] [Bug 1615482] Re: apt-daily timer runs at random hours of the day

Fun story: unattended-upgrades upgraded docker-engine in the middle of a day, breaking gitlab CI builds until a sysadmin figured out what happened and rebooted the machine manually. unattended-upgrades has an option to postpone unattended reboots to some safer time (like 2AM). Perhaps a similar

[Touch-packages] [Bug 1615482] Re: apt-daily timer runs at random hours of the day

My attempt to restrict unattended reboots to times between 0 and 6 AM wasn't successful. What I did is I created a /etc/systemd/system/apt- daily.timer.d/override.conf with the following contents: [Timer] OnCalendar=*-*-* 00:00 RandomizedDelaySec=6h unattended-upgrade ran and

[Touch-packages] [Bug 1632575] Re: systemd starts two copies of ntp at boot time

Unfortunately there were more unattended upgrades that require a reboot since I filed this bug, so systemd-analyze can't see what happened any more. As for systemd service files, I believe ntp has none. systemctl status ntp says Loaded: loaded (/etc/init.d/ntp; bad; vendor preset: enabled)

[Touch-packages] [Bug 1637333] Re: gnome-terminal crashes when tab is dragged onto another tab's terminal area

Upstream thinks this is a GTK+ bug, hence I'm adding gtk+ to this bug. ** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Also affects: gtk via https://bugzilla.gnome.org/show_bug.cgi?id=767588 Importance: Unknown Status: Unknown ** Also affects:

[Touch-packages] [Bug 1632575] [NEW] systemd starts two copies of ntp at boot time

Public bug reported: My system monitoring check noticed a stale /var/run/ntpd.pid pidfile on a xenial machine that rebooted at 2 AM after unattended upgrades. ntpd itself was running, but with a different pid. Digging through journalctl I can see Oct 12 02:00:11 xenial64 ntp[681]: *

[Touch-packages] [Bug 1686759] [NEW] apparmor denies sendmsg to /run/systemd/journal/socket

Public bug reported: While debugging why Polari can no longer connect to IRC servers after an upgrade to Ubuntu 17.04, I noticed the following errors in my journal: Bal 27 18:05:56 platonas audit[4869]: AVC apparmor="DENIED" operation="sendmsg" profile="/usr/lib/telepathy/mission-control-5"

[Touch-packages] [Bug 1632575] Re: systemd starts two copies of ntp at boot time

No, I never saw this again. The very next day after filing this bug I had another monitoring warning about a stale ntpd pidfile, but this time there was no second ntpd process running, and journalctl showed a simple conflict with ntpdate during startup. I apt-get removed ntpdate and never saw

[Touch-packages] [Bug 1718371] [NEW] Reboot hangs forever because /bin/systemctl --force reboot fails with "Failed to execute operation: Connection timed out"

Public bug reported: This morning unattended-upgrades had a reboot scheduled for 6:30 AM. The reboot process succeeded in turning off all network access but failed to actually reboot. As far as I can tell, this is because Sep 20 06:50:44 fridge systemd[1]: Starting Reboot... Sep 20

[Touch-packages] [Bug 1718371] Re: Reboot hangs forever because /bin/systemctl --force reboot fails with "Failed to execute operation: Connection timed out"

Here's the full journal log of the shutdown process. ** Attachment added: "Journal of the shutdown process" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1718371/+attachment/4953370/+files/reboot-hangs.txt -- You received this bug notification because you are a member of Ubuntu

[Touch-packages] [Bug 1721294] [NEW] Unattended upgrade fails with "Error in function"

Public bug reported: This is the cron email I received today: From: root To: r...@pov.lt Subject: unattended-upgrades result for 'iv-4.pov.lt': 'False' Date: Wed, 4 Oct 2017 03:40:19 +0300 (EEST) Unattended upgrade returned: False Packages that

[Touch-packages] [Bug 1721294] Re: Unattended upgrade fails with "Error in function"

This happened again this morning, on a different VPS, while trying to upgrade curl libcurl3 libcurl3-gnutls linux-libc-dev. My guess that this had something to do with ca-certificates upgade printing non-ASCII strings to the output was proven wrong. -- You received this bug notification because

[Touch-packages] [Bug 1554365] Re: UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 2886: ordinal not in range(128)

Last night's update gave me two more of these errors, both in OpenVZ containers. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1554365 Title:

[Touch-packages] [Bug 1554365] Re: UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 2886: ordinal not in range(128)

It looks like the unattended upgrade itself was successful, it's just that instead of the usual email showing me the upgrade log I get this traceback. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in

[Touch-packages] [Bug 1719159] [NEW] 'service procps start' does nothing

Public bug reported: /etc/sysctl.d/README says After making any changes, please run "service procps start" (or, from a Debian package maintainer script "invoke-rc.d procps start"). however running this command does absolutely nothing on Ubuntu 17.04 (and, presumably, any other Ubuntu

[Touch-packages] [Bug 1721294] Re: Unattended upgrade fails with "Error in function"

This happened again, while trying to upgrade libpq-dev libpq5 postgresql-9.3 postgresql-client-9.3. Running `unattended-upgrade -v` over an interactive SSH session succeeded. I'm not sure what's different. Locale? The successful installation log contains some non-ASCII characters, specifically

[Touch-packages] [Bug 792341] Re: gnome-terminal is sometimes not adding trailing slash when [Tab] used

Tab-completion is implemented by your shell (bash, most likely), not by gnome-terminal. ** Changed in: gnome-terminal (Ubuntu) Status: Confirmed => Invalid ** Also affects: bash (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a

[Touch-packages] [Bug 1637797] Re: kernel referred to by /*.old autoremoved

I accidentally ran apt-get autoremove twice on a couple of Ubuntu 14.04 LTS servers, and it removed the stale kernel (on 1st run) and the old kernel (on 2nd run), leaving the latest kernel the only one available in /boot. The .old kernel was linux-headers-3.13.0-139-generic, and if I look at

[Touch-packages] [Bug 1637797] Re: kernel referred to by /*.old autoremoved

FWIW I can reinstall linux-image-3.13.0-139-generic, mark it as autoremovable with apt-mark auto linux-image-3.13.0-139-generic, and at that point apt-get autoremove doesn't try to remove it any more. (But the apt-get install didn't restore /vmlinuz.old or /initrd.img.old symlinks.) I'm not sure

[Touch-packages] [Bug 1637797] Re: kernel referred to by /*.old autoremoved

One interesting thing is that this bug didn't manifest on other Ubuntu 14.04 LTS servers. I've a couple of sibling servers that are supposed to be exact copies (one is a hot standby for the other). One of them is now down to just one kernel, with two kernels listed in

[Touch-packages] [Bug 1721294] Re: Unattended upgrade fails with "Error in function"

This happened again. Can I tweak some config file to enable verbose mode for unattended-upgrades and see if it'll fail when run from cron tomorrow night? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in

[Touch-packages] [Bug 1721294] Re: Unattended upgrade fails with "Error in function"

(By reading that script I've discovered the existence of APT::Periodic::Verbose. We'll see what happens next morning with this set to "1"!) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu.

[Touch-packages] [Bug 1721294] Re: Unattended upgrade fails with "Error in function"

The thing is, whenever I run it interactively over ssh, unattended- upgrade succeeds. It's only the cron job that fails. If there's no separate config file, I'll edit /etc/cron.daily/apt directly. (This server is still on Ubuntu 14.04 LTS). -- You received this bug notification because you

[Touch-packages] [Bug 1721294] Re: Unattended upgrade fails with "Error in function"

The good news is the problem is reproducible. The bad news is APT::Periodic::Verbose "1" doesn't make unattended- upgrade produce any more output in its failure email: Unattended upgrade returned: False Packages that attempted to upgrade: dh-apparmor libapparmor1

[Touch-packages] [Bug 1721294] Re: Unattended upgrade fails with "Error in function"

Well, I got the debug output this time (a whole megabyte of it, split in two different emails), but unattended-upgrades succeeded, so I still don't know what the original problem was. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is

[Touch-packages] [Bug 1637797] Re: kernel referred to by /*.old autoremoved

The nightly unattended-upgrade (which I've configured to Unattended- Upgrade::Remove-Unused-Dependencies "true";) removed the .old kernel on two different 14.04 LTS servers last night, leaving both with no backup kernel at all. In fact now that I'm paying attention again, I have quite a number of

[Touch-packages] [Bug 1721294] Re: Unattended upgrade fails with "Error in function"

Yurii: can you clarify how that broke unattended upgrades? I also don't see how a cron script might get different PATH values from one day to the other. I just had another instance of this bug on a third Ubuntu 14.04 LTS server (this one a physical machine, not a VPS) where unattended-upgrades

[Touch-packages] [Bug 1721294] Re: Unattended upgrade fails with "Error in function"

This is a very annoying bug. Last morning unattended-upgrade failed on a machine, so I set APT::Periodic::Verbose to "3" and this morning I got a very verbose email showing that it succeeded. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which

[Touch-packages] [Bug 1582629] Re: mutt does not properly restore console colors on exit

FWIW a cleaner workaround that also works is creating a /etc/Muttrc.d/00 -fix-black-bar.rc that does color normal default default This way you don't have to deal with conffile changes on next upgrade. -- You received this bug notification because you are a member of Ubuntu Touch seeded

[Touch-packages] [Bug 1551623] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed

gconf2 broke my 18.04 -> 18.10 upgrade with dpkg: dependency problems prevent processing triggers for gconf2: gconf2 priklauso nuo psmisc; tačiau: Paketas psmisc dar nekonfigūruotas. dpkg: klaida, apdorojant paketą gconf2 (--configure): dependency problems - leaving

[Touch-packages] [Bug 1800167] [NEW] fstrim: /var/spool/postfix/etc/sasldb2: not a directory

Public bug reported: I've started getting weekly cron emails starting on Oct 7, 2018 that say /etc/cron.weekly/fstrim: fstrim: /var/spool/postfix/etc/sasldb2: not a directory The previous week's email did not have any complaints from fstrim, and I'm not sure what changed since then.

[Touch-packages] [Bug 1807930] [NEW] cups-daemon upgrades stop cups-browsed and leave it stopped

Public bug reported: Whenever cups-daemon is upgraded (by unattended-upgrades usually), it stops cups-browsed as a side effect of the upgrade. While cups.service itself is restarted by the time the upgrade process is done, cups- browsed.service remains stopped until manual admin intervention,

[Touch-packages] [Bug 1792934] Re: symlink loop detected in path 'usr/share/doc/module-init-tools/changelog.Debian.gz'

(TBH I've no idea what debsums is nattering about, /usr/share/doc /module-init-tools/changelog.Debian.gz is a regular file, and no parent directory is a symlink.) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in

[Touch-packages] [Bug 1792934] [NEW] symlink loop detected in path 'usr/share/doc/module-init-tools/changelog.Debian.gz'

Public bug reported: I ran debsums -ac and it printed this error debsums: Error: symlink loop detected in path 'usr/share/doc/module- init-tools/changelog.Debian.gz'. Please file a bug again module-init- tools. So here I am, filing a bug against module-init-tools. ProblemType: Bug

[Touch-packages] [Bug 1800167] Re: fstrim: /var/spool/postfix/etc/sasldb2: not a directory

Forwarded upstream: https://github.com/karelzak/util-linux/issues/857 ** Bug watch added: github.com/karelzak/util-linux/issues #857 https://github.com/karelzak/util-linux/issues/857 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is

[Touch-packages] [Bug 1843623] Re: LVM volumes not activated during boot after upgrade to 18.04 LTS

FWIW journalctl -b is showing a bunch of Sep 11 19:16:30 fridge lvmetad[457]: WARNING: Ignoring unsupported value for cmd. Sep 11 19:16:30 fridge lvmetad[457]: WARNING: Ignoring unsupported value for cmd. before systemd unit timeouts that are about those missing partitions failing to mount.

[Touch-packages] [Bug 1843623] Re: LVM volumes not activated during boot after upgrade to 18.04 LTS

In case this might be relevant: - /var is a separate partition (/dev/md1) - /var/cache is a separate partition (an LVM volume) - /tmp is a separate partition (an LVM volume) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to

[Touch-packages] [Bug 1843623] Re: LVM volumes not activated during boot after upgrade to 18.04 LTS

If I run pvscan --cache -aay in the systemd emergency console, all logical volumes get activated and the system then proceeds to boot normally. It seems like for some reason udev is not running pvscan for me? -- You received this bug notification because you are a member of Ubuntu Touch seeded

[Touch-packages] [Bug 1843554] Re: apt update is trying to use IPv6 for some reason, which does not work

Oops, I didn't read the error messages closely enough, sorry! (Also the mirror came back up right when I applied the Acquire::ForceIPv4 "true"; workaround, making me think my initial analysis was right. What a coincidence!) -- You received this bug notification because you are a member of

[Touch-packages] [Bug 1843623] Re: LVM volumes not activated during boot after upgrade to 18.04 LTS

So, uh, I tried another reboot so I could debug the problem some more, and ... well ... the machine booted. No problems. I've no idea what's going on, feel free to close this bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is

[Touch-packages] [Bug 1843554] [NEW] apt update is trying to use IPv6 for some reason, which does not work

Public bug reported: Today I've discovered that I cannot use apt-get any more: apt update Hit:1 http://ppa.launchpad.net/mgedmin/ppa/ubuntu disco InRelease Ign:2 http://ddebs.ubuntu.com disco InRelease Ign:3 http://ddebs.ubuntu.com disco-updates InRelease Hit:4

[Touch-packages] [Bug 1813430] Re: fstrim.service should not run inside container

*** This bug is a duplicate of bug 1589289 *** https://bugs.launchpad.net/bugs/1589289 ** This bug has been marked a duplicate of bug 1589289 fstrim: cannot open /dev/.lxd-mounts: Permission denied -- You received this bug notification because you are a member of Ubuntu Touch seeded

[Touch-packages] [Bug 1843623] [NEW] LVM volumes not activated during boot after upgrade to 18.04 LTS

Public bug reported: I've upgraded a server from Ubuntu 16.04 LTS to 18.04 LTS and now it fails to activate LVM volumes during boot (which causes systemd to stop in the middle of the boot process and ask me to fix this on the console without starting up services like SSH). The root partition,

[Touch-packages] [Bug 1843607] [NEW] package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1

Public bug reported: I was upgrading an Ubuntu 16.04 LTS server to 18.04 with sudo do- release-upgrade and it crashed. I did not see where the error was because etckeeper's messages made them scroll too far back, and do-release-upgrade sets up screen in a way that makes it impossible for me to

[Touch-packages] [Bug 1843607] Re: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1

So I see Setting up ca-certificates (20180409) ... Updating certificates in /etc/ssl/certs... rehash: error: skipping dovecot.pem, cannot open file rehash: warning: skipping duplicate certificate in AlphaSSL_root.crt dpkg: error processing package ca-certificates

[Touch-packages] [Bug 1751006] Re: Journalctl compiled without pattern matching support, pcre2 is not in main

journactl --grep works in Ubuntu 19.10 (but not 19.04 or older versions). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1751006 Title: Journalctl compiled without

[Touch-packages] [Bug 1751657] Re: man journalctl gives info about -g option not present in command

This is fixed on Ubuntu 19.10, where journalctl -g works fine. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1751657 Title: man journalctl gives info about -g option not

[Touch-packages] [Bug 1931077] Re: emergency shell ignores all keyboard input

Ideally, I'd wish it not to stop sshd when /boot/efi becomes unavailable. Or at least bring back the services it stopped when the emergency shell is canceled. More practically, and more on topic to the original reason for this bug report, I'd like it if stopping the emergency shell would print a

[Touch-packages] [Bug 1931077] [NEW] emergency shell ignores all keyboard input

Public bug reported: An SSD that held my /boot/efi partition failed, took down local-fs.target, which brought up emergency.target. I ended up with no ssh access, and a message on the local console telling me to press Enter to get a root shell, or press Ctrl-D to continue booting normally.

[Touch-packages] [Bug 1931077] Re: emergency shell ignores all keyboard input

Looking at the journal, I think the sequence of events is: - SSD fails last Friday - I log in today over ssh, start messing around - I notice that collectd is not running (since Friday), try to `sudo systemctl start collectd` - systemd tries to bring up collectd's dependency local-fs.target,

[Touch-packages] [Bug 1707611] Re: Sound does not automatically switch to HDMI when connected

My laptop with Ubuntu 20.10 automatically switches to the HDMI output when I plug in my monitor (via a USB C cable connected to a dock station connected to the monitor via a HDMI cable). And then, a second later, it switches to the USB dock's audio output (which has nothing plugged in), but

[Touch-packages] [Bug 1940808] Re: cannot install libssl-dev due to phased updates

On a closer look it may just be a mirror inconsistency. There's no Phased-Update-Percentage field in /var/lib/apt/lists/lt.archive.ubuntu.com_ubuntu_dists_focal- updates_main_binary-amd64_Packages for the libssl-dev entry, and the only available version is 1.1.1f-1ubuntu2.4. ** Changed in: apt

[Touch-packages] [Bug 1940808] [NEW] cannot install libssl-dev due to phased updates

Public bug reported: I have two Vagrant boxes: one with Ubuntu 18.04 LTS, one with Ubuntu 20.04 LTS. Both currently refuse to install libssl-dev for me: vagrant@ubuntu2004:~$ sudo apt install libssl-dev Reading package lists... Done Building dependency tree Reading state information...

[Touch-packages] [Bug 1940808] Re: cannot install libssl-dev due to phased updates?

https://launchpad.net/ubuntu/+archivemirrors shows four mirrors in Lithuania, all "up to date". Two of them actually are. One (Vilnius University) has a focal- updates/Packages.gz from 2021-05-04 with libssl-dev version 1.1.1f-1ubuntu2.3, one (LitNET) has a focal-updates/Packages.gz from

[Touch-packages] [Bug 1958503] [NEW] package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status

Public bug reported: Nothing very interesting here, the /boot partition on this server is very small (240M) and the upgrade ran out of space while generating an initramfs image. I was able to recover by removing the oldest linux-image package. I was surprised that do-release-upgrade didn't

[Touch-packages] [Bug 412195] Re: ttf-tahoma-replacement makes some web-sites look ugly

Debian reverted the change to isolate these low quality fonts from the rest of the system in https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=883973, and now this bug is back in Ubuntu 23.10. ** Bug watch added: Debian Bug tracker #883973