[Bug 1726306] Re: Failure to reactivate display after locking
It's definitely not (directly) related to either of those - I can't even get the display to come back on, let alone enter a password at the lock screen. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1726306 Title: Failure to reactivate display after locking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1726306/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1726306] [NEW] Failure to reactivate display after locking
Public bug reported: I'm using a laptop with no external monitors attached (System76 Oryx Pro 2016). After the screen is locked (either manually or via timeout) and it blanks/deactivates the screen, the display remains deactivated and my session is unrecoverable. (I can still ssh into the machine, but have so far been unable to get the display back without rebooting, even via restarting gdm.) It seems somewhat similar to https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1715811 , but it's only after the display is deactivated, and not at boot. The scope of the problem seems to be compounded by the fact that there's no straightforward way to prevent gnome-shell from blanking the screen when it locks. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.26.1-3ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 23 10:20:55 2017 SourcePackage: gdm3 UpgradeStatus: Upgraded to artful on 2017-10-20 (3 days ago) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ** Attachment added: "syslog" https://bugs.launchpad.net/bugs/1726306/+attachment/4987497/+files/syslog -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1726306 Title: Failure to reactivate display after locking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1726306/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1317116] [NEW] libgtk2.0-dev is not multiarch-ready
Public bug reported: This means that if I want to compile a Gtk+ program for x86 on an amd64 machine, I need to install libgtk2.0-0:i386 and then manually symlink: libgtk-x11-2.0.so libgdk-x11-2.0.so libatk-1.0.so libgio-2.0.so libpangoft2-1.0.so libpangocairo-1.0.so libcairo.so libpango-1.0.so libgobject-2.0.so libglib-2.0.so in /usr/lib/i386-linux-gnu $ sudo apt-get install libgtk2.0-dev:i386 Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libgtk2.0-dev:i386 : Depends: gir1.2-gtk-2.0:i386 (= 2.24.23-0ubuntu1) but it is not going to be installed Depends: libgdk-pixbuf2.0-dev:i386 (= 2.21.0) but it is not going to be installed Depends: libpango1.0-dev:i386 (= 1.20) but it is not going to be installed Depends: libatk1.0-dev:i386 (= 1.29.2) but it is not going to be installed Recommends: python:i386 (= 2.4) but it is not going to be installed E: Unable to correct problems, you have held broken packages. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libgtk2.0-dev 2.24.23-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 7 16:17:56 2014 InstallationDate: Installed on 2011-05-11 (1091 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) SourcePackage: gtk+2.0 UpgradeStatus: Upgraded to trusty on 2014-04-22 (15 days ago) ** Affects: gtk+2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1317116 Title: libgtk2.0-dev is not multiarch-ready To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1317116/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 912909] Re: gimp-2.6 crashed with SIGSEGV
This happens when creating a new file, i.e. on Save As, not Save. Creating an empty file outside of GIMP then saving to that works. Deleting ~/.config/dconf fixed the problem for me. Source: https://bugzilla.redhat.com/show_bug.cgi?id=828015 ** Bug watch added: Red Hat Bugzilla #828015 https://bugzilla.redhat.com/show_bug.cgi?id=828015 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/912909 Title: gimp-2.6 crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/912909/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 224288] Re: Playbar acting strange
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/14017680/Dependencies.txt ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/14017681/ProcMaps.txt ** Attachment added: ProcStatus.txt http://launchpadlibrarian.net/14017682/ProcStatus.txt -- Playbar acting strange https://bugs.launchpad.net/bugs/224288 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 224288] [NEW] Playbar acting strange
Public bug reported: Binary package hint: rhythmbox I know that Rhythmbox has always been this way and I'm not sure if there is a reason, but when you click on the playbar to a point further into the song it will increase the time in increments and keep going past the point of the click. I would image the proper behavior of this should be for the song to jump directly to the that is clicked instead of this strange jumping behavior. ProblemType: Bug Architecture: i386 Date: Tue Apr 29 11:37:12 2008 DistroRelease: Ubuntu 8.04 ExecutablePath: /usr/bin/rhythmbox NonfreeKernelModules: nvidia Package: rhythmbox 0.11.5-0ubuntu6 PackageArchitecture: i386 ProcEnviron: PATH=/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-16-generic i686 ** Affects: rhythmbox Importance: Unknown Status: Unknown ** Affects: rhythmbox (Ubuntu) Importance: Low Assignee: Ubuntu Desktop Bugs (desktop-bugs) Status: Triaged ** Tags: apport-bug -- Playbar acting strange https://bugs.launchpad.net/bugs/224288 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
