[Bug 1799293] Re: Locking the screen once leaves screen contents visible but not interactive. Locking the screen a second time works.
@hjwp2, For most folk I do believe Super+L twice is sufficient but it isn't a full workaround. While it does suspend the machine, it doesn't prevent the thing folks are fussing about: If someone wakes up your machine the UI is still bugged, so a random citizen is still able to interact with the docks (so they can run any script you have in your dock). That and... maybe you don't want to suspend your machine. How big of a deal these are is... relative. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799293 Title: Locking the screen once leaves screen contents visible but not interactive. Locking the screen a second time works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1799293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800352] Re: screen lock leaves desktop and current applications displayed unless activated twice
(Eh, where "it" is hitting Super+L a second time. The first time of course just freezes the screen, as reported.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800352 Title: screen lock leaves desktop and current applications displayed unless activated twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1800352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800352] Re: screen lock leaves desktop and current applications displayed unless activated twice
@hjwp2 - FWIW, for me it does bring up the lock screen but it's still bugged, as--while I cannot interact with them once they're started--I am able to start applications in the Gnome Dock and as well as interact with any Gnome Activities Bar widgets. Depending on what's on your dock, I suppose this could be "bad". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800352 Title: screen lock leaves desktop and current applications displayed unless activated twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1800352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806194] [NEW] Lock screen / Screensaver doesn't work in Ubuntu 18.10
Public bug reported: In Gnome, when I hit "Super-L" my screen freezes but the image remains intact instead of taking me to a login screen. Further, I can still access the application dock and start applications (though I cannot see the apps or interact with them) and I can interact with the top activities bar. Maybe it's useful, maybe not, but I'm using X11 not Wayland due to an issue with my NVidia card. $ gnome-screensaver-command --lock ** (gnome-screensaver-command:22849): WARNING **: 10:37:00.517: unable to send message: Timeout was reached ** Message: 10:37:00.517: Did not receive a reply from the screensaver. $ vi /var/log/syslog Dec 1 10:36:31 hostname dbus-daemon[1488]: [session uid=123 pid=1488] Reloaded configuration Dec 1 10:36:31 hostname dbus-daemon[2445]: [session uid=1000 pid=2445] Reloaded configuration Dec 1 10:36:31 hostname dbus-daemon[1488]: [session uid=123 pid=1488] Reloaded configuration Dec 1 10:36:31 hostname dbus-daemon[2445]: [session uid=1000 pid=2445] Reloaded configuration Dec 1 10:36:31 hostname dbus-daemon[1488]: [session uid=123 pid=1488] Reloaded configuration Dec 1 10:36:31 hostname dbus-daemon[2445]: [session uid=1000 pid=2445] Reloaded configuration Dec 1 10:36:35 hostname gnome-shell[2614]: pushModal: invocation of begin_modal failed Dec 1 10:36:35 hostname gnome-shell[2614]: ../../../../gobject/gsignal.c:2641: instance '0x556570a1cbb0' has no handler with id '143890' Dec 1 10:36:35 hostname gnome-shell[2614]: ../../../../gobject/gsignal.c:2641: instance '0x556570a1cbb0' has no handler with id '143891' Dec 1 10:36:35 hostname gnome-shell[2614]: Object Meta.WindowActor (0x556573104440), has been already deallocated — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Dec 1 10:36:35 hostname org.gnome.Shell.desktop[2614]: == Stack trace for context 0x55656e024200 == Dec 1 10:36:35 hostname org.gnome.Shell.desktop[2614]: #0 7ffe9ff3c590 b resource:///org/gnome/gjs/modules/overrides/GObject.js:468 (7f6fa3ecc040 @ 25) Dec 1 10:36:35 hostname org.gnome.Shell.desktop[2614]: #1 5565960b1138 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:416 (7f6fa068aca0 @ 20) Dec 1 10:36:35 hostname org.gnome.Shell.desktop[2614]: #2 7ffe9ff3d700 b self-hosted:261 (7f6fa3ec1dc0 @ 223) Dec 1 10:36:35 hostname org.gnome.Shell.desktop[2614]: #3 5565960b1080 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:415 (7f6fa068ac10 @ 172) Dec 1 10:36:35 hostname org.gnome.Shell.desktop[2614]: #4 7ffe9ff3e810 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7f6fa3eb0b80 @ 71) Dec 1 10:36:35 hostname org.gnome.Shell.desktop[2614]: #5 5565960b1000 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:424 (7f6fa068ad30 @ 17) Dec 1 10:36:35 hostname org.gnome.Shell.desktop[2614]: #6 7ffe9ff3f780 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7f6fa3eb0b80 @ 71) Dec 1 10:36:35 hostname org.gnome.Shell.desktop[2614]: #7 5565960b0f80 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:89 (7f6fa068a430 @ 42) Dec 1 10:36:35 hostname org.gnome.Shell.desktop[2614]: #8 7ffe9ff406f0 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7f6fa3eb0b80 @ 71) Dec 1 10:36:35 hostname org.gnome.Shell.desktop[2614]: #9 5565960b0ef8 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:456 (7f6fa067f280 @ 82) Dec 1 10:36:35 hostname org.gnome.Shell.desktop[2614]: #10 7ffe9ff41660 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7f6fa3eb0b80 @ 71) Dec 1 10:36:35 hostname org.gnome.Shell.desktop[2614]: #11 5565960b0e60 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1784 (7f6fa0684670 @ 116) Dec 1 10:36:35 hostname org.gnome.Shell.desktop[2614]: #12 7ffe9ff425d0 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7f6fa3eb0b80 @ 71) Dec 1 10:36:35 hostname org.gnome.Shell.desktop[2614]: #13 5565960b0de0 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1903 (7f6fa0684a60 @ 37) Dec 1 10:36:35 hostname org.gnome.Shell.desktop[2614]: #14 7ffe9ff43540 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7f6fa3eb0b80 @ 71) Dec 1 10:36:35 hostname org.gnome.Shell.desktop[2614]: #15 5565960b0d60 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/extension.js:31 (7f6fa06759d0 @ 12) Dec 1 10:36:35 hostname org.gnome.Shell.desktop[2614]: #16 5565960b0ca0 i resource:///org/gnome/shell/ui/extensionSystem.js:83 (7f6fa3a5a040 @ 436) Dec 1 10:36:35 hostname org.gnome.Shell.desktop[2614]: #17 5565960b0c20 i resource:///org/gnome/shell/ui/extensionSystem.js:354 (7f6fa3a5ab80 @ 13) Dec 1 10:36:35 hostname org.gnome.Shell.desktop[2614]: #18 7ffe9ff446b0 b self-hosted:261 (7f6fa3ec1dc0 @ 223) Dec 1 10:36:35 hostname
[Bug 205349] Re: install from usb
This is a old bug report (2008) but I think I got the sample problem today (2012)... and maybe I can help with details about the problem. I download Ubuntu image ubuntu-12.04-desktop-amd64.iso e wrote it on usb pen-drive, under Windows 7, using tue recommended software Universal-USB-Installer-1.9.0.4. I did like this: http://www.ubuntu.com/download/help/create-a-usb-stick-on-windows. I got no (unexpected) problems booting from the first boot menu option Run Ubuntu from this USB. Just my usual LCD back light problem that I am familiar with. Because of this known problem I need to set nomodeset at startup in order to turn my LCD screem lights on... So I went to Help menu item... and in the Help index, I pick F6 Special boot parameters for special machines. It shows this at the bottom: For example: boot: install vga=771 noapic nolapic No matter if a try the comand in the example or my own boot: install nomodeset... I always get the same error: could not find kernel image: install Well, then I burn the same image on a DVD-R media, check nomodeset, in the boot menu options, and every thing works fine then. I known that this information maybe not enough to find the problem, so you van ask me for any other info or propose a test. I'm a programmer so it will be no trouble. Thankx. Gabriel C. Stabel. ** Changed in: systeminstaller (Ubuntu) Status: Invalid = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/205349 Title: install from usb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systeminstaller/+bug/205349/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 42178] Re: apt-get doesn't use the same pinning as synaptic
Still broken in Ubuntu 10.10 (Maverick). The partial Jonathon`s workaround (above) still working: $ sudo rm /var/lib/synaptic/preferences $ sudo ln -s /etc/apt/preferences /var/lib/synaptic/preferences I got an unexpect server error this morning (openerp server freezes, and about ten people stop working) because my colegue administrator updates de server using apt-upgrade after I locked packages in Synaptic... For me this is a bug, not a feature. Everbody treat Synaptic as GUI for apt. -- apt-get doesn't use the same pinning as synaptic https://bugs.launchpad.net/bugs/42178 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550807] Re: Update installation path for libjdic.so and libtray.so
You can set LD_LIBRARY_PATH environment variable to fix it. Worked fine fo me. $ export LD_LIBRARY_PATH=/usr/lib/jni Thanks to Stéphane ideia from: https://lists.ubuntu.com/archives /universe-bugs/2009-February/047833.html. -- Update installation path for libjdic.so and libtray.so https://bugs.launchpad.net/bugs/550807 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 451337] Re: CPU cooling fan does not start at all
Updating the BIOS fixed my problem, I know is scary but it is really not that hard. -- CPU cooling fan does not start at all https://bugs.launchpad.net/bugs/451337 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 451337] Re: CPU cooling fan does not start at all
I can confirm that by updating the BIOS, this issue is fixed. -- CPU cooling fan does not start at all https://bugs.launchpad.net/bugs/451337 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 451337] Re: CPU cooling fan does not start at all
Can anyone confirm if this issue is fixed in 2.6.31-16-generic? -- CPU cooling fan does not start at all https://bugs.launchpad.net/bugs/451337 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 451337] Re: CPU cooling fan does not start at all
I can confirm 2.6.31-15-generic didn't fix the issue. How can I revert back to 14-apw? -- CPU cooling fan does not start at all https://bugs.launchpad.net/bugs/451337 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 479162] [NEW] [ASUSTeK Computer INC. 1000] late resume failure
Public bug reported: It was during the second resume that I got this problem. The first resume worked fine. ProblemType: KernelOops Annotation: This occured during a previous suspend and prevented it from resuming properly. The resume processing hung very near the end and will have appeared to have completed normally. AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gabriel1578 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf7eb8000 irq 16' Mixer name : 'Realtek ALC269' Components : 'HDA:10ec0269,1043834a,0014' Controls : 12 Simple ctrls : 7 Date: Mon Nov 9 08:31:00 2009 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/share/apport/apportcheckresume Failure: late resume HibernationDevice: RESUME=UUID=f3a13bf6-f402-4851-ab58-cea340314cb9 InterpreterPath: /usr/bin/python2.6 MachineType: ASUSTeK Computer INC. 1000 Package: linux-image-2.6.31-14-generic 2.6.31-14.48 ProcCmdLine: root=UUID=72404e88-be10-4572-b32d-cfa342c30339 ro quiet splash ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume ProcEnviron: PATH=(custom, no user) ProcVersionSignature: Ubuntu 2.6.31-14.48-generic RelatedPackageVersions: linux-backports-modules-2.6.31-14-generic N/A linux-firmware 1.24 SourcePackage: linux Tags: resume suspend resume-late-hang ubuntu-unr Title: [ASUSTeK Computer INC. 1000] late resume failure Uname: Linux 2.6.31-14-generic i686 UserGroups: WpaSupplicantLog: dmi.bios.date: 08/01/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0803 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1000 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTek Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0803:bd08/01/2008:svnASUSTeKComputerINC.:pn1000:pvrx.x:rvnASUSTeKComputerINC.:rn1000:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x: dmi.product.name: 1000 dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-kerneloops i386 resume resume-late-hang suspend ubuntu-unr -- [ASUSTeK Computer INC. 1000] late resume failure https://bugs.launchpad.net/bugs/479162 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 479162] Re: [ASUSTeK Computer INC. 1000] late resume failure
** Attachment added: AlsaDevices.txt http://launchpadlibrarian.net/35419782/AlsaDevices.txt ** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/35419784/BootDmesg.txt ** Attachment added: Card0.Amixer.values.txt http://launchpadlibrarian.net/35419785/Card0.Amixer.values.txt ** Attachment added: Card0.Codecs.codec.0.txt http://launchpadlibrarian.net/35419786/Card0.Codecs.codec.0.txt ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/35419787/CurrentDmesg.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/35419788/Dependencies.txt ** Attachment added: IwConfig.txt http://launchpadlibrarian.net/35419791/IwConfig.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/35419795/Lspci.txt ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/35419796/Lsusb.txt ** Attachment added: PciMultimedia.txt http://launchpadlibrarian.net/35419797/PciMultimedia.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/35419798/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/35419799/ProcInterrupts.txt ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/35419800/ProcMaps.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/35419801/ProcModules.txt ** Attachment added: ProcStatus.txt http://launchpadlibrarian.net/35419802/ProcStatus.txt ** Attachment added: ResumeHangLog.txt http://launchpadlibrarian.net/35419803/ResumeHangLog.txt ** Attachment added: RfKill.txt http://launchpadlibrarian.net/35419804/RfKill.txt ** Attachment added: SleepLog.txt http://launchpadlibrarian.net/35419806/SleepLog.txt ** Attachment added: UdevDb.txt http://launchpadlibrarian.net/35419807/UdevDb.txt ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/35419808/UdevLog.txt ** Attachment added: WifiSyslog.txt http://launchpadlibrarian.net/35419809/WifiSyslog.txt -- [ASUSTeK Computer INC. 1000] late resume failure https://bugs.launchpad.net/bugs/479162 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 60606] Re: New Server demands password
This error Error connecting to the server: fe_sendauth: no password supplied is caused by a file permission error in .pgpass. It should be 0600. Fix it like this: $chmod 0600 /home/username/.pgpass -- New Server demands password https://bugs.launchpad.net/bugs/60606 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 349314] Re: Slow performance and tiling issues on i915
I can confirm too that using Setting Tiling to False in xorg.conf didn't work in my EeePC 900 -- Slow performance and tiling issues on i915 https://bugs.launchpad.net/bugs/349314 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
