[Bug 882160] Re: Extra battery detected which does not exist and is considered empty
*** This bug is a duplicate of bug 852406 *** https://bugs.launchpad.net/bugs/852406 ** This bug has been marked a duplicate of bug 852406 Phantom battery appears after resume from suspend -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/882160 Title: Extra battery detected which does not exist and is considered empty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/882160/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 885722] Re: Automatic hibernate on Dell Latitude E6410 because of phantom battery reading
*** This bug is a duplicate of bug 852406 *** https://bugs.launchpad.net/bugs/852406 ** This bug is no longer a duplicate of bug 882160 Extra battery detected which does not exist and is considered empty ** This bug has been marked a duplicate of bug 852406 Phantom battery appears after resume from suspend -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/885722 Title: Automatic hibernate on Dell Latitude E6410 because of phantom battery reading To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/885722/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 531762] Re: System monitor System tab should show architecture (32/64bit)
System settings now has a "System Info" icon, which shows the 64-bit in the OS type field of the overview. Fixed if you ask me, this bug can be closed. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/531762 Title: System monitor System tab should show architecture (32/64bit) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-system-monitor/+bug/531762/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 442634] Re: if laptop lid already closed, doesn't detect when it should suspend when mains power removed
I can't get the Maverick behavior to work in Oneiric. http://mail.gnome.org/archives/commits-list/2010-November/msg06088.html seems to state that earlier mentioned solutions will not work. I consider this a problem with Oneiric and can't find how to fix it so the behavior is like reported above. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/442634 Title: if laptop lid already closed, doesn't detect when it should suspend when mains power removed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/442634/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 882160] Re: Extra battery detected which does not exist and is considered empty
-- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/882160 Title: Extra battery detected which does not exist and is considered empty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/882160/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 882160] [NEW] Extra battery detected which does not exist and is considered empty
Public bug reported: After a supsend, gnome-power-manager detects a second battery which is empty. The battery shows up in the panel icon. When I start gnome-power-statistics, from the commandline, it lists the second battery and then aborts: $ gnome-power-statistics (gnome-power-statistics:3634): PowerManager-DEBUG: got filename: ac-adapter; (gnome-power-statistics:3634): PowerManager-DEBUG: got filename: gpm-battery-missing;gpm-battery-000;battery-missing; (gnome-power-statistics:3634): PowerManager-DEBUG: got filename: gpm-battery-100-charging;battery-full-charging; (gnome-power-statistics:3634): PowerManager-DEBUG: selected row is: /org/freedesktop/UPower/devices/battery_BAT0 (gnome-power-statistics:3634): PowerManager-DEBUG: selected row is: /org/freedesktop/UPower/devices/battery_BAT1 ** PowerManager:ERROR:gpm-statistics.c:416:gpm_device_state_to_localised_string: code should not be reached Aborted Because I have suspend issues with the new Oneiric release, I had acpi_listen running in the background. This also repots a second battery: Started Wed Oct 26 19:02:13 CEST 2011 battery BAT0 0081 0001 battery BAT1 0081 battery BAT0 0080 0001 The E6510 laptop is notorious for it's power problems. So I would like to add that I have BIOS A10 and no extra kernel parameters at the moment. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-power-manager 3.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-13.21-generic 3.0.6 Uname: Linux 3.0.0-13-generic x86_64 ApportVersion: 1.23-0ubuntu3 Architecture: amd64 CheckboxSubmission: 9acf66a3871e17f683940a81669f9f51 CheckboxSystem: d00f84de8a555815fa1c4660280da308 Date: Wed Oct 26 19:17:50 2011 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GnomeSessionSuspendInhibited: No InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: Dell Inc. Latitude E6510 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-13-generic root=UUID=d9d49fb9-bbe3-4669-9d5f-a707232955d6 ro SourcePackage: gnome-power-manager UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/23/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0N5KHN dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/23/2011:svnDellInc.:pnLatitudeE6510:pvr0001:rvnDellInc.:rn0N5KHN:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6510 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. gnome-power-bugreport: Error: [Errno 2] No such file or directory ** Affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oneiric -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/882160 Title: Extra battery detected which does not exist and is considered empty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/882160/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 649184] Re: empathy-av crashed with SIGSEGV in pthread_mutex_lock()
I was not able to reproduce this bug with the latest versions in maverick. ** Changed in: empathy (Ubuntu) Status: Incomplete => Invalid -- empathy-av crashed with SIGSEGV in pthread_mutex_lock() https://bugs.launchpad.net/bugs/649184 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 649184] Re: empathy-av crashed with SIGSEGV in pthread_mutex_lock()
** Visibility changed to: Public -- empathy-av crashed with SIGSEGV in pthread_mutex_lock() https://bugs.launchpad.net/bugs/649184 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 531762] Re: System monitor System tab does not show architecture (32/64bit)
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/40134634/Dependencies.txt ** Attachment added: "ProcMaps.txt" http://launchpadlibrarian.net/40134635/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://launchpadlibrarian.net/40134636/ProcStatus.txt ** Attachment added: "XsessionErrors.txt" http://launchpadlibrarian.net/40134637/XsessionErrors.txt ** Summary changed: - System monitor System tab does not show architecture (32/64bit) + [wishlist] System monitor System tab should show architecture (32/64bit) -- [wishlist] System monitor System tab should show architecture (32/64bit) https://bugs.launchpad.net/bugs/531762 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-monitor in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 531762] [NEW] [wishlist] System monitor System tab should show architecture (32/64bit)
Public bug reported: Binary package hint: gnome-system-monitor After installing Ubuntu, it is not clear to the user wether they are using a 32bit or a 64bit version. The System Monitor System tab should contain architecture information so people know whether they are running 32bit or 64bit. It is currently unclear to me where people can look to decide which proprietary binary they should download. "uname -a" solves the problem, but a normal user should not rely on the console for this information. ProblemType: Bug Architecture: amd64 Date: Thu Mar 4 08:19:28 2010 DistroRelease: Ubuntu 10.04 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-system-monitor InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20091209) Package: gnome-system-monitor 2.28.0-1ubuntu2 ProcEnviron: PATH=(custom, user) LANG=en_US.utf8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-15.22-generic SourcePackage: gnome-system-monitor Uname: Linux 2.6.32-15-generic x86_64 ** Affects: gnome-system-monitor (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid -- [wishlist] System monitor System tab should show architecture (32/64bit) https://bugs.launchpad.net/bugs/531762 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-monitor in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 470651] Re: window list applet does not show windows from both monitors
*** This bug is a duplicate of bug 412789 *** https://bugs.launchpad.net/bugs/412789 ** This bug has been marked a duplicate of bug 412789 The window selector menu in the panel randomly fails to show some of my open windows. Also, when waking from a sleeping state, the panel does not update, so my clock tells the wrong time, etc. -- window list applet does not show windows from both monitors https://bugs.launchpad.net/bugs/470651 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 305927] Re: gedit leaks memory
I've got a git checkout and rand valgrind, the leaks that are definite according to valgrind: libio (from glib) launchpadintegration bug #483610 glibc nns (g_option_context_parse) libfontconfig in a call of FcConfigParseAndLoad XML_ParseBuffer from g_type_create_instance into fontconfig g_object_newv into fontconfig It seems like there is a leak in pango, libio and launchpadintegration and gedit using them all to leak as fast as it can :) ** Attachment added: "valgrind_log.txt.gz" http://launchpadlibrarian.net/35933511/valgrind_log.txt.gz -- gedit leaks memory https://bugs.launchpad.net/bugs/305927 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 403564] Re: Incorrect battery recall warning for Lenovo T61
1) I reset the parameter gconftool -u /apps/gnome-power-manager/notify/perhaps_recall The recall message came back again after a reboot. 2) I downloaded the rules file. I began with MD5 27e7f10f85cce16411e20af5437fe956 /lib/udev/rules.d/95-devkit-power-battery-recall-ibm.rules And after the copy I had 6cad53b74ceb0115ee732a6505cebdab /lib/udev/rules.d/95-devkit-power-battery-recall-ibm.rules 3) I reset the key again gconftool -u /apps/gnome-power-manager/notify/perhaps_recall 4) After a reboot I did not get a battery recall message again. It's fixed for me! -- Incorrect battery recall warning for Lenovo T61 https://bugs.launchpad.net/bugs/403564 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 403564] Re: Incorrect battery recall warning for Lenovo T61
$ hexdump -C /sys/class/dmi/id/product_name 36 34 36 36 39 4d 47 0a |64669MG.| 0008 I'm not really sure when I last saw the battery reccall message, but I told it to not show it again and that worked for me (in karmic with the latest updates). All hardware is still the same, so the data should still match. -- Incorrect battery recall warning for Lenovo T61 https://bugs.launchpad.net/bugs/403564 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 331099] Re: totem plugin wont play sound on mywoot.net
Clicking "test", as suggested in the report, works perfectly with me on Karmic, 64 bit, Firefox 3.5, totem 2.27.2-0ubuntu4. I can't reproduce this bug on Karmic at this moment. -- totem plugin wont play sound on mywoot.net https://bugs.launchpad.net/bugs/331099 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 277309] Re: Missing suspend icon with non-human theme
I've seen this bug all through Jaunty and the development releases of karmic, I'm still seeing the bug in Karmic at this date. gnome-session: 2.27.5-0ubuntu1 -- Missing suspend icon with non-human theme https://bugs.launchpad.net/bugs/277309 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 407491] Re: [karmic] gnome-power-preferences not storing settings
2.27.5-0ubuntu2~ppa4 did not solve the problem for me. Here is what I have for On Battery Power, When battery power is critically low. >From Combobox to verbose result Suspend -> suspend Hibernate -> blank Shutdown -> hibernate This was just after an "gconftool-2 --recursive-unset /apps/gnome-power- manager", which does seem to effect everything in the listing, but does not solve anything. Also, please let me know if you think having pushed "Make default" before Karmic started, could be of any influence in this. Thanks for the quick uptake! -- [karmic] gnome-power-preferences not storing settings https://bugs.launchpad.net/bugs/407491 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 407491] Re: [karmic] gnome-power-preferences not storing settings
The settings are off-by-one for me, and it looks like storing the settings work. And the settings take effect as soon as they are set. Your log showed: TI:17:26:54 TH:0x207f070FI:gpm-prefs-core.c FN:gpm_prefs_action_combo_changed_cb,267 - Changing /apps/gnome-power-manager/buttons/lid_battery to blank Which means that you have set the lid closed when on battery to "blank". Start gnome-power-preferences with --verbose again and try every entry in the pull-down list. If your bug is the same as mine, the verbose output will show that the preferences manager will set the option just above the one you choose. Just to make this clear, my findings are: 1) What --verbose output is set, and stored/retained. If you then close the preferences manager it will work properly according to what the output told you (not what the GUI shows). 2) As soon as you open gnome-power-preferences, it resets the options (shown in verbose) to new values which are again wrongly shown in the GUI. Closing it after that will have changed your settings even if you didn't do anything. I'm using 64bit with the latest updates (2.27.5-0ubuntu1). I tried installing 64bit karmic alpha 3 in KVM and this did not confirm the bug. However, KVM did not have suspend and hibernate options, so it may be a problem with the insertion of the extra options, or a wrong enumeration value?? -- [karmic] gnome-power-preferences not storing settings https://bugs.launchpad.net/bugs/407491 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 407491] Re: [karmic] gnome-power-preferences not storing settings
Upon futher investigation, settings are stored. The problem was specific to which option I choose, the problem is an off by one thing. For "On Battery Power", "Wehn laptop lid is closed" the options are: Blank Screen Suspend Hibernate Shutdown If I choose Hibernate, --verbose shows - Changing /apps/gnome-power-manager/buttons/lid_battery to suspend choosing shutdown shows hibernate, suspend shows blank, blank shows "nothing". So the option choices are just off-by one and my choice seemed to be ignored but was really stored as the option above it. Soo, choosing Hibernate sets it to suspend. This choice is reflected the next time I open gnome-power-preferences, so it is actually stored. The option box is just off-by-one. Every time I open the application, it loads the options, showing what I chooce -1, saving it on close as shown -1 again, so opening closing, opening will -1 the option also. For some reason hibernate seems to be a default becuase opening and closing a few times seems to have it end up with hibernate. If I set it to hibernate, verifying with --verbose that it actually sets it to suspend, everything works normaly. So the option is stored and acted upon correctly. This bug is merely an interface problem. -- [karmic] gnome-power-preferences not storing settings https://bugs.launchpad.net/bugs/407491 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 407491] Re: [karmic] gnome-power-preferences not storing settings
** Attachment added: "Log showing the output of running gnome-power-preferences --verbose two times" http://launchpadlibrarian.net/29759981/gnome-power-preferences_verbose.log ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/29759983/Dependencies.txt ** Attachment added: "DevkitPower.txt" http://launchpadlibrarian.net/29759984/DevkitPower.txt ** Attachment added: "GConfNonDefault.txt" http://launchpadlibrarian.net/29759985/GConfNonDefault.txt ** Attachment added: "gnome-power-bugreport.txt" http://launchpadlibrarian.net/29759986/gnome-power-bugreport.txt -- [karmic] gnome-power-preferences not storing settings https://bugs.launchpad.net/bugs/407491 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 407491] [NEW] [karmic] gnome-power-preferences not storing settings
Public bug reported: Binary package hint: gnome-power-manager Actions: Open gnome-power-preferences Change settings Close gnome-power-preferences Result: Power management does not follow the set options. Opening the preference window again, shows the settings according to some default and do not reflect the choices I made earlier. Expected result: The settings should have been stored in the configuration. The attached log shows the output of: gnome-power-preferences --verbose > attached_file.log gnome-power-preferences --verbose >> attached_file.log It seems like the settings are not properly stored and/or reset on opening the application. ProblemType: Bug Architecture: amd64 Date: Fri Jul 31 22:29:36 2009 DistroRelease: Ubuntu 9.10 Package: gnome-power-manager 2.27.2+git20090729-0ubuntu2 ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=en_US.UTF-8 ProcVersionSignature: Ubuntu 2.6.31-4.23-generic SourcePackage: gnome-power-manager Uname: Linux 2.6.31-4-generic x86_64 ** Affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug -- [karmic] gnome-power-preferences not storing settings https://bugs.launchpad.net/bugs/407491 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 403564]
** Attachment added: "gnome-power-bugreport.txt" http://launchpadlibrarian.net/29434530/gnome-power-bugreport.txt ** Changed in: gnome-power-manager (Ubuntu) Status: Incomplete => New ** Tags added: apport-collected -- Incorrect recall warning for Lenovo T61 https://bugs.launchpad.net/bugs/403564 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 403564]
** Attachment added: "DevkitPower.txt" http://launchpadlibrarian.net/29434526/DevkitPower.txt -- Incorrect recall warning for Lenovo T61 https://bugs.launchpad.net/bugs/403564 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 403564]
** Attachment added: "GConfNonDefault.txt" http://launchpadlibrarian.net/29434527/GConfNonDefault.txt -- Incorrect recall warning for Lenovo T61 https://bugs.launchpad.net/bugs/403564 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 403564]
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/29434525/Dependencies.txt -- Incorrect recall warning for Lenovo T61 https://bugs.launchpad.net/bugs/403564 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 403564] apport-collect data
Architecture: amd64 DistroRelease: Ubuntu 9.10 Package: gnome-power-manager 2.27.2-0ubuntu2 PackageArchitecture: amd64 ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=en_US.UTF-8 ProcVersionSignature: Ubuntu 2.6.31-3.19-generic Uname: Linux 2.6.31-3-generic x86_64 UserGroups: adm admin audio cdrom dialout dip floppy fuse kvm lpadmin plugdev sambashare video -- Incorrect recall warning for Lenovo T61 https://bugs.launchpad.net/bugs/403564 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 403564] Re: Incorrect recall warning for Lenovo T61
*** This bug is a duplicate of bug 402287 *** https://bugs.launchpad.net/bugs/402287 I personally do not consider this a duplicate. Not being able to hide the recall message, and the recall message being wrong (not contain the correct information as the battery is not being recalled) are two different problems. -- Incorrect recall warning for Lenovo T61 https://bugs.launchpad.net/bugs/403564 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 403564] [NEW] Incorrect recall warning for Lenovo T61
Public bug reported: Binary package hint: gnome-power-manager I've got a Lenovo battery with: ASM P/N: 92P1142 FRU P/N: 92P1141 (top right corner of label) So, I get a recall warning pointing me to the website[1]. I can't run the automated checking system, so I called support. Turns out: there is no recall. The problem is that I have a Lenovo T61 and the T61 is not in the list of machines for which the battery is recalled. Also, 14 moths is more then 12 so it's not in warranty either :( My feelings aside, on to the bug: if the battery is seen inside a T61, it is not being recalled, only if it is seen in another model. I'm not sure how that works, but it probably has something to do with the shipping dates of these models? [1] http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid =BATT-LENOVO ** Affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: New -- Incorrect recall warning for Lenovo T61 https://bugs.launchpad.net/bugs/403564 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 353741] Re: nautilus crashed with SIGSEGV in strlen()
** Attachment added: "CoreDump.gz" http://launchpadlibrarian.net/24687469/CoreDump.gz ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/24687470/Dependencies.txt ** Attachment added: "Disassembly.txt" http://launchpadlibrarian.net/24687471/Disassembly.txt ** Attachment added: "ProcMaps.txt" http://launchpadlibrarian.net/24687472/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://launchpadlibrarian.net/24687473/ProcStatus.txt ** Attachment added: "Registers.txt" http://launchpadlibrarian.net/24687474/Registers.txt ** Attachment added: "Stacktrace.txt" http://launchpadlibrarian.net/24687475/Stacktrace.txt ** Attachment added: "ThreadStacktrace.txt" http://launchpadlibrarian.net/24687476/ThreadStacktrace.txt ** Visibility changed to: Public -- nautilus crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/353741 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 334540] Re: anonymous ftp PASS command sent without argument
** Bug watch added: GNOME Bug Tracker #533219 http://bugzilla.gnome.org/show_bug.cgi?id=533219 ** Also affects: gvfs via http://bugzilla.gnome.org/show_bug.cgi?id=533219 Importance: Unknown Status: Unknown -- anonymous ftp PASS command sent without argument https://bugs.launchpad.net/bugs/334540 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 334540] Re: anonymous ftp PASS command sent without argument
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/23129437/Dependencies.txt -- anonymous ftp PASS command sent without argument https://bugs.launchpad.net/bugs/334540 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 334540] [NEW] anonymous ftp PASS command sent without argument
Public bug reported: Binary package hint: gvfs When connecting to an anonymous FTP account on an FTP server, the gvfs- backend for ftp does not send an argument with the PASS command. This means that for any RFC959 compliant server will not allow the anonymous entry and send back an error message (501 Syntax error: command (PASS) needs an argument.) If the server allows for PASS without an argument (against RFC959) everything will be ok, and the anonymous ftp will be mounted without any problem. When does this happen: always, when connecting with an anonymous FTP server using nautilus. To reproduce it (this is just how I came across it): - Install pyftpdlib from my ppa: https://launchpad.net/~bneijt/+archive/ppa or download it from http://code.google.com/p/pyftpdlib/ - Download an older version of shareftp [1] - Run "shareftp -a" (make sure you have python-avahi installed) - Browse to the ShareFTP share under Network in Nautilus. [1] http://git.logfish.net/?p=shareftp.git;a=blob;f=shareftp;h=45353b6bee141e4d88f367a2da1ddff6b975e252;hb=be76787aef89a14a4e0ba1cf9fe41eb82c194720 ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 9.04 Package: gvfs-backends 1.1.6-0ubuntu2 ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=en_US.UTF-8 SourcePackage: gvfs Uname: Linux 2.6.28-8-generic x86_64 ** Affects: gvfs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug -- anonymous ftp PASS command sent without argument https://bugs.launchpad.net/bugs/334540 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 269986] Re: gedit open in all workspaces
Ah, I think I found the problem then, unmarking it is not saved because gedit core-dumps every time you close it. So it probably doesn't save the preferences because of the core-dump then. This should be fixed as soon as the core-dump is fixed. ** Attachment added: "Gedit core dump" http://launchpadlibrarian.net/21531999/core-dumplog.txt -- gedit open in all workspaces https://bugs.launchpad.net/bugs/269986 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 269986] Re: gedit open in all workspaces
Did you use a 64 bit version of Ubuntu? I'm using the following, so please try to get as close to this configuration as possible: 2.6.28-4-generic #11-Ubuntu SMP Fri Jan 16 21:50:52 UTC 2009 x86_64 GNU/Linux Package: gedit Version: 2.25.4-0ubuntu1 No compiz installed Intel GMA965 / X3100 graphics chip and driver Focus follows mouse Gnome 2.25.4 To reproduce it, simply start gedit, either from the terminal or the menu. The bug seems so obvious that I actually thought it would be removed in a matter of days and did not report it at first. -- gedit open in all workspaces https://bugs.launchpad.net/bugs/269986 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 269986] Re: gedit open in all workspaces
This is not a Xubuntu bug. In Jaunty using the plain vanilla Ubuntu (64bit) and Gnome, starting gedit from a terminal will start it with "Always on visible workspace". To reproduce: - Open a gnome-terminal - Type gedit - Right click on the window bar of gedit, observe the Workspace visibility status Does this happen all the time? Yes ** Also affects: gedit (Ubuntu) Importance: Undecided Status: New -- gedit open in all workspaces https://bugs.launchpad.net/bugs/269986 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 253570] Re: Searching may stop current song
Here is the last part, which should contain the problem. I'm not sure what I should be looking for, but I have seen this: (16:29:51) [0xb41500] [rb_shell_player_get_playing_song_duration] rb-shell-player.c:3385: Did not get playing entry : return -1 as length Attached is the last part of the log (after the whole database was mentioned). ** Attachment added: "rhythmbox_debuglog.txt" http://launchpadlibrarian.net/18138503/rhythmbox_debuglog.txt -- Searching may stop current song https://bugs.launchpad.net/bugs/253570 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 253570] Re: Searching may stop current song
I ran that, but that log also included a complete listing of my library of songs and information about my file system layout. So I would have to read that log and remove the lines out of it before I'm going to post that here. I don't have time for that now, so please consider asking for a more specific debug or just ask me again and I will find the time to clean up the log. You can also send me a personal request because I am willing to send it to you personally via mail. I'm currently on intrepid with rhythmbox 0.11.6. It seems I can only reproduce the problem with cross-fade enabled and in an automatic listing. Because it is very probably a timing issue, I suggest placing your system under load when testing for this. (disk IO may help). So here are some steps again: 1. Create an automatic playlist 2. Make sure cross-fading is enabled in the preferences 3. If possible, use Vorbis VBR files 4. Make sure there is some load on the system. Although this is not really needed, it may help in enlarging the window of opportunity. 5. While playing a song, type something in the search bar. Try different key strokes with different delays, use backspace if needed. It may very well be that this bug: http://bugzilla.gnome.org/show_bug.cgi?id=553230 is related to this problem, as it seems to do with song end signals and time problems when the crossfading is enabled. -- Searching may stop current song https://bugs.launchpad.net/bugs/253570 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 242149] Re: Clicking 'Up' or 'Back' whilst generating thumbnails does not change location URL
I'm confirming this bug and have have a way of reproducing it: increase the system load. To reproduce: 1. First make sure you have allot of load on your HD and the location bar is visible in nautilus. You can introduce system load by reading allot of files from disk, for example: cat * */* > /dev/null (make sure you have enough and large files in * and */* to make your HD really work as fast as possible) 2. Click on a directory (doesn't need to be in the places bar) 3. Make sure the location bar has updated to the new location, but you shouldn't be able to see anything yet. The GNOME foot is still wiggling it's toes. 4. Click on the up button. Result: The content of the directory you started in is shown immediately because it comes from cache. However, the location bar is still pointing to the directory you entered at step 2. Expected result: The location bar should always point to the directory you are currently viewing. -- Clicking 'Up' or 'Back' whilst generating thumbnails does not change location URL https://bugs.launchpad.net/bugs/242149 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 253570] Re: Searching may stop current song
I've made a screencast of what happens. It's terrible quality, but I think it shows the point. Searching in the automatic playlist (as shown in the movie) will skip to other songs and eventually completely stop when the result list is empty. If I type something that doesn't result in any songs quickly, then the current song will simply stay running. One of these behaviors is a bug: either an empty search should stop the song (always) or it should never influence the playing song (which I prefer ;) ). ** Attachment added: "rb_autolistproblems.ogg" http://launchpadlibrarian.net/16532815/rb_autolistproblems.ogg -- Searching may stop current song https://bugs.launchpad.net/bugs/253570 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 253570] Re: Searching may stop current song
Yes, it happens with the "My Top Rated" list. Trying it out a bit, I also had the following result, which is generally the same. It does seem to be some kind of timing issue, so it might help to have more numbers in your automatic list (you can also just create one which includes all your music). My automatic playlist contains about 4000 numbers and searches take about 500ms (less then a second, but notacable). I also found another way to reprocude the problem: - Create the automatic playlist with enough numbers to make searching a bit slower then instantanious - Star playing a song from that list (any song with enough minutes to test the next steps will do) - Type in one letter, and at the moment you think the results are going to show up add another letter. Keep doing this till the result set is empty. When it hits that empty list, any playing music is stopped. I've got both shuffle and repeat on, and sometimes I saw it skip to another song, so I think the result is that it search the search result as an update of the automatic list and then chooses a new number from the list. If the list is empty, it just stops. I might be able to make a screencast, but I can't see how this would help if you can't reproduce the problem. Hope the above steps will work. -- Searching may stop current song https://bugs.launchpad.net/bugs/253570 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 253570] Re: Searching may stop current song
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/16437774/Dependencies.txt ** Attachment added: "ProcMaps.txt" http://launchpadlibrarian.net/16437775/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://launchpadlibrarian.net/16437776/ProcStatus.txt -- Searching may stop current song https://bugs.launchpad.net/bugs/253570 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 253570] [NEW] Searching may stop current song
Public bug reported: Binary package hint: rhythmbox There seems to be some kind of race condition that, given the right timing, will stop the current song from playing if search results are empty. To reproduce: 1) Use an automatic playlist (not sure this is needed) 2) Play a song from the playlist 3) Looking at the playlist while playing the song, try searching for something you don't have 4) Repeatedly change the search results by changing the search box values just after the search has been done. One example would be: type "asdf", wait for some result and quickly do backspace and add some other letteres. Repeat this a couple of times. Result: Once in a while, it seems to be something with timing and also with empty search results, the current song will stop playing. Expected result: The current song should not be influenced at all by the kind or number of search results I get. Notes: it seems to be some kind of race condition and may or may not be related to the automatic playlist. Rhythmbox 0.11.5, amd64, Hardy. ProblemType: Bug Architecture: amd64 Date: Thu Jul 31 10:35:09 2008 DistroRelease: Ubuntu 8.04 ExecutablePath: /usr/bin/rhythmbox Package: rhythmbox 0.11.5-0ubuntu8 PackageArchitecture: amd64 ProcEnviron: PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rhythmbox Uname: Linux 2.6.24-19-generic x86_64 ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug -- Searching may stop current song https://bugs.launchpad.net/bugs/253570 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 240187] [NEW] Focus conflict blocks all input
Public bug reported: Binary package hint: gnome-keyring There is a situation where a focus conflict seems to arise. When this happens, I can't change anything or enter the required password. The only thing that is possible is moving to another terminal and killing the keyring applicaiton. Steps to reproduce the bug (this is how I got it, but other methods are probably possible): 1) Turn of you wireless AP (for which the password will be retrieved from the keyring) 2) Make sure your keyring is closed (e.g. reboot) 3) Click on the network manager to see a list of wireless APs, keep this menu open by not selecting any of them. 4) Turn on your wireless AP, this will make the network manager discover the AP and ask for the keyring password 5) When the keyring password entry dialog appears, try to access it. What happens: When the last step is executed, the dialog is not accessible, not in focus and none of the windows respond. The network manager has focus for it's sub-menu and won't let go (because it is blocked, probably for the password) and the keyring dialog can't seem to get the focus in any way. At this point, none of the X things seems to work. I tried: Alt-tab, clicking, clicking on window list, using enter, using space, typing in something, Alt-F2 to be able to execute something. None of those work. The solution that worked was opening another terminal and killing gnome- keyring and then switching back. Although this bug is raised with the network-manager, I think it's possible to find other programs affected by this. Therefore I think it might be a problem that needs to be solved at the gnome-keyring level. Kernel 2.6.24-18-generic #1 SMP x86_64 GNU/Linux gnome-keyring Version: 2.22.2-0ubuntu1 network-manager Version: 0.6.6-0ubuntu5 Ubuntu Hardy ** Affects: gnome-keyring (Ubuntu) Importance: Undecided Status: New -- Focus conflict blocks all input https://bugs.launchpad.net/bugs/240187 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 111736] Re: Mouse cursor not visible at popup in fullscreen mode
** Attachment added: "Dependencies.txt" http://librarian.launchpad.net/7511490/Dependencies.txt ** Attachment added: "ProcMaps.txt" http://librarian.launchpad.net/7511491/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://librarian.launchpad.net/7511492/ProcStatus.txt -- Mouse cursor not visible at popup in fullscreen mode https://bugs.launchpad.net/bugs/111736 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for totem in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 111736] Mouse cursor not visible at popup in fullscreen mode
Public bug reported: Binary package hint: totem This is a very low priority feature-request like bug. Because I can imagine it being fixed easily, it might be worth mentioning. When the user gets an error report or message box from totem, when totem is in full screen mode, the cursor will stay hidden except for on the popup itself. The user can solve this problem by simply pressing space or blindly searching for the center of the screen with the mouse, because the cursor will show up on the popup itself. To reproduce: 1) Open a movie in totem 2) Play the movie 3) Move/remove the movie from it's location 4) Put totem in fullscreen mode (press F) 5) Wait until the controls have vanisched (don't move the mouse for long enough) 6) Wait for the end of the movie. What happens: At the end of the movie, totem will try to open the first file in the playlist (that same movie) but it has been moved (step 3) and will produce an error telling you totem can't find the movie. When this message pops up, the mouse cursor is not visible. Expected result: the mouse cursor would become visible again to allow you to use that to press the "OK" button. ProblemType: Bug Architecture: i386 Date: Wed May 2 11:12:59 2007 DistroRelease: Ubuntu 7.04 ExecutablePath: /usr/bin/totem Package: totem-gstreamer 2.18.1-0ubuntu3 PackageArchitecture: i386 ProcCmdline: totem ProcCwd: /home/bram ProcEnviron: LANGUAGE=en_US:en PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: totem Uname: Linux pooh 2.6.20-13-386 #2 Sun Mar 25 00:18:53 UTC 2007 i686 GNU/Linux ** Affects: totem (Ubuntu) Importance: Undecided Status: Unconfirmed -- Mouse cursor not visible at popup in fullscreen mode https://bugs.launchpad.net/bugs/111736 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for totem in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 74297] Genius SlimStar 310 (GK-050010/C) keyboard layout missing
Public bug reported: Binary package hint: gnome-control-center My new SlimStar 310 keyboard has some keys are not registered. There needs to be a new keyboard layout, along with some setkeycodes to get the kernel to support some of the keys. Some of the keys include e011 and e02d (from kernel messages). I couldn't find documentation on adding all this myself, but I am willing to help. ** Affects: control-center (Ubuntu) Importance: Undecided Status: Unconfirmed -- Genius SlimStar 310 (GK-050010/C) keyboard layout missing https://launchpad.net/bugs/74297 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 71253] Re: Crash on fast clicking on rating in automatic playlist
Here is a complete report from the "Problem report for" help program. Due to the ease with which this problem is recreated I havn't taken the time to install the debugsysms for the used program. And the problem can simply be avoided by clicking more slowely or simply turning on shuffle so it is impossible to click on song that just started playing. Hopefully, this report does add something however. ** Attachment added: "Crash report file" http://librarian.launchpad.net/5063244/_usr_bin_rhythmbox.1000.crash -- Crash on fast clicking on rating in automatic playlist https://launchpad.net/bugs/71253 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 71253] Crash on fast clicking on rating in automatic playlist
Public bug reported: Using a automatic playlist with only unrated (rating=0) songs, rhythmbox will crash if you click on the songs rating quickly and repeatedly (songs will be removed from the list if their rating goes up). This is probably a race condition problem. To reproduce the bug: 1) Make sure you have songs with zero rating (no stars) 2) Create an automatic playlist matching only zero rated songs (no stars). 3) Don't enable shuffle 4) Start clicking on the rating of the playing song and keep clicking until it crashes (about 10 to 20 songs on my machine). Clicking will bring up the song below it and remove the song from the list. If you click fast enough rythmbox will crash. Misc info: rythmbox 0.9.6 gstreamer 0.10 Ogg Vorbis music files ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: Unconfirmed -- Crash on fast clicking on rating in automatic playlist https://launchpad.net/bugs/71253 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
