[Dx-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
As far as I can tell it is fixed in 14.10, been running it for some time and the bug wasn't triggered happen. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Bug description: *** IMPORTANT ** *** The fix is not included in TRUSTY. Will be included with next SRU. *** If you can reproduce this bug please be sure to provide the following info: 1. Do you use a multi-head setup? If yes, using just one monitor fixes the issue? 2. Can you reproduce all the time? 3. Do you use ldap? If yes, using gnome-screensaver fix the issue (see comment #115) can you still reproduce that? 4. Please consider posting /var/log/auth.log (at least part of it, should not contain sensitive information) 5. Please specify the unity version *** END IMPORTANT ** Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
Same here, same hardware as henryweismann in comment #19 (System76 Gazelle pro), with external monitor (i.e. dual monitor setup). Switching to VT1 and running unity fixes it but then the windows are on different desktops, some settings are reset (e.g. ctrl-alt-0 does not minimize windows anymore, top menu line is empty, no indicators etc.). Also tried compiz --replace and unity --replace, neither fixes the keyboard shortcuts and empty menu/panel at the top of the screen (where notifications are). -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Triaged Status in “unity” package in Ubuntu: Confirmed Bug description: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1242339] Re: window-stack-bridge crashed with SIGSEGV in data()
doesn't seem like the fix helped, I have hud (13.10.1+13.10.20131014-0ubuntu1) installed but I just saw the crash (segfault). erik@jojda:~$ COLUMNS=250 dpkg -l hud Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++--=-=-== ii hud 13.10.1+13.10.20131014-0ubuntu1 amd64 Backend for the Unity HUD -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1242339 Title: window-stack-bridge crashed with SIGSEGV in data() Status in Unity HUD: Fix Committed Status in “hud” package in Ubuntu: Confirmed Status in “hud” source package in Saucy: Fix Released Bug description: [Impact] High impoact on our users, this is one of the highest reported issues on errors.ubuntu.com: https://errors.ubuntu.com/problem/80ec348bd203ad9f5b91a956c463234dce72d2e7 [Test case] Use Unity, switch between applications and try to access menus via the HUD. [Rgression potential] This changes behavior in the window properties retrieval. Regression potential is low since this would simply return an empty set (rather than crashing) should the window not be identifyable. --- Just working in eclipse ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: hud 13.10.1+13.10.20131014-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2 Architecture: i386 Date: Sun Oct 20 20:11:13 2013 ExecutablePath: /usr/lib/i386-linux-gnu/hud/window-stack-bridge InstallationDate: Installed on 2012-05-14 (523 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012) MarkForUpload: True ProcCmdline: /usr/lib/i386-linux-gnu/hud/window-stack-bridge ProcEnviron: PATH=(custom, no user) LANGUAGE=ru XDG_RUNTIME_DIR=set LANG=ru_RU.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0xb73110d7 _ZN22QDBusAbstractInterface25asyncCallWithArgumentListERK7QStringRK5QListI8QVariantE+23: mov0x4(%edi),%esi PC (0xb73110d7) ok source 0x4(%edi) (0x0004) not located in a known VMA region (needed readable region)! destination %esi ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: hud StacktraceTop: QDBusAbstractInterface::asyncCallWithArgumentList(QString const, QListQVariant const) () from /usr/lib/i386-linux-gnu/libQt5DBus.so.5 BamfWindow::xProp(QString const) () BamfWindowStack::GetWindowProperties(unsigned int, QString const, QStringList const) () WindowStackAdaptor::GetWindowProperties(unsigned int, QString const, QStringList const) () ?? () Title: window-stack-bridge crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() UpgradeStatus: Upgraded to saucy on 2013-10-19 (1 days ago) UserGroups: adm lpadmin nopasswdlogin sambashare sudo upstart.window-stack-bridge.log: QDBusConnection: name 'org.ayatana.bamf' had owner '' but we thought it was ':1.14' Error getting parents for /org/ayatana/bamf/window/75613984 QDBusError(org.freedesktop.DBus.Error.UnknownMethod, Интерфейс «org.ayatana.bamf.view» для пути /org/ayatana/bamf/window/75613984 объекта не найден) Error getting parents for /org/ayatana/bamf/window/75614083 QDBusError(org.freedesktop.DBus.Error.UnknownMethod, Интерфейс «org.ayatana.bamf.view» для пути /org/ayatana/bamf/window/75614083 объекта не найден) To manage notifications about this bug go to: https://bugs.launchpad.net/hud/+bug/1242339/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1238338] Re: window-stack-bridge crashed with SIGSEGV in BamfWindow::windowId()
doesn't seem like the fix helped, I have hud (13.10.1+13.10.20131014-0ubuntu1) installed but I just saw the crash (segfault). erik@jojda:~$ COLUMNS=250 dpkg -l hud Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++--=-=-== ii hud 13.10.1+13.10.20131014-0ubuntu1 amd64 Backend for the Unity HUD -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1238338 Title: window-stack-bridge crashed with SIGSEGV in BamfWindow::windowId() Status in “hud” package in Ubuntu: Fix Released Bug description: apt-cache policy hud hud: Installed: 13.10.1+13.10.20131010.1-0ubuntu1 Candidate: 13.10.1+13.10.20131010.1-0ubuntu1 Version table: *** 13.10.1+13.10.20131010.1-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: hud 13.10.1+13.10.20131010.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Fri Oct 11 08:29:01 2013 ExecutablePath: /usr/lib/x86_64-linux-gnu/hud/window-stack-bridge InstallationDate: Installed on 2012-09-30 (375 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120817.1) MarkForUpload: True ProcCmdline: /usr/lib/x86_64-linux-gnu/hud/window-stack-bridge SegvAnalysis: Segfault happened at: 0x409b70 _ZN10BamfWindow8windowIdEv: mov 0x24(%rdi),%eax PC (0x00409b70) ok source 0x24(%rdi) (0x0024) not located in a known VMA region (needed readable region)! destination %eax ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: hud StacktraceTop: BamfWindow::windowId() () BamfWindowStack::removeWindow(QString const) () BamfWindowStack::ViewClosed(QString const, QString const) () ?? () QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 Title: window-stack-bridge crashed with SIGSEGV in BamfWindow::windowId() UpgradeStatus: Upgraded to saucy on 2013-05-06 (157 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo upstart.window-stack-bridge.log: Error getting parents for /org/ayatana/bamf/window/65011880 QDBusError(org.freedesktop.DBus.Error.UnknownMethod, Интерфейс «org.ayatana.bamf.view» для пути /org/ayatana/bamf/window/65011880 объекта не найден) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1238338/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
