[Desktop-packages] [Bug 1345585] [NEW] xorg.conf with manual config is moved away at upgrade
Public bug reported: I need to configure a couple of options for the nvidia driver, e.g. Coolbits. For this I have /etc/X11/xorg.conf which contains purely my manual configuration. I have found that this file is being renamed xorg.conf.MMDD at irregular intervals, thereby disabling these manual settings. /var/lib/dpkg/info/nvidia-prime.postrm is very likely what's causing this: case $1 in purge|remove|upgrade|failed-upgrade|abort-install|abort-upgrade|disappear) # Remove the xorg.conf if [ -f $xorg_conf ]; then mv $xorg_conf $xorg_conf.$now fi Iiuc this is run on every upgrade of the nvidia-prime package. I don't know the reasons for doing this, but given that /etc/X11/xorg.conf is still intended (only) for manual configuration, it should not summarily be moved away. If there's a risk for conflicting old configs then they should be detected more accurately and handled through the normal tools that updates/replaces /etc files containing local changes. ** Affects: nvidia-prime (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1345585 Title: xorg.conf with manual config is moved away at upgrade Status in “nvidia-prime” package in Ubuntu: New Bug description: I need to configure a couple of options for the nvidia driver, e.g. Coolbits. For this I have /etc/X11/xorg.conf which contains purely my manual configuration. I have found that this file is being renamed xorg.conf.MMDD at irregular intervals, thereby disabling these manual settings. /var/lib/dpkg/info/nvidia-prime.postrm is very likely what's causing this: case $1 in purge|remove|upgrade|failed-upgrade|abort-install|abort-upgrade|disappear) # Remove the xorg.conf if [ -f $xorg_conf ]; then mv $xorg_conf $xorg_conf.$now fi Iiuc this is run on every upgrade of the nvidia-prime package. I don't know the reasons for doing this, but given that /etc/X11/xorg.conf is still intended (only) for manual configuration, it should not summarily be moved away. If there's a risk for conflicting old configs then they should be detected more accurately and handled through the normal tools that updates/replaces /etc files containing local changes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1345585/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 726480] Re: gnome-screensaver forces itself upon xscreensaver users
Can note that this still happens in Trusty, and since bug #726471 is fixed, this user level workaround now works: mkdir -p ~/.local/share/dbus-1/services cat EOF ~/.local/share/dbus-1/services/org.gnome.ScreenSaver.service [D-BUS Service] Name=org.gnome.ScreenSaver Exec= EOF On a side note, I do believe this is a bug in gnome screensaver. It should have a notion of whether or not it is supposed to be managing screensaving in the user session, and if not then it should respond to DBus clients with an appropriate error if they try to activate it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/726480 Title: gnome-screensaver forces itself upon xscreensaver users Status in “gnome-screensaver” package in Ubuntu: Confirmed Bug description: Binary package hint: gnome-screensaver gnome-screensaver installs the DBus file /usr/share/dbus-1/services/org.gnome.ScreenSaver.service which unconditionally starts gnome-screensaver whenever some other process (e.g. nm-applet, update-notifier) pull the trigger. This is troubling for users of non-gnome desktop environments, e.g. LXDE. A workaround for me was to install the following /usr/local/share/dbus-1/services/org.gnome.ScreenSaver.service: [D-BUS Service] Name=org.gnome.ScreenSaver Exec=/bin/sh -c 'if xscreensaver-command -version /dev/null 21; then renice +10 $$ /dev/null 21; while sleep 60; do :; done else exec /usr/bin/gnome-screensaver; fi' gnome-screensaver-placeholder The dummy process remains active because if it exited immediately, dbus might try to restart gnome-screensaver. I don't know if this is really necessary. First of all, this needs to be fixed -- screensavers should not step on each others' toes. Secondly, is there a more elegant workaround? Note that because of bug #726471, a user can't override a misguided /usr/share/ service file in his home (~/.local/share) configuration: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/726471 ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: gnome-screensaver 2.30.0-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.31-11.154-rt Uname: Linux 2.6.31-11-rt i686 Architecture: i386 Date: Mon Feb 28 12:44:49 2011 GnomeSessionIdleInhibited: Unknown GnomeSessionInhibitors: Failed to acquire InstallationMedia: Xubuntu 10.04 Lucid Lynx - Release i386 (20100429) ProcEnviron: LC_COLLATE=C PATH=(custom, user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: gnome-screensaver WindowManager: gnome-wm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/726480/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 794307] Re: VPN login notification message gets many don't show this again buttons
This bug disappears if I remove the notification-daemon package and only use notify-osd (because there are not buttons at all in then). ** Package changed: network-manager-applet (Ubuntu) = notification- daemon (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/794307 Title: VPN login notification message gets many don't show this again buttons Status in “notification-daemon” package in Ubuntu: New Bug description: Each time the VPN Login Message notification box shows, regardless whether it's for a successful vpn connect or a vpn dropout error, it gets another Don't show this message again button. All the buttons appear next to each other on the same line, which means the notification box soon gets wider than the screen. I can make it grow more and more buttons by repeatedly connecting and disconnecting a vpn session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notification-daemon/+bug/794307/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 896376] Re: Galaxy Nexus (MTP, phone) and Xoom (MTP, tablet) don't show up in Banshee
I have these symptoms, but the .is_audio_player suggestion does not work for me. libmtp 1.1.2, banshee 2.2.1. The banshee debug log does not say anything useful: [1 Debug 18:55:30.868] Delayed Initializating Banshee.Dap.DapService [1 Debug 18:55:30.872] Dap support extension loaded: Banshee.Dap.MassStorage [1 Debug 18:55:30.872] Dap support extension loaded: Banshee.Dap.AppleDevice [1 Debug 18:55:30.873] Dap support extension loaded: Banshee.Dap.Mtp [1 Debug 18:55:30.874] Delayed Initializating Banshee.Daap.DaapService [3 Debug 18:55:30.879] Refreshing any podcasts that haven't been updated in over an hour [4 Debug 18:55:31.007] DAAP Proxy listening for connections on port 8089 [1 Debug 18:55:31.882] Finished - Startup Job mtp-detect shows the device just fine. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to banshee in Ubuntu. https://bugs.launchpad.net/bugs/896376 Title: Galaxy Nexus (MTP, phone) and Xoom (MTP, tablet) don't show up in Banshee Status in Banshee Music Player: New Status in “banshee” package in Ubuntu: Triaged Bug description: I have a new phone, but it doesn't show up in Banshee. I've even recompiled libmtp to add the device ID, but that didn't help. As the same thing happens with my Xoom tablet (also an Android device), which is included in the unpatched libmtp, I think this is a Banshee bug. The MTP plugin is enabled. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: banshee 2.2.1-1ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6 Uname: Linux 3.0.0-13-generic x86_64 ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Fri Nov 25 19:45:32 2011 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha amd64 (20110803) ProcEnviron: PATH=(custom, user) LANG=nl_NL.UTF-8 SHELL=/bin/bash SourcePackage: banshee UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/banshee/+bug/896376/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 684538] Re: Opening calendar applet on gnome-panel in Ubuntu 10.10 is slow
I still experience this problem in Natty (haven't tested Oneiric since it's unusable on a desktop). I can confirm that the delays are much worse with Google calendars as opposed to On the Web calendars. ** Changed in: gnome-panel (Ubuntu) Status: Expired = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/684538 Title: Opening calendar applet on gnome-panel in Ubuntu 10.10 is slow Status in “gnome-panel” package in Ubuntu: Confirmed Bug description: Binary package hint: gnome-panel Clicking on the Clock applet on gnome-panel takes a few seconds to display the calendar. This occurs with Google Calendar enabled in Evolution and Evolution in online mode. With Evolution in off- line mode, the applet opens quickly. In System Monitor, I can see the Network utilization spike each time I click on the Clock applet. Referencing Bug #87796, other users have suggested that the clock applet is retrieving information from Google each time it is opened. This behavior is exhibited in Ubuntu 10.10 (x64). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/684538/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 727660] Re: The panel encountered a problem while loading... on a live session
Martin Stjernholm (msub) wrote on 2011-09-19: Furthermore, I have never experienced the problem if I log out and back in again. I have to correct myself on this. I have now seen it after a logout/login cycle as well. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-applets in Ubuntu. https://bugs.launchpad.net/bugs/727660 Title: The panel encountered a problem while loading... on a live session Status in “gnome-applets” package in Ubuntu: Incomplete Bug description: Binary package hint: gnome-panel ISO Testing Natty Alpha3, booting in a live session I get errors about Applet Loading. While reporting I'm having «The panel encountered a problem while loading TrashAppletFactory::TrashApplet » but in a previous boot I got error on notification area applet. Testcase performed: Live Session: http://testcases.qa.ubuntu.com/Install/DesktopLiveSession Attaching a screenshot ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: gnome-panel 1:2.32.1-0ubuntu6 ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6 Uname: Linux 2.6.38-5-generic i686 Architecture: i386 Date: Wed Mar 2 09:17:47 2011 GConfNonDefault: /apps/panel/general/applet_id_list=[indicator_appmenu_screen0,trashapplet_screen0,workspace_switcher_screen0,window_list_screen0,show_desktop_button_screen0,indicator_applet_screen0,notification_area_screen0] /apps/panel/general/object_id_list=[menu_bar_screen0] /apps/panel/general/toplevel_id_list=[bottom_panel_screen0,top_panel_screen0] /apps/panel/global/disable_lock_screen=true LiveMediaBuild: Ubuntu 11.04 Natty Narwhal - Alpha i386 (20110302) ProcEnviron: LANGUAGE=it_IT:en LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: gnome-panel UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-applets/+bug/727660/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 727660] Re: The panel encountered a problem while loading... on a live session
Indeed, that is an interesting observation. I can confirm it: Out of three boxes I have with Natty, only one exhibits this behavior on a regular basis, and that is also the only one with autologin. Furthermore, I have never experienced the problem if I log out and back in again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-applets in Ubuntu. https://bugs.launchpad.net/bugs/727660 Title: The panel encountered a problem while loading... on a live session Status in “gnome-applets” package in Ubuntu: Incomplete Bug description: Binary package hint: gnome-panel ISO Testing Natty Alpha3, booting in a live session I get errors about Applet Loading. While reporting I'm having «The panel encountered a problem while loading TrashAppletFactory::TrashApplet » but in a previous boot I got error on notification area applet. Testcase performed: Live Session: http://testcases.qa.ubuntu.com/Install/DesktopLiveSession Attaching a screenshot ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: gnome-panel 1:2.32.1-0ubuntu6 ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6 Uname: Linux 2.6.38-5-generic i686 Architecture: i386 Date: Wed Mar 2 09:17:47 2011 GConfNonDefault: /apps/panel/general/applet_id_list=[indicator_appmenu_screen0,trashapplet_screen0,workspace_switcher_screen0,window_list_screen0,show_desktop_button_screen0,indicator_applet_screen0,notification_area_screen0] /apps/panel/general/object_id_list=[menu_bar_screen0] /apps/panel/general/toplevel_id_list=[bottom_panel_screen0,top_panel_screen0] /apps/panel/global/disable_lock_screen=true LiveMediaBuild: Ubuntu 11.04 Natty Narwhal - Alpha i386 (20110302) ProcEnviron: LANGUAGE=it_IT:en LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: gnome-panel UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-applets/+bug/727660/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
