[Dx-packages] [Bug 1499354] Re: Invalid password after long uptime
Well unity is just using PAM to check if the password is correct. You can try to reproduce the problem with gnome-screensaver. If it happens with g-s as well then it's not unity's fault. -- 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/1499354 Title: Invalid password after long uptime Status in Unity: Incomplete Status in unity package in Ubuntu: Incomplete Status in unity-greeter package in Ubuntu: Invalid Bug description: After a 15.04 system has been running for a long time (more than 2-3 days), and the system has locked the screen automatically during inactivity, attempting to unlock the screen will result in an "invalid password" message at the lock screen, despite using the correct password. The only fix I've found is to jump to a TTY, log in there (which works), and do a "sudo service lightdm restart". I've made no changes to my PAM configuration, nor do I have any packages installed which modify it. Only other thing I've noticed is that normally, my screens go to sleep after the display is locked. Every time this problem presents itself, the displays have awoken at some point overnight. No obvious errors in auth.log, xorg.log, or lightdm.log. Using the proprietary NVIDIA drivers. Unity Installed: 7.3.2+15.04.20150420-0ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1499354/+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 390508] Re: notifyOSD ignores the expire timeout parameter
I agree with quequotion, you can't assume that the number of people
annoyed by these issues are limited to the number of people complaining
about it in a bug report.
Case in point, I ditched Ubuntu entirely on my desktop because systemd
rendered it unbootable. I'm not going to file a bug report, I'm just
going to leave, because systemd is a (poor) design decision they're
apparently going to stick with no matter what... just like this notify-
OSD timeout nonsense.
Also: happy 6th birthday, notifyOSD bug! It's comforting to know that
some things will never change.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to notify-osd in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/390508
Title:
notifyOSD ignores the expire timeout parameter
Status in One Hundred Papercuts:
Invalid
Status in Message Web:
New
Status in notify-osd package in Ubuntu:
Won't Fix
Status in notify-osd package in Arch Linux:
New
Bug description:
Binary package hint: libnotify-bin
adyroman@panther:~/libnotify-0.4.5/tools$ lsb_release -rd
Description: Ubuntu 9.04
Release: 9.04
adyroman@panther:~/libnotify-0.4.5/tools$
adyroman@panther:~/libnotify-0.4.5/tools$ apt-cache policy libnotify-bin
libnotify-bin:
Installed: 0.4.5-0ubuntu1
Candidate: 0.4.5-0ubuntu1
Version table:
*** 0.4.5-0ubuntu1 0
500 http://ro.archive.ubuntu.com jaunty/universe Packages
100 /var/lib/dpkg/status
adyroman@panther:~/libnotify-0.4.5/tools$
adyroman@panther:~/libnotify-0.4.5/tools$ cat notify-send.c | grep
expire_timeout
static glong expire_timeout = NOTIFY_EXPIRES_DEFAULT;
{ "expire-time", 't', 0,G_OPTION_ARG_INT, &expire_timeout,
notify_notification_set_timeout(notify, expire_timeout);
adyroman@panther:~/libnotify-0.4.5/tools$
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/390508/+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 1314869] Re: Gmail Webapp Locks System (Firefox 29)
Nicholas Smith, thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal: apport-collect -p xorg 1314869 Please ensure you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information. ** This bug is no longer a duplicate of bug 1309044 Unity webapps crash Ubuntu 14.04 LTS on my computer ** Package changed: libunity-webapps (Ubuntu) => xorg (Ubuntu) ** Changed in: xorg (Ubuntu) Importance: Undecided => Low ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity-webapps in Ubuntu. https://bugs.launchpad.net/bugs/1314869 Title: Gmail Webapp Locks System (Firefox 29) Status in xorg package in Ubuntu: Incomplete Bug description: Fresh install of Ubuntu 14.04 64-bit Mac specific on a MacBook Pro 6,1. Accessed Gmail, logged-in. Let it create a webapp launcher. Closed browser, pulled updates with "sudo apt-get update; sudo apt-get upgrade". Launched Firefox, now shows version 29. Run the Gmail launcher. A blank window appears (has a back/forward button at the bottom). Sometimes partially loads Gmail in the window. System locks up, keyboard doesn't respond. Requires hard power cycle to reboot. version info: $ lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 $ apt-cache policy firefox firefox: Installed: 29.0+build1-0ubuntu0.14.04.2 Candidate: 29.0+build1-0ubuntu0.14.04.2 Version table: *** 29.0+build1-0ubuntu0.14.04.2 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 100 /var/lib/dpkg/status 28.0+build2-0ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages $ apt-cache policy unity-webapps-service unity-webapps-service: Installed: 2.5.0~+14.04.20140409-0ubuntu1 Candidate: 2.5.0~+14.04.20140409-0ubuntu1 Version table: *** 2.5.0~+14.04.20140409-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-webapps-service 2.5.0~+14.04.20140409-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 30 20:12:52 2014 InstallationDate: Installed on 2014-04-30 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64+mac (20140417) SourcePackage: libunity-webapps UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1314869/+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 390508] Re: notifyOSD ignores the expire timeout parameter
>People who look for, find, and comment in bug reports are
disproportionately those who notice and are annoyed by software's
current behavior. People who don't notice, don't care about, or agree
with, current behavior don't go looking for bug reports about it.
I strongly disagree.
You aren't taking into account people who notice and are annoyed, but
don't know anything about bug reports--or even what to call "the
annoying bubble thingies that won't ever go away".
Before discovering launchpad, or the forums, or making an account,
they'll get frustrated, give up and think this, Ubuntu, and/or Linux are
[insert expletive here]--and use something else.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to notify-osd in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/390508
Title:
notifyOSD ignores the expire timeout parameter
Status in One Hundred Papercuts:
Invalid
Status in Message Web:
New
Status in notify-osd package in Ubuntu:
Won't Fix
Status in notify-osd package in Arch Linux:
New
Bug description:
Binary package hint: libnotify-bin
adyroman@panther:~/libnotify-0.4.5/tools$ lsb_release -rd
Description: Ubuntu 9.04
Release: 9.04
adyroman@panther:~/libnotify-0.4.5/tools$
adyroman@panther:~/libnotify-0.4.5/tools$ apt-cache policy libnotify-bin
libnotify-bin:
Installed: 0.4.5-0ubuntu1
Candidate: 0.4.5-0ubuntu1
Version table:
*** 0.4.5-0ubuntu1 0
500 http://ro.archive.ubuntu.com jaunty/universe Packages
100 /var/lib/dpkg/status
adyroman@panther:~/libnotify-0.4.5/tools$
adyroman@panther:~/libnotify-0.4.5/tools$ cat notify-send.c | grep
expire_timeout
static glong expire_timeout = NOTIFY_EXPIRES_DEFAULT;
{ "expire-time", 't', 0,G_OPTION_ARG_INT, &expire_timeout,
notify_notification_set_timeout(notify, expire_timeout);
adyroman@panther:~/libnotify-0.4.5/tools$
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/390508/+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 1226962] Re: Hotkeys not functional in non-latin keyboard layout
Bug exists in Ubuntu 15.10 beta2 - unable to start gnome-terminal in GNOME sessions on non-latin layout. -- 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/1226962 Title: Hotkeys not functional in non-latin keyboard layout Status in aptana-studio-installer: New Status in Default settings and artwork for Baltix OS: New Status in LibreOffice Productivity Suite: Fix Released Status in ibus: New Status in Indicator keyboard: Fix Released Status in Inkscape: New Status in monodevelop: New Status in mutter: Fix Released Status in okular: New Status in OpenOffice: New Status in sigram: New Status in Unity: Fix Released Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-terminal package in Ubuntu: Triaged Status in openjdk-7 package in Ubuntu: Incomplete Status in unity package in Ubuntu: Triaged Status in unity-settings-daemon package in Ubuntu: Triaged Status in gnome-shell package in Fedora: Unknown Status in openoffice package in Fedora: Unknown Bug description: New keyboard layout changer in Ubuntu 13.10 introduce old-new bug. Any system or application hotkey witch use char (for example: ctrl+alt+t for terminal or ctrl+t for new tab in browser) become unfunctional when selected non-latin keyboard layout. Hotkeys with F1-12, numbers and other non-character buttons works perfectly. Window manager hotkeys not affected by this bug. All hotkeys in system parameters->keyboard->hotkeys->windows works perfect with any keyboard layout. Workaround for some system hotkeys and two layouts (english and non- latin): rebind all hotkeys in your local layout. For example instead of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with english layout. If you use english and two different non-latin layouts this workaround helps only with one of them. Dear Ubuntu users and developers! Please include the following information to your comment about non-latin shortcuts problems: 1. What Ubuntu version do you have (Ubuntu 13.10, Ubuntu 13.10 GNOME, Ubuntu 14.04, Ubuntu 14.04 GNOME and so on), upgraded (describe version) or clean installed 2. What keyboard layout do you have 3. What shortcut for keyboard layout switching do you use 4. On which session you have problems - that is one from Unity, GNOME Shell, GNOME FlashBack/Fallback (Metacity), GNOME FlashBack/Fallback (Compiz) 5. With which program and its version and origin (Ubuntu repositories, PPA, non-deb binary package from some website) you have problems. By providing this information you can make bug-fixing much simpler and may be faster. -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- To manage notifications about this bug go to: https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+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 1245473] Re: Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes shortcuts with ctrl+shift, etc not working in any program
Bug exists in Ubuntu 15.10 beta2, Ctrl+Shift as layout switch (English and Russian). I unable to use for text selection and in Firefox, in the following sessions: * GNOME Flashback (Metacity) * GNOME Flashback (Compiz) All these shortcuts work as expected in Unity. -- 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/1245473 Title: Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes shortcuts with ctrl+shift, etc not working in any program Status in gnome-shell: Won't Fix Status in Unity: Confirmed Status in gnome-settings-daemon package in Ubuntu: Triaged Status in unity package in Ubuntu: Triaged Status in gnome-settings-daemon package in ALT Linux: Unknown Status in gnome-settings-daemon package in Debian: New Status in gnome-settings-daemon package in Fedora: Unknown Status in gnome-settings-daemon package in openSUSE: Confirmed Bug description: Tried only with ctrl+shift, maybe behaves the same for other modifier key combinations when used as shortcut for switching layouts. - Set ctrl+shift as shortcut for switching keyboard layouts - Try to use ctrl+shift+v, ctrl+shift+c in Terminal -- it doesn't work (actually Terminal window loses focus when ctrl+shift is pressed, and layout is switched) -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-settings-daemon 3.8.5-0ubuntu11.1 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Mon Oct 28 16:40:02 2013 InstallationDate: Installed on 2013-10-23 (5 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1245473/+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 1263228] Re: icons in indicators are small (difficult to view on FullHD display and smaller than was on 12.04)
Bug exists in Ubuntu 15.10 beta2. ** Tags added: wily -- You received this bug notification because you are a member of DX Packages, which is subscribed to ido in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1263228 Title: icons in indicators are small (difficult to view on FullHD display and smaller than was on 12.04) Status in ido package in Ubuntu: Triaged Status in indicator-power package in Ubuntu: Fix Released Bug description: I have Ubuntu 14.04 with all updates installed. My screen resolution is 1920x1080 (FullHD) at 16.4 inches. Icons from the menu of newest indicator-keyboard and other gnome-panel icons are very small (difficult to read). Please adapt icon sizes to large screen resolutions. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-keyboard 0.0.0+14.04.20131125-0ubuntu1 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.7-0ubuntu3 Architecture: i386 CurrentDesktop: Unity Date: Sat Dec 21 00:41:25 2013 InstallationDate: Installed on 2013-10-20 (61 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1) SourcePackage: indicator-keyboard UpgradeStatus: Upgraded to trusty on 2013-11-19 (31 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ido/+bug/1263228/+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 1446081] Re: Incorrect scaling of launcher icons
This error wasnot still fixed. Hoping it will be fixed October 22, 2015. Files, Network, Software Updater, Google Chrome, Trash, ** Attachment added: "Screenshot from 2015-09-27 03-39-31.png" https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1446081/+attachment/4475743/+files/Screenshot%20from%202015-09-27%2003-39-31.png -- 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/1446081 Title: Incorrect scaling of launcher icons Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Launcher icons shown w/o issues only on this sizes of launcher: 16, 24, 32, 48, 64. Screenshot attached. Look at Sublime, Chrome and Skype icons. There was no such issue before vivid. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150410.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3 Uname: Linux 3.19.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Apr 20 00:26:44 2015 JournalErrors: Error: command ['journalctl', '-b', '--priority', 'warning'] failed with exit code 1: No journal files were found. SourcePackage: unity UpgradeStatus: Upgraded to vivid on 2015-03-27 (23 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1446081/+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 1499747] Re: gedit crashed with SIGABRT in g_assertion_message()
Oh and you can reproduce it by turning the External Tools plugin on -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-gtk-module in Ubuntu. https://bugs.launchpad.net/bugs/1499747 Title: gedit crashed with SIGABRT in g_assertion_message() Status in gedit package in Ubuntu: Invalid Status in glib2.0 package in Ubuntu: Invalid Status in unity-gtk-module package in Ubuntu: Triaged Bug description: Gedit crashed just after opening a (small) text file from nautilus with "Open with". ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: gedit 3.10.4-0ubuntu13 ProcVersionSignature: Ubuntu 4.2.0-11.13-lowlatency 4.2.1 Uname: Linux 4.2.0-11-lowlatency x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Fri Sep 25 16:05:28 2015 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2014-12-13 (285 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) ProcCmdline: gedit /home/username/Bureau/Export_cabmnt_329340483152739798.csv Signal: 6 SourcePackage: gedit StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 Title: gedit crashed with SIGABRT in g_assertion_message() UpgradeStatus: Upgraded to wily on 2015-09-21 (4 days ago) UserGroups: adm audio cdrom dialout dip libvirtd lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1499747/+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 1499747] Re: gedit crashed with SIGABRT in g_assertion_message()
It's *probably* a bug in unity-gtk-module - Will has been looking into this. ** Also affects: unity-gtk-module (Ubuntu) Importance: Undecided Status: New ** Changed in: unity-gtk-module (Ubuntu) Status: New => Triaged ** Changed in: unity-gtk-module (Ubuntu) Importance: Undecided => High ** Changed in: glib2.0 (Ubuntu) Status: Confirmed => Invalid ** Changed in: gedit (Ubuntu) Status: Confirmed => Invalid ** Changed in: unity-gtk-module (Ubuntu) Assignee: (unassigned) => William Hua (attente) -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-gtk-module in Ubuntu. https://bugs.launchpad.net/bugs/1499747 Title: gedit crashed with SIGABRT in g_assertion_message() Status in gedit package in Ubuntu: Invalid Status in glib2.0 package in Ubuntu: Invalid Status in unity-gtk-module package in Ubuntu: Triaged Bug description: Gedit crashed just after opening a (small) text file from nautilus with "Open with". ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: gedit 3.10.4-0ubuntu13 ProcVersionSignature: Ubuntu 4.2.0-11.13-lowlatency 4.2.1 Uname: Linux 4.2.0-11-lowlatency x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Fri Sep 25 16:05:28 2015 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2014-12-13 (285 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) ProcCmdline: gedit /home/username/Bureau/Export_cabmnt_329340483152739798.csv Signal: 6 SourcePackage: gedit StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 Title: gedit crashed with SIGABRT in g_assertion_message() UpgradeStatus: Upgraded to wily on 2015-09-21 (4 days ago) UserGroups: adm audio cdrom dialout dip libvirtd lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1499747/+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 1354741] Re: In Hotcorners, “Toggle Desktop” works only for showing windows
** Also affects: unity (Ubuntu) Importance: Undecided Status: New ** Changed in: unity (Ubuntu) Status: New => Confirmed -- 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/1354741 Title: In Hotcorners, “Toggle Desktop” works only for showing windows Status in unity package in Ubuntu: Confirmed Status in unity-tweak-tool package in Ubuntu: Triaged Bug description: The “Toggle Desktop” option, which can be activated in the “Hotcorners” category, does only work for showing windows, not for hiding them. Steps to reproduce: q) Enable the “Toggle desktop” function for any corner under “Hotcorners” w) Move your mouse to that corner e) The window(s) should disappear r) Repeat, the window(s) should reappear t) Repeat again y) The window(s) don't reappear! u) Show desktop using Ctrl+Super+d i) Move the cursor to the corner again. o) The window(s) reappear. p) Repeat t-o ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-tweak-tool 0.0.6ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: Unity Date: Sat Aug 9 22:05:43 2014 InstallationDate: Installed on 2014-04-10 (121 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140410) PackageArchitecture: all SourcePackage: unity-tweak-tool UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1354741/+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 1439599] Re: Search button not clickable on revealed unity launcher
Thank you for taking the time to report this bug. We have tried to recreate this on the latest release of Ubuntu and cannot reproduce it. This bug is being marked as Invalid. If you believe the problem to still exist in the latest version of Ubuntu please comment on why that is the case and change the bug status to NEW. ** Changed in: unity (Ubuntu) Status: New => Invalid -- 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/1439599 Title: Search button not clickable on revealed unity launcher Status in Unity: New Status in unity package in Ubuntu: Invalid Bug description: I have auto-hide of launcher enabled and I am opening it with Alt+F1. When the launcher appears, the search button (the top-most button) is selected (has focus) and accessible when I press Enter - the search screen appears. But the button is not accessible by mouse - the mouse click is not handled immediatelly and the search screen does not appear. I need to click somewhere else or press Esc key - it behaves like the click is remembered, but processed later. Expected is that the search screen appears immediately when I click the search (the top-most) button of the launcher. I am using Ubuntu 14.04.2 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1439599/+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 1498199] Re: Switching to fullscreen app causes unity freeze
Thank you for taking the time to report this bug. We have tried to recreate this on the latest release of Ubuntu 15.10 and cannot reproduce it. This bug is being marked as Invalid. If you believe the problem to still exist in the latest version of Ubuntu please comment on why that is the case and change the bug status to NEW. ** Changed in: unity (Ubuntu) Status: New => Invalid -- 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/1498199 Title: Switching to fullscreen app causes unity freeze Status in unity package in Ubuntu: Invalid Bug description: I'm reporting this for unity but it might just as well be compiz- related. Reproduce 1. Open fullscreen app (e.g. fullscreen HTML5 video, a game) 2. switch to another virtual desktop (i.e. using crtl+alt+arrow_keys) 3. switch back This started happening to me in 15.04. It does not happen all the time but can be reproduced by trying several times. If you need more info, let me know what and how to get it. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150420-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Sep 21 23:18:19 2015 InstallationDate: Installed on 2014-03-11 (559 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64+mac (20140302) SourcePackage: unity UpgradeStatus: Upgraded to vivid on 2015-05-20 (124 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1498199/+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 1500066] Re: package zeitgeist-datahub 0.9.14-0ubuntu4.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configura
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of DX Packages, which is subscribed to zeitgeist in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1500066 Title: package zeitgeist-datahub 0.9.14-0ubuntu4.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in zeitgeist package in Ubuntu: New Bug description: I don't know. While updating there was a note, that there is a problem and I was asked report the problem. So I did.But I don't know anything about it. Sorry ProblemType: Package DistroRelease: Ubuntu 14.04 Package: zeitgeist-datahub 0.9.14-0ubuntu4.1 ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 Uname: Linux 3.13.0-63-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 Date: Sat Sep 26 12:29:08 2015 DuplicateSignature: package:zeitgeist-datahub:0.9.14-0ubuntu4.1:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2011-10-12 (1445 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) RelatedPackageVersions: dpkg 1.17.5ubuntu5.4 apt 1.0.1ubuntu2.10 SourcePackage: zeitgeist Title: package zeitgeist-datahub 0.9.14-0ubuntu4.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to trusty on 2014-09-10 (381 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/1500066/+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 1500066] [NEW] package zeitgeist-datahub 0.9.14-0ubuntu4.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configu
Public bug reported: I don't know. While updating there was a note, that there is a problem and I was asked report the problem. So I did.But I don't know anything about it. Sorry ProblemType: Package DistroRelease: Ubuntu 14.04 Package: zeitgeist-datahub 0.9.14-0ubuntu4.1 ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 Uname: Linux 3.13.0-63-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 Date: Sat Sep 26 12:29:08 2015 DuplicateSignature: package:zeitgeist-datahub:0.9.14-0ubuntu4.1:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2011-10-12 (1445 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) RelatedPackageVersions: dpkg 1.17.5ubuntu5.4 apt 1.0.1ubuntu2.10 SourcePackage: zeitgeist Title: package zeitgeist-datahub 0.9.14-0ubuntu4.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to trusty on 2014-09-10 (381 days ago) ** Affects: zeitgeist (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- You received this bug notification because you are a member of DX Packages, which is subscribed to zeitgeist in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1500066 Title: package zeitgeist-datahub 0.9.14-0ubuntu4.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in zeitgeist package in Ubuntu: New Bug description: I don't know. While updating there was a note, that there is a problem and I was asked report the problem. So I did.But I don't know anything about it. Sorry ProblemType: Package DistroRelease: Ubuntu 14.04 Package: zeitgeist-datahub 0.9.14-0ubuntu4.1 ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 Uname: Linux 3.13.0-63-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 Date: Sat Sep 26 12:29:08 2015 DuplicateSignature: package:zeitgeist-datahub:0.9.14-0ubuntu4.1:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2011-10-12 (1445 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) RelatedPackageVersions: dpkg 1.17.5ubuntu5.4 apt 1.0.1ubuntu2.10 SourcePackage: zeitgeist Title: package zeitgeist-datahub 0.9.14-0ubuntu4.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to trusty on 2014-09-10 (381 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/1500066/+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 49579] Re: screen doesn't lock when some menu is open
As part of the big bug review for 16.04 LTS I have tested this on 15.10 and the bug is still there. -- 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/49579 Title: screen doesn't lock when some menu is open Status in GNOME Screensaver: Expired Status in OEM Priority Project: Won't Fix Status in OEM Priority Project precise series: Won't Fix Status in Unity: Triaged Status in Unity 7.2 series: Triaged Status in X.Org X server: Confirmed Status in gnome-screensaver package in Ubuntu: Triaged Status in unity package in Ubuntu: Confirmed Status in gnome-screensaver source package in Precise: Confirmed Status in unity source package in Precise: Confirmed Status in xorg-server package in Debian: Confirmed Bug description: Binary package hint: gnome-screensaver I'm running a fresh install of Dapper with screensaver set to 'blank screen', and 'lock screen when screensaver is active' enabled. If a panel menu (e.g. Applications) is open and the machine is left idle, the screen fails to lock. It fades out after the time period as expected, but the desktop reappears after a few seconds. Ben (comments / criticism welcome, this is my first bug report) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+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 1500050] Re: No way to stop an alarm that has been snoozed
** Also affects: ubuntu-ux Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1500050 Title: No way to stop an alarm that has been snoozed Status in Ubuntu UX: New Status in indicator-datetime package in Ubuntu: New Bug description: Once a user snoozes an alarm, there is no way to stop the alarm without having to wait for the snooze period to be over. The indicator datetime should provide options to completely stop the alarm like Android does. This pattern can already been seen in the messaging indicator where users can reply to messages. Another example is a missed call where users can either call back or message them via the action buttons show in the indicator. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1500050/+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 1500050] [NEW] No way to stop an alarm that has been snoozed
Public bug reported: Once a user snoozes an alarm, there is no way to stop the alarm without having to wait for the snooze period to be over. The indicator datetime should provide options to completely stop the alarm like Android does. This pattern can already been seen in the messaging indicator where users can reply to messages. Another example is a missed call where users can either call back or message them via the action buttons show in the indicator. ** Affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1500050 Title: No way to stop an alarm that has been snoozed Status in indicator-datetime package in Ubuntu: New Bug description: Once a user snoozes an alarm, there is no way to stop the alarm without having to wait for the snooze period to be over. The indicator datetime should provide options to completely stop the alarm like Android does. This pattern can already been seen in the messaging indicator where users can reply to messages. Another example is a missed call where users can either call back or message them via the action buttons show in the indicator. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1500050/+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 1029371] Re: drag&drop of files randomly silently fails
I have also noticed that this does not only happen when dragging and dropping among and within Nautilus windows and/or the Desktop, but also when dragging a file to an application capable of handling it, such as dropping a file into Filezilla (on the server-side panel, i.e. the right one) for upload. In that case, also, at random times the operation is silently ignored. I would say it does appear to be more likely to happen when the drag-n-drop is done quickly, but it's difficult to say, because most of the times I do it quickly, unless I am re-doing it just after a failure. -- 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/1029371 Title: drag&drop of files randomly silently fails Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: I'm not sure whether this is Nautilus or Unity at fault. This happens with both a Nautilus window and the Desktop: 1. In a Nautilus window: click on a file icon, drag it and drop it over a folder. Or hold the Ctrl key and click and drag and drop the file immediately in almost the same place where it was. In the first case (dragging over a folder) the file should be moved; in the second case the file should be copied. In both cases, if you do it quickly enough, the action is completely ignored and nothing happens. It seems to be related to the fact that the Launcher (or whatever it is called) shows up on the left of the screen when you start dragging. If its show-up animation is not complete when you drop the item, the drag&drop operation is ignored. 2. On the desktop, the same happens. Or if you simply move an icon (in which case the expected behavior would be for the icon to snap to the nearest position in the grid and stay there) you can also observe that the action is ignored and the icon goes back to its original position. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.14.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21 Uname: Linux 3.2.0-27-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu11 Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,decor,vpswitch,mousepoll,compiztoolbox,snap,place,resize,session,regex,grid,wall,move,gnomecompat,imgpng,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Thu Jul 26 12:44:14 2012 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: Upgraded to precise on 2012-05-17 (69 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1029371/+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 1499354] Re: Invalid password after long uptime
Is there a way I can gather information as to what Unity thinks its doing when that invalid password prompt comes up? -- 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/1499354 Title: Invalid password after long uptime Status in Unity: Incomplete Status in unity package in Ubuntu: Incomplete Status in unity-greeter package in Ubuntu: Invalid Bug description: After a 15.04 system has been running for a long time (more than 2-3 days), and the system has locked the screen automatically during inactivity, attempting to unlock the screen will result in an "invalid password" message at the lock screen, despite using the correct password. The only fix I've found is to jump to a TTY, log in there (which works), and do a "sudo service lightdm restart". I've made no changes to my PAM configuration, nor do I have any packages installed which modify it. Only other thing I've noticed is that normally, my screens go to sleep after the display is locked. Every time this problem presents itself, the displays have awoken at some point overnight. No obvious errors in auth.log, xorg.log, or lightdm.log. Using the proprietary NVIDIA drivers. Unity Installed: 7.3.2+15.04.20150420-0ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1499354/+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 1499354] Re: Invalid password after long uptime
System layout is pc105/us, and this doesn't impact system behavior at any other time. Only the login screen, and only after days have passed. -- 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/1499354 Title: Invalid password after long uptime Status in Unity: Incomplete Status in unity package in Ubuntu: Incomplete Status in unity-greeter package in Ubuntu: Invalid Bug description: After a 15.04 system has been running for a long time (more than 2-3 days), and the system has locked the screen automatically during inactivity, attempting to unlock the screen will result in an "invalid password" message at the lock screen, despite using the correct password. The only fix I've found is to jump to a TTY, log in there (which works), and do a "sudo service lightdm restart". I've made no changes to my PAM configuration, nor do I have any packages installed which modify it. Only other thing I've noticed is that normally, my screens go to sleep after the display is locked. Every time this problem presents itself, the displays have awoken at some point overnight. No obvious errors in auth.log, xorg.log, or lightdm.log. Using the proprietary NVIDIA drivers. Unity Installed: 7.3.2+15.04.20150420-0ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1499354/+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 1499882] Re: Password hint - feature request
** Changed in: unity Status: New => Opinion ** Changed in: unity Importance: Undecided => Wishlist ** Also affects: unity (Ubuntu) Importance: Undecided Status: New ** Changed in: unity (Ubuntu) Status: New => Opinion ** Changed in: unity (Ubuntu) Importance: Undecided => Wishlist -- 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/1499882 Title: Password hint - feature request Status in Unity: Opinion Status in unity package in Ubuntu: Opinion Bug description: I think that it would be really good if like in Windows and Mac (I think) there was an optional feature for a 'password hint' which could be displayed if the user gets the password wrong a certain number of times. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1499882/+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 827380] Re: scroll bar disappears when switching tabs
Bug no longer present in Wily, since it ditches its unmaintained overlay scrollbar and goes with some stock (and maintained) Gtk+ solution. -- You received this bug notification because you are a member of DX Packages, which is subscribed to overlay-scrollbar in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/827380 Title: scroll bar disappears when switching tabs Status in overlay-scrollbar package in Ubuntu: Confirmed Bug description: 1. Open gnome-terminal. 2. Open a second tab. 3. Press enter until the bottom of the screen and the scroll bar appears. 4. Switch to the other tab, then switch back. The scrollbar is now invisible until you push enter again. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-terminal 3.0.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.0.0-7.9-generic 3.0.0 Uname: Linux 3.0.0-7-generic x86_64 Architecture: amd64 Date: Tue Aug 16 14:52:18 2011 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110803.1) ProcEnviron: LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: Upgraded to oneiric on 2011-08-15 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/overlay-scrollbar/+bug/827380/+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 1079755] Re: HUD may give focus back to wrong window
FTR, it seems that the issue is resolved in 14.04. -- 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/1079755 Title: HUD may give focus back to wrong window Status in Unity: Expired Status in unity package in Ubuntu: Expired Bug description: Here's how to reproduce the bug: 1. open two windows, say WIN1 and WIN2 2. ALT-TAB (or SUPER-TAB) from WIN1 and WIN2 3. press ALT twice: to bring up the HUD and to hide it back 4. the focus is now on WIN2, although it is still below WIN1 5. press ALT twice again: the focus is back to WIN1 If you try to repeat the ALT-ALT trick, the focus is not moved away anymore after that. If you change focus with mouse (via launcher or by clicking inside other window), everything is fine. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.16.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30 Uname: Linux 3.2.0-32-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.0.1-0ubuntu15 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Fri Nov 16 19:57:32 2012 MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1079755/+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 1011496] Re: compiz crashed with SIGSEGV in std::__detail::_List_node_base::_M_hook() from sigc::internal::signal_impl::insert() from sigc::internal::signal_impl::connect()
>If this does still occur, we can either reopen this bug report or open a new one. Hello. I recently encountered bug 1497426 on Ubuntu Wily, which was automatically marked as a duplicate of this one. It's not clear to me how it was triggered as it was apport reporting a crash. However, if it is indeed a duplicate it looks like this issue has resurfaced. How do you prefer we proceed with this, should I reopen bug 1497426 so that someone may take a look at it? -- 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/1011496 Title: compiz crashed with SIGSEGV in std::__detail::_List_node_base::_M_hook() from sigc::internal::signal_impl::insert() from sigc::internal::signal_impl::connect() Status in Unity: Fix Released Status in unity package in Ubuntu: Fix Released Bug description: At session start ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: unity 5.12-0ubuntu3 ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0 Uname: Linux 3.4.0-5-generic x86_64 ApportVersion: 2.1.1-0ubuntu2 Architecture: amd64 CrashCounter: 1 Date: Mon Jun 11 09:59:20 2012 ExecutablePath: /usr/bin/compiz InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcCmdline: compiz SegvAnalysis: Segfault happened at: 0x7f321b87e950 <_ZNSt8__detail15_List_node_base7_M_hookEPS0_>: mov0x8(%rsi),%rax PC (0x7f321b87e950) ok source "0x8(%rsi)" (0x0001807d) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: unity StacktraceTop: std::__detail::_List_node_base::_M_hook(std::__detail::_List_node_base*) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 sigc::internal::signal_impl::insert(std::_List_iterator, sigc::slot_base const&) () from /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 sigc::internal::signal_impl::connect(sigc::slot_base const&) () from /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 sigc::signal_base::connect(sigc::slot_base const&) () from /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 unity::UnityScreen::UnityScreen(CompScreen*) () from /usr/lib/compiz/libunityshell.so Title: compiz crashed with SIGSEGV in std::__detail::_List_node_base::_M_hook() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1011496/+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 1482181] Re: Media keys (ctrl-alt-t, brightness, play/pause) don't work randomly after logging
Problem figured out by Trevinho and didrocks on irc: unity only emits AcceleratorActivated() for the first id returned by GrabAccelerator() and doesn't watch the unique name of the grabbing process. Thus, when something other than unity-settings-daemon grabs the key before it, or u-s-d crashes, those keys it grabbed at the very beginning can never be regrabbed. After a couple of rounds of testing and some code review, I can't make unity-settings-daemon subscribe to the same accelerator twice and thus getting into that situation itself. Feel free to reassign it to u-s-d once unity is fixed but this problem still persists. ** Changed in: unity-settings-daemon (Ubuntu) Status: Triaged => Invalid -- 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/1482181 Title: Media keys (ctrl-alt-t, brightness, play/pause) don't work randomly after logging Status in Unity: Triaged Status in unity package in Ubuntu: Triaged Status in unity-settings-daemon package in Ubuntu: Invalid Bug description: I've installed 15.10 and I can't open a terminal using ctrl-alt-t or use any other media keys. All system shorcuts as well don't work. Note that this started at least in 14.10. Restarting Unity "fixes" it (or logging out/logging back), so it seems a race between Unity and settings daemon at startup. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1482181/+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
