[Dx-packages] [Bug 1086656] Re: Possible breakage of fallback on other desktops
** Tags added: utopic ** Also affects: libappindicator (Ubuntu) Importance: Undecided Status: New ** Tags added: xubuntu -- You received this bug notification because you are a member of DX Packages, which is subscribed to libappindicator in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1086656 Title: Possible breakage of fallback on other desktops Status in Libappindicator: Confirmed Status in “libappindicator” package in Ubuntu: New Bug description: It seems many people in the Steam forums are reporting that the libappindicator fallback isn't working on some desktops. It is unclear of the complete situation, but this bug is to track it and try to figure out if there is an issue, and if so, fix it. The Steam forum threads: http://steamcommunity.com/app/221410/discussions/1/882966056643744991/ http://steamcommunity.com/app/221410/discussions/1/882966056417505546/ http://steamcommunity.com/app/221410/discussions/1/882965239659234799/ To manage notifications about this bug go to: https://bugs.launchpad.net/libappindicator/+bug/1086656/+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 1185117] Re: [MIR] unity-gtk-module
** Changed in: unity-gtk-module (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-gtk-module in Ubuntu. https://bugs.launchpad.net/bugs/1185117 Title: [MIR] unity-gtk-module Status in “unity-gtk-module” package in Ubuntu: Fix Released Bug description: Rationale: Unity's global menu bar is implemented by patching GTK+ to load appmenu-gtk, which watches for GtkMenu construction and exports an equivalent structure over D-Bus for indicator-appmenu. This module is meant as a replacement appmenu-gtk so that the patch can be dropped. MIR Issues: The test suite cannot be run at build time since the module needs to be already installed and in effect for the tests to be applicable. Therefore the tests should be run post-install in order to be effective. The other MIRs have also been checked and no other issues have been found. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-gtk-module/+bug/1185117/+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 845920] Re: Unity works very sloooooow.
Since Ubuntu14.04 graphics is very slow on 1. a VMware installation 2. on RS780 AMD graphics On Ubuntu12.04 there was no problem, including watching movies with RS780 graphics. With Ubuntu14.04 it is impossible (too slow). -- 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/845920 Title: Unity works very sloow. Status in Unity: Expired Status in “unity” package in Ubuntu: Expired Bug description: When I press Super button, dash will show only after 3-5 seconds. If I press alt+tab, list of windows shows afret 5 seconds or more. Pages in browser scrolls very slow. When I click on link, browser freezes on 10 seconds (sometimes more, sometimes less). It's in all browsers (FF, Chrome, Opera). When I run gwibber (or some another program) I must wait more than 10 seconds while it loading. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: unity 4.12.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4 Uname: Linux 3.0.0-10-generic i686 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86 Kernel Module 280.13 Wed Jul 27 16:55:43 PDT 2011 GCC version: gcc version 4.6.1 (Ubuntu/Linaro 4.6.1-9ubuntu2) .tmp.unity.support.test.0: Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,gnomecompat,grid,imgpng,mousepoll,move,place,regex,resize,session,snap,unitymtgrabhandles,vpswitch,wall,thumbnail,animation,expo,ezoom,fade,scale,unityshell,workarounds] CompositorRunning: compiz Date: Fri Sep 9 21:49:54 2011 DistUpgraded: Fresh install DistroCodename: oneiric DistroVariant: ubuntu DkmsStatus: nvidia-current, 280.13, 3.0.0-10-generic, i686: installed nvidia-current, 280.13, 3.0.0-9-generic, i686: installed GraphicsCard: nVidia Corporation G86 [GeForce 8600M GS] [10de:0425] (rev a1) (prog-if 00 [VGA controller]) Subsystem: LG Electronics, Inc. Device [1854:0094] InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta i386 (20110901) JockeyStatus: xorg:nvidia_173 - NVIDIA accelerated graphics driver (Proprietary, Disabled, Not in use) xorg:nvidia_current-update - NVIDIA accelerated graphics driver (post-release updates) (Proprietary, Disabled, Not in use) xorg:nvidia_current - NVIDIA accelerated graphics driver (Proprietary, Enabled, Not in use) xorg:nvidia_173-update - NVIDIA accelerated graphics driver (post-release updates) (Proprietary, Disabled, Not in use) MachineType: LG Electronics R500-U.CP21R1 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: PATH=(custom, no user) LANG=uk_UA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.0.0-10-generic root=UUID=d1297443-a1be-403d-8941-167ab2a1acfa ro quiet splash vt.handoff=7 SourcePackage: unity UnitySupportTest: Error: command ['/usr/lib/nux/unity_support_test', '-p', '-f'] failed with exit code -11: UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/29/2007 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: COLSSF10 dmi.board.name: COLUMBIA dmi.board.vendor: LG Electronics dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LG Electronics dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrCOLSSF10:bd08/29/2007:svnLGElectronics:pnR500-U.CP21R1:pvrNotApplicable:rvnLGElectronics:rnCOLUMBIA:rvrNotApplicable:cvnLGElectronics:ct10:cvrN/A: dmi.product.name: R500-U.CP21R1 dmi.product.version: Not Applicable dmi.sys.vendor: LG Electronics version.compiz: compiz 1:0.9.5.92+bzr2791-0ubuntu2 version.libdrm2: libdrm2 2.4.26-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20110811.g93fc084-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/845920/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help :
[Dx-packages] [Bug 1201947] Re: unity-panel-service crashed with signal 5 in g_type_create_instance() from bamf_matcher_get_default()
Ubuntu 14.10. Just turning my computer on: unity-panel-service crashed with signal 5 in g_type_create_instance() Same bug? -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-appmenu in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1201947 Title: unity-panel-service crashed with signal 5 in g_type_create_instance() from bamf_matcher_get_default() Status in BAMF Application Matching Framework: Confirmed Status in “indicator-appmenu” package in Ubuntu: Confirmed Bug description: Opening a new firefox window, I got this crash. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: indicator-appmenu 13.01.0daily13.06.07-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-2.11-generic 3.10.0 Uname: Linux 3.10.0-2-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.10.2-0ubuntu4 Architecture: i386 CheckboxSubmission: c4273c0f4f2b8d26cd6bf31cadfd2912 CheckboxSystem: a871981cb5bdf4d6ebd55be46becf77e Date: Wed Jul 17 00:06:00 2013 EcryptfsInUse: Yes ExecutablePath: /usr/lib/unity/unity-panel-service MarkForUpload: True ProcCmdline: /usr/lib/unity/unity-panel-service ProcEnviron: PATH=(custom, user) SHELL=/bin/bash LANG=fr_FR.UTF-8 LANGUAGE=fr_FR:en XDG_RUNTIME_DIR=set Signal: 5 SourcePackage: indicator-appmenu StacktraceTop: ?? () from /usr/lib/i386-linux-gnu/libbamf3.so.1 g_type_create_instance (type=162641616) at /build/buildd/glib2.0-2.37.3/./gobject/gtype.c:1868 g_object_new_internal (class=class@entry=0x9b1b740, params=params@entry=0x0, n_params=n_params@entry=0) at /build/buildd/glib2.0-2.37.3/./gobject/gobject.c:1743 g_object_newv (object_type=object_type@entry=162641616, n_parameters=n_parameters@entry=0, parameters=parameters@entry=0x0) at /build/buildd/glib2.0-2.37.3/./gobject/gobject.c:1887 g_object_new (object_type=162641616, first_property_name=0x0) at /build/buildd/glib2.0-2.37.3/./gobject/gobject.c:1553 Title: unity-panel-service crashed with signal 5 in g_type_create_instance() UpgradeStatus: Upgraded to saucy on 2013-05-25 (51 days ago) UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev pulse pulse-access scanner tape users video To manage notifications about this bug go to: https://bugs.launchpad.net/bamf/+bug/1201947/+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 647437] Re: [ati] unity extremely slow
Even the desktop edition has very poor graphics performance. On RS780 graphics, which was fast enough to view hd-movies in Ubuntu12.04. VMware graphics is EXTREME slow compared to ubuntu12.04. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/647437 Title: [ati] unity extremely slow Status in Mutter: New Status in Unity: Won't Fix Status in “unity” package in Ubuntu: Won't Fix Bug description: Binary package hint: unity Desktop edition works fine, but the netbook edition is extremely slow. I have an ATI HD3470 graphic card and use the latest fglrx driver. If I uses the free driver I get a corrupted display. I've never got unity or gnome shell to work properly in this laptop. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: unity 0.2.44-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic i686 NonfreeKernelModules: fglrx Architecture: i386 Date: Sat Sep 25 12:30:14 2010 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta i386 (20100901.1) ProcEnviron: LANG=fr_FR.utf8 SHELL=/bin/bash SourcePackage: unity To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/647437/+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 160311] Re: Resizing windows by grabbing window borders is difficult
After 7 years it is finally confirmed! :O -- 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/160311 Title: Resizing windows by grabbing window borders is difficult Status in Ayatana Design: Fix Released Status in Decorator for compiz-fusion: New Status in One Hundred Papercuts: Fix Released Status in The Metacity Window Manager: In Progress Status in Release Notes for Ubuntu: Fix Released Status in Unity: Fix Released Status in Unity 2D: Invalid Status in “light-themes” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Confirmed Bug description: This bug is fixed in unity-3d since ubuntu 11.04. It still exists in unity-2d and will never be fixed as unity-2d is no longer supported since ubuntu 12.10 (see comment #343). * This should mostly be fixed for Natty and might get backported to earlier releases as well. For Precise (12.04) this is again broken for unity-2d (as of 17.7.2012 unity-2d 5.12.0-0ubuntu1.1). Note that if the window has a scrollbar, you can grab that to resize the window. If not, you are stuck with the 1px border. Workaround: NONE KNOWN (see comment 320)? * *Blueprint for Natty, Ubuntu 11.04: https://blueprints.edge.launchpad.net/ubuntu/+spec/packageselection- dx-n-resizing-windows Work items1 * Make sure the new resize grip fits in current applications; doesn't interfere with anything. We should make some noise about this during the Natty cycle so people keep their eyes open and file bugs. 2 * Invisible window resize area - around 3px invisible area to allow resize on all sides. * Working grip backported to gtk2 already available in ppa : https://launchpad.net/~bratsche/+archive/gtk * Workaround for Compiz/Unity: Alt+Middlemousebutton resizes a window most comfortably. Workaround: Edit /usr/share/themes/Ambiance/metacity-1/metacity- theme-1.xml. Set the following values in frame_geometry_normal as desired: distance name=left_width value=3/ distance name=right_width value=3/ distance name=bottom_height value=3/ Binary package hint: metacity - The issue has been an issue for users (especially of large) screens for several releases- Trackpad users seem to be particularly impacted by this- The issue appears to have been significantly aggravated in Lucid by changing the border width from 3 pixels to 1 pixel The window borders in metacity are far too thin to be used for comfortable window resizing, and resize handles are not available in all applications (or even most). In fact, of all the windows I have open right now, not a single one of them has a resize handle. The result is that I get a lot of misses when I try to drag a window border, which usually results in my clicking on the wrong window altogether. The best fix for this usability bug is to create an invisible region around each non-maximized window about 4px thick that can be used for resizing (in addition to the visible border). Or perhaps there should be a border thickness option on the System Preferences Windows dialog (although the default thickness should still be increased considerably). Ideally all windows would also have a resize handle but I realize that these have to be application controlled (at least that seems to be the position of the metacity team). To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/160311/+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 1360102] Re: Unity device blacklist nonfunctional
** Changed in: unity Status: New = Triaged ** Changed in: unity Importance: Undecided = Medium ** Changed in: unity (Ubuntu) Status: New = Triaged ** Changed in: unity (Ubuntu) Importance: Undecided = Medium -- 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/1360102 Title: Unity device blacklist nonfunctional Status in Unity: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: Installing 14.04 in a classroom dual-boot environment, Unity shows icons for the Windows partitions on the launcher, nonfunctional since they require root to mount. Such extraneous icons only serve to confuse the user. Googling, I found out about the com.canonical.Unity.Devices blacklist gsettings entry. I made a script that generates a schema such as this, for internal drives: [com.canonical.Unity.Devices] blacklist=['F236BFEF36BFB349','1A98C11998C0F473','c251a534-47dd-4ecb-a62c-2ced6914ef4a','122357ec-3130-482f-b20e-a4c6522e0873'] Here's the corresponding output of blkid -o list device fs_type labelmount point UUID --- /dev/sda1ntfsSystem (not mounted)F236BFEF36BFB349 /dev/sda2ntfsOSDisk (not mounted)1A98C11998C0F473 /dev/sda3swap swap c251a534-47dd-4ecb-a62c-2ced6914ef4a /dev/sda4ext4 / 122357ec-3130-482f-b20e-a4c6522e0873 I put the file in /usr/share/glib-2.0/schemas and ran glib-compile- schemas on it. The entry _does_ show up in a user's session as evidenced by gsettings get and dconf-editor. dconf-editor also has a documentation line for the entry that indicates that this _should_ indeed prevent the named drives from appearing. However, the icons persist in appearing, even on a clean home directory (no old user configuration to confuse anything). Can this be fixed, or is there another way to prevent Unity from showing local internal drives to users who have no means of accessing them? Disabling drive icons altogether would be suboptimal but perhaps workable too, though it'd be preferable that the removable drives would get icons. However, even removing unity://devices from com.canonical.Unity.Launcher favorites didn't prevent the icons from appearing (though the same edit did succeed in removing other application icons, so the setting itself went through properly). lsb_release -rd is: Description: Ubuntu 14.04.1 LTS Release: 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1360102/+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 1358340] Re: [Indicators] Complete greeter profiles
** Changed in: indicator-sound (Ubuntu) Importance: Undecided = High ** Changed in: indicator-sound (Ubuntu) Status: New = Confirmed ** Changed in: indicator-transfer (Ubuntu) Importance: Undecided = High ** Changed in: indicator-transfer (Ubuntu) Status: New = Confirmed -- 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/1358340 Title: [Indicators] Complete greeter profiles Status in The Date and Time Indicator: Confirmed Status in The Messaging Menu: Confirmed Status in Sound Menu: Confirmed Status in Transfer Indicator: Confirmed Status in Ubuntu UX bugs: Fix Committed Status in The Unity 8 shell: Fix Released Status in “gsettings-ubuntu-touch-schemas” package in Ubuntu: Fix Released Status in “indicator-datetime” package in Ubuntu: New Status in “indicator-messages” package in Ubuntu: New Status in “indicator-sound” package in Ubuntu: Confirmed Status in “indicator-transfer” package in Ubuntu: Confirmed Status in “ubuntu-system-settings” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu RTM: Fix Released Bug description: A recent change in the interest of security removed access to the indicators when the phone is locked and the greeter is showing. This was an accentual change based on a misunderstanding There had been a plan to support media playback control via the sound indicator. Without this the user must unlock the phone in order to simply pause the music or change songs, etc. Desired resolution: - Revert the change that caused this issue - Add a switch to System Settings to enable security conscious user to switch off Launcher and Greeter access while the phone is locked. This setting should *always* be off by default. https://wiki.ubuntu.com/SecurityAndPrivacySettings#Locking To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1358340/+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 1300722] Re: hud-service is eating up 100% of one of my CPUs in a poll loop
I've noticed it when running emacs-snapshot. emacs is very responsive at first but after a while (one hour more or less) it's unbearably slow. Moving the focus from one window to another takes a few seconds. When that happens, both emacs and hud-service cpu usage go up to 100% (I have a dual-core CPU). -- 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/1300722 Title: hud-service is eating up 100% of one of my CPUs in a poll loop Status in Unity HUD: Confirmed Status in “hud” package in Ubuntu: In Progress Bug description: hud-service is polling like crazy: Context Switches: PID ProcessVoluntary Involuntary Total Ctxt Sw/Sec Ctxt Sw/Sec Ctxt Sw/Sec 2295 hud-service 46084.6342.94 46127.58 (very high) 2325 hud-service 0.09 0.00 0.09 (very low) 2329 hud-service 0.07 0.00 0.07 (very low) 2340 hud-service 0.05 0.00 0.05 (very low) Total 46084.8442.94 46127.78 File I/O operations: No file I/O operations detected. System calls traced: PID Process Syscall CountRate/Sec 2295 hud-service poll 83 23124.8503 2295 hud-service write10 0.2313 2295 hud-service sendmsg 4 0.0925 2325 hud-service restart_syscall 1 0.0231 2329 hud-service restart_syscall 1 0.0231 2340 hud-service restart_syscall 1 0.0231 Total 100 23125.2435 (gdb) where #0 0x7fda8121cfbd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fda7f1bb4b8 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #2 0x7fda7f1ba3ff in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #3 0x7fda7f1a49dc in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #4 0x7fda7f1a5464 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #5 0x7fda82ce9e65 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #6 0x7fda82d2fc64 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7fda82d30582 in QDBusPendingCallWatcher::waitForFinished() () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #8 0x7fda83eb940b in DBusMenuImporter::slotMenuAboutToShow() () from /usr/lib/x86_64-linux-gnu/libdbusmenu-qt5.so.2 #9 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x0045ab3f in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int) () #11 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int) () #12 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int) () #13 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int) () #14 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int) () #15 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int) () #16 0x0045ae8d in hud::service::DBusMenuCollector::activate() () #17 0x00441e43 in hud::service::WindowImpl::activate() () #18 0x00439f6a in hud::service::QueryImpl::updateToken(QSharedPointerhud::service::Window) () #19 0x0043a672 in hud::service::QueryImpl::refresh() () #20 0x0044b115 in ?? () #21 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x0045662a in hud::service::ApplicationListImpl::FocusedWindowChanged(unsigned int, QString const, unsigned int) () #23 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x00467361 in ComCanonicalUnityWindowStackInterface::FocusedWindowChanged(unsigned int, QString const, unsigned int) () #25 0x004678bd in ?? () #26 0x00467c63 in ComCanonicalUnityWindowStackInterface::qt_metacall(QMetaObject::Call, int, void**) () #27 0x7fda82cf180f in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #28 0x7fda8435e22e in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x7fda823d5c2c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #30 0x7fda823dadf6 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #31 0x7fda84335c2d in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #32
[Dx-packages] [Bug 1364070] Re: utopic unity (7.3.1+14.10.20140811-0ubuntu1) launcher addition through gsettings isn't picked up
** Description changed: As discussed on IRC, I tried to change the favorites key, and 3 trials on 10 didn't make any change in what the launcher displays. seb128 reproduced it as well. (just be aware that we just create the .desktop file just before). The exact same code seems to work 100% of the time on trusty. So, we: 1. create the desktop file 2. from gi.repository import GLib, Gio gsettings = Gio.Settings(schema_id=com.canonical.Unity.Launcher, path=/com/canonical/unity/launcher/) then, get the favorites list and add the desktop file. 3. gsettings.set_strv(favorites, new_launcher_list) - No launcher icon added from new launcher list. However, a $ gsettings get shows that desktop file (which is present. Note that changing the list and changing it back works. + + + This was first experimented on June 2014 on IRC. -- 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/1364070 Title: utopic unity (7.3.1+14.10.20140811-0ubuntu1) launcher addition through gsettings isn't picked up Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: As discussed on IRC, I tried to change the favorites key, and 3 trials on 10 didn't make any change in what the launcher displays. seb128 reproduced it as well. (just be aware that we just create the .desktop file just before). The exact same code seems to work 100% of the time on trusty. So, we: 1. create the desktop file 2. from gi.repository import GLib, Gio gsettings = Gio.Settings(schema_id=com.canonical.Unity.Launcher, path=/com/canonical/unity/launcher/) then, get the favorites list and add the desktop file. 3. gsettings.set_strv(favorites, new_launcher_list) - No launcher icon added from new launcher list. However, a $ gsettings get shows that desktop file (which is present. Note that changing the list and changing it back works. This was first experimented on June 2014 and reported on IRC. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1364070/+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 1364070] Re: utopic unity (7.3.1+14.10.20140811-0ubuntu1) launcher addition through gsettings isn't picked up
** Description changed: As discussed on IRC, I tried to change the favorites key, and 3 trials on 10 didn't make any change in what the launcher displays. seb128 reproduced it as well. (just be aware that we just create the .desktop file just before). The exact same code seems to work 100% of the time on trusty. So, we: 1. create the desktop file 2. from gi.repository import GLib, Gio gsettings = Gio.Settings(schema_id=com.canonical.Unity.Launcher, path=/com/canonical/unity/launcher/) then, get the favorites list and add the desktop file. 3. gsettings.set_strv(favorites, new_launcher_list) - No launcher icon added from new launcher list. However, a $ gsettings get shows that desktop file (which is present. Note that changing the list and changing it back works. - - This was first experimented on June 2014 on IRC. + This was first experimented on June 2014 and reported on IRC. -- 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/1364070 Title: utopic unity (7.3.1+14.10.20140811-0ubuntu1) launcher addition through gsettings isn't picked up Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: As discussed on IRC, I tried to change the favorites key, and 3 trials on 10 didn't make any change in what the launcher displays. seb128 reproduced it as well. (just be aware that we just create the .desktop file just before). The exact same code seems to work 100% of the time on trusty. So, we: 1. create the desktop file 2. from gi.repository import GLib, Gio gsettings = Gio.Settings(schema_id=com.canonical.Unity.Launcher, path=/com/canonical/unity/launcher/) then, get the favorites list and add the desktop file. 3. gsettings.set_strv(favorites, new_launcher_list) - No launcher icon added from new launcher list. However, a $ gsettings get shows that desktop file (which is present. Note that changing the list and changing it back works. This was first experimented on June 2014 and reported on IRC. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1364070/+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 1364070] Re: utopic unity (7.3.1+14.10.20140811-0ubuntu1) launcher addition through gsettings isn't picked up
** Changed in: unity Importance: Undecided = Medium ** Changed in: unity (Ubuntu) Importance: Undecided = Medium -- 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/1364070 Title: utopic unity (7.3.1+14.10.20140811-0ubuntu1) launcher addition through gsettings isn't picked up Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: As discussed on IRC, I tried to change the favorites key, and 3 trials on 10 didn't make any change in what the launcher displays. seb128 reproduced it as well. (just be aware that we just create the .desktop file just before). The exact same code seems to work 100% of the time on trusty. So, we: 1. create the desktop file 2. from gi.repository import GLib, Gio gsettings = Gio.Settings(schema_id=com.canonical.Unity.Launcher, path=/com/canonical/unity/launcher/) then, get the favorites list and add the desktop file. 3. gsettings.set_strv(favorites, new_launcher_list) - No launcher icon added from new launcher list. However, a $ gsettings get shows that desktop file (which is present. Note that changing the list and changing it back works. This was first experimented on June 2014 and reported on IRC. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1364070/+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 1260978] Re: [Greeter] should be able to control music service while greeter locked
** Tags removed: touch-2014-09-25 ** Tags added: ota-2 -- 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/1260978 Title: [Greeter] should be able to control music service while greeter locked Status in Media Hub: In Progress Status in Ubuntu UX bugs: Triaged Status in “indicator-sound” package in Ubuntu: Opinion Status in “ubuntu-music-app” package in Ubuntu: Opinion Status in “ubuntu-settings-components” package in Ubuntu: Opinion Status in “unity8” package in Ubuntu: Opinion Bug description: Not sure what component to file this against-- please reassign as desired. I use my phone to play music on random while I'm driving. This works great except when I want to advance or pause the song, where I have to go through the greeter first to access the player. This can either take my attention away from driving or I need to wait until the next stop light to advance the song. This is less of a concern when the greeter can just be swiped with one gesture, but is a big concern if you enable the passcode lock where you have to add the passcode to access the player. If the music is playing, the greeter should allow rudimentary manipulation of the music, eg, pause/play and forward/back. Other platforms seem to allow for this (eg android). To manage notifications about this bug go to: https://bugs.launchpad.net/media-hub/+bug/1260978/+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 1369971] [NEW] unity style dialogs sometimes not clickable (keyboard shortcuts, shutdown, ...)
You have been subscribed to a public bug: When you log into Ubuntu 14.04 for the first time, a keyboard shortcuts dialog is shown. This dialog has an (X) in the upper left corner, but sometimes it's not actually possible to click it. The dialog buttons are for some reason unresponsive. The same happens with the shutdown dialog. The issue can be reproduced by placing a shutdown icon on the desktop. An executable ~/Desktop/shutdown.desktop file with these contents: [Desktop Entry] Comment= Terminal=false Name=Shutdown Exec=/usr/bin/gnome-session-quit --reboot Type=Application Icon=system-shutdown You might have to relogin or refresh the desktop with F5 for the icon to be shown. When clicking that icon, the shutdown dialog appears but it's entirely unresponsive. You can't click the buttons, you can't click the (X) in the upper left corner. If there is a window in the background of the dialog, for some reason all clicks go to that background window even though the dialog is shown on top. So it's as if the dialog lives in the wrong layer or something. This only happens when starting the dialog from the desktop icon. The dialog works if you put the icon in the dash instead, or start /usr/bin /gnome-session-quit --reboot from a terminal, or change 'Terminal=false' to 'Terminal=true' (which makes a terminal window appear when you click the icon). I'll attach the screenshot that shows unresponsive dialog, and regular dialog side by side. You can see the mouse cursor is ignored for the unresponsive dialog, whereas it highlights (X), buttons, etc. properly for the working one. I can reproduce this both within the Ubuntu 14.04.1 Live CD system, as well as in the finished install. ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- unity style dialogs sometimes not clickable (keyboard shortcuts, shutdown, ...) https://bugs.launchpad.net/bugs/1369971 You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. -- 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 1369971] Re: unity style dialogs sometimes not clickable (keyboard shortcuts, shutdown, ...)
Thanks, these dialogs come from unity itself, so reassigning there. ** Package changed: gnome-session (Ubuntu) = unity (Ubuntu) -- 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/1369971 Title: unity style dialogs sometimes not clickable (keyboard shortcuts, shutdown, ...) Status in “unity” package in Ubuntu: New Bug description: When you log into Ubuntu 14.04 for the first time, a keyboard shortcuts dialog is shown. This dialog has an (X) in the upper left corner, but sometimes it's not actually possible to click it. The dialog buttons are for some reason unresponsive. The same happens with the shutdown dialog. The issue can be reproduced by placing a shutdown icon on the desktop. An executable ~/Desktop/shutdown.desktop file with these contents: [Desktop Entry] Comment= Terminal=false Name=Shutdown Exec=/usr/bin/gnome-session-quit --reboot Type=Application Icon=system-shutdown You might have to relogin or refresh the desktop with F5 for the icon to be shown. When clicking that icon, the shutdown dialog appears but it's entirely unresponsive. You can't click the buttons, you can't click the (X) in the upper left corner. If there is a window in the background of the dialog, for some reason all clicks go to that background window even though the dialog is shown on top. So it's as if the dialog lives in the wrong layer or something. This only happens when starting the dialog from the desktop icon. The dialog works if you put the icon in the dash instead, or start /usr/bin/gnome-session-quit --reboot from a terminal, or change 'Terminal=false' to 'Terminal=true' (which makes a terminal window appear when you click the icon). I'll attach the screenshot that shows unresponsive dialog, and regular dialog side by side. You can see the mouse cursor is ignored for the unresponsive dialog, whereas it highlights (X), buttons, etc. properly for the working one. I can reproduce this both within the Ubuntu 14.04.1 Live CD system, as well as in the finished install. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1369971/+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 1305202] Re: workplace switcher not active by default, contradicting doc
** Branch linked: lp:ubuntu/utopic-proposed/ubuntu-docs -- 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/1305202 Title: workplace switcher not active by default, contradicting doc Status in “ubuntu-docs” package in Ubuntu: Fix Committed Status in “unity” package in Ubuntu: Invalid Bug description: In Trusty beta 2, fully updated, the workplace switcher is not active by default. This contradicts the doc, https://help.ubuntu.com/14.04/ubuntu-help/shell-windows.html I had to turn to a a third party page, http://iloveubuntu.net/ubuntu-1404-received-improved-keyboard-shortcuts-workspaces to see how to enable it. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140404-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed Apr 9 10:28:55 2014 InstallationDate: Installed on 2014-04-07 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1305202/+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 1305202] Re: workplace switcher not active by default, contradicting doc
This bug was fixed in the package ubuntu-docs - 14.10.2 --- ubuntu-docs (14.10.2) utopic; urgency=low * power-hibernate.page: - Correction of the fix in version 14.10.1 (LP: #1360657). * html/ubuntu.xsl: - Include wiki name in the Community Help Wiki link URL. * Bump version to 14.10 / trusty. * startup-applications.page: New page. * sharing-bluetooth.page, unity-launcher-menu.page: - Typos fixed (LP: #1301487, LP: #1303143). * References to non-existent Nautilus gear button replaced (LP: #1301468). * tips-specialchars.page: - Instruction how to enter a character by code point corrected (LP: #1303017). * shell-workspaces*.page: - Description of how to enable workspaces added (LP: #1305202). * look-background.page: - Removed suggestion to switch workspace - workspaces disabled by default. * What's new page disabled due to few news. * Updated ubuntu-help.pot. * ubuntu-help/C/figures/ubuntu-mascot-creature.jpg: Unicorn mascot. * New Chechen (ce) translation. * The latest translations exported from Launchpad. [ Doug Smythies ] * html/Makefile: - Missing languages added. - Broken make install fixed. -- Gunnar Hjalmarsson gunna...@ubuntu.com Thu, 18 Sep 2014 19:32:00 +0200 ** Changed in: ubuntu-docs (Ubuntu) Status: Fix Committed = Fix Released -- 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/1305202 Title: workplace switcher not active by default, contradicting doc Status in “ubuntu-docs” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Invalid Bug description: In Trusty beta 2, fully updated, the workplace switcher is not active by default. This contradicts the doc, https://help.ubuntu.com/14.04/ubuntu-help/shell-windows.html I had to turn to a a third party page, http://iloveubuntu.net/ubuntu-1404-received-improved-keyboard-shortcuts-workspaces to see how to enable it. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140404-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed Apr 9 10:28:55 2014 InstallationDate: Installed on 2014-04-07 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1305202/+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
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1359211 Title: Mouse cursor tiny when hovering unity elements in high DPI mode Status in Unity: New 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 1165463] Re: Unity crashed - no window options, no keyboard - unity disappeared
How did you run `dconf reset -f /org/compiz/` if unity is broken (it complains `error: Cannot autolaunch D-Bus without X11 $DISPLAY` when run in console opened with kbdStrg/kbd+kbdAlt/kbd+kbdF5/kbd)? -- 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/1165463 Title: Unity crashed - no window options, no keyboard - unity disappeared Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: I lost use of my keyboard, sorry! Anyways, unity's window manager top bars of the windows, the panel at the top and the side panel all disappeared. I was unable to use the keyboard, but I could use my mouse to copy information and paste it. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 6.12.0daily13.04.01-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5 Uname: Linux 3.8.0-16-generic i686 ApportVersion: 2.9.2-0ubuntu5 Architecture: i386 CasperVersion: 1.330 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sat Apr 6 12:54:50 2013 LiveMediaBuild: Ubuntu 13.04 Raring Ringtail - Alpha i386 (20130402.1) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set 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/1165463/+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 1342208] Re: Scroll wheel uses inverted logic to switch between applications/windows in the switcher
** Also affects: nux (Ubuntu) Importance: Undecided Status: New ** Changed in: nux (Ubuntu) Status: New = Fix Committed ** Changed in: nux (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1342208 Title: Scroll wheel uses inverted logic to switch between applications/windows in the switcher Status in Nux: Fix Committed Status in Nux trusty series: In Progress Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in “nux” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: [Impact] Scrolling on the Alt+Tab has invalid behavior: - Scrolling down, moves to the previous icon/window - Scrolling up, moves to the next icon/window - Scrolling left, moves to the next icon/window - Scrolling right, moves to the previous icon/window [Test case] 1. Press Alt+Tab 2. While pressing the keys, use mouse scroll wheel to scroll vertically (and, if possible, horizontally) Expected behavior: - Scrolling down, moves to the next icon/window - Scrolling up, moves to the previous icon/window - Scrolling left, moves to the previous icon/window - Scrolling right, moves to the next icon/window [Regression potential] Vertical scrolling has not been touched by the change, so there's no possibility to regress in this sense. To manage notifications about this bug go to: https://bugs.launchpad.net/nux/+bug/1342208/+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 1165463] Re: Unity crashed - no window options, no keyboard - unity disappeared
Forget it, if there's an (almost) invisible window (e.g. 1x1 pixel window size), one has to figure out which it might be and kill it in the tty console with `kill` (or `pkill` if you want), then a terminal can be opened with kbdCtrl/kbd+kbdAlt/kbd+kbdt/kbd. -- 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/1165463 Title: Unity crashed - no window options, no keyboard - unity disappeared Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: I lost use of my keyboard, sorry! Anyways, unity's window manager top bars of the windows, the panel at the top and the side panel all disappeared. I was unable to use the keyboard, but I could use my mouse to copy information and paste it. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 6.12.0daily13.04.01-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5 Uname: Linux 3.8.0-16-generic i686 ApportVersion: 2.9.2-0ubuntu5 Architecture: i386 CasperVersion: 1.330 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sat Apr 6 12:54:50 2013 LiveMediaBuild: Ubuntu 13.04 Raring Ringtail - Alpha i386 (20130402.1) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set 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/1165463/+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 1300915] Re: bluetooth pairing does not require a pin
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-bluetooth (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1300915 Title: bluetooth pairing does not require a pin Status in “indicator-bluetooth” package in Ubuntu: Confirmed Bug description: click on bluetooth desktop applet, turn on visible on nexus 4 go to settings bluetooth click on ubuntu-0 under available devices pairing succeeds without asking for a pin or authentication from Ubuntu! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-bluetooth 0.0.6+14.04.20140207-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 1 18:41:07 2014 InstallationDate: Installed on 2014-03-27 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) SourcePackage: indicator-bluetooth UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1300915/+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 1300915] Re: bluetooth pairing does not require a pin
I've noticed the same with Ubuntu 14.04. I discovered it because my neighbor's mobile device name suddenly appeared in my network applet. Tested it with my own Android mobile and tablet (all running standard Android). Ubuntu is running on my Lenovo E530c. Also when I run the Ubuntu 14.04 live cd (from USB). I'm able to connect without requiring a pin to pair the devices. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1300915 Title: bluetooth pairing does not require a pin Status in “indicator-bluetooth” package in Ubuntu: Confirmed Bug description: click on bluetooth desktop applet, turn on visible on nexus 4 go to settings bluetooth click on ubuntu-0 under available devices pairing succeeds without asking for a pin or authentication from Ubuntu! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-bluetooth 0.0.6+14.04.20140207-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 1 18:41:07 2014 InstallationDate: Installed on 2014-03-27 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) SourcePackage: indicator-bluetooth UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1300915/+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 1370215] [NEW] unity menu scrolls itself up from time to time
You have been subscribed to a public bug: I had big trouble to describe it, and the problem bothers me so much that guided by the motto a picture is worth thousand words I decided to record a video that shows it: https://www.youtube.com/watch?v=UkWYYbYu2FY In other words sometimes when I hover an icon, then menu instead of stopping on this icon scrolls itself up instead. Note that I do not have two monitors so my cursor does not go beyond the edge of the monitor. moreover, this happens only sometimes. Description:Ubuntu 14.04.1 LTS Release:14.04 unity 7.2.2+14.04.20140714-0ubuntu1.1 ** Affects: unity (Ubuntu) Importance: Undecided Status: New -- unity menu scrolls itself up from time to time https://bugs.launchpad.net/bugs/1370215 You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. -- 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 1370215] Re: unity menu scrolls itself up from time to time
** Package changed: ubuntu = unity (Ubuntu) -- 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/1370215 Title: unity menu scrolls itself up from time to time Status in “unity” package in Ubuntu: New Bug description: I had big trouble to describe it, and the problem bothers me so much that guided by the motto a picture is worth thousand words I decided to record a video that shows it: https://www.youtube.com/watch?v=UkWYYbYu2FY In other words sometimes when I hover an icon, then menu instead of stopping on this icon scrolls itself up instead. Note that I do not have two monitors so my cursor does not go beyond the edge of the monitor. moreover, this happens only sometimes. Description: Ubuntu 14.04.1 LTS Release: 14.04 unity 7.2.2+14.04.20140714-0ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1370215/+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 1280759] Re: Unity shortcuts (Super+A/F/M/C/V) do not work on non-latin layout in Trusty - shortcuts are defined via keyboard layout, not the keys
I experienced the following issue, I think It's related to the same bug. I have two keyboard layouts: English and Aabic (Azerty). I typed a text in the search box on Firefox then tried to select it with CTRL+A shortcut. With Arabic layout activated this had caused Firefox to close. In the other hand, when English layout is activated this had behaved normally (selecting all the text in the box). I switched back to Cinnamon because of this issue. User experience in Unity become very complicated when using a non latin layout with a latin one. -- 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/1280759 Title: Unity shortcuts (Super+A/F/M/C/V) do not work on non-latin layout in Trusty - shortcuts are defined via keyboard layout, not the keys Status in Unity: Triaged Status in Unity Settings Daemon: Confirmed Status in “unity” package in Ubuntu: Triaged Bug description: There are shortcuts to open lenses in Unity, for example Super + A for App Lens, or Super + F for Files Lens, etc. There are also shortcuts in the Launcher Super + 1 to 9 to launch apps from the Launcher. These shortcuts don't work if the keyboard layout is set to a non-Latin layout, in my case Persian, where almost all the keys are mapped to new characters. HOW TO REPRODUCE: Add a new Persian keyboard layout to the system, in addition to English, via keyboard layout indicator -- Text Entry Settings. Switch to the Persian layout (by clicking on the keyboard layout indicator). Press Super + F. WHAT HAPPENS: Dash is not open. Nothing happens. WHAT SHOULD HEPPEN: The Files Lens in the dash should open. The shortcuts should be associated with the keys on the keyboard, not to the characters they are associated with (which depends on the active keyboard layout). When I am typing something in Persian, and I want to search for a file, it is not reasonable that I should first switch back to the English layout before I can use a particular shortcut. This problem does not happen in some other apps like gedit or Firefox. COMPARE TO GEDIT: Open gedit text editor. Write something. Switch to the Persian layout. Press Ctrl + S (the shortcut to save the document). WHAT HAPPENS, AND WHAT SHOULD HAPPEN: The save dialoge box appears. I think this problem happens for all keyboard layouts that don't use Latin characters. Layout-wise, when I press Ctrl + S while Persian layout is active, I am typing Ctrl + س. But keyboard-wise, I am always pressing the same keyboard binding. -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libunity9 7.1.4+14.04.20140210-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 ApportVersion: 2.13.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 16 12:04:10 2014 InstallationDate: Installed on 2014-02-15 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140211) SourcePackage: libunity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1280759/+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 1353379] Re: VoiceMail notification pretends there are 255 messages. It is not true there are only 2
As I'd mentioned before, there are numerous methods of indicating voice- mail waiting message counts. It appears that some of these methods work, and some don't. It seems we have more investigation needed. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-messages in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1353379 Title: VoiceMail notification pretends there are 255 messages. It is not true there are only 2 Status in “indicator-messages” package in Ubuntu: Invalid Status in “ofono” package in Ubuntu: Triaged Bug description: Mako build #175 The VoiceMail notification indicates there are 255 voice messages (cf screenshot) on voice mail while there were only 2 new messages. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: indicator-messages 13.10.1+14.10.20140725-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.5-0ubuntu3 Architecture: armhf Date: Wed Aug 6 11:57:43 2014 InstallationDate: Installed on 2014-08-06 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140806-020204) SourcePackage: indicator-messages UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1353379/+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 1353379] Re: VoiceMail notification pretends there are 255 messages. It is not true there are only 2
Just tested RTM #39 on mako with ATT SIM. As screenshot shows, the indicator shows two waiting messages. ** Attachment added: lp1353379-mako.png https://bugs.launchpad.net/ubuntu/+source/ofono/+bug/1353379/+attachment/4208249/+files/lp1353379-mako.png -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-messages in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1353379 Title: VoiceMail notification pretends there are 255 messages. It is not true there are only 2 Status in “indicator-messages” package in Ubuntu: Invalid Status in “ofono” package in Ubuntu: Triaged Bug description: Mako build #175 The VoiceMail notification indicates there are 255 voice messages (cf screenshot) on voice mail while there were only 2 new messages. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: indicator-messages 13.10.1+14.10.20140725-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.5-0ubuntu3 Architecture: armhf Date: Wed Aug 6 11:57:43 2014 InstallationDate: Installed on 2014-08-06 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140806-020204) SourcePackage: indicator-messages UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1353379/+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 1353379] Re: VoiceMail notification pretends there are 255 messages. It is not true there are only 2
Also tested RTM #44 with krillin, and I get a different result yet again. This time the indicator just states VoiceMail Messages with no count. This is using a single T-Mobile pre-paid SIM in slot #1. ** Attachment added: lp1353379-krillin.png https://bugs.launchpad.net/ubuntu/+source/ofono/+bug/1353379/+attachment/4208250/+files/lp1353379-krillin.png -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-messages in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1353379 Title: VoiceMail notification pretends there are 255 messages. It is not true there are only 2 Status in “indicator-messages” package in Ubuntu: Invalid Status in “ofono” package in Ubuntu: Triaged Bug description: Mako build #175 The VoiceMail notification indicates there are 255 voice messages (cf screenshot) on voice mail while there were only 2 new messages. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: indicator-messages 13.10.1+14.10.20140725-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.5-0ubuntu3 Architecture: armhf Date: Wed Aug 6 11:57:43 2014 InstallationDate: Installed on 2014-08-06 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140806-020204) SourcePackage: indicator-messages UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1353379/+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 1272686] Re: indicator-bluetooth-service crashed with SIGSEGV in org_bluez_adapter_set_property()
I also got this bug manifest itself when my BT controller stopped working for some reason (another bug?) lsusb -s 024 -v Bus 001 Device 024: ID 13d3:3362 IMC Networks Couldn't open device, some information will be missing Asus notebook model N76V, internal USB adapter -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1272686 Title: indicator-bluetooth-service crashed with SIGSEGV in org_bluez_adapter_set_property() Status in “indicator-bluetooth” package in Ubuntu: Triaged Bug description: After activating bluetooth. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: indicator-bluetooth 0.0.6+14.04.20140124-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-1.16-generic 3.13.0-rc7 Uname: Linux 3.13.0-1-generic x86_64 ApportVersion: 2.13.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jan 25 15:02:43 2014 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-bluetooth/indicator-bluetooth-service InstallationDate: Installed on 2013-12-10 (45 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64+mac (20131210) ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-bluetooth/indicator-bluetooth-service SegvAnalysis: Segfault happened at: 0x40d880: mov(%rbx),%rdi PC (0x0040d880) ok source (%rbx) (0x) not located in a known VMA region (needed readable region)! destination %rdi ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: indicator-bluetooth StacktraceTop: ?? () ?? () ?? () g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: indicator-bluetooth-service crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1272686/+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 1353379] Re: VoiceMail notification pretends there are 255 messages. It is not true there are only 2
I recommend to check the behaviour in reference phone with those SIM cards. I would not be surprised if T-Mobile for example just does not update the count. Also it would be interesting to know what was your exact test sequence. Did you see the lp1353379-krillin.png run time or after restarting ofono? If you did it see it run-time, did the message count change after restarting the ofono? -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-messages in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1353379 Title: VoiceMail notification pretends there are 255 messages. It is not true there are only 2 Status in “indicator-messages” package in Ubuntu: Invalid Status in “ofono” package in Ubuntu: Triaged Bug description: Mako build #175 The VoiceMail notification indicates there are 255 voice messages (cf screenshot) on voice mail while there were only 2 new messages. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: indicator-messages 13.10.1+14.10.20140725-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.5-0ubuntu3 Architecture: armhf Date: Wed Aug 6 11:57:43 2014 InstallationDate: Installed on 2014-08-06 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140806-020204) SourcePackage: indicator-messages UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1353379/+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
