[Dx-packages] [Bug 848115] Re: Active windows lose focus to desktop randomly and when show desktop command is run even when they're still active
I found post about same behaviour (Unity windows in background) in Ubuntu 12.10: http://askubuntu.com/questions/209518/unity-and-dash- displayed-under-all-active-windows In my case unity --replace (temporarily?) fixed problem. -- 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/848115 Title: Active windows lose focus to desktop randomly and when show desktop command is run even when they're still active Status in Unity: Expired Status in “unity” package in Ubuntu: Expired Bug description: Active windows randomly lose focus to desktop though they are on top and active. This renders them frozen and unusable. Focus returns after some time automatically. This happens with show desktop command too. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: unity 4.14.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-11.17-generic 3.0.4 Uname: Linux 3.0.0-11-generic i686 NonfreeKernelModules: nvidia ApportVersion: 1.22.1-0ubuntu2 Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,resize,fade,unitymtgrabhandles,scale,session,unityshell] Date: Mon Sep 12 23:10:54 2011 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta i386 (20110901) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/848115/+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 1229171] Re: switch fcitx to input chinese failed in dash
In UbuntuKylin13.10, still couldn't input chinese in dash by switching the fcitx. -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1229171 Title: switch fcitx to input chinese failed in dash Status in Nux: New Status in Ubuntu Kylin: Confirmed Status in “nux” package in Ubuntu: Fix Released Bug description: switch to chinese failed when want to input chinese， other place all well To manage notifications about this bug go to: https://bugs.launchpad.net/nux/+bug/1229171/+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 1198653] Re: It is not possible to drag drop and pin icon to launch bar when auto-hiding is turned on
I have found that you answer is correct, I have ubuntu 13.04 on my gateway, I turned off the auto hide then I was able to drag-and-drop icons onto it. Thanks for that info. -- 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/1198653 Title: It is not possible to drag drop and pin icon to launch bar when auto-hiding is turned on Status in “unity” package in Ubuntu: New Bug description: When you have auto-hiding of launch bar turned on, you can not drag an application from search, because when you just put mouse with icon over the bar, it hides all the time and if you want to add it though, you have to disable auto-hiding first. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2 Uname: Linux 3.8.0-26-generic i686 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sun Jul 7 13:23:45 2013 InstallationDate: Installed on 2013-06-20 (16 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424) MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1198653/+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 1235649] Re: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch
** Changed in: upstart Assignee: (unassigned) = James Hunt (jamesodhunt) ** Changed in: upstart Status: New = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1235649 Title: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch Status in Upstart: Fix Committed Status in “linux” package in Ubuntu: Invalid Status in “systemd” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: Confirmed Status in “upstart” package in Ubuntu: In Progress Status in “linux” source package in Saucy: Invalid Status in “systemd” source package in Saucy: Invalid Status in “unity” source package in Saucy: Confirmed Status in “upstart” source package in Saucy: Fix Released Bug description: using ubuntu touch image 82 i see the session init consume about 10MB per minute as long as the screen is on with Mir. running the same session with surfaceflinger only consumes 1MB per minute. in both cases the system starts to swap heavily at some point, making the UI unresponsive. http://paste.ubuntu.com/6196223/ has the top output of a Mir session after 30min, the UI just got completely unresponsive when this snapshot was taken. http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger session where the screen was off for about 10min apparently the leak only occurs while the screen is on, it seems to be permanently there but in the case of surfaceflinger it hits less hard. To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1235649/+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 1250447] [NEW] Crash of HUD -- while trying to send a bug report from Terminal
Public bug reported: I had a bug with linux-image on 13.10. After reseting the computer and loading the system again, I tried to send a bug report via terminal. While process was taking place, it just didn't finish and got stuck. When I forced closed it, I got the error report regarding package HUD. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: hud 13.10.1+13.10.20131014-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic i686 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 Date: Tue Nov 12 14:34:57 2013 InstallationDate: Installed on 2012-12-17 (329 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012) MarkForUpload: True SourcePackage: hud UpgradeStatus: Upgraded to saucy on 2013-10-26 (16 days ago) upstart.window-stack-bridge.log: QDBusConnection: name 'org.ayatana.bamf' had owner '' but we thought it was ':1.17' Could not get window property _GTK_WINDOW_OBJECT_PATH /org/ayatana/bamf/window/4194312 Could not get window property _UNITY_OBJECT_PATH /org/ayatana/bamf/window/4194312 Could not get window property WM_NAME /org/ayatana/bamf/window/10485763 ** Affects: hud (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 saucy -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1250447 Title: Crash of HUD -- while trying to send a bug report from Terminal Status in “hud” package in Ubuntu: New Bug description: I had a bug with linux-image on 13.10. After reseting the computer and loading the system again, I tried to send a bug report via terminal. While process was taking place, it just didn't finish and got stuck. When I forced closed it, I got the error report regarding package HUD. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: hud 13.10.1+13.10.20131014-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic i686 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 Date: Tue Nov 12 14:34:57 2013 InstallationDate: Installed on 2012-12-17 (329 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012) MarkForUpload: True SourcePackage: hud UpgradeStatus: Upgraded to saucy on 2013-10-26 (16 days ago) upstart.window-stack-bridge.log: QDBusConnection: name 'org.ayatana.bamf' had owner '' but we thought it was ':1.17' Could not get window property _GTK_WINDOW_OBJECT_PATH /org/ayatana/bamf/window/4194312 Could not get window property _UNITY_OBJECT_PATH /org/ayatana/bamf/window/4194312 Could not get window property WM_NAME /org/ayatana/bamf/window/10485763 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1250447/+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 1239381] Re: Unity crashes when entering a term including emu in the home lens
Luc: I can confirm the crash with 'wri' on Saucy, but not on Trusty. The backtrace on saucy looks similar to me to this bug. -- 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/1239381 Title: Unity crashes when entering a term including emu in the home lens Status in Unity: Fix Committed Status in Unity 7.0 series: In Progress Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Saucy: Confirmed Bug description: Unity version 7.1.2. on Ubuntu 13.10 daily build 2013-10-13 To reproduce: -Make sure an Internet connection is working -Start the Unity Dash, in the home lens -Enter a term including emu -Unity crashes ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.2+13.10.20131011-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 319.60 Wed Sep 25 14:28:26 PDT 2013 GCC version: gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu8) .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Oct 13 17:50:58 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: nvidia-319-updates, 319.60, 3.11.0-12-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CardExpert Technology Device [10b0:11c0] InstallationDate: Installed on 2013-10-13 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20131013) JockeyStatus: kmod:nvidia_319_updates - nvidia_319_updates (Proprietär, Aktiviert, Nicht benutzt) kmod:nvidia_304 - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietär, Deaktiviert, Nicht benutzt) kmod:nvidia_304_updates - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietär, Deaktiviert, Nicht benutzt) kmod:nvidia_319 - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietär, Deaktiviert, Nicht benutzt) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=c1338261-d55c-4a44-87e4-cb7a961b0a27 ro quiet splash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/03/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.20 dmi.board.name: Z87 Pro3 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.20:bd07/03/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ87Pro3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental 9.2.1-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Sun Oct 13 17:29:03 2013 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB Gaming Mouse MOUSE, id 8 inputChicony Saitek Eclipse II Keyboard KEYBOARD, id 9 inputChicony Saitek Eclipse II Keyboard KEYBOARD, id 10 xserver.errors: Failed to load /usr/lib/xorg/modules/libglamoregl.so: /usr/lib/xorg/modules/libglamoregl.so: undefined symbol: _glapi_tls_Context Failed to load module glamoregl (loader failed, 7) open /dev/fb0: No such file or directory
[Dx-packages] [Bug 1228360] Re: No clock in menu bar and can't edit Clock settings
** Also affects: indicator-datetime Importance: Undecided Status: New ** Changed in: indicator-datetime (Ubuntu) Status: Confirmed = Triaged ** Changed in: indicator-datetime Status: New = Confirmed ** Changed in: indicator-datetime (Ubuntu) Importance: Undecided = High ** Also affects: hundredpapercuts Importance: Undecided Status: New ** Changed in: hundredpapercuts Importance: Undecided = High ** Changed in: hundredpapercuts Status: New = Triaged -- 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/1228360 Title: No clock in menu bar and can't edit Clock settings Status in One Hundred Papercuts: Triaged Status in The Date and Time Indicator: Confirmed Status in “indicator-datetime” package in Ubuntu: Triaged Bug description: The latest update broke the clock in several ways: * No clock shows up in the menu bar. * Open Time Date settings. You cannot edit anything in the Clock tab. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu38 ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1 Uname: Linux 3.11.0-7-generic x86_64 ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 Date: Fri Sep 20 15:51:55 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2011-07-12 (800 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha amd64 (20110705.1) MarkForUpload: True SourcePackage: gnome-control-center SystemImageInfo: Error: [Errno 2] No such file or directory: 'system-image-cli' UpgradeStatus: Upgraded to saucy on 2011-12-23 (637 days ago) usr_lib_gnome-control-center: deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20130913-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3daily13.06.14.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1228360/+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 1234458] Re: Indicator stuck on mouse icon, along with estimating...
** Changed in: indicator-power (Ubuntu) Status: Confirmed = Triaged ** Changed in: indicator-power (Ubuntu) Importance: Undecided = Low ** Also affects: hundredpapercuts Importance: Undecided Status: New ** Changed in: hundredpapercuts Status: New = Triaged ** Changed in: hundredpapercuts Importance: Undecided = Low -- 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/1234458 Title: Indicator stuck on mouse icon, along with estimating... Status in One Hundred Papercuts: Triaged Status in The Power Indicator: Triaged Status in “indicator-power” package in Ubuntu: Triaged Bug description: indicator-power 12.10.6+13.10.20130918.2-0ubuntu1, Ubuntu 13.10 My power indicator is stuck on the mouse icon. When I click on it, it says Mouse (estimating). Why is it stuck on estimating? Why show the icon at all if I'm using a Logitech mouse with a battery? https://wiki.ubuntu.com/Power#time-presentation: The brief time-remaining string for a component should be: * the time remaining for it to empty or fully charge, if estimable, in H:MM format; otherwise * 'estimating…' if the time remaining has been inestimable for less than 30 seconds; otherwise * 'unknown' if the time remaining has been inestimable for between 30 seconds and one minute; otherwise * the empty string. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1234458/+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 1234624] Re: Spread - In the spread view, clicking on an empty space should perform the same action as pressing the ESC key
** Branch linked: lp:~andyrock/compiz/fix-1234624 -- 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/1234624 Title: Spread - In the spread view, clicking on an empty space should perform the same action as pressing the ESC key Status in Ayatana Design: Fix Committed Status in Compiz: In Progress Status in Unity: Invalid Status in “compiz” package in Ubuntu: In Progress Status in “unity” package in Ubuntu: Invalid Bug description: In the spread view, clicking on an empty space (e.g. anywhere that is not a window or the launcher) should perform the same action as pressing the ESC key and should exit the spread. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1234624/+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 1247882] Re: /usr/lib/unity/unity-panel-service:11:menu_hidden:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist:g_signal_emit
https://launchpad.net/ubuntu/+source/ido/13.10.0+14.04.20131106-0ubuntu1 ** Changed in: ido (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to ido in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1247882 Title: /usr/lib/unity/unity-panel- service:11:menu_hidden:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist:g_signal_emit Status in “ido” package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity. This problem was most recently seen with version 13.01.0+13.10.20130930-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/970ecbed32838f7c29c40f27dfc56177dfba8ddd contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ido/+bug/1247882/+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 1218810] Re: video switch hot key will return super key and p and no response to switch video mode
** Changed in: linux (Ubuntu)
Status: Incomplete = 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/1218810
Title:
video switch hot key will return super key and p and no response to
switch video mode
Status in “linux” package in Ubuntu:
Confirmed
Status in “unity” package in Ubuntu:
New
Bug description:
CID 201209-11735
For some machines, for example, HP laptop HP 1000 has a hot key on F4 to
perform the shorcut super + p to switch video modes.
Use command sudo showkey -k to capture the key code of the hot key you will
see the key code of super key and p
This key combination is expected to change the video mode.
platfrom: HP laptop HP 1000
image: 12.04.3
Steps to reproduce:
1. open an terminal,
2. plugin an external monitor
3. press the video switch hotkey, for HP 1000 it is the F4 key
Expected result:
1. Video mode is changed by the hotkey
2. no character is printed on terminal
Actual result
1. Video mode is not changed.
2. a p will be printed on the terminal screen
The other information:
1. A similar bug was reported on LP:#539477 before.
2. The hotkey in 13.04 works
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.8.0-29-generic 3.8.0-29.42~precise1 [modified:
boot/vmlinuz-3.8.0-29-generic]
ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5
Uname: Linux 3.8.0-29-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.4
Architecture: amd64
Date: Fri Aug 30 17:34:56 2013
InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release amd64
(20130820.1)
MarkForUpload: True
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: linux-lts-raring
UpgradeStatus: No upgrade log present (probably fresh install)
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k3.8.0-29-generic.
ApportVersion: 2.0.1-0ubuntu17.4
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC269VC Analog [ALC269VC Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 1675 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0x6360 irq 47'
Mixer name : 'Intel PantherPoint HDMI'
Components : 'HDA:10ec0269,103c1855,00100202
HDA:80862806,80860101,0010'
Controls : 27
Simple ctrls : 10
CurrentDmesg:
[ 45.884915] ISO 9660 Extensions: RRIP_1991A
[ 60.442781] audit_printk_skb: 3 callbacks suppressed
[ 60.442785] type=1400 audit(1378093422.964:31): apparmor=DENIED
operation=open parent=1 profile=/usr/lib/telepathy/mission-control-5
name=/usr/share/gvfs/remote-volume-monitors/ pid=1849 comm=mission-control
requested_mask=r denied_mask=r fsuid=1000 ouid=0
[ 65.385488] r8169 :0e:00.0 eth0: link up
[ 65.385510] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=932733cb-db60-4153-8565-3e3ccb1a6f6d
InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release amd64
(20130820.1)
Lsusb:
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 003: ID 05c8:0223 Cheng Uei Precision Industry Co., Ltd
(Foxlink)
MachineType: Hewlett-Packard HP 1000 Notebook PC
MarkForUpload: True
Package: linux (not installed)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
0 radeondrmfb
1 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic
root=UUID=770667e1-92a4-4f2e-a434-b9998d55cb30 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5
RelatedPackageVersions:
linux-restricted-modules-3.8.0-29-generic N/A
linux-backports-modules-3.8.0-29-generic N/A
linux-firmware1.79.6
Tags: precise running-unity
Uname: Linux 3.8.0-29-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 12/25/2012
dmi.bios.vendor: Insyde
dmi.bios.version: B.50
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 1855
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 64.22
dmi.chassis.asset.tag: Classis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias:
[Dx-packages] [Bug 1237725] Re: indicator-session-service crashed with SIGSEGV in g_strdup()
*** This bug is a duplicate of bug 1201659 *** https://bugs.launchpad.net/bugs/1201659 ** This bug is no longer a duplicate of bug 1230021 Gnome-Panel crashed after attempting to add a weather location on the clock applet ** This bug has been marked a duplicate of bug 1201659 gnome-panel crashed with SIGSEGV in gweather_location_equal() -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-session in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1237725 Title: indicator-session-service crashed with SIGSEGV in g_strdup() Status in “indicator-session” package in Ubuntu: New Bug description: Logged in, got this error report ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: indicator-session 12.10.5+13.10.20131004-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.18-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Thu Oct 10 00:41:14 2013 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-session/indicator-session-service InstallationDate: Installed on 2013-10-09 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20131008) MarkForUpload: True ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-session/indicator-session-service ProcEnviron: SHELL=/bin/false XDG_RUNTIME_DIR=set PATH=(custom, no user) LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SegvAnalysis: Segfault happened at: 0x7f69353835f1 __strlen_sse2_pminub+17: movdqu (%rdi),%xmm1 PC (0x7f69353835f1) ok source (%rdi) (0x0001) not located in a known VMA region (needed readable region)! destination %xmm1 ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: indicator-session StacktraceTop: g_strdup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 g_cclosure_marshal_generic () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: indicator-session-service crashed with SIGSEGV in g_strdup() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1237725/+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 1230021] Re: Gnome-Panel crashed after attempting to add a weather location on the clock applet
*** This bug is a duplicate of bug 1201659 *** https://bugs.launchpad.net/bugs/1201659 ** This bug has been marked a duplicate of bug 1201659 gnome-panel crashed with SIGSEGV in gweather_location_equal() -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-session in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1230021 Title: Gnome-Panel crashed after attempting to add a weather location on the clock applet Status in “gnome-panel” package in Ubuntu: Confirmed Status in “indicator-session” package in Ubuntu: Confirmed Bug description: Apport says indicator-session caused the crash, but potential other packages involved include gnome-panel and gnome-applets. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: indicator-session 12.10.5+13.10.20130823-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 Uname: Linux 3.11.0-8-generic x86_64 ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 Date: Tue Sep 24 21:42:45 2013 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-session/indicator-session-service InstallationDate: Installed on 2012-09-13 (376 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) MarkForUpload: True ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-session/indicator-session-service ProcEnviron: SHELL=/bin/false XDG_RUNTIME_DIR=set PATH=(custom, no user) LANG=en_US.utf8 SegvAnalysis: Segfault happened at: 0x7feefcd78c7f __strlen_sse42+15:pcmpeqb (%rdi),%xmm1 PC (0x7feefcd78c7f) ok source (%rdi) (0x) not located in a known VMA region (needed readable region)! destination %xmm1 ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: indicator-session StacktraceTop: g_strdup (str=0x1 Address 0x1 out of bounds) at /build/buildd/glib2.0-2.37.93/./glib/gstrfuncs.c:363 schedule_call_in_idle (call_type=CALL_TYPE_NAME_VANISHED, client=0x24dfd70) at /build/buildd/glib2.0-2.37.93/./gio/gdbusnamewatching.c:193 do_call (client=0x24dfd70, call_type=CALL_TYPE_NAME_VANISHED) at /build/buildd/glib2.0-2.37.93/./gio/gdbusnamewatching.c:214 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 Title: indicator-session-service crashed with SIGSEGV in g_strdup() UpgradeStatus: Upgraded to saucy on 2012-09-14 (376 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1230021/+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 1193360] Re: Can't type diacritics with AltGr+letter in Dash or HUD
I'm having this issue with ru+ruu layout both in tty sessions and X11 (any app, WM is i3). -- 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/1193360 Title: Can't type diacritics with AltGr+letter in Dash or HUD Status in One Hundred Papercuts: Confirmed Status in “unity” package in Ubuntu: Triaged Bug description: In the default polish keyboard layout, diacritics are written using AltGr (right Alt) + letter, i.e. AltGr+l gives ł. This is now broken in unity, Compose key still works, though. To test, english layout has ł under AltGr+w. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.0.0daily13.06.19-0ubuntu1 ProcVersionSignature: Ubuntu 3.9.0-6.14-generic 3.9.6 Uname: Linux 3.9.0-6-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.10.2-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Fri Jun 21 14:55:27 2013 MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1193360/+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 1250262] Re: Selecting power-cog restart lands highlight on shutdown
** Also affects: unity (Ubuntu) Importance: Undecided Status: New ** Changed in: unity Status: New = Triaged ** Changed in: unity (Ubuntu) Status: New = Confirmed ** Changed in: unity Importance: Undecided = Medium ** Changed in: unity Milestone: None = 7.2.0 -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1250262 Title: Selecting power-cog restart lands highlight on shutdown Status in Unity: Triaged Status in “unity” package in Ubuntu: Confirmed Bug description: Ubuntu 13.10. Selecting the power-cog restart should result in the popup highlighting/pre-selecting Restart so users only have to hit Enter. Presently users who select Restart from the power-cog menu have to then use the cursor keys to actually select Restart else a shutdown will occur. It makes no sense to put Restart in the power-cog menu only to have the popup that appears highlight Shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1250262/+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 1250262] Re: Selecting power-cog restart lands highlight on shutdown
No restart menu item should ever shown in the power indicator menu. So, unity is not wrong here. ** Also affects: indicator-session 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/1250262 Title: Selecting power-cog restart lands highlight on shutdown Status in The Session Menu: New Status in Unity: Triaged Status in “unity” package in Ubuntu: Confirmed Bug description: Ubuntu 13.10. Selecting the power-cog restart should result in the popup highlighting/pre-selecting Restart so users only have to hit Enter. Presently users who select Restart from the power-cog menu have to then use the cursor keys to actually select Restart else a shutdown will occur. It makes no sense to put Restart in the power-cog menu only to have the popup that appears highlight Shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/1250262/+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 1250262] Re: Selecting power-cog restart lands highlight on shutdown
** Changed in: unity Status: In Progress = Triaged ** Changed in: unity (Ubuntu) Status: In Progress = Confirmed ** Changed in: unity Assignee: Andrea Azzarone (andyrock) = (unassigned) ** Changed in: unity (Ubuntu) Assignee: Andrea Azzarone (andyrock) = (unassigned) -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1250262 Title: Selecting power-cog restart lands highlight on shutdown Status in The Session Menu: New Status in Unity: Triaged Status in “unity” package in Ubuntu: Confirmed Bug description: Ubuntu 13.10. Selecting the power-cog restart should result in the popup highlighting/pre-selecting Restart so users only have to hit Enter. Presently users who select Restart from the power-cog menu have to then use the cursor keys to actually select Restart else a shutdown will occur. It makes no sense to put Restart in the power-cog menu only to have the popup that appears highlight Shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/1250262/+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 1250134] Re: RemoteContent field should be mandatory in .scope file
setting the default to true would be just as good if making a mandatory field is challenging - that also wouldn't break any existing scopes that don't declare a value for it. They would just only be used if online searching was enabled, if they don't specify that they are safe for local only mode then we should assume they do some online stuff. -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1250134 Title: RemoteContent field should be mandatory in .scope file Status in LibUnity: New Status in “libunity” package in Ubuntu: Confirmed Bug description: If a .scope file has no RemoteContent field, the default is to assume false. The RemoteContent field should be mandatory, to ensure that scope authors aren't ignoring the privacy setting by mistake. To manage notifications about this bug go to: https://bugs.launchpad.net/libunity/+bug/1250134/+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 1208204] Re: indicator-sound no longer functions with xfce4-indicator-plugin
The workaround in #5 worked for me, too. Thanks! -- 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/1208204 Title: indicator-sound no longer functions with xfce4-indicator-plugin Status in Sound Menu: New Status in Ubuntu Studio: New Status in “indicator-sound” package in Ubuntu: Triaged Bug description: *** Problems with the default Bluetooth indicator on Xfce are caused by a different, unrelated bug. See https://bugs.launchpad.net/ubuntu/+source/glipper/+bug/1203888 *** downgrading to the previous version, indicator- sound_12.10.2daily13.04.12-0ubuntu1_amd64 from Raring allows the sound indicator to function in Saucy. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-sound 12.10.2+13.10.20130731-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic x86_64 ApportVersion: 2.12-0ubuntu2 Architecture: amd64 Date: Sun Aug 4 12:20:02 2013 InstallationDate: Installed on 2012-08-01 (367 days ago) InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120801) MarkForUpload: True SourcePackage: indicator-sound UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-sound/+bug/1208204/+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 1199877] Update Released
The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1199877 Title: unity-panel-service memory leak and 100% CPU usage Status in The Application Menu: Fix Committed Status in Application Menu Indicator 13.10 series: Fix Committed Status in The Ubuntu Power Consumption Project: New Status in Unity: Invalid Status in “gtk+3.0” package in Ubuntu: Fix Released Status in “indicator-appmenu” package in Ubuntu: In Progress Status in “unity” package in Ubuntu: Invalid Status in “gtk+3.0” source package in Saucy: Fix Committed Status in “indicator-appmenu” source package in Saucy: Fix Released Bug description: Impact: high CPU/memory usage from unity-panel-service Test case: Open a large image in the GIMP and activate a lot of items from the global menu. Using shortcuts is enough and faster to reproduce this bug (I've always used Ctrl+A and Ctrl+Shift+A). Memory usage of unity- panel-service increases steadily and it uses a lot of CPU shortly after activating the menu items in a short time. Regression potential: check that the menus are stable/working as they should - Just going about my business on Ubuntu Raring amd64 on an x230 and I heard the fan kick into action. top showed me that unity-panel-service was consuming all the free cycles on one of my CPUs. I killed it before my machine overheated, so I didn't attach a debugger to see why it was totally pegging out a CPU. I'm not sure if this adds any context, but I was using a LibreOffice spreadsheet and I could not insert a table because the menu had lost it's mind, and then I observed the overly loaded CPU a very short while after that. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-appmenu/+bug/1199877/+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 1199877] Re: unity-panel-service memory leak and 100% CPU usage
This bug was fixed in the package indicator-appmenu - 13.01.0+13.10.20131031-0ubuntu1 --- indicator-appmenu (13.01.0+13.10.20131031-0ubuntu1) saucy; urgency=low [ Lars Uebernickel ] * Call gtk_widget_destroy() to break potential ref cycles (lp: #1199877). (LP: #1199877) [ Ubuntu daily release ] * Automatic snapshot from revision 247 -- Ubuntu daily release ps-jenk...@lists.canonical.com Thu, 31 Oct 2013 19:31:17 + ** Changed in: indicator-appmenu (Ubuntu Saucy) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1199877 Title: unity-panel-service memory leak and 100% CPU usage Status in The Application Menu: Fix Committed Status in Application Menu Indicator 13.10 series: Fix Committed Status in The Ubuntu Power Consumption Project: New Status in Unity: Invalid Status in “gtk+3.0” package in Ubuntu: Fix Released Status in “indicator-appmenu” package in Ubuntu: In Progress Status in “unity” package in Ubuntu: Invalid Status in “gtk+3.0” source package in Saucy: Fix Committed Status in “indicator-appmenu” source package in Saucy: Fix Released Bug description: Impact: high CPU/memory usage from unity-panel-service Test case: Open a large image in the GIMP and activate a lot of items from the global menu. Using shortcuts is enough and faster to reproduce this bug (I've always used Ctrl+A and Ctrl+Shift+A). Memory usage of unity- panel-service increases steadily and it uses a lot of CPU shortly after activating the menu items in a short time. Regression potential: check that the menus are stable/working as they should - Just going about my business on Ubuntu Raring amd64 on an x230 and I heard the fan kick into action. top showed me that unity-panel-service was consuming all the free cycles on one of my CPUs. I killed it before my machine overheated, so I didn't attach a debugger to see why it was totally pegging out a CPU. I'm not sure if this adds any context, but I was using a LibreOffice spreadsheet and I could not insert a table because the menu had lost it's mind, and then I observed the overly loaded CPU a very short while after that. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-appmenu/+bug/1199877/+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 1246536] Re: segfault in menu_hidden()
testing (and errors.ubuntu.com) seems to confirm the fix is working ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of DX Packages, which is subscribed to ido in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1246536 Title: segfault in menu_hidden() Status in Sound Menu: Fix Committed Status in “ido” package in Ubuntu: Fix Released Status in “ido” source package in Saucy: Fix Committed Bug description: Impact: indicator-sound is segfaulting the unity-panel-service sometimes Test Case: - install the current GTK version from saucy-proposed - use the indicator-sound slider and the play multimedia key to start/stop rhythmbox - the indicator should be stable Regression potential: try desktop indicators and make sure they keep working --- Using saucy stable, happened a few times today while using the slider, muting/unmuting, using play multimedia key/mpris to start/stop rhythmbox #0 menu_hidden (menu=0x96882c0, scale=0x97b8110) at idoscalemenuitem.c:640 #1 0xb6e454d3 in g_cclosure_marshal_VOID__VOID (closure=0x97b5818, return_value=0x0, n_param_values=1, param_values=0xbff2e970, invocation_hint=0xbff2e91c, marshal_data=0x0) at /build/buildd/glib2.0-2.38.1/./gobject/gmarshal.c:85 #2 0xb6e438ae in g_closure_invoke (closure=0x97b5818, return_value=return_value@entry=0x0, n_param_values=1, param_values=param_values@entry=0xbff2e970, invocation_hint=invocation_hint@entry=0xbff2e91c) at /build/buildd/glib2.0-2.38.1/./gobject/gclosure.c:777 #3 0xb6e55df9 in signal_emit_unlocked_R (node=node@entry=0x9562ec8, detail=0, instance=0x96882c0, emission_return=emission_return@entry=0x0, instance_and_params=0xbff2e970) at /build/buildd/glib2.0-2.38.1/./gobject/gsignal.c:3586 #4 0xb6e5d753 in g_signal_emit_valist (instance=instance@entry=0x96882c0, signal_id=signal_id@entry=5, detail=detail@entry=0, var_args=var_args@entry=0xbff2eaac h\027;\267) at /build/buildd/glib2.0-2.38.1/./gobject/gsignal.c:3330 #5 0xb6e5d9e3 in g_signal_emit (instance=instance@entry=0x96882c0, signal_id=5, detail=detail@entry=0) at /build/buildd/glib2.0-2.38.1/./gobject/gsignal.c:3386 #6 0xb73b1820 in gtk_widget_hide (widget=widget@entry=0x96882c0) at /tmp/gtk+3/build-area/gtk+3.0-3.8.6/./gtk/gtkwidget.c:4268 #7 0xb7278678 in gtk_menu_popdown (menu=menu@entry=0x96882c0) at /tmp/gtk+3/build-area/gtk+3.0-3.8.6/./gtk/gtkmenu.c:1848 #8 0xb727877d in gtk_menu_deactivate (menu_shell=0x96882c0) at /tmp/gtk+3/build-area/gtk+3.0-3.8.6/./gtk/gtkmenu.c:4546 #9 0xb6e454d3 in g_cclosure_marshal_VOID__VOID (closure=0x956c640, return_value=0x0, n_param_values=1, param_values=0xbff2ec90, invocation_hint=0xbff2ec3c, marshal_data=0xb7278700 gtk_menu_deactivate) at /build/buildd/glib2.0-2.38.1/./gobject/gmarshal.c:85 #10 0xb6e423d4 in g_type_class_meta_marshal (closure=0x956c640, return_value=0x0, n_param_values=1, param_values=0xbff2ec90, invocation_hint=0xbff2ec3c, marshal_data=0x1ec) at /build/buildd/glib2.0-2.38.1/./gobject/gclosure.c:970 #11 0xb6e438ae in g_closure_invoke (closure=closure@entry=0x956c640, return_value=return_value@entry=0x0, n_param_values=1, param_values=param_values@entry=0xbff2ec90, invocation_hint=invocation_hint@entry=0xbff2ec3c) at /build/buildd/glib2.0-2.38.1/./gobject/gclosure.c:777 #12 0xb6e5549c in signal_emit_unlocked_R (node=node@entry=0x956d3b8, detail=0, instance=0x96882c0, emission_return=emission_return@entry=0x0, instance_and_params=0xbff2ec90) at /build/buildd/glib2.0-2.38.1/./gobject/gsignal.c:3516 #13 0xb6e5d753 in g_signal_emit_valist (instance=instance@entry=0x96882c0, signal_id=signal_id@entry=82, detail=detail@entry=0, var_args=var_args@entry=0xbff2edcc ) at /build/buildd/glib2.0-2.38.1/./gobject/gsignal.c:3330 #14 0xb6e5d9e3 in g_signal_emit (instance=instance@entry=0x96882c0, signal_id=82, detail=detail@entry=0) at /build/buildd/glib2.0-2.38.1/./gobject/gsignal.c:3386 #15 0xb7282923 in gtk_menu_shell_deactivate (menu_shell=0x96882c0) at /tmp/gtk+3/build-area/gtk+3.0-3.8.6/./gtk/gtkmenushell.c:616 #16 0xb7283202 in gtk_menu_shell_activate_item ( menu_shell=menu_shell@entry=0x96882c0, menu_item=menu_item@entry=0x962a0b8, force_deactivate=force_deactivate@entry=1) at /tmp/gtk+3/build-area/gtk+3.0-3.8.6/./gtk/gtkmenushell.c:1433 #17 0xb7283626 in gtk_menu_shell_button_release (widget=0x96882c0, event=0x9648650) at /tmp/gtk+3/build-area/gtk+3.0-3.8.6/./gtk/gtkmenushell.c:842 #18 0xb7276ce9 in gtk_menu_button_release (widget=0x96882c0, event=0x9648650) at /tmp/gtk+3/build-area/gtk+3.0-3.8.6/./gtk/gtkmenu.c:3391 #19 0xb7267ee6 in _gtk_marshal_BOOLEAN__BOXEDv
[Dx-packages] [Bug 1244688] Re: /usr/lib/i386-linux-gnu/hud/hud-service:5:name_lost_cb:actually_do_call:do_call:ffi_call_SYSV:ffi_call
looking to errors report it seems the fix is working, setting as verification-done ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1244688 Title: /usr/lib/i386-linux-gnu/hud/hud- service:5:name_lost_cb:actually_do_call:do_call:ffi_call_SYSV:ffi_call Status in “hud” package in Ubuntu: Fix Released Status in “hud” source package in Saucy: Fix Committed Bug description: SRU for saucy. [Impact] A reported crash in certain situations. [Test Case] A crasher, no clear test case. Ensure errors.ubuntu.com stops reporting this. [Regression Potential] Low, doing graceful exiting instead of abort. The Ubuntu Error Tracker has been receiving reports about a problem regarding hud. This problem was most recently seen with version 13.10.1+13.10.20131014-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/23bafefb567e15de49e41a1fda7e468768652425 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1244688/+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 1179210] Re: unity_low_gfx_mode + auto hide launcher causes visual artifacts
** Also affects: unity/7.1 Importance: Undecided Status: New ** Changed in: unity/7.1 Status: New = In Progress ** Changed in: unity/7.1 Importance: Undecided = Medium ** Changed in: unity/7.1 Assignee: (unassigned) = Christopher Townsend (townsend) ** Changed in: unity/7.1 Milestone: None = 7.1.3 -- 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/1179210 Title: unity_low_gfx_mode + auto hide launcher causes visual artifacts Status in Unity: In Progress Status in Unity 7.1 series: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: If you enable low gfx mode and auto hide launcher an ugly rectangle is drawn on top of the desktop along the left screen border, where the hidden launcher would have been. Take a look at the attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8 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 Date: Sun May 12 15:16:18 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu GraphicsCard: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Device [144d:c08c] Subsystem: Samsung Electronics Co Ltd Device [144d:c08c] InstallationDate: Installed on 2013-05-11 (1 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: SAMSUNG ELECTRONICS CO., LTD. NF110/NF210/NF310 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=sv_SE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=a402d2be-1682-4d17-9229-f152a96a19e0 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/08/2011 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 04MY.M033.20110308.JIP dmi.board.asset.tag: SAMSUNG dmi.board.name: NF110/NF210/NF310 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr04MY.M033.20110308.JIP:bd03/08/2011:svnSAMSUNGELECTRONICSCO.,LTD.:pnNF110/NF210/NF310:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNF110/NF210/NF310:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.name: NF110/NF210/NF310 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.43-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 xserver.bootTime: Sun May 12 15:11:20 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.3-0ubuntu6 xserver.video_driver: intel To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1179210/+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 1244688] Re: /usr/lib/i386-linux-gnu/hud/hud-service:5:name_lost_cb:actually_do_call:do_call:ffi_call_SYSV:ffi_call
This bug was fixed in the package hud - 13.10.1+13.10.20131031-0ubuntu1 --- hud (13.10.1+13.10.20131031-0ubuntu1) saucy; urgency=low [ Charles Kerr ] * If we can't get the busname, log a g_critical and then exit gracefully instead of abort()ing in g_error. (LP: #1244688) * Add a null safeguard when accessing window SharedPtrs held in the m_windows QMap. (LP: #1243654) [ Ubuntu daily release ] * Automatic snapshot from revision 344 -- Ubuntu daily release ps-jenk...@lists.canonical.com Thu, 31 Oct 2013 23:12:19 + ** Changed in: hud (Ubuntu Saucy) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1244688 Title: /usr/lib/i386-linux-gnu/hud/hud- service:5:name_lost_cb:actually_do_call:do_call:ffi_call_SYSV:ffi_call Status in “hud” package in Ubuntu: Fix Released Status in “hud” source package in Saucy: Fix Released Bug description: SRU for saucy. [Impact] A reported crash in certain situations. [Test Case] A crasher, no clear test case. Ensure errors.ubuntu.com stops reporting this. [Regression Potential] Low, doing graceful exiting instead of abort. The Ubuntu Error Tracker has been receiving reports about a problem regarding hud. This problem was most recently seen with version 13.10.1+13.10.20131014-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/23bafefb567e15de49e41a1fda7e468768652425 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1244688/+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 1246536] Re: segfault in menu_hidden()
This bug was fixed in the package ido - 13.10.0+13.10.20131031-0ubuntu1 --- ido (13.10.0+13.10.20131031-0ubuntu1) saucy; urgency=low [ Lars Uebernickel ] * idoscalemenuitem: disconnect signal from parent This fixes a crash: the widget installed a handler for the parent's hide signal, but was destroyed before the parent without disconnecting the signal. (LP: #1246536) [ Ubuntu daily release ] * Automatic snapshot from revision 154 -- Ubuntu daily release ps-jenk...@lists.canonical.com Thu, 31 Oct 2013 21:39:29 + ** Changed in: ido (Ubuntu Saucy) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to ido in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1246536 Title: segfault in menu_hidden() Status in Sound Menu: Fix Committed Status in “ido” package in Ubuntu: Fix Released Status in “ido” source package in Saucy: Fix Released Bug description: Impact: indicator-sound is segfaulting the unity-panel-service sometimes Test Case: - install the current GTK version from saucy-proposed - use the indicator-sound slider and the play multimedia key to start/stop rhythmbox - the indicator should be stable Regression potential: try desktop indicators and make sure they keep working --- Using saucy stable, happened a few times today while using the slider, muting/unmuting, using play multimedia key/mpris to start/stop rhythmbox #0 menu_hidden (menu=0x96882c0, scale=0x97b8110) at idoscalemenuitem.c:640 #1 0xb6e454d3 in g_cclosure_marshal_VOID__VOID (closure=0x97b5818, return_value=0x0, n_param_values=1, param_values=0xbff2e970, invocation_hint=0xbff2e91c, marshal_data=0x0) at /build/buildd/glib2.0-2.38.1/./gobject/gmarshal.c:85 #2 0xb6e438ae in g_closure_invoke (closure=0x97b5818, return_value=return_value@entry=0x0, n_param_values=1, param_values=param_values@entry=0xbff2e970, invocation_hint=invocation_hint@entry=0xbff2e91c) at /build/buildd/glib2.0-2.38.1/./gobject/gclosure.c:777 #3 0xb6e55df9 in signal_emit_unlocked_R (node=node@entry=0x9562ec8, detail=0, instance=0x96882c0, emission_return=emission_return@entry=0x0, instance_and_params=0xbff2e970) at /build/buildd/glib2.0-2.38.1/./gobject/gsignal.c:3586 #4 0xb6e5d753 in g_signal_emit_valist (instance=instance@entry=0x96882c0, signal_id=signal_id@entry=5, detail=detail@entry=0, var_args=var_args@entry=0xbff2eaac h\027;\267) at /build/buildd/glib2.0-2.38.1/./gobject/gsignal.c:3330 #5 0xb6e5d9e3 in g_signal_emit (instance=instance@entry=0x96882c0, signal_id=5, detail=detail@entry=0) at /build/buildd/glib2.0-2.38.1/./gobject/gsignal.c:3386 #6 0xb73b1820 in gtk_widget_hide (widget=widget@entry=0x96882c0) at /tmp/gtk+3/build-area/gtk+3.0-3.8.6/./gtk/gtkwidget.c:4268 #7 0xb7278678 in gtk_menu_popdown (menu=menu@entry=0x96882c0) at /tmp/gtk+3/build-area/gtk+3.0-3.8.6/./gtk/gtkmenu.c:1848 #8 0xb727877d in gtk_menu_deactivate (menu_shell=0x96882c0) at /tmp/gtk+3/build-area/gtk+3.0-3.8.6/./gtk/gtkmenu.c:4546 #9 0xb6e454d3 in g_cclosure_marshal_VOID__VOID (closure=0x956c640, return_value=0x0, n_param_values=1, param_values=0xbff2ec90, invocation_hint=0xbff2ec3c, marshal_data=0xb7278700 gtk_menu_deactivate) at /build/buildd/glib2.0-2.38.1/./gobject/gmarshal.c:85 #10 0xb6e423d4 in g_type_class_meta_marshal (closure=0x956c640, return_value=0x0, n_param_values=1, param_values=0xbff2ec90, invocation_hint=0xbff2ec3c, marshal_data=0x1ec) at /build/buildd/glib2.0-2.38.1/./gobject/gclosure.c:970 #11 0xb6e438ae in g_closure_invoke (closure=closure@entry=0x956c640, return_value=return_value@entry=0x0, n_param_values=1, param_values=param_values@entry=0xbff2ec90, invocation_hint=invocation_hint@entry=0xbff2ec3c) at /build/buildd/glib2.0-2.38.1/./gobject/gclosure.c:777 #12 0xb6e5549c in signal_emit_unlocked_R (node=node@entry=0x956d3b8, detail=0, instance=0x96882c0, emission_return=emission_return@entry=0x0, instance_and_params=0xbff2ec90) at /build/buildd/glib2.0-2.38.1/./gobject/gsignal.c:3516 #13 0xb6e5d753 in g_signal_emit_valist (instance=instance@entry=0x96882c0, signal_id=signal_id@entry=82, detail=detail@entry=0, var_args=var_args@entry=0xbff2edcc ) at /build/buildd/glib2.0-2.38.1/./gobject/gsignal.c:3330 #14 0xb6e5d9e3 in g_signal_emit (instance=instance@entry=0x96882c0, signal_id=82, detail=detail@entry=0) at /build/buildd/glib2.0-2.38.1/./gobject/gsignal.c:3386 #15 0xb7282923 in gtk_menu_shell_deactivate (menu_shell=0x96882c0) at /tmp/gtk+3/build-area/gtk+3.0-3.8.6/./gtk/gtkmenushell.c:616 #16 0xb7283202 in gtk_menu_shell_activate_item ( menu_shell=menu_shell@entry=0x96882c0,
[Dx-packages] [Bug 1197788] Re: indicator-application-service crashed with signal 5 in g_type_create_instance()
Hello denissius, or anyone else affected, Accepted indicator-application into saucy-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source /indicator-application/12.10.1+13.10.20131107-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: indicator-application (Ubuntu Saucy) Status: Triaged = Fix Committed ** Tags added: verification-needed -- 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/1197788 Title: indicator-application-service crashed with signal 5 in g_type_create_instance() Status in Application Indicators: Fix Committed Status in “indicator-application” package in Ubuntu: Fix Committed Status in “indicator-application” source package in Saucy: Fix Committed Bug description: [Impact] Any users who starts indicator-application with an inaccessible dbus session bus. [Test case] Try to start indicator-application-service as a different user than the user currently connected (i.e. sudo -u toto /usr/lib/*/indicator-application-service ) Observe that it does not crash and rather stops gracefully. [Regression potential] The service could fail to successfully start even when the bus should be available, in which case it should normally get respawned automatically. --- indicator-application-service crashed with signal 5 in g_type_create_instance() ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: indicator-application 12.10.1daily13.01.25-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-25.17-lowlatency 3.8.13 Uname: Linux 3.8.0-25-lowlatency i686 ApportVersion: 2.10.2-0ubuntu3 Architecture: i386 Date: Thu Jul 4 16:16:42 2013 ExecutablePath: /usr/lib/i386-linux-gnu/indicator-application-service MarkForUpload: True ProcCmdline: /usr/lib/i386-linux-gnu/indicator-application-service Signal: 5 SourcePackage: indicator-application StacktraceTop: ?? () g_type_create_instance () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 g_object_newv () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 g_object_new () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 Title: indicator-application-service crashed with signal 5 in g_type_create_instance() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev scanner video To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-application/+bug/1197788/+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 1245473] Re: Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes shortcuts with ctrl+shift, etc not working in any program
I don't see any focus change. Hotkeys just doesnt work. Not only hotkeys, ctrl+shift+arrow keys doesn't work too. -- 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/1245473 Title: Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes shortcuts with ctrl+shift, etc not working in any program Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: Tried only with ctrl+shift, maybe behaves the same for other modifier key combinations when used as shortcut for switching layouts. - Set ctrl+shift as shortcut for switching keyboard layouts - Try to use ctrl+shift+v, ctrl+shift+c in Terminal -- it doesn't work (actually Terminal window loses focus when ctrl+shift is pressed, and layout is switched) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-settings-daemon 3.8.5-0ubuntu11.1 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Mon Oct 28 16:40:02 2013 InstallationDate: Installed on 2013-10-23 (5 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1245473/+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 1197788] Re: indicator-application-service crashed with signal 5 in g_type_create_instance()
** Branch linked: lp:ubuntu/saucy-proposed/indicator-application -- 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/1197788 Title: indicator-application-service crashed with signal 5 in g_type_create_instance() Status in Application Indicators: Fix Committed Status in “indicator-application” package in Ubuntu: Fix Committed Status in “indicator-application” source package in Saucy: Fix Committed Bug description: [Impact] Any users who starts indicator-application with an inaccessible dbus session bus. [Test case] Try to start indicator-application-service as a different user than the user currently connected (i.e. sudo -u toto /usr/lib/*/indicator-application-service ) Observe that it does not crash and rather stops gracefully. [Regression potential] The service could fail to successfully start even when the bus should be available, in which case it should normally get respawned automatically. --- indicator-application-service crashed with signal 5 in g_type_create_instance() ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: indicator-application 12.10.1daily13.01.25-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-25.17-lowlatency 3.8.13 Uname: Linux 3.8.0-25-lowlatency i686 ApportVersion: 2.10.2-0ubuntu3 Architecture: i386 Date: Thu Jul 4 16:16:42 2013 ExecutablePath: /usr/lib/i386-linux-gnu/indicator-application-service MarkForUpload: True ProcCmdline: /usr/lib/i386-linux-gnu/indicator-application-service Signal: 5 SourcePackage: indicator-application StacktraceTop: ?? () g_type_create_instance () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 g_object_newv () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 g_object_new () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 Title: indicator-application-service crashed with signal 5 in g_type_create_instance() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev scanner video To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-application/+bug/1197788/+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 1245473] Re: Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes shortcuts with ctrl+shift, etc not working in any program
It's probably related to fix released for bug #1218322 -- 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/1245473 Title: Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes shortcuts with ctrl+shift, etc not working in any program Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: Tried only with ctrl+shift, maybe behaves the same for other modifier key combinations when used as shortcut for switching layouts. - Set ctrl+shift as shortcut for switching keyboard layouts - Try to use ctrl+shift+v, ctrl+shift+c in Terminal -- it doesn't work (actually Terminal window loses focus when ctrl+shift is pressed, and layout is switched) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-settings-daemon 3.8.5-0ubuntu11.1 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Mon Oct 28 16:40:02 2013 InstallationDate: Installed on 2013-10-23 (5 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1245473/+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 1199877] Re: unity-panel-service memory leak and 100% CPU usage
This bug was fixed in the package gtk+3.0 - 3.8.6-0ubuntu2 --- gtk+3.0 (3.8.6-0ubuntu2) saucy; urgency=low * Backport fixes from git * debian/patches/git_frame_disconnect.patch debian/patches/git_frame_update.patch: - This fixes high wake-up count from any application using GtkTreeView, even idle ones. * debian/patches/git_submenus_leak.patch: - don't leak submenus, thanks Lars Uebernickel (lp: #1199877) gtk+3.0 (3.8.6-0ubuntu1) saucy; urgency=low * New upstream version * debian/patches/git_padding_value.patch: - drop, the fix is the new version * debian/patches/git_list_handlers.patch: gtk was made, during the 3.8 cycle, to ignore the mimetype handlers with NoDisplay=true. The change turned out to be wrong and got reverted in 3.10, doing the same here. It makes, e.g shotwell to be listed again (lp: #1238149) -- Sebastien Bacher seb...@ubuntu.com Mon, 28 Oct 2013 10:50:18 -0700 ** Changed in: gtk+3.0 (Ubuntu Saucy) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1199877 Title: unity-panel-service memory leak and 100% CPU usage Status in The Application Menu: Fix Committed Status in Application Menu Indicator 13.10 series: Fix Committed Status in The Ubuntu Power Consumption Project: New Status in Unity: Invalid Status in “gtk+3.0” package in Ubuntu: Fix Released Status in “indicator-appmenu” package in Ubuntu: In Progress Status in “unity” package in Ubuntu: Invalid Status in “gtk+3.0” source package in Saucy: Fix Released Status in “indicator-appmenu” source package in Saucy: Fix Released Bug description: Impact: high CPU/memory usage from unity-panel-service Test case: Open a large image in the GIMP and activate a lot of items from the global menu. Using shortcuts is enough and faster to reproduce this bug (I've always used Ctrl+A and Ctrl+Shift+A). Memory usage of unity- panel-service increases steadily and it uses a lot of CPU shortly after activating the menu items in a short time. Regression potential: check that the menus are stable/working as they should - Just going about my business on Ubuntu Raring amd64 on an x230 and I heard the fan kick into action. top showed me that unity-panel-service was consuming all the free cycles on one of my CPUs. I killed it before my machine overheated, so I didn't attach a debugger to see why it was totally pegging out a CPU. I'm not sure if this adds any context, but I was using a LibreOffice spreadsheet and I could not insert a table because the menu had lost it's mind, and then I observed the overly loaded CPU a very short while after that. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-appmenu/+bug/1199877/+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 1245473] Re: Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes shortcuts with ctrl+shift, etc not working in any program
** Tags added: keyboard-layout-switching-related ** Tags removed: keyboard-layout-switching-related ** Tags added: keyboard-layout-switching-hotkeys -- 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/1245473 Title: Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes shortcuts with ctrl+shift, etc not working in any program Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: Tried only with ctrl+shift, maybe behaves the same for other modifier key combinations when used as shortcut for switching layouts. - Set ctrl+shift as shortcut for switching keyboard layouts - Try to use ctrl+shift+v, ctrl+shift+c in Terminal -- it doesn't work (actually Terminal window loses focus when ctrl+shift is pressed, and layout is switched) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-settings-daemon 3.8.5-0ubuntu11.1 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Mon Oct 28 16:40:02 2013 InstallationDate: Installed on 2013-10-23 (5 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1245473/+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 1250632] [NEW] Date and time indicator option Add an event doesn't work.
Public bug reported: When I clicking Add an event it does nothing... ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-datetime 13.10.0+13.10.20131023.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Tue Nov 12 23:11:32 2013 InstallationDate: Installed on 2013-11-10 (2 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: indicator-datetime UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- 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/1250632 Title: Date and time indicator option Add an event doesn't work. Status in “indicator-datetime” package in Ubuntu: New Bug description: When I clicking Add an event it does nothing... ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-datetime 13.10.0+13.10.20131023.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Tue Nov 12 23:11:32 2013 InstallationDate: Installed on 2013-11-10 (2 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: indicator-datetime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1250632/+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 1228360] Re: No clock in menu bar and can't edit Clock settings
Affects me as well. Brand new 13.10 install on a new partition. Got all the other icons, no clock, can't edit clock settings. System has only been up about a week, have installed various things, not sure if I ever had a clock. Time keeps on slipping, slipping, slipping... into the future. -- 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/1228360 Title: No clock in menu bar and can't edit Clock settings Status in One Hundred Papercuts: Triaged Status in The Date and Time Indicator: Confirmed Status in “indicator-datetime” package in Ubuntu: Triaged Bug description: The latest update broke the clock in several ways: * No clock shows up in the menu bar. * Open Time Date settings. You cannot edit anything in the Clock tab. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu38 ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1 Uname: Linux 3.11.0-7-generic x86_64 ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 Date: Fri Sep 20 15:51:55 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2011-07-12 (800 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha amd64 (20110705.1) MarkForUpload: True SourcePackage: gnome-control-center SystemImageInfo: Error: [Errno 2] No such file or directory: 'system-image-cli' UpgradeStatus: Upgraded to saucy on 2011-12-23 (637 days ago) usr_lib_gnome-control-center: deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20130913-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3daily13.06.14.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1228360/+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 1232726] Re: Dash bg color doesn't match its surroundings
I gave Trusty a spin, and the bug is fixed. I guess it's a matter of time before the fix hits Saucy :) -- 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/1232726 Title: Dash bg color doesn't match its surroundings Status in Unity: Fix Committed Status in Unity 7.1 series: In Progress Status in “mesa” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Saucy: In Progress Bug description: Lately, after login the Dash keeps a black background even if the Launcher and panel follow the current wallpaper color. I've added a screenshot. If I change the wallpaper, Dash recovers its chameleonic effect (until next reboot). Also, this started happening at the same time that a new error message (at log time) appeared, I've attached this error message, too. Description: Ubuntu Saucy Salamander (development branch) Release: 13.10 unity: Installed: 7.1.1+13.10.20130927.1-0ubuntu1 Candidate: 7.1.1+13.10.20130927.1-0ubuntu1 Version table: *** 7.1.1+13.10.20130927.1-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ saucy/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.1+13.10.20130927.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2 Uname: Linux 3.11.0-9-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu1 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Sep 29 08:00:07 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:30a2] Subsystem: Hewlett-Packard Company Device [103c:30a2] InstallationDate: Installed on 2013-08-31 (28 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130830) MachineType: Hewlett-Packard HP Compaq nx7400 (GF451LA#ABM) MarkForUpload: True PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-9-generic root=UUID=cab2c6d5-2bf8-4db8-ba85-daaf28b1afec ro quiet splash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2006 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68YGU Ver. F.0A dmi.board.name: 30A2 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 40.17 dmi.chassis.asset.tag: CNU7111JLR dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68YGUVer.F.0A:bd12/18/2006:svnHewlett-Packard:pnHPCompaqnx7400(GF451LA#ABM):pvrF.0A:rvnHewlett-Packard:rn30A2:rvrKBCVersion40.17:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP Compaq nx7400 (GF451LA#ABM) dmi.product.version: F.0A dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.10+13.10.20130927.1-0ubuntu1 version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu9 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Sun Sep 29 07:53:46 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: OutputTV-0 VGA-0 xserver.version: 2:1.14.2.901-2ubuntu6 xserver.video_driver: intel To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1232726/+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 1228360] Re: No clock in menu bar and can't edit Clock settings
Upon shutdown and restart, I have the clock back. Tried running apps I had previously been using, to see if I could reproduce the problem. Those were: Firefox, a terminal, Phoronix opendwarfs benchmark, Synaptic Package Manager, and System Settings. So my problem is transitory. If it occurs again I'll report what I can about it. -- 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/1228360 Title: No clock in menu bar and can't edit Clock settings Status in One Hundred Papercuts: Triaged Status in The Date and Time Indicator: Confirmed Status in “indicator-datetime” package in Ubuntu: Triaged Bug description: The latest update broke the clock in several ways: * No clock shows up in the menu bar. * Open Time Date settings. You cannot edit anything in the Clock tab. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu38 ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1 Uname: Linux 3.11.0-7-generic x86_64 ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 Date: Fri Sep 20 15:51:55 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2011-07-12 (800 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha amd64 (20110705.1) MarkForUpload: True SourcePackage: gnome-control-center SystemImageInfo: Error: [Errno 2] No such file or directory: 'system-image-cli' UpgradeStatus: Upgraded to saucy on 2011-12-23 (637 days ago) usr_lib_gnome-control-center: deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20130913-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3daily13.06.14.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1228360/+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 1203888] Re: appindicator ignores menu entries after having sent the menu to the indicator
Hello Jeremy, or anyone else affected, Accepted into saucy-proposed. The package will build now and be available in a few hours in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: libdbusmenu (Ubuntu Saucy) Status: In Progress = Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of DX Packages, which is subscribed to libdbusmenu in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1203888 Title: appindicator ignores menu entries after having sent the menu to the indicator Status in Glipper: Invalid Status in DBus Menu: Fix Committed Status in “libdbusmenu” package in Ubuntu: Fix Committed Status in “libdbusmenu” source package in Saucy: Fix Committed Bug description: Impact: some indicator menus are incomplete Test Case: see comment #8 Regression potential: Check that your menus still work correctly, the change is only impacting gtk2 and renaming from a signal that was dropped to an existant one, it shouldn't create any issue --- On Saucy, the glipper appindicator shows but none of its menu items show up when left or right-clicking on it. $ glipper SHARED_DATA_DIR: /usr/share/glipper Binding shortcut CtrlAltc to popup glipper Changed process name to: glipper /usr/lib/python2.7/dist-packages/glipper/AppIndicator.py:43: Warning: /build/buildd/glib2.0-2.37.3/./gobject/gsignal.c:2475: signal 'child-added' is invalid for instance '0x20c90f0' of type 'GtkMenu' self._app_indicator.set_menu(self.menu) (glipper:20249): LIBDBUSMENU-GLIB-WARNING **: About to Show called on an item wihtout submenus. We're ignoring it. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: glipper 2.4-3 ProcVersionSignature: Ubuntu 3.10.0-4.13-generic 3.10.1 Uname: Linux 3.10.0-4-generic x86_64 ApportVersion: 2.11-0ubuntu1 Architecture: amd64 Date: Mon Jul 22 18:17:16 2013 InstallationDate: Installed on 2013-06-14 (38 days ago) InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Alpha amd64 (20130613) MarkForUpload: True PackageArchitecture: all SourcePackage: glipper UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/glipper/+bug/1203888/+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 842768] Re: Cups notifies printer ' xxx ' may be not connected although printer is OK and printing is OK too
** Branch linked: lp:~ubuntu-desktop/gnome-settings-daemon/unity -- 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/842768 Title: Cups notifies printer ' xxx ' may be not connected although printer is OK and printing is OK too Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Status in “indicator-printers” package in Ubuntu: Fix Released Status in “system-config-printer” package in Ubuntu: Invalid Status in “gnome-settings-daemon” source package in Oneiric: Confirmed Status in “indicator-printers” source package in Oneiric: Fix Released Status in “system-config-printer” source package in Oneiric: Invalid Status in “gnome-settings-daemon” source package in Precise: Confirmed Status in “indicator-printers” source package in Precise: Fix Released Status in “system-config-printer” source package in Precise: Invalid Bug description: My printer :USB HP deskjet 460c well installed when I launch any printing job ( from all apps included printing test page by printer menu in system/logout right menu ) , system notifies me that my printer may be not connected .. but all works . ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: cups 1.5.0-5 ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4 Uname: Linux 3.0.0-10-generic x86_64 Architecture: amd64 CupsErrorLog: W [06/Sep/2011:07:56:14 +0200] failed to AddProfile: org.freedesktop.ColorManager.Failed:profile object path '/org/freedesktop/ColorManager/profiles/Deskjet_460_RGB__' has already been added E [06/Sep/2011:07:56:14 +0200] Failed to update TXT record for HP Deskjet 460 @ pierreolivier-Desktop: -2 Date: Tue Sep 6 16:32:30 2011 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha amd64 (20110808) Lpstat: device for Deskjet-460: hp:/usb/Deskjet_460?serial=MY64P4Z38M MachineType: System manufacturer System Product Name Papersize: a4 PpdFiles: Deskjet-460: HP Deskjet 460, hpcups 3.11.7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-10-generic root=UUID=b2f3b035-88c2-450b-919e-0b65be858730 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/10/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0220 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5QPL-VM EPU dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0220:bd04/10/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QPL-VMEPU:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/842768/+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
All, Unity 7.0.0 resolved this specific bug so if you are still experiencing it, it probably has a different cause. Please file a separate bug report with `ubuntu-bug unity` or assume it is bug 925260 as Marcello suggested. -- 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: Confirmed Status in Unity 6.0 series: Confirmed Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Precise: Confirmed Status in “unity” 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 1203888] Re: appindicator ignores menu entries after having sent the menu to the indicator
Commit Log for Tue Nov 12 18:26:58 2013 Upgraded the following packages: gir1.2-dbusmenu-glib-0.4 (12.10.3+13.10.20130913-0ubuntu2) to 12.10.3+13.10.20131104-0ubuntu1 gir1.2-dbusmenu-gtk-0.4 (12.10.3+13.10.20130913-0ubuntu2) to 12.10.3+13.10.20131104-0ubuntu1 libdbusmenu-glib4 (12.10.3+13.10.20130913-0ubuntu2) to 12.10.3+13.10.20131104-0ubuntu1 libdbusmenu-gtk3-4 (12.10.3+13.10.20130913-0ubuntu2) to 12.10.3+13.10.20131104-0ubuntu1 libdbusmenu-gtk4 (12.10.3+13.10.20130913-0ubuntu2) to 12.10.3+13.10.20131104-0ubuntu1 My issue was resolved by this proposed package. Thank you! -- 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/1203888 Title: appindicator ignores menu entries after having sent the menu to the indicator Status in Glipper: Invalid Status in DBus Menu: Fix Committed Status in “libdbusmenu” package in Ubuntu: Fix Committed Status in “libdbusmenu” source package in Saucy: Fix Committed Bug description: Impact: some indicator menus are incomplete Test Case: see comment #8 Regression potential: Check that your menus still work correctly, the change is only impacting gtk2 and renaming from a signal that was dropped to an existant one, it shouldn't create any issue --- On Saucy, the glipper appindicator shows but none of its menu items show up when left or right-clicking on it. $ glipper SHARED_DATA_DIR: /usr/share/glipper Binding shortcut CtrlAltc to popup glipper Changed process name to: glipper /usr/lib/python2.7/dist-packages/glipper/AppIndicator.py:43: Warning: /build/buildd/glib2.0-2.37.3/./gobject/gsignal.c:2475: signal 'child-added' is invalid for instance '0x20c90f0' of type 'GtkMenu' self._app_indicator.set_menu(self.menu) (glipper:20249): LIBDBUSMENU-GLIB-WARNING **: About to Show called on an item wihtout submenus. We're ignoring it. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: glipper 2.4-3 ProcVersionSignature: Ubuntu 3.10.0-4.13-generic 3.10.1 Uname: Linux 3.10.0-4-generic x86_64 ApportVersion: 2.11-0ubuntu1 Architecture: amd64 Date: Mon Jul 22 18:17:16 2013 InstallationDate: Installed on 2013-06-14 (38 days ago) InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Alpha amd64 (20130613) MarkForUpload: True PackageArchitecture: all SourcePackage: glipper UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/glipper/+bug/1203888/+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
