[Bug 1219428] [NEW] Unlock password dialog blank on resume
Public bug reported: Upon resume, the password dialog did not draw its contents and did not work typing blindly. This is not identical to other bug reports because in this case the rectangle for the window is drawn, but never gains any contents. Screen photo attached. Cannot install mainline or saucy on this machine; mainline won't dkms nvidia and saucy install chokes at the first dialog. So I won't do that as a troubleshooting step at this point, because of ubuntu bugs. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-screensaver 3.6.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Sun Sep 1 05:09:45 2013 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session idle-delay uint32 600 org.gnome.desktop.session session-name 'ubuntu' MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set SHELL=/bin/bash SourcePackage: gnome-screensaver UpgradeStatus: Upgraded to raring on 2013-04-22 (131 days ago) ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring ** Attachment added: screensaverfail.jpg https://bugs.launchpad.net/bugs/1219428/+attachment/3797660/+files/screensaverfail.jpg -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1219428 Title: Unlock password dialog blank on resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1219428/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1189463] [NEW] cannot select text entry field on unlock screen
Public bug reported: Sometimes when I resume from suspend I cannot select the text entry field so that I can enter my password, and the cursor is not in the box. The keyboard is unresponsive, but the mouse works as I can click the buttons, just not the text entry field. Then I have to reboot. I can't even use the text console due to the typical nvidia console bug. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-screensaver 3.6.1-0ubuntu3 Uname: Linux 3.9.0-030900rc8-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 Date: Mon Jun 10 06:08:05 2013 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session idle-delay uint32 600 org.gnome.desktop.session session-name 'ubuntu' MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set SHELL=/bin/bash SourcePackage: gnome-screensaver UpgradeStatus: Upgraded to raring on 2013-04-22 (48 days ago) ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1189463 Title: cannot select text entry field on unlock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1189463/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 588155] Re: randomly gnome-settings-daemon fails to start
I have this problem on an install of lucid from the original alternate ISO and upgraded from there, i386 on a P4 with ATI (Mobility). Compiz is working nicely but gnome-settings-daemon usually doesn't start. No problems on my natty desktop. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/588155 Title: randomly gnome-settings-daemon fails to start -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 776849] [NEW] login panel appears on wrong display with dual monitors
Public bug reported: Binary package hint: gdm nVidia 240 GT, HDMI to DVI and DVI to DVI in use to two displays. If the mouse pointer is left alone it will be on the secondary display, which is to the right physically and logically Then the menu appears on that display, usually whether you move the mouse to the primary display or not The login panel generally appears wherever the mouse is before it appears, but sometimes it appears wherever the menu is ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: gdm 2.32.1-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Tue May 3 19:26:38 2011 ProcEnviron: LANGUAGE=C:en PATH=(custom, user) LANG=C SHELL=/bin/bash SourcePackage: gdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dual natty nvidia running-unity -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/776849 Title: login panel appears on wrong display with dual monitors -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 776849] Re: login panel appears on wrong display with dual monitors
-- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/776849 Title: login panel appears on wrong display with dual monitors -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 274461] Re: gnome-system-monitor window is semi-transparent when using compiz
It is stupid to have the apps set opacity, that is Compiz' job. If you put the settings in the apps the user has to control them per-app. If you let the compositing manager handle opacity then all the settings are in one place. It's not a feature, it's an intentional bug, and it's done the WRONG way. I would go so far as to say it's done the anti-Unix way, which is to have small tools that work well and don't have too many features. This is definitely a feature that doesn't belong in the tool since the typical desktop already has a mechanism for managing this. BUG. -- gnome-system-monitor window is semi-transparent when using compiz https://bugs.launchpad.net/bugs/274461 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 636343] [NEW] nautilus crashed with SIGSEGV in g_closure_invoke()
Public bug reported: Binary package hint: nautilus I was opening nautilus when it failed. No clue. ProblemType: Crash DistroRelease: Ubuntu 10.10 Package: nautilus 1:2.31.90-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.35-20.29-generic 2.6.35.4 Uname: Linux 2.6.35-20-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 CrashCounter: 1 Date: Sun Sep 12 05:22:25 2010 ExecutablePath: /usr/bin/nautilus ProcCmdline: nautilus ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x49f196:mov0x18(%rdi),%r12 PC (0x0049f196) ok source 0x18(%rdi) (0x0018) not located in a known VMA region (needed readable region)! destination %r12 ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: ?? () g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 ?? () from /usr/lib/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0 g_signal_emit () from /usr/lib/libgobject-2.0.so.0 Title: nautilus crashed with SIGSEGV in g_closure_invoke() UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare XsessionErrors: (polkit-gnome-authentication-agent-1:2288): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed (nm-applet:2305): Gdk-CRITICAL **: IA__gdk_window_thaw_toplevel_updates_libgtk_only: assertion `private-update_and_descendants_freeze_count 0' failed ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash maverick -- nautilus crashed with SIGSEGV in g_closure_invoke() https://bugs.launchpad.net/bugs/636343 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 636343] Re: nautilus crashed with SIGSEGV in g_closure_invoke()
** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/636343/+attachment/1573877/+files/Dependencies.txt ** Attachment added: Disassembly.txt https://bugs.launchpad.net/bugs/636343/+attachment/1573878/+files/Disassembly.txt ** Attachment added: GConfNonDefault.txt https://bugs.launchpad.net/bugs/636343/+attachment/1573879/+files/GConfNonDefault.txt ** Attachment added: ProcMaps.txt https://bugs.launchpad.net/bugs/636343/+attachment/1573880/+files/ProcMaps.txt ** Attachment added: ProcStatus.txt https://bugs.launchpad.net/bugs/636343/+attachment/1573881/+files/ProcStatus.txt ** Attachment added: Registers.txt https://bugs.launchpad.net/bugs/636343/+attachment/1573882/+files/Registers.txt ** Attachment added: Stacktrace.txt https://bugs.launchpad.net/bugs/636343/+attachment/1573883/+files/Stacktrace.txt ** Attachment added: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/636343/+attachment/1573884/+files/ThreadStacktrace.txt ** Attachment added: usr_lib_nautilus.txt https://bugs.launchpad.net/bugs/636343/+attachment/1573885/+files/usr_lib_nautilus.txt -- nautilus crashed with SIGSEGV in g_closure_invoke() https://bugs.launchpad.net/bugs/636343 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 631253] [NEW] package evince-common (not installed) failed to install/upgrade: trying to overwrite '/etc/apparmor.d/abstractions/evince', which is also in package evince 2.30.3-0ubuntu1.1
Public bug reported: Binary package hint: evince occurred during update from lucid to maverick ProblemType: Package DistroRelease: Ubuntu 10.10 Package: evince-common (not installed) ProcVersionSignature: Ubuntu 2.6.32-24.42-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Sun Sep 5 18:49:06 2010 ErrorMessage: trying to overwrite '/etc/apparmor.d/abstractions/evince', which is also in package evince 2.30.3-0ubuntu1.1 SourcePackage: evince Title: package evince-common (not installed) failed to install/upgrade: trying to overwrite '/etc/apparmor.d/abstractions/evince', which is also in package evince 2.30.3-0ubuntu1.1 ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package maverick -- package evince-common (not installed) failed to install/upgrade: trying to overwrite '/etc/apparmor.d/abstractions/evince', which is also in package evince 2.30.3-0ubuntu1.1 https://bugs.launchpad.net/bugs/631253 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 631253] Re: package evince-common (not installed) failed to install/upgrade: trying to overwrite '/etc/apparmor.d/abstractions/evince', which is also in package evince 2.30.3-0ubuntu1.1
** Attachment added: AptOrdering.txt https://bugs.launchpad.net/bugs/631253/+attachment/1548418/+files/AptOrdering.txt ** Attachment added: Df.txt https://bugs.launchpad.net/bugs/631253/+attachment/1548419/+files/Df.txt ** Attachment added: Dmesg.txt https://bugs.launchpad.net/bugs/631253/+attachment/1548420/+files/Dmesg.txt ** Attachment added: DpkgTerminalLog.gz https://bugs.launchpad.net/bugs/631253/+attachment/1548421/+files/DpkgTerminalLog.gz -- package evince-common (not installed) failed to install/upgrade: trying to overwrite '/etc/apparmor.d/abstractions/evince', which is also in package evince 2.30.3-0ubuntu1.1 https://bugs.launchpad.net/bugs/631253 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 409640] Re: Video is tinted blue after update
I confirm this bug, using nvidia driver. kgokbulut's fix works perfectly (without reboot.) The bug might be in xv code, but only gstreamer seems to trigger it. -- Video is tinted blue after update https://bugs.launchpad.net/bugs/409640 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gstreamer0.10 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 223772] Re: hibernate, suspend occasionally missing from shutdown menu
While the first time I logged in I had options other than Log Out and Switch User, those days are gone. :P I can still run pm-suspend and pm-hibernate, although last time I ran pm-suspend the system suspended and then immediately woke up (which it did successfully, however.) On 11/21/08, Andy Buckley [EMAIL PROTECTED] wrote: I'm using an up-to-date Intrepid, by the way. -- hibernate, suspend occasionally missing from shutdown menu https://bugs.launchpad.net/bugs/223772 You received this bug notification because you are a direct subscriber of the bug. Status in gnome-power-manager source package in Ubuntu: Incomplete Bug description: Sometimes the Hibernate and Suspend options are missing from the GNOME shutdown menu. This happens without any indication from the system of what the cause is. It would be far better if the user were kept informed of what's going on. For example, ghosted buttons on the shutdown menu, with tooltip indications such as GNOME cannot suspend your system because you don't have the required permissions, ...because gnome-power-manager is not running, ...because the dbus session restarted. Another possibility would be a popup notification when the event happens, e.g. gnome-power-manager has died. You will not be able to suspend your system. or dbus session restarted. Your computer will be unusable. Ha ha, sucks to be you. -- hibernate, suspend occasionally missing from shutdown menu https://bugs.launchpad.net/bugs/223772 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 223772] Re: hibernate, suspend occasionally missing from shutdown menu
I am seeing the same problem with Intrepid, updated as of about thirty minutes ago. I am using avant-window-navigator and have disabled gnome- panel, if that helps. -- hibernate, suspend occasionally missing from shutdown menu https://bugs.launchpad.net/bugs/223772 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
Re: [Bug 243387] Re: Tomboy enters infinite loop of errors on start
Looks like it does NOT happen on a new user account. I previously wiped out everything but the .tomboy directory, which of course contains my notes Looks like if I delete my .tomboy I can come up and reinitialize the system correctly... oho! if I delete my .tomboy/addins-db-001 the problem goes away. attached is my bad .tomboy (sans private notes) ** Attachment added: unnamed http://launchpadlibrarian.net/15637186/unnamed ** Attachment added: badtomboy.tgz http://launchpadlibrarian.net/15637187/badtomboy.tgz -- Tomboy enters infinite loop of errors on start https://bugs.launchpad.net/bugs/243387 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
Re: [Bug 95155] Re: [apport] alacarte crashed while editing menus with Exception in __writeItem()
I was dragging a launcher (I promise, it was a launcher!) that I made to run Dreamweaver 8 in Wine. On 4/7/07, Travis Watkins [EMAIL PROTECTED] wrote: According to the code you were dragging a shell script or regular binary into alacarte, not a launcher. I never thought 'os.path.split(file_path)[1].strip()' would fail to give some sort of output so I didn't put in an exception handler here. What were you dragging into alacarte? ** Changed in: alacarte (Ubuntu) Assignee: (unassigned) = Travis Watkins Status: Confirmed = Needs Info -- [apport] alacarte crashed while editing menus with Exception in __writeItem() https://bugs.launchpad.net/bugs/95155 You received this bug notification because you are a direct subscriber of the bug. -- [apport] alacarte crashed while editing menus with Exception in __writeItem() https://bugs.launchpad.net/bugs/95155 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for alacarte in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 95155] [apport] alacarte crashed while editing menus with Exception in __writeItem()
Public bug reported: Binary package hint: alacarte alacarte in general is not working correctly. this crash was the result of dragging a launcher icon from the desktop to the program. new launchers don't show up until I quit and restart alacarte, and if I drag them to a new position they disppear, but are moved to the correct location (which I find out after restarting alacarte.) The move up/move down buttons work in the same fashion. ProblemType: Crash Architecture: i386 Date: Fri Mar 23 11:35:21 2007 DistroRelease: Ubuntu 7.04 ExecutablePath: /usr/bin/alacarte InterpreterPath: /usr/bin/python2.5 Package: alacarte 0.11.3-0ubuntu1 PackageArchitecture: all ProcCmdline: /usr/bin/python -OOt /usr/bin/alacarte ProcCwd: /home/mespinoza ProcEnviron: LANGUAGE=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 PythonArgs: ['/usr/bin/alacarte'] SourcePackage: alacarte Uname: Linux sec2lpt7-linux 2.6.20-12-generic #2 SMP Sun Mar 18 03:07:14 UTC 2007 i686 GNU/Linux ** Affects: alacarte (Ubuntu) Importance: Undecided Status: Unconfirmed -- [apport] alacarte crashed while editing menus with Exception in __writeItem() https://launchpad.net/bugs/95155 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 95155] Re: [apport] alacarte crashed while editing menus with Exception in __writeItem()
** Attachment added: Dependencies.txt http://librarian.launchpad.net/6904170/Dependencies.txt ** Attachment added: ProcMaps.txt http://librarian.launchpad.net/6904171/ProcMaps.txt ** Attachment added: ProcStatus.txt http://librarian.launchpad.net/6904172/ProcStatus.txt ** Attachment added: Traceback.txt http://librarian.launchpad.net/6904173/Traceback.txt -- [apport] alacarte crashed while editing menus with Exception in __writeItem() https://launchpad.net/bugs/95155 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
