[Dx-packages] [Bug 889145] Re: focus follows mouse breaks desktop interaction
*** This bug is a duplicate of bug 674138 *** https://bugs.launchpad.net/bugs/674138 In 14.04 - in many cases using Super+D focuses correctly on the desktop. -- 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/889145 Title: focus follows mouse breaks desktop interaction Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Environment: 11.10 x86_64, unity; focus follows mouse enabled with 'gconftool-2 --get /apps/metacity/general/focus_mode' The problem: When there is at least one window open, the desktop doesn't get focus. Key presses go to the window and not the desktop. To reproduce: 1) start with empty desktop 2) create an empty test folder (mouse 3new folder) 3) open nautilus window. Move so that it doesn't obscure the test folder 4) select test folder on desktop. Leave mouse outside nautilus window. 5) type delete to delete the folder. The keypress is delivered to the nautilus window. (If anything was selected in the nautilus window, it was deleted instead of the test folder.) Since Unity doesn't come with a configuration interface I'm unsure which user preferences are supported/intended by developers and which ones aren't. I'm assuming that Canonical intends users to be able to set prevalent preferences (such as focus follows mouse) since doing otherwise would create a profound user experience regression. Is that assumption correct? To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/889145/+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 1307021] Re: indicator-power-service crashed with SIGSEGV in g_type_check_instance()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-power (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1307021 Title: indicator-power-service crashed with SIGSEGV in g_type_check_instance() Status in indicator-power package in Ubuntu: Confirmed Bug description: patryk@Aspire-E1-772G:~$ lsb_release -rd; apt-cache policy indicator-power Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 indicator-power: Zainstalowana: 12.10.6+14.04.20140328-0ubuntu1 Kandydująca: 12.10.6+14.04.20140328-0ubuntu1 Tabela wersji: *** 12.10.6+14.04.20140328-0ubuntu1 0 500 http://at.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status patryk@Aspire-E1-772G:~$ shows problem on startup ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: indicator-power 12.10.6+14.04.20140328-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 Date: Sat Apr 12 23:06:23 2014 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-power/indicator-power-service InstallationDate: Installed on 2014-03-01 (42 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140301) ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-power/indicator-power-service SegvAnalysis: Segfault happened at: 0x7f7ffe6237ed g_type_check_instance+13: mov (%rdi),%rax PC (0x7f7ffe6237ed) ok source (%rdi) (0x0021) not located in a known VMA region (needed readable region)! destination %rax ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: indicator-power StacktraceTop: g_type_check_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_handler_disconnect () from /usr/lib/x86_64-linux-gnu/libgobject-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: indicator-power-service crashed with SIGSEGV in g_type_check_instance() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1307021/+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 1399900] [NEW] screen brightness cannot be changed anymore
Public bug reported: The screen brightness does not reliably respond to adjustments anymore since 14.10 release. Previously in 14.04 it was adjustable via a slider in Ubuntu Control Center and via the keyboard buttons (so there is driver and keyboard support for this laptop). Now the keyboard buttons as well as the slider have no effect and the brightness defaults to 100% which is on this device about five times brighter than the comfortable level, and strains the battery. However about 1 in 20 bootups/logins, the brightness is adjustable, but when I logout/login again in the user session, it might again become locked to 100%. I have the suspicion that it depends on the loading of desktop configs or the time I wait before typing my password to login. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Dec 6 12:20:50 2014 DistUpgraded: 2014-11-04 18:35:56,188 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.18, 3.16.0-24-generic, x86_64: installed virtualbox, 4.3.18, 3.16.0-25-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3978] InstallationDate: Installed on 2014-02-02 (306 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140201) MachineType: LENOVO 20266 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic.efi.signed root=UUID=4bfb3686-b9f7-487d-81f6-eceb41097ad9 ro quiet splash acpi_backlight=vendor vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-11-04 (31 days ago) XorgConf: dmi.bios.date: 10/31/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN31WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Sat Dec 6 12:19:59 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16970 vendor SDC xserver.version: 2:1.16.0-1ubuntu1 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 third-party-packages ubuntu utopic -- 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/1399900 Title: screen brightness cannot be changed anymore Status in unity package in Ubuntu: New Bug description: The screen brightness does not reliably respond to adjustments anymore since 14.10 release. Previously in 14.04 it was adjustable via a slider in Ubuntu Control Center and via the keyboard buttons (so there is driver and keyboard support for this laptop). Now the keyboard buttons as well as the slider have no effect and the brightness defaults to 100% which is on this device about five times brighter than the comfortable level, and strains the battery. However about 1 in 20 bootups/logins, the brightness is adjustable, but when I logout/login again in the user session, it might again become locked to 100%. I have the suspicion that it depends on the loading of desktop configs or the time I wait before typing my password to login. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity
[Dx-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
For me, the bug status is not clear ? Someone know if the fix for Ubuntu 14.04 has been released or not ? Below what I understand : - The fix has not been yet released for Ubuntu 14.04 - The fix will be released on Ubuntu 14.04 with Unity 7.2.4 (The current release of Unity is 7.2.3) = https://launchpad.net/unity = https://launchpad.net/unity/+milestones = https://launchpad.net/unity/+milestone/7.2.4 Anyone can tell me if I'm right or not ? Thanks and have a good day ;) -- 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: Confirmed Status in Unity 7.2 series: Confirmed Status in unity package in Ubuntu: Fix Released 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 1399906] [NEW] guest session does not start with Xorg
Public bug reported: When choosing the guest session from the login screen, the screen freezes. `pidof Xorg` gives no running process of the x server. When being logged into a user account and switching to a guest session, it returns after some time to the lock screen of the logged in user. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sat Dec 6 12:51:14 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-02-02 (306 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140201) SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-11-04 (31 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages utopic -- 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/1399906 Title: guest session does not start with Xorg Status in unity package in Ubuntu: New Bug description: When choosing the guest session from the login screen, the screen freezes. `pidof Xorg` gives no running process of the x server. When being logged into a user account and switching to a guest session, it returns after some time to the lock screen of the logged in user. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sat Dec 6 12:51:14 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-02-02 (306 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140201) SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-11-04 (31 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1399906/+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 1315369]
I guess this one is either fixed or dead. -- 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/1315369 Title: Log in not available after lock screen with multi-monitor Status in Unity: Invalid Status in X.org xf86-video-intel: Invalid Status in linux package in Ubuntu: Confirmed Status in unity package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Status in unity source package in Trusty: Confirmed Bug description: After the screen locks I am unable to log back in because the screen with the login prompt is black, and the screen on my laptop just shows the Ubuntu logo. Furthermore, if I then unplug the external monitor (in an attempt to force the log in option to be displayed on the laptop) the laptop screen then goes black and I can't do anything at all. I can't reproduce this if I select lock screen from the UI, but it happens reliably if it locks due to inactivity. Other info: - I am running a fresh install of 14.04 - I have it set to lock after 5 min of inactivity, and require login after lock - I have an external monitor, configured to be on the left side of the laptop screen --- ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jane 2184 F pulseaudio /dev/snd/controlC0: jane 2184 F pulseaudio 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] CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=61f52096-031e-4e3d-b1ae-e504b3b3edec InstallationDate: Installed on 2014-05-01 (20 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417) MachineType: Dell Inc. Dell System XPS L321X Package: unity 7.2.0+14.04.20140416-0ubuntu1 PackageArchitecture: i386 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic root=/dev/mapper/ubuntu--vg-root ro persistent quiet splash ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 Tags: trusty trusty Uname: Linux 3.13.0-24-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/09/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 085X6F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA04:bd04/09/2012:svnDellInc.:pnDellSystemXPSL321X:pvr:rvnDellInc.:rn085X6F:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L321X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1315369/+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 1315369] Re: Log in not available after lock screen with multi-monitor
** Changed in: xserver-xorg-video-intel Status: Incomplete = 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/1315369 Title: Log in not available after lock screen with multi-monitor Status in Unity: Invalid Status in X.org xf86-video-intel: Invalid Status in linux package in Ubuntu: Confirmed Status in unity package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Status in unity source package in Trusty: Confirmed Bug description: After the screen locks I am unable to log back in because the screen with the login prompt is black, and the screen on my laptop just shows the Ubuntu logo. Furthermore, if I then unplug the external monitor (in an attempt to force the log in option to be displayed on the laptop) the laptop screen then goes black and I can't do anything at all. I can't reproduce this if I select lock screen from the UI, but it happens reliably if it locks due to inactivity. Other info: - I am running a fresh install of 14.04 - I have it set to lock after 5 min of inactivity, and require login after lock - I have an external monitor, configured to be on the left side of the laptop screen --- ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jane 2184 F pulseaudio /dev/snd/controlC0: jane 2184 F pulseaudio 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] CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=61f52096-031e-4e3d-b1ae-e504b3b3edec InstallationDate: Installed on 2014-05-01 (20 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417) MachineType: Dell Inc. Dell System XPS L321X Package: unity 7.2.0+14.04.20140416-0ubuntu1 PackageArchitecture: i386 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic root=/dev/mapper/ubuntu--vg-root ro persistent quiet splash ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 Tags: trusty trusty Uname: Linux 3.13.0-24-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/09/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 085X6F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA04:bd04/09/2012:svnDellInc.:pnDellSystemXPSL321X:pvr:rvnDellInc.:rn085X6F:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L321X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1315369/+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
We released a fix but it does not work. The one we released was about text entry not showing randomly on multimonitor and seems to be fixed. Probably what you can reproduce now is a problem with permissions. -- 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: Confirmed Status in Unity 7.2 series: Confirmed Status in unity package in Ubuntu: Fix Released 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 1180260] Re: frozen applications keep the mouse click focus
Can you still reproduce that? ** Changed in: unity Status: New = Incomplete ** Changed in: unity (Ubuntu) Status: New = Incomplete -- 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/1180260 Title: frozen applications keep the mouse click focus Status in Unity: Incomplete Status in unity package in Ubuntu: Incomplete Bug description: happened to me at least twice. An application window is not responding (but not greyed so not considered not responding ), CPU load is low(no high computing) as well as i/o. This time the application was eclipse Kepler Last time I think it was firefox Well, then the mouse can't click. I move the pointer, I can use super key to show unity board, but I can't click anywhere just as there was a glass panel between the mouse and the applications. I press ctrl alt F1, killall -9 application (firefox or java) and on ctrl alt F7 I got my mouse click again. I think this is a bug in the renderer library, maybe a race condition. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-20.31-generic 3.8.11 Uname: Linux 3.8.0-20-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,resize,fade,unitymtgrabhandles,scale,session,unityshell] Date: Wed May 15 09:24:26 2013 InstallationDate: Installed on 2011-07-05 (679 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: Upgraded to raring on 2013-04-26 (18 days ago) --- ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,resize,fade,unitymtgrabhandles,scale,session,unityshell] DistroRelease: Ubuntu 13.04 InstallationDate: Installed on 2011-07-05 (679 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) MarkForUpload: True NonfreeKernelModules: nvidia wl Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.8.0-20.31-generic 3.8.11 Tags: gnome3-ppa raring third-party-packages Uname: Linux 3.8.0-20-generic x86_64 UpgradeStatus: Upgraded to raring on 2013-04-26 (18 days ago) UserGroups: adm admin cdrom davfs2 dialout fuse libvirtd lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1180260/+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 1180548] Re: High load when running VirtualBox
** Changed in: unity (Ubuntu) Status: New = Invalid ** Changed in: unity Status: New = Invalid ** Also affects: virtualbox Importance: Undecided Status: New -- 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/1180548 Title: High load when running VirtualBox Status in Unity: Invalid Status in Virtualbox: New Status in unity package in Ubuntu: Invalid Bug description: When running VirtualBox, the system load suddenly raises without stopping. When I kill compiz (which includes Unity), the load goes down again. If I don't kill it quick enough, the system locks up completely and I need to power off the machine. I was searching very long for a solution because I thought it's a VirtualBox problem. I'm using the Oracle 4.2.12 package provided on http://www.virtualbox.org/, but I also tried using the stock Ubuntu package and even with an older VirtualBox version (4.1), but the problem still occured. Before I had this problem, I was using Ubuntu 12.10 without any issues. When 13.04 came out, I decided to make a fresh installation and have this problem since then. Description of the problem: - I'm running Ubuntu 13.04 on an Asus Zenbook UX31A with 4 GB memory and 128 GB SSD. - Before I start VirtualBox, I have already opened several programs: Chromium, Firefox, Skype are the biggest in terms of memory usage (I think the problem occured less often when VirtualBox was running alone, so maybe it's related to memory usage) - When I start VirtualBox, the problem occurs sometimes during boot, but sometimes only after a a few minutes of uptime. Most of the time, it happened when the machine was idle and I was working in a different window. Workarounds: 1) I can use Unity only when I run a background job which checks for the load and kills / replaces compiz unity if the system load is too high. 2) I decided to install ubuntu-gnome-desktop and switch to GNOME for the time being. It uses compiz as well but without Unity, and the problem is completely gone! (That's why I'm pretty sure it must be a Unity issue...) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1180548/+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 1190898] Re: segfault in unity_support_test
Can you still reproduce that? ** Changed in: unity Status: Confirmed = Incomplete ** Changed in: unity (Ubuntu) Status: Confirmed = Incomplete -- 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/1190898 Title: segfault in unity_support_test Status in Unity: Incomplete Status in unity package in Ubuntu: Incomplete Bug description: After update to Ubuntu 13.04 I was unable to use unity as shell. lxde and gnome appear to work fine. When I choose unity the screen gives just the background and never arrives at the the point where the quicklist is visible or the dash. I made a copy of the /var/log/syslog and then a cat /dev/null / var/log/syslog This is what I got in /var/log/syslog after a login attempt to unity: root@legolas:/var/log# cat syslog Jun 14 09:52:57 legolas colord: device removed: xrandr-LVDS1 Jun 14 09:52:57 legolas colord: Profile removed: icc-0aad3f9acbd994c5976bc9cd10292033 Jun 14 09:52:57 legolas bluetoothd[771]: Endpoint unregistered: sender=:1.362 path=/MediaEndpoint/HFPAG Jun 14 09:52:57 legolas bluetoothd[771]: Endpoint unregistered: sender=:1.362 path=/MediaEndpoint/HFPHS Jun 14 09:52:57 legolas bluetoothd[771]: Endpoint unregistered: sender=:1.362 path=/MediaEndpoint/A2DPSource Jun 14 09:52:57 legolas bluetoothd[771]: Endpoint unregistered: sender=:1.362 path=/MediaEndpoint/A2DPSink Jun 14 09:52:57 legolas bluetoothd[771]: hci0: Remove UUID (0x0011) failed: Busy (0x0a) Jun 14 09:52:57 legolas rtkit-daemon[1840]: Successfully made thread 7285 of process 7285 (n/a) owned by '1000' high priority at nice level -11. Jun 14 09:52:57 legolas rtkit-daemon[1840]: Supervising 1 threads of 1 processes of 1 users. Jun 14 09:52:57 legolas pulseaudio[7285]: [pulseaudio] pid.c: Stale PID file, overwriting. Jun 14 09:52:57 legolas dbus[733]: [system] Activating service name='org.freedesktop.systemd1' (using servicehelper) Jun 14 09:52:57 legolas dbus[733]: [system] Successfully activated service 'org.freedesktop.systemd1' Jun 14 09:52:57 legolas colord: Device added: xrandr-LVDS1 Jun 14 09:52:57 legolas rtkit-daemon[1840]: Successfully made thread 7312 of process 7285 (n/a) owned by '1000' RT at priority 5. Jun 14 09:52:57 legolas rtkit-daemon[1840]: Supervising 2 threads of 1 processes of 1 users. Jun 14 09:52:57 legolas rtkit-daemon[1840]: Successfully made thread 7313 of process 7285 (n/a) owned by '1000' RT at priority 5. Jun 14 09:52:57 legolas rtkit-daemon[1840]: Supervising 3 threads of 1 processes of 1 users. Jun 14 09:52:57 legolas rtkit-daemon[1840]: Successfully made thread 7314 of process 7285 (n/a) owned by '1000' RT at priority 5. Jun 14 09:52:57 legolas rtkit-daemon[1840]: Supervising 4 threads of 1 processes of 1 users. Jun 14 09:52:58 legolas bluetoothd[771]: Endpoint registered: sender=:1.375 path=/MediaEndpoint/HFPAG Jun 14 09:52:58 legolas bluetoothd[771]: Endpoint registered: sender=:1.375 path=/MediaEndpoint/HFPHS Jun 14 09:52:58 legolas bluetoothd[771]: Endpoint registered: sender=:1.375 path=/MediaEndpoint/A2DPSource Jun 14 09:52:58 legolas bluetoothd[771]: Endpoint registered: sender=:1.375 path=/MediaEndpoint/A2DPSink Jun 14 09:52:58 legolas rtkit-daemon[1840]: Successfully made thread 7319 of process 7319 (n/a) owned by '1000' high priority at nice level -11. Jun 14 09:52:58 legolas rtkit-daemon[1840]: Supervising 5 threads of 2 processes of 1 users. Jun 14 09:52:58 legolas pulseaudio[7319]: [pulseaudio] pid.c: Daemon already running. Jun 14 09:52:58 legolas colord: Profile added: icc-9b80530f957bc21605981b113eb57c5c Jun 14 09:52:58 legolas kernel: [ 2376.756271] unity_support_t[7352]: segfault at c2 ip 0040173f sp 7fff55e49250 error 4 in unity_support_test[40+4000] Jun 14 09:53:28 legolas goa[7539]: goa-daemon version 3.6.2 starting [main.c:112, main()] root@legolas:/var/log# Thanks ahead, any suggestions welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1190898/+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 1243369] Re: Mouse cursor movement became jerky, then system stopped responding
Can you still reproduce that? ** Changed in: unity Status: New = Incomplete ** Changed in: unity (Ubuntu) Status: New = Incomplete -- 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/1243369 Title: Mouse cursor movement became jerky, then system stopped responding Status in Unity: Incomplete Status in unity package in Ubuntu: Incomplete Bug description: Just after the failure described in https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/1243365 and after removing the usb pendrive, mouse cursor movements became jerky, meaning that from time to time the mouse cursor would freeze even though I was moving the mouse. Then, the system stopped responding to clicks and I couldn't do anything useful. Apparently there wasn't high CPU or disk activity. Only thing I could do was a hard power off. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.06.19~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8 Uname: Linux 3.8.0-31-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Tue Oct 22 21:22:15 2013 InstallationDate: Installed on 2013-10-11 (11 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) 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/1243369/+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 1263392] Re: I no longer have a shut down on that menu
Your shutdown menu is back? ** Changed in: unity Status: New = Incomplete ** Changed in: unity (Ubuntu) Status: New = Incomplete -- 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/1263392 Title: I no longer have a shut down on that menu Status in Unity: Incomplete Status in unity package in Ubuntu: Incomplete Bug description: A few months - sometime after getting Time Warner Cable - I lost the shut down option. I have to manually hold the power button in for 5 seconds. Where did it go? I know that I did not delete it even if I could. Is it something that Time Warner does with the cable modem? Very annoying. How can I fix this? Can you fix this? 12.04 LTS has been very problematic for me. I have to pray that Unity will pop out. It may take many tries of slamming the mouse against the edge. I've tried low and high sensitivity and in the middle; it doesn't seem to matter!! I can't tell you how many times I've had to wait for my mouse click to do anything!! 30 seconds or more and very often!! What happened to Ubuntu??? Very frustrated with this version of Ubuntu!! I can't seem to find where to stop scripts until one hangs the system for minutes!!! Even when I click stop script It laughs at me!! Not really, just hangs some more. There is no option in the system that I can locate that lets me choose don't run scripts or something equivalent. Help! Please, I really hate Windows. I've been using Linux systems for many years, I'd like to stay a user of a real operating system rather than Bill's. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.20.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-58.88-generic-pae 3.2.53 Uname: Linux 3.2.0-58-generic-pae i686 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sat Dec 21 12:20:48 2013 MarkForUpload: True ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1263392/+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 1232351] Re: the screen blackens out completely for few seconds and it's highly difficult to perform multiple operations at the same time.
Can you still reproduce that? How? ** Changed in: unity Status: New = Incomplete ** Changed in: unity (Ubuntu) Status: New = Incomplete -- 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/1232351 Title: the screen blackens out completely for few seconds and it's highly difficult to perform multiple operations at the same time. Status in Unity: Incomplete Status in unity package in Ubuntu: Incomplete Bug description: Multiple operations are difficult and the screen blackens for few seconds and also the system generates lot of heat. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.20.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-40.62~precise1-generic 3.5.7.20 Uname: Linux 3.5.0-40-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.0.1-0ubuntu17.4 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] CrashDB: unity Date: Sat Sep 28 10:50:05 2013 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/1232351/+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 1263137] Re: unity-panel-service eats cpu and ram
@Alan, it's already fixed right? ** Changed in: unity Status: New = Incomplete ** Changed in: unity (Ubuntu) Status: New = Incomplete -- 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/1263137 Title: unity-panel-service eats cpu and ram Status in Unity: Incomplete Status in unity package in Ubuntu: Incomplete Bug description: I am getting high cpu and ram usage from unity-panel-service on 13.10. Maybe bug 1199877 isn't fixed? My laptop was crawling and swapping like mad, ran top and found unity- panel-service at the top. Killed it and all is happy again. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity-services 7.1.2+13.10.20131014.1-0ubuntu1 Uname: Linux 3.12.0-031200-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,grid,imgpng,gnomecompat,scale,workarounds,mousepoll,regex,wall,move,place,vpswitch,resize,unitymtgrabhandles,snap,session,expo,ezoom,unityshell] Date: Fri Dec 20 15:29:42 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2012-06-29 (538 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MarkForUpload: True SourcePackage: unity UpgradeStatus: Upgraded to saucy on 2013-07-12 (160 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1263137/+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 1205876] Re: whole system became unresponsive to clicks and keystrokes for a couple of minutes
Can you still reproduce that? How often does it happen? ** Changed in: unity Status: New = Incomplete ** Changed in: unity (Ubuntu) Status: New = Incomplete -- 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/1205876 Title: whole system became unresponsive to clicks and keystrokes for a couple of minutes Status in Unity: Incomplete Status in unity package in Ubuntu: Incomplete Bug description: I went to close a couple of windows (Gedit and a Nautilus window), both became grey and both showed up the not-responding pupup (to both of which I replied cancel) and the system stayed unresponsive to both clicks and keystrokes for a full two minutes or so. Mouse cursor was moving fluidly without the smallest jerkyness, but neither clicks nor keystrokes would do nothing. Even Ctrl+Alt+F1 wouldn't work (which would have allowed me to open a virtual terminal and have a look at the processes) By chance, I had a visible open terminal window with top running just prior to the incident, and it wasn't showing high CPU consumption; also, the cooler fan speed didn't seem to indicate that was the case. After a few minutes everything got back to normal. NO MATTER WHAT, keystrokes and clicks must always have the highest priority, in shuch a way that it must NEVER, EVER happen that you can't even open a virtual terminal with Ctrl+Alt+F1. Something is very wrong at a very low level if the whole system can become unresponsive due to some process being very busy or even if this was due to swapping. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: unity 6.12.0-0ubuntu0.2 ProcVersionSignature: Ubuntu 3.5.0-37.58-generic 3.5.7.16 Uname: Linux 3.5.0-37-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu12 Architecture: i386 CompizPlugins: [core,composite,opengl,decor,vpswitch,mousepoll,compiztoolbox,snap,commands,place,resize,session,regex,grid,wall,move,gnomecompat,imgpng,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Sun Jul 28 18:27:47 2013 InstallationDate: Installed on 2010-06-23 (1131 days ago) InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: Upgraded to quantal on 2013-01-13 (196 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1205876/+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 1278985] Re: Regression: Alt invocation of search cannot be remapped, causing pain to Emacs users
Is this still a problem? ** Changed in: unity Status: New = Incomplete ** Changed in: unity (Ubuntu) Status: New = Incomplete -- 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/1278985 Title: Regression: Alt invocation of search cannot be remapped, causing pain to Emacs users Status in Unity: Incomplete Status in unity package in Ubuntu: Incomplete Bug description: A long while ago, we Emacs users requested that it be possible to remap HUD search invocation away from Alt (and especially left-Alt) since this is a very common key chord prefix for Emacs. At some point this was done. In my recent bug LP: #1278582 I mentioned that the binding disappeared in the System Settings-Keyboard-Shortcuts window, but that bug has both been resolved, and a workaround was described by seb128 and tedg in irc that I could use gnome-control-center.real. That does indeed show me the Key to show the HUD setting. However, we still have a pain-inducing regression here ;). That setting is Disabled on my system, and yet the Unity/HUD search dialog is still invoked when hitting either left-Alt or right-Alt. Something consumes the first press of the Alt key so that it does not get passed to any window. I've confirmed this with Emacs, Claws-Mail, and Terminal. For example, if I hit Alt-F with focus in Emacs, Emacs does not see this key binding. If however, I only release the 'F' key, holding down Left-Alt, and then tap 'F' again, Emacs will see the key the second time. Claws exhibits very similar behavior (e.g. I have expunge bound to Alt-K - Claws only sees the second tap of Alt-K). Even worse, if in the course of trying to tap e.g. Alt-F in Emacs I happen to quickly tap Alt (either left or right), then the search dialog comes up and all subsequent typing is diverted to search instead of to Emacs. This is highly disruptive as you might imagine ;) At one point, I had hud and the launcher invocation remapped to Super (and right-Super in fact) and this is much more conducive to Emacs users. On my Trusty box where I've delayed updating to the latest archive packages, hud/unity search is still invoked by Super and *not* by Alt. However, on my fully updated Trusty machine, I experience this regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1278985/+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 1299054] Re: resizing loop on high-dpi screen
** Changed in: unity Status: New = Confirmed ** Changed in: unity Importance: Undecided = Medium ** Changed in: unity Milestone: None = 7.3.2 -- 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/1299054 Title: resizing loop on high-dpi screen Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: When the global scaling factor is set to 2, some dialogs occasionally start changing their window size causing very high CPU activity. This occurs for example in dconf-editor while searching: It appears dconf-editor tries to adjust the window dimensions to the size of the content and reduces the window size until it is unusable. This causes very high CPU activity and freezes the window content. It also happens when (then) resizing the window width (→) or height (↓) afterwards, it tries to revert to the previous window size. However, the only way to resize the window back so that it doesn't reduce its size is by dragging the window corner (↓→). This issue happens also in other applications, for example in apport- dialogs when expanding the collapsed details view. This does not happen when the global scaling factor is set to 1. It could be related to the new window resizing method that updates the window content. org.gnome.desktop.interface.scaling-factor = 2 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140321-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Mar 28 16:07:47 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-02-02 (53 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140201) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1299054/+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 1289204] Re: Local Menus don't work when running as root or invoking as root with gksu [video demo]
** Changed in: unity 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/1289204 Title: Local Menus don't work when running as root or invoking as root with gksu [video demo] Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Video Demo: http://youtu.be/jFrSjHgpMEI This is a small usability bug for the Local Menus in Ubuntu 14.04. This will probably not be experienced by most people and I pretty much just stumbled across this bug myself so it probably wouldn't be a high priority but I wanted to submit it anyway. The bug occurs when running as root or invoking root with gksu. Another bug is found when invoking with gksu using the -k option to stay in the user environment. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1289204/+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 1361311] Re: Dash fade-in/fade-out animation should be configurable
** Changed in: unity Status: New = Opinion ** Changed in: unity (Ubuntu) Status: New = Opinion ** Changed in: unity 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/1361311 Title: Dash fade-in/fade-out animation should be configurable Status in Unity: Opinion Status in unity package in Ubuntu: Opinion Bug description: When I hit super key, or click on Ubuntu logo, there's a fade-in/fade-out transition for the dash window. I personally don't like any type of animation or transition effects, as they seem to me a waste of time. Especialy this fade-in/fade-out transition, it's highly erratic depending on the hardware been executed, the system load, the number of lenses running, etc. I think when using UNITY_LOW_GFX_MODE=1 all animations and transitions should be disabled, or better, this animation times should be configurable by dconf keys. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1361311/+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 1359211] Re: Mouse cursor tiny when hovering unity elements in high DPI mode
** Changed in: unity 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/1359211 Title: Mouse cursor tiny when hovering unity elements in high DPI mode Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: On a high DPI screen (220 DPI) the mouse cursor is really tiny when hovering unity elements. There are various keys in dconf to change the cursor's scale factor or size. I've managed to change it in a way that it looks normal when inside application windows, but its still tiny when on unity elements. I think this should be set automatically by the scale factor setting in system settings. (Using unity 7.3.1+14.10.20140811-0ubuntu1) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1359211/+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 1358823] Re: count emblem in launcher and tabbox doesn't regard high dpi scale settings
*** This bug is a duplicate of bug 1353070 *** https://bugs.launchpad.net/bugs/1353070 ** This bug has been marked a duplicate of bug 1353070 Launcher icon emblems (count) do not scale to match DPI settings -- 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/1358823 Title: count emblem in launcher and tabbox doesn't regard high dpi scale settings Status in Unity: New Status in unity package in Ubuntu: New Bug description: The count emblem on icons in launcher and tabbox stay really tiny even though the rest of the interface is scaled up. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1358823/+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
Thanks for your answer and also for your work Andrea ! Thanks to Marco Trevisan too. Sorry for my english but I don't understand if the fix works or not when you say We released a fix but it does not work then The one we released was text entry not showing randomly on multimonitor and seems to be fixed, for me it's contradictory. What I can say : - My PC using Marco Trevisan's unity package (https://launchpad.net/~3v1n0/+archive/ubuntu/unity-tests) works perfectly since 2014-09-11, - Another PC using Ubuntu's unity package, randomly, I have no input field to type password for unlock (normally this PC is up to date but I have to check). Both use multimonitor and LDAP authentication. -- 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: Confirmed Status in Unity 7.2 series: Confirmed Status in unity package in Ubuntu: Fix Released 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 1399710] Re: no audible warning of high volume level
Marked to be looked at by design. Let them adjust it then we can add it to the indicator-sound backlog. Thanks! ** Also affects: ubuntu-ux Importance: Undecided Status: New ** Changed in: indicator-sound (Ubuntu) Status: New = Incomplete ** Changed in: indicator-sound (Ubuntu) Importance: Undecided = Wishlist -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1399710 Title: no audible warning of high volume level Status in Ubuntu UX bugs: New Status in indicator-sound package in Ubuntu: Incomplete Bug description: Additional to the work done on bug 1373404, I think we need to consider adding an audio warning when the volume crosses the threshold value. The way android works is that the user is asked if they want to allow higher volume levels (they must click ok). Our approach is to just display a visual warning. That's fine (assuming it complies with all legal regs), but it isn't helpful from an accessibility perspective. Obviously folk can hear when levels become painful high, but how about we insert an audible warning when the user crosses the threshold? I'd suggest we do both of the following to indicate an audible warning: 1) Mute (or atleast lower) the currently playing audio streams. 2) Play two beeps in quick succession (at the original volume level prior to mute/lowering). Once the beeps have been played, the volume level will be restored to the appropriate (higher) level. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1399710/+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 1307021] Re: indicator-power-service crashed with SIGSEGV in g_type_check_instance()
** Branch linked: lp:~ted/indicator-sound/lp1307021-closed-disconnect -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1307021 Title: indicator-power-service crashed with SIGSEGV in g_type_check_instance() Status in indicator-power package in Ubuntu: In Progress Bug description: patryk@Aspire-E1-772G:~$ lsb_release -rd; apt-cache policy indicator-power Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 indicator-power: Zainstalowana: 12.10.6+14.04.20140328-0ubuntu1 Kandydująca: 12.10.6+14.04.20140328-0ubuntu1 Tabela wersji: *** 12.10.6+14.04.20140328-0ubuntu1 0 500 http://at.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status patryk@Aspire-E1-772G:~$ shows problem on startup ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: indicator-power 12.10.6+14.04.20140328-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 Date: Sat Apr 12 23:06:23 2014 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-power/indicator-power-service InstallationDate: Installed on 2014-03-01 (42 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140301) ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-power/indicator-power-service SegvAnalysis: Segfault happened at: 0x7f7ffe6237ed g_type_check_instance+13: mov (%rdi),%rax PC (0x7f7ffe6237ed) ok source (%rdi) (0x0021) not located in a known VMA region (needed readable region)! destination %rax ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: indicator-power StacktraceTop: g_type_check_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_handler_disconnect () from /usr/lib/x86_64-linux-gnu/libgobject-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: indicator-power-service crashed with SIGSEGV in g_type_check_instance() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1307021/+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 1307021] Re: indicator-power-service crashed with SIGSEGV in g_type_check_instance()
** Changed in: indicator-power (Ubuntu) Status: Confirmed = In Progress ** Changed in: indicator-power (Ubuntu) Assignee: (unassigned) = Ted Gould (ted) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1307021 Title: indicator-power-service crashed with SIGSEGV in g_type_check_instance() Status in indicator-power package in Ubuntu: In Progress Bug description: patryk@Aspire-E1-772G:~$ lsb_release -rd; apt-cache policy indicator-power Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 indicator-power: Zainstalowana: 12.10.6+14.04.20140328-0ubuntu1 Kandydująca: 12.10.6+14.04.20140328-0ubuntu1 Tabela wersji: *** 12.10.6+14.04.20140328-0ubuntu1 0 500 http://at.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status patryk@Aspire-E1-772G:~$ shows problem on startup ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: indicator-power 12.10.6+14.04.20140328-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 Date: Sat Apr 12 23:06:23 2014 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-power/indicator-power-service InstallationDate: Installed on 2014-03-01 (42 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140301) ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-power/indicator-power-service SegvAnalysis: Segfault happened at: 0x7f7ffe6237ed g_type_check_instance+13: mov (%rdi),%rax PC (0x7f7ffe6237ed) ok source (%rdi) (0x0021) not located in a known VMA region (needed readable region)! destination %rax ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: indicator-power StacktraceTop: g_type_check_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_handler_disconnect () from /usr/lib/x86_64-linux-gnu/libgobject-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: indicator-power-service crashed with SIGSEGV in g_type_check_instance() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1307021/+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 1399862] Re: SIGSEGV with module-remap-sink mixing to mono
** Changed in: indicator-sound (Ubuntu) Status: New = In Progress ** Changed in: indicator-sound (Ubuntu) Importance: Undecided = Medium ** Changed in: indicator-sound (Ubuntu) Assignee: (unassigned) = Ted Gould (ted) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1399862 Title: SIGSEGV with module-remap-sink mixing to mono Status in indicator-sound package in Ubuntu: In Progress Bug description: indicator-sound-service crashes with a SIGSEGV immediately when it's executed if I have a mono sink made with module-remap-sink in /etc/pulse/default.pa. This is the line that makes it crash: load-module module-remap-sink sink_name=mono master=alsa_output.pci-_00_1b.0.analog-stereo channels=2 channel_map=mono,mono I have never tried variations of that line, but I know that the sink works normally and does what it's supposed to do (mix the audio to mono), so I don't think it's a problem with it. If I comment it and restart pulseaudio, then I can start indicator-sound-service and it will work normally. I'm using Ubuntu 15.04. indicator-sound 12.10.2+15.04.20141105-0ubuntu1 (the most recent version as of now). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1399862/+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 1399862] Re: SIGSEGV with module-remap-sink mixing to mono
** Branch linked: lp:~ted/indicator-sound/lp1399862-active-port-null -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1399862 Title: SIGSEGV with module-remap-sink mixing to mono Status in indicator-sound package in Ubuntu: In Progress Bug description: indicator-sound-service crashes with a SIGSEGV immediately when it's executed if I have a mono sink made with module-remap-sink in /etc/pulse/default.pa. This is the line that makes it crash: load-module module-remap-sink sink_name=mono master=alsa_output.pci-_00_1b.0.analog-stereo channels=2 channel_map=mono,mono I have never tried variations of that line, but I know that the sink works normally and does what it's supposed to do (mix the audio to mono), so I don't think it's a problem with it. If I comment it and restart pulseaudio, then I can start indicator-sound-service and it will work normally. I'm using Ubuntu 15.04. indicator-sound 12.10.2+15.04.20141105-0ubuntu1 (the most recent version as of now). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1399862/+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 1391164] Re: Silent mode setting is not read on startup
** Also affects: canonical-devices-system-image Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1391164 Title: Silent mode setting is not read on startup Status in the base for Ubuntu mobile products: New Status in indicator-sound package in Ubuntu: Confirmed Status in indicator-sound package in Ubuntu RTM: Confirmed Bug description: 1) Enable silent mode in system-settings 2) Restart the device 3) Notice that the sound indicator shows silent mode as disabled but the system-settings shows it as enabled It appears like the sound indicator is not reading the silent mode state on start up? $ system-image-cli -i current build number: 125 device name: mako channel: ubuntu-touch/ubuntu-rtm/devel-proposed alias: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2014-11-08 05:08:10 version version: 125 version ubuntu: 20141108 version device: 20141106 version custom: mako-1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1391164/+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 1307021] Re: indicator-power-service crashed with SIGSEGV in g_type_check_instance()
** Also affects: indicator-sound (Ubuntu) Importance: Undecided Status: New ** Changed in: indicator-sound (Ubuntu) Status: New = In Progress ** Changed in: indicator-sound (Ubuntu) Importance: Undecided = Medium ** Changed in: indicator-sound (Ubuntu) Assignee: (unassigned) = Ted Gould (ted) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1307021 Title: indicator-power-service crashed with SIGSEGV in g_type_check_instance() Status in indicator-power package in Ubuntu: In Progress Status in indicator-sound package in Ubuntu: In Progress Bug description: patryk@Aspire-E1-772G:~$ lsb_release -rd; apt-cache policy indicator-power Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 indicator-power: Zainstalowana: 12.10.6+14.04.20140328-0ubuntu1 Kandydująca: 12.10.6+14.04.20140328-0ubuntu1 Tabela wersji: *** 12.10.6+14.04.20140328-0ubuntu1 0 500 http://at.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status patryk@Aspire-E1-772G:~$ shows problem on startup ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: indicator-power 12.10.6+14.04.20140328-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 Date: Sat Apr 12 23:06:23 2014 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-power/indicator-power-service InstallationDate: Installed on 2014-03-01 (42 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140301) ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-power/indicator-power-service SegvAnalysis: Segfault happened at: 0x7f7ffe6237ed g_type_check_instance+13: mov (%rdi),%rax PC (0x7f7ffe6237ed) ok source (%rdi) (0x0021) not located in a known VMA region (needed readable region)! destination %rax ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: indicator-power StacktraceTop: g_type_check_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_handler_disconnect () from /usr/lib/x86_64-linux-gnu/libgobject-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: indicator-power-service crashed with SIGSEGV in g_type_check_instance() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1307021/+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 1307021] Re: indicator-power-service crashed with SIGSEGV in g_type_check_instance()
So, I screwed up and thought this was an indicator-sound bug, and found an issue. But I can't find anything to do with dbus closing in indicator-power :-( ** Changed in: indicator-power (Ubuntu) Status: In Progress = Invalid -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1307021 Title: indicator-power-service crashed with SIGSEGV in g_type_check_instance() Status in indicator-power package in Ubuntu: Invalid Status in indicator-sound package in Ubuntu: In Progress Bug description: patryk@Aspire-E1-772G:~$ lsb_release -rd; apt-cache policy indicator-power Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 indicator-power: Zainstalowana: 12.10.6+14.04.20140328-0ubuntu1 Kandydująca: 12.10.6+14.04.20140328-0ubuntu1 Tabela wersji: *** 12.10.6+14.04.20140328-0ubuntu1 0 500 http://at.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status patryk@Aspire-E1-772G:~$ shows problem on startup ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: indicator-power 12.10.6+14.04.20140328-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 Date: Sat Apr 12 23:06:23 2014 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-power/indicator-power-service InstallationDate: Installed on 2014-03-01 (42 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140301) ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-power/indicator-power-service SegvAnalysis: Segfault happened at: 0x7f7ffe6237ed g_type_check_instance+13: mov (%rdi),%rax PC (0x7f7ffe6237ed) ok source (%rdi) (0x0021) not located in a known VMA region (needed readable region)! destination %rax ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: indicator-power StacktraceTop: g_type_check_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_handler_disconnect () from /usr/lib/x86_64-linux-gnu/libgobject-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: indicator-power-service crashed with SIGSEGV in g_type_check_instance() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1307021/+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
In a nuthsell: the bug is not fixed. You using ldap? Probably it's a configuration issue. Gnome screensaver used to be buggy using ldap authentication too, but most of time it's just a configuration issue. -- 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: Confirmed Status in Unity 7.2 series: Confirmed Status in unity package in Ubuntu: Fix Released 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
Re: [Dx-packages] [Bug 1278985] Re: Regression: Alt invocation of search cannot be remapped, causing pain to Emacs users
On Dec 06, 2014, at 02:29 PM, Andrea Azzarone wrote: Is this still a problem? No. It's not entirely discoverable, but it is possible to fix. -- 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/1278985 Title: Regression: Alt invocation of search cannot be remapped, causing pain to Emacs users Status in Unity: Incomplete Status in unity package in Ubuntu: Incomplete Bug description: A long while ago, we Emacs users requested that it be possible to remap HUD search invocation away from Alt (and especially left-Alt) since this is a very common key chord prefix for Emacs. At some point this was done. In my recent bug LP: #1278582 I mentioned that the binding disappeared in the System Settings-Keyboard-Shortcuts window, but that bug has both been resolved, and a workaround was described by seb128 and tedg in irc that I could use gnome-control-center.real. That does indeed show me the Key to show the HUD setting. However, we still have a pain-inducing regression here ;). That setting is Disabled on my system, and yet the Unity/HUD search dialog is still invoked when hitting either left-Alt or right-Alt. Something consumes the first press of the Alt key so that it does not get passed to any window. I've confirmed this with Emacs, Claws-Mail, and Terminal. For example, if I hit Alt-F with focus in Emacs, Emacs does not see this key binding. If however, I only release the 'F' key, holding down Left-Alt, and then tap 'F' again, Emacs will see the key the second time. Claws exhibits very similar behavior (e.g. I have expunge bound to Alt-K - Claws only sees the second tap of Alt-K). Even worse, if in the course of trying to tap e.g. Alt-F in Emacs I happen to quickly tap Alt (either left or right), then the search dialog comes up and all subsequent typing is diverted to search instead of to Emacs. This is highly disruptive as you might imagine ;) At one point, I had hud and the launcher invocation remapped to Super (and right-Super in fact) and this is much more conducive to Emacs users. On my Trusty box where I've delayed updating to the latest archive packages, hud/unity search is still invoked by Super and *not* by Alt. However, on my fully updated Trusty machine, I experience this regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1278985/+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 1278985] Re: Regression: Alt invocation of search cannot be remapped, causing pain to Emacs users
** Changed in: unity Status: Incomplete = Invalid ** Changed in: unity (Ubuntu) Status: Incomplete = 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/1278985 Title: Regression: Alt invocation of search cannot be remapped, causing pain to Emacs users Status in Unity: Invalid Status in unity package in Ubuntu: Invalid Bug description: A long while ago, we Emacs users requested that it be possible to remap HUD search invocation away from Alt (and especially left-Alt) since this is a very common key chord prefix for Emacs. At some point this was done. In my recent bug LP: #1278582 I mentioned that the binding disappeared in the System Settings-Keyboard-Shortcuts window, but that bug has both been resolved, and a workaround was described by seb128 and tedg in irc that I could use gnome-control-center.real. That does indeed show me the Key to show the HUD setting. However, we still have a pain-inducing regression here ;). That setting is Disabled on my system, and yet the Unity/HUD search dialog is still invoked when hitting either left-Alt or right-Alt. Something consumes the first press of the Alt key so that it does not get passed to any window. I've confirmed this with Emacs, Claws-Mail, and Terminal. For example, if I hit Alt-F with focus in Emacs, Emacs does not see this key binding. If however, I only release the 'F' key, holding down Left-Alt, and then tap 'F' again, Emacs will see the key the second time. Claws exhibits very similar behavior (e.g. I have expunge bound to Alt-K - Claws only sees the second tap of Alt-K). Even worse, if in the course of trying to tap e.g. Alt-F in Emacs I happen to quickly tap Alt (either left or right), then the search dialog comes up and all subsequent typing is diverted to search instead of to Emacs. This is highly disruptive as you might imagine ;) At one point, I had hud and the launcher invocation remapped to Super (and right-Super in fact) and this is much more conducive to Emacs users. On my Trusty box where I've delayed updating to the latest archive packages, hud/unity search is still invoked by Super and *not* by Alt. However, on my fully updated Trusty machine, I experience this regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1278985/+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 1228093] Re: Dash content flickers when the touchpad is used to scroll it.
** Branch linked: lp:nux/trusty -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1228093 Title: Dash content flickers when the touchpad is used to scroll it. Status in Nux: Fix Committed Status in Nux trusty series: Fix Committed Status in nux package in Ubuntu: Fix Released Status in nux source package in Trusty: Fix Released Bug description: [Impact] Dash content flickers when two-finger scrolling on the touchpad [Test case] 1. Enable two fingers scroll from Unity Control Center - Mouse and Touchpad 2. Open the unity dash, expand the search results and start scrolling vertically 3. Content should not flicker and should ignore horizontal scroll events [Regression potential] Scrolling on dash content does not work properly To manage notifications about this bug go to: https://bugs.launchpad.net/nux/+bug/1228093/+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 1399862] Re: SIGSEGV with module-remap-sink mixing to mono
The stacktrace looks very similar to the one in this bug: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1395455 -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1399862 Title: SIGSEGV with module-remap-sink mixing to mono Status in indicator-sound package in Ubuntu: In Progress Bug description: indicator-sound-service crashes with a SIGSEGV immediately when it's executed if I have a mono sink made with module-remap-sink in /etc/pulse/default.pa. This is the line that makes it crash: load-module module-remap-sink sink_name=mono master=alsa_output.pci-_00_1b.0.analog-stereo channels=2 channel_map=mono,mono I have never tried variations of that line, but I know that the sink works normally and does what it's supposed to do (mix the audio to mono), so I don't think it's a problem with it. If I comment it and restart pulseaudio, then I can start indicator-sound-service and it will work normally. I'm using Ubuntu 15.04. indicator-sound 12.10.2+15.04.20141105-0ubuntu1 (the most recent version as of now). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1399862/+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
