[Dx-packages] [Bug 1359249] Re: Launching PAVUControl works from Xubuntu, but not from Xfce
same as #1443229.
I investigate the source code of indicator-sound, and find that in
src/service.vala:
var env = Environment.get_variable ("DESKTOP_SESSION");
string cmd;
if (env == "xubuntu" || env == "ubuntustudio")
cmd = "pavucontrol";
else
I think you would support more desktop environment such as XFCE by
adding " || env == "xfce""
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-sound in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1359249
Title:
Launching PAVUControl works from Xubuntu, but not from Xfce
Status in indicator-sound package in Ubuntu:
Confirmed
Bug description:
In Xubuntu 14.04 when clicking the sound indicator and choosing "Sound
Settings" Pavucontrol is launched, but it does not get launched in the
same scenario when the session "Xfce" is launched instead, with the
same settings. In fact I installed the xfce4 package on top of
Xubuntu's and launched it. Both xsession files list the same thing to
start it, so is indicator only choosing to work on whitelisted
sessions?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1359249/+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 1443774] [NEW] Horizontal scrolling is backwards
Public bug reported: Don't know where to report this specifically, sorry. In native gnome applications (file manager, gedit, etc), scrolling horizontally via Trackpoint middle-button scrolling is backwards: * Middle button + trackpoint move up = scroll up (expected) * Middle button + trackpoint move down = scroll down (expected) * Middle button + trackpoint move left = scroll right (backwards) * Middle button + trackpoint move right = scroll left (backwards) Scolling horizontally in Firefox and Chromium work as expected. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150410.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3 Uname: Linux 3.19.0-13-generic x86_64 ApportVersion: 2.17-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Apr 13 23:36:58 2015 InstallationDate: Installed on 2015-03-07 (38 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: unity UpgradeStatus: Upgraded to vivid on 2015-03-29 (16 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages vivid -- 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/1443774 Title: Horizontal scrolling is backwards Status in unity package in Ubuntu: New Bug description: Don't know where to report this specifically, sorry. In native gnome applications (file manager, gedit, etc), scrolling horizontally via Trackpoint middle-button scrolling is backwards: * Middle button + trackpoint move up = scroll up (expected) * Middle button + trackpoint move down = scroll down (expected) * Middle button + trackpoint move left = scroll right (backwards) * Middle button + trackpoint move right = scroll left (backwards) Scolling horizontally in Firefox and Chromium work as expected. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150410.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3 Uname: Linux 3.19.0-13-generic x86_64 ApportVersion: 2.17-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Apr 13 23:36:58 2015 InstallationDate: Installed on 2015-03-07 (38 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: unity UpgradeStatus: Upgraded to vivid on 2015-03-29 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1443774/+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 1391989] Re: When switching desktops Hangouts always steals focus
This bug could be a duplicate of Bug #1125442 -- 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/1391989 Title: When switching desktops Hangouts always steals focus Status in Unity: New Status in unity package in Ubuntu: Confirmed Bug description: When I switch to a desktop that has the hangouts "window" on it, it steals the focus. Steps to repeat: * Desktop 1 has a terminal and the hangouts window * Type in the terminal * Switch to desktop 2 (using CTRL+ALT+RightArrow) * Switch back to desktop 1 * Continue typing in the terminal Outcome: Nothing happens in the terminal because your focus is on hangouts (as visible in the desktop title bar) Expected: The terminal keeps focus This is just one example (switching desktops) but there seems to be lots of different ways in which hangouts steals focus. It's not a traditional window so I don't see options to disable "always on top" if that's what's happening. I have tried to update the CCSM>General>Focus & Raise Behavior to set up focus prevention to no effect. See also: * https://askubuntu.com/questions/547328/google-hangouts-window-steals-focus-when-switching-desktops * https://productforums.google.com/forum/#!category-topic/hangouts/i-found-a-bug/feature-other/desktop-other/chrome-extension/wC-PJXBmGQU To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1391989/+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 1391989] Re: When switching desktops Hangouts always steals focus
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/1391989 Title: When switching desktops Hangouts always steals focus Status in Unity: New Status in unity package in Ubuntu: Confirmed Bug description: When I switch to a desktop that has the hangouts "window" on it, it steals the focus. Steps to repeat: * Desktop 1 has a terminal and the hangouts window * Type in the terminal * Switch to desktop 2 (using CTRL+ALT+RightArrow) * Switch back to desktop 1 * Continue typing in the terminal Outcome: Nothing happens in the terminal because your focus is on hangouts (as visible in the desktop title bar) Expected: The terminal keeps focus This is just one example (switching desktops) but there seems to be lots of different ways in which hangouts steals focus. It's not a traditional window so I don't see options to disable "always on top" if that's what's happening. I have tried to update the CCSM>General>Focus & Raise Behavior to set up focus prevention to no effect. See also: * https://askubuntu.com/questions/547328/google-hangouts-window-steals-focus-when-switching-desktops * https://productforums.google.com/forum/#!category-topic/hangouts/i-found-a-bug/feature-other/desktop-other/chrome-extension/wC-PJXBmGQU To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1391989/+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 1390625] Re: mouse cursor gets corrupted
when my cursor got deformed then i tried to drag the same icon again and it got corrected.using elementary os freya. -- 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/1390625 Title: mouse cursor gets corrupted Status in elementary OS: Confirmed Status in Ubuntu UX bugs: New Status in Unity: Invalid Status in unity package in Ubuntu: Confirmed Bug description: In Ubuntu 14.10, the mouse cursor graphic gets corrupted under certain occasions. It then looks flipped, sheared or shows fragments of a previous cursor. * when switching the cursor them forth and back in Gnome Tweak Tool * when drag&dropping a document icon Maybe related, the cursor does not always show the correct image scale on a high-dpi display (this was working right in 14.04). For example after login, or when hovering specific areas, or on mouse down to start a drag&drop, the cursor appears 1/4 the expected size. Attached is a photo of a corrupted cursor (whereas a screenshot with Gimp showed the uncorrupted cursor). ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 BootLog: * Setting up X socket directories... [400G [394G[ OK ] CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Nov 7 22:12:52 2014 DistUpgraded: 2014-11-04 18:35:56,188 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3978] InstallationDate: Installed on 2014-02-02 (278 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140201) MachineType: LENOVO 20266 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed root=UUID=4bfb3686-b9f7-487d-81f6-eceb41097ad9 ro quiet splash acpi_backlight=vendor SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-11-04 (3 days ago) dmi.bios.date: 10/31/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN31WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Fri Nov 7 14:54:59 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: [dix] ELAN Touchscreen: unable to find touch point 1 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16970 vendor SDC xserver.version: 2:1.16.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1390625/+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 833729] Re: compiz crashed with SIGSEGV in CompositeScreen::compositingActive()
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/833729 Title: compiz crashed with SIGSEGV in CompositeScreen::compositingActive() Status in Compiz Core: Fix Released Status in Unity: Fix Released Status in Unity Distro Priority: Fix Released Status in compiz package in Ubuntu: Fix Released Status in unity package in Ubuntu: Confirmed Bug description: Crashes when used by /usr/lib/nux/unity_support_test ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: compiz-core 1:0.9.5.92+bzr2791-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3 Uname: Linux 3.0.0-9-generic x86_64 Architecture: amd64 CompizPlugins: [core,gtkloader,bailer,detection,composite,opengl,imgjpeg,compiztoolbox,decor,grid,mousepoll,wallpaper,resize,move,place,imgpng,imgsvg,gnomecompat,text,snap,wall,vpswitch,regex,session,thumbnail,unitymtgrabhandles,animation,expo,workarounds,ezoom,staticswitcher,fade,opacify,scale,unityshell] CompositorRunning: compiz CrashCounter: 1 Date: Thu Aug 25 07:50:21 2011 DistUpgraded: Log time: 2011-08-12 01:37:52.657651 DistroCodename: oneiric DistroVariant: ubuntu ExecutablePath: /usr/bin/compiz GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0487] InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110803.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 003: ID 04f2:b1d8 Chicony Electronics Co., Ltd MachineType: Acer Aspire 5742Z ProcCmdline: compiz ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-9-generic root=UUID=beff164b-12df-49d5-b810-f23d5495eb50 ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x7f2969ce32e0 <_ZN15CompositeScreen17compositingActiveEv>:mov0x48(%rdi),%rax PC (0x7f2969ce32e0) ok source "0x48(%rdi)" (0x0048) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: compiz StacktraceTop: CompositeScreen::compositingActive() () from /usr/lib/compiz/libcomposite.so PrivateCompositeWindow::PrivateCompositeWindow(CompWindow*, CompositeWindow*) () from /usr/lib/compiz/libcomposite.so CompositeWindow::CompositeWindow(CompWindow*) () from /usr/lib/compiz/libcomposite.so PluginClassHandler::get(CompWindow*) () from /usr/lib/compiz/libopengl.so PrivateGLWindow::PrivateGLWindow(CompWindow*, GLWindow*) () from /usr/lib/compiz/libopengl.so Title: compiz crashed with SIGSEGV in CompositeScreen::compositingActive() UpgradeStatus: Upgraded to oneiric on 2011-08-12 (13 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 01/10/2011 dmi.bios.vendor: Acer dmi.bios.version: V1.14 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Aspire 5742Z dmi.board.vendor: Acer dmi.board.version: V1.14 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.14 dmi.modalias: dmi:bvnAcer:bvrV1.14:bd01/10/2011:svnAcer:pnAspire5742Z:pvrV1.14:rvnAcer:rnAspire5742Z:rvrV1.14:cvnAcer:ct10:cvrV1.14: dmi.product.name: Aspire 5742Z dmi.product.version: V1.14 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.5.92+bzr2791-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu16 version.libdrm2: libdrm2 2.4.26-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3 version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20110811.g93fc084-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz-core/+bug/833729/+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 1443675] [NEW] Sound-indicator no detect my soundcard in Ubuntu 15.04 beta
Public bug reported: I have Asus Xonar DX sound work good but I only can control with alsamixer. Sound-indicator not detect sound card. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: indicator-sound 12.10.2+15.04.20150413-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3 Uname: Linux 3.19.0-13-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.17-0ubuntu2 Architecture: i386 CurrentDesktop: GNOME-Flashback:Unity Date: Tue Apr 14 00:09:56 2015 ExecutablePath: /usr/lib/i386-linux-gnu/indicator-sound/indicator-sound-service ProcEnviron: PATH=(custom, no user) SHELL=/bin/bash LANG=es_ES.UTF-8 LANGUAGE=es_ES XDG_RUNTIME_DIR= SourcePackage: indicator-sound UpgradeStatus: No upgrade log present (probably fresh install) upstart.indicator-sound.log: (process:1550): indicator-sound-WARNING **: service.vala:236: unable to launch sound settings: Falló al ejecutar el proceso hijo «gnome-control-center» (No existe el archivo o el directorio) ** Affects: indicator-sound (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 vivid -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1443675 Title: Sound-indicator no detect my soundcard in Ubuntu 15.04 beta Status in indicator-sound package in Ubuntu: New Bug description: I have Asus Xonar DX sound work good but I only can control with alsamixer. Sound-indicator not detect sound card. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: indicator-sound 12.10.2+15.04.20150413-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3 Uname: Linux 3.19.0-13-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.17-0ubuntu2 Architecture: i386 CurrentDesktop: GNOME-Flashback:Unity Date: Tue Apr 14 00:09:56 2015 ExecutablePath: /usr/lib/i386-linux-gnu/indicator-sound/indicator-sound-service ProcEnviron: PATH=(custom, no user) SHELL=/bin/bash LANG=es_ES.UTF-8 LANGUAGE=es_ES XDG_RUNTIME_DIR= SourcePackage: indicator-sound UpgradeStatus: No upgrade log present (probably fresh install) upstart.indicator-sound.log: (process:1550): indicator-sound-WARNING **: service.vala:236: unable to launch sound settings: Falló al ejecutar el proceso hijo «gnome-control-center» (No existe el archivo o el directorio) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1443675/+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 1390625] Re: mouse cursor gets corrupted
Having the same problem with elementary OS Freya on my Dell Latitude e4310. -- 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/1390625 Title: mouse cursor gets corrupted Status in elementary OS: Confirmed Status in Ubuntu UX bugs: New Status in Unity: Invalid Status in unity package in Ubuntu: Confirmed Bug description: In Ubuntu 14.10, the mouse cursor graphic gets corrupted under certain occasions. It then looks flipped, sheared or shows fragments of a previous cursor. * when switching the cursor them forth and back in Gnome Tweak Tool * when drag&dropping a document icon Maybe related, the cursor does not always show the correct image scale on a high-dpi display (this was working right in 14.04). For example after login, or when hovering specific areas, or on mouse down to start a drag&drop, the cursor appears 1/4 the expected size. Attached is a photo of a corrupted cursor (whereas a screenshot with Gimp showed the uncorrupted cursor). ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 BootLog: * Setting up X socket directories... [400G [394G[ OK ] CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Nov 7 22:12:52 2014 DistUpgraded: 2014-11-04 18:35:56,188 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3978] InstallationDate: Installed on 2014-02-02 (278 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140201) MachineType: LENOVO 20266 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed root=UUID=4bfb3686-b9f7-487d-81f6-eceb41097ad9 ro quiet splash acpi_backlight=vendor SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-11-04 (3 days ago) dmi.bios.date: 10/31/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN31WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Fri Nov 7 14:54:59 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: [dix] ELAN Touchscreen: unable to find touch point 1 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16970 vendor SDC xserver.version: 2:1.16.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1390625/+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 1443005] Re: Indicator shouldn't set volume on pulse/account service if the volume didn't change
This bug was fixed in the package indicator-sound - 12.10.2+15.04.20150413-0ubuntu1 --- indicator-sound (12.10.2+15.04.20150413-0ubuntu1) vivid; urgency=medium [ CI Train Bot ] * New rebuild forced. [ Ricardo Salveti de Araujo ] * volume-control-pulse: only set volume if value is indeed different and reason not from AS (LP: #1443005) [ Ted Gould ] * Fix stream property lookup to reliably signal multimedia streams (LP: #1436021) -- CI Train BotMon, 13 Apr 2015 06:02:32 + ** Changed in: indicator-sound (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1443005 Title: Indicator shouldn't set volume on pulse/account service if the volume didn't change Status in indicator-sound package in Ubuntu: Fix Released Bug description: current build number: 168 device name: mako channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-04-12 03:49:09 version version: 168 version ubuntu: 20150411 version device: 20150210 version custom: 20150411 This is a regression from RTM. The current logic doesn't check for the volume value before calling pulseaudio and account service when updating the volume variable. The consequence is that it will set the volume at least twice after you change it, since it will get a callback from account service, and that will result in another volume set with the exact same volume. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1443005/+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 1436021] Re: max volume warning for headphones not working on all devices
This bug was fixed in the package indicator-sound - 12.10.2+15.04.20150413-0ubuntu1 --- indicator-sound (12.10.2+15.04.20150413-0ubuntu1) vivid; urgency=medium [ CI Train Bot ] * New rebuild forced. [ Ricardo Salveti de Araujo ] * volume-control-pulse: only set volume if value is indeed different and reason not from AS (LP: #1443005) [ Ted Gould ] * Fix stream property lookup to reliably signal multimedia streams (LP: #1436021) -- CI Train BotMon, 13 Apr 2015 06:02:32 + ** Changed in: indicator-sound (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1436021 Title: max volume warning for headphones not working on all devices Status in indicator-sound package in Ubuntu: Fix Released Bug description: Works fine on krillin for rtm-14.09 & vivid does not work on Nexus4 (and other devices) on current vivid (and vivid from a couple of weeks ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1436021/+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 1436021] Re: max volume warning for headphones not working on all devices
** Branch linked: lp:ubuntu/vivid-proposed/indicator-sound -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1436021 Title: max volume warning for headphones not working on all devices Status in indicator-sound package in Ubuntu: In Progress Bug description: Works fine on krillin for rtm-14.09 & vivid does not work on Nexus4 (and other devices) on current vivid (and vivid from a couple of weeks ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1436021/+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 1443005] Re: Indicator shouldn't set volume on pulse/account service if the volume didn't change
** Branch linked: lp:ubuntu/vivid-proposed/indicator-sound -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1443005 Title: Indicator shouldn't set volume on pulse/account service if the volume didn't change Status in indicator-sound package in Ubuntu: In Progress Bug description: current build number: 168 device name: mako channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-04-12 03:49:09 version version: 168 version ubuntu: 20150411 version device: 20150210 version custom: 20150411 This is a regression from RTM. The current logic doesn't check for the volume value before calling pulseaudio and account service when updating the volume variable. The consequence is that it will set the volume at least twice after you change it, since it will get a callback from account service, and that will result in another volume set with the exact same volume. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1443005/+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 1419001] Re: Reminders trigger at the time of the event and not before by default
@popey can you get this scheduled ** Changed in: ubuntu-calendar-app Importance: Undecided => High ** Changed in: ubuntu-calendar-app Assignee: (unassigned) => Alan Pope (popey) ** Changed in: canonical-devices-system-image Assignee: Thomas Strehl (strehl-t) => Pat McGowan (pat-mcgowan) ** Changed in: canonical-devices-system-image Milestone: ww13-2015 => ww17-2015 -- 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/1419001 Title: Reminders trigger at the time of the event and not before by default Status in the base for Ubuntu mobile products: Confirmed Status in Calendar application for Ubuntu devices: Confirmed Status in indicator-datetime package in Ubuntu: Fix Released Status in qtorganizer5-eds package in Ubuntu: Invalid Bug description: Sync of google calendar. The Google calendar setting is set by default to notify 10 min prior to all meetings. Is it possible to get this default notification time from google with the sync? or can we add a setting for a default notification time in the calendar app? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1419001/+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 1378048] Re: Make music controls work in the sound indicator
** Changed in: canonical-devices-system-image Milestone: ww13-2015 => ww18-2015 -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1378048 Title: Make music controls work in the sound indicator Status in the base for Ubuntu mobile products: Confirmed Status in indicator-sound package in Ubuntu: Invalid Status in media-hub package in Ubuntu: Confirmed Bug description: Steps: 1. Play an album in the music player 2. Pull down sound indicator 3. Click forward button Observed: the music does not advance Expected: the music advances To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1378048/+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 1442166] Re: Calendar alarms rings forever if Low Battery dialog visible
** Changed in: canonical-devices-system-image Milestone: ww15-2015 => ww17-2015 -- 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/1442166 Title: Calendar alarms rings forever if Low Battery dialog visible Status in the base for Ubuntu mobile products: Confirmed Status in indicator-datetime package in Ubuntu: Confirmed Status in usensord package in Ubuntu: Confirmed Bug description: I'm on rtm build 258 on krillin Steps to reproduce: - let battery run down on phone (was sitting unplugged for 1 or 2 days) - in the morning, a calendar alarm starting ringing/vibrating and would not stop - when I looked at the phone, the screen was on and I see the Low Battery dialog - after dismissing the dialog, then I see the notification for the alarm, and only after 5-10 more seconds does the ringing stop Seems like while the Low Battery dialog is displayed it keeps the alarm ringing forever To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1442166/+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 1435830] Re: AP test failure: unity.tests.launcher.test_keynav.LauncherKeyNavTests.test_launcher_keynav_changes_panel(Single Monitor)
** 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/1435830
Title:
AP test failure:
unity.tests.launcher.test_keynav.LauncherKeyNavTests.test_launcher_keynav_changes_panel(Single
Monitor)
Status in Unity:
Fix Committed
Status in unity package in Ubuntu:
Fix Released
Bug description:
AP test fails consistently on every run.
FAIL:
unity.tests.launcher.test_keynav.LauncherKeyNavTests.test_launcher_keynav_changes_panel(Single
Monitor)
--
/var/log/syslog: {{{
Mar 19 16:18:46 xt2-14 com.canonical.Unity.Scope.File.Gdrive[1599]: login
finished
Mar 19 16:18:46 xt2-14 com.canonical.Unity.Scope.File.Gdrive[1599]: Got
token: ya29.OwFvVwItMuU7CMLyfIe22KhPBBlD_v62HgletZAa1aS8K5U1WNfqY6QL
Mar 19 16:18:46 xt2-14 com.canonical.Unity.Scope.File.Gdrive[1599]: Search
changed to: 'Has'
Mar 19 16:18:46 xt2-14 com.canonical.Unity.Scope.File.Gdrive[1599]: Searching
for: Has
Mar 19 16:18:46 xt2-14 com.canonical.Unity.Scope.File.Gdrive[1599]: Search
changed to: 'HasFocus'
Mar 19 16:18:46 xt2-14 com.canonical.Unity.Scope.File.Gdrive[1599]: Searching
for: HasFocus
}}}
unity-log: {{{
DEBUG 2015-03-19 16:18:41 unity.launcher.icon.application
ApplicationLauncherIcon.cpp:173 Compiz active now true
DEBUG 2015-03-19 16:18:41 unity.launcher.icon.application
ApplicationLauncherIcon.cpp:173 Terminal active now false
DEBUG 2015-03-19 16:18:52 unity.launcher.icon.application
ApplicationLauncherIcon.cpp:173 Compiz active now false
DEBUG 2015-03-19 16:18:52 unity.launcher.icon.application
ApplicationLauncherIcon.cpp:173 Terminal active now true
}}}
Traceback (most recent call last):
File
"/usr/lib/python2.7/dist-packages/unity/tests/launcher/test_keynav.py", line
247, in test_launcher_keynav_changes_panel
self.assertThat(self.unity.panels.get_active_panel().title,
Eventually(Equals("Search your computer and online sources")))
File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 423, in
assertThat
raise mismatch_error
MismatchError: After 10.0 seconds test on MenuView.panel_title failed: !=:
reference = u'Search your computer and online sources'
actual= u''
To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1435830/+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 1108956] Re: The dash closes when trying to switch from Command lens to home lens
** 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/1108956 Title: The dash closes when trying to switch from Command lens to home lens Status in Ayatana Design: Fix Committed Status in Unity: Fix Committed Status in Unity 7.2 series: Triaged Status in unity package in Ubuntu: Fix Released Bug description: When I open the command lens by pressing ALT+F2, if I press "Super" the dash is closed. It should not be closed, it should switch to the home lens instead. This is the suite of the bug 1019457 To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1108956/+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 1294864] Re: window snapping to the right edge is making the windows one or two pixels too narrow
** Also affects: unity Importance: Undecided Status: New ** Changed in: unity Status: New => Fix Committed ** Changed in: unity Importance: Undecided => Low ** Changed in: unity Assignee: (unassigned) => Stephen M. Webb (bregma) ** Changed in: unity Milestone: None => 7.3.3 ** Changed in: unity (Ubuntu) Importance: Undecided => Low ** Changed in: unity (Ubuntu) Assignee: (unassigned) => Stephen M. Webb (bregma) ** Also affects: unity/7.2 Importance: Undecided Status: New ** Changed in: unity/7.2 Status: New => Triaged ** Changed in: unity/7.2 Importance: Undecided => Low ** Changed in: unity/7.2 Assignee: (unassigned) => Stephen M. Webb (bregma) ** Changed in: unity/7.2 Milestone: None => 7.2.5 -- 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/1294864 Title: window snapping to the right edge is making the windows one or two pixels too narrow Status in Compiz: Fix Committed Status in Compiz 0.9.11 series: Triaged Status in Unity: Fix Committed Status in Unity 7.2 series: Triaged Status in compiz package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Bug description: Today is the first day I experience this. Window snapping has always worked perfectly on this machine. When snapping windows to the right side of the screen using either mouse or keyboard, any application's windows are not resized to fill up the screen to the right completely. vlc, nautilus, terminal, firefox, thundebird, chrome in rare cases, the resizing works correctly. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140318-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,gnomecompat,resize,regex,move,compiztoolbox,vpswitch,mousepoll,place,snap,grid,imgpng,animation,workarounds,wall,unitymtgrabhandles,session,fade,expo,scale,ezoom,unityshell] CurrentDesktop: Unity Date: Wed Mar 19 22:13:18 2014 InstallationDate: Installed on 2013-12-24 (85 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131220) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1294864/+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 998285] Re: Tapping alt-tab switches between windows of the same application sometimes
This bug was fixed in the package unity - 7.3.2+15.04.20150410.1-0ubuntu1 --- unity (7.3.2+15.04.20150410.1-0ubuntu1) vivid; urgency=medium [ Brandon Schaefer ] * When we get a launcher key press (ie. super key). We check if the command lens is open. If it is then just switch the lens to the home lens. This way we dont close the dash. (LP: #1108956) [ CI Train Bot ] * New rebuild forced. [ Gerry Boland ] * SwitcherController: add first selection mode property, to decide what to select at first (LP: #998285) [ Marco Trevisan (Treviño) ] * SwitcherController: add first selection mode property, to decide what to select at first (LP: #998285) * UnityScreen: terminate spread if active when initiating Switcher (LP: #1412001) [ Stephen M. Webb ] * (Ubuntu packaging) move the session migration scripts to Python3 (LP: #1440560) * fixed the Panel title string expected by Launcher keynav AP tests (LP: #1435830) * test_wm_keybindings: fix AP failures caused by upstream Compiz change (LP: #1294864) -- CI Train BotFri, 10 Apr 2015 21:59:12 + ** Changed in: unity (Ubuntu) Status: In Progress => 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/998285 Title: Tapping alt-tab switches between windows of the same application sometimes Status in Unity: In Progress Status in unity package in Ubuntu: Fix Released Bug description: Normally, tapping alt-tab switches between applications, and tapping alt-` switches between windows of the front-most application. However, if the two front-most windows are from the same application, then alt- tab will switch between these windows instead, instead of moving to the second-front-most application. Hence, in this case, alt-tab duplicates the action of alt-`. Here is an example: 1) create the stack with two nautilus windows at the top, e.g. Nautilus window 1 (N1), Nautilus window 2 (N2), and Firefox window (F1) (but you can use any applications). Create the stack either by [clicking F1, N2, N1] or [switching to Nautilus with alt-tab, then alt-` to the other Nautilus window]. 2) Tap alt-tab. What happens: I switch to the other nautilus window. What I expected: to switch to the other application (i.e. Firefox). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.12-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Sat May 12 10:17:21 2012 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: unity UpgradeStatus: Upgraded to precise on 2012-04-29 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/998285/+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 1294864] Re: window snapping to the right edge is making the windows one or two pixels too narrow
This bug was fixed in the package unity - 7.3.2+15.04.20150410.1-0ubuntu1 --- unity (7.3.2+15.04.20150410.1-0ubuntu1) vivid; urgency=medium [ Brandon Schaefer ] * When we get a launcher key press (ie. super key). We check if the command lens is open. If it is then just switch the lens to the home lens. This way we dont close the dash. (LP: #1108956) [ CI Train Bot ] * New rebuild forced. [ Gerry Boland ] * SwitcherController: add first selection mode property, to decide what to select at first (LP: #998285) [ Marco Trevisan (Treviño) ] * SwitcherController: add first selection mode property, to decide what to select at first (LP: #998285) * UnityScreen: terminate spread if active when initiating Switcher (LP: #1412001) [ Stephen M. Webb ] * (Ubuntu packaging) move the session migration scripts to Python3 (LP: #1440560) * fixed the Panel title string expected by Launcher keynav AP tests (LP: #1435830) * test_wm_keybindings: fix AP failures caused by upstream Compiz change (LP: #1294864) -- CI Train BotFri, 10 Apr 2015 21:59:12 + ** Changed in: unity (Ubuntu) Status: New => 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/1294864 Title: window snapping to the right edge is making the windows one or two pixels too narrow Status in Compiz: Fix Committed Status in Compiz 0.9.11 series: Triaged Status in compiz package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Bug description: Today is the first day I experience this. Window snapping has always worked perfectly on this machine. When snapping windows to the right side of the screen using either mouse or keyboard, any application's windows are not resized to fill up the screen to the right completely. vlc, nautilus, terminal, firefox, thundebird, chrome in rare cases, the resizing works correctly. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140318-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,gnomecompat,resize,regex,move,compiztoolbox,vpswitch,mousepoll,place,snap,grid,imgpng,animation,workarounds,wall,unitymtgrabhandles,session,fade,expo,scale,ezoom,unityshell] CurrentDesktop: Unity Date: Wed Mar 19 22:13:18 2014 InstallationDate: Installed on 2013-12-24 (85 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131220) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1294864/+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 1108956] Re: The dash closes when trying to switch from Command lens to home lens
This bug was fixed in the package unity - 7.3.2+15.04.20150410.1-0ubuntu1 --- unity (7.3.2+15.04.20150410.1-0ubuntu1) vivid; urgency=medium [ Brandon Schaefer ] * When we get a launcher key press (ie. super key). We check if the command lens is open. If it is then just switch the lens to the home lens. This way we dont close the dash. (LP: #1108956) [ CI Train Bot ] * New rebuild forced. [ Gerry Boland ] * SwitcherController: add first selection mode property, to decide what to select at first (LP: #998285) [ Marco Trevisan (Treviño) ] * SwitcherController: add first selection mode property, to decide what to select at first (LP: #998285) * UnityScreen: terminate spread if active when initiating Switcher (LP: #1412001) [ Stephen M. Webb ] * (Ubuntu packaging) move the session migration scripts to Python3 (LP: #1440560) * fixed the Panel title string expected by Launcher keynav AP tests (LP: #1435830) * test_wm_keybindings: fix AP failures caused by upstream Compiz change (LP: #1294864) -- CI Train BotFri, 10 Apr 2015 21:59:12 + ** Changed in: unity (Ubuntu) Status: In Progress => 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/1108956 Title: The dash closes when trying to switch from Command lens to home lens Status in Ayatana Design: Fix Committed Status in Unity: In Progress Status in Unity 7.2 series: Triaged Status in unity package in Ubuntu: Fix Released Bug description: When I open the command lens by pressing ALT+F2, if I press "Super" the dash is closed. It should not be closed, it should switch to the home lens instead. This is the suite of the bug 1019457 To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1108956/+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 1294864] Re: window snapping to the right edge is making the windows one or two pixels too narrow
** Changed in: compiz Status: In Progress => Fix Committed ** Changed in: compiz/0.9.11 Status: Confirmed => Triaged -- 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/1294864 Title: window snapping to the right edge is making the windows one or two pixels too narrow Status in Compiz: Fix Committed Status in Compiz 0.9.11 series: Triaged Status in compiz package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Bug description: Today is the first day I experience this. Window snapping has always worked perfectly on this machine. When snapping windows to the right side of the screen using either mouse or keyboard, any application's windows are not resized to fill up the screen to the right completely. vlc, nautilus, terminal, firefox, thundebird, chrome in rare cases, the resizing works correctly. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140318-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,gnomecompat,resize,regex,move,compiztoolbox,vpswitch,mousepoll,place,snap,grid,imgpng,animation,workarounds,wall,unitymtgrabhandles,session,fade,expo,scale,ezoom,unityshell] CurrentDesktop: Unity Date: Wed Mar 19 22:13:18 2014 InstallationDate: Installed on 2013-12-24 (85 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131220) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1294864/+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 1435830] Re: AP test failure: unity.tests.launcher.test_keynav.LauncherKeyNavTests.test_launcher_keynav_changes_panel(Single Monitor)
This bug was fixed in the package unity -
7.3.2+15.04.20150410.1-0ubuntu1
---
unity (7.3.2+15.04.20150410.1-0ubuntu1) vivid; urgency=medium
[ Brandon Schaefer ]
* When we get a launcher key press (ie. super key). We check if the
command lens is open. If it is then just switch the lens to the home
lens. This way we dont close the dash. (LP: #1108956)
[ CI Train Bot ]
* New rebuild forced.
[ Gerry Boland ]
* SwitcherController: add first selection mode property, to decide
what to select at first (LP: #998285)
[ Marco Trevisan (Treviño) ]
* SwitcherController: add first selection mode property, to decide
what to select at first (LP: #998285)
* UnityScreen: terminate spread if active when initiating Switcher
(LP: #1412001)
[ Stephen M. Webb ]
* (Ubuntu packaging) move the session migration scripts to Python3
(LP: #1440560)
* fixed the Panel title string expected by Launcher keynav AP tests
(LP: #1435830)
* test_wm_keybindings: fix AP failures caused by upstream Compiz
change (LP: #1294864)
-- CI Train BotFri, 10 Apr 2015 21:59:12 +
** Changed in: unity (Ubuntu)
Status: New => 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/1435830
Title:
AP test failure:
unity.tests.launcher.test_keynav.LauncherKeyNavTests.test_launcher_keynav_changes_panel(Single
Monitor)
Status in Unity:
In Progress
Status in unity package in Ubuntu:
Fix Released
Bug description:
AP test fails consistently on every run.
FAIL:
unity.tests.launcher.test_keynav.LauncherKeyNavTests.test_launcher_keynav_changes_panel(Single
Monitor)
--
/var/log/syslog: {{{
Mar 19 16:18:46 xt2-14 com.canonical.Unity.Scope.File.Gdrive[1599]: login
finished
Mar 19 16:18:46 xt2-14 com.canonical.Unity.Scope.File.Gdrive[1599]: Got
token: ya29.OwFvVwItMuU7CMLyfIe22KhPBBlD_v62HgletZAa1aS8K5U1WNfqY6QL
Mar 19 16:18:46 xt2-14 com.canonical.Unity.Scope.File.Gdrive[1599]: Search
changed to: 'Has'
Mar 19 16:18:46 xt2-14 com.canonical.Unity.Scope.File.Gdrive[1599]: Searching
for: Has
Mar 19 16:18:46 xt2-14 com.canonical.Unity.Scope.File.Gdrive[1599]: Search
changed to: 'HasFocus'
Mar 19 16:18:46 xt2-14 com.canonical.Unity.Scope.File.Gdrive[1599]: Searching
for: HasFocus
}}}
unity-log: {{{
DEBUG 2015-03-19 16:18:41 unity.launcher.icon.application
ApplicationLauncherIcon.cpp:173 Compiz active now true
DEBUG 2015-03-19 16:18:41 unity.launcher.icon.application
ApplicationLauncherIcon.cpp:173 Terminal active now false
DEBUG 2015-03-19 16:18:52 unity.launcher.icon.application
ApplicationLauncherIcon.cpp:173 Compiz active now false
DEBUG 2015-03-19 16:18:52 unity.launcher.icon.application
ApplicationLauncherIcon.cpp:173 Terminal active now true
}}}
Traceback (most recent call last):
File
"/usr/lib/python2.7/dist-packages/unity/tests/launcher/test_keynav.py", line
247, in test_launcher_keynav_changes_panel
self.assertThat(self.unity.panels.get_active_panel().title,
Eventually(Equals("Search your computer and online sources")))
File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 423, in
assertThat
raise mismatch_error
MismatchError: After 10.0 seconds test on MenuView.panel_title failed: !=:
reference = u'Search your computer and online sources'
actual= u''
To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1435830/+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 1412001] Re: alt+backtick doesn't focus on selected one of many windows previously clicked
This bug was fixed in the package unity - 7.3.2+15.04.20150410.1-0ubuntu1 --- unity (7.3.2+15.04.20150410.1-0ubuntu1) vivid; urgency=medium [ Brandon Schaefer ] * When we get a launcher key press (ie. super key). We check if the command lens is open. If it is then just switch the lens to the home lens. This way we dont close the dash. (LP: #1108956) [ CI Train Bot ] * New rebuild forced. [ Gerry Boland ] * SwitcherController: add first selection mode property, to decide what to select at first (LP: #998285) [ Marco Trevisan (Treviño) ] * SwitcherController: add first selection mode property, to decide what to select at first (LP: #998285) * UnityScreen: terminate spread if active when initiating Switcher (LP: #1412001) [ Stephen M. Webb ] * (Ubuntu packaging) move the session migration scripts to Python3 (LP: #1440560) * fixed the Panel title string expected by Launcher keynav AP tests (LP: #1435830) * test_wm_keybindings: fix AP failures caused by upstream Compiz change (LP: #1294864) -- CI Train BotFri, 10 Apr 2015 21:59:12 + ** Changed in: unity (Ubuntu) Status: In Progress => 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/1412001 Title: alt+backtick doesn't focus on selected one of many windows previously clicked Status in Unity: In Progress Status in Unity 7.2 series: Confirmed Status in unity package in Ubuntu: Fix Released Bug description: This a user experience issue and easily reproducible. Open multiple instances of your favorite application. Then click on Unity's icon for the app when you are already focused on one instance of it. This opens up a tile of the instances of the application which you can select from with the mouse. Now while that tile is shown, use ATL+backtick to select the window you want instead of clicking with the mouse. The result is that the tile window doesn't go away. If you use ALT+backtick and switch to ALT+tab (or start from ALT+tab from the start) and select another kind of application, then the tile goes away correctly and the other application comes in the front. I can verify that the window you would select with ALT+backtick does actually get to the top of the view and is marked as the "last visited instance", because if you switch to another application (using ALT+tab) and click back on the group of the original application you would see the one you previously selected with ALT+backtick. --- Here are step-by-step instructions. - Open a couple of terminals - Open firefox - Click on the terminal icon * This should open a tile showing the various terminal windows you have open * If that doesn't happen, click again (you were not on a terminal window before) - Use ALT+backtick to select one of the terminal windows Expected behavior: The tile of terminals goes away and the selected terminal is focused Observed behavior: The tile of terminals stays on the screen ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,place,grid,mousepoll,compiztoolbox,vpswitch,regex,gnomecompat,imgpng,snap,move,unitymtgrabhandles,resize,session,wall,animation,workarounds,fade,expo,scale,ezoom,unityshell] CurrentDesktop: Unity Date: Sat Jan 17 16:32:05 2015 ExecutablePath: /usr/bin/compiz ProcEnviron: PATH=(custom, no user) LANGUAGE=en_US XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-11-01 (76 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1412001/+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 1440560] Re: please convert the session-migration scripts to Python3
This bug was fixed in the package unity - 7.3.2+15.04.20150410.1-0ubuntu1 --- unity (7.3.2+15.04.20150410.1-0ubuntu1) vivid; urgency=medium [ Brandon Schaefer ] * When we get a launcher key press (ie. super key). We check if the command lens is open. If it is then just switch the lens to the home lens. This way we dont close the dash. (LP: #1108956) [ CI Train Bot ] * New rebuild forced. [ Gerry Boland ] * SwitcherController: add first selection mode property, to decide what to select at first (LP: #998285) [ Marco Trevisan (Treviño) ] * SwitcherController: add first selection mode property, to decide what to select at first (LP: #998285) * UnityScreen: terminate spread if active when initiating Switcher (LP: #1412001) [ Stephen M. Webb ] * (Ubuntu packaging) move the session migration scripts to Python3 (LP: #1440560) * fixed the Panel title string expected by Launcher keynav AP tests (LP: #1435830) * test_wm_keybindings: fix AP failures caused by upstream Compiz change (LP: #1294864) -- CI Train BotFri, 10 Apr 2015 21:59:12 + ** Changed in: unity (Ubuntu) Status: In Progress => 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/1440560 Title: please convert the session-migration scripts to Python3 Status in unity package in Ubuntu: Fix Released Bug description: There is still the goal to remove Python2 from the desktop images, and to use Python3 only. please convert the session-migration scripts to Python3. There is also a missing dependency on python3-gi. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1440560/+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 1270486] Re: libdbusmenu doesn't use the menu item's label if it has a stock icon
This bug was fixed in the package libdbusmenu - 12.10.3+15.04.20150410.2-0ubuntu1 --- libdbusmenu (12.10.3+15.04.20150410.2-0ubuntu1) vivid; urgency=medium [ CI Train Bot ] * New rebuild forced. [ Marco Trevisan (Treviño) ] * Parser: don't override the label for stock items if a custom one is provided (LP: #1270486) -- CI Train BotFri, 10 Apr 2015 21:56:13 + ** Changed in: libdbusmenu (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to libdbusmenu in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1270486 Title: libdbusmenu doesn't use the menu item's label if it has a stock icon Status in libdbusmenu package in Ubuntu: Fix Released Bug description: To reproduce, run the attached testcase1.py. You will see a new indicator, inside it will be one menu item with label "Pause" and a pause button icon. The menu item should have the label "Hello". Also note that this bug has been fixed once before: https://bugs.launchpad.net/indicator-application/+bug/520048 For trusty, see comment 3. Glade is used by deluge to set the indicator menu, this is where the problem was first observed. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-application 12.10.1+13.10.20131107-0ubuntu1 Uname: Linux 3.11.0-031100-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Sat Jan 18 20:40:29 2014 InstallationDate: Installed on 2013-08-27 (143 days ago) InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130827) MarkForUpload: True SourcePackage: indicator-application UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdbusmenu/+bug/1270486/+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 1390625] Re: mouse cursor gets corrupted
What would the appropriate Ubuntu project be for graphics or kernel bugs? ** Also affects: ubuntu-ux Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1390625 Title: mouse cursor gets corrupted Status in elementary OS: Confirmed Status in Ubuntu UX bugs: New Status in Unity: Invalid Status in unity package in Ubuntu: Confirmed Bug description: In Ubuntu 14.10, the mouse cursor graphic gets corrupted under certain occasions. It then looks flipped, sheared or shows fragments of a previous cursor. * when switching the cursor them forth and back in Gnome Tweak Tool * when drag&dropping a document icon Maybe related, the cursor does not always show the correct image scale on a high-dpi display (this was working right in 14.04). For example after login, or when hovering specific areas, or on mouse down to start a drag&drop, the cursor appears 1/4 the expected size. Attached is a photo of a corrupted cursor (whereas a screenshot with Gimp showed the uncorrupted cursor). ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 BootLog: * Setting up X socket directories... [400G [394G[ OK ] CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Nov 7 22:12:52 2014 DistUpgraded: 2014-11-04 18:35:56,188 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3978] InstallationDate: Installed on 2014-02-02 (278 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140201) MachineType: LENOVO 20266 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed root=UUID=4bfb3686-b9f7-487d-81f6-eceb41097ad9 ro quiet splash acpi_backlight=vendor SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-11-04 (3 days ago) dmi.bios.date: 10/31/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN31WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Fri Nov 7 14:54:59 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: [dix] ELAN Touchscreen: unable to find touch point 1 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16970 vendor SDC xserver.version: 2:1.16.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1390625/+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 1294864] Re: window snapping to the right edge is making the windows one or two pixels too narrow
** Branch linked: lp:ubuntu/vivid-proposed/compiz -- 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/1294864 Title: window snapping to the right edge is making the windows one or two pixels too narrow Status in Compiz: In Progress Status in Compiz 0.9.11 series: Confirmed Status in compiz package in Ubuntu: In Progress Status in unity package in Ubuntu: New Bug description: Today is the first day I experience this. Window snapping has always worked perfectly on this machine. When snapping windows to the right side of the screen using either mouse or keyboard, any application's windows are not resized to fill up the screen to the right completely. vlc, nautilus, terminal, firefox, thundebird, chrome in rare cases, the resizing works correctly. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140318-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,gnomecompat,resize,regex,move,compiztoolbox,vpswitch,mousepoll,place,snap,grid,imgpng,animation,workarounds,wall,unitymtgrabhandles,session,fade,expo,scale,ezoom,unityshell] CurrentDesktop: Unity Date: Wed Mar 19 22:13:18 2014 InstallationDate: Installed on 2013-12-24 (85 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131220) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1294864/+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 1294864] Re: window snapping to the right edge is making the windows one or two pixels too narrow
This bug was fixed in the package compiz - 1:0.9.12.1+15.04.20150410.1-0ubuntu1 --- compiz (1:0.9.12.1+15.04.20150410.1-0ubuntu1) vivid; urgency=medium [ CI Train Bot ] * New rebuild forced. [ Chris Townsend ] * Expo plugin: Make sure the Expo animation is completed before allowing clicks to be handled. (LP: #1026553) * Grid plugin: Float to int division truncating caused a 1 px gap on the right side of right semi-maximized window when the workspace has an odd width. Fix is to add 0.5 to the float division first to account for any truncation error. (LP: #1294864) [ Eleni Maria Stea ] * Change in GLVector implementation * Minor change: when the skydome was working (in the c version of compiz) it was rendered on top of the background so, there was no need to clear the screen before drawing (the skydome was rendered on top of the garbage from previous renderings, hiding it). In the c++ plugin, the skydome is buggy and the background is visible (as well as some garbage from previous renderings). A temporary glClear(GL_COLOR_BUFFER_BIT) was added until we fix the skydome and the other cube bugs. * glDisableOutputClipping was not implemented in 3d.cpp => a parent class glDisableOutputClipping was called, causing 2d clipping artifacts (the 3d cube was clipped and you couldn't see the windows move) [ Marco Trevisan (Treviño) ] * OpenGL: don't hardcode X11 sync blacklisted models, but use settings instead (LP: #1441190) [ Stephen M. Webb ] * (Ubuntu packaging) migrate migration scripts to Python3. (LP: #1440548) * exclude Wine applications from window close animations (LP: #957879) -- CI Train BotFri, 10 Apr 2015 21:55:34 + ** Changed in: compiz (Ubuntu) Status: In Progress => 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/1294864 Title: window snapping to the right edge is making the windows one or two pixels too narrow Status in Compiz: In Progress Status in Compiz 0.9.11 series: Confirmed Status in compiz package in Ubuntu: Fix Released Status in unity package in Ubuntu: New Bug description: Today is the first day I experience this. Window snapping has always worked perfectly on this machine. When snapping windows to the right side of the screen using either mouse or keyboard, any application's windows are not resized to fill up the screen to the right completely. vlc, nautilus, terminal, firefox, thundebird, chrome in rare cases, the resizing works correctly. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140318-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,gnomecompat,resize,regex,move,compiztoolbox,vpswitch,mousepoll,place,snap,grid,imgpng,animation,workarounds,wall,unitymtgrabhandles,session,fade,expo,scale,ezoom,unityshell] CurrentDesktop: Unity Date: Wed Mar 19 22:13:18 2014 InstallationDate: Installed on 2013-12-24 (85 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131220) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1294864/+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 1443549] Re: notification-daemon crashed with SIGABRT in g_assertion_message()
*** This bug is a duplicate of bug 1421821 *** https://bugs.launchpad.net/bugs/1421821 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1421821, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1443549/+attachment/4374177/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1443549/+attachment/4374179/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1443549/+attachment/4374181/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1443549/+attachment/4374182/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1443549/+attachment/4374183/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1443549/+attachment/4374184/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1443549/+attachment/4374185/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1421821 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of DX Packages, which is subscribed to notification-daemon in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1443549 Title: notification-daemon crashed with SIGABRT in g_assertion_message() Status in notification-daemon package in Ubuntu: New Bug description: I plugged in an iPhone and lots of notification boxes popped up and this crashed ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: notification-daemon 3.14.1-1 ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3 Uname: Linux 3.19.0-13-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Mon Apr 13 17:54:29 2015 ExecutablePath: /usr/lib/notification-daemon/notification-daemon ProcCmdline: /usr/lib/notification-daemon/notification-daemon ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: notification-daemon 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 ?? () ?? () ?? () Title: notification-daemon crashed with SIGABRT in g_assertion_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notification-daemon/+bug/1443549/+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 1270486] Re: libdbusmenu doesn't use the menu item's label if it has a stock icon
** Branch linked: lp:ubuntu/vivid-proposed/libdbusmenu -- You received this bug notification because you are a member of DX Packages, which is subscribed to libdbusmenu in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1270486 Title: libdbusmenu doesn't use the menu item's label if it has a stock icon Status in libdbusmenu package in Ubuntu: In Progress Bug description: To reproduce, run the attached testcase1.py. You will see a new indicator, inside it will be one menu item with label "Pause" and a pause button icon. The menu item should have the label "Hello". Also note that this bug has been fixed once before: https://bugs.launchpad.net/indicator-application/+bug/520048 For trusty, see comment 3. Glade is used by deluge to set the indicator menu, this is where the problem was first observed. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-application 12.10.1+13.10.20131107-0ubuntu1 Uname: Linux 3.11.0-031100-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Sat Jan 18 20:40:29 2014 InstallationDate: Installed on 2013-08-27 (143 days ago) InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130827) MarkForUpload: True SourcePackage: indicator-application UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdbusmenu/+bug/1270486/+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 1443502] Re: indicator-session-unknown-user-error
** Package changed: upstart (Ubuntu) => indicator-session (Ubuntu) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-session in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1443502 Title: indicator-session-unknown-user-error Status in indicator-session package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding upstart. This problem was most recently seen with version 1.13.2-0ubuntu13, the problem page at https://errors.ubuntu.com/problem/45a450ff9d534458de5666d47abe150801af4041 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1443502/+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 1432446] Re: indicator-sound-service crashed with signal 5 in indicator_sound_service_construct()
** Changed in: indicator-sound (Ubuntu) Assignee: (unassigned) => Charles Kerr (charlesk) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1432446 Title: indicator-sound-service crashed with signal 5 in indicator_sound_service_construct() Status in indicator-sound package in Ubuntu: Confirmed Bug description: At log in white screen .. mouse click and then this request ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: indicator-sound 12.10.2+15.04.20150311-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-9.9-lowlatency 3.19.1 Uname: Linux 3.19.0-9-lowlatency x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CrashCounter: 1 Date: Sun Mar 15 18:39:06 2015 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service InstallationDate: Installed on 2015-02-13 (30 days ago) InstallationMedia: Ubuntu-Studio 15.04 "Vivid Vervet" - Alpha amd64 (20150213) ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: indicator-sound StacktraceTop: indicator_sound_service_construct () _start () Title: indicator-sound-service crashed with signal 5 in indicator_sound_service_construct() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1432446/+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 1443502] [NEW] indicator-session-unknown-user-error
You have been subscribed to a public bug: The Ubuntu Error Tracker has been receiving reports about a problem regarding upstart. This problem was most recently seen with version 1.13.2-0ubuntu13, the problem page at https://errors.ubuntu.com/problem/45a450ff9d534458de5666d47abe150801af4041 contains more details. ** Affects: indicator-session (Ubuntu) Importance: Undecided Status: New ** Tags: kylin-14.10 kylin-15.04 trusty utopic vivid -- indicator-session-unknown-user-error https://bugs.launchpad.net/bugs/1443502 You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-session 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 1432446] Re: indicator-sound-service crashed with signal 5 in indicator_sound_service_construct()
https://errors.ubuntu.com/problem/b200c67dc8b4d749da796ad4c670ce350e127b26 seems to indicated in started with 12.10.2+15.04.20150311-0ubuntu1 -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1432446 Title: indicator-sound-service crashed with signal 5 in indicator_sound_service_construct() Status in indicator-sound package in Ubuntu: Confirmed Bug description: At log in white screen .. mouse click and then this request ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: indicator-sound 12.10.2+15.04.20150311-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-9.9-lowlatency 3.19.1 Uname: Linux 3.19.0-9-lowlatency x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CrashCounter: 1 Date: Sun Mar 15 18:39:06 2015 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service InstallationDate: Installed on 2015-02-13 (30 days ago) InstallationMedia: Ubuntu-Studio 15.04 "Vivid Vervet" - Alpha amd64 (20150213) ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: indicator-sound StacktraceTop: indicator_sound_service_construct () _start () Title: indicator-sound-service crashed with signal 5 in indicator_sound_service_construct() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1432446/+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 1442166] Re: Calendar alarms rings forever if Low Battery dialog visible
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: usensord (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/1442166 Title: Calendar alarms rings forever if Low Battery dialog visible Status in the base for Ubuntu mobile products: Confirmed Status in indicator-datetime package in Ubuntu: Confirmed Status in usensord package in Ubuntu: Confirmed Bug description: I'm on rtm build 258 on krillin Steps to reproduce: - let battery run down on phone (was sitting unplugged for 1 or 2 days) - in the morning, a calendar alarm starting ringing/vibrating and would not stop - when I looked at the phone, the screen was on and I see the Low Battery dialog - after dismissing the dialog, then I see the notification for the alarm, and only after 5-10 more seconds does the ringing stop Seems like while the Low Battery dialog is displayed it keeps the alarm ringing forever To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1442166/+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 1442166] Re: Calendar alarms rings forever if Low Battery dialog visible
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/1442166 Title: Calendar alarms rings forever if Low Battery dialog visible Status in the base for Ubuntu mobile products: Confirmed Status in indicator-datetime package in Ubuntu: Confirmed Status in usensord package in Ubuntu: Confirmed Bug description: I'm on rtm build 258 on krillin Steps to reproduce: - let battery run down on phone (was sitting unplugged for 1 or 2 days) - in the morning, a calendar alarm starting ringing/vibrating and would not stop - when I looked at the phone, the screen was on and I see the Low Battery dialog - after dismissing the dialog, then I see the notification for the alarm, and only after 5-10 more seconds does the ringing stop Seems like while the Low Battery dialog is displayed it keeps the alarm ringing forever To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1442166/+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 1052024] Re: Week 38 - keynav mode quicklist exit fails to work when mouse is used to right click and choose an option
** Changed in: unity Assignee: Marco Trevisan (Treviño) (3v1n0) => Christopher Townsend (townsend) ** Changed in: unity/7.2 Assignee: Marco Trevisan (Treviño) (3v1n0) => Christopher Townsend (townsend) ** Changed in: unity (Ubuntu) Assignee: (unassigned) => Christopher Townsend (townsend) ** 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/1052024 Title: Week 38 - keynav mode quicklist exit fails to work when mouse is used to right click and choose an option Status in Unity: In Progress Status in Unity 7.2 series: Triaged Status in unity package in Ubuntu: In Progress Bug description: Ubuntu 12.10 Quantal with ppa:unity-team/staging Issue:- Right click using mouse on dash icon in keynav mode fails to exit keynav mode and does not activate the option chosen by the user. Only if the user clicks anywhere on the screen, the chosen option gets activated. For example:- In keynav mode, right click on dash and click on "Applications". This will not exit keynav mode and will not open applications lens. Only when the user click somewhere on the screen, keynav mode exits and applications lens is opened. Action: - Press Alt+F1 to enter keynav mode - now right click on dash icon, click on any options in the quicklist ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: unity 6.4.0+bzr2684ubuntu0+778 [origin: LP-PPA-unity-team-staging] ProcVersionSignature: Ubuntu 3.5.0-14.19-generic 3.5.3 Uname: Linux 3.5.0-14-generic i686 ApportVersion: 2.5.1-0ubuntu7 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CrashDB: unity Date: Mon Sep 17 16:27:38 2012 InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120713.1) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1052024/+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 1441819] Re: The sound indicator is a bit cluttered
** Summary changed: - The unity sound settings is a bit cluttered + The sound indicator is a bit cluttered ** Changed in: indicator-sound (Ubuntu) Assignee: (unassigned) => Matthew Paul Thomas (mpt) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1441819 Title: The sound indicator is a bit cluttered Status in indicator-sound package in Ubuntu: Confirmed Bug description: The best is to view the added screen-shot, in the attachmentst, and my proposed 'fix'. This is an revised image of the one in the attachment: http://i.stack.imgur.com/o0Jd1.png Please ignore the one in the attachments, its slightly off, of what I meant ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.4+14.04.20141217-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is een map: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.113 Mon Dec 1 21:08:13 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.8 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: Wed Apr 8 21:12:36 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.16.0-33-generic, x86_64: installed nvidia-331, 331.113, 3.16.0-33-generic, x86_64: installed nvidia-331-uvm, 331.113, 3.16.0-33-generic, x86_64: installed vboxhost, 4.3.26, 3.16.0-33-generic, x86_64: installed GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:124d] Subsystem: ASUSTeK Computer Inc. Device [1043:124d] InstallationDate: Installed on 2015-04-07 (1 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: ASUSTeK COMPUTER INC. X550CC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-33-generic root=UUID=e4df7d74-dffc-4deb-9ea1-b7653d90c4c6 ro quiet splash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550CC.217 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550CC dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550CC.217:bd10/16/2013:svnASUSTeKCOMPUTERINC.:pnX550CC:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550CC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550CC dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Apr 8 19:32:08 2015 xserver.configfile: /etc/X11/xorg.conf xserver.errors: NVIDIA(0): Failed to initiate mode change. NVIDIA(0): Failed to complete mode change xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 927 vendor LGD xserver.version: 2:1.16.0-1ubuntu1.2~trusty2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1441819/+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 1411643] Re: Automatic brightness toggle switch missing on krillin/vivid
*** This bug is a duplicate of bug 1382861 *** https://bugs.launchpad.net/bugs/1382861 ** This bug has been marked a duplicate of bug 1382861 Auto brightness toggle sometimes doesn't appear in power indicator -- 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/1411643 Title: Automatic brightness toggle switch missing on krillin/vivid Status in indicator-power package in Ubuntu: Incomplete Bug description: I noticed that on my krillin device with devel-propsed (r70), the automatic display brightness toggle switch is missing in the battery indicator. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1411643/+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 1422814] Re: indicator-datetime crashes when 'Weekday' or 'Day and month' are checked
Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart. Now open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit. If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'. I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding. ** Changed in: indicator-datetime (Ubuntu) Status: New => Invalid -- 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/1422814 Title: indicator-datetime crashes when 'Weekday' or 'Day and month' are checked Status in indicator-datetime package in Ubuntu: Invalid Bug description: lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 apt-cache policy indicator-datetime indicator-datetime: Installed: 13.10.0+14.04.20140415.3-0ubuntu1 Candidate: 13.10.0+14.04.20140415.3-0ubuntu1 Version table: *** 13.10.0+14.04.20140415.3-0ubuntu1 0 990 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status I executed apt-get update at 2/16/15 21:20 US Eastern time. Before doing so I added ppa:libreoffice/ppa repo Previous apt-get update was executed on 2/12/15 08:00 I expect to have the Time and Date showing in the Unity bar as it has been since I originally set up my system. I also expect the calendar to start on Mondays because I have `export LC_TIME=en_GB.UTF-8` set in my .bashrc. What is happening now: Today, 2/17/15, I was no longer seeing the date and time in the Unity bar. If I disable 'Weekday' and 'Day and month' in the settings, then the time will show. If I enable either 'Weekday' or 'Day and month' the time disappears The calendar that shows when I click the time is US standard starting on Sunday. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1422814/+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 1437242] Re: Event notification no text
> looks like related to Date time indicator That wouldn't explain why there are no events in the Today scope. Maybe events didn't get saved to EDS? ** Changed in: indicator-datetime (Ubuntu) Status: New => Invalid -- 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/1437242 Title: Event notification no text Status in Calendar application for Ubuntu devices: New Status in indicator-datetime package in Ubuntu: Invalid Bug description: Aquaris, build 20. An audio alert from Calendar this morning but no accompanying text notification, no events shown in Today scope and no notification in top menu or in the 'circle'. Left wondering at first what the harp sound meant. Sound was at the exact time of the appointment. Fortunately I was there on time ! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1437242/+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 1437652] Re: Bluetooth is enabled after leaving air plane mode even if it was deaktivated bevore
I experience the same problem as bogdanke8: bq device, Ubuntu 14.10 (r20). Steps to reproduce: 1) turn off Bluetooth 2) turn on Airplane mode, 3) turn off Airplane mode. What happens: Bluetooth is always turned on What should happen: It gets restored to the previous state I believe that this is a big regression from the original bug posted by HP, where this behaviour occurs only if between steps 2 and 3 there is reboot. -- 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/1437652 Title: Bluetooth is enabled after leaving air plane mode even if it was deaktivated bevore Status in indicator-bluetooth package in Ubuntu: Confirmed Bug description: If the bq Ubuntu Phone is running and mobile radio is activated while bluetooth is deactivate it still will be the same after entering and subsequent leaving the air plane mode. contrariwise: The bq Ubuntu Phone is running and mobile radio is activated while bluetooth is deactivate, in the next step we will enter air plain mode and shut down the phone. After boot up we will deactivate the air plane mode, then mobile radio and bluetooth is activated even if bluetooth was deactivated before entering the air plane mode. If bluetooth was deactivated before entering the air plane mode is should also be deactivated after leaving the air plane mode even if the telephone was shut down meanwhile. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1437652/+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 1350821] Re: unity-panel-service crashed with SIGSEGV in ido_calendar_menu_item_key_press()
> Thread 1 (Thread 0x7ffbbbaa39c0 (LWP 2565)):
> #0 ido_calendar_menu_item_key_press (widget=widget@entry=0x1e090f0,
> event=0x7fff8761dad0, data=0x0, data@entry=0x1e37790) at
> idocalendarmenuitem.c:159
The crash is straightforward enough, but I'm not sure yet what's causing
it.
data is NULL, and ido_calendar_menu_item_key_press() casts it to an
IdoCalendarMenuItem* and dereferences it:
> static gboolean
> ido_calendar_menu_item_key_press (GtkWidget *widget,
> GdkEventKey *event,
> gpointer data)
> {
> IdoCalendarMenuItem *menuitem = (IdoCalendarMenuItem *)data;
>
> if (menuitem->priv->selected)
> {
...
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to ido in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1350821
Title:
unity-panel-service crashed with SIGSEGV in
ido_calendar_menu_item_key_press()
Status in ido package in Ubuntu:
Triaged
Bug description:
No idea what happened.
ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: unity-services 7.3.0+14.10.20140711-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
Uname: Linux 3.16.0-6-generic x86_64
.tmp.unity.support.test.0:
ApportVersion: 2.14.5-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: Thu Jul 31 13:53:14 2014
DistUpgraded: Fresh install
DistroCodename: utopic
DistroVariant: ubuntu
DkmsStatus:
virtualbox, 4.3.12, 3.16.0-5-generic, x86_64: installed
virtualbox, 4.3.12, 3.16.0-6-generic, x86_64: installed
ExecutablePath: /usr/lib/unity/unity-panel-service
GraphicsCard:
Intel Corporation 2nd Generation Core Processor Family Integrated Graphics
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Lenovo Device [17aa:21da]
InstallationDate: Installed on 2013-12-22 (221 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131221)
MachineType: LENOVO 429149G
ProcCmdline: /usr/lib/unity/unity-panel-service
ProcEnviron:
PATH=(custom, user)
LANGUAGE=de_DE
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-6-generic
root=UUID=23a70067-84b7-4d69-8cbc-11f2fe3f429d ro quiet splash vt.handoff=7
SegvAnalysis:
Segfault happened at: 0x7ffbbaf3b766:mov0x10(%rdx),%ecx
PC (0x7ffbbaf3b766) ok
source "0x10(%rdx)" (0x0010) not located in a known VMA region (needed
readable region)!
destination "%ecx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libido3-0.1.so.0
?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: unity-panel-service crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare scanner sudo
dmi.bios.date: 05/18/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 8DET46WW (1.16 )
dmi.board.asset.tag: Not Available
dmi.board.name: 429149G
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias:
dmi:bvnLENOVO:bvr8DET46WW(1.16):bd05/18/2011:svnLENOVO:pn429149G:pvrThinkPadX220:rvnLENOVO:rn429149G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 429149G
dmi.product.version: ThinkPad X220
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.11+14.10.20140707-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.54-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.3-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.3-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu8
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.914-1~exp1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.10-1ubuntu2
xserver.bootTime: Wed Jul 30 18:55:05 2014
xserver.configfile: default
xserver.errors:
intel: Failed to load module "dri3" (module does not exist, 0)
intel: Failed to load module "present" (module does not exist, 0)
xserver.logfile:
[Dx-packages] [Bug 1443005] Re: Indicator shouldn't set volume on pulse/account service if the volume didn't change
** Changed in: indicator-sound (Ubuntu) Status: New => In Progress ** Changed in: indicator-sound (Ubuntu) Assignee: (unassigned) => Ricardo Salveti (rsalveti) ** Changed in: indicator-sound (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1443005 Title: Indicator shouldn't set volume on pulse/account service if the volume didn't change Status in indicator-sound package in Ubuntu: In Progress Bug description: current build number: 168 device name: mako channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-04-12 03:49:09 version version: 168 version ubuntu: 20150411 version device: 20150210 version custom: 20150411 This is a regression from RTM. The current logic doesn't check for the volume value before calling pulseaudio and account service when updating the volume variable. The consequence is that it will set the volume at least twice after you change it, since it will get a callback from account service, and that will result in another volume set with the exact same volume. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1443005/+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 1432446] Re: Login after startup
Doesn't look like it -- I don't see anything sensitive in the crash attachments. ** Information type changed from Private to Public ** Summary changed: - Login after startup + indicator-sound-service crashed with signal 5 in indicator_sound_service_construct() -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1432446 Title: indicator-sound-service crashed with signal 5 in indicator_sound_service_construct() Status in indicator-sound package in Ubuntu: Confirmed Bug description: At log in white screen .. mouse click and then this request ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: indicator-sound 12.10.2+15.04.20150311-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-9.9-lowlatency 3.19.1 Uname: Linux 3.19.0-9-lowlatency x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CrashCounter: 1 Date: Sun Mar 15 18:39:06 2015 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service InstallationDate: Installed on 2015-02-13 (30 days ago) InstallationMedia: Ubuntu-Studio 15.04 "Vivid Vervet" - Alpha amd64 (20150213) ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: indicator-sound StacktraceTop: indicator_sound_service_construct () _start () Title: indicator-sound-service crashed with signal 5 in indicator_sound_service_construct() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1432446/+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 1443178] Re: Accounts Service always relies on language fallback if never set by the user
Hi Michal,
Please note that the problem isn't Unity 8 specific. I added that
user_get_fallback_value() function a few years ago (admittedly it's a
little 'heavy'), and the purpose was to get the start value right in
various GUIs for setting language/locale, both in Ubuntu and the
flavours. Even if I'm not quite sure yet, I think the problem is best
fixed in the accountsservice package.
--
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/1443178
Title:
Accounts Service always relies on language fallback if never set by
the user
Status in the base for Ubuntu mobile products:
New
Status in accountsservice package in Ubuntu:
In Progress
Status in ubuntu-system-settings package in Ubuntu:
New
Status in unity8 package in Ubuntu:
New
Bug description:
current build number: 169
device name: mako
channel: ubuntu-touch/devel-proposed
alias: ubuntu-touch/vivid-proposed
last update: 2015-04-12 20:38:14
version version: 169
version ubuntu: 20150412
version device: 20150210
version custom: 20150412
This causes a bad side effect when changing volume via indicator-
sound, as that will cause a sync to accountsservice in order to sync
the volume. Once that sync happens, it will request the user
properties, and in case the user doesn't have a valid language at
/var/lib/AccountsService/users/, it will always rely on the
fallback, which would be fine if calculating the fallback wasn't 't so
cpu or i/o intensive (and that happens multiple times).
As a test, just flash latest vivid image on mako, don't set any
language when the wizard shows up, run top and then change the volume
by pressing volume up/down. This is what I see with mako:
PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND
2609 phablet 20 0 499660 121220 52688 S 7.6 6.5 0:41.69 unity8
5600 phablet 20 03676 1760 1288 R 6.0 0.1 0:00.19
language-option
1312 root 20 0 211532 15572 11344 S 1.9 0.8 0:07.25
unity-system-co
1316 phablet 20 0 36532 3792 2928 S 1.3 0.2 0:01.66
accounts-daemon
And the reason why:
src/user.c
...
static void
user_get_property (GObject*object,
guint param_id,
GValue *value,
GParamSpec *pspec)
{
User *user = USER (object);
...
case PROP_LANGUAGE:
if (user->language)
g_value_set_string (value, user->language);
else
g_value_set_string (value, user_get_fallback_value
(user, "Language"));
break;
case PROP_FORMATS_LOCALE:
if (user->formats_locale)
g_value_set_string (value, user->formats_locale);
else
g_value_set_string (value, user_get_fallback_value
(user, "FormatsLocale"));
break;
user_set_property never gets called unless the user changes the system
language from system-settings or wizard.
Once you change the language, it will set a valid language at
/var/lib/AccountsService/users/, causing this behavior to stop.
Another bad side effect of this issue is that it takes quite a while
for accountsservice to reply back to indicator-sound when the sync
happens, possibly causing sync aborts (as indicator-sound only waits 1
second before triggering another sync).
Some possible ways to fix this issue:
1) Make wizard to set language even when the selected language is already the
default one;
2) Change accountsservice to save the fallback value at the first time it
gets that from the system;
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1443178/+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 1443178] Re: Accounts Service always relies on language fallback if never set by the user
OK so the unity8/wizard part seems to be that the language isn't being
stored in AS if it's not changed from default. This could very well be
libubuntu-system-settings then.
** Changed in: unity8 (Ubuntu)
Status: Incomplete => New
** Also affects: ubuntu-system-settings (Ubuntu)
Importance: Undecided
Status: New
--
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/1443178
Title:
Accounts Service always relies on language fallback if never set by
the user
Status in the base for Ubuntu mobile products:
New
Status in accountsservice package in Ubuntu:
In Progress
Status in ubuntu-system-settings package in Ubuntu:
New
Status in unity8 package in Ubuntu:
New
Bug description:
current build number: 169
device name: mako
channel: ubuntu-touch/devel-proposed
alias: ubuntu-touch/vivid-proposed
last update: 2015-04-12 20:38:14
version version: 169
version ubuntu: 20150412
version device: 20150210
version custom: 20150412
This causes a bad side effect when changing volume via indicator-
sound, as that will cause a sync to accountsservice in order to sync
the volume. Once that sync happens, it will request the user
properties, and in case the user doesn't have a valid language at
/var/lib/AccountsService/users/, it will always rely on the
fallback, which would be fine if calculating the fallback wasn't 't so
cpu or i/o intensive (and that happens multiple times).
As a test, just flash latest vivid image on mako, don't set any
language when the wizard shows up, run top and then change the volume
by pressing volume up/down. This is what I see with mako:
PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND
2609 phablet 20 0 499660 121220 52688 S 7.6 6.5 0:41.69 unity8
5600 phablet 20 03676 1760 1288 R 6.0 0.1 0:00.19
language-option
1312 root 20 0 211532 15572 11344 S 1.9 0.8 0:07.25
unity-system-co
1316 phablet 20 0 36532 3792 2928 S 1.3 0.2 0:01.66
accounts-daemon
And the reason why:
src/user.c
...
static void
user_get_property (GObject*object,
guint param_id,
GValue *value,
GParamSpec *pspec)
{
User *user = USER (object);
...
case PROP_LANGUAGE:
if (user->language)
g_value_set_string (value, user->language);
else
g_value_set_string (value, user_get_fallback_value
(user, "Language"));
break;
case PROP_FORMATS_LOCALE:
if (user->formats_locale)
g_value_set_string (value, user->formats_locale);
else
g_value_set_string (value, user_get_fallback_value
(user, "FormatsLocale"));
break;
user_set_property never gets called unless the user changes the system
language from system-settings or wizard.
Once you change the language, it will set a valid language at
/var/lib/AccountsService/users/, causing this behavior to stop.
Another bad side effect of this issue is that it takes quite a while
for accountsservice to reply back to indicator-sound when the sync
happens, possibly causing sync aborts (as indicator-sound only waits 1
second before triggering another sync).
Some possible ways to fix this issue:
1) Make wizard to set language even when the selected language is already the
default one;
2) Change accountsservice to save the fallback value at the first time it
gets that from the system;
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1443178/+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 1241757] Re: Unity Launcher always assumes default background is active for a couple of seconds
I verified this on an old, slow machine where the described phenomenon was more easily observed and it indeed no longer occurs. There is still a whole-screen flicker as Compiz starts up but that's an unrelated issue. ** Tags removed: verification-needed ** Tags added: verification-done -- 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/1241757 Title: Unity Launcher always assumes default background is active for a couple of seconds Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [IMPACT] Every time the computer boots and autologins to my desktop, I see the default background only behind the Unity Launcher for a couple of seconds, and then it is replaced with the current wallpaper. [TEST CASE] (1) Configure the desktop to use a non-default wallpaper. (2) Log in to a Unity session and observe the area behind the Launcher. [REGRESSION POTENTIAL] The solution to this problem was to eliminate the animation of the BFB icon on initial startup. Potentially this could cause the animation to not run at other times, although even if this did occur, it is unlikely to be noticed. [OTHER INFO] The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu "Vivid Vervet" dev release where it has been in production use for some time without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1241757/+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 1442166] Re: Calendar alarms rings forever if Low Battery dialog visible
>From the description this seems like a different case of the vibration. Does it keep *ringing* literally, or just vibrating? Is it with the screen off? or on. -- 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/1442166 Title: Calendar alarms rings forever if Low Battery dialog visible Status in the base for Ubuntu mobile products: Confirmed Status in indicator-datetime package in Ubuntu: New Status in usensord package in Ubuntu: New Bug description: I'm on rtm build 258 on krillin Steps to reproduce: - let battery run down on phone (was sitting unplugged for 1 or 2 days) - in the morning, a calendar alarm starting ringing/vibrating and would not stop - when I looked at the phone, the screen was on and I see the Low Battery dialog - after dismissing the dialog, then I see the notification for the alarm, and only after 5-10 more seconds does the ringing stop Seems like while the Low Battery dialog is displayed it keeps the alarm ringing forever To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1442166/+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 1443229] Re: support for xfce only environment
*** This bug is a duplicate of bug 1359249 ***
https://bugs.launchpad.net/bugs/1359249
** This bug has been marked a duplicate of bug 1359249
Launching PAVUControl works from Xubuntu, but not from Xfce
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-sound in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1443229
Title:
support for xfce only environment
Status in indicator-sound package in Ubuntu:
New
Bug description:
hi dev team,
I find that indicator-sound cannot open pavucontrol by clicking "Sound
Settings..." in the popup menu, in a XFCE only environment, not
xubuntu, but a customized OS made by myself.
I investigate the source code of indicator-sound, and find that in
src/service.vala:
var env = Environment.get_variable ("DESKTOP_SESSION");
string cmd;
if (env == "xubuntu" || env == "ubuntustudio")
cmd = "pavucontrol";
else
I think you would support more desktop environment such as XFCE.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1443229/+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 907411] Re: printer tray icon doesn't appear (any more) when printing
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-printers (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/907411 Title: printer tray icon doesn't appear (any more) when printing Status in Unity: Invalid Status in indicator-printers package in Ubuntu: New Status in unity package in Ubuntu: Invalid Bug description: I'm not sure where the bug is but it's almost certainly somehow related to the change of gnome in favor to unity. In ubuntu 10.10 and earlier, when I printed any document (no matter from what application), a tray icon of a printer appeared on the upper-right size of the . By clicking on it I could see the printing queue, the status of the jobs, I could manage printing jobs etc. Now in ubuntu 11.10 that icon does not appear any more. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: unity 4.24.0-0ubuntu2.1 ProcVersionSignature: Ubuntu 3.0.0-15.24-generic 3.0.13 Uname: Linux 3.0.0-15-generic i686 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86 Kernel Module 280.13 Wed Jul 27 16:55:43 PDT 2011 GCC version: gcc version 4.6.1 (Ubuntu/Linaro 4.6.1-9ubuntu3) .tmp.unity.support.test.0: ApportVersion: 1.23-0ubuntu4 Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,decor,vpswitch,mousepoll,compiztoolbox,snap,place,resize,session,regex,grid,wall,move,gnomecompat,imgpng,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: None Date: Wed Dec 21 17:10:33 2011 DistUpgraded: Log time: 2011-12-07 19:34:40.350850 DistroCodename: oneiric DistroVariant: ubuntu GraphicsCard: nVidia Corporation G84 [GeForce 9500M GS] [10de:0405] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:15d2] InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) JockeyStatus: xorg:nvidia_173 - NVIDIA accelerated graphics driver (Proprietary, Disabled, Not in use) xorg:nvidia_173_updates - NVIDIA accelerated graphics driver (post-release updates) (Proprietary, Disabled, Not in use) xorg:nvidia_current - NVIDIA accelerated graphics driver (Proprietary, Enabled, In use) pkg:sl-modem-daemon - Software modem (Proprietary, Disabled, Not in use) xorg:nvidia_current_updates - NVIDIA accelerated graphics driver (post-release updates) (Proprietary, Disabled, Not in use) MachineType: ASUSTeK Computer Inc. M51Sn ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-15-generic root=UUID=173acbf5-26a0-49e3-8d2b-f1c142582cbf ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to oneiric on 2011-12-07 (13 days ago) dmi.bios.date: 12/24/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: M51Sn dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr303:bd12/24/2007:svnASUSTeKComputerInc.:pnM51Sn:pvr1.0:rvnASUSTeKComputerInc.:rnM51Sn:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: M51Sn dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu6 version.libdrm2: libdrm2 2.4.26-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20110811.g93fc084-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/907411/+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 907411] Re: printer tray icon doesn't appear (any more) when printing
** Project changed: indicator-printers => indicator-printers (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/907411 Title: printer tray icon doesn't appear (any more) when printing Status in Unity: Invalid Status in indicator-printers package in Ubuntu: New Status in unity package in Ubuntu: Invalid Bug description: I'm not sure where the bug is but it's almost certainly somehow related to the change of gnome in favor to unity. In ubuntu 10.10 and earlier, when I printed any document (no matter from what application), a tray icon of a printer appeared on the upper-right size of the . By clicking on it I could see the printing queue, the status of the jobs, I could manage printing jobs etc. Now in ubuntu 11.10 that icon does not appear any more. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: unity 4.24.0-0ubuntu2.1 ProcVersionSignature: Ubuntu 3.0.0-15.24-generic 3.0.13 Uname: Linux 3.0.0-15-generic i686 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86 Kernel Module 280.13 Wed Jul 27 16:55:43 PDT 2011 GCC version: gcc version 4.6.1 (Ubuntu/Linaro 4.6.1-9ubuntu3) .tmp.unity.support.test.0: ApportVersion: 1.23-0ubuntu4 Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,decor,vpswitch,mousepoll,compiztoolbox,snap,place,resize,session,regex,grid,wall,move,gnomecompat,imgpng,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: None Date: Wed Dec 21 17:10:33 2011 DistUpgraded: Log time: 2011-12-07 19:34:40.350850 DistroCodename: oneiric DistroVariant: ubuntu GraphicsCard: nVidia Corporation G84 [GeForce 9500M GS] [10de:0405] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:15d2] InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) JockeyStatus: xorg:nvidia_173 - NVIDIA accelerated graphics driver (Proprietary, Disabled, Not in use) xorg:nvidia_173_updates - NVIDIA accelerated graphics driver (post-release updates) (Proprietary, Disabled, Not in use) xorg:nvidia_current - NVIDIA accelerated graphics driver (Proprietary, Enabled, In use) pkg:sl-modem-daemon - Software modem (Proprietary, Disabled, Not in use) xorg:nvidia_current_updates - NVIDIA accelerated graphics driver (post-release updates) (Proprietary, Disabled, Not in use) MachineType: ASUSTeK Computer Inc. M51Sn ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-15-generic root=UUID=173acbf5-26a0-49e3-8d2b-f1c142582cbf ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to oneiric on 2011-12-07 (13 days ago) dmi.bios.date: 12/24/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: M51Sn dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr303:bd12/24/2007:svnASUSTeKComputerInc.:pnM51Sn:pvr1.0:rvnASUSTeKComputerInc.:rnM51Sn:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: M51Sn dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu6 version.libdrm2: libdrm2 2.4.26-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20110811.g93fc084-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/907411/+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 1442166] Re: Calendar alarms rings forever if Low Battery dialog visible
This same thing happened to me but with alarm clock: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1438036 (See comment #6) -- 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/1442166 Title: Calendar alarms rings forever if Low Battery dialog visible Status in the base for Ubuntu mobile products: Confirmed Status in indicator-datetime package in Ubuntu: New Status in usensord package in Ubuntu: New Bug description: I'm on rtm build 258 on krillin Steps to reproduce: - let battery run down on phone (was sitting unplugged for 1 or 2 days) - in the morning, a calendar alarm starting ringing/vibrating and would not stop - when I looked at the phone, the screen was on and I see the Low Battery dialog - after dismissing the dialog, then I see the notification for the alarm, and only after 5-10 more seconds does the ringing stop Seems like while the Low Battery dialog is displayed it keeps the alarm ringing forever To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1442166/+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 1443178] Re: Accounts Service always relies on language fallback if never set by the user
Not sure what unity8 could do here?
** Changed in: unity8 (Ubuntu)
Status: New => Incomplete
--
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/1443178
Title:
Accounts Service always relies on language fallback if never set by
the user
Status in the base for Ubuntu mobile products:
New
Status in accountsservice package in Ubuntu:
In Progress
Status in unity8 package in Ubuntu:
Incomplete
Bug description:
current build number: 169
device name: mako
channel: ubuntu-touch/devel-proposed
alias: ubuntu-touch/vivid-proposed
last update: 2015-04-12 20:38:14
version version: 169
version ubuntu: 20150412
version device: 20150210
version custom: 20150412
This causes a bad side effect when changing volume via indicator-
sound, as that will cause a sync to accountsservice in order to sync
the volume. Once that sync happens, it will request the user
properties, and in case the user doesn't have a valid language at
/var/lib/AccountsService/users/, it will always rely on the
fallback, which would be fine if calculating the fallback wasn't 't so
cpu or i/o intensive (and that happens multiple times).
As a test, just flash latest vivid image on mako, don't set any
language when the wizard shows up, run top and then change the volume
by pressing volume up/down. This is what I see with mako:
PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND
2609 phablet 20 0 499660 121220 52688 S 7.6 6.5 0:41.69 unity8
5600 phablet 20 03676 1760 1288 R 6.0 0.1 0:00.19
language-option
1312 root 20 0 211532 15572 11344 S 1.9 0.8 0:07.25
unity-system-co
1316 phablet 20 0 36532 3792 2928 S 1.3 0.2 0:01.66
accounts-daemon
And the reason why:
src/user.c
...
static void
user_get_property (GObject*object,
guint param_id,
GValue *value,
GParamSpec *pspec)
{
User *user = USER (object);
...
case PROP_LANGUAGE:
if (user->language)
g_value_set_string (value, user->language);
else
g_value_set_string (value, user_get_fallback_value
(user, "Language"));
break;
case PROP_FORMATS_LOCALE:
if (user->formats_locale)
g_value_set_string (value, user->formats_locale);
else
g_value_set_string (value, user_get_fallback_value
(user, "FormatsLocale"));
break;
user_set_property never gets called unless the user changes the system
language from system-settings or wizard.
Once you change the language, it will set a valid language at
/var/lib/AccountsService/users/, causing this behavior to stop.
Another bad side effect of this issue is that it takes quite a while
for accountsservice to reply back to indicator-sound when the sync
happens, possibly causing sync aborts (as indicator-sound only waits 1
second before triggering another sync).
Some possible ways to fix this issue:
1) Make wizard to set language even when the selected language is already the
default one;
2) Change accountsservice to save the fallback value at the first time it
gets that from the system;
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1443178/+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 1443178] Re: Accounts Service always relies on language fallback if never set by the user
** Changed in: accountsservice (Ubuntu)
Importance: Undecided => Medium
** Changed in: accountsservice (Ubuntu)
Status: New => Triaged
** Changed in: accountsservice (Ubuntu)
Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)
** Changed in: accountsservice (Ubuntu)
Status: Triaged => In Progress
--
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/1443178
Title:
Accounts Service always relies on language fallback if never set by
the user
Status in the base for Ubuntu mobile products:
New
Status in accountsservice package in Ubuntu:
In Progress
Status in unity8 package in Ubuntu:
New
Bug description:
current build number: 169
device name: mako
channel: ubuntu-touch/devel-proposed
alias: ubuntu-touch/vivid-proposed
last update: 2015-04-12 20:38:14
version version: 169
version ubuntu: 20150412
version device: 20150210
version custom: 20150412
This causes a bad side effect when changing volume via indicator-
sound, as that will cause a sync to accountsservice in order to sync
the volume. Once that sync happens, it will request the user
properties, and in case the user doesn't have a valid language at
/var/lib/AccountsService/users/, it will always rely on the
fallback, which would be fine if calculating the fallback wasn't 't so
cpu or i/o intensive (and that happens multiple times).
As a test, just flash latest vivid image on mako, don't set any
language when the wizard shows up, run top and then change the volume
by pressing volume up/down. This is what I see with mako:
PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND
2609 phablet 20 0 499660 121220 52688 S 7.6 6.5 0:41.69 unity8
5600 phablet 20 03676 1760 1288 R 6.0 0.1 0:00.19
language-option
1312 root 20 0 211532 15572 11344 S 1.9 0.8 0:07.25
unity-system-co
1316 phablet 20 0 36532 3792 2928 S 1.3 0.2 0:01.66
accounts-daemon
And the reason why:
src/user.c
...
static void
user_get_property (GObject*object,
guint param_id,
GValue *value,
GParamSpec *pspec)
{
User *user = USER (object);
...
case PROP_LANGUAGE:
if (user->language)
g_value_set_string (value, user->language);
else
g_value_set_string (value, user_get_fallback_value
(user, "Language"));
break;
case PROP_FORMATS_LOCALE:
if (user->formats_locale)
g_value_set_string (value, user->formats_locale);
else
g_value_set_string (value, user_get_fallback_value
(user, "FormatsLocale"));
break;
user_set_property never gets called unless the user changes the system
language from system-settings or wizard.
Once you change the language, it will set a valid language at
/var/lib/AccountsService/users/, causing this behavior to stop.
Another bad side effect of this issue is that it takes quite a while
for accountsservice to reply back to indicator-sound when the sync
happens, possibly causing sync aborts (as indicator-sound only waits 1
second before triggering another sync).
Some possible ways to fix this issue:
1) Make wizard to set language even when the selected language is already the
default one;
2) Change accountsservice to save the fallback value at the first time it
gets that from the system;
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1443178/+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
