[Dx-packages] [Bug 1100546] Re: Power indicator favours 'not present' mouse over laptop battery level
We try to stick to a rule that each indicator has one icon and/or one piece of text. If we diverged from that, it would be harder to tell when every indicator ended and the next began. -- 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/1100546 Title: Power indicator favours 'not present' mouse over laptop battery level Status in The Power Indicator: Triaged Status in “indicator-power” package in Ubuntu: Triaged Bug description: The power indicator shows the battery level for cordless mice and keyboards, even when it cannot identify the battery level. This is a problem as it seems to favour showing a not present mouse status over the laptop battery level in the top bar. I haven't done a good job of explaining it, so check out the screenshot - it will explain all :) Basically, the laptop battery should be shown in the top bar if the mouse/keyboard is not present. Also hiding the mouse and keyboard when the battery level is unknown would also be useful too :) ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: indicator-power 12.10.6daily12.11.21.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-0.3-generic 3.8.0-rc3 Uname: Linux 3.8.0-0-generic x86_64 ApportVersion: 2.8-0ubuntu1 Architecture: amd64 Date: Thu Jan 17 10:11:16 2013 InstallationDate: Installed on 2012-12-14 (33 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20121214) MarkForUpload: True SourcePackage: indicator-power UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-power/+bug/1100546/+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 1314587] Re: Windows slow/stall/freeze when minimizing/restoring/etc in Unity 7 14.04
There seems to be an ibus problem with similar symptoms: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1276186 (added workaround there, but that workaround doesn't fix this issue). -- 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/1314587 Title: Windows slow/stall/freeze when minimizing/restoring/etc in Unity 7 14.04 Status in “unity” package in Ubuntu: Confirmed Status in “xorg” package in Ubuntu: Confirmed Bug description: Steps to reproduce: * Minimize current window or alt-tab between windows * Reveal launcher to click on application * Click `Super` to bring up Dash * Hold `Super` to bring up Keyboard Shortcuts What should happen: Action completes smoothly and quickly. What happens instead: * Action may be slow / animation jerky. * Action may stall (animation frozen on given frame, e.g. window partially minimized) - initiating another action cancels first action and second action may succeed (most often calling Guake with F12 seems to solve the issue) * Action may freeze - cursor no longer moves - a soft reboot (Alt+PrtScr+REISUB) usually works, otherwise a hard reboot Notes: * Not application specific. Minimizing is reliably slow/stalls with minimizing Firefox (including 29, I do not have a lot of bookmarks) or Pidgin, but I use those programs more often. * I am using an Nvidia Optimus machine with the default Nouveau driver - no `nvidia-prime`, no Bumblebee. I temporarily installed the latest stable Nvidia driver (including `nvidia-prime`) and it made no difference. * I did not experience this issue on the same machine running 13.10 (with Bumblebee). * I am running Maximus. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 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-0ubuntu3 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 30 12:53:15 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10, 3.13.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:04b6] NVIDIA Corporation GF108M [GeForce GT 525M] [10de:0df5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:04b6] InstallationDate: Installed on 2014-04-24 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Dell Inc. Dell System XPS L502X ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=3a8fb3f3-1054-45a0-8ec0-0cbeba33da00 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0YR8NN 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.:bvrA04:bd03/25/2011:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0YR8NN:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L502X 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-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 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: Wed Apr 30 12:03:43 2014 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs:
[Dx-packages] [Bug 1330037] Re: upower 0.99 transition
** Description changed: upower 0.99 needs uploading for gnome 3.12. This bug tracks the transition. A transition is required as some features were removed and the SONAME was changed Some packages are staged in https://launchpad.net/~noskcaj/+archive/upower/+packages - wmbattery will probably need removing. If a package only needs a - rebuild, mark it fix commited, if something else is needed, in progress. + wmbattery and sugar will probably need removing. If a package only needs + a rebuild, mark it fix commited, if something else is needed, in + progress. cairo-dock-plug-ins: needs rebuilding gnome-applets - patch at bgo:730588 gnome-shell - ready, just need to drop upower revert. gnome-control-center: WIP gnome-packagekit: Upower dropped from newest upstream release. Merge from debian gnome-power-manager: Fixed in newest upstream release. Merge from debian experimental gnome-session: Done in ppa, needs patches from git or new upstream release gnome-settings-daemon: 3.12 is ready out of the box, however that also requires gnome-desktop transition. 3.8 and also u-s-d: I have a package that is mostly working, however had to cherry-pick quite a few patches and may just be better to backport 3.12 power plugin. (considering g-s-d patches will be temporary, but u-s-d not so) kde: works fine with systemd, suspend and device management broken with upstart mate: all mate packages need rebuilding python-dbusmock: lp:1324791 sugar: Upstream bug now filed. Unlikely to be ready in time for 14.10. We should remove this from the archive till the next upstream release telepathy-mission-control-5: Debian has dropped upower support, needs merging wmbattery: needs removal. orphaned upstream/debian and doesn't work with new kernals xfce4-power-manager: Fixed upstream. Merge at lp:1334185. Will need rebuilding xfce4-session: patch is upstream, needs work to apply with our current patchset xfce4-settings: Patch from upstream in ppa xfce4-systemload-plugin: needs rebuild -- 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/1330037 Title: upower 0.99 transition Status in “cairo-dock-plug-ins” package in Ubuntu: Fix Committed Status in “gnome-applets” package in Ubuntu: New Status in “gnome-control-center” package in Ubuntu: New Status in “gnome-packagekit” package in Ubuntu: Fix Released Status in “gnome-power-manager” package in Ubuntu: New Status in “gnome-session” package in Ubuntu: New Status in “gnome-settings-daemon” package in Ubuntu: New Status in “gnome-shell” package in Ubuntu: New Status in “indicator-power” package in Ubuntu: Triaged Status in “kde4libs” package in Ubuntu: New Status in “mate-applets” package in Ubuntu: New Status in “mate-power-manager” package in Ubuntu: New Status in “mate-session-manager” package in Ubuntu: New Status in “mutter” package in Ubuntu: New Status in “powerd” package in Ubuntu: New Status in “python-dbusmock” package in Ubuntu: New Status in “razorqt” package in Ubuntu: New Status in “sugar-0.96” package in Ubuntu: New Status in “sugar-0.98” package in Ubuntu: New Status in “telepathy-mission-control-5” package in Ubuntu: New Status in “tracker” package in Ubuntu: New Status in “ubuntu-system-settings” package in Ubuntu: New Status in “unity-control-center” package in Ubuntu: New Status in “unity-settings-daemon” package in Ubuntu: New Status in “upower” package in Ubuntu: New Status in “xfce4-power-manager” package in Ubuntu: New Status in “xfce4-session” package in Ubuntu: New Status in “xfce4-settings” package in Ubuntu: New Status in “xfce4-systemload-plugin” package in Ubuntu: Fix Committed Status in “wmbattery” package in Debian: New Bug description: upower 0.99 needs uploading for gnome 3.12. This bug tracks the transition. A transition is required as some features were removed and the SONAME was changed Some packages are staged in https://launchpad.net/~noskcaj/+archive/upower/+packages wmbattery and sugar will probably need removing. If a package only needs a rebuild, mark it fix commited, if something else is needed, in progress. cairo-dock-plug-ins: needs rebuilding gnome-applets - patch at bgo:730588 gnome-shell - ready, just need to drop upower revert. gnome-control-center: WIP gnome-packagekit: Upower dropped from newest upstream release. Merge from debian gnome-power-manager: Fixed in newest upstream release. Merge from debian experimental gnome-session: Done in ppa, needs patches from git or new upstream release gnome-settings-daemon: 3.12 is ready out of the box, however that also requires gnome-desktop transition. 3.8 and also u-s-d: I have a package that is mostly working, however had to cherry-pick quite a few patches and may just be better to backport 3.12 power plugin.
[Dx-packages] [Bug 1330037] Re: upower 0.99 transition
** Changed in: mutter (Ubuntu) Status: New = In Progress -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1330037 Title: upower 0.99 transition Status in “cairo-dock-plug-ins” package in Ubuntu: Fix Committed Status in “gnome-applets” package in Ubuntu: New Status in “gnome-control-center” package in Ubuntu: New Status in “gnome-packagekit” package in Ubuntu: Fix Released Status in “gnome-power-manager” package in Ubuntu: New Status in “gnome-session” package in Ubuntu: New Status in “gnome-settings-daemon” package in Ubuntu: New Status in “gnome-shell” package in Ubuntu: New Status in “indicator-power” package in Ubuntu: Triaged Status in “kde4libs” package in Ubuntu: New Status in “mate-applets” package in Ubuntu: New Status in “mate-power-manager” package in Ubuntu: New Status in “mate-session-manager” package in Ubuntu: New Status in “mutter” package in Ubuntu: In Progress Status in “powerd” package in Ubuntu: New Status in “python-dbusmock” package in Ubuntu: New Status in “razorqt” package in Ubuntu: New Status in “sugar-0.96” package in Ubuntu: New Status in “sugar-0.98” package in Ubuntu: New Status in “telepathy-mission-control-5” package in Ubuntu: New Status in “tracker” package in Ubuntu: New Status in “ubuntu-system-settings” package in Ubuntu: New Status in “unity-control-center” package in Ubuntu: New Status in “unity-settings-daemon” package in Ubuntu: New Status in “upower” package in Ubuntu: New Status in “xfce4-power-manager” package in Ubuntu: New Status in “xfce4-session” package in Ubuntu: New Status in “xfce4-settings” package in Ubuntu: New Status in “xfce4-systemload-plugin” package in Ubuntu: Fix Committed Status in “wmbattery” package in Debian: New Bug description: upower 0.99 needs uploading for gnome 3.12. This bug tracks the transition. A transition is required as some features were removed and the SONAME was changed Some packages are staged in https://launchpad.net/~noskcaj/+archive/upower/+packages wmbattery and sugar will probably need removing. If a package only needs a rebuild, mark it fix commited, if something else is needed, in progress. cairo-dock-plug-ins: needs rebuilding gnome-applets - patch at bgo:730588 gnome-shell - ready, just need to drop upower revert. gnome-control-center: WIP gnome-packagekit: Upower dropped from newest upstream release. Merge from debian gnome-power-manager: Fixed in newest upstream release. Merge from debian experimental gnome-session: Done in ppa, needs patches from git or new upstream release gnome-settings-daemon: 3.12 is ready out of the box, however that also requires gnome-desktop transition. 3.8 and also u-s-d: I have a package that is mostly working, however had to cherry-pick quite a few patches and may just be better to backport 3.12 power plugin. (considering g-s-d patches will be temporary, but u-s-d not so) kde: works fine with systemd, suspend and device management broken with upstart mate: all mate packages need rebuilding python-dbusmock: lp:1324791 sugar: Upstream bug now filed. Unlikely to be ready in time for 14.10. We should remove this from the archive till the next upstream release telepathy-mission-control-5: Debian has dropped upower support, needs merging wmbattery: needs removal. orphaned upstream/debian and doesn't work with new kernals xfce4-power-manager: Fixed upstream. Merge at lp:1334185. Will need rebuilding xfce4-session: patch is upstream, needs work to apply with our current patchset xfce4-settings: Patch from upstream in ppa xfce4-systemload-plugin: needs rebuild To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo-dock-plug-ins/+bug/1330037/+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 1319352] Re: indicator-application does not work in MATE 1.8
Exactly the same behavior in Xubuntu 14.10 with MATE 1.8 installed from Ubuntu repositories. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-application in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1319352 Title: indicator-application does not work in MATE 1.8 Status in “indicator-application” package in Ubuntu: Confirmed Bug description: Ubuntu version: Xubuntu 14.04 LTS indicator-application version: 12.10.1+14.04.20140407-0ubuntu1 indicator-application-gtk2 version: 12.10.0.1-0ubuntu2 Steps to reproduce: 1. Install Xubuntu 14.04 2. Install MATE 1.8 following the instructions at http://www.webupd8.org/2014/03/how-to-install-mate-18-in-ubuntu.html 3. Install mate-indicator-applet (a container for the indicators) and add it to MATE panel 4. Install indicator-application and indicator-application-gtk2 What expected to happen: Working indicator-application, displaying the network manager icon in mate-indicator-applet area. At the same time, the network manager icon should disappear from the notification area. What happened instead: The indicator-application apparently does not run. No network manager icon is displayed in mate-indicator-applet area. The network manager icon is still displayed in the notification area. Additional info: 1. All the steps above worked fine before in Ubuntu 13.10. 2. If I manually run /usr/lib/x86_64-linux-gnu/indicator-application/indicator-application-service from the terminal, the network manager icon disappears from the notification area, but it still doesn't appear in mate-indicator-applet area. At the same time, a message is displayed in the terminal: initctl: UPSTART_SESSION isn't set in the environment. Unable to locate the Upstart instance. 3. On the contrary, indicator-sound/indicator-sound-gtk2 work in MATE just fine. The volume icon is properly displayed in mate-indicator-applet area. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-application/+bug/1319352/+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 1337244] [NEW] compiz crashed with SIGSEGV in nux::WindowThread::ComputeQueuedLayout()
Public bug reported: Hi, this is basically the same bug as https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1298202, but that bug is marked as Fix Released with Unity 7.2.0, and I'm still seeing this bug on trusty, with the latest Unity version (unity 7.2.1+14.04.20140513-0ubuntu2). I already mentioned in that bug that I was still seeing it quite a while ago, but got no reply to that. Crashes are being experienced in multiple machines, while unlocking the screen. The stacktraces vary, but they always fail in the same function and same line. First stacktrace: #0 0x0410 in ?? () #1 0x7fd4bf4eb75d in nux::WindowThread::ComputeQueuedLayout (this=this@entry=0x22c1990) at ./WindowThread.cpp:318 #2 0x7fd4bf4ecb28 in nux::WindowThread::RenderInterfaceFromForeignCmd (this=0x22c1990, clip=...) at ./WindowThread.cpp:1627 #3 0x7fd4c0c20389 in unity::UnityScreen::paintDisplay() () from /usr/lib/compiz/libunityshell.so #4 0x7fd4c0c20748 in unity::UnityScreen::glPaintOutput(GLScreenPaintAttrib const, GLMatrix const, CompRegion const, CompOutput*, unsigned int) () from /usr/lib/compiz/libunityshell.so #5 0x7fd4d4f2e272 in GLScreen::glPaintOutput(GLScreenPaintAttrib const, GLMatrix const, CompRegion const, CompOutput*, unsigned int) () from /usr/lib/compiz/libopengl.so #6 0x7fd4d4f2eed4 in PrivateGLScreen::paintOutputs(std::listCompOutput*, std::allocatorCompOutput* , unsigned int, CompRegion const) () from /usr/lib/compiz/libopengl.so #7 0x7fd4d556944f in CompositeScreen::paint(std::listCompOutput*, std::allocatorCompOutput* , unsigned int) () from /usr/lib/compiz/libcomposite.so #8 0x7fd4d556caf2 in CompositeScreen::handlePaintTimeout() () from /usr/lib/compiz/libcomposite.so #9 0x7fd4e12c053d in CompTimer::triggerCallback() () from /usr/lib/libcompiz_core.so.ABI-20140123 #10 0x7fd4e12c05ef in CompTimeoutSource::callback() () from /usr/lib/libcompiz_core.so.ABI-20140123 #11 0x7fd4e12bfb4d in CompTimeoutSource::dispatch(sigc::slot_base*) () from /usr/lib/libcompiz_core.so.ABI-20140123 #12 0x7fd4df7ac35f in Glib::Source::dispatch_vfunc(_GSource*, int (*)(void*), void*) () from /usr/lib/x86_64-linux-gnu/libglibmm-2.4.so.1 #13 0x7fd4df29ece5 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x7fd4df29f048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x7fd4df29f30a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7fd4e127b0eb in compiz::private_screen::EventManager::startEventLoop(_XDisplay*) () from /usr/lib/libcompiz_core.so.ABI-20140123 #17 0x00401971 in main () Second stacktrace (different machine): #0 0x7f0058407ed0 in nux_area_accessible_check_pending_notification () from /usr/lib/compiz/libunityshell.so #1 0x7f0056cb175d in nux::WindowThread::ComputeQueuedLayout (this=this@entry=0x1d530e0) at ./WindowThread.cpp:318 #2 0x7f0056cb2b28 in nux::WindowThread::RenderInterfaceFromForeignCmd (this=0x1d530e0, clip=...) at ./WindowThread.cpp:1627 #3 0x7f00583e6389 in unity::UnityScreen::paintDisplay() () from /usr/lib/compiz/libunityshell.so #4 0x7f00583e6748 in unity::UnityScreen::glPaintOutput(GLScreenPaintAttrib const, GLMatrix const, CompRegion const, CompOutput*, unsigned int) () from /usr/lib/compiz/libunityshell.so #5 0x7f00705e2272 in GLScreen::glPaintOutput(GLScreenPaintAttrib const, GLMatrix const, CompRegion const, CompOutput*, unsigned int) () from /usr/lib/compiz/libopengl.so #6 0x7f00705e2ed4 in PrivateGLScreen::paintOutputs(std::listCompOutput*, std::allocatorCompOutput* , unsigned int, CompRegion const) () from /usr/lib/compiz/libopengl.so #7 0x7f0070c1d44f in CompositeScreen::paint(std::listCompOutput*, std::allocatorCompOutput* , unsigned int) () from /usr/lib/compiz/libcomposite.so #8 0x7f0070c20af2 in CompositeScreen::handlePaintTimeout() () from /usr/lib/compiz/libcomposite.so #9 0x7f007879b53d in CompTimer::triggerCallback() () from /usr/lib/libcompiz_core.so.ABI-20140123 #10 0x7f007879b5ef in CompTimeoutSource::callback() () from /usr/lib/libcompiz_core.so.ABI-20140123 #11 0x7f007879ab4d in CompTimeoutSource::dispatch(sigc::slot_base*) () from /usr/lib/libcompiz_core.so.ABI-20140123 #12 0x7f0076c8735f in Glib::Source::dispatch_vfunc(_GSource*, int (*)(void*), void*) () from /usr/lib/x86_64-linux-gnu/libglibmm-2.4.so.1 #13 0x7f0076779ce5 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x7f007677a048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x7f007677a30a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7f00787560eb in compiz::private_screen::EventManager::startEventLoop(_XDisplay*) () from /usr/lib/libcompiz_core.so.ABI-20140123 #17 0x00401971 in main () I have more, but I don't know how useful it is to add them all. All stacktraces have
[Dx-packages] [Bug 1086563] Update Released
The verification of the Stable Release Update for libdbusmenu has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1086563 Title: Adding a menu item without a label gets treated as a separator even if label is added later Status in DBus Menu: Fix Committed Status in “libdbusmenu” package in Ubuntu: Fix Released Status in “libdbusmenu” source package in Trusty: Fix Released Bug description: * Impact If you add a Gtk.MenuItem to an indicator menu without a label then appindicator treats the menu item like it is a separator (according to dbusmenu-dumper). * Test case Run this python script http://pastebin.ubuntu.com/7604811/ * Regression potential check that menus and indicators are correctly displayed To manage notifications about this bug go to: https://bugs.launchpad.net/libdbusmenu/+bug/1086563/+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 1086563] Re: Adding a menu item without a label gets treated as a separator even if label is added later
This bug was fixed in the package libdbusmenu - 12.10.3+14.04.20140612-0ubuntu1 --- libdbusmenu (12.10.3+14.04.20140612-0ubuntu1) trusty; urgency=low [ Marco Trevisan (Treviño) ] * Backporting lp:~3v1n0/libdbusmenu/really-recreate-menu/+merge/222419 (LP: #1086563) -- Ubuntu daily release ps-jenk...@lists.canonical.com Thu, 12 Jun 2014 16:36:28 + ** Changed in: libdbusmenu (Ubuntu Trusty) Status: Fix Committed = 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/1086563 Title: Adding a menu item without a label gets treated as a separator even if label is added later Status in DBus Menu: Fix Committed Status in “libdbusmenu” package in Ubuntu: Fix Released Status in “libdbusmenu” source package in Trusty: Fix Released Bug description: * Impact If you add a Gtk.MenuItem to an indicator menu without a label then appindicator treats the menu item like it is a separator (according to dbusmenu-dumper). * Test case Run this python script http://pastebin.ubuntu.com/7604811/ * Regression potential check that menus and indicators are correctly displayed To manage notifications about this bug go to: https://bugs.launchpad.net/libdbusmenu/+bug/1086563/+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 1290785] Re: Users with UID 60000 are invisible in login and Settings-User unless /etc/login.defs updated
I have attached the backported patch of the changes from the above mentioned 0.6.37-1ubuntu4 and 0.6.37-1ubuntu5 to trusty's 0.6.35-0ubuntu5 accountsservice. This needs to be put into the debian/patches/ directory and added to debian/patches/series and debian/patches/ubuntu.series I have successfully built and tested packages with this using pbuilder. btw: I think the 2003-dont-use-max_uid-from-login.defs.patch should be removed from the debian/patches/ directory in trusty, since it is not used there. @Robert: would You please build and upload an official package for trusty? ** Patch added: backport of MAX_UID and nobody patches to trusty https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1290785/+attachment/4144540/+files/2003-dont-use-max_uid-from-login.defs.patch -- 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/1290785 Title: Users with UID 6 are invisible in login and Settings-User unless /etc/login.defs updated Status in “accountsservice” package in Ubuntu: Fix Released Status in “accountsservice” source package in Trusty: Triaged Bug description: [Impact] Users of Ubuntu 14.04 LTS with UID 6 will not show in the greeter or system settings without editing UID_MAX in /etc/login.defs. This was not required in 12.04 LTS. In 12.04 LTS users were only hidden if they had UID UID_MIN. In 13.10 this was changed to UID UID_MIN or UID UID_MAX. [Test Case] 1. Create a user with a UID UID_MAX: $ adduser --uid 60001 big-uid 2. Restart system Expected result: big-uid is shown in the greeter. Once logged in big-uid is shown in system settings. Observed result: big-uid is not shown in the greeter (14.04 LTS, 14.10) big-uid is not shown in system settings (13.10, 14.04LTS, 14.10) [Regression Potential] This could cause users that were previously hidden to be shown. This seems unlikely to be a problem as all system created user accounts are less than UID_MIN and there doesn't seem be a convention to use accounts UID_MAX for this case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1290785/+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 1011233] Re: Manual use of 'notify-send' not working as it used to.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: notify-osd (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to notify-osd in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1011233 Title: Manual use of 'notify-send' not working as it used to. Status in “notify-osd” package in Ubuntu: Confirmed Bug description: Hi, i'm italian and i don't speak english very well (and i don't know if this is the right place to report this bug, because my bug is in the command notify-send) When i had a previous Ubuntu's version I could send notification using the command notify-send body message on the terminal. If body or message were too long for a line, I saw the text split in two lines. For example, if i wrote notif-send hello, how are you? I'm fine, thanks, and you? Me too. What are you doing now? i'm studying I saw; hello, how are you? I'm fine, thanks, and you? Me too. What are you doing now? i'm studying (the text was split in three lines because there wasn't enough space) But now (with Ubuntu 12.04) i see: hello, how are you? I'm fine, thanks, because it doesn't split the lines. Are there a know solution for this problem? Lucio ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: notify-osd 0.9.34-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16 Uname: Linux 3.2.0-24-generic x86_64 ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Sun Jun 10 18:35:02 2012 GtkTheme: Ambiance IconTheme: ubuntu-mono-dark InstallationMedia: Ubuntu Precise - Build amd64 LIVE Binary 20120426-22:45 MachineType: Acer Extensa 5235 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic root=UUID=496935d1-6bd3-43d8-96fc-5413b9bc347b ro quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.6+12ubuntu1 libgl1-mesa-glx 8.0.2-0ubuntu3.1 libdrm2 2.4.32-1ubuntu1 xserver-xorg-video-intel 2:2.17.0-1ubuntu4 xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 SourcePackage: notify-osd UpgradeStatus: No upgrade log present (probably fresh install) WindowManager: No value set for `/desktop/gnome/session/required_components/windowmanager' dmi.bios.date: 12/21/2009 dmi.bios.vendor: Phoenix dmi.bios.version: V1.3311 dmi.board.name: BA50-MV dmi.board.vendor: Acer dmi.board.version: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenix:bvrV1.3311:bd12/21/2009:svnAcer:pnExtensa5235:pvrNotApplicable:rvnAcer:rnBA50-MV:rvrNotApplicable:cvnAcer:ct10:cvrN/A: dmi.product.name: Extensa 5235 dmi.product.version: Not Applicable dmi.sys.vendor: Acer glxinfo: Error: [Errno 2] File o directory non esistente To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1011233/+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 1313437] Re: typing in DASH do not show the A word.
Hi, It does happen all the time and yes, it seems to be rendering issue, I tried to reinstall and now the A works without problems, BUT, it does not work with R word. Macbook Air. ** Changed in: unity (Ubuntu) Status: Expired = New ** Summary changed: - typing in DASH do not show the A word. + typing in DASH do not show the some words. ** Summary changed: - typing in DASH do not show the some words. + typing in DASH do not show some words. -- 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/1313437 Title: typing in DASH do not show some words. Status in “unity” package in Ubuntu: New Bug description: I cannot type A word in dash, other words works. Instead of A it types the space. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 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: Sun Apr 27 22:27:10 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.141+bdcom, 3.13.0-17-generic, x86_64: installed bcmwl, 6.30.223.141+bdcom, 3.13.0-20-generic, x86_64: installed bcmwl, 6.30.223.141+bdcom, 3.13.0-23-generic, x86_64: installed bcmwl, 6.30.223.141+bdcom, 3.13.0-24-generic, x86_64: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device [106b:00eb] InstallationDate: Installed on 2014-03-29 (29 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140317) MachineType: Apple Inc. MacBookAir4,2 ProcEnviron: LANGUAGE=cs_CZ PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=cs_CZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=39d50fd6-1e16-4028-9276-0f69dc2486d7 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/24/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA41.88Z.0077.B0F.1201241549 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-742912EFDBEE19B3 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir4,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-742912EFDBEE19B3 dmi.modalias: dmi:bvnAppleInc.:bvrMBA41.88Z.0077.B0F.1201241549:bd01/24/2012:svnAppleInc.:pnMacBookAir4,2:pvr1.0:rvnAppleInc.:rnMac-742912EFDBEE19B3:rvrMacBookAir4,2:cvnAppleInc.:ct10:cvrMac-742912EFDBEE19B3: dmi.product.name: MacBookAir4,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple 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-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sun Apr 27 22:24:10 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 40176 vendor APP xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1313437/+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 1262022] Re: incorrect multi-arch related meta information.
I'm also running into this on Trusty. What needs to happen to get someone to look at the bzr branches and merge request linked in this bug? ** Tags added: trusty -- 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/1262022 Title: incorrect multi-arch related meta information. Status in “overlay-scrollbar” package in Ubuntu: Triaged Bug description: I'm on a 64-bit system trying to install overlay-scrollbar-gtk2:i386 which depends on the overlay-scrollbar:i386 package. overlay- scrollbar:i386 doesn't have an install candidate because it's a multi-arch package. This should (or so I've been told) be reflected in the meta information of the overlay-scrollbar package but isn't, which is why the former package fails to install. As a more competent person than I put it: The overlay-scrollbar package does not come in i386 or amd64 flavors; it comes as an all flavor, which installs on all archs. It appears to be missing the Multi-Arch: allowed header so it won't satisfy an i386 package depending on it. You should file a bug report asking that the missing header be added. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: overlay-scrollbar 0.2.16+r359+13.10.20130826-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Wed Dec 18 02:14:35 2013 InstallationDate: Installed on 2013-12-14 (3 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True PackageArchitecture: all SourcePackage: overlay-scrollbar UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/overlay-scrollbar/+bug/1262022/+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 1304560] Re: the icon used forcalendar events doesn't work well on light themes
** Changed in: ubuntu-settings-components (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1304560 Title: the icon used forcalendar events doesn't work well on light themes Status in “indicator-datetime” package in Ubuntu: Invalid Status in “ubuntu-settings-components” package in Ubuntu: Fix Released Bug description: Using the current trusty version, the alarm-symbolic icon used for events is a symbolic/grey one, that provides little contrast on light theme colors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1304560/+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 1155166] Re: HUD keyboard shortcut always reset after an update
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/1155166 Title: HUD keyboard shortcut always reset after an update Status in “unity” package in Ubuntu: Confirmed Bug description: It's really frustrating that every time the update manager runs and applies an update, my keyboard shortcut for showing the HUD (default: Alt L) is reset to the default and I always have to set it back to something else (which I never use, like Shift+Ctrl+Alt+F12). I do this, because I have a xbindkeys mapping of Alt + Left / Alt + Right mapped to my Logitech 10 button mouse's forward/back thumb buttons. I haven't noticed any other shortcuts changing after an update. I never use the HUD and I don't really find it useful. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: unity 6.12.0-0ubuntu0.2 ProcVersionSignature: Ubuntu 3.5.0-26.42-generic 3.5.7.6 Uname: Linux 3.5.0-26-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 CompizPlugins: [core,composite,gtkloader,opengl,copytex,decor,mousepoll,imgjpeg,commands,resize,place,imgsvg,regex,session,grid,compiztoolbox,imgpng,move,gnomecompat,animation,snap,wall,expo,fade,workarounds,ezoom,scale,unityshell] Date: Thu Mar 14 15:36:14 2013 InstallationDate: Installed on 2011-11-17 (482 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MarkForUpload: True SourcePackage: unity UpgradeStatus: Upgraded to quantal on 2013-01-05 (68 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1155166/+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 1155166] Re: HUD keyboard shortcut always reset after an update
I have the same bug on Ubuntu 14.04 LTS. -- 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/1155166 Title: HUD keyboard shortcut always reset after an update Status in “unity” package in Ubuntu: Confirmed Bug description: It's really frustrating that every time the update manager runs and applies an update, my keyboard shortcut for showing the HUD (default: Alt L) is reset to the default and I always have to set it back to something else (which I never use, like Shift+Ctrl+Alt+F12). I do this, because I have a xbindkeys mapping of Alt + Left / Alt + Right mapped to my Logitech 10 button mouse's forward/back thumb buttons. I haven't noticed any other shortcuts changing after an update. I never use the HUD and I don't really find it useful. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: unity 6.12.0-0ubuntu0.2 ProcVersionSignature: Ubuntu 3.5.0-26.42-generic 3.5.7.6 Uname: Linux 3.5.0-26-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 CompizPlugins: [core,composite,gtkloader,opengl,copytex,decor,mousepoll,imgjpeg,commands,resize,place,imgsvg,regex,session,grid,compiztoolbox,imgpng,move,gnomecompat,animation,snap,wall,expo,fade,workarounds,ezoom,scale,unityshell] Date: Thu Mar 14 15:36:14 2013 InstallationDate: Installed on 2011-11-17 (482 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MarkForUpload: True SourcePackage: unity UpgradeStatus: Upgraded to quantal on 2013-01-05 (68 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1155166/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1244285] Re: Date/time sometimes doesn’t appear in menu bar, settings greyed out (Ubuntu 13.10, 14.04)
I'm having this problem on 14.04. HLP!!! -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1244285 Title: Date/time sometimes doesn’t appear in menu bar, settings greyed out (Ubuntu 13.10, 14.04) Status in One Hundred Papercuts: Triaged Status in The Date and Time Indicator: Confirmed Status in “indicator-datetime” package in Ubuntu: Confirmed Bug description: it does not happen often, and when it happens, just a log out and re- log in is enough to restore it. http://askubuntu.com/questions/357266/how-to-show-time-in- ubuntu-13-10/357280 To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1244285/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 381416] Re: notify-osd should have a close button
You guys can use the patched NotifyOSD: it's close to the default one, but with very usefull features, like click to close, time/font/color/position configurations. This article: http://www.webupd8.org/2012/11/patched-notifyosd-with-close-on- click.html Cites only until 13.10, but it works fine on 14.04, I use it. -- You received this bug notification because you are a member of DX Packages, which is subscribed to notify-osd in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/381416 Title: notify-osd should have a close button Status in “notify-osd” package in Ubuntu: Won't Fix Bug description: Binary package hint: notify-osd As simple as that. The new notification system works fine, but it really bugs me that I'm forced to wait for those little messages to fade away by themselves. Should I suggest this somewhere else? Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/381416/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1244285] Re: Date/time sometimes doesn’t appear in menu bar, settings greyed out (Ubuntu 13.10, 14.04)
Jeton, when was the last time you updated the system? this is a new installation or an upgrade from 13.10? -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1244285 Title: Date/time sometimes doesn’t appear in menu bar, settings greyed out (Ubuntu 13.10, 14.04) Status in One Hundred Papercuts: Triaged Status in The Date and Time Indicator: Confirmed Status in “indicator-datetime” package in Ubuntu: Confirmed Bug description: it does not happen often, and when it happens, just a log out and re- log in is enough to restore it. http://askubuntu.com/questions/357266/how-to-show-time-in- ubuntu-13-10/357280 To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1244285/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1337601] Re: touchpad gesture reveals open windows in the lock screen
*** This bug is a duplicate of bug 1321043 *** https://bugs.launchpad.net/bugs/1321043 ** Information type changed from Private Security to Public Security ** Changed in: unity (Ubuntu) Status: New = Confirmed ** This bug has been marked a duplicate of bug 1321043 [regression] lock screen bypass with touchpad -- 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/1337601 Title: touchpad gesture reveals open windows in the lock screen Status in “unity” package in Ubuntu: Confirmed Bug description: Performing a double 3-finger tap touchpad gesture opens the window switcher, even if the screen is locked. If more than one window is open for any application, a live thumbnail preview is displayed, revealing user's activity. Ubuntu 14.04 unity 7.2.1+14.04.20140513-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1337601/+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 1319191] Re: middle-click in window's top bar does not send-to-back
William, thanks for the excellent description. I too get the unity-provided window bar after selecting use system titlebars and borders AND moving the window around. Just leaving it in place does not draw the unity system titlebars and borders. Perhaps this should also be assigned to unity. The right thing happens, eventually, but the process is clunky. Thanks ** Also affects: unity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1319191 Title: middle-click in window's top bar does not send-to-back Status in “chromium-browser” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: New Bug description: In Unity, middle-clicking the title bars of other windows sends those windows to the bottom of the stack, making it very easy to expose the windows underneath. Chromium-browser, however, does not respect this convention. To reproduce this issue, start another program or two, such as urxvt or firefox, and chromium-browser. Drag all the windows to e.g. the right side of the screen to have them occupy the right half of the screen. Middle click the chromium-browser title bar and notice how nothing happens. Raise one of the other windows using the Unity dock, middle-click the title bar, and notice how the window is sent to the bottom of the stack. If the stack does not contain chromium-browser, it is possible to cycle through all windows this way. If the stack does contain chromium-browser, the cycle is broken with chromium-browser. I expect chromium-browser to behave identical to the other programs I run and move to the bottom of the stack. Thanks ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: chromium-browser 34.0.1847.116-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Tue May 13 14:19:04 2014 Desktop-Session: DESKTOP_SESSION = ubuntu XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg XDG_DATA_DIRS = /usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/ Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationDate: Installed on 2012-10-18 (572 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) SourcePackage: chromium-browser UpgradeStatus: Upgraded to trusty on 2014-04-12 (31 days ago) chromium-default: CHROMIUM_FLAGS= gconf-keys: /desktop/gnome/applications/browser/exec = b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n' modified.conffile..etc.default.chromium.browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1319191/+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 1311316] Re: After locking screen there is no input field to type password for unlock
I am also having this issue. Dual monitor setup, nvidia card. I've also noticed that it seems to happen pretty often if my screen locks when I have a chrome PDF-viewer window open on one or both of my screens. -- 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/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: New Status in “unity” package in Ubuntu: Confirmed Bug description: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+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 1296114] Re: Bluetooth is always enabled after reboot even if it was disabled
I'm suffering from tis bug too, I do not use bluetooth on laptop, why this is so difficult to remember this? -- 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/1296114 Title: Bluetooth is always enabled after reboot even if it was disabled Status in Bluetooth Menu: New Status in “indicator-bluetooth” package in Ubuntu: Triaged Bug description: If bluetooth was disabled using the switcher in the bluetooth indicator, after reboot it becomes enabled. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-bluetooth 0.0.6+14.04.20140207-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 22 22:34:52 2014 InstallationDate: Installed on 2014-01-27 (54 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140124) SourcePackage: indicator-bluetooth UpgradeStatus: No upgrade log present (probably fresh install) upstart.indicator-bluetooth.log: (bluetooth-wizard:2251): Gtk-DEBUG: Connecting to session manager To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-bluetooth/+bug/1296114/+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 1337693] Re: compiz crashed with SIGSEGV in sigc::internal::trackable_callback_list::remove_callback()
*** This bug is a duplicate of bug 936462 *** https://bugs.launchpad.net/bugs/936462 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 #936462, 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/1337693/+attachment/4145255/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1337693/+attachment/4145257/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1337693/+attachment/4145259/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1337693/+attachment/4145260/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1337693/+attachment/4145261/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1337693/+attachment/4145262/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1337693/+attachment/4145263/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 936462 ** 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 unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1337693 Title: compiz crashed with SIGSEGV in sigc::internal::trackable_callback_list::remove_callback() Status in “unity” package in Ubuntu: New Bug description: temporary froze my system after closing Chrome dev and then compiz crashed ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: unity 7.3.0+14.10.20140619-0ubuntu1 ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0 Uname: Linux 3.15.0-6-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jul 4 07:15:16 2014 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2014-05-14 (51 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) ProcCmdline: compiz SegvAnalysis: Segfault happened at: 0x7ff21b9b5798 _ZN4sigc8internal23trackable_callback_list15remove_callbackEPv+24:cmp %rsi,0x10(%rbx) PC (0x7ff21b9b5798) ok source %rsi ok destination 0x10(%rbx) (0x00b7) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: sigc::internal::trackable_callback_list::remove_callback(void*) () from /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 sigc::internal::typed_slot_repsigc::bound_mem_functor0void, unity::decoration::Item ::destroy(void*) () from /usr/lib/compiz/libunityshell.so sigc::slot_base::~slot_base() () from /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 std::_List_basesigc::slot_base, std::allocatorsigc::slot_base ::_M_clear() () from /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 sigc::signal_base::~signal_base() () from /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 Title: compiz crashed with SIGSEGV in sigc::internal::trackable_callback_list::remove_callback() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1337693/+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 1337620] [NEW] Application indicator icon only changes after mouse click
You have been subscribed to a public bug: I have an application indicator which shows the moon phase/orientation as its icon (along with a text label). When the indicator does an update (several times per hour), the icon is recreated (as an SVG file) and so the icon changes over time. Recently, the icon is not showing any change unless I mouse click the icon (or label). I'm on Ubuntu 14.04 64 bit and my indicator uses Python 3 and Appindicator3. I have attached a sample script which is representative of the issue and shows an icon which should change every three seconds. The icon itself is an SVG file and shows a numerical count, starting from zero and increments every three seconds. I have tested on Ubuntu 12.04 and Xubuntu 12.04 (via VirtualBox) and the icon DOES change on each three second update. Testing on Ubuntu 14.04, the icon does NOT change UNLESS I click on it. If I change the label text on each update, the icon WILL also change, but only if I don't repeat the SAME text for the label. FYI: I initially asked this at http://askubuntu.com/questions/490634 /application-indicator-icon-not-changing-until-clicked but have had no response. Thanks in advance, Bernmeister. ** Affects: libappindicator (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: bot-comment trusty -- Application indicator icon only changes after mouse click https://bugs.launchpad.net/bugs/1337620 You received this bug notification because you are a member of DX Packages, which is subscribed to libappindicator 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 1337620] Re: Application indicator icon only changes after mouse click
Had to choose a package - not sure if this is the most appropriate but it's a start! ** Package changed: ubuntu = libappindicator (Ubuntu) -- You received this bug notification because you are a member of DX Packages, which is subscribed to libappindicator in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1337620 Title: Application indicator icon only changes after mouse click Status in “libappindicator” package in Ubuntu: Confirmed Bug description: I have an application indicator which shows the moon phase/orientation as its icon (along with a text label). When the indicator does an update (several times per hour), the icon is recreated (as an SVG file) and so the icon changes over time. Recently, the icon is not showing any change unless I mouse click the icon (or label). I'm on Ubuntu 14.04 64 bit and my indicator uses Python 3 and Appindicator3. I have attached a sample script which is representative of the issue and shows an icon which should change every three seconds. The icon itself is an SVG file and shows a numerical count, starting from zero and increments every three seconds. I have tested on Ubuntu 12.04 and Xubuntu 12.04 (via VirtualBox) and the icon DOES change on each three second update. Testing on Ubuntu 14.04, the icon does NOT change UNLESS I click on it. If I change the label text on each update, the icon WILL also change, but only if I don't repeat the SAME text for the label. FYI: I initially asked this at http://askubuntu.com/questions/490634 /application-indicator-icon-not-changing-until-clicked but have had no response. Thanks in advance, Bernmeister. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libappindicator/+bug/1337620/+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
