[Bug 1827727] Re: All plugins disabled due to expired cert
I agree. At least an ETA would be nice instead of vague "releases are coming" for such a critical bug. It has been long two working days waiting for a fix and still no idea when to expect it to be working again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827727 Title: All plugins disabled due to expired cert To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1827727/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
On 29/01/2019 13.44, Marc Pignat wrote: > If I understand well, ubiquity is the installer, so the iso image must > be tested. > > Where can I find a 18.04-daily iso image? As I understand it (might be wrong), the normal daily ISO is not the correct one to test with because it is not based on the /proposed/ repository. The correct procedure is documented here: https://wiki.ubuntu.com/Testing/EnableProposed#Installation_testing_using_-proposed Looks like there are no normal ISOs available. Thus there is a requirement to set up a netboot environment, which is documented here: https://help.ubuntu.com/community/Installation/Netboot However, the expected location for the /proposed/ netboot installer does not have recent enough version to include this fix: http://archive.ubuntu.com/ubuntu/dists/bionic-proposed/main/installer-amd64/ Maybe it will appear there at a later time... Janne Snabb sn...@epipe.com -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
I agree. It appears that version 0.130ubuntu3.3 is broken again. When looking at the changelog here: http://changelogs.ubuntu.com/changelogs/pool/main/i/initramfs-tools /initramfs-tools_0.130ubuntu3.3/changelog ...and comparing it to the changelog at: http://changelogs.ubuntu.com/changelogs/pool/main/i/initramfs-tools /initramfs-tools_0.130ubuntu3.2/changelog ...it looks like the Steve Langasek's fixes introduced in version 0.130ubuntu3.2 to fix this bug are lost in package version 0.130ubuntu3.3. ** Changed in: initramfs-tools (Ubuntu Bionic) Status: Fix Committed => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1508146] Re: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable
$ apt-file search kbd_mode kbd: /bin/kbd_mode kbd: /usr/share/man/man1/kbd_mode.1.gz [..] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1508146 Title: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1508146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762215] Re: wvdial crashes after upgrade to bionic 18.04
After disappearing for a while, the problem re-appeared. Luckily the bug is now fixed in Debian. The fix will eventually land in a future Ubuntu version. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762215 Title: wvdial crashes after upgrade to bionic 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wvdial/+bug/1762215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
I have this issue at every boot in my Ubuntu Virtualbox VM. It started happening after updating it from Ubuntu 17.10 to Ubuntu 18.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762215] Re: wvdial crashes after upgrade to bionic 18.04
It appears that the crash does not happen any more even though the wvdial package version remains the same as before. Possibly some condition has changed, not sure what (library versions is one possibility). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762215 Title: wvdial crashes after upgrade to bionic 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wvdial/+bug/1762215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759920] Re: intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-image-4.13.0-37-generic)
I may have experienced this issue also on bionic (18.04) with the current kernel version as of today (4.15.0-13.14). I upgraded one affected system with "do-release-upgrade -d". After completing the upgrade and rebooting, the system froze the same way as with the affected 17.10 kernel and microcode combination. After adding "apparmor=0" to the kernel command line the boot was successful. The system has sssd. I was not able to perform further testing today. I will try to confirm tomorrow. Or maybe someone else with an affected system is able to try bionic as well? ISOs available at http://releases.ubuntu.com/18.04/ if needed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759920 Title: intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux- image-4.13.0-37-generic) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759920] Re: intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-image-4.13.0-37-generic)
I tested the new kernel in artful-proposed on a system which failed with the newest kernel + intel-microcode in normal artful repository. Thus I confirm that the kernel in artful-proposed fixes this issue for me. $ apt policy linux-image-4.13.0-39-generic linux-image-4.13.0-39-generic: Installed: 4.13.0-39.44 Candidate: 4.13.0-39.44 Version table: *** 4.13.0-39.44 400 400 http://archive.ubuntu.com/ubuntu artful-proposed/main amd64 Packages 100 /var/lib/dpkg/status $ apt policy intel-microcode intel-microcode: Installed: 3.20180312.0~ubuntu17.10.1 Candidate: 3.20180312.0~ubuntu17.10.1 Version table: *** 3.20180312.0~ubuntu17.10.1 500 500 http://fi.archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu artful-security/main amd64 Packages 100 /var/lib/dpkg/status 3.20170707.1 500 500 http://fi.archive.ubuntu.com/ubuntu artful/restricted amd64 Packages ** Tags removed: verification-needed-artful ** Tags added: verification-done-artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759920 Title: intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux- image-4.13.0-37-generic) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762215] [NEW] wvdial crashes after upgrade to bionic 18.04
Public bug reported: Since upgrading Ubuntu from 17.10 to 18.04 wvdial is crashing with the following error message when connection is established: # wvdial 3gconnect --> WvDial: Internet dialer version 1.61 --> Initializing modem. --> Sending: ATZ ATZ OK --> Sending: ATQ0 V1 E1 S0=0 +FCLASS=0 ATQ0 V1 E1 S0=0 +FCLASS=0 OK --> Sending: AT+CGDCONT=1,"IP","internet" AT+CGDCONT=1,"IP","internet" OK --> Modem initialized. --> Sending: ATDT*99# --> Waiting for carrier. ATDT*99# CONNECT 2100 --> Carrier detected. Starting PPP immediately. --> Starting pppd at Sun Apr 8 18:50:07 2018 --> Pid of pppd: 7400 wvdial: utils/wvtask.cc:303: static int WvTaskMan::yield(int): Assertion `*current_task->stack_magic == WVTASK_MAGIC' failed. Aborted (core dumped) The connection is still established. It happens after pppd is already started. On 17.10 I did not encounter this issue. Package version: $ apt policy wvdial wvdial: Installed: 1.61-4.1build1 Candidate: 1.61-4.1build1 Version table: *** 1.61-4.1build1 500 500 http://se.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status It happens also on Debian. See the following for more details: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863039 ** Affects: wvdial (Ubuntu) Importance: Undecided Status: New ** Affects: wvdial (Debian) Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #863039 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863039 ** Also affects: wvdial (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863039 Importance: Unknown Status: Unknown ** Description changed: Since upgrading Ubuntu from 17.10 to 18.04 wvdial is crashing with the following error message when connection is established: # wvdial 3gconnect --> WvDial: Internet dialer version 1.61 --> Initializing modem. --> Sending: ATZ ATZ OK --> Sending: ATQ0 V1 E1 S0=0 +FCLASS=0 ATQ0 V1 E1 S0=0 +FCLASS=0 OK --> Sending: AT+CGDCONT=1,"IP","internet" AT+CGDCONT=1,"IP","internet" OK --> Modem initialized. --> Sending: ATDT*99# --> Waiting for carrier. ATDT*99# CONNECT 2100 --> Carrier detected. Starting PPP immediately. --> Starting pppd at Sun Apr 8 18:50:07 2018 --> Pid of pppd: 7400 wvdial: utils/wvtask.cc:303: static int WvTaskMan::yield(int): Assertion `*current_task->stack_magic == WVTASK_MAGIC' failed. Aborted (core dumped) - - The connection is still established. So it looks like this happens after pppd is already started. + The connection is still established. It happens after pppd is already + started. On 17.10 I did not encounter this issue. Package version: $ apt policy wvdial wvdial: - Installed: 1.61-4.1build1 - Candidate: 1.61-4.1build1 - Version table: - *** 1.61-4.1build1 500 - 500 http://se.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages - 100 /var/lib/dpkg/status + Installed: 1.61-4.1build1 + Candidate: 1.61-4.1build1 + Version table: + *** 1.61-4.1build1 500 + 500 http://se.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages + 100 /var/lib/dpkg/status It happens also on Debian. See the following for more details: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863039 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762215 Title: wvdial crashes after upgrade to bionic 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wvdial/+bug/1762215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745666] Re: gsd-housekeeping leaks file descriptors
Also affects Ubuntu 18.04 bionic (beta2 right now). $ apt policy gnome-settings-daemon gnome-settings-daemon: Installed: 3.28.0-0ubuntu2 Candidate: 3.28.0-0ubuntu2 Version table: *** 3.28.0-0ubuntu2 500 500 http://se.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1745666 Title: gsd-housekeeping leaks file descriptors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1745666/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745666] Re: gsd-housekeeping leaks file descriptors
Temporary workaround: 1) sudo mv /usr/lib/gnome-settings-daemon/gsd-housekeeping /usr/lib/gnome-settings-daemon/gsd-housekeeping.off 2) logout and login This needs to be redone when "gnome-settings-daemon" package is updated. I do not know if it is doing something useful for some people. Personally I feel this is some useless service which should be optional and disabled by default. I do not want or need some unknown software traversing my filesystem. I am worried about the potential privacy issues as the system logs now contain file system contents listing. The logs may be accidentally shipped outside my system for example when submitting bug reports. And it also causes system load while doing it. I have never asked it to do so! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1745666 Title: gsd-housekeeping leaks file descriptors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1745666/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1735910] Re: Grub installation failure
The same hardware and same default choices results with successfull installation (using grub-install /dev/sda) when using ubuntu- gnome-16.04.3-desktop-amd64.iso. So the bug has appeared after that version. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1735910 Title: Grub installation failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1735910/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1526029] Re: Installer disabled button
This happened with ubuntu-gnome-16.04.3-desktop-amd64.iso when trying to install on a system which had a pre-existing Ubuntu installation on hard disk -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1526029 Title: Installer disabled button To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1526029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1735910] Re: Grub installation failure
Another report of the same bug: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1708880 (That one is also incorrectly marked Invalid.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1735910 Title: Grub installation failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1735910/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1735910] Re: Grub installation failure
I encountered this issue also. I downloaded ubuntu-17.10.1-desktop- amd64.iso and created USB disk and tried to install Ubuntu using it. I did not specify anything, just pressing and selecting whatever is offered by default. It should not end like this. ** Changed in: ubiquity (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1735910 Title: Grub installation failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1735910/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745666] [NEW] gsd-housekeeping leaks file descriptors
Public bug reported: Apparently a process called gsd-housekeeping is periodically invoked on my Ubuntu 17.10 system. It traverses my /var/tmp for some reason. Looks like it is leaking file descriptors while doing so. My syslogs are full of error messages like the following: Jan 26 20:21:42 snail gsd-housekeepin[3178]: Failed to enumerate children of /var/tmp/chmaa-backup/usr/include/c++/5/bits/stl_raw_storage_iter.h: Error opening directory '/var/tmp/chmaa-backup/usr/include/c++/5/bits/stl_raw_storage_iter.h': Too many open files Jan 26 20:21:42 snail gsd-housekeepin[3178]: Failed to enumerate children of /var/tmp/chmaa-backup/usr/include/c++/5/bits/basic_string.h: Error opening directory '/var/tmp/chmaa-backup/usr/include/c++/5/bits/basic_string.h': Too many open files Jan 26 20:21:42 snail gsd-housekeepin[3178]: Failed to enumerate children of /var/tmp/chmaa-backup/usr/include/c++/5/bits/quoted_string.h: Error opening directory '/var/tmp/chmaa-backup/usr/include/c++/5/bits/quoted_string.h': Too many open files Jan 26 20:21:42 snail gsd-housekeepin[3178]: Failed to enumerate children of /var/tmp/chmaa-backup/usr/include/c++/5/bits/postypes.h: Error opening directory '/var/tmp/chmaa-backup/usr/include/c++/5/bits/postypes.h': Too many open files Jan 26 20:21:42 snail gsd-housekeepin[3178]: Failed to enumerate children of /var/tmp/chmaa-backup/usr/include/c++/5/bits/stl_iterator.h: Error opening directory '/var/tmp/chmaa-backup/usr/include/c++/5/bits/stl_iterator.h': Too many open files Jan 26 20:21:42 snail gsd-housekeepin[3178]: Failed to enumerate children of /var/tmp/chmaa-backup/usr/include/c++/5/bits/move.h: Error opening directory '/var/tmp/chmaa-backup/usr/include/c++/5/bits/move.h': Too many open files $ lsb_release -rd Description:Ubuntu 17.10 Release:17.10 $ apt policy gnome-settings-daemon gnome-settings-daemon: Installed: 3.26.2-0ubuntu0.1 Candidate: 3.26.2-0ubuntu0.1 Version table: *** 3.26.2-0ubuntu0.1 500 500 http://se.archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.26.1-0ubuntu5 500 500 http://se.archive.ubuntu.com/ubuntu artful/main amd64 Packages ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1745666 Title: gsd-housekeeping leaks file descriptors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1745666/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1715435] Re: Can't lock screen with keyboard shortcuts when using lightdm
In my case I was able to workaround this issue by changing the lock shortcut from super-L to ctrl-alt-L. All shortcuts using super are broken. My "window action key" in gnome-tweaks is "super". So it appears that it is impossible to use the window action key for shortcuts any more after some very recent updata. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715435 Title: Can't lock screen with keyboard shortcuts when using lightdm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1715435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1715435] Re: Can't lock screen with keyboard shortcuts when using lightdm
I am using gdm3 (AFAIK) and super-L also stopped working just now when I did "apt dist-upgrade". So in my case it does not seem to depend on lightdm vs gdm3. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715435 Title: Can't lock screen with keyboard shortcuts when using lightdm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1715435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1719106] Re: Notification message colour unreadable with "GNOME Classic" session
Forgot to include affected gnome-shell-extensions package version: $ apt policy gnome-shell-extensions gnome-shell-extensions: Installed: 3.26.0-1 Candidate: 3.26.0-1 Version table: *** 3.26.0-1 500 500 http://se.archive.ubuntu.com/ubuntu artful/universe amd64 Packages 500 http://se.archive.ubuntu.com/ubuntu artful/universe i386 Packages 100 /var/lib/dpkg/status -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1719106 Title: Notification message colour unreadable with "GNOME Classic" session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extensions/+bug/1719106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1719106] Re: Notification message colour unreadable after upgrade to artful
This bug appears only with "GNOME Classic" session. How to repeat: 1. Install Ubuntu 17.10 2. apt install gnome-shell-extensions 3. reboot 4. login choosing "GNOME Classic" session 5. open terminal 6. do "notify-send foobar" 7. unreadable notification box appears Thus, I was able to get rid of this problem by choosing "GNOME on Xorg" session. ** Package changed: gnome-shell (Ubuntu) => gnome-shell-extensions (Ubuntu) ** Summary changed: - Notification message colour unreadable after upgrade to artful + Notification message colour unreadable with "GNOME Classic" session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1719106 Title: Notification message colour unreadable with "GNOME Classic" session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extensions/+bug/1719106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1719106] [NEW] Notification message colour unreadable after upgrade to artful
Public bug reported: After upgrading my Ubuntu GNOME 17.04 system to Ubuntu 17.10 the notification message window colour is unreadable. It is black text on very dark grey background. See attached screenshot. To make sure that it does not come from my settings, I created a new user account with empty home directory and logged in using that user account. The issue still remains. I am not sure if the notification messages are produced by the gnome- shell package. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME-Classic:GNOME Date: Sat Sep 23 19:31:17 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2015-06-06 (839 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-09-20 (2 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ** Attachment added: "Screenshot with unreadable colours" https://bugs.launchpad.net/bugs/1719106/+attachment/4955699/+files/invisible-notification-text.png ** Description changed: After upgrading my Ubuntu GNOME 17.04 system to Ubuntu 17.10 the notification message window colour is unreadable. It is black text on very dark grey background. See attached screenshot. To make sure that it does not come from my settings, I created a new user account with empty home directory and logged in using that user account. The issue still remains. I am not sure if the notification messages are produced by the gnome- shell package. - - gnome-shell: - Installed: 3.26.0-0ubuntu1 - Candidate: 3.26.0-0ubuntu1 - Version table: - *** 3.26.0-0ubuntu1 500 - 500 http://se.archive.ubuntu.com/ubuntu artful/main amd64 Packages - 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME-Classic:GNOME Date: Sat Sep 23 19:31:17 2017 DisplayManager: gdm3 GsettingsChanges: - b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' - b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" + b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' + b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2015-06-06 (839 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) JournalErrors: - Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. -Users in the 'systemd-journal' group can see all messages. Pass -q to -turn off this notice. - No journal files were opened due to insufficient permissions. + Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. + Users in the 'systemd-journal' group can see all messages. Pass -q to + turn off this notice. + No journal files were opened due to insufficient permissions. SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-09-20 (2 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1719106 Title: Notification message colour unreadable after upgrade to artful To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1719106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland
I have this problem on Ubuntu Gnome 17.04 running in virtualbox. I believe it is not using Wayland. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1710637 Title: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1710637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1542000] Re: plymouthd crashed with SIGSEGV in script_obj_deref_direct()
Happens every time after login on fresh install of Ubuntu GNOME 17.04. Happened also with few previous releases of Ubuntu. Reproducible: always on every Ubuntu installation Not dependent on hardware as it happens on virtual box VMs as well as on physical machines. This gives a very bad impression of Ubuntu and Linux in general. New users are wondering why their freshly installed computers keep producing scary looking system problems. It makes the whole Ubuntu system feel unreliable. Please replace/remove plymouth from Ubuntu! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1542000 Title: plymouthd crashed with SIGSEGV in script_obj_deref_direct() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1542000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1678574] Re: percona-xtrabackup wrong mysql socket path
Thanks! I verified that the bug is fixed in these versions: ii percona-xtrabackup 2.3.7-0ubuntu0.16.10.2 amd64Open source backup tool for InnoDB and XtraDB ii percona-xtrabackup 2.3.7-0ubuntu0.16.04.2 amd64Open source backup tool for InnoDB and XtraDB ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1678574 Title: percona-xtrabackup wrong mysql socket path To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/percona-xtrabackup/+bug/1678574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1678574] [NEW] percona-xtrabackup wrong mysql socket path
Public bug reported: percona-xtrabackup was upgraded from 2.2.3-2.1build1.1 to 2.3.7-0ubuntu0.16.04.1. It appears that MySQL default socket file path has changed in the new version. After the update my backups started failing with the following: 170402 06:30:04 Connecting to MySQL server host: localhost, user: root, password: not set, port: not set, socket: not set Failed to connect to MySQL server: Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2). Workaround: Add the following in /root/.my.cnf or similar: [client] socket = /run/mysqld/mysqld.sock Version details: root@chmaa ~ # lsb_release -rd Description:Ubuntu 16.04.2 LTS Release:16.04 root@chmaa ~ # apt-cache policy percona-xtrabackup percona-xtrabackup: Installed: 2.3.7-0ubuntu0.16.04.1 Candidate: 2.3.7-0ubuntu0.16.04.1 Version table: *** 2.3.7-0ubuntu0.16.04.1 500 500 http://de.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages 100 /var/lib/dpkg/status 2.2.3-2.1build1 500 500 http://de.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages ** Affects: percona-xtrabackup (Ubuntu) Importance: Undecided Status: New ** Tags: regression-update ** Tags added: regression-update -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1678574 Title: percona-xtrabackup wrong mysql socket path To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/percona-xtrabackup/+bug/1678574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1617765] Re: Connections reset when downloading snaps from CDN
I have found several other mentions of this issue: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1612882 https://irclogs.ubuntu.com/2016/04/26/%23snappy.html https://irclogs.ubuntu.com/2016/08/30/%23snappy.html Clearly some other people are affected too, not just the two of us. :) In some of the above links there is a workaround (for snapd case): apt-get purge snapd apt-get install snapd After my 1st attempt the problem remained. However after doing the above for a 2nd time the problem went away! Maybe it picked another non-broken CDN node after the 2nd reinstall? Or something else similar to that? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1617765 Title: Connections reset when downloading snaps from CDN To manage notifications about this bug go to: https://bugs.launchpad.net/software-center-agent/+bug/1617765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1617765] Re: Connections reset when downloading snaps from CDN
** Also affects: snapd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1617765 Title: Connections reset when downloading snaps from CDN To manage notifications about this bug go to: https://bugs.launchpad.net/software-center-agent/+bug/1617765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1411030] Re: backport support for unix domain sockets
Before applying this patch, please note that it has a regression in ProxyPass connectiontimeout parameter handling, see https://bugzilla.redhat.com/show_bug.cgi?id=1242416 ** Bug watch added: Red Hat Bugzilla #1242416 https://bugzilla.redhat.com/show_bug.cgi?id=1242416 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1411030 Title: backport support for unix domain sockets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1411030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1411030] Re: backport support for unix domain sockets
Before applying this patch, please note that it has a regression in ProxyPass connectiontimeout parameter handling, see https://bugzilla.redhat.com/show_bug.cgi?id=1242416 ** Bug watch added: Red Hat Bugzilla #1242416 https://bugzilla.redhat.com/show_bug.cgi?id=1242416 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 in Ubuntu. https://bugs.launchpad.net/bugs/1411030 Title: backport support for unix domain sockets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1411030/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 722950] Re: ctrl-x does not work in grub-efi
I am affected by this issue on Ubuntu 15.04 x86_64. I have AMI BIOS/UEFI. Ctrl-X does not work (but F10 works). In my case 'x' is inserted as if I did not press Ctrl key. I found a discussion and a potential patch at: https://lists.gnu.org/archive/html/grub-devel/2013-08/msg3.html Possibly related question at StackExchange: https://unix.stackexchange.com/questions/103989/pressing-ctrl-x-or-f10 -does-not-boot-linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/722950 Title: ctrl-x does not work in grub-efi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/722950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1450442] Re: Kernel Oops - unable to handle kernel NULL pointer dereference at (null); Call Trace: [ffffffff810fb39b] ? audit_compare_dname_path+0x2b/0xa0
I encountered this issue on a Hetzner VPS. It is a KVM based virtual server, not VMware. After rebooting I was unable to login through ssh. Accessing the system from console was possible thugh running many commands resulted in Killed. The kernel stack trace was the same as in the original bug report. There is no quick and dirty workaround documented yet on this bug report, so I add it. Do the following to get your system quickly back to usable state while waiting for the patched kernel: 1) disable starting auditd at boot (for example chmod 000 /etc/init.d/auditd is an easy and ugly way to do it) 2) reboot the system (in my case the reboot command did not work, I had to hard-reset the system) Done. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1450442 Title: Kernel Oops - unable to handle kernel NULL pointer dereference at (null); Call Trace: [810fb39b] ? audit_compare_dname_path+0x2b/0xa0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1450442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1394193] Re: 114 instances of indicator-sound-service running
Same issue herre on Xubuntu 14.04.1 x86_64. I have 103 instances of the process. The processes are owned by lightdm user except for one which is owned by my userid snabb (see the process list at the end). There are also 103 instances of process init --user --startup-event indicator-services-start owned by lightdm as well, except one is owned by myself again (see the second process list at the end). When executing sudo killall indicator-sound-service all of the instances were restated. At the time there was lots of syslog output by pulseaudio. See the end of message for tail output. $ sudo ps axuwww | fgrep indicator-sound-service | fgrep -v fgrep lightdm 3440 0.0 0.0 399020 5024 ?Ssl 17:57 0:00 /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service lightdm 3441 0.0 0.0 472752 5048 ?Ssl 17:57 0:00 /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service lightdm 3442 0.0 0.0 399040 5036 ?Ssl 17:57 0:00 /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service lightdm 3453 0.0 0.0 399020 5024 ?Ssl 17:57 0:00 /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service lightdm 3462 0.0 0.0 399012 5156 ?Ssl 17:57 0:00 /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service lightdm 3463 0.0 0.0 399020 5020 ?Ssl 17:57 0:00 /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service lightdm 3467 0.0 0.0 399012 5152 ?Ssl 17:57 0:00 /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service lightdm 3474 0.0 0.0 399012 5156 ?Ssl 17:57 0:00 /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service lightdm 3483 0.0 0.0 399012 5156 ?Ssl 17:57 0:00 /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service lightdm 3498 0.0 0.0 399020 5164 ?Ssl 17:57 0:00 /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service lightdm 3506 0.0 0.0 407208 5132 ?Ssl 17:57 0:00 /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service lightdm 3507 0.0 0.0 399020 5168 ?Ssl 17:57 0:00 /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service lightdm 3512 0.0 0.0 399012 5160 ?Ssl 17:57 0:00 /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service lightdm 3513 0.0 0.0 407208 5168 ?Ssl 17:57 0:00 /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service lightdm 3514 0.0 0.0 399020 4976 ?Ssl 17:57 0:00 /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service lightdm 3555 0.0 0.0 399012 5160 ?Ssl 17:57 0:00 /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service lightdm 3560 0.0 0.0 399012 5152 ?Ssl 17:57 0:00 /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service lightdm 3561 0.0 0.0 399020 4972 ?Ssl 17:57 0:00 /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service lightdm 3605 0.0 0.0 399020 4976 ?Ssl 17:57 0:00 /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service lightdm 3638 0.0 0.0 399020 5164 ?Ssl 17:58 0:00 /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service lightdm 3639 0.0 0.0 399020 5168 ?Ssl 17:58 0:00 /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service lightdm 3647 0.0 0.0 399012 5156 ?Ssl 17:58 0:00 /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service lightdm 3648 0.0 0.0 399020 5164 ?Ssl 17:58 0:00 /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service lightdm 3652 0.0 0.0 399012 5148 ?Ssl 17:58 0:00 /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service lightdm 3653 0.0 0.0 399012 5156 ?Ssl 17:58 0:00 /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service lightdm 3654 0.0 0.0 399016 5152 ?Ssl 17:58 0:00 /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service lightdm 3660 0.0 0.0 399020 4980 ?Ssl 17:58 0:00 /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service lightdm 3674 0.0 0.0 399012 5152 ?Ssl 17:58 0:00 /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service lightdm 3677 0.0 0.0 399020 4972 ?Ssl 17:58 0:00 /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service lightdm 3683 0.0 0.0 399020 5168 ?Ssl 17:58 0:00 /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service lightdm 3698 0.0 0.0 399020 4972 ?Ssl 17:58 0:00 /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service lightdm 3713 0.0 0.0 399016 5160 ?Ssl 17:58 0:00 /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service lightdm 3714 0.0 0.0 399020 4980 ?Ssl 17:58 0:00
[Bug 1394193] Re: 114 instances of indicator-sound-service running
One more thing:
I was able to get rid of the processes by executing the following
command:
$ sudo kill `ps axuwww | fgrep indicator-services-start | awk '{ print
$2 }'`
However, as a result I lost the sound control thingy from the panel. I
should have probably excluded the indicator process which was owned by
myself.
The following command might be better (not tested, for future
reference):
$ sudo pkill -u lightdm -f indicator-services-start
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1394193
Title:
114 instances of indicator-sound-service running
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1394193/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 930563] Re: NM Applet menu entries not responding
On 2013-01-08 23:21, Hadrien Titeux wrote: Apparently this problem only appears after an upgrade.It seems I never got this kind of problem with fresh installs, and people here appear to be in the same situation... I have a fresh install of Ubuntu 12.10 and I have this problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/930563 Title: NM Applet menu entries not responding To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdbusmenu/+bug/930563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 930563] Re: NM Applet menu entries not responding
Please increase the importance of this bug! It is really embarrassing to go to a customer meeting, open my laptop and notice that I can not connect to a network because network-manager does not respond. I have to start by apologizing that I need to reboot my computer. It is a major PITA. While I am rebooting, they ask me what OS do I run... I seriously can not recommend Linux/Ubuntu to my customers when they see this episode every other time I have a meeting with them! It is just ridiculous. I am using Xubuntu 12.10 x86_64 on Dell Inspiron 3420 laptop (which was sold with Ubuntu pre-installed, older version though). I had this problem with my old laptop on 12.04 as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/930563 Title: NM Applet menu entries not responding To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdbusmenu/+bug/930563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 933791] Re: Stops responding to mouse clicks and won't open the VPN menu
This bug appears to be a possible duplicate of bug #930563 which is certainly not fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/933791 Title: Stops responding to mouse clicks and won't open the VPN menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/933791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 845660] Re: Network manager not responding to button presses
This appears to be duplicate of bug #930563 (or vice versa?). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/845660 Title: Network manager not responding to button presses To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/845660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1085812] Re: modem-manager crashed with SIGSEGV in get_cind_signal_done()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1085812 Title: modem-manager crashed with SIGSEGV in get_cind_signal_done() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1085812/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1085812] Re: modem-manager crashed with SIGSEGV in get_cind_signal_done()
Here is a syslog snippet from the time when the crash happened. Looks like the crash is triggered when the connection is terminated for some reason: Dec 3 06:31:15 foil pppd[19273]: LCP terminated by peer Dec 3 06:31:15 foil pppd[19273]: Connect time 444.3 minutes. Dec 3 06:31:15 foil pppd[19273]: Sent 9088405 bytes, received 82487382 bytes. Dec 3 06:31:15 foil pppd[19273]: Modem hangup Dec 3 06:31:15 foil pppd[19273]: Connection terminated. Dec 3 06:31:15 foil avahi-daemon[950]: Withdrawing workstation service for ppp0. Dec 3 06:31:15 foil NetworkManager[1058]: info (ttyUSB2): device state change: activated - failed (reason 'ip-config-unavailable') [100 120 5] Dec 3 06:31:15 foil modem-manager[1042]: info (ttyUSB2) closing serial port... Dec 3 06:31:15 foil modem-manager[1042]: info (ttyUSB2) serial port closed Dec 3 06:31:15 foil pppd[19273]: Exit. Dec 3 06:31:15 foil NetworkManager[1058]: warn Activation (ttyUSB2) failed for connection 'Saunalahti Postpaid (contract) NAT (available for all subscribers)' Dec 3 06:31:15 foil modem-manager[1042]: info Modem /org/freedesktop/ModemManager/Modems/0: state changed (connected - disconnecting) Dec 3 06:31:15 foil modem-manager[1042]: info Modem /org/freedesktop/ModemManager/Modems/0: state changed (disconnecting - connected) Dec 3 06:31:15 foil modem-manager[1042]: mm_serial_port_close: assertion `priv-open_count 0' failed Dec 3 06:31:15 foil dbus[680]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper) Dec 3 06:31:15 foil NetworkManager[1058]:SCPlugin-Ifupdown: devices removed (path: /sys/devices/virtual/net/ppp0, iface: ppp0) Dec 3 06:31:15 foil NetworkManager[1058]: info (ttyUSB2): now unmanaged Dec 3 06:31:15 foil NetworkManager[1058]: info (ttyUSB2): device state change: failed - unmanaged (reason 'removed') [120 10 36] Dec 3 06:31:15 foil NetworkManager[1058]: info (ttyUSB2): deactivating device (reason 'removed') [36] Dec 3 06:31:15 foil dbus[680]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Dec 3 06:31:15 foil NetworkManager[1058]: warn could not read ppp stats: No such device Dec 3 06:31:15 foil NetworkManager[1058]: warn DNS: plugin dnsmasq update failed Dec 3 06:31:15 foil NetworkManager[1058]: info ((null)): removing resolv.conf from /sbin/resolvconf Dec 3 06:31:15 foil dnsmasq[2994]: setting upstream servers from DBus Dec 3 06:31:15 foil NetworkManager[1058]: info (ttyUSB2): cleaning up... Dec 3 06:31:15 foil NetworkManager[1058]: info (ttyUSB2): taking down device. Dec 3 06:31:15 foil NetworkManager[1058]: info Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889) Dec 3 06:31:15 foil NetworkManager[1058]: info Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889) Dec 3 06:31:22 foil dnsmasq[1565]: no servers found in /etc/resolv.conf, will retry Dec 3 06:31:39 foil kernel: [55157.862296] modem-manager[1042]: segfault at 0 ip 0042926e sp 7fff30a7f210 error 4 in modem-manager[40+66000] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1085812 Title: modem-manager crashed with SIGSEGV in get_cind_signal_done() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1085812/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1070247] Re: unbound crashes with high query load
Some additional details: - This bug is triggered only if num-threads setting in unbound.conf is higher than 1. Therefore a simple workaround is to reduce the amount of threads to 1 (which is the default). - A description of the problem and a patch is available at https://unbound.net/pipermail/unbound-users/2012-September/002571.html (see the attachment at the end of that message). The patch does not apply cleanly against Unbound 1.4.16 but it is simple enough to fix it. - The fix is committed in Unbound SVN repository at r2733. It will be included in the next Unbound version. I am attaching a patch which applies cleanly against 1.4.16 to this bug. ** Patch added: unbound-1.4.16-openssl-threads.patch https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/1070247/+attachment/3414686/+files/unbound-1.4.16-openssl-threads.patch ** Summary changed: - unbound crashes with high query load + unbound crashes under high query load if num-threads 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1070247 Title: unbound crashes under high query load if num-threads 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/1070247/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1070247] Re: unbound crashes under high query load if num-threads 1
** Bug watch added: Debian Bug tracker #691528 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691528 ** Also affects: unbound (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691528 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1070247 Title: unbound crashes under high query load if num-threads 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/1070247/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1070247] [NEW] unbound crashes with high query load
Public bug reported: $ gdb /usr/sbin/unbound core.28338 GNU gdb (Ubuntu/Linaro 7.4-2012.04-0ubuntu2) 7.4-2012.04 Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as x86_64-linux-gnu. For bug reporting instructions, please see: http://bugs.launchpad.net/gdb-linaro/... Reading symbols from /usr/sbin/unbound...Reading symbols from /usr/lib/debug/usr/sbin/unbound...done. done. [New LWP 28345] [New LWP 28338] [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. Core was generated by `unbound'. Program terminated with signal 11, Segmentation fault. #0 RSA_new_method (engine=optimized out) at rsa_lib.c:191 191 rsa_lib.c: No such file or directory. (gdb) bt #0 RSA_new_method (engine=optimized out) at rsa_lib.c:191 #1 0x7f7d1a04a0f4 in ldns_key_buf2rsa_raw () from /usr/lib/libldns.so.1 #2 0x00469aea in setup_key_digest (keylen=optimized out, key=optimized out, digest_type=synthetic pointer, evp_key=synthetic pointer, algo=8) at validator/val_sigcrypt.c:1413 #3 verify_canonrrset (reason=0x7f7d177b16d8, keylen=optimized out, key=optimized out, sigblock_len=optimized out, sigblock=0x7f7d106a6b95 t$\313\314\032J\002\235y͙'\273\221jj\353\367\222\3550\030e\350RJ\016\355Kb\221\207\071\200\312\344\\236\232\325G\260\262\241\265\026EC\341\371\302A\376\370==\330\006ݦ\022\062j\033T\255\255\353\231Q\310\v\342\350١AK=e\322\067\335i\373\273\063:7\264\244\035Y\230\226}\030\260\360JX\237\242[\331\327]u\006\351_\003\t\346|E\362l?\364\317+oZ\204P\245`\266, algo=8, buf=0x7f7d1056fac0) at validator/val_sigcrypt.c:1506 #4 dnskey_verify_rrset_sig (region=optimized out, buf=0x7f7d1056fac0, ve=0x18f0310, now=1350983573, rrset=0x7f7d106a67b8, dnskey=optimized out, dnskey_idx=0, sig_idx=0, sortree=0x7f7d177b14d0, buf_canon=0x7f7d177b14dc, reason=0x7f7d177b16d8) at validator/val_sigcrypt.c:1683 #5 0x0043039c in dnskeyset_verify_rrset_sig (reason=0x7f7d177b16d8, sortree=0x7f7d177b14d0, sig_idx=0, dnskey=0x7f7d177b1520, rrset=0x7f7d106a67b8, now=1350983573, ve=0x18f0310, env=0x1920298) at validator/val_sigcrypt.c:680 #6 dnskeyset_verify_rrset (env=0x1920298, ve=0x18f0310, rrset=0x7f7d106a67b8, dnskey=0x7f7d177b1520, sigalg=0x7f7d109102f0 \b, reason=0x7f7d177b16d8) at validator/val_sigcrypt.c:581 #7 0x00432ea4 in val_verify_rrset (reason=0x7f7d177b16d8, sigalg=0x7f7d109102f0 \b, keys=0x7f7d177b1520, rrset=0x7f7d106a67b8, ve=0x18f0310, env=0x1920298) at validator/val_utils.c:335 #8 val_verify_rrset_entry (env=0x1920298, ve=0x18f0310, rrset=0x7f7d106a67b8, kkey=optimized out, reason=0x7f7d177b16d8) at validator/val_utils.c:381 #9 0x0042e9f8 in list_is_secure (reason=optimized out, kkey=optimized out, num=optimized out, list=optimized out, ve=optimized out, env=optimized out) at validator/val_nsec3.c:1313 #10 nsec3_prove_nods (reason=0x7f7d177b16d8, kkey=0x7f7d1090ff20, qinfo=0x7f7d106a4190, num=3, list=0x7f7d106a6690, ve=0x18f0310, env=0x1920298) at validator/val_nsec3.c:1340 #11 ds_response_to_ke.isra.1 (ke=synthetic pointer, qinfo=0x7f7d106a4190, rcode=optimized out, id=optimized out, qstate=optimized out) at validator/validator.c:2435 #12 process_ds_response.29359 (qstate=optimized out, vq=0x7f7d1090fdf8, id=optimized out, rcode=optimized out, msg=optimized out, qinfo=0x7f7d106a4190, origin=0x7f7d106a6fb8) at validator/validator.c:2552 #13 0x00444d61 in val_inform_super (qstate=0x7f7d106a4190, id=0, super=0x7f7d1160e430) at validator/validator.c:2892 #14 0x0046191b in mesh_walk_supers (mesh=0x7f7d1055f280, mstate=optimized out) at services/mesh.c:916 #15 0x00431724 in mesh_continue (ev=synthetic pointer, s=optimized out, mstate=0x7f7d106a4140, mesh=optimized out) at services/mesh.c:1033 #16 mesh_run (mesh=0x7f7d1055f280, mstate=0x7f7d106a4140, ev=optimized out, e=0x0) at services/mesh.c:1064 #17 0x00431ed6 in worker_handle_service_reply (c=0x7f7d1033d520, arg=0x7f7d106a6600, error=0, reply_info=0x7f7d177b1ca0) at daemon/worker.c:283 #18 0x0041f34b in serviced_callbacks.39588 (sq=0x7f7d10a8f210, error=0, c=0x7f7d1033d520, rep=0x7f7d177b1ca0) at services/outside_network.c:1505 #19 0x00428d71 in serviced_udp_callback (c=0x7f7d1033d520, arg=0x7f7d10a8f210, error=0, rep=0x7f7d177b1ca0) at services/outside_network.c:1776 #20 0x0041bbd8 in outnet_udp_cb.part.21 (reply_info=0x7f7d177b1ca0, arg=0x7f7d100b2aa0, c=0x7f7d1033d520) at services/outside_network.c:457 #21 outnet_udp_cb (c=0x7f7d1033d520, arg=0x7f7d100b2aa0, error=optimized out,
[Bug 1069543] [NEW] ntpd crashes when network interface goes down
Public bug reported: ntpd crashes with SIGSEGV when (teredo IPv6) interface goes down after unplugging a network cable: Oct 22 03:17:03 oil ntpdate[5896]: adjust time server 118.143.17.82 offset 0.005534 sec Oct 22 03:17:03 oil ntpd[5951]: ntpd 4.2.6p3@1.2290-o Mon Aug 20 15:15:21 UTC 2012 (1) Oct 22 03:17:03 oil ntpd[5952]: proto: precision = 0.106 usec Oct 22 03:17:03 oil ntpd[5952]: ntp_io: estimated max descriptors: 2144, initial socket boundary: 16 Oct 22 03:17:03 oil ntpd[5952]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123 Oct 22 03:17:03 oil ntpd[5952]: Listen and drop on 1 v6wildcard :: UDP 123 Oct 22 03:17:03 oil ntpd[5952]: Listen normally on 2 lo 127.0.0.1 UDP 123 Oct 22 03:17:03 oil ntpd[5952]: Listen normally on 3 eth0 192.168.0.2 UDP 123 Oct 22 03:17:03 oil ntpd[5952]: Listen normally on 4 teredo fe80:::: UDP 123 Oct 22 03:17:03 oil ntpd[5952]: Listen normally on 5 eth0 fe80::16fe:b5ff:fea4:b39f UDP 123 Oct 22 03:17:03 oil ntpd[5952]: Listen normally on 6 teredo 2001:0:53aa:64c:875:7e15:90bc:9593 UDP 123 Oct 22 03:17:03 oil ntpd[5952]: Listen normally on 7 lo ::1 UDP 123 Oct 22 03:17:03 oil ntpd[5952]: peers refreshed Oct 22 03:17:03 oil ntpd[5952]: Listening on routing socket on fd #24 for interface updates Oct 22 03:24:45 oil ntpd[5952]: Deleting interface #5 eth0, fe80::16fe:b5ff:fea4:b39f#123, interface stats: received=0, sent=0, dropped=0, active_time=460 secs Oct 22 03:24:45 oil ntpd[5952]: Deleting interface #3 eth0, 192.168.0.2#123, interface stats: received=40, sent=41, dropped=0, active_time=460 secs Oct 22 03:24:45 oil ntpd[5952]: 220.130.158.71 interface 192.168.0.2 - (none) Oct 22 03:24:45 oil ntpd[5952]: 118.143.17.82 interface 192.168.0.2 - (none) Oct 22 03:24:45 oil ntpd[5952]: 14.0.18.136 interface 192.168.0.2 - (none) Oct 22 03:24:45 oil ntpd[5952]: 54.251.61.122 interface 192.168.0.2 - (none) Oct 22 03:24:45 oil ntpd[5952]: 203.176.128.10 interface 192.168.0.2 - (none) Oct 22 03:24:45 oil ntpd[5952]: peers refreshed Oct 22 03:25:02 oil ntpd[5952]: Deleting interface #6 teredo, 2001:0:53aa:64c:875:7e15:90bc:9593#123, interface stats: received=0, sent=0, dropped=0, active_time=477 secs Oct 22 03:25:02 oil kernel: [197600.300333] ntpd[5952]: segfault at 8 ip 7fda05b58321 sp 7fff380bd540 error 4 in ntpd[7fda05b3b000+96000] Here is a gdb output: (gdb) c Continuing. Program received signal SIGSEGV, Segmentation fault. 0x7f743f09e321 in remove_interface (ep=0x7f74411771b0) at ntp_io.c:1098 1098ntp_io.c: No such file or directory. (gdb) bt #0 0x7f743f09e321 in remove_interface (ep=0x7f74411771b0) at ntp_io.c:1098 #1 update_interfaces (port=port@entry=123, receiver=receiver@entry=0x0, data=data@entry=0x0) at ntp_io.c:2010 #2 0x7f743f09fb34 in interface_update (receiver=receiver@entry=0x0, data=data@entry=0x0) at ntp_io.c:1617 #3 0x7f743f0c1215 in timer () at ntp_timer.c:394 #4 0x7f743f0a489b in ntpdmain (argc=optimized out, argv=optimized out) at ntpd.c:1127 #5 0x7f743f0954a9 in main (argc=optimized out, argv=optimized out) at ntpd.c:358 (gdb) I can only reproduce this with the teredo interface. If I disable it (by running service miredo stop before testing) I can not re-produce the problem any more. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: ntp 1:4.2.6.p3+dfsg-1ubuntu5 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu4 Architecture: amd64 Date: Mon Oct 22 03:42:12 2012 InstallationMedia: Xubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110920.2) KernLog: MarkForUpload: True SourcePackage: ntp UpgradeStatus: Upgraded to quantal on 2012-10-19 (2 days ago) modified.conffile..etc.ntp.conf: [modified] mtime.conffile..etc.ntp.conf: 2012-09-02T19:37:38.651830 ** Affects: ntp (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug quantal -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1069543 Title: ntpd crashes when network interface goes down To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1069543/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1069543] [NEW] ntpd crashes when network interface goes down
Public bug reported: ntpd crashes with SIGSEGV when (teredo IPv6) interface goes down after unplugging a network cable: Oct 22 03:17:03 oil ntpdate[5896]: adjust time server 118.143.17.82 offset 0.005534 sec Oct 22 03:17:03 oil ntpd[5951]: ntpd 4.2.6p3@1.2290-o Mon Aug 20 15:15:21 UTC 2012 (1) Oct 22 03:17:03 oil ntpd[5952]: proto: precision = 0.106 usec Oct 22 03:17:03 oil ntpd[5952]: ntp_io: estimated max descriptors: 2144, initial socket boundary: 16 Oct 22 03:17:03 oil ntpd[5952]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123 Oct 22 03:17:03 oil ntpd[5952]: Listen and drop on 1 v6wildcard :: UDP 123 Oct 22 03:17:03 oil ntpd[5952]: Listen normally on 2 lo 127.0.0.1 UDP 123 Oct 22 03:17:03 oil ntpd[5952]: Listen normally on 3 eth0 192.168.0.2 UDP 123 Oct 22 03:17:03 oil ntpd[5952]: Listen normally on 4 teredo fe80:::: UDP 123 Oct 22 03:17:03 oil ntpd[5952]: Listen normally on 5 eth0 fe80::16fe:b5ff:fea4:b39f UDP 123 Oct 22 03:17:03 oil ntpd[5952]: Listen normally on 6 teredo 2001:0:53aa:64c:875:7e15:90bc:9593 UDP 123 Oct 22 03:17:03 oil ntpd[5952]: Listen normally on 7 lo ::1 UDP 123 Oct 22 03:17:03 oil ntpd[5952]: peers refreshed Oct 22 03:17:03 oil ntpd[5952]: Listening on routing socket on fd #24 for interface updates Oct 22 03:24:45 oil ntpd[5952]: Deleting interface #5 eth0, fe80::16fe:b5ff:fea4:b39f#123, interface stats: received=0, sent=0, dropped=0, active_time=460 secs Oct 22 03:24:45 oil ntpd[5952]: Deleting interface #3 eth0, 192.168.0.2#123, interface stats: received=40, sent=41, dropped=0, active_time=460 secs Oct 22 03:24:45 oil ntpd[5952]: 220.130.158.71 interface 192.168.0.2 - (none) Oct 22 03:24:45 oil ntpd[5952]: 118.143.17.82 interface 192.168.0.2 - (none) Oct 22 03:24:45 oil ntpd[5952]: 14.0.18.136 interface 192.168.0.2 - (none) Oct 22 03:24:45 oil ntpd[5952]: 54.251.61.122 interface 192.168.0.2 - (none) Oct 22 03:24:45 oil ntpd[5952]: 203.176.128.10 interface 192.168.0.2 - (none) Oct 22 03:24:45 oil ntpd[5952]: peers refreshed Oct 22 03:25:02 oil ntpd[5952]: Deleting interface #6 teredo, 2001:0:53aa:64c:875:7e15:90bc:9593#123, interface stats: received=0, sent=0, dropped=0, active_time=477 secs Oct 22 03:25:02 oil kernel: [197600.300333] ntpd[5952]: segfault at 8 ip 7fda05b58321 sp 7fff380bd540 error 4 in ntpd[7fda05b3b000+96000] Here is a gdb output: (gdb) c Continuing. Program received signal SIGSEGV, Segmentation fault. 0x7f743f09e321 in remove_interface (ep=0x7f74411771b0) at ntp_io.c:1098 1098ntp_io.c: No such file or directory. (gdb) bt #0 0x7f743f09e321 in remove_interface (ep=0x7f74411771b0) at ntp_io.c:1098 #1 update_interfaces (port=port@entry=123, receiver=receiver@entry=0x0, data=data@entry=0x0) at ntp_io.c:2010 #2 0x7f743f09fb34 in interface_update (receiver=receiver@entry=0x0, data=data@entry=0x0) at ntp_io.c:1617 #3 0x7f743f0c1215 in timer () at ntp_timer.c:394 #4 0x7f743f0a489b in ntpdmain (argc=optimized out, argv=optimized out) at ntpd.c:1127 #5 0x7f743f0954a9 in main (argc=optimized out, argv=optimized out) at ntpd.c:358 (gdb) I can only reproduce this with the teredo interface. If I disable it (by running service miredo stop before testing) I can not re-produce the problem any more. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: ntp 1:4.2.6.p3+dfsg-1ubuntu5 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu4 Architecture: amd64 Date: Mon Oct 22 03:42:12 2012 InstallationMedia: Xubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110920.2) KernLog: MarkForUpload: True SourcePackage: ntp UpgradeStatus: Upgraded to quantal on 2012-10-19 (2 days ago) modified.conffile..etc.ntp.conf: [modified] mtime.conffile..etc.ntp.conf: 2012-09-02T19:37:38.651830 ** Affects: ntp (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug quantal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1069543 Title: ntpd crashes when network interface goes down To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1069543/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1068468] Re: Kubuntu upgrade 12.04 - 12.10 - php5-suhosin_0.9.33-3build1_amd64.deb
I encountered this error also when trying to update Xubuntu 12.04 to 12.10 with do-release-upgrade. I got the following output: Preparing to replace php5-suhosin 0.9.33-1 (using .../php5-suhosin_0.9.33-3build1_amd64.deb) ... mv: cannot move `/etc/php5/conf.d/suhosin.ini' to `/etc/php5/mods-available/suhosin.ini': No such file or directory dpkg: error processing /var/cache/apt/archives/php5-suhosin_0.9.33-3build1_amd64.deb (--unpack): subprocess new pre-installation script returned error exit status 1 No apport report written because MaxReports is reached already The upgrade aborted half-way and after rebooting the system did not recognize my ethernet adapter any more. I was able to get a network access by booting an older kernel. After that I run apt-get -f install and apt-get dist-upgrade and now I seem to have a working Xubuntu 12.10 system. This seems to be Debian bug #675278 ** Bug watch added: Debian Bug tracker #675278 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675278 ** Also affects: debian via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675278 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1068468 Title: Kubuntu upgrade 12.04 - 12.10 - php5-suhosin_0.9.33-3build1_amd64.deb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1068468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1068468] Re: Kubuntu upgrade 12.04 - 12.10 - php5-suhosin_0.9.33-3build1_amd64.deb
Additionally I have the following messages in /var/log/dist- upgrade/main.log: 2012-10-19 18:07:56,014 ERROR got an error from dpkg for pkg: '/var/cache/apt/archives/php5-suhosin_0.9.33-3build1_amd64.deb': 'subprocess new pre-installation script returned error exit status 1' 2012-10-19 18:07:56,027 DEBUG running apport_pkgfailure() php5-suhosin: subprocess new pre-installation script returned error exit status 1 2012-10-19 18:09:32,167 ERROR not handled exception: SystemError: E:Sub-process /usr/bin/dpkg returned an error code (1) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1068468 Title: Kubuntu upgrade 12.04 - 12.10 - php5-suhosin_0.9.33-3build1_amd64.deb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1068468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 997269] Re: dovecot imap broken by apparmor policy
** Changed in: apparmor (Ubuntu) Status: Expired = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dovecot in Ubuntu. https://bugs.launchpad.net/bugs/997269 Title: dovecot imap broken by apparmor policy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/997269/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 997269] Re: dovecot imap broken by apparmor policy
** Changed in: apparmor (Ubuntu) Status: Expired = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/997269 Title: dovecot imap broken by apparmor policy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/997269/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 858697] Re: daily cron script complains about packages not being installed
There is an easy workaround. I am adding it here for the benefit of others who are bothered by this: # dpkg-reconfigure popularity-contest And select No. (There is no point in submitting this data when nobody bothered to update this package for precise. Feels like nobody appreciates users submitting this data. Sorry about whining.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/858697 Title: daily cron script complains about packages not being installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/popularity-contest/+bug/858697/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 929219] Re: chromium-browser, gvfsd-http and others using eglibc crash with SIGSEGV in __nscd_get_mapping() or gethostbyname2_r()
I encountered this issue today the first time when adding a torrent to transmission's download queue. According to apport it is the same bug. I have the following libc6 package version, my system is fully up to date: 2.15-0ubuntu10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/929219 Title: chromium-browser, gvfsd-http and others using eglibc crash with SIGSEGV in __nscd_get_mapping() or gethostbyname2_r() To manage notifications about this bug go to: https://bugs.launchpad.net/eglibc/+bug/929219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1024528] Re: psgi_plugin.so: undefined symbol: boot_DynaLoader
Hi,
I installed 1.0.3+dfsg-1ubuntu0.1 from precise-proposed and looks like
it is working fine.
My PSGI app was loaded successfully:
Tue Jul 17 08:12:13 2012 - PSGI app 0 (/www/test/TestApp/bin/app.pl)
loaded at 0x176d038
And nginx can successfully request a page from it:
[pid: 28119|app: -1|req: -1/1] 124.248.XXX.XXX () {44 vars in 679 bytes}
[Tue Jul 17 08:13:19 2012] GET / = generated 5373 bytes in 139 msecs
(HTTP/1.0 200) 4 headers in 143 bytes (0 switches on core 0)
Thank you!
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1024528
Title:
psgi_plugin.so: undefined symbol: boot_DynaLoader
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/uwsgi/+bug/1024528/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1024528] Re: psgi_plugin.so: undefined symbol: boot_DynaLoader
I forgot to add a successfull test case result which matches the original simple test case. The test case in the bug description can be now verified by observing the following in /var/log/uwsgi/app/test.log: Tue Jul 17 22:06:05 2012 - PSGI app 0 (/dev/null) loaded at 0x105ed18 Tue Jul 17 22:06:05 2012 - *** uWSGI is running in multiple interpreter mode *** Tue Jul 17 22:06:05 2012 - spawned uWSGI master process (pid: 6590) Tue Jul 17 22:06:05 2012 - spawned uWSGI worker 1 (pid: 6592, cores: 1) Tue Jul 17 22:06:05 2012 - spawned uWSGI worker 2 (pid: 6593, cores: 1) We can see that the PSGI now starts successfully (our test app /dev/null is not very useful though :). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1024528 Title: psgi_plugin.so: undefined symbol: boot_DynaLoader To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/uwsgi/+bug/1024528/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1024528] Re: psgi_plugin.so: undefined symbol: boot_DynaLoader
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1024528 Title: psgi_plugin.so: undefined symbol: boot_DynaLoader To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/uwsgi/+bug/1024528/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1024528] [NEW] psgi_plugin.so: undefined symbol: boot_DynaLoader
Public bug reported: It appears that uwsgi-plugin-psgi does not load libperl.so and therefore the package is unusable. How to test: 1. # apt-get install uwsgi uwsgi-plugin-psgi 2. # vi /etc/uwsgi/apps-available/test.yaml Put the following contents there: ---cut-here--- uwsgi: plugins: psgi psgi: /dev/null ---cut-here--- 3. # ln -s /etc/uwsgi/apps-available/test.yaml /etc/uwsgi/apps-enabled/ 4. # service uwsgi restart 5. # less /var/log/uwsgi/app/test.log Observe the following error message: /usr/lib/uwsgi/plugins/psgi_plugin.so: undefined symbol: boot_DynaLoader The problem is obvious when looking at the uwsgi plugin file with ldd: $ ldd /usr/lib/uwsgi/plugins/psgi_plugin.so linux-vdso.so.1 = (0x7fff395ff000) libc.so.6 = /lib/x86_64-linux-gnu/libc.so.6 (0x7f2f4a70d000) libpthread.so.0 = /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f2f4a4f) /lib64/ld-linux-x86-64.so.2 (0x7f2f4acfe000) It does not load the perl shared library! As a workaround I retrieved the current source package version 1.2.3+dfsg-2~experimental1 from Debian and built it on Ubuntu precise. It works fine (and gives excellent PSGI performance :). Compare the ldd output: $ ldd /usr/lib/uwsgi/plugins/psgi_plugin.so linux-vdso.so.1 = (0x7fffa33ff000) libperl.so.5.14 = /usr/lib/libperl.so.5.14 (0x7fbf47482000) libpthread.so.0 = /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fbf47265000) libc.so.6 = /lib/x86_64-linux-gnu/libc.so.6 (0x7fbf46ea7000) libdl.so.2 = /lib/x86_64-linux-gnu/libdl.so.2 (0x7fbf46ca3000) libm.so.6 = /lib/x86_64-linux-gnu/libm.so.6 (0x7fbf469a9000) libcrypt.so.1 = /lib/x86_64-linux-gnu/libcrypt.so.1 (0x7fbf4676f000) /lib64/ld-linux-x86-64.so.2 (0x7fbf47a13000) The working version of the plugin depends on libperl.so while the non- working version does not. I think the problem has been fixed by this upstream commit: https://github.com/unbit/uwsgi/commit/15aaddb4d306912c2cb570cb47a82a68b900a27a See the changes in plugins/psgi/uwsgiplugin.py ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: uwsgi-plugin-psgi 1.0.3+dfsg-1 ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18 Uname: Linux 3.2.0-25-generic x86_64 ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Sat Jul 14 01:57:46 2012 InstallationMedia: Xubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110920.2) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: uwsgi UpgradeStatus: Upgraded to precise on 2012-04-27 (77 days ago) ** Affects: uwsgi (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1024528 Title: psgi_plugin.so: undefined symbol: boot_DynaLoader To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/uwsgi/+bug/1024528/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 997269] Re: dovecot imap broken by apparmor policy
apport information ** Tags added: apport-collected ** Description changed: Syslog output: Apr 29 10:59:06 host12 dovecot: imap(foobar): Error: fcntl(unlock) locking failed for file /home/foobar/Maildir/dovecot.index.log: No such file or directory Apr 29 10:59:06 host12 dovecot: imap(foobar): Error: fstat() failed with file /home/foobar/Maildir/dovecot.index.log: No such file or directory Apr 29 10:59:37 dovecot: last message repeated 122 times Apr 29 11:00:38 dovecot: last message repeated 248 times Apr 29 11:01:54 dovecot: last message repeated 203 times audit.log, lots of entries similar to the following: type=AVC msg=audit(1335712674.515:655016): apparmor=ALLOWED operation=getattr parent=10922 profile=/usr/sbin/dovecot//null-107 //null-10b//null-118 name=/home/foobar/Maildir/.foobar/dovecot.index.log pid=10937 comm=imap requested_mask=r denied_mask=r fsuid=1000 ouid=1000 The apparmor policy is as shipped with 12.04. The strange thing here is that audit.log says that the access was allowed and the apparmor policy has flags=(complain), but the imap server still fails accessing some files in the Maildir folders. Workaround: # ln -s /etc/apparmor.d/usr.sbin.dovecot /etc/apparmor.d/disable/ After disabling the usr.sbin.dovecot apparmor policy everything works fine. There is no need to disable the usr.lib.dovecot.imap policy. It looks like the imap process is incorrectly running under the dovecot main daemon's apparmor profile. And for some odd reason the profile is enforcing things even though it should be in complain mode. What are these //null-NNN/ strings in the logged apparmor profile name? I do not know apparmor well enough to debug this further at this point. Someone else has encountered this also, see thread at: http://comments.gmane.org/gmane.mail.imap.dovecot/60533 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: dovecot-imapd 1:2.0.19-0ubuntu1 ProcVersionSignature: User Name 3.2.0-24.37-virtual 3.2.14 Uname: Linux 3.2.0-24-virtual x86_64 ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Wed May 9 18:36:11 2012 ProcEnviron: SHELL=/bin/bash TERM=screen LANG=en_US.UTF-8 SourcePackage: dovecot UpgradeStatus: Upgraded to precise on 2012-04-27 (12 days ago) + --- + ApportVersion: 2.0.1-0ubuntu8 + Architecture: amd64 + DistroRelease: Ubuntu 12.04 + InstallationMedia: Ubuntu-Server 12.04 LTS Precise Pangolin - Release amd64 (20120424.1) + Package: apparmor 2.7.102-0ubuntu3.1 + PackageArchitecture: amd64 + ProcEnviron: + TERM=linux + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic root=UUID=7e6df5b7-d31e-4757-a388-f4f477187a63 ro + ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 + Tags: precise + Uname: Linux 3.2.0-23-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: ** Attachment added: ApparmorPackages.txt https://bugs.launchpad.net/bugs/997269/+attachment/3216655/+files/ApparmorPackages.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dovecot in Ubuntu. https://bugs.launchpad.net/bugs/997269 Title: dovecot imap broken by apparmor policy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/997269/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 997269] ApparmorStatusOutput.txt
apport information ** Attachment added: ApparmorStatusOutput.txt https://bugs.launchpad.net/bugs/997269/+attachment/3216656/+files/ApparmorStatusOutput.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dovecot in Ubuntu. https://bugs.launchpad.net/bugs/997269 Title: dovecot imap broken by apparmor policy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/997269/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 997269] Dependencies.txt
apport information ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/997269/+attachment/3216657/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dovecot in Ubuntu. https://bugs.launchpad.net/bugs/997269 Title: dovecot imap broken by apparmor policy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/997269/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 997269] KernLog.txt
apport information ** Attachment added: KernLog.txt https://bugs.launchpad.net/bugs/997269/+attachment/3216658/+files/KernLog.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dovecot in Ubuntu. https://bugs.launchpad.net/bugs/997269 Title: dovecot imap broken by apparmor policy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/997269/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 997269] PstreeP.txt
apport information ** Attachment added: PstreeP.txt https://bugs.launchpad.net/bugs/997269/+attachment/3216659/+files/PstreeP.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dovecot in Ubuntu. https://bugs.launchpad.net/bugs/997269 Title: dovecot imap broken by apparmor policy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/997269/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 997269] Re: dovecot imap broken by apparmor policy
I am able to reproduce this on a fresh install some times but not
reliably. It would be great if someone who has some apparmor experience
could have a look at this.
Steps to re-produce:
1. Install Ubuntu 12.04 Server from amd64 ISO in a virtual machine and make
sure it is up to date:
# apt-get update apt-get upgrade
# reboot
2. Install dovecot imapd and fetchmail for testing:
# apt-get install dovecot-imapd fetchmail
(I possibly needed to issue service dovecot start separately.)
3. Create user who receives mail:
# adduser foobar
4. Make mail directories for the user:
# mkdir -p /home/foobar/Maildir/{cur,new,tmp}
5. Send one e-mail to our user:
# (echo From: foo; echo; echo bar) /home/foobar/Maildir/new/foo
6. Ensure correct ownership:
# chown -R foobar /home/foobar/Maildir
7. Try to retrieve the mail:
# fetchmail --user foobar --mda cat localhost
Observe success. Ignore warning about certificate. The mail should be output to
stdout.
8. Install apparmor-profiles:
# apt-get install apparmor-profiles
9. Reboot to ensure fresh state:
# reboot
10. Send another e-mail:
# (echo From: foo; echo; echo bar) /home/foobar/Maildir/new/foo2
11. Again, change ownership:
# chown foobar /home/foobar/Maildir/new/foo2
12. Try fetching mail again:
# fetchmail --user foobar --mda cat localhost
You may or may not see a failure here.
13. If there was no failure, open another terminal and log in as foobar, and
create a pile of e-mails:
while true ; do ( echo From: foo; echo; echo bar )
/home/foobar/Maildir/new/foo$SECONDS.$RANDOM ; done
Hit ctrl-C after some time.
14. Try fetching mail again:
# fetchmail --user foobar --mda cat localhost
15. If there was no failure, repeat steps 13 and 14 until the failure is
observed. There will be error entries in /var/log/mail.err when the
problem appears.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dovecot in Ubuntu.
https://bugs.launchpad.net/bugs/997269
Title:
dovecot imap broken by apparmor policy
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/997269/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 997269] Re: dovecot imap broken by apparmor policy
On 07/08/2012 09:02 PM, Jamie Strandboge wrote: Thanks for the extra information. Can you also attach the output of: $ sudo aa-status This is already there, in the attachment ApparmorStatusOutput.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dovecot in Ubuntu. https://bugs.launchpad.net/bugs/997269 Title: dovecot imap broken by apparmor policy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/997269/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 997269] Re: dovecot imap broken by apparmor policy
apport information ** Tags added: apport-collected ** Description changed: Syslog output: Apr 29 10:59:06 host12 dovecot: imap(foobar): Error: fcntl(unlock) locking failed for file /home/foobar/Maildir/dovecot.index.log: No such file or directory Apr 29 10:59:06 host12 dovecot: imap(foobar): Error: fstat() failed with file /home/foobar/Maildir/dovecot.index.log: No such file or directory Apr 29 10:59:37 dovecot: last message repeated 122 times Apr 29 11:00:38 dovecot: last message repeated 248 times Apr 29 11:01:54 dovecot: last message repeated 203 times audit.log, lots of entries similar to the following: type=AVC msg=audit(1335712674.515:655016): apparmor=ALLOWED operation=getattr parent=10922 profile=/usr/sbin/dovecot//null-107 //null-10b//null-118 name=/home/foobar/Maildir/.foobar/dovecot.index.log pid=10937 comm=imap requested_mask=r denied_mask=r fsuid=1000 ouid=1000 The apparmor policy is as shipped with 12.04. The strange thing here is that audit.log says that the access was allowed and the apparmor policy has flags=(complain), but the imap server still fails accessing some files in the Maildir folders. Workaround: # ln -s /etc/apparmor.d/usr.sbin.dovecot /etc/apparmor.d/disable/ After disabling the usr.sbin.dovecot apparmor policy everything works fine. There is no need to disable the usr.lib.dovecot.imap policy. It looks like the imap process is incorrectly running under the dovecot main daemon's apparmor profile. And for some odd reason the profile is enforcing things even though it should be in complain mode. What are these //null-NNN/ strings in the logged apparmor profile name? I do not know apparmor well enough to debug this further at this point. Someone else has encountered this also, see thread at: http://comments.gmane.org/gmane.mail.imap.dovecot/60533 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: dovecot-imapd 1:2.0.19-0ubuntu1 ProcVersionSignature: User Name 3.2.0-24.37-virtual 3.2.14 Uname: Linux 3.2.0-24-virtual x86_64 ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Wed May 9 18:36:11 2012 ProcEnviron: SHELL=/bin/bash TERM=screen LANG=en_US.UTF-8 SourcePackage: dovecot UpgradeStatus: Upgraded to precise on 2012-04-27 (12 days ago) + --- + ApportVersion: 2.0.1-0ubuntu8 + Architecture: amd64 + DistroRelease: Ubuntu 12.04 + InstallationMedia: Ubuntu-Server 12.04 LTS Precise Pangolin - Release amd64 (20120424.1) + Package: apparmor 2.7.102-0ubuntu3.1 + PackageArchitecture: amd64 + ProcEnviron: + TERM=linux + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic root=UUID=7e6df5b7-d31e-4757-a388-f4f477187a63 ro + ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 + Tags: precise + Uname: Linux 3.2.0-23-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: ** Attachment added: ApparmorPackages.txt https://bugs.launchpad.net/bugs/997269/+attachment/3216655/+files/ApparmorPackages.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/997269 Title: dovecot imap broken by apparmor policy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/997269/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 997269] ApparmorStatusOutput.txt
apport information ** Attachment added: ApparmorStatusOutput.txt https://bugs.launchpad.net/bugs/997269/+attachment/3216656/+files/ApparmorStatusOutput.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/997269 Title: dovecot imap broken by apparmor policy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/997269/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 997269] Dependencies.txt
apport information ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/997269/+attachment/3216657/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/997269 Title: dovecot imap broken by apparmor policy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/997269/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 997269] KernLog.txt
apport information ** Attachment added: KernLog.txt https://bugs.launchpad.net/bugs/997269/+attachment/3216658/+files/KernLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/997269 Title: dovecot imap broken by apparmor policy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/997269/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 997269] PstreeP.txt
apport information ** Attachment added: PstreeP.txt https://bugs.launchpad.net/bugs/997269/+attachment/3216659/+files/PstreeP.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/997269 Title: dovecot imap broken by apparmor policy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/997269/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 997269] Re: dovecot imap broken by apparmor policy
I am able to reproduce this on a fresh install some times but not
reliably. It would be great if someone who has some apparmor experience
could have a look at this.
Steps to re-produce:
1. Install Ubuntu 12.04 Server from amd64 ISO in a virtual machine and make
sure it is up to date:
# apt-get update apt-get upgrade
# reboot
2. Install dovecot imapd and fetchmail for testing:
# apt-get install dovecot-imapd fetchmail
(I possibly needed to issue service dovecot start separately.)
3. Create user who receives mail:
# adduser foobar
4. Make mail directories for the user:
# mkdir -p /home/foobar/Maildir/{cur,new,tmp}
5. Send one e-mail to our user:
# (echo From: foo; echo; echo bar) /home/foobar/Maildir/new/foo
6. Ensure correct ownership:
# chown -R foobar /home/foobar/Maildir
7. Try to retrieve the mail:
# fetchmail --user foobar --mda cat localhost
Observe success. Ignore warning about certificate. The mail should be output to
stdout.
8. Install apparmor-profiles:
# apt-get install apparmor-profiles
9. Reboot to ensure fresh state:
# reboot
10. Send another e-mail:
# (echo From: foo; echo; echo bar) /home/foobar/Maildir/new/foo2
11. Again, change ownership:
# chown foobar /home/foobar/Maildir/new/foo2
12. Try fetching mail again:
# fetchmail --user foobar --mda cat localhost
You may or may not see a failure here.
13. If there was no failure, open another terminal and log in as foobar, and
create a pile of e-mails:
while true ; do ( echo From: foo; echo; echo bar )
/home/foobar/Maildir/new/foo$SECONDS.$RANDOM ; done
Hit ctrl-C after some time.
14. Try fetching mail again:
# fetchmail --user foobar --mda cat localhost
15. If there was no failure, repeat steps 13 and 14 until the failure is
observed. There will be error entries in /var/log/mail.err when the
problem appears.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/997269
Title:
dovecot imap broken by apparmor policy
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/997269/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 997269] Re: dovecot imap broken by apparmor policy
On 07/08/2012 09:02 PM, Jamie Strandboge wrote: Thanks for the extra information. Can you also attach the output of: $ sudo aa-status This is already there, in the attachment ApparmorStatusOutput.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/997269 Title: dovecot imap broken by apparmor policy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/997269/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 865499] Re: Please include virtio-rng in linux-image-*-virtual
As a workaround I run haveged in some of my virtual machines. It hopefully seeds /dev/random with something truly random. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/865499 Title: Please include virtio-rng in linux-image-*-virtual To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/865499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1002434] Re: TLS interoperability issue in NSS based software
It appears that the limit has been already increased to 3072 bits in the newest NSS release 3.13.4, see diff at: http://bonsai.mozilla.org/cvsview2.cgi?diff_mode=contextwhitespace_mode=showfile=blapit.hbranch=root=/cvsrootsubdir=mozilla/security/nss/lib/freeblcommand=DIFF_FRAMESETrev1=1.25rev2=1.26 Increase to 16k has been targeted to next NSS release 3.13.5 (see the linked mozilla bug). Could this be backported to precise as it is a LTS release? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1002434 Title: TLS interoperability issue in NSS based software To manage notifications about this bug go to: https://bugs.launchpad.net/nss/+bug/1002434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1002434]
How to test: certtool --generate-privkey --outfile key.pem certtool --generate-self-signed --load-privkey key.pem --outfile cert.pem certtool --generate-dh-params --bits 2237 --outfile dh2237.pem certtool --generate-dh-params --bits 2236 --outfile dh2236.pem gnutls-serv --http --x509keyfile key.pem --x509certfile cert.pem --dhparams dh2237.pem --disable-client-cert --priority NONE:+VERS-TLS- ALL:+CIPHER-ALL:+MAC-ALL:+DHE-RSA:+SIGN-ALL:+COMP-ALL Connect to https://localhost:5556/ (with firefox for example) and observe the failure. gnutls-serv --http --x509keyfile key.pem --x509certfile cert.pem --dhparams dh2236.pem --disable-client-cert --priority NONE:+VERS-TLS- ALL:+CIPHER-ALL:+MAC-ALL:+DHE-RSA:+SIGN-ALL:+COMP-ALL Connect to https://localhost:5556/ (with firefox for example) and observe the normal security warning about untrusted certificate. gnutls-serv and certtool are part of GnuTLS tools. They can be installed on Debian and Ubuntu by running apt-get install gnutls-bin. The long priority string is there just to ensure that the TLS handshake negotiates DHE-RSA based key exchange (new GnuTLS versions negotiate ECDHE-RSA otherwise which masks the issue because DHE key will not be needed). With older GnuTLS versions (I think less than 3) priority string NORMAL is sufficient as the older GnuTLS library does not have support for elliptic curves. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1002434 Title: TLS interoperability issue in NSS based software To manage notifications about this bug go to: https://bugs.launchpad.net/nss/+bug/1002434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1002434] [NEW] TLS interoperability issue in NSS based software
Public bug reported: NSS (Netscape Security Services) module provides encryption services to many applications, such as Thunderbird, Firefox and Chromium. NSS has a hard coded maximum limit of 2236 bits for ephemeral Diffie-Hellman (DHE) keys. If the TLS server (such as a web server, SMTP server, IMAP server, etc) requests a bigger DHE key size, NSS based applications refuse to interoperate. They just close the connection and display a confusing error message (such as Unknown error). Recent versions of GnuTLS (as shipped by Ubuntu and other distributions) include a new library API which recommends and automatically selects the following key sizes: Security level key bits LOW 1248 LEGACY 1776 NORMAL 2432 HIGH 3248 See the following for more information: https://www.gnu.org/software/gnutls/manual/html_node/Selecting- cryptographic-key-sizes.html As can be seen, NSS's maximum limit of 2236 bits can only interoperate with GnuTLS server which has been set at LOW or LEGACY security level. This bug was discovered when Exim's GnuTLS interface was revamped recently. Thunderbird refused to complete TLS handshake with the Exim SMTP server any more, because the new GnuTLS interface was following the GnuTLS library's opinion on suitable key sizes. Please patch the NSS library to accept reasonable key sizes: at the very least 3248 bits should be accepted to allow interoperability with GnuTLS at HIGH level. NSS is the only TLS library which has such a low hard limit on DHE key size. The only reason people are not hitting this bug frequently yet is that most main stream server software still does not use GnuTLS library's new API or recommendations but instead hard codes the DHE key size to 1024 or 2048 bits. I am attaching a patch which points out the relevant #define in blapit.h. ** Affects: nss Importance: Unknown Status: Unknown ** Affects: thunderbird Importance: Unknown Status: Unknown ** Affects: chromium (Ubuntu) Importance: Undecided Status: New ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Affects: nss (Ubuntu) Importance: Undecided Status: New ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1002434 Title: TLS interoperability issue in NSS based software To manage notifications about this bug go to: https://bugs.launchpad.net/nss/+bug/1002434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1002434] Re: TLS interoperability issue in NSS based software
** Patch added: nss-dh-max-p-bits.patch https://bugs.launchpad.net/bugs/1002434/+attachment/3156350/+files/nss-dh-max-p-bits.patch ** Bug watch added: Mozilla Bugzilla #636802 https://bugzilla.mozilla.org/show_bug.cgi?id=636802 ** Also affects: thunderbird via https://bugzilla.mozilla.org/show_bug.cgi?id=636802 Importance: Unknown Status: Unknown ** Package changed: thunderbird (Ubuntu) = nss (Ubuntu) ** Also affects: thunderbird (Ubuntu) Importance: Undecided Status: New ** Also affects: firefox (Ubuntu) Importance: Undecided Status: New ** Also affects: chromium (Ubuntu) Importance: Undecided Status: New ** Also affects: nss via https://bugzilla.mozilla.org/show_bug.cgi?id=636802 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1002434 Title: TLS interoperability issue in NSS based software To manage notifications about this bug go to: https://bugs.launchpad.net/nss/+bug/1002434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1002434] Re: TLS interoperability issue in NSS based software
Here are the relevant error messages from different NSS consumers. Thunderbird: Sending of message failed. The message could not be sent using SMTP server localhost for an unknown reason. Please verify that your SMTP server settings are correct and try again, or contact your network administrator. Firefox: Secure Connection Failed An error occurred during a connection to localhost. Unable to generate public/private key pair. (Error code: sec_error_keygen_fail) Chromium: This webpage is not available The webpage at https://localhost/ might be temporarily down or it may have moved permanently to a new web address. Error 2 (net::ERR_FAILED): Unknown error. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1002434 Title: TLS interoperability issue in NSS based software To manage notifications about this bug go to: https://bugs.launchpad.net/nss/+bug/1002434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1002434] Re: TLS interoperability issue in NSS based software
How to test: certtool --generate-privkey --outfile key.pem certtool --generate-self-signed --load-privkey key.pem --outfile cert.pem certtool --generate-dh-params --bits 2237 --outfile dh2237.pem certtool --generate-dh-params --bits 2236 --outfile dh2236.pem gnutls-serv --http --x509keyfile key.pem --x509certfile cert.pem --dhparams dh2237.pem --disable-client-cert --priority NONE:+VERS-TLS- ALL:+CIPHER-ALL:+MAC-ALL:+DHE-RSA:+SIGN-ALL:+COMP-ALL Connect to https://localhost:5556/ (with firefox for example) and observe the failure. gnutls-serv --http --x509keyfile key.pem --x509certfile cert.pem --dhparams dh2236.pem --disable-client-cert --priority NONE:+VERS-TLS- ALL:+CIPHER-ALL:+MAC-ALL:+DHE-RSA:+SIGN-ALL:+COMP-ALL Connect to https://localhost:5556/ (with firefox for example) and observe the normal security warning about untrusted certificate. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1002434 Title: TLS interoperability issue in NSS based software To manage notifications about this bug go to: https://bugs.launchpad.net/nss/+bug/1002434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 997269] [NEW] dovecot imap broken by apparmor policy
Public bug reported: Syslog output: Apr 29 10:59:06 host12 dovecot: imap(foobar): Error: fcntl(unlock) locking failed for file /home/foobar/Maildir/dovecot.index.log: No such file or directory Apr 29 10:59:06 host12 dovecot: imap(foobar): Error: fstat() failed with file /home/foobar/Maildir/dovecot.index.log: No such file or directory Apr 29 10:59:37 dovecot: last message repeated 122 times Apr 29 11:00:38 dovecot: last message repeated 248 times Apr 29 11:01:54 dovecot: last message repeated 203 times audit.log, lots of entries similar to the following: type=AVC msg=audit(1335712674.515:655016): apparmor=ALLOWED operation=getattr parent=10922 profile=/usr/sbin/dovecot//null-107 //null-10b//null-118 name=/home/foobar/Maildir/.foobar/dovecot.index.log pid=10937 comm=imap requested_mask=r denied_mask=r fsuid=1000 ouid=1000 The apparmor policy is as shipped with 12.04. The strange thing here is that audit.log says that the access was allowed and the apparmor policy has flags=(complain), but the imap server still fails accessing some files in the Maildir folders. Workaround: # ln -s /etc/apparmor.d/usr.sbin.dovecot /etc/apparmor.d/disable/ After disabling the usr.sbin.dovecot apparmor policy everything works fine. There is no need to disable the usr.lib.dovecot.imap policy. It looks like the imap process is incorrectly running under the dovecot main daemon's apparmor profile. And for some odd reason the profile is enforcing things even though it should be in complain mode. What are these //null-NNN/ strings in the logged apparmor profile name? I do not know apparmor well enough to debug this further at this point. Someone else has encountered this also, see thread at: http://comments.gmane.org/gmane.mail.imap.dovecot/60533 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: dovecot-imapd 1:2.0.19-0ubuntu1 ProcVersionSignature: User Name 3.2.0-24.37-virtual 3.2.14 Uname: Linux 3.2.0-24-virtual x86_64 ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Wed May 9 18:36:11 2012 ProcEnviron: SHELL=/bin/bash TERM=screen LANG=en_US.UTF-8 SourcePackage: dovecot UpgradeStatus: Upgraded to precise on 2012-04-27 (12 days ago) ** Affects: dovecot (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dovecot in Ubuntu. https://bugs.launchpad.net/bugs/997269 Title: dovecot imap broken by apparmor policy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/997269/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 997269] Re: dovecot imap broken by apparmor policy
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dovecot in Ubuntu. https://bugs.launchpad.net/bugs/997269 Title: dovecot imap broken by apparmor policy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/997269/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 997269] Re: dovecot imap broken by apparmor policy
This looks like it could be an apparmor bug instead of dovecot bug, it just happens to manifest itself with dovecot. Adding apparmor in affects. ** Also affects: apparmor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dovecot in Ubuntu. https://bugs.launchpad.net/bugs/997269 Title: dovecot imap broken by apparmor policy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/997269/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 997269] [NEW] dovecot imap broken by apparmor policy
Public bug reported: Syslog output: Apr 29 10:59:06 host12 dovecot: imap(foobar): Error: fcntl(unlock) locking failed for file /home/foobar/Maildir/dovecot.index.log: No such file or directory Apr 29 10:59:06 host12 dovecot: imap(foobar): Error: fstat() failed with file /home/foobar/Maildir/dovecot.index.log: No such file or directory Apr 29 10:59:37 dovecot: last message repeated 122 times Apr 29 11:00:38 dovecot: last message repeated 248 times Apr 29 11:01:54 dovecot: last message repeated 203 times audit.log, lots of entries similar to the following: type=AVC msg=audit(1335712674.515:655016): apparmor=ALLOWED operation=getattr parent=10922 profile=/usr/sbin/dovecot//null-107 //null-10b//null-118 name=/home/foobar/Maildir/.foobar/dovecot.index.log pid=10937 comm=imap requested_mask=r denied_mask=r fsuid=1000 ouid=1000 The apparmor policy is as shipped with 12.04. The strange thing here is that audit.log says that the access was allowed and the apparmor policy has flags=(complain), but the imap server still fails accessing some files in the Maildir folders. Workaround: # ln -s /etc/apparmor.d/usr.sbin.dovecot /etc/apparmor.d/disable/ After disabling the usr.sbin.dovecot apparmor policy everything works fine. There is no need to disable the usr.lib.dovecot.imap policy. It looks like the imap process is incorrectly running under the dovecot main daemon's apparmor profile. And for some odd reason the profile is enforcing things even though it should be in complain mode. What are these //null-NNN/ strings in the logged apparmor profile name? I do not know apparmor well enough to debug this further at this point. Someone else has encountered this also, see thread at: http://comments.gmane.org/gmane.mail.imap.dovecot/60533 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: dovecot-imapd 1:2.0.19-0ubuntu1 ProcVersionSignature: User Name 3.2.0-24.37-virtual 3.2.14 Uname: Linux 3.2.0-24-virtual x86_64 ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Wed May 9 18:36:11 2012 ProcEnviron: SHELL=/bin/bash TERM=screen LANG=en_US.UTF-8 SourcePackage: dovecot UpgradeStatus: Upgraded to precise on 2012-04-27 (12 days ago) ** Affects: dovecot (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/997269 Title: dovecot imap broken by apparmor policy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/997269/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 997269] Re: dovecot imap broken by apparmor policy
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/997269 Title: dovecot imap broken by apparmor policy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/997269/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 997269] Re: dovecot imap broken by apparmor policy
This looks like it could be an apparmor bug instead of dovecot bug, it just happens to manifest itself with dovecot. Adding apparmor in affects. ** Also affects: apparmor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/997269 Title: dovecot imap broken by apparmor policy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/997269/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 864609] Re: libvte9 fails to record utmp/login entries
This bug still exists on Xubuntu 12.04 precise as released, version information below: $ apt-cache policy libvte9 libvte9: Installed: 1:0.28.2-3ubuntu2 Candidate: 1:0.28.2-3ubuntu2 Version table: *** 1:0.28.2-3ubuntu2 0 500 http://kh.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages 100 /var/lib/dpkg/status The symlink workaround from my comment #3 still fixes the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/864609 Title: libvte9 fails to record utmp/login entries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte/+bug/864609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 864609] Re: libvte9 fails to record utmp/login entries
How about updating libvte (1:0.28.2-4) now from Debian when there is still time remaining before the various freezes start in release schedule? It would be nice to have a working terminal application in the next Xubuntu release. The debian maintainer fixed the broken packaging already more than a month ago... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/864609 Title: libvte9 fails to record utmp/login entries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte/+bug/864609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 734777] Re: cannot acquire state change lock problems
I got hit by this on natty. There seems to be a corresponding Red Hat bug at: https://bugzilla.redhat.com/show_bug.cgi?id=676205 ** Bug watch added: Red Hat Bugzilla #676205 https://bugzilla.redhat.com/show_bug.cgi?id=676205 ** Also affects: libvirt via https://bugzilla.redhat.com/show_bug.cgi?id=676205 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/734777 Title: cannot acquire state change lock problems To manage notifications about this bug go to: https://bugs.launchpad.net/libvirt/+bug/734777/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 842478] Re: virt-manager depends on gnome libraries
I noticed that it also brought in Gnome libraries on Xubuntu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/842478 Title: virt-manager depends on gnome libraries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/842478/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 734777] Re: cannot acquire state change lock problems
I got hit by this on natty. There seems to be a corresponding Red Hat bug at: https://bugzilla.redhat.com/show_bug.cgi?id=676205 ** Bug watch added: Red Hat Bugzilla #676205 https://bugzilla.redhat.com/show_bug.cgi?id=676205 ** Also affects: libvirt via https://bugzilla.redhat.com/show_bug.cgi?id=676205 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/734777 Title: cannot acquire state change lock problems To manage notifications about this bug go to: https://bugs.launchpad.net/libvirt/+bug/734777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 873360] Re: powertop statistics display zero
*** This bug is a duplicate of bug 834725 *** https://bugs.launchpad.net/bugs/834725 ** This bug has been marked a duplicate of bug 834725 Powertop fails to report number of wakeups/events -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/873360 Title: powertop statistics display zero To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/powertop/+bug/873360/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 873360] Re: powertop statistics display zero
*** This bug is a duplicate of bug 834725 *** https://bugs.launchpad.net/bugs/834725 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/873360 Title: powertop statistics display zero To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/powertop/+bug/873360/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 873360] [NEW] powertop statistics display zero
*** This bug is a duplicate of bug 834725 *** https://bugs.launchpad.net/bugs/834725 Public bug reported: I installed powertop to find out information about my laptop's power consumption. Unfortunately it does not display some of the essential statistics, they remain at zero. For example the first line of the Overview screen: Summary: 0.0 wakeups/second, 0.0 GPU ops/second and 0.0 VFS ops/sec All of them stay at 0.0. Also the Events/s column stays at 0.0 for all rows below. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: powertop 1.97-2 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Thu Oct 13 20:44:01 2011 InstallationMedia: Xubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110920.2) ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: powertop UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: powertop (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oneiric -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/873360 Title: powertop statistics display zero To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/powertop/+bug/873360/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 864609] Re: xfce4-terminal fails to record utmp/login entries
Some additional details about this bug: I run strace -o trace.out -f xfce4-terminal and found the following: 6828 execve(/usr/lib/vte/gnome-pty-helper, [gnome-pty-helper], [/* 54 vars */]) = -1 ENOENT (No such file or directory) On my system locate gnome-pty-helper tells me the following: /usr/lib/libvte2-90/gnome-pty-helper /usr/lib/libvte9/gnome-pty-helper Thus the path of gnome-pty-helper is wrong somewhere. I also tried strace -o trace.out -f gnome-terminal for comparison. In that case the path of gnome-pty-helper is correct: 9000 execve(/usr/lib/libvte2-90/gnome-pty-helper, [gnome-pty- helper], [/* 50 vars */]) = 0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/864609 Title: xfce4-terminal fails to record utmp/login entries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-terminal/+bug/864609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 864609] Re: xfce4-terminal fails to record utmp/login entries
Looks like libvte9 package is internally using an incorrect path for gnome-pty-helper. libvte-2.90-9 package of the same library is using the correct path. gnome-terminal updates utmp successfully because it is using the latter library. libvte9 tries to run /usr/lib/vte/gnome-pty-helper but installs /usr/lib/libvte9/gnome-pty-helper. The following shows the incorrect path in libvte.so.9 and the correct path in libvte2_90.so.9: $ strings /usr/lib/libvte.so.9 | fgrep /gnome-pty-helper /usr/lib/vte/gnome-pty-helper $ strings /usr/lib/libvte2_90.so.9 | fgrep /gnome-pty-helper /usr/lib/libvte2-90/gnome-pty-helper This shows where these packages have installed their gnome-pty-helper: $ dpkg -S gnome-pty-helper libvte9: /usr/lib/libvte9/gnome-pty-helper libvte-2.90-9: /usr/lib/libvte2-90/gnome-pty-helper As a workaround I made a symbolic link such as follows: $ ln -s libvte9 /usr/lib/vte $ ls -la /usr/lib/vte lrwxrwxrwx 1 root root 7 2011-10-12 20:14 /usr/lib/vte - libvte9 ...and that solves the problem for me. xfce4-terminal now correctly adds utmp entries. These are the installed libvte package versions: $ apt-cache policy libvte9 libvte-2.90-9 libvte-2.90-9: Installed: 1:0.28.2-0ubuntu2 Candidate: 1:0.28.2-0ubuntu2 Version table: *** 1:0.28.2-0ubuntu2 0 500 http://kh.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages 100 /var/lib/dpkg/status libvte9: Installed: 1:0.28.2-0ubuntu2 Candidate: 1:0.28.2-0ubuntu2 Version table: *** 1:0.28.2-0ubuntu2 0 500 http://kh.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages 100 /var/lib/dpkg/status ** Package changed: xfce4-terminal (Ubuntu) = vte (Ubuntu) ** Summary changed: - xfce4-terminal fails to record utmp/login entries + libvte9 fails to record utmp/login entries -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/864609 Title: libvte9 fails to record utmp/login entries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte/+bug/864609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 864609] Re: libvte9 fails to record utmp/login entries
** Bug watch added: Debian Bug tracker #645104 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645104 ** Also affects: vte (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645104 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/864609 Title: libvte9 fails to record utmp/login entries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte/+bug/864609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 838820] Re: the proxy authentication option is not easy to use
See attached patch. Description: Move the gnome-pty-helper into the -common package and install only a single copy of this set-gid binary in /usr/lib/libvte. The downside of this approach is that the -common package becomes architecture specific. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/838820 Title: the proxy authentication option is not easy to use To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/838820/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 838820] Re: the proxy authentication option is not easy to use
Oops, wrong bug. Sorry about that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/838820 Title: the proxy authentication option is not easy to use To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/838820/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 864609] Re: libvte9 fails to record utmp/login entries
See attached patch. Move the gnome-pty-helper into the -common package and install only a single copy of this set-gid binary in /usr/lib/libvte. The downside of this approach is that the -common package becomes architecture specific. I submitted this to the Debian bug also. ** Patch added: vte-pty-helper-path.patch https://bugs.launchpad.net/ubuntu/+source/vte/+bug/864609/+attachment/2538922/+files/vte-pty-helper-path.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/864609 Title: libvte9 fails to record utmp/login entries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte/+bug/864609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 865499] [NEW] Please include virtio-rng in linux-image-*-virtual
Public bug reported: This is more of a feature request than a bug. Please include the virtio-rng hw_random module in the -virtual kernel package along with the other virtio drivers. Virtual machines often do not have much of hardware randomness available. This can negatively affect performance of cryptographic operations (HTTPS/TLS handshakes, SSH connections, running GPG etc.) as well as simple things such as opening TCP connections. This virtio driver solves the problem with QEMU/KVM by providing randomness available in the host machine to the guests which have this driver loaded. This is then used to seed /dev/random. This module seems to be currently available in the -generic and -server packages (where it is not really needed). ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/865499 Title: Please include virtio-rng in linux-image-*-virtual To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/865499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 865499] Re: Please include virtio-rng in linux-image-*-virtual
apport logs are not useful because this is a feature request. Changing status. ** Changed in: linux (Ubuntu) Status: Incomplete = Opinion ** Changed in: linux (Ubuntu) Status: Opinion = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/865499 Title: Please include virtio-rng in linux-image-*-virtual To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/865499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 864609] [NEW] xfce4-terminal fails to record utmp/login entries
Public bug reported: When using xfce4-terminal (0.4.8-1) on freshly installed Xubuntu 11.10 beta2 x86_64 no utmp entries are being recorded. On the same machine login, sshd, screen, xterm and gnome-terminal all record utmp entries successfully. This is an example output of w and who run on a machine with several xfce4-terminals open: snabb@oil:~$ w 19:47:37 up 2:32, 0 users, load average: 0.52, 2.00, 2.81 USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT snabb@oil:~$ who am i snabb@oil:~$ who -a system boot 2011-10-02 17:15 run-level 2 2011-10-02 17:15 LOGIN tty4 2011-10-02 17:15 1255 id=4 LOGIN tty5 2011-10-02 17:15 1259 id=5 LOGIN tty2 2011-10-02 17:15 1266 id=2 LOGIN tty3 2011-10-02 17:15 1268 id=3 LOGIN tty6 2011-10-02 17:15 1274 id=6 LOGIN tty1 2011-10-02 17:15 2198 id=1 snabb@oil:~$ This is an example output when xterm is being used (with one window open). It can be seen that xterm records utmp entries successfully: snabb@oil:~$ w 19:49:47 up 2:34, 1 user, load average: 0.32, 1.38, 2.48 USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT snabbpts/14 :0.0 19:490.00s 0.33s 0.01s w snabb@oil:~$ who am i snabbpts/14 2011-10-02 19:49 (:0.0) snabb@oil:~$ who -a system boot 2011-10-02 17:15 run-level 2 2011-10-02 17:15 LOGIN tty4 2011-10-02 17:15 1255 id=4 LOGIN tty5 2011-10-02 17:15 1259 id=5 LOGIN tty2 2011-10-02 17:15 1266 id=2 LOGIN tty3 2011-10-02 17:15 1268 id=3 LOGIN tty6 2011-10-02 17:15 1274 id=6 LOGIN tty1 2011-10-02 17:15 2198 id=1 snabb+ pts/14 2011-10-02 19:49 . 10462 (:0.0) snabb@oil:~$ Some additional observations: - I am surprised that gnome-terminal does NOT exhibit this problem. I thought that both xfce4-terminal and gnome-terminal just use libvte routines for utmp handling. - utmp was recently moved to /run/utmp. Maybe this is related? I will add additional details to this report in case I notice something useful. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: xfce4-terminal 0.4.8-1 ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 ApportVersion: 1.23-0ubuntu2 Architecture: amd64 Date: Sun Oct 2 19:42:57 2011 InstallationMedia: Xubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110920.2) ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xfce4-terminal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xfce4-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oneiric -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/864609 Title: xfce4-terminal fails to record utmp/login entries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-terminal/+bug/864609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 864609] Re: xfce4-terminal fails to record utmp/login entries
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/864609 Title: xfce4-terminal fails to record utmp/login entries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-terminal/+bug/864609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
