[Dx-packages] [Bug 1298656] Re: hud-service crashed with g-assert-if-reached in GMenu call from qtgmenu::QtGMenuModel::CreateChild()
** Branch unlinked: lp:~unity-api-team/hud/lp-1298656 -- 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/1298656 Title: hud-service crashed with g-assert-if-reached in GMenu call from qtgmenu::QtGMenuModel::CreateChild() Status in “hud” package in Ubuntu: In Progress Bug description: Don't think I did anything special. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: hud 13.10.1+14.04.20140326-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Thu Mar 27 22:37:06 2014 ExecutablePath: /usr/lib/x86_64-linux-gnu/hud/hud-service InstallationDate: Installed on 2013-09-29 (179 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64+mac (20130925.1) ProcCmdline: /usr/lib/x86_64-linux-gnu/hud/hud-service Signal: 6 SourcePackage: hud StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () ?? () Title: hud-service crashed with SIGABRT in g_assertion_message() UpgradeStatus: Upgraded to trusty on 2014-03-15 (12 days ago) UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sudo upstart.hud.log: (hud-service:1836): GLib-CRITICAL **: g_sequence_get: assertion '!is_end (iter)' failed (hud-service:1836): GLib-GIO-CRITICAL **: g_dbus_menu_model_get_item_links: assertion 'item' failed ** GLib-GIO:ERROR:/build/buildd/glib2.0-2.39.92/./gio/gmenumodel.c:398:g_menu_model_real_get_item_link: code should not be reached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1298656/+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 1307520] Re: [UX] Can't Change Menu when Submenu Opened by Right-Arrow
Thanks for this perceptive report, Hernawan. You're correct that Right arrow should navigate to the next top-level menu whenever a submenu title isn't highlighted. I verified this in Internet Explorer 9 on Windows 7 SP1, and in OS X 10.7. This might be a GTK bug, rather than an indicator-appmenu bug. ** Changed in: indicator-appmenu (Ubuntu) Status: New = Confirmed ** Description changed: - Description: Ubuntu 13.10 - Release: 13.10 + Problem occurs with: Ubuntu 13.10, Ubuntu 14.04 beta + Does not occur with: Windows 7 SP1, OS X 10.7 - In this report, I choose firefox-28.0 as model. But, It is a ubuntu - global menu bug, not only app specified. - - Reproduce - --- - 1. Open any application with multiple menu and at least one submenu. + 1. Open any application with multiple menus and at least one submenu. (e.g. firefox with File, Edit, View - Toolbar - Customize..., Help) 2. Navigate to View menu. 3. Press down-arrow (so, the 'Toolbars' menu selected). 4. Press right-arrow to open submenu of 'Toolbars'. 5. Press right-arrow again to open next menu. Expected - History menu opened! - Occured + Occurred - It is still open View - Toolbars submenu and stand still. - - I have search in launchpad but not found any. Notice me if it is - duplicated and also if the above info is not enough. - - Thanks. + The View - Toolbars submenu remains opens. -- 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/1307520 Title: [UX] Can't Change Menu when Submenu Opened by Right-Arrow Status in “indicator-appmenu” package in Ubuntu: Confirmed Bug description: Problem occurs with: Ubuntu 13.10, Ubuntu 14.04 beta Does not occur with: Windows 7 SP1, OS X 10.7 1. Open any application with multiple menus and at least one submenu. (e.g. firefox with File, Edit, View - Toolbar - Customize..., Help) 2. Navigate to View menu. 3. Press down-arrow (so, the 'Toolbars' menu selected). 4. Press right-arrow to open submenu of 'Toolbars'. 5. Press right-arrow again to open next menu. Expected - History menu opened! Occurred The View - Toolbars submenu remains opens. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-appmenu/+bug/1307520/+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 1289689] Re: Launcher icons don't work when option is set to only show launcher on one monitor.
*** This bug is a duplicate of bug 1303325 *** https://bugs.launchpad.net/bugs/1303325 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/1289689 Title: Launcher icons don't work when option is set to only show launcher on one monitor. Status in “unity” package in Ubuntu: Confirmed Bug description: In Ubuntu 14.04 beta when the launcher is set to only show on one monitor if you open an application from the menu it opens, but if you close it and try to open it again nothing happens when you click the icon. The way it behaves it's like you're clicking an empty space, the right click menu still works and if you show the launcher on both monitors it also works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1289689/+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 1303325] Re: clicking on its launcher icon doesn't open it (occured after closing app before)
Confirming this bug to. Also latest updates won't fixed the issue. Very annoying, please fix asap if it's not too complicated With best regards, Vitaliy, System administrator of SoftTechnics, Odessa Ukraine -- 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/1303325 Title: clicking on its launcher icon doesn't open it (occured after closing app before) Status in “unity” package in Ubuntu: Confirmed Bug description: steps to reproduce: 1. open any apps from launcher (gedit for example) by clicking gedit icon with left mouse button (LMB) 2. close this apps (gedit) 3. try to open gedit again by clicking LMB - !!gedit doesn't open again!! (not shake, nothing to happens) NOTE: if i clicking RIGHT mouse button, I can open gedit from context menu open a new window ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140403-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 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_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-17ubuntu2) .tmp.unity.support.test.0: ApportVersion: 2.14.1-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: Sun Apr 6 15:54:21 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GF114 [GeForce GTX 560] [10de:1201] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:83b5] InstallationDate: Installed on 2014-03-17 (19 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140316) MachineType: System manufacturer Rampage Extreme ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-19-generic root=UUID=035868ff-323c-42a4-80bf-43c3eb7f719d ro quiet splash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: Rampage Extreme dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 2.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0301:bd07/08/2008:svnSystemmanufacturer:pnRampageExtreme:pvrSystemVersion:rvnASUSTeKComputerINC.:rnRampageExtreme:rvrRev2.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: Rampage Extreme dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sun Apr 6 15:38:37 2014 xserver.configfile: /etc/X11/xorg.conf xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech Unifying Device. Wireless PID:101a MOUSE, id 8 inputLogitech Unifying Device. Wireless PID:4003 KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.0-1ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1303325/+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 1221783] Re: turning off bluetooth kills the applet
*** This bug is a duplicate of bug 1126108 *** https://bugs.launchpad.net/bugs/1126108 This will help: start console. sudo modprobe btusb reset=1 sudo rfkill unblock all I greet all zVID -- 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/1221783 Title: turning off bluetooth kills the applet Status in “indicator-bluetooth” package in Ubuntu: Confirmed Bug description: Steps to repro: 1. Boot from cold boot 2. Right click the Bluetooth applet 3. Uncheck the bluetooth option to turn off bluetooth 4. Applet disappears from the top bar 5. Open Systems Preferences 6. Select Bluetooth 7. Toggle the on/off switch. Button reflashes and reverts to off position and the following is displayed in /var/log/syslog Sep 6 11:12:07 x1 kernel: [ 1528.999488] usb 1-1.4: new full-speed USB device number 8 using ehci-pci Sep 6 11:12:07 x1 kernel: [ 1529.096809] usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=21e6 Sep 6 11:12:07 x1 kernel: [ 1529.096822] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Sep 6 11:12:07 x1 kernel: [ 1529.096828] usb 1-1.4: Product: BCM20702A0 Sep 6 11:12:07 x1 kernel: [ 1529.096833] usb 1-1.4: Manufacturer: Broadcom Corp Sep 6 11:12:07 x1 kernel: [ 1529.096839] usb 1-1.4: SerialNumber: 2016D8D72EBD Sep 6 11:12:07 x1 mtp-probe: checking bus 1, device 8: /sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.4 Sep 6 11:12:07 x1 mtp-probe: bus: 1, device: 8 was not an MTP device Sep 6 11:12:07 x1 bluetoothd[477]: Unknown command complete for opcode 19 Sep 6 11:12:07 x1 bluetoothd[477]: Endpoint registered: sender=:1.55 path=/MediaEndpoint/HFPAG Sep 6 11:12:07 x1 bluetoothd[477]: Endpoint registered: sender=:1.55 path=/MediaEndpoint/HFPHS Sep 6 11:12:07 x1 bluetoothd[477]: Endpoint registered: sender=:1.55 path=/MediaEndpoint/A2DPSource Sep 6 11:12:07 x1 bluetoothd[477]: Endpoint registered: sender=:1.55 path=/MediaEndpoint/A2DPSink Sep 6 11:12:07 x1 kernel: [ 1529.399061] usb 1-1.4: USB disconnect, device number 8 Sep 6 11:12:07 x1 bluetoothd[477]: Unregister path: /org/bluez/477/hci0 Sep 6 11:12:07 x1 bluetoothd[477]: Endpoint unregistered: sender=:1.55 path=/MediaEndpoint/A2DPSink Sep 6 11:12:07 x1 bluetoothd[477]: Endpoint unregistered: sender=:1.55 path=/MediaEndpoint/A2DPSource Sep 6 11:12:07 x1 bluetoothd[477]: Endpoint unregistered: sender=:1.55 path=/MediaEndpoint/HFPAG Sep 6 11:12:07 x1 bluetoothd[477]: Endpoint unregistered: sender=:1.55 path=/MediaEndpoint/HFPHS ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-bluetooth 0.0.6+13.10.20130823-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Uname: Linux 3.11.0-4-generic x86_64 ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Fri Sep 6 11:08:48 2013 InstallationDate: Installed on 2013-08-09 (27 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130809) MarkForUpload: True 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/1221783/+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 1268047] Re: Can't make bluetooth visible for reverse connection on phone
** No longer affects: ubuntu-ux ** No longer affects: indicator-bluetooth (Ubuntu) ** Changed in: ubuntu-system-settings (Ubuntu) Status: Confirmed = In Progress -- 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/1268047 Title: Can't make bluetooth visible for reverse connection on phone Status in “ubuntu-system-settings” package in Ubuntu: In Progress Bug description: My hands-free system works the reverse way in that the phone needs to be made visible for the car to connect to it, which is currently impossible with the Bluetooth panel. This probably affects indicator-bluetooth, too. Adding ubuntu-ux as well, since https://wiki.ubuntu.com/Bluetooth#Phone does not seem to cater for the reverse use case on the phone. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubuntu-system-settings 0.1+14.04.20140109.2-0ubuntu1 Uname: Linux 3.4.0-3-mako armv7l ApportVersion: 2.12.7-0ubuntu6 Architecture: armhf Date: Fri Jan 10 23:49:07 2014 InstallationDate: Installed on 2014-01-10 (0 days ago) InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140110) SourcePackage: ubuntu-system-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1268047/+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 1289470] Re: The phone has three brightness sliders
Specification updated. https://wiki.ubuntu.com/Power#Phone_and_tablet As agreed with Shruti Kapur, the battery menu should no longer contain a brightness slider. It's possible that a brightness slider may return in a future indicator design, and in that case we'd have to tackle the System Settings side. ** Changed in: indicator-power (Ubuntu) Status: New = In Progress ** Changed in: indicator-power (Ubuntu) Importance: Undecided = Low ** Changed in: indicator-power (Ubuntu) Status: In Progress = Triaged ** Changed in: indicator-power (Ubuntu) Assignee: Matthew Paul Thomas (mpt) = (unassigned) -- 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/1289470 Title: The phone has three brightness sliders Status in “indicator-power” package in Ubuntu: Triaged Status in “ubuntu-system-settings” package in Ubuntu: New Bug description: The current phone design has three brightness sliders that do exactly the same thing: * System Settings Brightness * System Settings Battery * the Battery menu. This is kind of ridiculous. We should get rid of one or two. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1289470/+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 1298088] Re: battery indicator is hidden when no battery is present
** Changed in: indicator-power (Ubuntu) Status: New = In Progress -- 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/1298088 Title: battery indicator is hidden when no battery is present Status in “indicator-power” package in Ubuntu: In Progress Bug description: Though there's no battery attached on my laptop but then it should have a indicator in panel that power is plug in. lsb_release -rd Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 Beta2 upower -d Device: /org/freedesktop/UPower/devices/line_power_AC native-path: AC power supply: yes updated: Thursday, 27 March, 2014 05:32:48 AM PHT (2129 seconds ago) has history: no has statistics: no line-power online: yes Daemon: daemon-version: 0.9.23 can-suspend: yes can-hibernate: no on-battery: no on-low-battery: no lid-is-closed: no lid-is-present: yes is-docked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1298088/+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 1241101] Re: Java crash in libglib-2.0 after upgrade from 13.04 to 13.10
Yes, today Eclipse crashes again, taskset does not help. :( This is really very bad, hardly reproducible bug. It seems the faster machine and newer JDK and Linux, the more occurences I have ... Maybe the fastest method to fix it is to dig into the code of GTK ...? -- 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/1241101 Title: Java crash in libglib-2.0 after upgrade from 13.04 to 13.10 Status in Eclipse: Confirmed Status in “gtk+2.0” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Invalid Status in “gtk+2.0” package in Suse: New Bug description: Running smartgit 4.6.4 on 13.10 64 bits. After registering the product, smartgit crash when trying to open a new repository. Java error log : # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7fa59061f9c0, pid=12494, tid=140349308167936 # # JRE version: 7.0_25-b30 # Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libglib-2.0.so.0+0x389c0] g_str_hash+0x0 I tried different version of Java (Oracle v7 and v6 jre) with same result. Also, Eclipse display blank menus so there's a general java problem with displays. To manage notifications about this bug go to: https://bugs.launchpad.net/eclipse/+bug/1241101/+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 1235059] Re: hud-service crashed with signal 5 in _start()
** Information type changed from Private to Public -- 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/1235059 Title: hud-service crashed with signal 5 in _start() Status in “hud” package in Ubuntu: Confirmed Bug description: In a cairo launcher session hud-service crashed on me. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: hud 13.10.1+13.10.20131002.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Thu Oct 3 22:50:54 2013 ExecutablePath: /usr/lib/x86_64-linux-gnu/hud/hud-service InstallationDate: Installed on 2013-10-04 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20131003) MarkForUpload: True ProcCmdline: /usr/lib/x86_64-linux-gnu/hud/hud-service ProcEnviron: PATH=(custom, no user) LANGUAGE=en_US XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: hud StacktraceTop: _start () Title: hud-service crashed with signal 5 in _start() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo upstart.hud.log: (process:2046): hud-service-WARNING **: SIGTERM recieved (process:2046): hud-service-ERROR **: Unable to get name 'com.canonical.hud' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1235059/+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 1282261] Re: hud-service crashed with signal 7 in Columbus::Trie::append()
** Changed in: hud (Ubuntu) Status: New = Fix Released ** Changed in: libcolumbus Status: New = Invalid -- 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/1282261 Title: hud-service crashed with signal 7 in Columbus::Trie::append() Status in Libcolumbus, a small, fast, error tolerant matcher: Invalid Status in “hud” package in Ubuntu: Fix Released Bug description: Random bug. Not aware of what caused it past heavy workload. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: hud 13.10.1+14.04.20140218.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-88.8-mptcp Uname: Linux 3.11.0-88-mptcp x86_64 NonfreeKernelModules: ufsd ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Wed Feb 19 15:39:52 2014 ExecutablePath: /usr/lib/x86_64-linux-gnu/hud/hud-service InstallationDate: Installed on 2014-02-12 (7 days ago) InstallationMedia: It ProcCmdline: /usr/lib/x86_64-linux-gnu/hud/hud-service ProcEnviron: PATH=(custom, no user) LANGUAGE=en_CA:en XDG_RUNTIME_DIR=set LANG=en_CA.UTF-8 SHELL=/bin/bash Signal: 7 SourcePackage: hud StacktraceTop: Columbus::Trie::append(char const*, int) () from /usr/lib/x86_64-linux-gnu/libcolumbus.so.1 Columbus::Trie::addNewNode(unsigned int) () from /usr/lib/x86_64-linux-gnu/libcolumbus.so.1 Columbus::Trie::addNewSibling(unsigned int, unsigned int, unsigned short) () from /usr/lib/x86_64-linux-gnu/libcolumbus.so.1 Columbus::Trie::insertWord(Columbus::Word const, unsigned int) () from /usr/lib/x86_64-linux-gnu/libcolumbus.so.1 Columbus::WordStore::getID(Columbus::Word const) () from /usr/lib/x86_64-linux-gnu/libcolumbus.so.1 Title: hud-service crashed with signal 7 in Columbus::Trie::append() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip fuse lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/libcolumbus/+bug/1282261/+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 1281227] Re: hud-service crashed with SIGSEGV with an invalid pointer reference when a bad QSharedPointer goes out of scope in hud::service::QueryImpl::updateToken()
** Changed in: hud (Ubuntu) Status: New = Fix Released -- 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/1281227 Title: hud-service crashed with SIGSEGV with an invalid pointer reference when a bad QSharedPointer goes out of scope in hud::service::QueryImpl::updateToken() Status in “hud” package in Ubuntu: Fix Released Bug description: no more icons in the tray area ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: hud 13.10.1+14.04.20140212-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 ApportVersion: 2.13.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Mon Feb 17 19:22:23 2014 ExecutablePath: /usr/lib/x86_64-linux-gnu/hud/hud-service ProcCmdline: /usr/lib/x86_64-linux-gnu/hud/hud-service SegvAnalysis: Segfault happened at: 0x43317d _ZN3hud7service9QueryImpl11updateTokenE14QSharedPointerINS0_6WindowEE+77: lock subl $0x1,0x4(%rbx) PC (0x0043317d) ok source $0x1 ok destination 0x4(%rbx) (0x00b4) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: hud StacktraceTop: hud::service::QueryImpl::updateToken(QSharedPointerhud::service::Window) () hud::service::QueryImpl::refresh() () ?? () QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 hud::service::ApplicationListImpl::FocusedWindowChanged(unsigned int, QString const, unsigned int) () Title: hud-service crashed with SIGSEGV in hud::service::QueryImpl::updateToken() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo upstart.window-stack-bridge.log: QDBusConnection: name 'org.ayatana.bamf' had owner '' but we thought it was ':1.7' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1281227/+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 1308002] [NEW] Screen quickly autolocks again after unlocking
You have been subscribed to a public bug: Yes the title sounds odd, right? So I have seen it many times and others have reported that to me as well. Mostly after resuming from suspend and entering password to unlock the screen, lightdm password screen comes to front just in a few seconds after I unlock the screen, so basically i have to enter password twice to unlock screen. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu2 Architecture: i386 CurrentDesktop: Unity Date: Tue Apr 15 16:06:48 2014 InstallationDate: Installed on 2014-02-28 (45 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140228) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty -- Screen quickly autolocks again after unlocking https://bugs.launchpad.net/bugs/1308002 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 1308005] [NEW] [regression] no way to close tall windows as they appear below top panel
Public bug reported: Its a bad regression, when I open tall windows their title bar goes below the top panel. hence making it impossible to close the window with mouse, this is a problem for novice users on which I tested 14.04 and puts a bad impression. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 15 16:04:23 2014 InstallationDate: Installed on 2014-02-28 (45 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140228) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty -- 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/1308005 Title: [regression] no way to close tall windows as they appear below top panel Status in “unity” package in Ubuntu: New Bug description: Its a bad regression, when I open tall windows their title bar goes below the top panel. hence making it impossible to close the window with mouse, this is a problem for novice users on which I tested 14.04 and puts a bad impression. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 15 16:04:23 2014 InstallationDate: Installed on 2014-02-28 (45 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140228) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1308005/+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 1276390] Re: hud-service crashed with SIGSEGV in hud::service::QueryImpl::notifyPropertyChanged (this=0x0)
** Changed in: hud (Ubuntu) Status: New = Fix Released -- 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/1276390 Title: hud-service crashed with SIGSEGV in hud::service::QueryImpl::notifyPropertyChanged (this=0x0) Status in “hud” package in Ubuntu: Fix Released Bug description: Hud crashed after I closed the Unity8 phone shell simulator ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: hud 13.10.1+14.04.20140120-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0 Uname: Linux 3.13.0-6-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Feb 4 22:42:46 2014 ExecutablePath: /usr/lib/x86_64-linux-gnu/hud/hud-service InstallationDate: Installed on 2014-01-11 (24 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140111) ProcCmdline: /usr/lib/x86_64-linux-gnu/hud/hud-service SegvAnalysis: Segfault happened at: 0x432d9d _ZN3hud7service9QueryImpl11updateTokenE14QSharedPointerINS0_6WindowEE+77: lock subl $0x1,0x4(%rbx) PC (0x00432d9d) ok source $0x1 ok destination 0x4(%rbx) (0xe9af1e177a5b2a44) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: hud StacktraceTop: hud::service::QueryImpl::updateToken(QSharedPointerhud::service::Window) () hud::service::QueryImpl::refresh() () ?? () QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 hud::service::ApplicationListImpl::FocusedWindowChanged(unsigned int, QString const, unsigned int) () Title: hud-service crashed with SIGSEGV in hud::service::QueryImpl::updateToken() 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/hud/+bug/1276390/+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 1306368] Re: Consumed 100% CPU time, on one code and 270MB memory, for ~23hours
*** This bug is a duplicate of bug 1300722 *** https://bugs.launchpad.net/bugs/1300722 ** This bug has been marked a duplicate of bug 1300722 hud-service is eating up 100% of one of my CPUs in a poll loop -- 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/1306368 Title: Consumed 100% CPU time, on one code and 270MB memory, for ~23hours Status in “hud” package in Ubuntu: New Bug description: Subject says all. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: hud 13.10.1+14.04.20140402-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 CurrentDesktop: Unity Date: Thu Apr 10 21:13:44 2014 ExecutablePath: /usr/lib/x86_64-linux-gnu/hud/hud-service InstallationDate: Installed on 2013-04-02 (373 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130402) SourcePackage: hud UpgradeStatus: Upgraded to trusty on 2014-04-07 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1306368/+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 1283775] Re: Launcher: icon pips are not always updated properly
Also pips update properly when you open new windows in Spread Mode or Expo Mode (Super + S). -- 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/1283775 Title: Launcher: icon pips are not always updated properly Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: Only occurs when there is just 1 app's windows (unmaxed), assumes multiple workspaces is enabled Test case: Open nautilus (1 pip shows up R. click nautilus icon open another nautilus window (a 2nd pip does not show, likely due to Bug 1281816 Drag the 2nd naut window fully into current ws, 2nd pip still not shown Click on Desktop, 2nd pip shows up Close one of the naut windows, icon still shows 2 pips. Click again on Desktop, 2nd pip is then removed ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140220-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sun Feb 23 12:28:18 2014 InstallationDate: Installed on 2014-02-22 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140222) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1283775/+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 1283775] Re: Launcher: icon pips are not always updated properly
I would add that if for example I have opened Terminal and Nautilus and the focus is on Nautilus opening new Terminal with Ctrl+Alt+T shortcut or by right clicking on icon will result in pips updated properly. Pips will not update if I open another window for the app that I have in focus. For example I have Terminal window in focus and in the background maximized Chrome window and Nautilus then I open second and third Terminal window but launcher still displays one pip. Changing focus to another window or other interaction with environment will update pips. -- 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/1283775 Title: Launcher: icon pips are not always updated properly Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: Only occurs when there is just 1 app's windows (unmaxed), assumes multiple workspaces is enabled Test case: Open nautilus (1 pip shows up R. click nautilus icon open another nautilus window (a 2nd pip does not show, likely due to Bug 1281816 Drag the 2nd naut window fully into current ws, 2nd pip still not shown Click on Desktop, 2nd pip shows up Close one of the naut windows, icon still shows 2 pips. Click again on Desktop, 2nd pip is then removed ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140220-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sun Feb 23 12:28:18 2014 InstallationDate: Installed on 2014-02-22 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140222) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1283775/+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 1308002] Re: Screen quickly autolocks again after unlocking
** Package changed: lightdm (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/1308002 Title: Screen quickly autolocks again after unlocking Status in “unity” package in Ubuntu: New Bug description: Yes the title sounds odd, right? So I have seen it many times and others have reported that to me as well. Mostly after resuming from suspend and entering password to unlock the screen, lightdm password screen comes to front just in a few seconds after I unlock the screen, so basically i have to enter password twice to unlock screen. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu2 Architecture: i386 CurrentDesktop: Unity Date: Tue Apr 15 16:06:48 2014 InstallationDate: Installed on 2014-02-28 (45 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140228) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1308002/+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 1241101]
EDIT: workaround does not help. And one more note: Eclipse crashes earlier when showing variables in debug mode. -- 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/1241101 Title: Java crash in libglib-2.0 after upgrade from 13.04 to 13.10 Status in Eclipse: Confirmed Status in “gtk+2.0” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Invalid Status in “gtk+2.0” package in Suse: New Bug description: Running smartgit 4.6.4 on 13.10 64 bits. After registering the product, smartgit crash when trying to open a new repository. Java error log : # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7fa59061f9c0, pid=12494, tid=140349308167936 # # JRE version: 7.0_25-b30 # Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libglib-2.0.so.0+0x389c0] g_str_hash+0x0 I tried different version of Java (Oracle v7 and v6 jre) with same result. Also, Eclipse display blank menus so there's a general java problem with displays. To manage notifications about this bug go to: https://bugs.launchpad.net/eclipse/+bug/1241101/+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 1298088] Re: battery indicator is hidden when no battery is present
Specification updated. https://wiki.ubuntu.com/Power?action=diffrev2=65rev1=64 ** Changed in: indicator-power (Ubuntu) Status: In Progress = Triaged ** Changed in: indicator-power (Ubuntu) Assignee: Matthew Paul Thomas (mpt) = Charles Kerr (charlesk) ** Description changed: + Ubuntu Trusty Tahr (14.04 Beta2) + Though there's no battery attached on my laptop but then it should have a indicator in panel that power is plug in. - lsb_release -rd - - Description: Ubuntu Trusty Tahr (development branch) - Release: 14.04 Beta2 - - upower -d - Device: /org/freedesktop/UPower/devices/line_power_AC - native-path: AC - power supply: yes - updated: Thursday, 27 March, 2014 05:32:48 AM PHT (2129 seconds ago) - has history: no - has statistics: no - line-power - online: yes - - Daemon: - daemon-version: 0.9.23 - can-suspend: yes - can-hibernate: no - on-battery: no - on-low-battery: no - lid-is-closed: no - lid-is-present: yes - is-docked: no + https://wiki.ubuntu.com/Power#Settings: The “Show status in the menu + bar:” menu should have options “When a battery or chargeable device is + present”, “When something is charging or discharging”, and “Never”. -- 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/1298088 Title: battery indicator is hidden when no battery is present Status in “indicator-power” package in Ubuntu: Triaged Bug description: Ubuntu Trusty Tahr (14.04 Beta2) Though there's no battery attached on my laptop but then it should have a indicator in panel that power is plug in. https://wiki.ubuntu.com/Power#Settings: The “Show status in the menu bar:” menu should have options “When a battery or chargeable device is present”, “When something is charging or discharging”, and “Never”. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1298088/+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 1291461] Re: Lockscreen: keyboard layout switching shortcuts not working
The fix we had before was very rudimentary... it basically just compared the keysyms directly. The related branch above should allow switching with modifier-only shortcuts too now. ** Branch linked: lp:~attente/unity/1291461 -- 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/1291461 Title: Lockscreen: keyboard layout switching shortcuts not working Status in Unity: In Progress Status in “unity” package in Ubuntu: Fix Released Bug description: New Unity Lockscreen has the same problem as the old one from Gnome: the chosen keyboard shortcut is not switching keyboard layouts on it, the only way is to use mouse. Steps to reproduce: 1. To make things uncomfortable, switch layout to Russian or any other with your favourite shortcut(i am using alt-shift) 2. Lock the screen with ctrl-alt-l 3. Try to change layout back to English to enter password Expected: Layput should change and you should be able to login without touching anything but keyboard. What's happening: Nothing, doesn't react on the keyboard shortcut, you have to change layout using indicator on top panel. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1291461/+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 1308002] Re: Screen quickly autolocks again after unlocking
** Changed in: unity (Ubuntu) Importance: Undecided = Medium ** Also affects: unity Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1308002 Title: Screen quickly autolocks again after unlocking Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: Yes the title sounds odd, right? So I have seen it many times and others have reported that to me as well. Mostly after resuming from suspend and entering password to unlock the screen, lightdm password screen comes to front just in a few seconds after I unlock the screen, so basically i have to enter password twice to unlock screen. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu2 Architecture: i386 CurrentDesktop: Unity Date: Tue Apr 15 16:06:48 2014 InstallationDate: Installed on 2014-02-28 (45 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140228) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1308002/+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 1012204] Re: Is not clear enough when an application has information or not
Unfortunately, I share the exact same view as you do. Unfortunately x2, it's even more of a headache in 14.04. It seems as if the icons were switched to SVG to allow for better scaling on HiDPI screens, but at the expense of the pips being much smaller than before and the highlights of the icons being almost identical from their idle state. I reported my own bug report and haven't had that much activity on it, granted it's still a young report, although it's been listed as 'low importance', which of course given the fact there's little/no way to decipher an icon's status, this has me a little concerned to say the very least. Still crossing my fingers there... Here are some examples in 14.04 with Skype in particular: http://oi62.tinypic.com/nxjgh3.jpg http://oi59.tinypic.com/21mi1w0.jpg From bug report: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1304073 See how there's literally no difference? It's such a minor difference it's difficult to see even when you're actively watching the icon switch back and forth, let alone having to look at an icon when you get back to your computer to quickly see does this application need attention? As it stands now, it's clearly a broken feature as it's pretty much impossible to tell the difference. Hopeful that there's a quick resolution. I'd certainly hate to see the next LTS be stuck with something like this throughout its cycle. -- 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/1012204 Title: Is not clear enough when an application has information or not Status in Ayatana Design: New Status in Unity: Incomplete Status in “unity” package in Ubuntu: Incomplete Bug description: The difference of colour between the two states of the arrow on the left of a Launcher tile is not big enough. The colour of the default state is grey, not white. When a message is received, instead, the colour is light blue. With Skype, probably because of an optical illusion, the left arrow when in default state seems already slightly tint of blue, looks almost if there might be a message left by someone. Possible solutions: 1) Drop the colour on the Launcher arrows (pips) 2) Use a more different colour To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1012204/+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 1307890] Re: virt-manager starts with title bar behind menu bar
I see this too, the titlebar gets consistently placed behind the top menu. Not sure if it's unity or compiz, but I suspect the problem is in one of those. ** Also affects: unity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1307890 Title: virt-manager starts with title bar behind menu bar Status in “unity” package in Ubuntu: New Status in “virt-manager” package in Ubuntu: New Bug description: Virtual MAchine Manager always starts with it's title bar behind the menu bar, I always have to Alt + Click the window to drag it out of there, a bit annoying :) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: virt-manager 0.9.5-1ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 15 09:59:59 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-03-30 (15 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) PackageArchitecture: all SourcePackage: virt-manager UpgradeStatus: Upgraded to trusty on 2014-03-30 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1307890/+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 1308037] [NEW] No results from application lens
Public bug reported: Unity is in a state where I don't get any results from the applications lens. This sometimes happens for one search but either re-entering the search or toggling the lens has always fixed it in the past for me. This time neither of these steps work. I'm attaching a bustle log of the problem in case that's helpful. I searched for spotify, which I've got installed, and got 0 results. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 15 13:29:40 2014 InstallationDate: Installed on 2012-10-07 (554 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121007) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-05-07 (343 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty ** Attachment added: 2014-04-15 13:17:12.bustle https://bugs.launchpad.net/bugs/1308037/+attachment/4084375/+files/2014-04-15%2013%3A17%3A12.bustle -- 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/1308037 Title: No results from application lens Status in “unity” package in Ubuntu: New Bug description: Unity is in a state where I don't get any results from the applications lens. This sometimes happens for one search but either re-entering the search or toggling the lens has always fixed it in the past for me. This time neither of these steps work. I'm attaching a bustle log of the problem in case that's helpful. I searched for spotify, which I've got installed, and got 0 results. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 15 13:29:40 2014 InstallationDate: Installed on 2012-10-07 (554 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121007) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-05-07 (343 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1308037/+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 1302930] Re: Every message gets new list item on empathy indicator
** Branch linked: lp:~larsu/telepathy-indicator/lp1302930 ** Changed in: indicator-messages (Ubuntu) Status: Confirmed = In Progress ** Changed in: indicator-messages (Ubuntu) Assignee: (unassigned) = Lars Uebernickel (larsu) -- 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/1302930 Title: Every message gets new list item on empathy indicator Status in “indicator-messages” package in Ubuntu: In Progress Bug description: In messaging indicator i see every message as a separate item, even with same person. So i have many notifications with same persons. Also opening empathy doesn't remove item from list. Only clicking on indicator element. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1302930/+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 1307657] Re: UBUNTU_MENUPROXY should not be set in Xfce
Thanks Ted, merge proposed what you suggested for the short-term. ** Branch linked: lp:~attente/unity-gtk-module/1307657 -- 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/1307657 Title: UBUNTU_MENUPROXY should not be set in Xfce Status in “unity-gtk-module” package in Ubuntu: Confirmed Bug description: To reproduce: either start with a fresh Ubuntu install and then install xubuntu-desktop, or start with Xubuntu and then install ubuntu-desktop - ie have both Xfce and Unity installed on the same machine. Xfce now has support for gtk3 indicators launched by upstart, but indicator-appmenu is totally broken - it will constantly crash the panel and applications. Xfce has a mechanism to hide indicators, and then the frontend UI will not be loaded in the panel, but it seems that UBUNTU_MENUPROXY is still being set in Xfce, which causes menus to disappear from applications, even though nothing is available to receive them. I discussed this with tedg and he suggested that the problem may be to do with the upstart service which sets UBUNTU_MENUPROXY, ie /usr/share/upstart/sessions/unity-gtk-module.conf We may in future get the appmenus working in Xfce, and then we would need some way to turn the menuproxy on and off depending on the user configuration. But for now, since they are broken anyway, it would be easiest to simply blacklist xubuntu desktop completely. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-gtk-module-common 0.0.0+14.04.20140403-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Apr 14 19:40:36 2014 InstallationDate: Installed on 2014-02-11 (61 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140210) PackageArchitecture: all SourcePackage: unity-gtk-module UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-gtk-module/+bug/1307657/+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 1296431] Re: Phone doesn't alert user of critical power situations
** Changed in: indicator-power (Ubuntu) Status: Confirmed = In Progress -- 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/1296431 Title: Phone doesn't alert user of critical power situations Status in “indicator-power” package in Ubuntu: In Progress Bug description: The phone doesn't currently alert the user when the battery is critical. This leads to power loss at times and the user doesn't know it's about to happen or had happened. e.g. during a call, or while listening to music. Also if the phone is sat on the desk unplugged from power connection. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1296431/+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 1308055] [NEW] Shell Experience Seems a Little Jerky on Nexus 4
Public bug reported: I noticed since updating yesterday that certain events on the phone are no longer animated in a smooth way. For example: 1. Open an app 2. Use the power button to screen blank 3. Turn on the power button 4. swipe the launcher in from the left 5. Click the Home (Ubuntu Logo) button Result: the infographic leaving is not smooth, but instead is jerky Expected: Smooth animations There are other jerky things here and there, but that is the most noticeable so far ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity (not installed) Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.1-0ubuntu2 Architecture: armhf CompizPlugins: Error: [Errno 2] No such file or directory: 'gconftool-2' Date: Tue Apr 15 09:00:11 2014 GconfCompiz: Error: [Errno 2] No such file or directory: 'gconftool-2' InstallationDate: Installed on 2014-04-14 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS - armhf (20140414) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug armhf trusty -- 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/1308055 Title: Shell Experience Seems a Little Jerky on Nexus 4 Status in “unity” package in Ubuntu: New Bug description: I noticed since updating yesterday that certain events on the phone are no longer animated in a smooth way. For example: 1. Open an app 2. Use the power button to screen blank 3. Turn on the power button 4. swipe the launcher in from the left 5. Click the Home (Ubuntu Logo) button Result: the infographic leaving is not smooth, but instead is jerky Expected: Smooth animations There are other jerky things here and there, but that is the most noticeable so far ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity (not installed) Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.1-0ubuntu2 Architecture: armhf CompizPlugins: Error: [Errno 2] No such file or directory: 'gconftool-2' Date: Tue Apr 15 09:00:11 2014 GconfCompiz: Error: [Errno 2] No such file or directory: 'gconftool-2' InstallationDate: Installed on 2014-04-14 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS - armhf (20140414) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1308055/+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
reproducible on 13.10 ** Changed in: unity Assignee: (unassigned) = Taihsiang Ho (taihsiangho) ** Changed in: unity (Ubuntu) Assignee: (unassigned) = Taihsiang Ho (taihsiangho) ** Changed in: unity (Ubuntu) Status: Confirmed = 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: In Progress 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 1289470] Re: The phone has three brightness sliders
** Branch linked: lp:~laney/indicator-power/phone-no-slider -- 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/1289470 Title: The phone has three brightness sliders Status in “indicator-power” package in Ubuntu: Triaged Status in “ubuntu-system-settings” package in Ubuntu: New Bug description: The current phone design has three brightness sliders that do exactly the same thing: * System Settings Brightness * System Settings Battery * the Battery menu. This is kind of ridiculous. We should get rid of one or two. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1289470/+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 1289470] Re: The phone has three brightness sliders
** Changed in: indicator-power (Ubuntu) Assignee: (unassigned) = Iain Lane (laney) -- 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/1289470 Title: The phone has three brightness sliders Status in “indicator-power” package in Ubuntu: Triaged Status in “ubuntu-system-settings” package in Ubuntu: New Bug description: The current phone design has three brightness sliders that do exactly the same thing: * System Settings Brightness * System Settings Battery * the Battery menu. This is kind of ridiculous. We should get rid of one or two. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1289470/+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 767253] Re: Finish the implementation of sheet style dialogues
** Changed in: unity Assignee: Sam Spilsbury (smspillaz) = (unassigned) ** Changed in: unity (Ubuntu) Assignee: Sam Spilsbury (smspillaz) = (unassigned) -- 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/767253 Title: Finish the implementation of sheet style dialogues Status in Ayatana Design: Fix Committed Status in Unity: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: Sheet style dialogues were mostly complete when they got dropped late in the Natty cycle, they need to be finished and landed early in the Oneiric cycle so we have time to understand and solve any compatibility issues that may arise. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/767253/+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 1303060] Re: Unity Gestures don't honor alt_tab_bias_viewport setting
** Changed in: unity Milestone: None = 7.2.1 ** Changed in: unity Status: New = Fix Committed ** 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/1303060 Title: Unity Gestures don't honor alt_tab_bias_viewport setting Status in Unity: Fix Committed Status in “unity” package in Ubuntu: Fix Released Bug description: My new Elantech touchpad supports Unitys multitouch gestures, but I've noticed one inconsistency. I like seeing running applications from all workspaces in my Alt-Tab view, but by using the three-finger gestures on my touchpad I can only see applications on the current workspace. When I uncheck alt_tab_bias_viewport in CCSM, I expect Alt-Tab as well as Unity Gestures to behave the same way. The problem: The switcher only shows applications running on the current workspace when using Unity Gestures, even though I've unchecked Bias alt-tab to prefer windows on the current viewport. The fix: Show all windows if alt_tab_bias_viewport is unchecked. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140403-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sat Apr 5 16:25:24 2014 InstallationDate: Installed on 2014-04-04 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140404) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1303060/+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 1296443] Re: Unity screen lock does not do PAM account management or refresh credentials
** Changed in: unity Status: Triaged = 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/1296443 Title: Unity screen lock does not do PAM account management or refresh credentials Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: The Unity screen lock only calls pam_authenticate() to unlock. It should also call pam_acct_mgmt() to do any account management requirements and pam_setcred(PAM_REINITIALIZE_CRED) to reinitialize any credentials To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1296443/+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 1120223] Re: Multi-monitor: Mousepointer hangs when passing between monitors, although no Launcher is there (regression)
** Changed in: unity Status: Confirmed = Fix Released ** Changed in: unity (Ubuntu) Status: Confirmed = 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/1120223 Title: Multi-monitor: Mousepointer hangs when passing between monitors, although no Launcher is there (regression) Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: [How to reproduce] 1. Have a dual screen left-right config, with the Launcher just visible on your main (left) monitor 2. Make your mousepointer move between first and second display multiple times [What you would expect] You should feel no barrier when doing that, as there is no Launcher on the right screen. [What actually happens] The mousepointer sometimes hangs, when moving between those screens (both directions are affected, left-right right-left). Note: It always hangs once you stay longer than 1 second on each monitor. It also starts blocking after one second if you move between your screens rapidly. Workaround (without hacking the code): Edit unityshell.xml (best copy it to ~/.compiz-1/metadata) and change edge_passed_disabled_ms default and max settings to 9, which means your pointer will hang once in 250 hours/once every 10 days after the barrier has been broken. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1120223/+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 1298859] Re: quicklist doesn't appear correctly when the scale factor is 1.0
** Changed in: unity Milestone: None = 7.2.1 ** Changed in: unity Status: In Progress = Fix Committed -- 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/1298859 Title: quicklist doesn't appear correctly when the scale factor is 1.0 Status in Unity: Fix Committed Status in “unity” package in Ubuntu: Fix Released Bug description: When I set the UI scale to a value 1, I see some artifacts in the quicklist. Screenshot: http://i.imgur.com/VawQgQm.png To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1298859/+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 1306417] Re: Lockscreen can be bypassed after screen has blanked
** Changed in: unity Status: In Progress = Fix Committed -- 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/1306417 Title: Lockscreen can be bypassed after screen has blanked Status in Unity: Fix Committed Status in “unity” package in Ubuntu: Fix Released Bug description: Steps to reproduce: 1. Lock the screen 2. Let the lockscreen blank 3. Press ALT+TAB What happens: The application switcher appears and it's possible to switch between applications. The chosen application will get keyboard focus and any input will go there. What should happen: Nothing. Lockscreen should grab the keyboard and stop the input from going anywhere. This has security implications. For example it's possible to open the Run command view and run unity --replace to destroy the lockscreen and open the session. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140410.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Apr 11 10:06:50 2014 InstallationDate: Installed on 2014-02-23 (46 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140223) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1306417/+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 1308055] Re: Shell Experience Seems a Little Jerky on Nexus 4
** Package changed: unity (Ubuntu) = unity8 (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/1308055 Title: Shell Experience Seems a Little Jerky on Nexus 4 Status in “unity8” package in Ubuntu: New Bug description: I noticed since updating yesterday that certain events on the phone are no longer animated in a smooth way. For example: 1. Open an app 2. Use the power button to screen blank 3. Turn on the power button 4. swipe the launcher in from the left 5. Click the Home (Ubuntu Logo) button Result: the infographic leaving is not smooth, but instead is jerky Expected: Smooth animations There are other jerky things here and there, but that is the most noticeable so far ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity (not installed) Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.1-0ubuntu2 Architecture: armhf CompizPlugins: Error: [Errno 2] No such file or directory: 'gconftool-2' Date: Tue Apr 15 09:00:11 2014 GconfCompiz: Error: [Errno 2] No such file or directory: 'gconftool-2' InstallationDate: Installed on 2014-04-14 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS - armhf (20140414) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1308055/+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 1307857] Re: New lock screen doesn't work with On Screen Keyboard activated
Thank you for your bug report. That's a known issue, the new lockscreen has issues with the osk and it was decided to fallback to the old one until those are resolved ** Package changed: unity-greeter (Ubuntu) = unity (Ubuntu) ** Changed in: unity (Ubuntu) Importance: Undecided = Low ** 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/1307857 Title: New lock screen doesn't work with On Screen Keyboard activated Status in “unity” package in Ubuntu: Confirmed Bug description: To reproduce: 1. Activate On Screen Keyboard under System Settings - Universal Access 2. Lock screen, either by Ctrl + Alt + L or let it time out 3. Log in, you will see the old (is it gnome-screensaver-something?) pre 14.04 lock screen login and not the cool new one If you disable On Screen Keyboard and do the procedure again, it will show the new lock screen. Sorry if I files this bug against the wrong package. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-greeter 14.04.9-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 15 08:12:44 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-03-30 (15 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: unity-greeter UpgradeStatus: Upgraded to trusty on 2014-03-30 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1307857/+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 1306112] Re: calendar sync causing 100% cpu and does not complete
** Branch linked: lp:~renatofilho/ubuntu/trusty/syncevolution/fix-1306112 -- 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/1306112 Title: calendar sync causing 100% cpu and does not complete Status in Sync monitor for Ubuntu Touch: In Progress Status in “indicator-datetime” package in Ubuntu: In Progress Status in “qtorganizer5-eds” package in Ubuntu: New Status in “sync-monitor” package in Ubuntu: New Bug description: test using canonical google account this is the problem i'm seeing with the canonical account the calendar sync starts to run first, and it gets about progress of 70 and then evolution-calendar-factory starts consuming all the CPU - 100% (run top -d1) and at the same time the sync-monitor.log shows an infinite number of messages about static void ViewWatcher::onObjectsAdded(ECalClientView*, GSList*, ViewWatcher*) 0x15468a8 virtual QListQtOrganizer::QOrganizerCollection QOrganizerEDSEngine::collections(QtOrganizer::QOrganizerManager::Error*) virtual bool QOrganizerEDSEngine::startRequest(QtOrganizer::QOrganizerAbstractRequest*) virtual bool QOrganizerEDSEngine::waitForRequestFinished(QtOrganizer::QOrganizerAbstractRequest*, int) syn requested for account: bill.fil...@canonical.com calendar Account aready in the queue The sync never finishes, seems that evolution process is stuck. I have to kill it. http://pastebin.ubuntu.com/7231364/ Seems we might be in a loop when calendar events are getting added because of the sync we see tons of messages in the sync-monitor log maybe we're not ignoring the events correctly? or maybe it's a problem is the calendar has a recurring event? seems to cause infinite loop. This one is critical. To manage notifications about this bug go to: https://bugs.launchpad.net/sync-monitor/+bug/1306112/+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 1307649] Re: dash stops working when taking a screen shot
Thank you for your bug report. What do you mean by stops working? It seems to indeed not close when clicking on the background in those cases but still works correctly ** Changed in: unity (Ubuntu) Importance: Undecided = Low -- 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/1307649 Title: dash stops working when taking a screen shot Status in “unity” package in Ubuntu: New Bug description: when dash is open and if the mouse pointer is clicked on the desktop space somewhere other than the dash itself the dash minimizes (or disappears) this doesnot seem to happen when taking a screenshot. If the dash is open and the screenshot button is pressed on keyboard, and then if I try clicking on the desktop space other than the dash, the dash doesnot minimize. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140321-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 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: Mon Apr 14 23:51:24 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:0036] InstallationDate: Installed on 2014-04-05 (9 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta i386 (20140326) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-19-generic root=UUID=53bec5e5-c776-49b7-8bc1-be22d29942cb ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2011 dmi.bios.vendor: Intel Corp. dmi.bios.version: TCIBX10H.86A.0048.2011.1206.1342 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH55TC dmi.board.vendor: Intel Corporation dmi.board.version: AAE70932-302 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrTCIBX10H.86A.0048.2011.1206.1342:bd12/06/2011:svn:pn:pvr:rvnIntelCorporation:rnDH55TC:rvrAAE70932-302:cvn:ct3:cvr: version.compiz: compiz 1:0.9.11+14.04.20140320.1-0ubuntu1 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sun Apr 13 17:59:59 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 20147 vendor GSM xserver.version: 2:1.15.0-1ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1307649/+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 1307857] [NEW] New lock screen doesn't work with On Screen Keyboard activated
You have been subscribed to a public bug: To reproduce: 1. Activate On Screen Keyboard under System Settings - Universal Access 2. Lock screen, either by Ctrl + Alt + L or let it time out 3. Log in, you will see the old (is it gnome-screensaver-something?) pre 14.04 lock screen login and not the cool new one If you disable On Screen Keyboard and do the procedure again, it will show the new lock screen. Sorry if I files this bug against the wrong package. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-greeter 14.04.9-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 15 08:12:44 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-03-30 (15 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: unity-greeter UpgradeStatus: Upgraded to trusty on 2014-03-30 (15 days ago) ** Affects: unity (Ubuntu) Importance: Low Status: Confirmed ** Tags: amd64 apport-bug trusty -- New lock screen doesn't work with On Screen Keyboard activated https://bugs.launchpad.net/bugs/1307857 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 1308005] Re: [regression] no way to close tall windows as they appear below top panel
*** This bug is a duplicate of bug 1303462 *** https://bugs.launchpad.net/bugs/1303462 ** Changed in: unity Status: New = Triaged ** Changed in: unity (Ubuntu) Status: New = Triaged ** This bug has been marked a duplicate of bug 1303462 [Regression] Window titlebars placed behind panel -- 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/1308005 Title: [regression] no way to close tall windows as they appear below top panel Status in Unity: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: Its a bad regression, when I open tall windows their title bar goes below the top panel. hence making it impossible to close the window with mouse, this is a problem for novice users on which I tested 14.04 and puts a bad impression. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 15 16:04:23 2014 InstallationDate: Installed on 2014-02-28 (45 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140228) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1308005/+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 1308002] Re: Screen quickly autolocks again after unlocking
Since this bug is believed to have been fixed in a recent version of the Uniy shell, could you please report the version you have installed? From the command line, the command apt-cache policy unity should give this information. ** Changed in: unity (Ubuntu) Status: New = Incomplete ** Changed in: unity Status: New = Incomplete -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1308002 Title: Screen quickly autolocks again after unlocking Status in Unity: Incomplete Status in “unity” package in Ubuntu: Incomplete Bug description: Yes the title sounds odd, right? So I have seen it many times and others have reported that to me as well. Mostly after resuming from suspend and entering password to unlock the screen, lightdm password screen comes to front just in a few seconds after I unlock the screen, so basically i have to enter password twice to unlock screen. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu2 Architecture: i386 CurrentDesktop: Unity Date: Tue Apr 15 16:06:48 2014 InstallationDate: Installed on 2014-02-28 (45 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140228) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1308002/+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 1299741] Re: Shadows shouldn't wrap around to other workspaces
** Changed in: unity (Ubuntu) Status: Confirmed = Triaged ** Changed in: unity (Ubuntu) Importance: Undecided = Low -- 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/1299741 Title: Shadows shouldn't wrap around to other workspaces Status in Unity: Triaged Status in “compiz” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: Triaged Bug description: I suppose this could be seen as a matter of design opinion but, in my opinion, it's incredibly ugly. To reproduce, launch a whole bunch (10, 20, a lot) of windows on workspace 2, and position them on or near the right edge. Then switch to workspace 1, and observe the massive black blob on the left of the screen. This really doesn't make a whole lot of sense visually, and it's pretty ugly, IMO. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1299741/+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 1306973] Re: Unity Gestures: Gestures work on lock screen
** Changed in: unity Status: New = Fix Committed ** Changed in: unity Milestone: None = 7.2.1 ** Changed in: unity (Ubuntu) Status: New = Fix Released ** Changed in: unity (Ubuntu) Importance: Undecided = High -- 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/1306973 Title: Unity Gestures: Gestures work on lock screen Status in Unity: Fix Committed Status in “unity” package in Ubuntu: Fix Released Bug description: Unity Gestures can be invoked while the lock screen is shown. This is a security problem, as it allows to peek inside the running applications and show windows using a 3 finger gesture, while on the lock screen. A screenshot for this is attatched. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1306973/+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 1303060] Re: Unity Gestures don't honor alt_tab_bias_viewport setting
** Changed in: unity Assignee: (unassigned) = Alfred Neumayer (beidl) -- 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/1303060 Title: Unity Gestures don't honor alt_tab_bias_viewport setting Status in Unity: Fix Committed Status in “unity” package in Ubuntu: Fix Released Bug description: My new Elantech touchpad supports Unitys multitouch gestures, but I've noticed one inconsistency. I like seeing running applications from all workspaces in my Alt-Tab view, but by using the three-finger gestures on my touchpad I can only see applications on the current workspace. When I uncheck alt_tab_bias_viewport in CCSM, I expect Alt-Tab as well as Unity Gestures to behave the same way. The problem: The switcher only shows applications running on the current workspace when using Unity Gestures, even though I've unchecked Bias alt-tab to prefer windows on the current viewport. The fix: Show all windows if alt_tab_bias_viewport is unchecked. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140403-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sat Apr 5 16:25:24 2014 InstallationDate: Installed on 2014-04-04 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140404) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1303060/+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 990493] Re: After suspend+resume, date in menu bar is incorrect
Ok, I've read the rules and so even it seems strange, it is correct for this bug not to be fixed on 12.04. Question is what a security flaw or regression is in this case, as people's action based on wrong date information may be harmful. On the other side, it is no threat to the security of the computer system itself. So we keep going with wrong dates for another year :-) -- 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/990493 Title: After suspend+resume, date in menu bar is incorrect Status in The Date and Time Indicator: Fix Released Status in “getting-started-with-ubuntu-12.04” package in Ubuntu: Confirmed Status in “indicator-datetime” package in Ubuntu: Fix Released Bug description: indicator-datetime 0.3.94-0ubuntu2, Ubuntu 12.04 - Fake the date as 11:55 PM - Suspend system - Resume 10 minutes later - Date won't be updated in the unity top bar. For example: - Booted system on 4/27/12 - System repeatedly taken in and out of suspend - System placed in suspend around 4/27/12 11:30 PM - System resumed fom suspend 4/28/12 9:00 AM - When clicking the time in the unity top bar, date says Friday, 27 April 2012 - When running date from command line, date says Sat Apr 28 Screenshot: https://launchpadlibrarian.net/131172962/WrongTime.png See also bug 996743, and bug 1157914 for VMs in particular. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/990493/+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 1306454] Re: Webapps don't show up in launcher
*** This bug is a duplicate of bug 1307409 *** https://bugs.launchpad.net/bugs/1307409 ** This bug has been marked a duplicate of bug 1307409 Cannot install webbapp launcher from Firefox -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity-webapps in Ubuntu. https://bugs.launchpad.net/bugs/1306454 Title: Webapps don't show up in launcher Status in WebApps: libunity: New Status in “libunity-webapps” package in Ubuntu: New Bug description: It may be that my user session is screwed up and that this bug is invalid, but anyway I'd appreciate some hints on how to restore the functionality. I'm using firefox 28.0, and when I visit a webapp-supported website and I'm asked for integration and I accept it, nothing happens. For instance, when I visit gmail.com, no icon is added to the launcher. There is a gmail application in the dash, but I believe it's from an older version: in fact, when I start it, the command line being used is: webapp-container --app-id=Gmailmailgooglecom --webapp --enable-back- forward https://mail.google.com whis seems wrong (the --webapp argument is missing the webapp name). I tried removing all webapps from ~/.local/share/applications/, and I also removed the ~/.local/share/unity-webapps* directories, but this didn't help. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libunity-webapps0 2.5.0~+14.04.20140324-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 11 11:18:37 2014 InstallationDate: Installed on 2011-12-19 (843 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: libunity-webapps UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libunity-webapps/+bug/1306454/+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 1306968] Re: After unlocking the desktop, it locks itself again.
This bug seems to have resolved itself since reporting it. I took a look at the package install logs and there not obviously connected package that would have fixed this. Here's what's been installed since reporting the bug. Start-Date: 2014-04-13 18:42:52 Commandline: apt-get upgrade Upgrade: libabiword-3.0:amd64 (3.0.0-4, 3.0.0-4ubuntu1), abiword:amd64 (3.0.0-4, 3.0.0-4ubuntu1), multiarch-support:amd64 (2.19-0ubuntu5, 2.19-0ubuntu6), abiword-plugin-grammar:amd64 (3.0.0-4, 3.0.0-4ubuntu1), ubuntu-drivers-common:amd64 (0.2.91.3, 0.2.91.4), ubuntu-release-upgrader-gtk:amd64 (0.220.1, 0.220.2), libc-dev-bin:amd64 (2.19-0ubuntu5, 2.19-0ubuntu6), libc-bin:amd64 (2.19-0ubuntu5, 2.19-0ubuntu6), libc6:amd64 (2.19-0ubuntu5, 2.19-0ubuntu6), abiword-plugin-mathview:amd64 (3.0.0-4, 3.0.0-4ubuntu1), abiword-common:amd64 (3.0.0-4, 3.0.0-4ubuntu1), python3-distupgrade:amd64 (0.220.1, 0.220.2), libc6-i386:amd64 (2.19-0ubuntu5, 2.19-0ubuntu6), ubuntu-release-upgrader-core:amd64 (0.220.1, 0.220.2), libc6-dbg:amd64 (2.19-0ubuntu5, 2.19-0ubuntu6), libc6-dev:amd64 (2.19-0ubuntu5, 2.19-0ubuntu6) End-Date: 2014-04-13 18:43:58 Start-Date: 2014-04-14 09:21:51 Commandline: aptdaemon role='role-commit-packages' sender=':1.233' Install: qtdeclarative5-dialogs-plugin:amd64 (5.2.1-3ubuntu15), qtdeclarative5-privatewidgets-plugin:amd64 (5.2.1-3ubuntu15, automatic) Upgrade: webapp-container:amd64 (0.23+14.04.20140410-0ubuntu1, 0.23+14.04.20140411.1-0ubuntu1), webbrowser-app:amd64 (0.23+14.04.20140410-0ubuntu1, 0.23+14.04.20140411.1-0ubuntu1), qtdeclarative5-ubuntu-ui-extras-browser-plugin:amd64 (0.23+14.04.20140410-0ubuntu1, 0.23+14.04.20140411.1-0ubuntu1) End-Date: 2014-04-14 09:22:08 Start-Date: 2014-04-14 09:23:06 Commandline: aptdaemon role='role-commit-packages' sender=':1.233' Upgrade: oxideqt-codecs-extra:amd64 (1.0.0~bzr490-0ubuntu1, 1.0.0~bzr501-0ubuntu1), liboil0.3:amd64 (0.3.17-2ubuntu3, 0.3.17-2ubuntu4), liboxideqtcore0:amd64 (1.0.0~bzr490-0ubuntu1, 1.0.0~bzr501-0ubuntu1), liboxideqt-qmlplugin:amd64 (1.0.0~bzr490-0ubuntu1, 1.0.0~bzr501-0ubuntu1) End-Date: 2014-04-14 09:23:18 -- 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/1306968 Title: After unlocking the desktop, it locks itself again. Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: After idling for some time my desktop locks. When I return and enter the password, it unlocks and I briefly see my desktop and open applications before it locks itself again. After entering the password (again), it seems to work fine. Expected behavior: The desktop shouldn't lock immediately after unlocking. Reproduce: 1. Let the screen lock on its own. Using CTRL-ALT-L seems to only require unlocking once. 2. Try to unlock the desktop using your password. It will relock (for me). I have a feeling it might have something to do with the monitor going to sleep, which might explain why CTRL-ALT-L seems to work (the monitor never sleeps.) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu2 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 Apr 11 14:38:30 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] [1002:68f9] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:304a] InstallationDate: Installed on 2014-04-02 (10 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-19-generic root=UUID=e01ba637-d590-489e-ba5a-d0a4f1ed4cae ro quiet splash nomdmonddf nomdmonisw SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/05/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080014 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: A74MX-S/A74MX-K dmi.board.vendor: FOXCONN dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias:
[Dx-packages] [Bug 1308130] [NEW] indicator-messages-service is waking up every 4 seconds adding inotifies on paths that don't exist
Public bug reported:
I've observed that an idle indicator-messages-services is waking up
every 4 seconds on a poll() and doing two inotify_add_watch() calls on
paths that don't exist, which wastes power on devices such as phones.
strace shows:
clock_gettime(CLOCK_MONOTONIC, {10117, 224455428}) = 0
poll([{fd=8, events=POLLIN}, {fd=9, events=POLLIN}], 2, 3991) = 0 (Timeout)
clock_gettime(CLOCK_MONOTONIC, {10121, 224516469}) = 0
inotify_add_watch(9, /usr/local/share/applications,
IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR)
= -1 ENOENT (No such file or directory)
inotify_add_watch(9, /usr/share/ubuntu-touch/applications,
IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR)
= -1 ENOENT (No such file or directory)
clock_gettime(CLOCK_MONOTONIC, {10121, 232085521}) = 0
poll([{fd=8, events=POLLIN}, {fd=9, events=POLLIN}], 2, 3984) = 0 (Timeout)
clock_gettime(CLOCK_MONOTONIC, {10125, 222593684}) = 0
inotify_add_watch(9, /usr/local/share/applications,
IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR)
= -1 ENOENT (No such file or directory)
inotify_add_watch(9, /usr/share/ubuntu-touch/applications,
IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR)
= -1 ENOENT (No such file or directory)
clock_gettime(CLOCK_MONOTONIC, {10125, 229094524}) = 0
Can these redundant polling checks be reduced or removed? Polling every
4 seconds is a little bit heavy handed IMHO.
** Affects: indicator-messages (Ubuntu)
Importance: Undecided
Status: New
--
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/1308130
Title:
indicator-messages-service is waking up every 4 seconds adding
inotifies on paths that don't exist
Status in “indicator-messages” package in Ubuntu:
New
Bug description:
I've observed that an idle indicator-messages-services is waking up
every 4 seconds on a poll() and doing two inotify_add_watch() calls on
paths that don't exist, which wastes power on devices such as phones.
strace shows:
clock_gettime(CLOCK_MONOTONIC, {10117, 224455428}) = 0
poll([{fd=8, events=POLLIN}, {fd=9, events=POLLIN}], 2, 3991) = 0 (Timeout)
clock_gettime(CLOCK_MONOTONIC, {10121, 224516469}) = 0
inotify_add_watch(9, /usr/local/share/applications,
IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR)
= -1 ENOENT (No such file or directory)
inotify_add_watch(9, /usr/share/ubuntu-touch/applications,
IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR)
= -1 ENOENT (No such file or directory)
clock_gettime(CLOCK_MONOTONIC, {10121, 232085521}) = 0
poll([{fd=8, events=POLLIN}, {fd=9, events=POLLIN}], 2, 3984) = 0 (Timeout)
clock_gettime(CLOCK_MONOTONIC, {10125, 222593684}) = 0
inotify_add_watch(9, /usr/local/share/applications,
IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR)
= -1 ENOENT (No such file or directory)
inotify_add_watch(9, /usr/share/ubuntu-touch/applications,
IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR)
= -1 ENOENT (No such file or directory)
clock_gettime(CLOCK_MONOTONIC, {10125, 229094524}) = 0
Can these redundant polling checks be reduced or removed? Polling
every 4 seconds is a little bit heavy handed IMHO.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1308130/+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 1221848] Re: Eclipse menu won't open in Ubuntu 13.10 (beta1)
*** This bug is a duplicate of bug 1208019 *** https://bugs.launchpad.net/bugs/1208019 thank you Basher your solution worked for me i am using ubuntu 13.10 32bit version -- 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/1221848 Title: Eclipse menu won't open in Ubuntu 13.10 (beta1) Status in “unity” package in Ubuntu: Confirmed Bug description: I am using Eclipse-CDT (Kepler Linux 64bit) for some development and it worked perfectly on Ubuntu 13.04 X86_64. However, after upgrading to Ubuntu 13.10 (beta 1) yesterday I found I could not have Eclipse menus (located on Unity's top-panel ) droped down. I also tried to download a new copy of Eclipse but it was the same. It looks like something wrong in 13.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1221848/+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 1210077] Re: Screen freeze and garbled after resume from suspend
** Also affects: unity (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-331 (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-331 (Ubuntu Precise) Assignee: (unassigned) = Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-331 (Ubuntu Precise) Importance: Undecided = Medium ** Changed in: nvidia-graphics-drivers-331 (Ubuntu Precise) Status: New = In Progress ** No longer affects: unity (Ubuntu Precise) ** Description changed: + [Impact] + Users of nvidia graphics drivers can see graphics freezes or corruption after suspend/resume. Switching to a VT and back to X can potentially solve freeze issues, but corruption may result. + + [Test Case] + Suspend/Resume many times with nvidia graphics and see if the problem happens. + + [Regression Potential] + This is already in Trusty. + + -- + Perform regular suspend, either from system menu or close laptop lid, when system resuming from suspend, it will freeze. Switch to VT and back to X can solve freeze issue, but the screen are gabled and some character rendering are strange, however whole system can perform usual task. found affected graphics: gf108m gf117m gk107glm -- 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/1210077 Title: Screen freeze and garbled after resume from suspend Status in HWE Next Project: Fix Released Status in HWE Next trusty series: Fix Released Status in Unity: Fix Released Status in “nvidia-graphics-drivers-331” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-331” source package in Precise: In Progress Bug description: [Impact] Users of nvidia graphics drivers can see graphics freezes or corruption after suspend/resume. Switching to a VT and back to X can potentially solve freeze issues, but corruption may result. [Test Case] Suspend/Resume many times with nvidia graphics and see if the problem happens. [Regression Potential] This is already in Trusty. -- Perform regular suspend, either from system menu or close laptop lid, when system resuming from suspend, it will freeze. Switch to VT and back to X can solve freeze issue, but the screen are gabled and some character rendering are strange, however whole system can perform usual task. found affected graphics: gf108m gf117m gk107glm To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1210077/+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 1307983] [NEW] System not localized after an OEM installation
You have been subscribed to a public bug: Ubuntu Trusty Desktop amd64 20140414 TEST CASE: 1. Do an OEM installation of Ubuntu Trusty Desktop AMD64 2. Reboot and prepare for shipping 3. Reboot and configure the end-user - Select language: Deutsch 4. After the setup, reboot ACTUAL RESULT: System is in english EXPECTED RESULT: System is in german ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 Date: Tue Apr 15 12:21:55 2014 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity initrd=/casper/initrd.lz quiet splash -- keyboard-configuration/layoutcode=fr keyboard-configuration/variantcode=oss oem-config/enable=true InstallationDate: Installed on 2014-04-15 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140414) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: accountsservice (Ubuntu) Importance: High Status: Confirmed ** Tags: amd64 apport-bug iso-testing oem-config qa-manual-testing rls-t-incoming testcase trusty ubiquity-2.18.4 -- System not localized after an OEM installation https://bugs.launchpad.net/bugs/1307983 You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice 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 1308130] Re: indicator-messages-service is waking up every 4 seconds adding inotifies on paths that don't exist
This shows up in the daily testing too:
http://ci.ubuntu.com/power/eventstat/image/3138/machine/6/task
/indicator-messages-service/details/
--
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/1308130
Title:
indicator-messages-service is waking up every 4 seconds adding
inotifies on paths that don't exist
Status in “indicator-messages” package in Ubuntu:
New
Bug description:
I've observed that an idle indicator-messages-services is waking up
every 4 seconds on a poll() and doing two inotify_add_watch() calls on
paths that don't exist, which wastes power on devices such as phones.
strace shows:
clock_gettime(CLOCK_MONOTONIC, {10117, 224455428}) = 0
poll([{fd=8, events=POLLIN}, {fd=9, events=POLLIN}], 2, 3991) = 0 (Timeout)
clock_gettime(CLOCK_MONOTONIC, {10121, 224516469}) = 0
inotify_add_watch(9, /usr/local/share/applications,
IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR)
= -1 ENOENT (No such file or directory)
inotify_add_watch(9, /usr/share/ubuntu-touch/applications,
IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR)
= -1 ENOENT (No such file or directory)
clock_gettime(CLOCK_MONOTONIC, {10121, 232085521}) = 0
poll([{fd=8, events=POLLIN}, {fd=9, events=POLLIN}], 2, 3984) = 0 (Timeout)
clock_gettime(CLOCK_MONOTONIC, {10125, 222593684}) = 0
inotify_add_watch(9, /usr/local/share/applications,
IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR)
= -1 ENOENT (No such file or directory)
inotify_add_watch(9, /usr/share/ubuntu-touch/applications,
IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR)
= -1 ENOENT (No such file or directory)
clock_gettime(CLOCK_MONOTONIC, {10125, 229094524}) = 0
Can these redundant polling checks be reduced or removed? Polling
every 4 seconds is a little bit heavy handed IMHO.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1308130/+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 1308130] Re: indicator-messages-service is waking up every 4 seconds adding inotifies on paths that don't exist
Thanks Colin, that's the same issue than bug #1296233
Without improving/fixing/replace inotify we mostly have workaround
solution. One would be to create those directories on the default
image...
** Changed in: indicator-messages (Ubuntu)
Importance: Undecided = Low
** Changed in: indicator-messages (Ubuntu)
Status: New = Confirmed
--
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/1308130
Title:
indicator-messages-service is waking up every 4 seconds adding
inotifies on paths that don't exist
Status in “indicator-messages” package in Ubuntu:
Confirmed
Bug description:
I've observed that an idle indicator-messages-services is waking up
every 4 seconds on a poll() and doing two inotify_add_watch() calls on
paths that don't exist, which wastes power on devices such as phones.
strace shows:
clock_gettime(CLOCK_MONOTONIC, {10117, 224455428}) = 0
poll([{fd=8, events=POLLIN}, {fd=9, events=POLLIN}], 2, 3991) = 0 (Timeout)
clock_gettime(CLOCK_MONOTONIC, {10121, 224516469}) = 0
inotify_add_watch(9, /usr/local/share/applications,
IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR)
= -1 ENOENT (No such file or directory)
inotify_add_watch(9, /usr/share/ubuntu-touch/applications,
IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR)
= -1 ENOENT (No such file or directory)
clock_gettime(CLOCK_MONOTONIC, {10121, 232085521}) = 0
poll([{fd=8, events=POLLIN}, {fd=9, events=POLLIN}], 2, 3984) = 0 (Timeout)
clock_gettime(CLOCK_MONOTONIC, {10125, 222593684}) = 0
inotify_add_watch(9, /usr/local/share/applications,
IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR)
= -1 ENOENT (No such file or directory)
inotify_add_watch(9, /usr/share/ubuntu-touch/applications,
IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR)
= -1 ENOENT (No such file or directory)
clock_gettime(CLOCK_MONOTONIC, {10125, 229094524}) = 0
Can these redundant polling checks be reduced or removed? Polling
every 4 seconds is a little bit heavy handed IMHO.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1308130/+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 1307983] Re: System not localized after an OEM installation
** Package changed: ubiquity (Ubuntu) = accountsservice (Ubuntu) ** Also affects: accountsservice (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: accountsservice (Ubuntu Trusty) Importance: High Status: Confirmed ** Changed in: accountsservice (Ubuntu Precise) Status: New = Confirmed ** Changed in: accountsservice (Ubuntu Precise) Importance: Undecided = High -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1307983 Title: System not localized after an OEM installation Status in “accountsservice” package in Ubuntu: Confirmed Status in “accountsservice” source package in Precise: Confirmed Status in “accountsservice” source package in Trusty: Confirmed Bug description: Ubuntu Trusty Desktop amd64 20140414 TEST CASE: 1. Do an OEM installation of Ubuntu Trusty Desktop AMD64 2. Reboot and prepare for shipping 3. Reboot and configure the end-user - Select language: Deutsch 4. After the setup, reboot ACTUAL RESULT: System is in english EXPECTED RESULT: System is in german ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 Date: Tue Apr 15 12:21:55 2014 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity initrd=/casper/initrd.lz quiet splash -- keyboard-configuration/layoutcode=fr keyboard-configuration/variantcode=oss oem-config/enable=true InstallationDate: Installed on 2014-04-15 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140414) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1307983/+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 1289099] Re: [SRU] Window Matching fixes
This bug was fixed in the package libunity-webapps - 2.5.0~+13.10.20140327-0ubuntu1 --- libunity-webapps (2.5.0~+13.10.20140327-0ubuntu1) saucy; urgency=low * Automatic snapshot from revision 1240 libunity-webapps (2.5.0~+13.10.20140307-0ubuntu1) saucy; urgency=low [ Justin McPherson ] * Fix some of the matching problems. (LP: #1289099) [ Ubuntu daily release ] * Automatic snapshot from revision 1238 -- Ubuntu daily release ps-jenk...@lists.canonical.com Thu, 27 Mar 2014 23:49:39 + ** Changed in: libunity-webapps (Ubuntu Saucy) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity-webapps in Ubuntu. https://bugs.launchpad.net/bugs/1289099 Title: [SRU] Window Matching fixes Status in WebApps: libunity: Fix Released Status in “libunity-webapps” package in Ubuntu: Fix Released Status in “libunity-webapps” source package in Saucy: Fix Released Bug description: [Impact] * Window matching behaviors are deficient. This means that the Dash does not always correctly indicate which app is active, and sometimes two icons can be displayed for the same app (one that stays permanently for launching, and one that appears only when the app is running). [Test Case] * Browse to the affected website, notice the behavior of the webapps in the Dash is inconsistent. Behavior can include - * Browser Launcher item is not associated with the appropriate WebApp Launcher item * Two items may appear associated with the WebApp (instead of one) * Icon may appear as Launcher default, not the appropriate WebApp icon [Regression Potential] * Quite small, this change is confined to libunity-webapps and can't impact anything outisde of the webapps interaction in Unity. To manage notifications about this bug go to: https://bugs.launchpad.net/libunity-webapps/+bug/1289099/+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 1289099] Update Released
The verification of the Stable Release Update for libunity-webapps has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions. -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity-webapps in Ubuntu. https://bugs.launchpad.net/bugs/1289099 Title: [SRU] Window Matching fixes Status in WebApps: libunity: Fix Released Status in “libunity-webapps” package in Ubuntu: Fix Released Status in “libunity-webapps” source package in Saucy: Fix Released Bug description: [Impact] * Window matching behaviors are deficient. This means that the Dash does not always correctly indicate which app is active, and sometimes two icons can be displayed for the same app (one that stays permanently for launching, and one that appears only when the app is running). [Test Case] * Browse to the affected website, notice the behavior of the webapps in the Dash is inconsistent. Behavior can include - * Browser Launcher item is not associated with the appropriate WebApp Launcher item * Two items may appear associated with the WebApp (instead of one) * Icon may appear as Launcher default, not the appropriate WebApp icon [Regression Potential] * Quite small, this change is confined to libunity-webapps and can't impact anything outisde of the webapps interaction in Unity. To manage notifications about this bug go to: https://bugs.launchpad.net/libunity-webapps/+bug/1289099/+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 1307983] Re: System not localized after an OEM installation
I believe both this bug #1307983 and bug #1308056 are regressions since landing accountsservice patch for bug #1134364. Whilst the change does not regress bug #1134364 test case. -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1307983 Title: System not localized after an OEM installation Status in “accountsservice” package in Ubuntu: Confirmed Status in “accountsservice” source package in Precise: Confirmed Status in “accountsservice” source package in Trusty: Confirmed Bug description: Ubuntu Trusty Desktop amd64 20140414 TEST CASE: 1. Do an OEM installation of Ubuntu Trusty Desktop AMD64 2. Reboot and prepare for shipping 3. Reboot and configure the end-user - Select language: Deutsch 4. After the setup, reboot ACTUAL RESULT: System is in english EXPECTED RESULT: System is in german ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 Date: Tue Apr 15 12:21:55 2014 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity initrd=/casper/initrd.lz quiet splash -- keyboard-configuration/layoutcode=fr keyboard-configuration/variantcode=oss oem-config/enable=true InstallationDate: Installed on 2014-04-15 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140414) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1307983/+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
not reproducible on 12.04 unity 5.20.0 -- 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: In Progress 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 1289099] Re: [SRU] Window Matching fixes
Thanks Colin! -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity-webapps in Ubuntu. https://bugs.launchpad.net/bugs/1289099 Title: [SRU] Window Matching fixes Status in WebApps: libunity: Fix Released Status in “libunity-webapps” package in Ubuntu: Fix Released Status in “libunity-webapps” source package in Saucy: Fix Released Bug description: [Impact] * Window matching behaviors are deficient. This means that the Dash does not always correctly indicate which app is active, and sometimes two icons can be displayed for the same app (one that stays permanently for launching, and one that appears only when the app is running). [Test Case] * Browse to the affected website, notice the behavior of the webapps in the Dash is inconsistent. Behavior can include - * Browser Launcher item is not associated with the appropriate WebApp Launcher item * Two items may appear associated with the WebApp (instead of one) * Icon may appear as Launcher default, not the appropriate WebApp icon [Regression Potential] * Quite small, this change is confined to libunity-webapps and can't impact anything outisde of the webapps interaction in Unity. To manage notifications about this bug go to: https://bugs.launchpad.net/libunity-webapps/+bug/1289099/+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 1210077] Re: Screen freeze and garbled after resume from suspend
Hello Yung, or anyone else affected, Accepted nvidia-graphics-drivers-331 into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source /nvidia-graphics-drivers-331/331.20-0ubuntu0.0.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: nvidia-graphics-drivers-331 (Ubuntu Precise) Status: In Progress = Fix Committed ** Tags added: verification-needed -- 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/1210077 Title: Screen freeze and garbled after resume from suspend Status in HWE Next Project: Fix Released Status in HWE Next trusty series: Fix Released Status in Unity: Fix Released Status in “nvidia-graphics-drivers-331” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-331” source package in Precise: Fix Committed Bug description: [Impact] Users of nvidia graphics drivers can see graphics freezes or corruption after suspend/resume. Switching to a VT and back to X can potentially solve freeze issues, but corruption may result. [Test Case] Suspend/Resume many times with nvidia graphics and see if the problem happens. [Regression Potential] This is already in Trusty. -- Perform regular suspend, either from system menu or close laptop lid, when system resuming from suspend, it will freeze. Switch to VT and back to X can solve freeze issue, but the screen are gabled and some character rendering are strange, however whole system can perform usual task. found affected graphics: gf108m gf117m gk107glm To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1210077/+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 1210077] Re: Screen freeze and garbled after resume from suspend
** Branch linked: lp:ubuntu/precise-proposed/nvidia-graphics-drivers-331 -- 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/1210077 Title: Screen freeze and garbled after resume from suspend Status in HWE Next Project: Fix Released Status in HWE Next trusty series: Fix Released Status in Unity: Fix Released Status in “nvidia-graphics-drivers-331” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-331” source package in Precise: Fix Committed Bug description: [Impact] Users of nvidia graphics drivers can see graphics freezes or corruption after suspend/resume. Switching to a VT and back to X can potentially solve freeze issues, but corruption may result. [Test Case] Suspend/Resume many times with nvidia graphics and see if the problem happens. [Regression Potential] This is already in Trusty. -- Perform regular suspend, either from system menu or close laptop lid, when system resuming from suspend, it will freeze. Switch to VT and back to X can solve freeze issue, but the screen are gabled and some character rendering are strange, however whole system can perform usual task. found affected graphics: gf108m gf117m gk107glm To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1210077/+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 1305127] Re: Skype systray icon disappear
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/1305127 Title: Skype systray icon disappear Status in Unity: Triaged Status in “unity” package in Ubuntu: Confirmed Bug description: I did a Ubuntu 14.04 beta 2 fresh install on one of my notebooks. After that I install Skype from partner repository. The Skype icon in systray shows at start, but disappear after login into my Skype account. Any questions about this just ask. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1305127/+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 1269436] Re: Unity systray disappears
*** This bug is a duplicate of bug 1305127 *** https://bugs.launchpad.net/bugs/1305127 ** This bug has been marked a duplicate of bug 1305127 Skype systray icon disappear -- 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/1269436 Title: Unity systray disappears Status in “unity” package in Ubuntu: Confirmed Bug description: From time to time, systray disappears with all of its icons, which were showing OK up to that point. Needless to say, this defeats the main purpose of apps like Skype or Pidgin. Strange thing is, if I switch to another desktop workspace (Ctrl+Alt+Arrows), the systray appears for a split second during the workspace scrolling, then disappears again. I checked several other bugs and neither seemed to be my case. Also, note that Skype, Pidgin and a few others are whitelisted: $ gsettings get com.canonical.Unity.Panel systray-whitelist ['JavaEmbeddedFrame', 'Wine', 'Update-notifier', 'Skype', 'Pidgin', 'Evolution', 'Vuze', 'Azureus', 'Azureus2'] Is there at least a workaround to get the systray back when this happens? Thanks Using Ubuntu Desktop 12.04.4 LTS 64 bit, ATI Radeon with open source driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1269436/+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 1308193] [NEW] Upcoming recurring alarms on wrong day
Public bug reported: Open clock Set alarm, make it occur every working day - and today is Tuesday. Save alarm. Pull down indicator, observe that next alarm is shown as Mon not Wed which is tomorrow. Expectation would be that the indicator shows the next alarm, not the one 4 alarms away. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-datetime 13.10.0+14.04.20140408-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.1-0ubuntu2 Architecture: armhf Date: Tue Apr 15 18:35:01 2014 InstallationDate: Installed on 2014-04-15 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS - armhf (20140415.1) SourcePackage: indicator-datetime UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug armhf trusty ** Attachment added: device-2014-04-15-193319.png https://bugs.launchpad.net/bugs/1308193/+attachment/4084649/+files/device-2014-04-15-193319.png -- 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/1308193 Title: Upcoming recurring alarms on wrong day Status in “indicator-datetime” package in Ubuntu: New Bug description: Open clock Set alarm, make it occur every working day - and today is Tuesday. Save alarm. Pull down indicator, observe that next alarm is shown as Mon not Wed which is tomorrow. Expectation would be that the indicator shows the next alarm, not the one 4 alarms away. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-datetime 13.10.0+14.04.20140408-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.1-0ubuntu2 Architecture: armhf Date: Tue Apr 15 18:35:01 2014 InstallationDate: Installed on 2014-04-15 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS - armhf (20140415.1) SourcePackage: indicator-datetime 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/1308193/+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 1307226] Re: LibreOffice Writer menubar dont work perfectly.
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/1307226 Title: LibreOffice Writer menubar dont work perfectly. Status in “unity” package in Ubuntu: Confirmed Bug description: Hello guys, I tripped over a bug this morning in the LibreOffice Writer. Every time when I open it the menubar dont work perfectly. The minimize button, close button and maximize button dont appear. When you enable to show de menus in the window's title bar, all de menus simply disappear. This problem happens only in LibreOffice Writer, other applications are running smoothly. Sorry my english. Bye. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libreoffice-core 1:4.2.3~rc3-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 13 17:29:50 2014 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2014-04-13 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140412) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1307226/+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 1307226] Re: LibreOffice Writer menubar dont work perfectly.
I'm seeing this bug in a Live session. Can't actually install at present. -- 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/1307226 Title: LibreOffice Writer menubar dont work perfectly. Status in “unity” package in Ubuntu: Confirmed Bug description: Hello guys, I tripped over a bug this morning in the LibreOffice Writer. Every time when I open it the menubar dont work perfectly. The minimize button, close button and maximize button dont appear. When you enable to show de menus in the window's title bar, all de menus simply disappear. This problem happens only in LibreOffice Writer, other applications are running smoothly. Sorry my english. Bye. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libreoffice-core 1:4.2.3~rc3-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 13 17:29:50 2014 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2014-04-13 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140412) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1307226/+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 1308130] Re: indicator-messages-service is waking up every 4 seconds adding inotifies on paths that don't exist
how about you make the indicator (ab)use upstart for this, it has file
watchers already and could send an event the indicator could pick up
(hoping that systemd offers something equivalent indeed)
--
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/1308130
Title:
indicator-messages-service is waking up every 4 seconds adding
inotifies on paths that don't exist
Status in “indicator-messages” package in Ubuntu:
Confirmed
Bug description:
I've observed that an idle indicator-messages-services is waking up
every 4 seconds on a poll() and doing two inotify_add_watch() calls on
paths that don't exist, which wastes power on devices such as phones.
strace shows:
clock_gettime(CLOCK_MONOTONIC, {10117, 224455428}) = 0
poll([{fd=8, events=POLLIN}, {fd=9, events=POLLIN}], 2, 3991) = 0 (Timeout)
clock_gettime(CLOCK_MONOTONIC, {10121, 224516469}) = 0
inotify_add_watch(9, /usr/local/share/applications,
IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR)
= -1 ENOENT (No such file or directory)
inotify_add_watch(9, /usr/share/ubuntu-touch/applications,
IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR)
= -1 ENOENT (No such file or directory)
clock_gettime(CLOCK_MONOTONIC, {10121, 232085521}) = 0
poll([{fd=8, events=POLLIN}, {fd=9, events=POLLIN}], 2, 3984) = 0 (Timeout)
clock_gettime(CLOCK_MONOTONIC, {10125, 222593684}) = 0
inotify_add_watch(9, /usr/local/share/applications,
IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR)
= -1 ENOENT (No such file or directory)
inotify_add_watch(9, /usr/share/ubuntu-touch/applications,
IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR)
= -1 ENOENT (No such file or directory)
clock_gettime(CLOCK_MONOTONIC, {10125, 229094524}) = 0
Can these redundant polling checks be reduced or removed? Polling
every 4 seconds is a little bit heavy handed IMHO.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1308130/+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 1307226] Re: LibreOffice Writer menubar dont work perfectly.
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1307226 ** Tags added: iso-testing -- 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/1307226 Title: LibreOffice Writer menubar dont work perfectly. Status in “unity” package in Ubuntu: Confirmed Bug description: Hello guys, I tripped over a bug this morning in the LibreOffice Writer. Every time when I open it the menubar dont work perfectly. The minimize button, close button and maximize button dont appear. When you enable to show de menus in the window's title bar, all de menus simply disappear. This problem happens only in LibreOffice Writer, other applications are running smoothly. Sorry my english. Bye. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libreoffice-core 1:4.2.3~rc3-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 13 17:29:50 2014 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2014-04-13 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140412) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1307226/+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 1308193] Re: Upcoming recurring alarms on wrong day
** Changed in: indicator-datetime (Ubuntu) Assignee: (unassigned) = Charles Kerr (charlesk) ** Changed in: indicator-datetime (Ubuntu) Importance: Undecided = Medium -- 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/1308193 Title: Upcoming recurring alarms on wrong day Status in “indicator-datetime” package in Ubuntu: Confirmed Bug description: Open clock Set alarm, make it occur every working day - and today is Tuesday. Save alarm. Pull down indicator, observe that next alarm is shown as Mon not Wed which is tomorrow. Expectation would be that the indicator shows the next alarm, not the one 4 alarms away. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-datetime 13.10.0+14.04.20140408-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.1-0ubuntu2 Architecture: armhf Date: Tue Apr 15 18:35:01 2014 InstallationDate: Installed on 2014-04-15 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS - armhf (20140415.1) SourcePackage: indicator-datetime 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/1308193/+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 1308193] Re: Upcoming recurring alarms on wrong day
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-datetime (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 https://bugs.launchpad.net/bugs/1308193 Title: Upcoming recurring alarms on wrong day Status in “indicator-datetime” package in Ubuntu: Confirmed Bug description: Open clock Set alarm, make it occur every working day - and today is Tuesday. Save alarm. Pull down indicator, observe that next alarm is shown as Mon not Wed which is tomorrow. Expectation would be that the indicator shows the next alarm, not the one 4 alarms away. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-datetime 13.10.0+14.04.20140408-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.1-0ubuntu2 Architecture: armhf Date: Tue Apr 15 18:35:01 2014 InstallationDate: Installed on 2014-04-15 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS - armhf (20140415.1) SourcePackage: indicator-datetime 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/1308193/+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 1210077] Re: Screen freeze and garbled after resume from suspend
** Branch linked: lp:ubuntu/precise-proposed/nvidia-graphics- drivers-331-updates -- 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/1210077 Title: Screen freeze and garbled after resume from suspend Status in HWE Next Project: Fix Released Status in HWE Next trusty series: Fix Released Status in Unity: Fix Released Status in “nvidia-graphics-drivers-331” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-331” source package in Precise: Fix Committed Bug description: [Impact] Users of nvidia graphics drivers can see graphics freezes or corruption after suspend/resume. Switching to a VT and back to X can potentially solve freeze issues, but corruption may result. [Test Case] Suspend/Resume many times with nvidia graphics and see if the problem happens. [Regression Potential] This is already in Trusty. -- Perform regular suspend, either from system menu or close laptop lid, when system resuming from suspend, it will freeze. Switch to VT and back to X can solve freeze issue, but the screen are gabled and some character rendering are strange, however whole system can perform usual task. found affected graphics: gf108m gf117m gk107glm To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1210077/+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 1308037] Re: No results from application lens
Duplicate of bug #1295908? -- 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/1308037 Title: No results from application lens Status in “unity” package in Ubuntu: New Bug description: Unity is in a state where I don't get any results from the applications lens. This sometimes happens for one search but either re-entering the search or toggling the lens has always fixed it in the past for me. This time neither of these steps work. I'm attaching a bustle log of the problem in case that's helpful. I searched for spotify, which I've got installed, and got 0 results. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 15 13:29:40 2014 InstallationDate: Installed on 2012-10-07 (554 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121007) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-05-07 (343 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1308037/+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 1307701] Re: Unity does not get touch events when SDK apps running
can you reproduce on another touch screen? It seems to work fine on my XPS12 -- 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/1307701 Title: Unity does not get touch events when SDK apps running Status in OEM Priority Project: New Status in OEM Priority Project trusty series: New Status in “unity” package in Ubuntu: Confirmed Bug description: When running an SDK app on the desktop, it's not possible to use the touchscreen to move windows, use the launcher, etc. The SDK app seems to consume all touchscreen events. To reproduce: 1) On a desktop/laptop with a touchscreen (I am using a Dell XPS13), install 14.04 and check that the touchscreen works for moving windows 2) Install the camera-app package from universe (I have 2.9.1+14.04.20140331-0ubuntu1) 3) Launch the camera app 4) Touch once inside the camera-app window 5) Use the touchscreen to drag the camera-app window Expected results: You can move the camera-app window using the touchscreen Actual results: You cannot move the camera-app window, or perform any other touch tasks in unity, with the touchscreen This only affects touchscreen input - mouse/touchpad input is not affected This affects all apps written with the SDK (I tried camera-app, gallery-app, reminders-app). It's 100% reproducible. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Mon Apr 14 14:59:09 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-02 (132 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-02-12 (61 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1307701/+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 1308226] [NEW] unity package shouldn't ship gsettings schema in a versioned library package.
Public bug reported: This is a follow-up of bug 1193120. Shipping the schema in the versioned library package makes it difficult to depend on that schema from other packages. It should be moved to a common package, perhaps gsettings-desktop- schemas or gsettings-ubuntu-schemas, if possible. We need to investigate how this schema is being used, how tightly coupled it is to unity, etc. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140410-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 15 12:41:08 2014 InstallationDate: Installed on 2013-12-06 (130 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-12-06 (130 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Assignee: Robert Bruce Park (robru) Status: New ** Tags: amd64 apport-bug trusty -- 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/1308226 Title: unity package shouldn't ship gsettings schema in a versioned library package. Status in “unity” package in Ubuntu: New Bug description: This is a follow-up of bug 1193120. Shipping the schema in the versioned library package makes it difficult to depend on that schema from other packages. It should be moved to a common package, perhaps gsettings-desktop- schemas or gsettings-ubuntu-schemas, if possible. We need to investigate how this schema is being used, how tightly coupled it is to unity, etc. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140410-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 15 12:41:08 2014 InstallationDate: Installed on 2013-12-06 (130 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-12-06 (130 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1308226/+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 1307701] Re: Unity does not get touch events when SDK apps running
** Changed in: unity (Ubuntu) Assignee: (unassigned) = Stephen M. Webb (bregma) ** Changed in: unity (Ubuntu) Importance: Undecided = High ** Changed in: oem-priority/trusty 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/1307701 Title: Unity does not get touch events when SDK apps running Status in OEM Priority Project: New Status in OEM Priority Project trusty series: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: When running an SDK app on the desktop, it's not possible to use the touchscreen to move windows, use the launcher, etc. The SDK app seems to consume all touchscreen events. To reproduce: 1) On a desktop/laptop with a touchscreen (I am using a Dell XPS13), install 14.04 and check that the touchscreen works for moving windows 2) Install the camera-app package from universe (I have 2.9.1+14.04.20140331-0ubuntu1) 3) Launch the camera app 4) Touch once inside the camera-app window 5) Use the touchscreen to drag the camera-app window Expected results: You can move the camera-app window using the touchscreen Actual results: You cannot move the camera-app window, or perform any other touch tasks in unity, with the touchscreen This only affects touchscreen input - mouse/touchpad input is not affected This affects all apps written with the SDK (I tried camera-app, gallery-app, reminders-app). It's 100% reproducible. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Mon Apr 14 14:59:09 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-02 (132 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-02-12 (61 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1307701/+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 1308193] Re: Upcoming recurring alarms on wrong day
Looks like this might be a clock-app bug rather than an indicator- datetime one. Here's what gets saved in EDS' backend. Note that today is April 15 but the alarm's start date is stored as April 21 (DTSTART:20140421T06) phablet@ubuntu-phablet:~/.local/share/evolution/tasks/1397587814.2867.0@ubuntu-phablet$ date Tue Apr 15 19:54:29 UTC 2014 phablet@ubuntu-phablet:~/.local/share/evolution/tasks/1397587814.2867.0@ubuntu-phablet$ cat tasks.ics BEGIN:VCALENDAR CALSCALE:GREGORIAN PRODID:-//Ximian//NONSGML Evolution Calendar//EN VERSION:2.0 X-EVOLUTION-DATA-REVISION:2014-04-15T18:52:29.729672Z(2) BEGIN:VTODO UID:20140415T185226Z-2867-32011-2021-1@ubuntu-phablet DTSTAMP:20140415T185226Z DTSTART:20140421T06 DUE:20140421T06 RRULE;X-EVOLUTION-ENDDATE=19700101T00Z:FREQ=WEEKLY;COUNT=-1; BYDAY=MO,TU,WE,TH,FR SUMMARY:Alarm CREATED:20140415T185226Z LAST-MODIFIED:20140415T185226Z BEGIN:VALARM X-EVOLUTION-ALARM-UID:20140415T185226Z-2867-32011-2021-2@ubuntu-phablet ACTION:AUDIO ATTACH:/w== END:VALARM BEGIN:VALARM X-EVOLUTION-ALARM-UID:20140415T185226Z-2867-32011-2021-3@ubuntu-phablet ACTION:DISPLAY ATTACH:/woAQQBsAGEAcgBt END:VALARM END:VTODO END:VCALENDAR ** Also affects: ubuntu-clock-app (Ubuntu) Importance: Undecided Status: New ** Changed in: indicator-datetime (Ubuntu) Status: Confirmed = New ** Changed in: ubuntu-clock-app (Ubuntu) Importance: Undecided = Medium -- 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/1308193 Title: Upcoming recurring alarms on wrong day Status in “indicator-datetime” package in Ubuntu: New Status in “ubuntu-clock-app” package in Ubuntu: New Bug description: Open clock Set alarm, make it occur every working day - and today is Tuesday. Save alarm. Pull down indicator, observe that next alarm is shown as Mon not Wed which is tomorrow. Expectation would be that the indicator shows the next alarm, not the one 4 alarms away. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-datetime 13.10.0+14.04.20140408-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.1-0ubuntu2 Architecture: armhf Date: Tue Apr 15 18:35:01 2014 InstallationDate: Installed on 2014-04-15 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS - armhf (20140415.1) SourcePackage: indicator-datetime 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/1308193/+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 1308226] Re: unity package shouldn't ship gsettings schema in a versioned library package.
12:58 infinity robru: Whatever gets fixed for U, it would be lovely to also get it SRUed, if we can do it sanely. 12:58 infinity robru: It would make life nicer moving forward. ** Changed in: unity (Ubuntu) Milestone: None = later ** Changed in: unity (Ubuntu) Status: New = Triaged ** Changed in: unity (Ubuntu) Status: Triaged = 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/1308226 Title: unity package shouldn't ship gsettings schema in a versioned library package. Status in “unity” package in Ubuntu: Confirmed Bug description: This is a follow-up of bug 1193120. Shipping the schema in the versioned library package makes it difficult to depend on that schema from other packages. It should be moved to a common package, perhaps gsettings-desktop- schemas or gsettings-ubuntu-schemas, if possible. We need to investigate how this schema is being used, how tightly coupled it is to unity, etc. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140410-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 15 12:41:08 2014 InstallationDate: Installed on 2013-12-06 (130 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-12-06 (130 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1308226/+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 1307701] Re: Unity does not get touch events when SDK apps running
happens on the XPS12 too once you click _into_ an app some more observations: - once the bug is activated (by clicking into the touch app), all touch screen events seem to be either discarded (when not in the app surface) or consumed (when in app surface) - closing the app releases the events and the touch screen works fine again -- 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/1307701 Title: Unity does not get touch events when SDK apps running Status in OEM Priority Project: New Status in OEM Priority Project trusty series: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: When running an SDK app on the desktop, it's not possible to use the touchscreen to move windows, use the launcher, etc. The SDK app seems to consume all touchscreen events. To reproduce: 1) On a desktop/laptop with a touchscreen (I am using a Dell XPS13), install 14.04 and check that the touchscreen works for moving windows 2) Install the camera-app package from universe (I have 2.9.1+14.04.20140331-0ubuntu1) 3) Launch the camera app 4) Touch once inside the camera-app window 5) Use the touchscreen to drag the camera-app window Expected results: You can move the camera-app window using the touchscreen Actual results: You cannot move the camera-app window, or perform any other touch tasks in unity, with the touchscreen This only affects touchscreen input - mouse/touchpad input is not affected This affects all apps written with the SDK (I tried camera-app, gallery-app, reminders-app). It's 100% reproducible. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Mon Apr 14 14:59:09 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-02 (132 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-02-12 (61 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1307701/+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 1308130] Re: indicator-messages-service is waking up every 4 seconds adding inotifies on paths that don't exist
@Oliver, it would be surprising if upstart wouldn't get the same issue.
The problem here is that the mechanism provided by the kernel (inotify)
is not handling those usecases in a nice way, what client is using the
interface is not going to change that, you are just going to move the
wakeups to the upstart job (upstart might be able to reduce/share the
polling if several processes watch the same location though, but I'm
unsure that's the case here)
--
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/1308130
Title:
indicator-messages-service is waking up every 4 seconds adding
inotifies on paths that don't exist
Status in “indicator-messages” package in Ubuntu:
Confirmed
Bug description:
I've observed that an idle indicator-messages-services is waking up
every 4 seconds on a poll() and doing two inotify_add_watch() calls on
paths that don't exist, which wastes power on devices such as phones.
strace shows:
clock_gettime(CLOCK_MONOTONIC, {10117, 224455428}) = 0
poll([{fd=8, events=POLLIN}, {fd=9, events=POLLIN}], 2, 3991) = 0 (Timeout)
clock_gettime(CLOCK_MONOTONIC, {10121, 224516469}) = 0
inotify_add_watch(9, /usr/local/share/applications,
IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR)
= -1 ENOENT (No such file or directory)
inotify_add_watch(9, /usr/share/ubuntu-touch/applications,
IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR)
= -1 ENOENT (No such file or directory)
clock_gettime(CLOCK_MONOTONIC, {10121, 232085521}) = 0
poll([{fd=8, events=POLLIN}, {fd=9, events=POLLIN}], 2, 3984) = 0 (Timeout)
clock_gettime(CLOCK_MONOTONIC, {10125, 222593684}) = 0
inotify_add_watch(9, /usr/local/share/applications,
IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR)
= -1 ENOENT (No such file or directory)
inotify_add_watch(9, /usr/share/ubuntu-touch/applications,
IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR)
= -1 ENOENT (No such file or directory)
clock_gettime(CLOCK_MONOTONIC, {10125, 229094524}) = 0
Can these redundant polling checks be reduced or removed? Polling
every 4 seconds is a little bit heavy handed IMHO.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1308130/+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 1307701] Re: Unity does not get touch events when SDK apps running
also, happens with a non-SDK app, e.g. from http://qt-
project.org/doc/qt-5/qml-tutorial2.html
import QtQuick 2.0
Item {
id: container
property alias cellColor: rectangle.color
signal clicked(color cellColor)
width: 40; height: 25
Rectangle {
id: rectangle
border.color: white
anchors.fill: parent
}
MouseArea {
anchors.fill: parent
onClicked: container.clicked(container.cellColor)
}
}
--
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/1307701
Title:
Unity does not get touch events when SDK apps running
Status in OEM Priority Project:
New
Status in OEM Priority Project trusty series:
Confirmed
Status in “unity” package in Ubuntu:
Confirmed
Bug description:
When running an SDK app on the desktop, it's not possible to use the
touchscreen to move windows, use the launcher, etc. The SDK app seems
to consume all touchscreen events.
To reproduce:
1) On a desktop/laptop with a touchscreen (I am using a Dell XPS13), install
14.04 and check that the touchscreen works for moving windows
2) Install the camera-app package from universe (I have
2.9.1+14.04.20140331-0ubuntu1)
3) Launch the camera app
4) Touch once inside the camera-app window
5) Use the touchscreen to drag the camera-app window
Expected results:
You can move the camera-app window using the touchscreen
Actual results:
You cannot move the camera-app window, or perform any other touch tasks in
unity, with the touchscreen
This only affects touchscreen input - mouse/touchpad input is not
affected
This affects all apps written with the SDK (I tried camera-app,
gallery-app, reminders-app). It's 100% reproducible.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.0+14.04.20140411-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu2
Architecture: amd64
CompizPlugins:
[core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
CurrentDesktop: Unity
Date: Mon Apr 14 14:59:09 2014
DistributionChannelDescriptor:
# This is a distribution channel descriptor
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-precise-amd64-20130203-1
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-12-02 (132 days ago)
InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary
20130203-13:50
SourcePackage: unity
UpgradeStatus: Upgraded to trusty on 2014-02-12 (61 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1307701/+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 1308193] Re: Upcoming recurring alarms on wrong day
This value is being set in qtorganizer5-eds by QOrganizerEDSEngine::parseTodoStartTime(), which gets the value from a call to a QOrganizerTodoTime.startDateTime(). Looks like the QOrganizerTodo gets set in ubuntu-ui- toolkit/modules/Ubuntu/Components/plugin/adapters/alarmsadapter_organizer.cpp in AlarmsAdapter::organizerEventFromAlarmData(), which sets the start date and due date from the same value, alarm.date, where alarm is an AlarmData and date a simple property that gets set in UCAlarm::setDate(date)'s call to d-rawData-date = date. So at that point I think we're back to the qml. Oddly, ubuntu-clock-app/alarm/AddAlarmPage.qml's function to save a new alarm, saveNewAlarm(), creates a new Date object, updates its time fields based on the user's choices, and appears to leave the date fields unchanged...? I'm less sure about the steps in ubuntu-clock-app though -- nik90, could you give this a little triage? ** Changed in: ubuntu-clock-app (Ubuntu) Assignee: (unassigned) = Nekhelesh Ramananthan (nik90) -- 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/1308193 Title: Upcoming recurring alarms on wrong day Status in “indicator-datetime” package in Ubuntu: New Status in “ubuntu-clock-app” package in Ubuntu: New Bug description: Open clock Set alarm, make it occur every working day - and today is Tuesday. Save alarm. Pull down indicator, observe that next alarm is shown as Mon not Wed which is tomorrow. Expectation would be that the indicator shows the next alarm, not the one 4 alarms away. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-datetime 13.10.0+14.04.20140408-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.1-0ubuntu2 Architecture: armhf Date: Tue Apr 15 18:35:01 2014 InstallationDate: Installed on 2014-04-15 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS - armhf (20140415.1) SourcePackage: indicator-datetime 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/1308193/+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 1307701] Re: Unity does not get touch events when SDK apps running
Olli reproduced this with a simple QML app -- 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/1307701 Title: Unity does not get touch events when SDK apps running Status in OEM Priority Project: New Status in OEM Priority Project trusty series: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: When running an SDK app on the desktop, it's not possible to use the touchscreen to move windows, use the launcher, etc. The SDK app seems to consume all touchscreen events. To reproduce: 1) On a desktop/laptop with a touchscreen (I am using a Dell XPS13), install 14.04 and check that the touchscreen works for moving windows 2) Install the camera-app package from universe (I have 2.9.1+14.04.20140331-0ubuntu1) 3) Launch the camera app 4) Touch once inside the camera-app window 5) Use the touchscreen to drag the camera-app window Expected results: You can move the camera-app window using the touchscreen Actual results: You cannot move the camera-app window, or perform any other touch tasks in unity, with the touchscreen This only affects touchscreen input - mouse/touchpad input is not affected This affects all apps written with the SDK (I tried camera-app, gallery-app, reminders-app). It's 100% reproducible. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Mon Apr 14 14:59:09 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-02 (132 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-02-12 (61 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1307701/+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 1308130] Re: indicator-messages-service is waking up every 4 seconds adding inotifies on paths that don't exist
what i meant is that the upstart file watcher is running anyway ... so
you could as well just use it and not have the indicator duplicate the
file watching functionality
--
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/1308130
Title:
indicator-messages-service is waking up every 4 seconds adding
inotifies on paths that don't exist
Status in “indicator-messages” package in Ubuntu:
Confirmed
Bug description:
I've observed that an idle indicator-messages-services is waking up
every 4 seconds on a poll() and doing two inotify_add_watch() calls on
paths that don't exist, which wastes power on devices such as phones.
strace shows:
clock_gettime(CLOCK_MONOTONIC, {10117, 224455428}) = 0
poll([{fd=8, events=POLLIN}, {fd=9, events=POLLIN}], 2, 3991) = 0 (Timeout)
clock_gettime(CLOCK_MONOTONIC, {10121, 224516469}) = 0
inotify_add_watch(9, /usr/local/share/applications,
IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR)
= -1 ENOENT (No such file or directory)
inotify_add_watch(9, /usr/share/ubuntu-touch/applications,
IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR)
= -1 ENOENT (No such file or directory)
clock_gettime(CLOCK_MONOTONIC, {10121, 232085521}) = 0
poll([{fd=8, events=POLLIN}, {fd=9, events=POLLIN}], 2, 3984) = 0 (Timeout)
clock_gettime(CLOCK_MONOTONIC, {10125, 222593684}) = 0
inotify_add_watch(9, /usr/local/share/applications,
IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR)
= -1 ENOENT (No such file or directory)
inotify_add_watch(9, /usr/share/ubuntu-touch/applications,
IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR)
= -1 ENOENT (No such file or directory)
clock_gettime(CLOCK_MONOTONIC, {10125, 229094524}) = 0
Can these redundant polling checks be reduced or removed? Polling
every 4 seconds is a little bit heavy handed IMHO.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1308130/+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 1308193] Re: Upcoming recurring alarms on wrong day
I think I may have found the bug. On reading the SDK Alarms API documentation, it specifies that if the daysOfTheWeek are specified, then it will strive to trigger the alarms on that day. Let me illustrate an example here to explain. Assume that the current date and time is Monday 15th April 10:00 AM, if the user tries to set an alarm to trigger everyday Mon-Fri at 08:30 AM, the alarm cannot trigger on 15th April Monday since that time has already passed. So the alarms API then tries the next possible date which is 21st April Monday at 08:30 AM which is a valid time instead of triggering the alarm on Tuesday 16th April. So this is a bug in the ubuntu clock app due to the way it creates new alarms. ** Changed in: ubuntu-clock-app (Ubuntu) Status: New = Confirmed ** Also affects: ubuntu-clock-app Importance: Undecided Status: New ** Changed in: ubuntu-clock-app Status: New = Confirmed ** Changed in: ubuntu-clock-app Importance: Undecided = High ** Changed in: ubuntu-clock-app Assignee: (unassigned) = Nekhelesh Ramananthan (nik90) ** Changed in: ubuntu-clock-app Milestone: None = backlog ** Tags added: alarm -- 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/1308193 Title: Upcoming recurring alarms on wrong day Status in Clock application for Ubuntu devices: Confirmed Status in “indicator-datetime” package in Ubuntu: New Status in “ubuntu-clock-app” package in Ubuntu: Confirmed Bug description: Open clock Set alarm, make it occur every working day - and today is Tuesday. Save alarm. Pull down indicator, observe that next alarm is shown as Mon not Wed which is tomorrow. Expectation would be that the indicator shows the next alarm, not the one 4 alarms away. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-datetime 13.10.0+14.04.20140408-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.1-0ubuntu2 Architecture: armhf Date: Tue Apr 15 18:35:01 2014 InstallationDate: Installed on 2014-04-15 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS - armhf (20140415.1) SourcePackage: indicator-datetime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1308193/+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 1308265] [NEW] First password letter not registered in lockscreen if screen off
Public bug reported: With the new lockscreen, if my screen is off, I just start typing, every time my password is too short. It looks like the first key only triggers the screen on and does not go to the input field. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140414.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 15 23:59:08 2014 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- 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/1308265 Title: First password letter not registered in lockscreen if screen off Status in “unity” package in Ubuntu: New Bug description: With the new lockscreen, if my screen is off, I just start typing, every time my password is too short. It looks like the first key only triggers the screen on and does not go to the input field. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140414.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 15 23:59:08 2014 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1308265/+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 1291088] Re: Doesn't unlock when coming back from the greeter
Looks fixed to me! -- 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/1291088 Title: Doesn't unlock when coming back from the greeter Status in Unity: Fix Committed Status in “unity” package in Ubuntu: Fix Released Bug description: Using the new unity-lock-screen from the current candidate version: - run unity on a system with multiple users - click on another user in indicator-session - the greeter is displayed with that user selected, so you can type the password to log in - select back your user and enter the password to unlock the session - what happens: the session is unlocked then locked again just after that - what should happen: the session should stay unlocked To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1291088/+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 1208019] Re: Eclipse menus doesn't show up in Saucy
This bug is still present in last daily build of ubuntu 14.04 LTS (16/04/2014). Is it planned to be solved before final release? Thx -- 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/1208019 Title: Eclipse menus doesn't show up in Saucy Status in Eclipse: Confirmed Status in Unity GTK+ module: In Progress Status in “oracle-jdk7-installer” package in Ubuntu: Triaged Status in “unity-gtk-module” package in Ubuntu: Fix Released Bug description: HOW TO REPRODUCE 1. Run Eclipse, Gimp or Inkscape. 2. Move the cursor to the top of the screen. 3. Click on any of the menu items (File, Edit, Navigate, ...) ** EXPECTED BEHAVIOUR ** - The content of the submenus show up. ** REAL BEHAVIOUR ** - Only the top-level headers are available. - Nothing happens when clicking on them - They don't show up in the HUD either. *** WORK-AROUND *** To modify /usr/share/applications/eclipse.desktop to look like this: [Desktop Entry] Type=Application Name=Eclipse Comment=Eclipse Integrated Development Environment Icon=eclipse Exec=env UBUNTU_MENUPROXY= eclipse Terminal=false Categories=Development;IDE;Java; RELEVANT DETAILS - Doesn't affect Ubuntu releases prior to 13.10. ** TECHNICAL INFO ** ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: eclipse 3.8.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic i686 ApportVersion: 2.11-0ubuntu1 Architecture: i386 Date: Sat Aug 3 17:03:55 2013 InstallationDate: Installed on 2013-07-08 (25 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130708) MarkForUpload: True PackageArchitecture: all SourcePackage: eclipse UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/eclipse/+bug/1208019/+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 1199571] Re: compiz crashed with SIGSEGV in af_latin_hints_compute_edges()
Brilliant work, Alexey. -- 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/1199571 Title: compiz crashed with SIGSEGV in af_latin_hints_compute_edges() Status in “cairo” package in Ubuntu: New Status in “unity” package in Ubuntu: Triaged Bug description: Fresh dist-upgrade; brought up the dash, typed term; single clicked on the terminal app and _bang_. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity 7.0.2+13.10.20130705.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-2.10-generic 3.10.0 Uname: Linux 3.10.0-2-generic x86_64 ApportVersion: 2.10.2-0ubuntu4 Architecture: amd64 Date: Tue Jul 9 17:47:10 2013 EcryptfsInUse: Yes ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2013-06-06 (33 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True ProcCmdline: compiz ProcEnviron: LANGUAGE=en_US PATH=(custom, user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7ff3b4ed7a10:mov%rdx,0x10(%rax) PC (0x7ff3b4ed7a10) ok source %rdx ok destination 0x10(%rax) (0x0010) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 FT_Load_Glyph () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 Title: compiz crashed with SIGSEGV in FT_Load_Glyph() 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/cairo/+bug/1199571/+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 1306112] Re: calendar sync causing 100% cpu and does not complete
** Branch linked: lp:ubuntu/trusty-proposed/qtorganizer5-eds -- 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/1306112 Title: calendar sync causing 100% cpu and does not complete Status in Sync monitor for Ubuntu Touch: In Progress Status in “indicator-datetime” package in Ubuntu: In Progress Status in “qtorganizer5-eds” package in Ubuntu: New Status in “sync-monitor” package in Ubuntu: New Bug description: test using canonical google account this is the problem i'm seeing with the canonical account the calendar sync starts to run first, and it gets about progress of 70 and then evolution-calendar-factory starts consuming all the CPU - 100% (run top -d1) and at the same time the sync-monitor.log shows an infinite number of messages about static void ViewWatcher::onObjectsAdded(ECalClientView*, GSList*, ViewWatcher*) 0x15468a8 virtual QListQtOrganizer::QOrganizerCollection QOrganizerEDSEngine::collections(QtOrganizer::QOrganizerManager::Error*) virtual bool QOrganizerEDSEngine::startRequest(QtOrganizer::QOrganizerAbstractRequest*) virtual bool QOrganizerEDSEngine::waitForRequestFinished(QtOrganizer::QOrganizerAbstractRequest*, int) syn requested for account: bill.fil...@canonical.com calendar Account aready in the queue The sync never finishes, seems that evolution process is stuck. I have to kill it. http://pastebin.ubuntu.com/7231364/ Seems we might be in a loop when calendar events are getting added because of the sync we see tons of messages in the sync-monitor log maybe we're not ignoring the events correctly? or maybe it's a problem is the calendar has a recurring event? seems to cause infinite loop. This one is critical. To manage notifications about this bug go to: https://bugs.launchpad.net/sync-monitor/+bug/1306112/+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 1208019] Re: Eclipse menus doesn't show up in Saucy
Hi José, is the problem that some of the menus disappear after some Eclipse usage? Do you happen to know if there's an easy way to replicate that problem? -- 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/1208019 Title: Eclipse menus doesn't show up in Saucy Status in Eclipse: Confirmed Status in Unity GTK+ module: In Progress Status in “oracle-jdk7-installer” package in Ubuntu: Triaged Status in “unity-gtk-module” package in Ubuntu: Fix Released Bug description: HOW TO REPRODUCE 1. Run Eclipse, Gimp or Inkscape. 2. Move the cursor to the top of the screen. 3. Click on any of the menu items (File, Edit, Navigate, ...) ** EXPECTED BEHAVIOUR ** - The content of the submenus show up. ** REAL BEHAVIOUR ** - Only the top-level headers are available. - Nothing happens when clicking on them - They don't show up in the HUD either. *** WORK-AROUND *** To modify /usr/share/applications/eclipse.desktop to look like this: [Desktop Entry] Type=Application Name=Eclipse Comment=Eclipse Integrated Development Environment Icon=eclipse Exec=env UBUNTU_MENUPROXY= eclipse Terminal=false Categories=Development;IDE;Java; RELEVANT DETAILS - Doesn't affect Ubuntu releases prior to 13.10. ** TECHNICAL INFO ** ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: eclipse 3.8.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic i686 ApportVersion: 2.11-0ubuntu1 Architecture: i386 Date: Sat Aug 3 17:03:55 2013 InstallationDate: Installed on 2013-07-08 (25 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130708) MarkForUpload: True PackageArchitecture: all SourcePackage: eclipse UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/eclipse/+bug/1208019/+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 1306112] Re: calendar sync causing 100% cpu and does not complete
This bug was fixed in the package qtorganizer5-eds - 0.1.1+14.04.20140415.1-0ubuntu1 --- qtorganizer5-eds (0.1.1+14.04.20140415.1-0ubuntu1) trusty; urgency=low [ Renato Araujo Oliveira Filho ] * Optimize eventid parse, and avoid memory leak. (LP: #1306112) * Used alarm component description as message field for visual reminders. (LP: #1284375) * Implemented support to update recurrence items with different modes. All (E_CAL_OBJ_MOD_ALL);. A single instance (E_CAL_OBJ_MOD_THIS),. A specific set of instances (E_CAL_OBJ_MOD_THIS_AND_PRIOR and E_CAL_OBJ_MOD_THIS_AND_FUTURE) (LP: #1283859) * Fixed recurrence date limit parse. (LP: #1292554) * Removed all debug messages. (LP: #1294426) -- Ubuntu daily release ps-jenk...@lists.canonical.com Tue, 15 Apr 2014 19:43:13 + ** Changed in: qtorganizer5-eds (Ubuntu) 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 https://bugs.launchpad.net/bugs/1306112 Title: calendar sync causing 100% cpu and does not complete Status in Sync monitor for Ubuntu Touch: In Progress Status in “indicator-datetime” package in Ubuntu: In Progress Status in “qtorganizer5-eds” package in Ubuntu: Fix Released Status in “sync-monitor” package in Ubuntu: New Bug description: test using canonical google account this is the problem i'm seeing with the canonical account the calendar sync starts to run first, and it gets about progress of 70 and then evolution-calendar-factory starts consuming all the CPU - 100% (run top -d1) and at the same time the sync-monitor.log shows an infinite number of messages about static void ViewWatcher::onObjectsAdded(ECalClientView*, GSList*, ViewWatcher*) 0x15468a8 virtual QListQtOrganizer::QOrganizerCollection QOrganizerEDSEngine::collections(QtOrganizer::QOrganizerManager::Error*) virtual bool QOrganizerEDSEngine::startRequest(QtOrganizer::QOrganizerAbstractRequest*) virtual bool QOrganizerEDSEngine::waitForRequestFinished(QtOrganizer::QOrganizerAbstractRequest*, int) syn requested for account: bill.fil...@canonical.com calendar Account aready in the queue The sync never finishes, seems that evolution process is stuck. I have to kill it. http://pastebin.ubuntu.com/7231364/ Seems we might be in a loop when calendar events are getting added because of the sync we see tons of messages in the sync-monitor log maybe we're not ignoring the events correctly? or maybe it's a problem is the calendar has a recurring event? seems to cause infinite loop. This one is critical. To manage notifications about this bug go to: https://bugs.launchpad.net/sync-monitor/+bug/1306112/+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 1306112] Re: calendar sync causing 100% cpu and does not complete
This bug was fixed in the package sync-monitor - 0.1+14.04.20140415.3-0ubuntu1 --- sync-monitor (0.1+14.04.20140415.3-0ubuntu1) trusty; urgency=low [ Renato Araujo Oliveira Filho ] * Force sync to start immediately if use dbus call. (LP: #1306070) * Keep a collection cache to compare with changed events. (LP: #1306112) * If the sync fails use the last sync mode in the next sync. (LP: #1306096) -- Ubuntu daily release ps-jenk...@lists.canonical.com Tue, 15 Apr 2014 22:20:51 + ** Branch linked: lp:ubuntu/trusty-proposed/syncevolution ** Changed in: sync-monitor (Ubuntu) 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 https://bugs.launchpad.net/bugs/1306112 Title: calendar sync causing 100% cpu and does not complete Status in Sync monitor for Ubuntu Touch: In Progress Status in “indicator-datetime” package in Ubuntu: In Progress Status in “qtorganizer5-eds” package in Ubuntu: Fix Released Status in “sync-monitor” package in Ubuntu: Fix Released Bug description: test using canonical google account this is the problem i'm seeing with the canonical account the calendar sync starts to run first, and it gets about progress of 70 and then evolution-calendar-factory starts consuming all the CPU - 100% (run top -d1) and at the same time the sync-monitor.log shows an infinite number of messages about static void ViewWatcher::onObjectsAdded(ECalClientView*, GSList*, ViewWatcher*) 0x15468a8 virtual QListQtOrganizer::QOrganizerCollection QOrganizerEDSEngine::collections(QtOrganizer::QOrganizerManager::Error*) virtual bool QOrganizerEDSEngine::startRequest(QtOrganizer::QOrganizerAbstractRequest*) virtual bool QOrganizerEDSEngine::waitForRequestFinished(QtOrganizer::QOrganizerAbstractRequest*, int) syn requested for account: bill.fil...@canonical.com calendar Account aready in the queue The sync never finishes, seems that evolution process is stuck. I have to kill it. http://pastebin.ubuntu.com/7231364/ Seems we might be in a loop when calendar events are getting added because of the sync we see tons of messages in the sync-monitor log maybe we're not ignoring the events correctly? or maybe it's a problem is the calendar has a recurring event? seems to cause infinite loop. This one is critical. To manage notifications about this bug go to: https://bugs.launchpad.net/sync-monitor/+bug/1306112/+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 727902] Re: Launcher icon highlighting should not switch off as soon the cursor moves after the app spread appears.
** Changed in: unity Milestone: None = 7.2.1 ** Changed in: unity Assignee: Andrea Azzarone (andyrock) = Marco Trevisan (Treviño) (3v1n0) ** Changed in: unity (Ubuntu) Assignee: Andrea Azzarone (andyrock) = Marco Trevisan (Treviño) (3v1n0) ** Changed in: unity Status: Triaged = In Progress ** Changed in: unity (Ubuntu) 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/727902 Title: Launcher icon highlighting should not switch off as soon the cursor moves after the app spread appears. Status in Ayatana Design: Fix Committed Status in Unity: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: Description. When a file is dragged and held over a application icon in the Launcher a spread of the app windows appear. The user can then drag and drop the file on to one of the windows to specify the window in which they would like the file to be loaded. The bug is that after the spread appears, any movement of the mouse switches off the selective highlighting and dimming of valid/non-valid drop receptacles. Desired behaviour - The highlighting and dimming of Launcher icons should persist until the user drops the file. - Note that the 'spread when a item is held over a launcher icon' behaviour seems to be broken in the Oneiric final freeze release (nothing happens). To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/727902/+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 607796] Re: Launcher, Window management - Dragging and holding a selection over an entry in the Launcher should spread out windows belonging to that application
** Changed in: unity Milestone: backlog = 7.2.1 ** Changed in: unity (Ubuntu) Assignee: (unassigned) = Marco Trevisan (Treviño) (3v1n0) ** Changed in: unity Status: Triaged = In Progress ** Changed in: unity (Ubuntu) Status: Triaged = In Progress ** Also affects: compiz Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/607796 Title: Launcher, Window management - Dragging and holding a selection over an entry in the Launcher should spread out windows belonging to that application Status in Ayatana Design: Fix Committed Status in Compiz: New Status in One Hundred Papercuts: Fix Released Status in Unity: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: If the user drags and hold a file over a running application in the Launcher, all the windows of that application should be shown with the spread. The user should then be able to drag and drop the file in a windows in the spread to load the file into that specific window. Bug #727903 needs to be fixed at the same time. --- History: This bug had been previously fixed as buggybutclosed for Unity on 2011-04-18, leaving this function with other bugs: https://bugs.launchpad.net/ayatana-design/+bug/727903 https://bugs.launchpad.net/ayatana-design/+bug/727904 https://bugs.launchpad.net/ayatana-design/+bug/727902 https://bugs.launchpad.net/ayatana-design/+bug/764424 https://bugs.launchpad.net/ayatana-design/+bug/832988 On 2011-10-18, it was reopened for regression in Oneiric. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/607796/+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 832988] Re: Launcher - a spread can accidentally be triggered during the 'dragging and dropping behind the Launcher' interaction
** Tags added: dnd -- 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/832988 Title: Launcher - a spread can accidentally be triggered during the 'dragging and dropping behind the Launcher' interaction Status in Ayatana Design: Fix Committed Status in Unity: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: To reproduce try dragging a file behind the launcher over a launcher icon that has 2 or more windows open and is a valid drop target. Frequently a spread will be accidentally triggered. Desired Resolution: - Block the triggering of a spread when the user is dragging a file and their cursor is positioned on the far left pixel of the screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/832988/+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
