[Bug 200614] Re: segfault and warnings from net-snmp 5.4.x
me too, would be great to see this fix in Hardy. -- segfault and warnings from net-snmp 5.4.x https://bugs.launchpad.net/bugs/200614 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 340075] Re: Cannot connect to ICQ ("The client version you are using is too old.") (2009-03-09)
yes, today pidgin 2.5.2 (intrepid) stopped working with ICQ ("your client
version is too old").
we need the upgrade in Intrepid.
--
Cannot connect to ICQ ("The client version you are using is too old.")
(2009-03-09)
https://bugs.launchpad.net/bugs/340075
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 340151] Re: ICQ protocol update [March 2009]
thanks for this fast update in Intrepid, ICQ protocol works again. -- ICQ protocol update [March 2009] https://bugs.launchpad.net/bugs/340151 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 290277] Re: Hide new IM conversation setting acts like 'never' when set to 'always'
ja, weird behavior. have the same (intrepid / pidgin 2.5.2) with one of my buddies. chat window for this one buddy popped up. This buddy seems to ignore preferences settings (hide new conversations - always). related: http://developer.pidgin.im/ticket/7380 -- Hide new IM conversation setting acts like 'never' when set to 'always' https://bugs.launchpad.net/bugs/290277 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 236881] Re: Firefox crashes when trying to eval xpath
i get the same exception with an empty firefox profile and installed colorful tabs extension, but not segmentation fault. Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.3) Gecko/2008101315 Ubuntu/8.10 (intrepid) Firefox/3.0.3 maybe related: http://forums.binaryturf.com/viewtopic.php?f=1&t=57 sorry for cross posting. -- Firefox crashes when trying to eval xpath https://bugs.launchpad.net/bugs/236881 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 244238] Re: Firefox 3.0 ignores general.useragent.locale (breaks extensions and firefox xpi language packs)
ok, thanks for clarify this. for development and testing i simply set now the LANG environment variable in my ant exec task before starting FF (and no longer us -UILocale ...). works for me. -- Firefox 3.0 ignores general.useragent.locale (breaks extensions and firefox xpi language packs) https://bugs.launchpad.net/bugs/244238 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 236881] Re: Firefox crashes when trying to eval xpath
but exception was not gone after disable or even uninstall colorful tabs. maybe, colorful tabs uninstall not completely or it change something in FF prefs to force this exception during startup how i reproduced it: 1. create a clean new FF profile -> start FF -> NO exception 2. install colorful tabs (3.6) -> restart FF -> exception 3. disable colorful tabs -> restart FF -> exception 4. uninstall colorful tabs -> restart FF -> exception to be sure, that this is related to colorful tabs, i created another new FF profile and installed some other Add-on -> got NO exception -- Firefox crashes when trying to eval xpath https://bugs.launchpad.net/bugs/236881 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 244238] Re: Firefox 3.0 ignores general.useragent.locale (breaks extensions and firefox xpi language packs)
same thing here, default locale is en_US (should be so, but for testing need firefox de-DE) - installed Applications/System/Supported Language: English and German (default English) - firefox about:config general.useragent.locale="de-DE" - UA: "Mozilla/5.0 (X11; U; Linux x86_64; de-DE; rv:1.9.0.3) Gecko/2008092510 Ubuntu/8.04 (hardy) Firefox/3.0.3" locale LANG=en_US.UTF-8 LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE="en_US.UTF-8" LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL= workaround for me too: firefox -UILocale de-DE (i need this for testing only, default should stay en-US, but want to switch locale with Quick Locale Switcher https://addons.mozilla.org/de/firefox/addon/1333) -- Firefox 3.0 ignores general.useragent.locale (breaks extensions and firefox xpi language packs) https://bugs.launchpad.net/bugs/244238 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 316252] Re: Unable to retrieve MSN Address Book
same here (Ubuntu 8.10, pidgin 2.5.2) above mentioned workaround helps: 1. apt-get install msn-pecan 2. restart pidgin 3. edit account and change from MSN to WLM protocol 4. enable account again Thanks -Moo -- Unable to retrieve MSN Address Book https://bugs.launchpad.net/bugs/316252 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 289098] Re: VMWare keyboard mapping made incorrect on recent Ubuntu Intrepid 8.10 Updates -dated Fri Oct 24 2008
thanks for posting this workaround: echo 'xkeymap.nokeycodeMap = true' >> ~/.vmware/config i got this one-time warning after vmware (6.5.1 build-126130, host: Ubuntu Intrepid, guest: Windows XP) restart: A language-specific mapping from X keysyms to machine scancodes will be used, based on the detected keyboard type of "de101", because you are not using an XFree86 server running on the local machine. However, this program's language-specific mapping may not be correct for your keyboard in all the details, because X keyboard mappings vary. You can override specific key mappings in the virtual-machine configuration. For more information, please see VMware Workstation documentation available on our Web site at "http://vmware.com/info?id=10";. but the workaround solved to use DELETE, INSERT etc. with vmware again. - Moo -- VMWare keyboard mapping made incorrect on recent Ubuntu Intrepid 8.10 Updates -dated Fri Oct 24 2008 https://bugs.launchpad.net/bugs/289098 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 289098] Re: VMWare keyboard mapping made incorrect on recent Ubuntu Intrepid 8.10 Updates -dated Fri Oct 24 2008
yep, i switched to set xkeymap.keycode as described above in ~/.vmware/config too. it also works for me without getting vmware workstation startup warning. thanks. - Moo -- VMWare keyboard mapping made incorrect on recent Ubuntu Intrepid 8.10 Updates -dated Fri Oct 24 2008 https://bugs.launchpad.net/bugs/289098 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 623144] Re: chkutmp assert failure: *** stack smashing detected ***: ./chkutmp terminated
Would be cool to get this fix in Lucid. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/623144 Title: chkutmp assert failure: *** stack smashing detected ***: ./chkutmp terminated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chkrootkit/+bug/623144/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 652929] Re: maverick rc gnome-settings-dameon doesn't start
After uprading a box from Lenny to Maverick I had exactly the same symptoms as Cameron describes: panel isn't styled, theme isn't applied to all windows etc. (grey and ugly gnome UI). in ~/.xsession_errors I had the same warning as Cameron: ** (gnome-settings-daemon:2028): WARNING **: You can only run one xsettings manager at a time; exiting The interesting part is, that after 7 reboots, suddenly the error in .xsession_errors was gone. That sounds, that we have here a timing issue not a configuration issue. Nevertheless, I reinstalled: aptitude reinstall gnome-control-center rebooted 3 times to verify. The mentioned error is gone and the panel and windows appear as expected. -- maverick rc gnome-settings-dameon doesn't start https://bugs.launchpad.net/bugs/652929 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 544139] Re: Active VT tracking can fail at startup
I had the same symptoms as Damien desribed in #9 (no automount of external drives, shutdown or restart was not possible as user). I used a similar workaround as Sepero pointed out in #10 (ubuntuforum link). My workaround were the following 2 steps: edit /etc/init/rc-sysinit.conf old: "start on filesystem and net-device-up IFACE=lo" new: "start on filesystem and started rsyslog and net-device-up IFACE=lo" apt-get install ifupdown --reinstall --purge Environment: - Lucid 2.6.32-24-generic #41-Ubuntu SMP Thu Aug 19 01:38:40 UTC 2010 x86_64 GNU/Linux - NVIDIA UNIX x86_64 Kernel Module 195.36.24 -- Active VT tracking can fail at startup https://bugs.launchpad.net/bugs/544139 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 544139] Re: Active VT tracking can fail at startup
sorry for my last comment #91. This workaround did not work for me. Same symptoms (no automount external drives, no shutdown etc.) after reboot. @Lennie I tested now your quick hack ppa from #66. I have not tested as intensive as Damien, but it works well after 10 reboots on my box. -- Active VT tracking can fail at startup https://bugs.launchpad.net/bugs/544139 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 544139] Re: Active VT tracking can fail at startup
Lennie, Damien, "trying again" is not written on my box zgrep "trying again" /var/log/* | wc -l 0 grep "console-kit" /var/log/syslog.1 | grep "Aug 31" | grep -v "VT_WAITACTIVE" Aug 31 07:51:10 st-002 console-kit-daemon[1369]: WARNING: ck_get_a_console_fd, choose: /dev/tty0 Aug 31 07:51:10 st-002 console-kit-daemon[1369]: WARNING: console_fd: 11 Aug 31 07:51:10 st-002 console-kit-daemon[1369]: WARNING: input of ck_get_active_console_num: 11 Aug 31 07:51:10 st-002 console-kit-daemon[1369]: WARNING: Current VT: tty7 Aug 31 07:51:10 st-002 console-kit-daemon[1369]: WARNING: skipping: 7 -- Active VT tracking can fail at startup https://bugs.launchpad.net/bugs/544139 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 544139] Re: Active VT tracking can fail at startup
just FYI: the latest ppa (0.4.1-3ubuntu1-lbesselink7) works for me. grep "but failed" /var/log/syslog | wc -l 0 grep "console-kit" /var/log/syslog | grep -v "VT_WAITACTIVE" Sep 1 11:49:26 st-002 console-kit-daemon[1368]: WARNING: did not fail Sep 1 11:49:26 st-002 console-kit-daemon[1368]: WARNING: skipping: 7 -- Active VT tracking can fail at startup https://bugs.launchpad.net/bugs/544139 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 544139] Re: Active VT tracking can fail at startup
Damien, i had the symptoms (no automount of external drives and shutdown/restart not working as user) described above in this bug at 99% of my reboots (On my new box since 4 weeks nearly with every daily boot - it's a workstation, not a server). As I had other priorities on this new box (i870 with ssd) I had just ignored this UI shutdown-problem ( sudo shutdown -h 0 works well :) ). As i am not familiar with consolekit and boot process, I have no clue for which string or which startup sequence I need to look with the stock ubuntu consolekit package. I have not systematic tested with the stock Ubuntu package, what's the difference in the error-case and the good-case was. If Lennie is interested in, he can build a ppa with debug logging, but without the re-try fix, so I can try to reproduce the bug on my box with a nearly original Lucid-consolekit package, but with more logging. Additionally what could be helpful: I will reboot several times with the original stock Ubuntu consolekit package to be sure, that I can reproduce the bug on this box (to validate my 99% failure rate without any fix...). -- Active VT tracking can fail at startup https://bugs.launchpad.net/bugs/544139 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 544139] Re: Active VT tracking can fail at startup
okay, I've used the original Lucid consolekit package (0.4.1-3ubuntu1) for some reboot tests. I can reproduce the symptoms: 1. reboot: okay - 2. .. 5. reboot failed with the symptoms. 1. reboot syslog (ok) egrep "console" /var/log/syslog_20100901_2 | grep -v activation Sep 1 18:16:04 st-002 rsyslogd-2039: Could no open output file '/dev/xconsole' [try http://www.rsyslog.com/e/2039 ] Sep 1 18:16:04 st-002 kernel: [0.00] console [tty0] enabled 2. reboot syslog (failed) egrep "console" /var/log/syslog_20100901_3 | grep -v activation Sep 1 18:20:03 st-002 rsyslogd-2039: Could no open output file '/dev/xconsole' [try http://www.rsyslog.com/e/2039 ] Sep 1 18:20:03 st-002 kernel: [0.00] console [tty0] enabled Sep 1 18:20:03 st-002 init: Failed to open system console: Input/output error Sep 1 18:20:04 st-002 console-kit-daemon[1050]: WARNING: Could not determine active console Good. Now I'll try to reproduce this timing problem with Lennies PPA. -- Active VT tracking can fail at startup https://bugs.launchpad.net/bugs/544139 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 544139] Re: Active VT tracking can fail at startup
I've repeated the tests with Lennies ppa (0.4.1-3ubuntu1-lbesselink7) In 9/10 reboots this is my syslog: grep console /var/log/syslog | grep -v VT_WAITACTIVE Sep 1 19:00:26 st-002 rsyslogd-2039: Could no open output file '/dev/xconsole' [try http://www.rsyslog.com/e/2039 ] Sep 1 19:00:26 st-002 kernel: [0.00] console [tty0] enabled Sep 1 19:00:26 st-002 init: Failed to open system console: Input/output error Sep 1 19:00:30 st-002 console-kit-daemon[1364]: WARNING: did not fail Sep 1 19:00:30 st-002 console-kit-daemon[1364]: WARNING: skipping: 7 in 1/10 reboot this is my syslog: grep console /var/log/syslog_20100901_9 | grep -v VT_WAITACTIVE Sep 1 18:58:08 st-002 rsyslogd-2039: Could no open output file '/dev/xconsole' [try http://www.rsyslog.com/e/2039 ] Sep 1 18:58:08 st-002 kernel: [0.00] console [tty0] enabled Sep 1 18:58:09 st-002 console-kit-daemon[1147]: WARNING: did not fail Sep 1 18:58:09 st-002 console-kit-daemon[1147]: WARNING: skipping: 1 Sep 1 18:58:09 st-002 console-kit-daemon[1147]: WARNING: skipping: 7 In all 10/10 reboots I have no symptoms as I've got with the original stock Lucid package (missing external drives etc.). I do not understand how "init: Failed to open system console: Input/output error" is related. -- Active VT tracking can fail at startup https://bugs.launchpad.net/bugs/544139 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 544139] Re: Active VT tracking can fail at startup
Lennie, no, unfortunately zero. all say with your ppa "did not fail". -- Active VT tracking can fail at startup https://bugs.launchpad.net/bugs/544139 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 454566] Re: False positive for SucKit
i have exact the same behavior and output as Maxime wrote in #14. This false positive happens on my box since 17.08.2010 after this update: "Preparing to replace upstart 0.6.5-6 (using .../upstart_0.6.5-7_amd64.deb)" -- False positive for SucKit https://bugs.launchpad.net/bugs/454566 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 544139] Re: Active VT tracking can fail at startup
Colin, sorry. At the moment I can test for Lucid only. Anyone else? -- Active VT tracking can fail at startup https://bugs.launchpad.net/bugs/544139 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 544139] Re: Active VT tracking can fail at startup
I rebooted my box (Lucid) 10 times. Good, I cannot reproduce the symptoms described in #9 or #109. zero errors. all okay. no fail or error in syslog. The Lucid consolekit package 0.4.1-3ubuntu2~ppa1 from cjwatson (#124 and #128) works for me. -- Active VT tracking can fail at startup https://bugs.launchpad.net/bugs/544139 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 550559] Re: hdd problems, failed command: READ FPDMA QUEUED
I had the same ugly ata errors with my Asus P7P55D-E Premium and a Crucial C300 SATA drive. lspci: SATA controller: Device 1b4b:9123 (rev 10) my workaround: disable NCQ and now I can use my SATA3 drive through the Marvell 9123 controller of my MoBo. (see: http://ubuntuforums.org/showpost.php?p=9684933&postcount=12) I tested this workaround with iozone3 without any errors. before this workaround: Aug 6 09:58:08 st-002 kernel: [3.249455] ata5.00: ATA-9: C300-CTFDDAC256MAG, 0002, max UDMA/100 Aug 6 09:58:08 st-002 kernel: [3.249461] ata5.00: 500118192 sectors, multi 1: LBA48 NCQ (depth 31/32), AA after this workaround: Aug 6 10:01:36 st-002 kernel: [3.369991] ata5.00: ATA-9: C300-CTFDDAC256MAG, 0002, max UDMA/100 Aug 6 10:01:36 st-002 kernel: [3.369996] ata5.00: 500118192 sectors, multi 1: LBA48 NCQ (not used) I have not found, if this bug is patched in any linux kernel yet (I'm using 2.6.32-24 64-bit). -- hdd problems, failed command: READ FPDMA QUEUED https://bugs.launchpad.net/bugs/550559 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 550559] Re: hdd problems, failed command: READ FPDMA QUEUED
marvell 9123 sata ahci initialization errors: https://bugzilla.kernel.org/show_bug.cgi?id=15573 ** Bug watch added: Linux Kernel Bug Tracker #15573 http://bugzilla.kernel.org/show_bug.cgi?id=15573 -- hdd problems, failed command: READ FPDMA QUEUED https://bugs.launchpad.net/bugs/550559 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 544139] Re: Active VT tracking can fail at startup
Lennie, I made 10 reboot tests. Looks good to me: 8x: Sep 2 09:16:04 st-002 kernel: [0.00] console [tty0] enabled Sep 2 09:16:04 st-002 init: Failed to open system console: Input/output error Sep 2 09:16:05 st-002 console-kit-daemon[1085]: WARNING: tried but failed Sep 2 09:16:05 st-002 console-kit-daemon[1085]: WARNING: eventually choose to use 12 Sep 2 09:16:05 st-002 console-kit-daemon[1085]: WARNING: first fd was 3 Sep 2 09:16:05 st-002 console-kit-daemon[1085]: WARNING: retried 1 times Sep 2 09:16:05 st-002 console-kit-daemon[1085]: WARNING: skipping: 7 2x Sep 2 09:17:40 st-002 kernel: [0.00] console [tty0] enabled Sep 2 09:17:41 st-002 console-kit-daemon[1161]: WARNING: did not fail Sep 2 09:17:41 st-002 console-kit-daemon[1161]: WARNING: skipping: 1 Sep 2 09:17:41 st-002 console-kit-daemon[1161]: WARNING: skipping: 7 0.4.1-3ubuntu1-lbesselink9 works for me, too. -- Active VT tracking can fail at startup https://bugs.launchpad.net/bugs/544139 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
