[Bug 1741027] Re: [SRU] Screen sharing panels abort using an non-existent vino gsettings key
Thanks Khurshid and Gunnar. Hi Khurshid, can you help provide the details per comment #24 to proceed further? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741027 Title: [SRU] Screen sharing panels abort using an non-existent vino gsettings key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1741027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741027] Re: [SRU] Screen sharing panels abort using an non-existent vino gsettings key
When can we expect this fix to be back-ported to 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/1741027 Title: [SRU] Screen sharing panels abort using an non-existent vino gsettings key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1741027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821632] Re: dmidecode causing system crash
We could see the random crashes while using ubiquity plugins when dmidecode (arm64) is installed on the system. If dmidecode package is removed the system is stable and no crash is observed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821632 Title: dmidecode causing system crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/1821632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821632] Re: dmidecode causing system crash
We are using Ubuntu 18.04 (Bionic) Arm64 variant of distro -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821632 Title: dmidecode causing system crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/1821632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1699311] [NEW] package mysql-server-5.7 5.7.18-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: package install error ProblemType: Package DistroRelease: Ubuntu 16.04 Package: mysql-server-5.7 5.7.18-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-54-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Tue Jun 20 18:28:18 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-06-18 (2 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Logs.var.log.daemon.log: MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql] MySQLConf.etc.mysql.conf.d.mysqldump.cnf: [mysqldump] quick quote-names max_allowed_packet = 16M MySQLConf.etc.mysql.mysql.conf.d.mysqld_safe_syslog.cnf: [mysqld_safe] syslog MySQLVarLibDirListing: ['ibtmp1', 'ib_logfile1', 'auto.cnf', 'ib_buffer_pool', 'ibdata1', 'performance_schema', 'mysql', 'ib_logfile0', 'debian-5.7.flag', 'sys'] ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.8.0-54-generic.efi.signed root=UUID=2b3ac252-4938-4f2b-8027-4eccc8b2807a ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: mysql-5.7 Title: package mysql-server-5.7 5.7.18-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mysql-5.7 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-package third-party-packages xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1699311 Title: package mysql-server-5.7 5.7.18-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1699311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1460259] [NEW] Incorrect dependency for openvswitch-pki in trusty updates
Public bug reported: I am using Ubuntu trusty with latest updates Description:Ubuntu 14.04.2 LTS Release:14.04 When trying to install the package openvswitch-pki it says The following packages have unmet dependencies: openvswitch-pki : Depends: openvswitch-common (< 2.0.1+git20140120-0ubuntu2.1~) but 2.0.2-0ubuntu0.14.04.2 is to be installed On the web page for openvswitch-pki package the dependency is listed as openvswitch-common (<< 2.0.2-0ubuntu0.14.04.1.1~) Open vSwitch common components openvswitch-common (>= 2.0.2-0ubuntu0.14.04.1) Because of this I am not able to install any openvswitch packages. Ninad ** Affects: openvswitch (Ubuntu) Importance: Undecided Status: New ** Tags: dependency openvswitch-pki -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1460259 Title: Incorrect dependency for openvswitch-pki in trusty updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1460259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1297140] Re: Ubuntu 12.04 (LTS) - icehouse - heat packaging issues
Is there any workaround for this issue that can be used till a fix is done? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1297140 Title: Ubuntu 12.04 (LTS) - icehouse - heat packaging issues To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-manuals/+bug/1297140/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 773285] Re: nspluginwrapper installation fails during upgrade to Natty
Solution works for me as well. Upgraded from Maverick to Natty at RC1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/773285 Title: nspluginwrapper installation fails during upgrade to Natty -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 321927] Re: /dev/pts and /dev/shm not mounted on boot
@scottywz Just saw your second comment. domount is a shell function and has been included from the /lib/init/mount-functions.sh script on line 28. Please see if the fix at bug 360160 helps you, which is due to a modified mountdevusbfs.sh script. In case it works, we might have found out where things are going wrong. -- /dev/pts and /dev/shm not mounted on boot https://bugs.launchpad.net/bugs/321927 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 321927] Re: /dev/pts and /dev/shm not mounted on boot
scottywz's workaround was successful. As per bug 360160, I replaced the mountdevusbfs.sh with the package maintainers version, and it solved the problem for me. After seeing the above comments, I checked my incorrectly functioning mountdevusbfs.sh script which I had backed up, and I confirm that the Should-Start did not have udev in it. Also, a diff of the 2 files shows that the earlier script had mountvirtfs in the Provides line, which is not there in the newer script. The diff has been attached to bug 360160. Kindly refer to that for further details. -- /dev/pts and /dev/shm not mounted on boot https://bugs.launchpad.net/bugs/321927 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 360160] Re: gnome-terminal does not launch on upgrade to jaunty
@Githlar: If you upgraded from an earlier version of Ubuntu, then there will be a mountdevusbfs.sh.dpkg-dist file in your /etc/init.d/ directory. Create a backup copy of the existing moundevusbfs.sh, and then replace it with the dpkg-dist file. If you don't have a dpkg-dist file due to some reasons, please download the file attached to this post, and copy it to /etc/init.d/ with 755 as the permission and root as the user and group of the file. At the same time, comment/remove the hack in the /etc/fstab, and then reboot. ** Attachment added: "mountdevsubfs.sh" http://launchpadlibrarian.net/25810146/mountdevsubfs.sh -- gnome-terminal does not launch on upgrade to jaunty https://bugs.launchpad.net/bugs/360160 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 360160] Re: gnome-terminal does not launch on upgrade to jaunty
I confirm that replacing mountdevusbfs.sh with mountdevusbfs.sh.dpkg- dist fixed the issue. This was done along with commenting the line in /etc/fstab. A side-by-side diff of the two mountdevusbfs is attached. Line 41 of the file shows that the options for 'domount devpts' have been changed. While I remember that any fiddling that I had done was in the next few lines, the ones after the comment "Magic to make /proc/bus/usb work", I did not touch any other parts of the file. ** Attachment added: "mountdevusbfs.sh.diff" http://launchpadlibrarian.net/25479439/mountdevusbfs.sh.diff -- gnome-terminal does not launch on upgrade to jaunty https://bugs.launchpad.net/bugs/360160 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 360160] Re: gnome-terminal does not launch on upgrade to jaunty
I do remember modifying the mountdevusbfs.sh in my Intrepid install for a work around needed in VirtualBox. But I also remember asking the dist-upgrader to replace mountdevusbfs.sh with the package maintainers version while upgrading to Jaunty. That must be the reason for this bug. I'll try what David did and get back to you all. However, it will take a little time as I have an exam in a few hours. P.S.: Attaching the term.log of dist-upgrade. I did not find any mention of mountdevusbfs.sh in the log. So I might be wrong altogether. ** Attachment added: "dist-upgrade term.log" http://launchpadlibrarian.net/25470225/term.log -- gnome-terminal does not launch on upgrade to jaunty https://bugs.launchpad.net/bugs/360160 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 360160] Re: gnome-terminal does not launch on upgrade to jaunty
I do remember modifying the mountdevusbfs.sh in my Intrepid install for a work around needed in VirtualBox. But I also remember asking the dist-upgrader to replace mountdevusbfs.sh with the package maintainers version while upgrading to Jaunty. That must be the reason for this bug. I'll try what David did and get back to you all. However, it will take a little time as I have an exam in a few hours. P.S.: Attaching the term.log of dist-upgrade. I did not find any mention of mountdevusbfs.sh in the log. So I might be wrong altogether. ** Attachment added: "dist-upgrade term.log" http://launchpadlibrarian.net/25468867/term.log -- gnome-terminal does not launch on upgrade to jaunty https://bugs.launchpad.net/bugs/360160 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 360160] Re: gnome-terminal does not launch on upgrade to jaunty
** Attachment added: "udev.devices.txt" http://launchpadlibrarian.net/25462106/udev.devices.txt -- gnome-terminal does not launch on upgrade to jaunty https://bugs.launchpad.net/bugs/360160 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 360160] Re: gnome-terminal does not launch on upgrade to jaunty
** Attachment added: "udev.log.txt" http://launchpadlibrarian.net/25462139/udev.log.txt -- gnome-terminal does not launch on upgrade to jaunty https://bugs.launchpad.net/bugs/360160 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 360160] Re: gnome-terminal does not launch on upgrade to jaunty
Here are my outputs of /etc/rcS.d, /etc/init.d, /lib/udev/devices and /var/log/udev. All these outputs are on a system where the /etc/fstab has been modified and the ptys are now accessible. If you need the above with no changes to fstab, let me know, I'll post them as well. ** Attachment added: "init.d.txt" http://launchpadlibrarian.net/25461927/init.d.txt -- gnome-terminal does not launch on upgrade to jaunty https://bugs.launchpad.net/bugs/360160 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 360160] Re: gnome-terminal does not launch on upgrade to jaunty
** Attachment added: "rcS.d.txt" http://launchpadlibrarian.net/25462002/rcS.d.txt -- gnome-terminal does not launch on upgrade to jaunty https://bugs.launchpad.net/bugs/360160 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 360160] Re: gnome-terminal does not launch on upgrade to jaunty
*** This bug is a duplicate of bug 321927 *** https://bugs.launchpad.net/bugs/321927 @Andreas: As per comment #62 on bug 321927, this bug is not related to that bug, and hence should be looked into. I am new here, so will need help. Please let me know any additional information that you need, to confirm this as a bug or invalid. -- gnome-terminal does not launch on upgrade to jaunty https://bugs.launchpad.net/bugs/360160 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 321927] Re: /dev/pts and /dev/shm not mounted on boot
> The original reporter's problem, and most of the duplicates/commentors, > is caused by running chkconfig/insserv which re-ordered the directory > incorrectly. This is assumedly a bug in those tools for not obeying the > Should-Start: udev directive in mountdevsubfs.sh > > If other people have this problem and *have not* reordered the init > script, they have a different bug I have not used either chkconfig or insserv to re-order the rcS.d directory, nor did I play it manually. So in that case, bug 360160 which I reported is not a duplicate of this bug, and should not be marked invalid. I am new here, so might need a little help. :) -- /dev/pts and /dev/shm not mounted on boot https://bugs.launchpad.net/bugs/321927 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 321927] Re: /dev/pts and /dev/shm not mounted on boot
I confirm scottywz's workaround of adding a line to fstab. I upgraded from a clean Intrepid install to a Jaunty install on 12/4/09, done by an alternate cd and getting the latest packages from the net. I noticed this error as soon as i rebooted after the upgrade process completed. Simply mounting /dev/pts with the right options did not work. Only editing fstab and rebooting solved the issue. Should I also provide outputs of ls /etc/rcS.d or anything else? -- /dev/pts and /dev/shm not mounted on boot https://bugs.launchpad.net/bugs/321927 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 331303] Re: nmap script engine run time error
I too confirm this bug in Jaunty (development). This only occurs when script scanning is enabled, ie then nmap is used with option '-sC', which is included in the option '-A'. Please let me know if more information is needed about this. Will be happy to help. -- nmap script engine run time error https://bugs.launchpad.net/bugs/331303 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 360160] Re: gnome-terminal does not launch on upgrade to jaunty
** Attachment added: "output of apport-cli -fp gnome-terminal" http://launchpadlibrarian.net/25293016/bugreport.txt -- gnome-terminal does not launch on upgrade to jaunty https://bugs.launchpad.net/bugs/360160 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 360160] [NEW] gnome-terminal does not launch on upgrade to jaunty
Public bug reported: Binary package hint: gnome-terminal Package: gnome-terminal ( 2.26.0-0ubuntu2 ) Description: Ubuntu upgraded from Intrepid to Jaunty using alternate iso and the latest packages over the net. After the upgrade completed ( with one small error in tzdata-java, which was rectified with a dpkg --configure -a )m I rebooted the system, and logged into GNOME. When I attempted to launch gnome-terminal, "There was an error creating the child process for this terminal" was the error it reported. Konsole on the other hand just spawned a new window and did not respond to anything after that. Fix: Searching on the net pointed me to these two links: 1. Launchpad Bug - SSH results in "There was an error creating the child process for this terminal" ( https://bugs.launchpad.net/gnome- terminal/+bug/332517 ). 2. LinuxQuestions.org forum : http://www.linuxquestions.org/questions/slackware-14/cant- start-a-terminal-200544/ Both the work arounds required that a line be added to /etc/fstab : devpts /dev/ptsdevpts gid=5,mode=620 0 0 Rebooting after this edit fixed the issue. However, this seems more like a hack than a solution. Attachments: The bug report produced by 'apport-cli -fp gnome-terminal' after fixing /etc/fstab Current system, as reported by lsb_release -rd: Description:Ubuntu jaunty (development branch) Release:9.04 ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: fstab gnome-terminal jaunty upgrade -- gnome-terminal does not launch on upgrade to jaunty https://bugs.launchpad.net/bugs/360160 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 212813] Re: PSI can't find GPG key [ERROR: This message is encrypted, and you are unable to decrypt it.]
Am really sorry! My mistake... As I said, I'd compiled from source... Will be more careful next time before I post. Thanx for pointing it out... -- PSI can't find GPG key [ERROR: This message is encrypted, and you are unable to decrypt it.] https://bugs.launchpad.net/bugs/212813 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 212813] Re: PSI can't find GPG key [ERROR: This message is encrypted, and you are unable to decrypt it.]
I confirm the bug on Kubuntu 8.10, with Psi 0.12 (compiled from source with check install). I was unable use my gpg key with Psi, which I could do in earlier versions of Psi and Ubuntu (dont remember which version of Psi though) The above solution of installing libqca2-plugin-gnupg worked for me too. If this is not a bug as such, then it should be included in the documentation/description of Psi that this package is necessary. Thank You Jana for the solution. -- PSI can't find GPG key [ERROR: This message is encrypted, and you are unable to decrypt it.] https://bugs.launchpad.net/bugs/212813 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75295] Re: system freeze while accessing DVD drive
I forgot to add the following in my earlier post... uname -a Linux mustang 2.6.24-21-generic #1 SMP Tue Oct 21 23:43:45 UTC 2008 i686 GNU/Linux Also attaching my lshw ** Attachment added: "Output of lshw by Ninad Pundalik" http://launchpadlibrarian.net/19274745/lshw.txt -- system freeze while accessing DVD drive https://bugs.launchpad.net/bugs/75295 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75295] Re: system freeze while accessing DVD drive
I tried the steps mentioned in the above post on my current Ubuntu Hardy installation. However, the upgrade in firmware gave me a respite for only 2-3 weeks and my system started locking up again, just as it used to before. I could never get uptimes beyond 2 days due to this, and I always had to stay at the system, just in case I had to reboot it. (My system is a laptop). However, I noticed that whenever the system was about to lock up, the hal-daemon process used up a high amount of process in polling my CD Drive, /dev/sdb. So, I have disabled hal polling on the drive by using 'hal-disable-polling --device /dev/sdb'. Ever since then, I have not had any problems about a system lock up. However, as the polling has been disabled, it has also disabled the auto-mount on my CD Drive, as hal-addon-storage is not working for /dev/sdb. A work around that I use is to enable hal polling temporarily when I use the drive, and disable it once I am done with the drive. Can someone confirm if this is correct? If it is not, kindly tell me what should I do. I'd be glad to help in fixing this problem. -- system freeze while accessing DVD drive https://bugs.launchpad.net/bugs/75295 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
