[Dx-packages] [Bug 1392642] [NEW] Daemons are restarted in the current session cgroups
Public bug reported: (forwarded from the relevant bug report raised in Debian BTS and adapted for upstart as PID1) Daemons which are not spawned via an upstart job (eg. those with initscripts, ifupdown hooks and similar) are not detached from the current logind session cgroups. This causes the session to linger in the closing state until the background processes are either terminated or manually moved by root into the root cgroups, so seat ACLs are not released. A (very crude) workaround on Debian Jessie is using cgm movepidabs / $$ to break out of the current session before performing any administrative action which could result in a daemon (re)start, but cgmanager is not installed by default on Trusty and the version of cgm shipped with it lacks the movepidabs subcommand (even though the MovePidAbs method in the DBus interface does exist). Note that this affects anything that uses service, invoke-rc.d, ifupdown hooks (like ifup on PPPoE links) or initscripts directly. Upstart jobs are not affected because they inherit their cgroup set from PID1 (which lives in the root cgroup). Nota bene: I'm raising the issue on systemd-shim on advice from its maintainer, even though it's unclear at what level this behavior should be addressed. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: systemd-shim 6-2bzr1 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 Date: Fri Nov 14 10:36:01 2014 InstallationDate: Installed on 2012-09-30 (774 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) SourcePackage: systemd-shim UpgradeStatus: Upgraded to trusty on 2014-08-18 (87 days ago) ** Affects: systemd-shim (Ubuntu) Importance: Undecided Status: New ** Affects: systemd-shim (Debian) Importance: Unknown Status: Unknown ** Tags: amd64 apport-bug trusty ** Bug watch added: Debian Bug tracker #769483 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769483 ** Also affects: systemd-shim (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769483 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1392642 Title: Daemons are restarted in the current session cgroups Status in “systemd-shim” package in Ubuntu: New Status in “systemd-shim” package in Debian: Unknown Bug description: (forwarded from the relevant bug report raised in Debian BTS and adapted for upstart as PID1) Daemons which are not spawned via an upstart job (eg. those with initscripts, ifupdown hooks and similar) are not detached from the current logind session cgroups. This causes the session to linger in the closing state until the background processes are either terminated or manually moved by root into the root cgroups, so seat ACLs are not released. A (very crude) workaround on Debian Jessie is using cgm movepidabs / $$ to break out of the current session before performing any administrative action which could result in a daemon (re)start, but cgmanager is not installed by default on Trusty and the version of cgm shipped with it lacks the movepidabs subcommand (even though the MovePidAbs method in the DBus interface does exist). Note that this affects anything that uses service, invoke-rc.d, ifupdown hooks (like ifup on PPPoE links) or initscripts directly. Upstart jobs are not affected because they inherit their cgroup set from PID1 (which lives in the root cgroup). Nota bene: I'm raising the issue on systemd-shim on advice from its maintainer, even though it's unclear at what level this behavior should be addressed. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: systemd-shim 6-2bzr1 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 Date: Fri Nov 14 10:36:01 2014 InstallationDate: Installed on 2012-09-30 (774 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) SourcePackage: systemd-shim UpgradeStatus: Upgraded to trusty on 2014-08-18 (87 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1392642/+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 610234] Re: Should support changing shortcuts via can_change_accels (menu item selection + key combination)
Everything menu-related in Ubuntu was awful throughout the years. It's like multiple concurrent failed attempts to come up with something newer and better (like global menus) when in fact it just produces inconsistency and removes something that works and people are familiar with. Just upgraded to 14.04 only to find Nautilus has no menus whatsoever, and after 1h of searching I still don't get them. can_change_accels works in neither dconf nor gconf, and manually editing accels files doesn't work, and files are overwritten on next program quit (by program I mean e.g. gedit). The level of regression in the area of Menus is just horrible. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-appmenu in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/610234 Title: Should support changing shortcuts via can_change_accels (menu item selection + key combination) Status in The Application Menu: Triaged Status in “indicator-appmenu” package in Ubuntu: Triaged Bug description: Binary package hint: indicator-appmenu Standard GTK menus support changing keyboard shortcuts displayed on the right hand side of the menus by highlighting the menu item and pressing the new shortcut. The feature is controlled by the can_change_accels Gconf key and is often the only supported way to configure shortcuts in applications [1]. [1] http://mail.gnome.org/archives/evince-list/2010-July/msg00036.html To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-appmenu/+bug/610234/+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 1392642] Re: Daemons are restarted in the current session cgroups
** Changed in: systemd-shim (Debian) Status: Unknown = New -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1392642 Title: Daemons are restarted in the current session cgroups Status in “systemd-shim” package in Ubuntu: New Status in “systemd-shim” package in Debian: New Bug description: (forwarded from the relevant bug report raised in Debian BTS and adapted for upstart as PID1) Daemons which are not spawned via an upstart job (eg. those with initscripts, ifupdown hooks and similar) are not detached from the current logind session cgroups. This causes the session to linger in the closing state until the background processes are either terminated or manually moved by root into the root cgroups, so seat ACLs are not released. A (very crude) workaround on Debian Jessie is using cgm movepidabs / $$ to break out of the current session before performing any administrative action which could result in a daemon (re)start, but cgmanager is not installed by default on Trusty and the version of cgm shipped with it lacks the movepidabs subcommand (even though the MovePidAbs method in the DBus interface does exist). Note that this affects anything that uses service, invoke-rc.d, ifupdown hooks (like ifup on PPPoE links) or initscripts directly. Upstart jobs are not affected because they inherit their cgroup set from PID1 (which lives in the root cgroup). Nota bene: I'm raising the issue on systemd-shim on advice from its maintainer, even though it's unclear at what level this behavior should be addressed. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: systemd-shim 6-2bzr1 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 Date: Fri Nov 14 10:36:01 2014 InstallationDate: Installed on 2012-09-30 (774 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) SourcePackage: systemd-shim UpgradeStatus: Upgraded to trusty on 2014-08-18 (87 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1392642/+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 1307559] Re: Window decorations not drawn on external monitor
Problem still exists in 14.10. I am using Dell E6230 laptop connected to HDMI monitor. -- 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/1307559 Title: Window decorations not drawn on external monitor Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: Window decorations (close / minimize / maximize buttons) do not draw on the external monitor on a laptop with external display. Windows on the laptop display are not affected. UI scale on the built-in display is 1.25; it's 1.0 on the external display. I am not sure if this is relevant. To reproduce: 1) Plug in an external monitor to a laptop; ensure that it is running in extended display mode 2) Launch an application such as the terminal 3) The terminal launches on the laptop's built-in display. Observe the window decorations draw as expected 4) Drag the terminal window to the second display Expected results; The terminal window is drawn on the extended display Actual results: The terminal window is drawn on the extended display but the close, minimize, and maximize buttons are missing. The problem happens on windows from all applications I've tried (firefox, terminal, emacs, thunderbird) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Apr 14 10:56:46 2014 DistUpgraded: 2014-02-12 13:40:42,704 DEBUG enabling apt cron job DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fwts-efi-runtime-dkms, 14.03.01, 3.13.0-23-generic, x86_64: installed fwts-efi-runtime-dkms, 14.03.01, 3.13.0-24-generic, x86_64: installed virtualbox, 4.3.10, 3.13.0-23-generic, x86_64: installed virtualbox, 4.3.10, 3.13.0-24-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:060a] InstallationDate: Installed on 2013-12-02 (132 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 MachineType: Dell Inc. XPS13 9333 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=0b9db31c-747b-40ad-bbbd-13a9a29caece ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-02-12 (60 days ago) dmi.bios.date: 11/11/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 0GFTRT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA01:bd11/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Apr 14 08:54:29 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4933 vendor CMN xserver.version: 2:1.15.0-1ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1307559/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help :
[Dx-packages] [Bug 1387711] Re: Unity doesn't respect NET_WM_ALLOWED_ACTIONS
In that case, I have no idea how I'm supposed to remove allowed actions using this atom. Reading the specification makes me think that passing a list that doesn't include _NET_WM_ACTION_RESIZE should cause it to be removed from the list: 'Atoms present in the list indicate allowed actions, atoms not present in the list indicate actions that are not supported for this window. The Window Manager MUST keep this property updated to reflect the actions which are currently active or sensitive for a window.' If the property change isn't reflected, maybe it's an xorg bug instead? Or maybe the properties are getting (re-)initialized by the decorator when the window is mapped? -- 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/1387711 Title: Unity doesn't respect NET_WM_ALLOWED_ACTIONS Status in Unity: Incomplete Status in “unity” package in Ubuntu: Incomplete Bug description: According to http://standards.freedesktop.org/wm-spec/latest/ar01s05.html : Atoms present in the list indicate allowed actions, atoms not present in the list indicate actions that are not supported for this window. The Window Manager MUST keep this property updated to reflect the actions which are currently active or sensitive for a window. However, if I set NET_WM_ALLOWED_ACTIONS to a list not containing NET_WM_ACTION_RESIZE (along with the MAXIMIZE atoms), I can still resize/maximize the window using the mouse. Only by forcing min and max size in the WM normal hints can I achieve the desired behavior. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,compiztoolbox,vpswitch,move,gnomecompat,grid,place,regex,imgpng,resize,annotate,mousepoll,wobbly,session,animation,fade,animationaddon,cube,rotate,workarounds,unitymtgrabhandles,cubeaddon,trailfocus,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Thu Oct 30 15:19:30 2014 InstallationDate: Installed on 2011-05-11 (1267 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-10-27 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1387711/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
Re: [Dx-packages] [Bug 1003950] Re: launcher does not show minimized update manager while clicked
Excuse me? On Nov 13, 2014 8:55 AM, John Muir 1003...@bugs.launchpad.net wrote: Such enlightening and helpful comments could only come from someone used to Microsoft software ;-) -- You received this bug notification because you are subscribed to a duplicate bug report (925260). https://bugs.launchpad.net/bugs/1003950 Title: launcher does not show minimized update manager while clicked Status in Unity: Fix Released Status in Unity 5.0 series: Fix Released Status in Unity 6.0 series: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “update-manager” package in Ubuntu: Confirmed Status in “unity” source package in Precise: Fix Released Status in “update-manager” source package in Precise: Confirmed Status in “unity” source package in Quantal: Fix Released Status in “update-manager” source package in Quantal: Confirmed Bug description: Update manager is showing up in the dock but I can click on the icon all day and nothing happens. Similarly if I do Super-S or Super-W it doesn't show up anywhere. Even if I alt-tab to the application nothing shows up. This happens only when update manager runs on its own. If I kill it and then launch it myself it comes to the foreground just fine. I'm not 100% sure whether this is a unity, compiz, or update-manager bug but so far my bet is on unity. =Original Report= Bug #877444 is showing again in latest updates, please re-open it. This is the exact same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1003950/+subscriptions -- 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/1003950 Title: launcher does not show minimized update manager while clicked Status in Unity: Fix Released Status in Unity 5.0 series: Fix Released Status in Unity 6.0 series: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “update-manager” package in Ubuntu: Confirmed Status in “unity” source package in Precise: Fix Released Status in “update-manager” source package in Precise: Confirmed Status in “unity” source package in Quantal: Fix Released Status in “update-manager” source package in Quantal: Confirmed Bug description: Update manager is showing up in the dock but I can click on the icon all day and nothing happens. Similarly if I do Super-S or Super-W it doesn't show up anywhere. Even if I alt-tab to the application nothing shows up. This happens only when update manager runs on its own. If I kill it and then launch it myself it comes to the foreground just fine. I'm not 100% sure whether this is a unity, compiz, or update-manager bug but so far my bet is on unity. =Original Report= Bug #877444 is showing again in latest updates, please re-open it. This is the exact same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1003950/+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 1386255] Re: devhelp and many other apps crash with SIGSEGV in g_closure_invoke() due to overlay-scrollbars
** Changed in: overlay-scrollbar (Ubuntu) Status: Confirmed = In Progress ** Changed in: overlay-scrollbar (Ubuntu) Assignee: Lars Uebernickel (larsu) = Sebastien Bacher (seb128) -- You received this bug notification because you are a member of DX Packages, which is subscribed to overlay-scrollbar in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1386255 Title: devhelp and many other apps crash with SIGSEGV in g_closure_invoke() due to overlay-scrollbars Status in Overlay Scrollbar: New Status in Ubuntu GNOME: New Status in “overlay-scrollbar” package in Ubuntu: In Progress Bug description: With the gnome3-team/gnome3-staging PPA enabled all Gtk+ applications segfault when I do stuff like - Press the Menu key - Press the Save button in gedit's headerbar - Press the hamburger menu button in devhelp's headerbar (the stack trace attached to this bug) - Press the Add button in gtimelog - Try to open any of the regular menus in gtimelog ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: devhelp 3.14.0-1~utopic1 [origin: LP-PPA-gnome3-team-gnome3-staging] ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 27 17:15:30 2014 Disassembly: = 0x0: Cannot access memory at address 0x0 EcryptfsInUse: Yes ExecutablePath: /usr/bin/devhelp InstallationDate: Installed on 2012-07-25 (824 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) ProcCmdline: devhelp SegvAnalysis: Segfault happened at: 0x0: Cannot access memory at address 0x0 PC (0x) not located in a known VMA region (needed executable region)! SegvReason: executing NULL VMA Signal: 11 SourcePackage: devhelp StacktraceTop: ?? () g_closure_invoke (closure=0x11e4ce0, return_value=0x0, n_param_values=2, param_values=0x7fffd6ed0920, invocation_hint=0x7fffd6ed08c0) at /build/buildd/glib2.0-2.42.0/./gobject/gclosure.c:768 signal_emit_unlocked_R (node=node@entry=0x11e50b0, detail=detail@entry=0, instance=instance@entry=0x182a510, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7fffd6ed0920) at /build/buildd/glib2.0-2.42.0/./gobject/gsignal.c:3483 g_signal_emit_valist (instance=optimized out, signal_id=optimized out, detail=optimized out, var_args=var_args@entry=0x7fffd6ed0ab0) at /build/buildd/glib2.0-2.42.0/./gobject/gsignal.c:3309 g_signal_emit (instance=instance@entry=0x182a510, signal_id=optimized out, detail=detail@entry=0) at /build/buildd/glib2.0-2.42.0/./gobject/gsignal.c:3365 Title: devhelp crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: Upgraded to utopic on 2014-10-24 (3 days ago) UserGroups: adm cdrom dip docker libvirtd lp lpadmin plugdev sambashare shared sudo wireshark To manage notifications about this bug go to: https://bugs.launchpad.net/overlay-scrollbar/+bug/1386255/+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 1392770] [NEW] Three fingered tap kills apple touchpad input
Public bug reported: I have the apple magic trackpad paired with my Ubuntu 14.04 desktop. It works fine until a 3 fingered tap (usually accidental), when it stops responding to input at all. After several minutes it starts functioning again, usually quicker if I execute sudo hciconfig hci0 reset. The problem is also described here (by someone else): http://superuser.com/questions/724282/apple-magic-trackpad-is-working- great-then-randomly-stops-until-hciconfig-reset ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Nov 14 15:40:04 2014 InstallationDate: Installed on 2014-03-14 (245 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140314) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1392770 Title: Three fingered tap kills apple touchpad input Status in “unity” package in Ubuntu: New Bug description: I have the apple magic trackpad paired with my Ubuntu 14.04 desktop. It works fine until a 3 fingered tap (usually accidental), when it stops responding to input at all. After several minutes it starts functioning again, usually quicker if I execute sudo hciconfig hci0 reset. The problem is also described here (by someone else): http://superuser.com/questions/724282/apple-magic-trackpad-is-working- great-then-randomly-stops-until-hciconfig-reset ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Nov 14 15:40:04 2014 InstallationDate: Installed on 2014-03-14 (245 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140314) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1392770/+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 1387711] Re: Unity doesn't respect NET_WM_ALLOWED_ACTIONS
Ok, I've given another read to the specs, and well, this atom as most of the NET_WM_* atoms must be filled by the window manager, to notify people around (in the old days where each process/component was an element of the shell) about what actions it can support for the given window, and it has not to be set by the window itself. In fact your example works only if you launch it with no window manager set. If an app doesn't want to be resizable, it should inform the WM using another protocol (and in this case the _MOTIF_WM_HINTS) as shown in the attached example (setting that hint the WM will update correctly the NET_WM_ALLOWED_ACTIONS). ** Attachment added: allowed-actions-mwm.c https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1387711/+attachment/4260539/+files/allowed-actions-mwm.c ** Changed in: unity Status: Incomplete = Won't Fix ** Changed in: unity (Ubuntu) Status: Incomplete = Won't Fix -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1387711 Title: Unity doesn't respect NET_WM_ALLOWED_ACTIONS Status in Unity: Won't Fix Status in “unity” package in Ubuntu: Won't Fix Bug description: According to http://standards.freedesktop.org/wm-spec/latest/ar01s05.html : Atoms present in the list indicate allowed actions, atoms not present in the list indicate actions that are not supported for this window. The Window Manager MUST keep this property updated to reflect the actions which are currently active or sensitive for a window. However, if I set NET_WM_ALLOWED_ACTIONS to a list not containing NET_WM_ACTION_RESIZE (along with the MAXIMIZE atoms), I can still resize/maximize the window using the mouse. Only by forcing min and max size in the WM normal hints can I achieve the desired behavior. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,compiztoolbox,vpswitch,move,gnomecompat,grid,place,regex,imgpng,resize,annotate,mousepoll,wobbly,session,animation,fade,animationaddon,cube,rotate,workarounds,unitymtgrabhandles,cubeaddon,trailfocus,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Thu Oct 30 15:19:30 2014 InstallationDate: Installed on 2011-05-11 (1267 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-10-27 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1387711/+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 1387691] Re: Media Player should not be visible in the app scope and launcher
** Changed in: mediaplayer-app Status: New = In Progress ** Changed in: mediaplayer-app (Ubuntu) Status: Confirmed = In Progress ** Also affects: mediaplayer-app (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: mediaplayer-app (Ubuntu RTM) Status: New = In Progress ** Changed in: mediaplayer-app Importance: Undecided = Medium -- You received this bug notification because you are a member of DX Packages, which is subscribed to url-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1387691 Title: Media Player should not be visible in the app scope and launcher Status in Media Player App: In Progress Status in Ubuntu UX bugs: Fix Committed Status in “mediaplayer-app” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu: Incomplete Status in “url-dispatcher” package in Ubuntu: Incomplete Status in “mediaplayer-app” package in Ubuntu RTM: In Progress Bug description: The mediaplayer is an 'auxiliary app' in the current design approach. That means that its purpouse it playback media launched by other apps (e.g Messaging) or scopes (e.g. Videos). It should not be launched from the App scopes. However, the 'Update' section System Settings should still display it when an update to mediaplayer is available. Current behaviour - Mediaplayer app displayed in App Scope, Launcher and Settings Desired behaviour - Mediaplayer app not displayed in App Scope or Launcher - Mediaplayer displayed in Settings Update To manage notifications about this bug go to: https://bugs.launchpad.net/mediaplayer-app/+bug/1387691/+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 1387691] Re: Media Player should not be visible in the app scope and launcher
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mediaplayer-app (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to url-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1387691 Title: Media Player should not be visible in the app scope and launcher Status in Media Player App: In Progress Status in Ubuntu UX bugs: Fix Committed Status in “mediaplayer-app” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu: Incomplete Status in “url-dispatcher” package in Ubuntu: Incomplete Status in “mediaplayer-app” package in Ubuntu RTM: In Progress Bug description: The mediaplayer is an 'auxiliary app' in the current design approach. That means that its purpouse it playback media launched by other apps (e.g Messaging) or scopes (e.g. Videos). It should not be launched from the App scopes. However, the 'Update' section System Settings should still display it when an update to mediaplayer is available. Current behaviour - Mediaplayer app displayed in App Scope, Launcher and Settings Desired behaviour - Mediaplayer app not displayed in App Scope or Launcher - Mediaplayer displayed in Settings Update To manage notifications about this bug go to: https://bugs.launchpad.net/mediaplayer-app/+bug/1387691/+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 1392844] [NEW] Unity crashes, doesn't restart and window borders are gone
Public bug reported: 1) Description:Ubuntu 14.04.1 LTS Release:14.04 2) unity: 7.2.2+14.04.20140714-0ubuntu1.1 3) Continue to run smoothly. 4) It crashed. I may have pressed the key for Ubuntu Dash Search (Super). After the crash, Super, ALT + F2 and ALT + TAB had no effect. The window borders were gone. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Nov 14 20:10:02 2014 InstallationDate: Installed on 2014-04-18 (209 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1392844 Title: Unity crashes, doesn't restart and window borders are gone Status in “unity” package in Ubuntu: New Bug description: 1) Description: Ubuntu 14.04.1 LTS Release: 14.04 2) unity: 7.2.2+14.04.20140714-0ubuntu1.1 3) Continue to run smoothly. 4) It crashed. I may have pressed the key for Ubuntu Dash Search (Super). After the crash, Super, ALT + F2 and ALT + TAB had no effect. The window borders were gone. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Nov 14 20:10:02 2014 InstallationDate: Installed on 2014-04-18 (209 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1392844/+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 1341562] Re: indicator-printers not working on Ubuntu 14.04
I think I have spotted what makes this bug happen and what makes the icon work. If I enter my password promptly when the dialog comes up, the icon usually doesn't work. If I delay (e.g. fire up the computer, then go and do something else before coming back to enter my password) it invariably does. I hope this narrows down the possibilities of what may be causing the bug, e.g. some process that is interrupted by the completion of the password dialog. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-printers in Ubuntu. https://bugs.launchpad.net/bugs/1341562 Title: indicator-printers not working on Ubuntu 14.04 Status in “indicator-printers” package in Ubuntu: Confirmed Bug description: This is a regression from bug 1304434 The bug is still there for quite a lot of users including myself. Please can the Ubuntu Dev Team look into this bug again for us please. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-printers/+bug/1341562/+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 1301125] Re: Lock screen after idle time freezes unity
I am having same exact issue on brand-new install of 14.04 on homegrown computer. I am new to Linux... Just got tired of Windows when WIN8 was released. Learning about ctrl+alt+f1 will be helpful until a fix (?) Is 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/1301125 Title: Lock screen after idle time freezes unity Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: Hello, I recently upgrade to 14.04. My system uses fglrx provided by 14.04. When I lock manually the screen, I get no problem. I can even sleep the system without problem. However, when the screen is locked by idle time, I cannot unlock it. At this point, I can see the screen but with some kind of translucent panel over it. Mouse also works. I tried to type blink the password but I had no luck. I only get a working system by going text mode (ctrl+alt+f1) and restarting lightdm. No dmesg or Xorg logs seems to indicate any error. The only strange log was in .xsession-errors.old: init: processos unity-settings-daemon main (2495) terminados com status 1 init: processos gnome-session (Unity) main (2539) terminados com status 1 init: processos unity-panel-service main (2572) terminados com status 1 init: processos hud main (2536) terminados com status 1 init: processo indicator-powermain (2740) morto pelo sinal TERM init: processo indicator-datetimemain (2741) morto pelo sinal TERM init: processo indicator-soundmain (2747) morto pelo sinal TERM init: processo indicator-printersmain (2748) morto pelo sinal TERM init: processo indicator-sessionmain (2768) morto pelo sinal TERM init: processo indicator-syncmain (2795) morto pelo sinal TERM init: processo update-notifier-crash (/var/crash/_usr_bin_istanbul.1000.crash)main (4987) morto pelo sinal TERM init: processos unity-panel-service-lockscreen main (7447) terminados com status 1 init: Disconnected from notified D-Bus bus init: processos at-spi2-registryd main (2538) terminados com status 1 But as it has no time info, I cannot tell when they happened. At least another user faces the same problem: http://ubuntuforums.org/showthread.php?t=2214421 And this seems to be different from bug 1283938 as pm sleep/wake works as expected. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140328.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14-0ubuntu1 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] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Apr 2 00:01:05 2014 DistUpgraded: 2014-03-31 21:24:46,145 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx-updates, 13.350.1, 3.11.0-18-generic, x86_64: installed fglrx-updates, 13.350.1, 3.13.0-20-generic, x86_64: installed vboxhost, 4.3.10, 3.11.0-18-generic, x86_64: installed vboxhost, 4.3.10, 3.13.0-20-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] [1002:6758] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0012] InstallationDate: Installed on 2012-10-19 (529 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) JockeyStatus: kmod:wl - Broadcom STA wireless driver (Proprietário, Desativado, Não está em uso) [auto-install] kmod:fglrx - Video driver for the AMD graphics accelerators (Proprietário, Desativado, Não está em uso) kmod:fglrx_updates - ATI Fire GL (Proprietário, Habilitado, Não está em uso) MachineType: Dell Inc. XPS 8300 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic root=UUID=6633d579-d782-47ec-ad5a-22abac1412a0 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-04-01 (1 days ago) dmi.bios.date: 10/17/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0Y2MRG dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd10/17/2011:svnDellInc.:pnXPS8300:pvr:rvnDellInc.:rn0Y2MRG:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.name: XPS 8300 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1
[Dx-packages] [Bug 1392910] [NEW] Valid links placed on desktop reported as broken after logon
Public bug reported: Steps to reproduce: - place on the Desktop some symbolic links to directories that are somewhere below /media (e.g. with drag-and-drop from Files) - restart ubuntu and log on again - the links now appear in the desktop as broken links (with a padlock in the icon, see attached screenshot) - clicking on the link icon and try to open it, you get an error message, and the linked directory does not open; the directory is expected to open in Files Workaround: - navigate to the linked directory by mean of Files or with command CD in a shell - click on the background of the desktop - hit F5 on the keyboard - now the links change icon, and by clicking on them they open as expected The issue is systematic. 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 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sat Nov 15 01:20:02 2014 InstallationDate: Installed on 2014-11-12 (2 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic ** Attachment added: Screenshot from 2014-11-15 01:05:49.png https://bugs.launchpad.net/bugs/1392910/+attachment/4260834/+files/Screenshot%20from%202014-11-15%2001%3A05%3A49.png -- 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/1392910 Title: Valid links placed on desktop reported as broken after logon Status in “unity” package in Ubuntu: New Bug description: Steps to reproduce: - place on the Desktop some symbolic links to directories that are somewhere below /media (e.g. with drag-and-drop from Files) - restart ubuntu and log on again - the links now appear in the desktop as broken links (with a padlock in the icon, see attached screenshot) - clicking on the link icon and try to open it, you get an error message, and the linked directory does not open; the directory is expected to open in Files Workaround: - navigate to the linked directory by mean of Files or with command CD in a shell - click on the background of the desktop - hit F5 on the keyboard - now the links change icon, and by clicking on them they open as expected The issue is systematic. 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 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sat Nov 15 01:20:02 2014 InstallationDate: Installed on 2014-11-12 (2 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1392910/+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 1003950] Re: launcher does not show minimized update manager while clicked
I haven't experienced this bug in a while, but the only similarity in my set up to Justin's is the multiple monitors. My setup was a laptop and external monitor. I might have had them configured to show the dock on both screens, but I've changed it to show only on the left, external monitor screen. -- 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/1003950 Title: launcher does not show minimized update manager while clicked Status in Unity: Fix Released Status in Unity 5.0 series: Fix Released Status in Unity 6.0 series: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “update-manager” package in Ubuntu: Confirmed Status in “unity” source package in Precise: Fix Released Status in “update-manager” source package in Precise: Confirmed Status in “unity” source package in Quantal: Fix Released Status in “update-manager” source package in Quantal: Confirmed Bug description: Update manager is showing up in the dock but I can click on the icon all day and nothing happens. Similarly if I do Super-S or Super-W it doesn't show up anywhere. Even if I alt-tab to the application nothing shows up. This happens only when update manager runs on its own. If I kill it and then launch it myself it comes to the foreground just fine. I'm not 100% sure whether this is a unity, compiz, or update-manager bug but so far my bet is on unity. =Original Report= Bug #877444 is showing again in latest updates, please re-open it. This is the exact same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1003950/+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 1389008] Re: Often fails to connect to Pulseaudio and unity-notifications (results in missing volume notifications and improper volume control)
** Branch linked: lp:ubuntu/ubuntu-touch-session -- 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/1389008 Title: Often fails to connect to Pulseaudio and unity-notifications (results in missing volume notifications and improper volume control) Status in “indicator-sound” package in Ubuntu: Invalid Status in “ubuntu-touch-session” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu: Confirmed Status in “indicator-sound” package in Ubuntu RTM: Invalid Status in “ubuntu-touch-session” package in Ubuntu RTM: Confirmed Status in “unity8” package in Ubuntu RTM: New Bug description: Often after boot indicator-sound fails to connect to Pulseaudio and to unity-notifications using libnotify. Therefore, volume notifications aren't shown and changes to the volume role go unnoticed, which then results in improper volume control. As already mentioned in the original bug description, running restart indicator-sound resolves the issue. Original description: Happens often after phone boot where changing volume by touch or by phone buttons. Volume correctly changes, but the org.freedesktop.Notifications popup isn't displayed. The problem seems fixes itself if you run restart indicator-sound, so maybe there's an issue with i-sound and unity-notifications starting at the same time, with the former querying the latter's capabilities before it's ready for business? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1389008/+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
