[Dx-packages] [Bug 936840] Re: ctrl key now known as primary which breaks keyboard shortcuts
Still being stored as Primary in my Ubuntu/xfce4 14.04 system. Seriously, what motivated some software engineer to rename ctrl as Primary? What problem did this solve that couldn't be solved some other way? This is what should be done now: Track down all software that writes Primary to any config file and change it to write ctrl (or ctrl_L or ctrl_R if you need). Also make sure that all the software understands Primary and converts it to ctrl when it reads a config file. Nonsense like this is why Linux is having so much trouble being adopted for the general desktop. Every single damn release breaks things. I can't stand upgrading because I know I need to fix fifty things when I do. -- You received this bug notification because you are a member of DX Packages, which is subscribed to libcompizconfig in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/936840 Title: ctrl key now known as primary which breaks keyboard shortcuts Status in Compiz: Fix Released Status in Compiz 0.9.8 series: Won't Fix Status in Compiz Configuration Library: Fix Committed Status in Unity Distro Priority: Fix Committed Status in compiz package in Ubuntu: Fix Released Status in libcompizconfig package in Ubuntu: Confirmed Bug description: Previously we used to call the control key Control but this has now been changed in GNOME so when the control key is pressed primary is returned. In compiz we set keyboard shortcuts as (for example) ControlAltLeft. When changing settings in gnome-control-center (for example) we will set primary but in compiz we're looking for control which breaks keyboard actions. This also affects CCSM for setting keyboard shortcuts. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: compiz-core 1:0.9.7.0~bzr2995-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-16.25-generic 3.2.6 Uname: Linux 3.2.0-16-generic x86_64 .tmp.unity.scope.cities: Error: [Errno 21] Is a directory: '/tmp/unity-scope-cities' .tmp.unity.support.test.0: ApportVersion: 1.91-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,resize,fade,unitymtgrabhandles,scale,session,unityshell] CompositorRunning: compiz Date: Mon Feb 20 09:19:51 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu DkmsStatus: virtualbox, 4.1.8, 3.2.0-15-generic, x86_64: installed virtualbox, 4.1.8, 3.2.0-16-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21da] InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120203) MachineType: LENOVO 4287CTO ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-16-generic root=UUID=86ea7114-6b69-4161-b91c-44ccb7fcfd67 ro quiet splash vt.handoff=7 SourcePackage: compiz UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET56WW (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 4287CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET56WW(1.26):bd12/01/2011:svnLENOVO:pn4287CTO:pvrThinkPadX220:rvnLENOVO:rn4287CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4287CTO dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.7.0~bzr2995-0ubuntu4 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.30-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0~rc2-0ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0~rc2-0ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.99.901+git20120126-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/936840/+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 969223] Re: Alt+F2 dialog reports 'There is nothing that matches ...'
Sometimes the search can find files and folders but not applications. Sometimes the search begins to work a little bit later. I have never had it find photos. -- 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/969223 Title: Alt+F2 dialog reports 'There is nothing that matches ...' Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: The Alt+F2 dialog reports a message Sorry, there is nothing that matches your search before I have even typed a word. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/969223/+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 1286580] Re: unity-panel-service crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED()
I have continued to get this crash, periodically. I think the circumstance that triggers it is, generally at least: 1. opening the app menus in the panel via keyboard shortcuts, then 2. hitting left-arrow to wrap around and access the indicator menus Doing the above does not reproduce the crash every time. I have not seen it happen, I think, when I hit right-arrow, to start on the leftmost indicator applet. Just the left-to-wrap-right move. The indicator-session opens, and often the menu stays stuck open for a while. Incidentally, this behavior is a workaround for the loss of HUD access to indicator menus. (I suppose it may be what I did before the HUD arrived; I don't remember clearly.) Thanks, Marco! -- 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/1286580 Title: unity-panel-service crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED() Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: I tried to open the panel menus. Probably by keyboard first. The panel froze crashed. No unusual circumstances that I noticed. I don't know if this will be relevant, but: since recently trying KDE packages on this machine, KDE's settings seemed to have fouled up Unity's, when I returned. Many of the indicator icons were wrong or missing. Attempts to clear the settings, remove KDE packages, and restart, didn't make any difference. But after this crash, weeks later, the usual icons were finally restored. Seems strange. Thanks. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity-services 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sat Mar 1 00:14:03 2014 ExecutablePath: /usr/lib/unity/unity-panel-service MarkForUpload: True ProcCmdline: /usr/lib/unity/unity-panel-service ProcEnviron: PATH=(custom, no user) LANGUAGE=en_US XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f8097fa93a6:mov0x10(%rdx),%ecx PC (0x7f8097fa93a6) ok source 0x10(%rdx) (0x0010) not located in a known VMA region (needed readable region)! destination %ecx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libido3-0.1.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: unity-panel-service crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: Upgraded to saucy on 2014-01-16 (43 days ago) UserGroups: adm cdrom dip lpadmin nopasswdlogin plugdev sambashare sudo wireshark To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1286580/+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 1286580] Re: unity-panel-service crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED()
Hm, to clarity: The indicator-session opens, and often the menu stays stuck open for a whileas the panel crashes. That's how I first know the crash has happened again What I wanted to convey was that the rightmost indicator menu opens, and then the crash freezes it; my continued right-arrow inpuds. Not every time. Whether that means that particular indicator is involved, or the next one, date/time, that never opens--or whether that means anything--I am not knowledgeable enough to say. Thank you. -- 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/1286580 Title: unity-panel-service crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED() Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: I tried to open the panel menus. Probably by keyboard first. The panel froze crashed. No unusual circumstances that I noticed. I don't know if this will be relevant, but: since recently trying KDE packages on this machine, KDE's settings seemed to have fouled up Unity's, when I returned. Many of the indicator icons were wrong or missing. Attempts to clear the settings, remove KDE packages, and restart, didn't make any difference. But after this crash, weeks later, the usual icons were finally restored. Seems strange. Thanks. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity-services 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sat Mar 1 00:14:03 2014 ExecutablePath: /usr/lib/unity/unity-panel-service MarkForUpload: True ProcCmdline: /usr/lib/unity/unity-panel-service ProcEnviron: PATH=(custom, no user) LANGUAGE=en_US XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f8097fa93a6:mov0x10(%rdx),%ecx PC (0x7f8097fa93a6) ok source 0x10(%rdx) (0x0010) not located in a known VMA region (needed readable region)! destination %ecx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libido3-0.1.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: unity-panel-service crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: Upgraded to saucy on 2014-01-16 (43 days ago) UserGroups: adm cdrom dip lpadmin nopasswdlogin plugdev sambashare sudo wireshark To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1286580/+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 1125442] Re: Always Visible and On Top Windows Steal Focus on Workspace Switch
This issue is present in trusty. Possibly a duplicate of #1073488 Google Hangout chats in Chrome (and Chromium?) are probably the most popular trigger for this issue. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1125442 Title: Always Visible and On Top Windows Steal Focus on Workspace Switch Status in Ayatana Design: New Status in Xubuntu: New Status in “unity” package in Ubuntu: Confirmed Status in “unity” source package in Precise: Confirmed Status in “unity” source package in Quantal: Confirmed Status in “unity” source package in Raring: Confirmed Bug description: 1. Open any application (e.g. TextEditor) 2. Right click the title bar 2a. Select Always on Visible Workspace 3. Right click the title bar 3a. Select Always on Top 4. Open a different application (e.g. Terminal) 5. Ensure that window has focus 6. Switch workspaces (Notice: the first application now has focus) 7. Return to first workspace (Notice: the second application does not regain focus) Expected: The initial application should not have ever regained focus, and certainly the second application should have it when returning to that workspace. antarus@mach ~ $ lsb_release -rd Description:Ubuntu 12.04.1 LTS Release:12.04 antarus@mach ~ $ apt-cache policy unity unity: Installed: 5.18.0-0ubuntu2 Candidate: 5.18.0-0ubuntu2 Version table: To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1125442/+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 1300646] Re: XBMC steals input from the lockscreen
what is this fixed in? I still get it with Unity 7.2.0 and xbmc 13.0. The only solution is to switch terminals, kill xbmc, then switch back to the lock screen, click on the indicator (which regains focus) and then click on the password text input. If this is fixed by another bug then the bugs should be linked so that we can track the release. -- 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/1300646 Title: XBMC steals input from the lockscreen Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: Steps to reproduce: * launch xbmc * suspend * resume Expected results: * screen is locked with the unity lockscreen * you can unlock the screen * no input goes to xbmc Current results: * screen is locked * you can't unlock, 'cause all the input goes to XBMC behind the lockscreen ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140328.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 1 09:05:06 2014 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1300646/+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 1239710] Re: indicator-datetime or -session missing ~10% of the time
Can not find a means to logout of Ubuntu 13/10 Unity. Have attempted several time to reboot however no change -- 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, dx-packages https://bugs.launchpad.net/bugs/1239710 Title: indicator-datetime or -session missing ~10% of the time Status in The Date and Time Indicator: Fix Released Status in The Session Menu: Fix Released Status in “indicator-datetime” package in Ubuntu: Fix Released Status in “indicator-session” package in Ubuntu: Fix Released Status in “indicator-datetime” source package in Saucy: Fix Released Status in “indicator-session” source package in Saucy: Fix Released Bug description: Impact: sometime indicator-session or datetime go missing in unity Test Case: start sessions until that happens (or not) Regression potential: the change is a one liner workaround for a glib lock, shouldn't create issue, just check that those indicators keep working as they should --- Indicator-datetime is not showing in the indicator bar today on image 96. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-datetime 13.10.0+13.10.20131011-0ubuntu1 Uname: Linux 3.4.0-3-mako armv7l ApportVersion: 2.12.5-0ubuntu2 Architecture: armhf Date: Mon Oct 14 16:00:26 2013 InstallationDate: Installed on 2013-10-14 (0 days ago) InstallationMedia: Ubuntu 13.10 - armhf (20131014) MarkForUpload: True ProcEnviron: TERM=linux PATH=(custom, no user) SourcePackage: indicator-datetime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1239710/+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 1239710] Re: indicator-datetime or -session missing ~10% of the time
Can not find a means to logout of Ubuntu 13/10 Unity. Have attempted several time to reboot however no change -- 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, dx-packages https://bugs.launchpad.net/bugs/1239710 Title: indicator-datetime or -session missing ~10% of the time Status in The Date and Time Indicator: Fix Released Status in The Session Menu: Fix Released Status in “indicator-datetime” package in Ubuntu: Fix Released Status in “indicator-session” package in Ubuntu: Fix Released Status in “indicator-datetime” source package in Saucy: Fix Released Status in “indicator-session” source package in Saucy: Fix Released Bug description: Impact: sometime indicator-session or datetime go missing in unity Test Case: start sessions until that happens (or not) Regression potential: the change is a one liner workaround for a glib lock, shouldn't create issue, just check that those indicators keep working as they should --- Indicator-datetime is not showing in the indicator bar today on image 96. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-datetime 13.10.0+13.10.20131011-0ubuntu1 Uname: Linux 3.4.0-3-mako armv7l ApportVersion: 2.12.5-0ubuntu2 Architecture: armhf Date: Mon Oct 14 16:00:26 2013 InstallationDate: Installed on 2013-10-14 (0 days ago) InstallationMedia: Ubuntu 13.10 - armhf (20131014) MarkForUpload: True ProcEnviron: TERM=linux PATH=(custom, no user) SourcePackage: indicator-datetime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1239710/+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 1054321] Re: indicator-datetime-service crashed with signal 5 in g_wakeup_new()
I don't recall this indicator crashing in quite some time, so letting this expire seems fine. Thanks. -- 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/1054321 Title: indicator-datetime-service crashed with signal 5 in g_wakeup_new() Status in “indicator-datetime” package in Ubuntu: Incomplete Bug description: Upgraded to indicator-datetime 12.10.1-0ubuntu1 today -- this crash under that version was the first time this process has ever crashed on my machines. No visible cause, or effect. it has recurred once, over a few day's span. The most notable thing I can see about the crash is over 1000 threads in the thread stacktrace. This was first filed as bug 1053830, but apparently something in the data there wasn't right. The core dump was 65M, and the LP message was size does not fit in an int, so I'm guessing that was too big. This is a re-submission without the core dump; I cut it out of the crash file. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: indicator-datetime 12.10.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4 Uname: Linux 3.5.0-15-generic x86_64 ApportVersion: 2.5.2-0ubuntu4 Architecture: amd64 Date: Fri Sep 21 01:02:07 2012 ExecutablePath: /usr/lib/indicator-datetime/indicator-datetime-service ProcCmdline: /usr/lib/indicator-datetime/indicator-datetime-service ProcCwd: / ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 Signal: 5 SourcePackage: indicator-datetime StacktraceTop: g_wakeup_new () at /build/buildd/glib2.0-2.33.14/./glib/gwakeup.c:163 g_cancellable_make_pollfd (cancellable=cancellable@entry=0x7f206c0022c0, pollfd=pollfd@entry=0x7f20564d05e0) at /build/buildd/glib2.0-2.33.14/./gio/gcancellable.c:406 socket_source_new (cancellable=0x7f206c0022c0, condition=(G_IO_IN | G_IO_ERR | G_IO_HUP), socket=0x7f206c003a80) at /build/buildd/glib2.0-2.33.14/./gio/gsocket.c:3270 g_socket_create_source (socket=0x7f206c003a80, condition=condition@entry=(G_IO_IN | G_IO_ERR | G_IO_HUP), cancellable=cancellable@entry=0x7f206c0022c0) at /build/buildd/glib2.0-2.33.14/./gio/gsocket.c:3335 _g_socket_read_with_control_messages (socket=0x7f206c003a80, buffer=0x7f205400aa00, count=16, messages=0x7f206c00f950, num_messages=0x7f206c00f958, io_priority=optimized out, cancellable=0x7f206c0022c0, callback=0x7f207f8f5620 _g_dbus_worker_do_read_cb, user_data=0x7f206c00f8c0) at /build/buildd/glib2.0-2.33.14/./gio/gdbusprivate.c:200 Title: indicator-datetime-service crashed with signal 5 in g_wakeup_new() UpgradeStatus: Upgraded to quantal on 2012-06-14 (98 days ago) UserGroups: adm cdrom dip lpadmin nopasswdlogin plugdev sambashare sudo XsessionErrors: (indicator-multiload:4573): GLib-GIO-CRITICAL **: GApplication subclass 'Main' failed to chain up on ::startup (from start of override function) (eog:6874): EOG-CRITICAL **: eog_list_store_length: assertion `EOG_IS_LIST_STORE (store)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1054321/+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 1013171] Re: Many package hooks not ported to python3
This report was already getting too big for Launchpad to handle quickly, and is all marked fixed. In these cases I'm usually advised to leave the closed report as it is, and handle the new occurrence with the new bug. You can certainly put a link to this bug, there, for informational purposes. Maybe I can get to that. Thanks! -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-applet in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1013171 Title: Many package hooks not ported to python3 Status in “apache2” package in Ubuntu: Fix Released Status in “apport” package in Ubuntu: Fix Released Status in “apport-symptoms” package in Ubuntu: Fix Released Status in “bluez” package in Ubuntu: Fix Released Status in “cairo-dock” package in Ubuntu: Fix Released Status in “chromium-browser” package in Ubuntu: Fix Released Status in “compiz” package in Ubuntu: Fix Released Status in “connman” package in Ubuntu: Fix Released Status in “dkms” package in Ubuntu: Fix Released Status in “gnome-control-center” package in Ubuntu: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: Fix Released Status in “indicator-applet” package in Ubuntu: Fix Released Status in “libatasmart” package in Ubuntu: Fix Released Status in “lxpanel” package in Ubuntu: Fix Released Status in “mdadm” package in Ubuntu: Fix Released Status in “mysql-5.5” package in Ubuntu: Fix Released Status in “mythtv” package in Ubuntu: Fix Released Status in “nautilus” package in Ubuntu: Fix Released Status in “network-manager” package in Ubuntu: Fix Released Status in “shadow” package in Ubuntu: Fix Released Status in “udisks2” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “xdiagnose” package in Ubuntu: Fix Released Status in “apache2” source package in Quantal: Fix Released Status in “apport” source package in Quantal: Fix Released Status in “apport-symptoms” source package in Quantal: Fix Released Status in “bluez” source package in Quantal: Fix Released Status in “cairo-dock” source package in Quantal: Fix Released Status in “chromium-browser” source package in Quantal: Fix Released Status in “compiz” source package in Quantal: Fix Released Status in “connman” source package in Quantal: Fix Released Status in “dkms” source package in Quantal: Fix Released Status in “gnome-control-center” source package in Quantal: Fix Released Status in “gnome-settings-daemon” source package in Quantal: Fix Released Status in “indicator-applet” source package in Quantal: Fix Released Status in “libatasmart” source package in Quantal: Fix Released Status in “lxpanel” source package in Quantal: Fix Released Status in “mdadm” source package in Quantal: Fix Released Status in “mysql-5.5” source package in Quantal: Fix Released Status in “mythtv” source package in Quantal: Fix Released Status in “nautilus” source package in Quantal: Fix Released Status in “network-manager” source package in Quantal: Fix Released Status in “shadow” source package in Quantal: Fix Released Status in “udisks2” source package in Quantal: Fix Released Status in “unity” source package in Quantal: Fix Released Status in “xdiagnose” source package in Quantal: Fix Released Bug description: Since the description here is the only post that can be updated, it seems the best place to keep a changing list of packages that need examining. (The original description was brief, and about only one package.) We've fixed all the packages that found in the apt logs uploaded in the first round of breakage. Now I've tried to review all the other apport hooks I could find in Quantal. Working from the archive's Contents file, I got the list of packages that have files under /usr/share/apport/package-hooks . I skipped the packages already fixed above, and those that were on my system, during the first round of breakage, and had no problems. For the rest, I downloaded the debs, extracted the apport hooks, and ran '2to3' on them. I've posted patches for every package that broke under python3. Thanks - Edward Donovan edward.dono...@numble.net These packages didn't break during the apport upgrade that forced a recompile, but they get warnings from the 2to3 tool: compiz-core eclipse-platform gnome-control-center-data gnome-settings-daemon grub-common nautilus-data unity-common apache2.2-common Now we have a bug report for at least gnome-control-center, bug 1018537, which I've duped here. So these may need patching, too. Hm...from a preliminary look, a number of those use the same code: if report.has_key(Stacktrace) which generates an exception with python3. We're probably going to want to change those to if Stacktrace in report and I'll try to post some of those
[Dx-packages] [Bug 967879] Re: hud-service has a memory leak (I think)
I see that this bug is marked as fixed in 0.3.96。I'm still seeing it in 0.3.97-0ubuntu1. I have a number of Ubuntu 12.04 LTSP Fat clients, and none of them can last more than a day or two without hud-service using up all of the memory on the machine. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-appmenu in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/967879 Title: hud-service has a memory leak (I think) Status in “indicator-appmenu” package in Ubuntu: Fix Released Bug description: After about 8 hours of use, I closed all the following programs: Pidgin Eclipse Rational Team Concert ATT's AGNclient VPN software Banshee Chrome Synaptic Gnome-Calculator Gnome-Terminal Nautilus Lotus Notes ...and noticed that hud-service is taking up 162M of RAM. It started out taking up something like 24M. Isn't that memory usage a little high? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-appmenu/+bug/967879/+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
