[Dx-packages] [Bug 1255530] Re: /home/phablet/.pam_environment does not get updated on OTA upgrades
** Package changed: pam (Ubuntu) = ubuntu-system-settings (Ubuntu) -- 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/1255530 Title: /home/phablet/.pam_environment does not get updated on OTA upgrades Status in “indicator-datetime” package in Ubuntu: Invalid Status in “ubuntu-system-settings” package in Ubuntu: New Bug description: starting my phone set to german language the lock screen properly shows a 24h clock ... as aoon as the panel clock shows up, the lockscreen format (and all other places where the time is shown in the UI) is swithcing to AM/PM 12h time format. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1255530/+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 1232037] Re: Adding an event to the calender on the top bar in Unity date time does nothing
*** This bug is a duplicate of bug 1250632 *** https://bugs.launchpad.net/bugs/1250632 ** This bug has been marked a duplicate of bug 1250632 Date and time indicator option Add an event doesn't work. -- 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/1232037 Title: Adding an event to the calender on the top bar in Unity date time does nothing Status in “indicator-datetime” package in Ubuntu: New Bug description: If you click on the time and then you click on add an event (sorry my screenshot is German) it simply does nothing. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: evolution (not installed) ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 Uname: Linux 3.11.0-8-generic x86_64 ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 Date: Fri Sep 27 16:13:36 2013 InstallationDate: Installed on 2013-09-27 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20130925.1) MarkForUpload: True SourcePackage: evolution UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1232037/+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 1240251] Re: Does not open with today, can't jump there
I think it is important that the indicator resets the selected date when it gets closed. It's not very feasible. -- 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/1240251 Title: Does not open with today, can't jump there Status in “indicator-datetime” package in Ubuntu: Confirmed Bug description: When clicking on the date/time, the dropdown window contains the year/month/day I visited there previously. Since altering the month or year doesn't change the day, often today's day number is highlighted. This, along with today's date being shown at the top, very easily leads to the misbelief that the current month's calendar is being shown, which is not necessarily the case. It's terribly misleading. (In the mean time, I understand that keeping the year/month during closure and reopening of the dropdown might be considered a feature useful for many people.) Furthermore, there's no option to jump to today, I have to manually walk to the current year and month. My suggestion is a Today button, with clearly distinguisable disabled state if it's already today's month being shown. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-datetime 13.10.0+13.10.20131011-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Tue Oct 15 23:55:07 2013 InstallationDate: Installed on 2012-05-30 (503 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MarkForUpload: True SourcePackage: indicator-datetime UpgradeStatus: Upgraded to saucy on 2013-10-12 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1240251/+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 1244285] Re: Date/time sometimes doesn’t appear in menu bar, settings greyed out (Ubuntu 13.10)
WRONG SOLUTION. Has nothing to do with reboot or kill. A bit of thinking. Has everything to do with matching repository server to your region. In my case, time region was China, but repo server was UK. Changing server to China solved the problem, permanently. Best tool for this is Synaptic. very easy user install problem to correct. -- 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/1244285 Title: Date/time sometimes doesn’t appear in menu bar, settings greyed out (Ubuntu 13.10) Status in “indicator-datetime” package in Ubuntu: Confirmed Bug description: it does not happen often, and when it happens, just a log out and re- log in is enough to restore it. http://askubuntu.com/questions/357266/how-to-show-time-in- ubuntu-13-10/357280 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1244285/+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 1247242] Re: Unity wont start - compiz could not load ccp
In my case I fix this by downgrading libprotobuf7 to version in repository. Until that moment I had a version from PPA: https://launchpad.net/~chris-lea/+archive/protobuf -- 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/1247242 Title: Unity wont start - compiz could not load ccp Status in “unity” package in Ubuntu: Incomplete Bug description: Using ubuntu 13.04. Two days ago after system restart unity could not start. Only nautilus desktop shows on the screen. When create terminal window and starts unity, following log appears: compiz (core) - Info: Loading plugin: core compiz (core) - Info: Starting plugin: core compiz (core) - Info: Loading plugin: ccp compiz (core) - Error: Failed to load plugin: ccp I was trying: - upgrade ubuntu to 13.10 (was waiting in line, but haven't time for this earlier) next - to reinstall unity/compiz (e.g. sudo apt-get install unity --force-reinstall true) - to reset config: unity --reset-icons; dconf reset -f /org/compiz/ - to reinstall nvidia drivers without any luck. On different accounts (users and guest) there is the same error .xsession-errors has nothing about unity XFree86.log also Nothing so far helps. Hardware configuration: - Thinkpad T61 (Dual Core T7500, Nvidia Quadro NVS 140M) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1247242/+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 1256298] [NEW] Artifacts visible in highlighted category header
Public bug reported: When searching, using keyboard navigation to highlight the category header often results in artifacts in the hightlight. See the attached video. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20131106.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia wl .proc.driver.nvidia.gpus.0: Error: [Errno 21] Jest katalogiem: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.20 Wed Oct 30 17:43:35 PDT 2013 GCC version: gcc version 4.8.2 (Ubuntu/Linaro 4.8.2-1ubuntu2) .tmp.unity.support.test.0: ApportVersion: 2.12.7-0ubuntu1 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: Fri Nov 29 13:46:12 2013 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0493] NVIDIA Corporation GF119M [NVS 4200M] [10de:1056] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:1493] MachineType: Dell Inc. Latitude E6420 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-12-generic root=/dev/mapper/username--laptop-ubuntu--root ro splash quiet vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/11/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd07/11/2012:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.49-2 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.2-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-5ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu1 xserver.bootTime: Wed Nov 27 14:45:45 2013 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) [drm] KMS not enabled xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 12606 vendor AUO xserver.version: 2:1.14.3-5ubuntu1 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 third-party-packages trusty ubuntu ** Attachment added: unity_artifact.mp4 https://bugs.launchpad.net/bugs/1256298/+attachment/3919742/+files/unity_artifact.mp4 -- 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/1256298 Title: Artifacts visible in highlighted category header Status in “unity” package in Ubuntu: New Bug description: When searching, using keyboard navigation to highlight the category header often results in artifacts in the hightlight. See the attached video. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20131106.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia wl .proc.driver.nvidia.gpus.0: Error: [Errno 21] Jest katalogiem: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.20 Wed Oct 30 17:43:35 PDT 2013 GCC version: gcc version 4.8.2 (Ubuntu/Linaro 4.8.2-1ubuntu2) .tmp.unity.support.test.0: ApportVersion: 2.12.7-0ubuntu1 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: Fri Nov 29 13:46:12 2013 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd
[Dx-packages] [Bug 1256308] [NEW] No suitable icon for metrics collection
Public bug reported: Once Ubuntu performs general metrics collection, it will invite you to opt in using a dialog with an icon. https://wiki.ubuntu.com/ErrorTracker#metrics Currently the theme contains no relevant icon for this purpose. As shown in the wireframe, I suggest a stethoscope. [Originally reported by e-mail on 2012-05-17.] ** Affects: humanity-icon-theme (Ubuntu) Importance: Low Assignee: Nick Tait (jnick-tait) Status: New ** Changed in: humanity-icon-theme (Ubuntu) Importance: Undecided = Low -- You received this bug notification because you are a member of DX Packages, which is subscribed to humanity-icon-theme in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1256308 Title: No suitable icon for metrics collection Status in “humanity-icon-theme” package in Ubuntu: New Bug description: Once Ubuntu performs general metrics collection, it will invite you to opt in using a dialog with an icon. https://wiki.ubuntu.com/ErrorTracker#metrics Currently the theme contains no relevant icon for this purpose. As shown in the wireframe, I suggest a stethoscope. [Originally reported by e-mail on 2012-05-17.] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1256308/+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 1256342] Re: unity-scope-loader crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()
** Information type changed from Private to Public ** Package changed: libunity (Ubuntu) = mediascanner (Ubuntu) -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1256342 Title: unity-scope-loader crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler() Status in “mediascanner” package in Ubuntu: New Bug description: This seems to be happening during unity8 autopilot test run, which suggests this is about the scope consumer restarting a lot. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: libunity9 7.1.3+14.04.20131106-0ubuntu1 Uname: Linux 3.4.0-3-mako armv7l ApportVersion: 2.12.7-0ubuntu1 Architecture: armhf CurrentDesktop: Unity Date: Fri Nov 29 14:55:24 2013 ExecutablePath: /usr/bin/unity-scope-loader ExecutableTimestamp: 1383715346 InstallationDate: Installed on 2013-11-29 (0 days ago) InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20131129) ProcCmdline: /usr/bin/unity-scope-loader music/mediascanner.scope video/mediascanner.scope ProcCwd: / Signal: 6 SourcePackage: libunity StacktraceTop: ?? () from /lib/arm-linux-gnueabihf/libc.so.6 raise () from /lib/arm-linux-gnueabihf/libc.so.6 abort () from /lib/arm-linux-gnueabihf/libc.so.6 __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6 ?? () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6 Title: unity-scope-loader crashed with SIGABRT in raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm autopilot cdrom dialout dip nopasswdlogin plugdev sudo tty video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mediascanner/+bug/1256342/+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 1253593] Re: hud memory usage grows over time
Thanks for this report guys. I am close to completing a significant overhaul to HUD, which should put a lid on these recurring memory leak issues. The reason you are seeing increased memory usage under normal conditions is because HUD had a voice recognition capability integrated into it for 13.10. This is never used on the desktop (it's only used on the phone), but because of the way I integrated it, it's running even though you can't actually use it with the legacy Unity7 user interface. Obviously this doesn't totally account for HUD using several hundred megabytes of memory. This is simply down to old fashioned memory leaks. In addition to a less leak-prone design, the revisions to HUD include splitting the voice engine out into its own service, which will only be started on the phone. Thus, your memory usage should go back down to similar levels as in 12.04. -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1253593 Title: hud memory usage grows over time Status in “hud” package in Ubuntu: Confirmed Bug description: After five days of uptime hud-service used 749 MB of RAM. Restarting hud-service drops it memory usage to about 100-150 MB, on the next day it's using already 227 MB of RAM. I'm using Ubuntu 13.10 for developing Qt-based application. Most of the time following applications started and used: Qt Creator, Qt Linguist, Qt Designer; gnome-terminal; gitk, git gui, cmake-gui; Firefox; Pidgin. In the tray there are: System Load Indicator, Nagstamon (v0.9.11 from official site), shutter, remmina. Also I use Yandex.Music and Grooveshark web-apps. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: hud 13.10.1+13.10.20131031-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10 Uname: Linux 3.8.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Thu Nov 21 14:29:59 2013 InstallationDate: Installed on 2013-10-16 (35 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: hud UpgradeStatus: Upgraded to saucy on 2013-11-07 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1253593/+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 1131385] Re: Always on top prevents application spread from working
** Changed in: unity Assignee: (unassigned) = Ryan Nathaniel Smith (ryan-smith) -- 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/1131385 Title: Always on top prevents application spread from working Status in Ayatana Design: Invalid Status in Compiz: Invalid Status in Unity: Triaged Status in “unity” package in Ubuntu: Confirmed Bug description: Consider you have many windows of the same type open. One method of switching between them is clicking the launcher icon which reveals the application spread. Now you can choose between the windows. This is how it should be. However, the design idea was, if the windows are marked Always on Top there is no need for an application spread, as they are always on top. This is a bug and needs to be changed, because it does not consider minimized windows and therefore prevents switching to those windows. If you have windows of the same application open, some of them minimized and ALL non-minimized windows are marked as Always on top, the application spread does not work anymore, clicking the launcher does nothing. Whether the minimized windows are marked always on top or not does not matter. So the simplest way to reproduce this bug would be: 1.) Open two windows of the same application. 2.) Minimize one and mark the other (non-minimized) as Always on top. 3.) Try to switch to the minimized window using application spread To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1131385/+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 1223635] Re: Move Title to Backend
** Changed in: sevilerow Status: New = Fix Released -- 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, dx-packages, dx-packages https://bugs.launchpad.net/bugs/1223635 Title: Move Title to Backend Status in Bluetooth Menu: Fix Released Status in The Date and Time Indicator: Fix Released Status in Indicator Location: Fix Released Status in The Messaging Menu: Fix Released Status in Network Menu: Fix Released Status in The Power Indicator: Fix Released Status in Sound Menu: Fix Released Status in The Sevilerow project: Fix Released Status in The Unity 8 shell: Fix Released Status in “indicator-bluetooth” package in Ubuntu: Fix Released Status in “indicator-datetime” package in Ubuntu: Fix Released Status in “indicator-location” package in Ubuntu: Fix Released Status in “indicator-messages” package in Ubuntu: Fix Released Status in “indicator-network” package in Ubuntu: Fix Released Status in “indicator-power” package in Ubuntu: Fix Released Status in “indicator-sound” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu: Fix Released Bug description: We should have the titles in the root action state for the indicators. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-bluetooth/+bug/1223635/+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 1131385] Re: Always on top prevents application spread from working
** Changed in: unity Status: Triaged = In Progress -- 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/1131385 Title: Always on top prevents application spread from working Status in Ayatana Design: Invalid Status in Compiz: Invalid Status in Unity: In Progress Status in “unity” package in Ubuntu: Confirmed Bug description: Consider you have many windows of the same type open. One method of switching between them is clicking the launcher icon which reveals the application spread. Now you can choose between the windows. This is how it should be. However, the design idea was, if the windows are marked Always on Top there is no need for an application spread, as they are always on top. This is a bug and needs to be changed, because it does not consider minimized windows and therefore prevents switching to those windows. If you have windows of the same application open, some of them minimized and ALL non-minimized windows are marked as Always on top, the application spread does not work anymore, clicking the launcher does nothing. Whether the minimized windows are marked always on top or not does not matter. So the simplest way to reproduce this bug would be: 1.) Open two windows of the same application. 2.) Minimize one and mark the other (non-minimized) as Always on top. 3.) Try to switch to the minimized window using application spread To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1131385/+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 1255981] Re: Indicator options stopped working with glib 2.39.1
** Branch linked: lp:ubuntu/trusty-proposed/indicator-power -- 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/1255981 Title: Indicator options stopped working with glib 2.39.1 Status in “indicator-power” package in Ubuntu: In Progress Bug description: The new glib got uploaded to trusty today, it somewhat made indicator- power unhappy. That warning is yeld on start: g_simple_action_set_state: assertion 'state_type != NULL' failed Stacktrace: #0 g_log (log_domain=log_domain@entry=0xb7f1c1d8 GLib-GIO, log_level=log_level@entry=G_LOG_LEVEL_CRITICAL, format=format@entry=0xb7d57fbe %s: assertion '%s' failed) at /build/glib2.0-tux5JG/glib2.0-2.39.1/./glib/gmessages.c:1055 #1 0xb7d0f28d in g_return_if_fail_warning ( log_domain=log_domain@entry=0xb7f1c1d8 GLib-GIO, pretty_function=pretty_function@entry=0xb7f37e70 __FUNCTION__.12093 g_simple_action_set_state, expression=0xb7f37815 state_type != NULL) at /build/glib2.0-tux5JG/glib2.0-2.39.1/./glib/gmessages.c:1068 #2 0xb7ec334e in g_simple_action_set_state (simple=simple@entry=0x8064a20, value=0x8062518) at /build/glib2.0-tux5JG/glib2.0-2.39.1/./gio/gsimpleaction.c:165 #3 0xb7ec35a1 in g_simple_action_set_property (object=0x8064a20, prop_id=5, value=0xbfffe9ec, pspec=0x80710d0) at /build/glib2.0-tux5JG/glib2.0-2.39.1/./gio/gsimpleaction.c:248 #4 0xb7ddbb64 in object_set_property (nqueue=0x80608a0, value=0xbfffea4c, pspec=0x80710d0, object=0x8064a20) at /build/glib2.0-tux5JG/glib2.0-2.39.1/./gobject/gobject.c:1376 #5 g_object_set_property (object=0x8064a20, property_name=0xb7f369b1 state, value=value@entry=0xbfffea4c) at /build/glib2.0-tux5JG/glib2.0-2.39.1/./gobject/gobject.c:2304 #6 0xb7ed2352 in g_settings_binding_key_changed ( settings=settings@entry=0x8063e40, key=0x80628c8 show-time, ---Type return to continue, or q return to quit--- user_data=user_data@entry=0x806f400) at /build/glib2.0-tux5JG/glib2.0-2.39.1/./gio/gsettings.c:2482 #7 0xb7ed523c in g_settings_bind_with_mapping (settings=0x8063e40, key=0x80561d0 show-time, object=0x8064a20, property=0x80562d2 state, flags=(G_SETTINGS_BIND_GET | G_SETTINGS_BIND_SET), get_mapping=0x8052dc0, set_mapping=0x8052db0, user_data=0x0, destroy=0x0) at /build/glib2.0-tux5JG/glib2.0-2.39.1/./gio/gsettings.c:2779 #8 0x08053945 in ?? () #9 0xb7df58d3 in g_type_create_instance (type=134658216) at /build/glib2.0-tux5JG/glib2.0-2.39.1/./gobject/gtype.c:1868 #10 0xb7dd871e in g_object_new_internal (class=class@entry=0x806b960, params=0xbfffed9c, n_params=1) at /build/glib2.0-tux5JG/glib2.0-2.39.1/./gobject/gobject.c:1722 #11 0xb7ddabb7 in g_object_new_valist ( object_type=object_type@entry=134658216, first_property_name=first_property_name@entry=0x80561a0 device-provider, var_args=optimized out, var_args@entry=0xbfffee68 \030\006\b) at /build/glib2.0-tux5JG/glib2.0-2.39.1/./gobject/gobject.c:1978 #12 0xb7ddae10 in g_object_new (object_type=134658216, first_property_name=0x80561a0 device-provider) at /build/glib2.0-tux5JG/glib2.0-2.39.1/./gobject/gobject.c:1569 Changing the options in the indicator menu (e.g show %) doesn't work as a result To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1255981/+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 1255981] Re: Indicator options stopped working with glib 2.39.1
This bug was fixed in the package indicator-power - 12.10.6+14.04.20131129-0ubuntu1 --- indicator-power (12.10.6+14.04.20131129-0ubuntu1) trusty; urgency=low [ Lars Uebernickel ] * Use GSettingsActions instead of g_settings_bind This also fixes a bug: the actions were created stateless, but assigned a state later. (LP: #1255981) [ Ubuntu daily release ] * Automatic snapshot from revision 217 -- Ubuntu daily release ps-jenk...@lists.canonical.com Fri, 29 Nov 2013 18:36:27 + ** Changed in: indicator-power (Ubuntu) Status: In Progress = Fix Released -- 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/1255981 Title: Indicator options stopped working with glib 2.39.1 Status in “indicator-power” package in Ubuntu: Fix Released Bug description: The new glib got uploaded to trusty today, it somewhat made indicator- power unhappy. That warning is yeld on start: g_simple_action_set_state: assertion 'state_type != NULL' failed Stacktrace: #0 g_log (log_domain=log_domain@entry=0xb7f1c1d8 GLib-GIO, log_level=log_level@entry=G_LOG_LEVEL_CRITICAL, format=format@entry=0xb7d57fbe %s: assertion '%s' failed) at /build/glib2.0-tux5JG/glib2.0-2.39.1/./glib/gmessages.c:1055 #1 0xb7d0f28d in g_return_if_fail_warning ( log_domain=log_domain@entry=0xb7f1c1d8 GLib-GIO, pretty_function=pretty_function@entry=0xb7f37e70 __FUNCTION__.12093 g_simple_action_set_state, expression=0xb7f37815 state_type != NULL) at /build/glib2.0-tux5JG/glib2.0-2.39.1/./glib/gmessages.c:1068 #2 0xb7ec334e in g_simple_action_set_state (simple=simple@entry=0x8064a20, value=0x8062518) at /build/glib2.0-tux5JG/glib2.0-2.39.1/./gio/gsimpleaction.c:165 #3 0xb7ec35a1 in g_simple_action_set_property (object=0x8064a20, prop_id=5, value=0xbfffe9ec, pspec=0x80710d0) at /build/glib2.0-tux5JG/glib2.0-2.39.1/./gio/gsimpleaction.c:248 #4 0xb7ddbb64 in object_set_property (nqueue=0x80608a0, value=0xbfffea4c, pspec=0x80710d0, object=0x8064a20) at /build/glib2.0-tux5JG/glib2.0-2.39.1/./gobject/gobject.c:1376 #5 g_object_set_property (object=0x8064a20, property_name=0xb7f369b1 state, value=value@entry=0xbfffea4c) at /build/glib2.0-tux5JG/glib2.0-2.39.1/./gobject/gobject.c:2304 #6 0xb7ed2352 in g_settings_binding_key_changed ( settings=settings@entry=0x8063e40, key=0x80628c8 show-time, ---Type return to continue, or q return to quit--- user_data=user_data@entry=0x806f400) at /build/glib2.0-tux5JG/glib2.0-2.39.1/./gio/gsettings.c:2482 #7 0xb7ed523c in g_settings_bind_with_mapping (settings=0x8063e40, key=0x80561d0 show-time, object=0x8064a20, property=0x80562d2 state, flags=(G_SETTINGS_BIND_GET | G_SETTINGS_BIND_SET), get_mapping=0x8052dc0, set_mapping=0x8052db0, user_data=0x0, destroy=0x0) at /build/glib2.0-tux5JG/glib2.0-2.39.1/./gio/gsettings.c:2779 #8 0x08053945 in ?? () #9 0xb7df58d3 in g_type_create_instance (type=134658216) at /build/glib2.0-tux5JG/glib2.0-2.39.1/./gobject/gtype.c:1868 #10 0xb7dd871e in g_object_new_internal (class=class@entry=0x806b960, params=0xbfffed9c, n_params=1) at /build/glib2.0-tux5JG/glib2.0-2.39.1/./gobject/gobject.c:1722 #11 0xb7ddabb7 in g_object_new_valist ( object_type=object_type@entry=134658216, first_property_name=first_property_name@entry=0x80561a0 device-provider, var_args=optimized out, var_args@entry=0xbfffee68 \030\006\b) at /build/glib2.0-tux5JG/glib2.0-2.39.1/./gobject/gobject.c:1978 #12 0xb7ddae10 in g_object_new (object_type=134658216, first_property_name=0x80561a0 device-provider) at /build/glib2.0-tux5JG/glib2.0-2.39.1/./gobject/gobject.c:1569 Changing the options in the indicator menu (e.g show %) doesn't work as a result To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1255981/+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 10905] Re: Keyboard shortcuts, window management - Can't use any global keyboard shortcuts or hotkeys when applet/menu is open
I've read the code in unity/services/panel-service.c about PanelService: close a menu and re-send the keyevent when handling a combination Or when we try to open HUD/Dash. Also, close the active menu if a new application is opened and focused. (LP: #10905, #1234457, #1197071), but it still does not resolve the problem about PrintScreen key to snapshot context menu. The root reason is at the XGrabKeyboard in popup_grab_on_window() of gtk/gtkmenu.c. Guys, don't bother yourself any more, as you know linux means freedom, we could get rid of XGrabKeyboard by ourselves: http://stackoverflow.com/a/20071469/264181 -- 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/10905 Title: Keyboard shortcuts, window management - Can't use any global keyboard shortcuts or hotkeys when applet/menu is open Status in Ayatana Design: Fix Committed Status in GTK+ GUI Toolkit: Won't Fix Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: Reproduce scenario : - left click on an applet - try the ^-Alt arrow to switch desktop When an applet contextual menu is opened, you can't switch desktop with keyboard shortcuts. Normally,we should have a consistent behaviour in regards with the workspace-selector applet, ie : - first ^-Alt-arrow (for the workspace-selector : click), the menu is unfolded - second ^-Alt-arrow , we go to the next desktop === see bug 29894 for not being able to take screenshots when menu is open, another symptom of this bug. -- Note from Design: This is a critical bug, a user should be able to use a global keyboard shortcut at any moment, including when a menu is open. In the unlikely case that there is a conflict between the global keyboard shortcuts ( see https://launchpadlibrarian.net/85352653/Super_key_shutcuts_overlay.png ) and the menu keyboard shortcuts, the menu keyboard shortcuts should take precedence. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/10905/+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
