[Dx-packages] [Bug 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled
This bug still affects me on an up to date saucy, with installed systemd-shim 6-0ubuntu0.13.10. I also tried systemd-shim in alternative ppa as described in https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1184262/comments/151 I could only workaround the problem through http://ubuntuforums.org/showthread.php?t=2182128p=12830153#post12830153 -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1252121 Title: missing PrepareForSleep signal after resuming, causing networking to stay disabled Status in “systemd-shim” package in Ubuntu: Confirmed Status in “systemd-shim” source package in Saucy: Confirmed Status in “systemd-shim” source package in Trusty: Confirmed Bug description: As per request from bug #1184262, this is a new report, along with dbus (to be attached) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: systemd-services 204-0ubuntu19 Uname: Linux 3.12.0-custom x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sun Nov 17 20:24:41 2013 MarkForUpload: True SourcePackage: systemd UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago) SRU INFORMATION: FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty already) Regression potential: Low. Flushing the session bus was introduced in version 4 and is obviously bogus as in a system D-BUS service there is no session bus. This causes lots of confusing error messages and unnecessary overhead like trying to start dbus-launch. Flushing the system bus is low-risk, in most cases it's a no-op and it would otherwise prevent losing signals after waking up. No known regressions. TEST CASE: Run several suspend/resume cycles with the lid, session indicator menu, and verify that the network comes back up. It is known that this fix is necessary but not sufficient, so it is not expected to fix all cases. But it should not make things worse, so if network now does not come up any more on a machine where it previously worked this would count as failure/regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1252121/+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 1275297] [NEW] Unity menu headings and nautilus icons/text ignoring text scaling factor
Public bug reported: After re-starting Ubuntu following the latest kernel update (which came on Jan 30 or 31), in Unity, the text scaling factor is now being ignored in the menu headings in all applications as well as for file/folder icons and all text in Nautilus and the Dash. It also has no effect on the time displayed in the system tray (though it continues to scale the other icons in the system tray). In the Universal Access settings, I have the text size set to large, which changes the text scaling factor from 1.0 to 1.25. I have also tried changing the text scaling factor through the Unity Tweak Tool, but that doesn't make a difference. An attachment is including showing a few screenshots. Notice that the menu headings are much smaller than the menu items in the dropdown, and the time display is smaller than the icons in the system tray. The icons and text in Nautilus are also smaller than the menu items, and remains unaffected when changing the text scaling factor. This is a brand new problem with the recent update. I've been running 13.10 since it was first released, and this problem just started today. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 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: Sat Feb 1 13:15:42 2014 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0589] InstallationDate: Installed on 2013-11-14 (79 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Dell Inc. XPS 12 9Q23 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-15-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash video.use_bios_initial_backlight=0 vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/06/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 00WT0D dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A04 dmi.modalias: dmi:bvnDellInc.:bvrA04:bd11/06/2012:svnDellInc.:pnXPS129Q23:pvrA04:rvnDellInc.:rn00WT0D:rvrA00:cvnDellInc.:ct8:cvrA04: dmi.product.name: XPS 12 9Q23 dmi.product.version: A04 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 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.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Sat Feb 1 10:41:17 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 957 vendor LGD xserver.version: 2:1.14.5-1ubuntu2~saucy1 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 saucy ubuntu ** Attachment added: Screenshots of menu headings, time display, and Nautilus https://bugs.launchpad.net/bugs/1275297/+attachment/3965577/+files/screenshots.pdf -- 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/1275297 Title: Unity menu headings and nautilus icons/text ignoring text scaling factor Status in “unity” package in Ubuntu: New Bug description: After re-starting Ubuntu following the latest kernel update (which came on Jan 30 or 31), in Unity, the text scaling factor is now being ignored in the menu headings in all applications as well as for file/folder icons and all text in Nautilus and the Dash. It also has no effect on the time displayed in the system tray (though it continues to scale the other icons in the system tray). In the Universal Access settings, I have the text size set to large, which changes the text scaling factor from 1.0 to 1.25. I have also tried changing the text scaling factor through the Unity Tweak Tool, but
[Dx-packages] [Bug 1275303] [NEW] Ubuntu 13.10 gedit fails every time unless user removes zeitgeist directory
Public bug reported: $ uname - a = Linux machine1 3.11.0-14-generic #21-Ubuntu SMP Tue Nov 12 17:04:55 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux $ gedit --version = gedit - Version 3.8.3 $ which gedit = /usr/bin/gedit $ ls -l /usr/bin/gedit = -rwxr-xr-x 1 root root 597776 Jul 13 2013 /usr/bin/gedi $ gedit = ** (gedit:7079): CRITICAL **: file log.c: line 980: unexpected error: Error calling StartServiceByName for org.gnome.zeitgeist.Engine: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process /usr/bin/zeitgeist-daemon exited with status 21 (g-dbus-error-quark, 25) $ rm ~/.local/share/zeitgeist -R = rm: descend into write-protected directory ‘/home/foo/.local/share/zeitgeist’? y = rm: remove write-protected directory ‘/home/foo/.local/share/zeitgeist’? y = rm: cannot remove ‘/home/foo/.local/share/zeitgeist’: Permission denied $ sudo rm ~/.local/share/zeitgeist -R = $ gedit Now works! ** Affects: unity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1275303 Title: Ubuntu 13.10 gedit fails every time unless user removes zeitgeist directory Status in “unity” package in Ubuntu: New Bug description: $ uname - a = Linux machine1 3.11.0-14-generic #21-Ubuntu SMP Tue Nov 12 17:04:55 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux $ gedit --version = gedit - Version 3.8.3 $ which gedit = /usr/bin/gedit $ ls -l /usr/bin/gedit = -rwxr-xr-x 1 root root 597776 Jul 13 2013 /usr/bin/gedi $ gedit = ** (gedit:7079): CRITICAL **: file log.c: line 980: unexpected error: Error calling StartServiceByName for org.gnome.zeitgeist.Engine: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process /usr/bin/zeitgeist-daemon exited with status 21 (g-dbus-error-quark, 25) $ rm ~/.local/share/zeitgeist -R = rm: descend into write-protected directory ‘/home/foo/.local/share/zeitgeist’? y = rm: remove write-protected directory ‘/home/foo/.local/share/zeitgeist’? y = rm: cannot remove ‘/home/foo/.local/share/zeitgeist’: Permission denied $ sudo rm ~/.local/share/zeitgeist -R = $ gedit Now works! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1275303/+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 1275303] Re: Ubuntu 13.10 gedit fails every time unless user removes zeitgeist directory
I found the solution only by reading a very similar bug report: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1245589 Titled: Doesn't run, reports a zeitgeist/dbus error This was the key suggestion that solved the problem: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1250314/comments/2 The reason I file this bug is that it took me a while to find this solution, and, I still don't know the cause, and, others may run into this problem also - so the ubuntu team would want to know about this. If this turns out to be a duplicate, I understand. If it turns out (somehow) to be user error, I understand - although - I never heard about this zeitgeist stuff before - so - if it was user error - I have no idea how that happened. -- 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/1275303 Title: Ubuntu 13.10 gedit fails every time unless user removes zeitgeist directory Status in “unity” package in Ubuntu: New Bug description: $ uname - a = Linux machine1 3.11.0-14-generic #21-Ubuntu SMP Tue Nov 12 17:04:55 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux $ gedit --version = gedit - Version 3.8.3 $ which gedit = /usr/bin/gedit $ ls -l /usr/bin/gedit = -rwxr-xr-x 1 root root 597776 Jul 13 2013 /usr/bin/gedi $ gedit = ** (gedit:7079): CRITICAL **: file log.c: line 980: unexpected error: Error calling StartServiceByName for org.gnome.zeitgeist.Engine: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process /usr/bin/zeitgeist-daemon exited with status 21 (g-dbus-error-quark, 25) $ rm ~/.local/share/zeitgeist -R = rm: descend into write-protected directory ‘/home/foo/.local/share/zeitgeist’? y = rm: remove write-protected directory ‘/home/foo/.local/share/zeitgeist’? y = rm: cannot remove ‘/home/foo/.local/share/zeitgeist’: Permission denied $ sudo rm ~/.local/share/zeitgeist -R = $ gedit Now works! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1275303/+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 1275325] [NEW] computer freezes (have to reboot) due to nouveau driver
Public bug reported: The problem seems to be when im browsing the web (any graphics / flash maybe). I have to reboot to recover since the computer just freezes. it originally occured with firefox, so i removed that and used chromium instead, but this also has the same problem. i just reproduced the freeze now while i was using google maps. i have also got this freeze while using mathematica. im using the nouveau drivers, i have an nvidia G96GL (Quadro Fx 580). i can see in /var/log/xorg lots of messages relating to nouveau. Is there a way i can capture the freeze and which files to check? one trace i did get mentioned X.org channel or something like that. when i reboot, the system detect there was a crash, so i have allowed ubuntu to analyse any crash logs. does anyone know of a better more stable graphics card that works well with ubuntu 13.10 im using the 32 bit version i686 of ubuntu 13.10. xeon quad core, 24 G ram. thanks. ** Affects: unity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1275325 Title: computer freezes (have to reboot) due to nouveau driver Status in “unity” package in Ubuntu: New Bug description: The problem seems to be when im browsing the web (any graphics / flash maybe). I have to reboot to recover since the computer just freezes. it originally occured with firefox, so i removed that and used chromium instead, but this also has the same problem. i just reproduced the freeze now while i was using google maps. i have also got this freeze while using mathematica. im using the nouveau drivers, i have an nvidia G96GL (Quadro Fx 580). i can see in /var/log/xorg lots of messages relating to nouveau. Is there a way i can capture the freeze and which files to check? one trace i did get mentioned X.org channel or something like that. when i reboot, the system detect there was a crash, so i have allowed ubuntu to analyse any crash logs. does anyone know of a better more stable graphics card that works well with ubuntu 13.10 im using the 32 bit version i686 of ubuntu 13.10. xeon quad core, 24 G ram. thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1275325/+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 879218] Re: some users prefer the old grid behaviour (dividing each time the keybinding are used)
This bug is still alive in compiz-0.9.10+20131011-0ubuntu1 (saucy salamander). -- You received this bug notification because you are a member of DX Packages, which is subscribed to compiz-plugins-main in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/879218 Title: some users prefer the old grid behaviour (dividing each time the keybinding are used) Status in Compiz: Fix Released Status in Compiz Grid Plugin: Fix Committed Status in Compiz Main Plugins: Fix Committed Status in Unity: Won't Fix Status in “compiz” package in Ubuntu: Fix Released Status in “compiz-plugins-main” package in Ubuntu: Fix Committed Bug description: I've used the Compiz Grid function for a long time and I generally use it to set my browser to the right 2/3 or 3/4 of the screen and have other apps on the top or bottom half of the remaining part. Now when I press ctrl + alt numpad 4 or numpad 6 it only does half and when pressing it a second or third time it does nothing. The options for different sizes work for all the corners and top and bottom. When I press ctrl + alt numpad 9 it does the same thing as pressing ctrl + alt numpat 8. Here's a video that may illustrate the problem better than my description. http://www.youtube.com/watch?v=i3WC0BnXe5E ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: unity 4.22.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 1.23-0ubuntu3 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,move,gnomecompat,mousepoll,imgpng,unitymtgrabhandles,regex,animation,grid,snap,expo,workarounds,ezoom,resize,vpswitch,place,wall,staticswitcher,fade,session,scale,unityshell] Date: Thu Oct 20 23:03:00 2011 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) A video of the latest Grid version (also showing this fix in action): https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/745159/+attachment/3660185/+files/GridAllFunctionalityFullyFixed.mp4 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/879218/+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
supposedly there was a fix released some weeks ago, but that didn't help. same issue: https://bugs.launchpad.net/ubuntu/+source/indicator- datetime/+bug/1239710 -- 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 “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/ubuntu/+source/indicator-datetime/+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 1239710] Re: indicator-datetime or -session missing ~10% of the time
well this is still happening, there's no fix yet. https://bugs.launchpad.net/ubuntu/+source/indicator- datetime/+bug/1228360 -- 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 1275379] [NEW] unity_support_test crashed with SIGSEGV in __GI___pthread_mutex_lock()
Public bug reported: This occured on VirtualBox. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: nux-tools 4.0.3+13.10.20131011-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0 Uname: Linux 3.13.0-6-generic x86_64 .tmp.unity.support.test.0: .tmp.unity.support.test.1: ApportVersion: 2.13.2-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 CurrentDesktop: Unity Date: Sun Feb 2 10:51:19 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExecutablePath: /usr/lib/nux/unity_support_test GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) InstallationDate: Installed on 2014-02-01 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140201) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcCmdline: /usr/lib/nux/unity_support_test ProcEnviron: LANGUAGE=ja PATH=(custom, user) XDG_RUNTIME_DIR=set LANG=ja_JP.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-6-generic root=UUID=3059f971-387f-40ef-aa3c-259dd346cbb1 ro quiet splash vt.handoff=7 Renderer: Software SegvAnalysis: Segfault happened at: 0x7f6342c2a414 __GI___pthread_mutex_lock+4:mov 0x10(%rdi),%esi PC (0x7f6342c2a414) ok source 0x10(%rdi) (0x20d8) not located in a known VMA region (needed readable region)! destination %esi ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: nux StacktraceTop: __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:66 ?? () from /usr/lib/x86_64-linux-gnu/dri/vboxvideo_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/vboxvideo_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/vboxvideo_dri.so start_thread (arg=0x7f63404de700) at pthread_create.c:312 Title: unity_support_test crashed with SIGSEGV in __GI___pthread_mutex_lock() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.907-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu1 xserver.bootTime: Sun Feb 2 10:51:12 2014 xserver.configfile: default xserver.errors: AIGLX error: vboxvideo does not export required DRI extension AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.14.5-1ubuntu3 xserver.video_driver: vboxvideo ** Affects: nux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash compiz-0.9 need-amd64-retrace trusty ubuntu ** Information type changed from Private to Public -- 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/1275379 Title: unity_support_test crashed with SIGSEGV in __GI___pthread_mutex_lock() Status in “nux” package in Ubuntu: New Bug description: This occured on VirtualBox. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: nux-tools 4.0.3+13.10.20131011-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0 Uname: Linux 3.13.0-6-generic x86_64 .tmp.unity.support.test.0: .tmp.unity.support.test.1: ApportVersion: 2.13.2-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 CurrentDesktop: Unity Date: Sun Feb 2 10
[Dx-packages] [Bug 1275387] [NEW] Network stay inactive after resume
Public bug reported: After each resume, network is not active and activating it from network- manager does nothing. Isuing the command sudo nmcli nm sleep false brings it back ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: systemd-shim 6-0ubuntu0.13.10 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Sun Feb 2 13:53:18 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-02-23 (343 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: systemd-shim UpgradeStatus: Upgraded to saucy on 2014-01-26 (6 days ago) ** Affects: systemd-shim (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 systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1275387 Title: Network stay inactive after resume Status in “systemd-shim” package in Ubuntu: New Bug description: After each resume, network is not active and activating it from network-manager does nothing. Isuing the command sudo nmcli nm sleep false brings it back ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: systemd-shim 6-0ubuntu0.13.10 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Sun Feb 2 13:53:18 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-02-23 (343 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: systemd-shim UpgradeStatus: Upgraded to saucy on 2014-01-26 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1275387/+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 1193810] Re: Bluetooth icon disappears when BT switched off
*** This bug is a duplicate of bug 1126108 *** https://bugs.launchpad.net/bugs/1126108 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-bluetooth (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1193810 Title: Bluetooth icon disappears when BT switched off Status in Bluetooth Menu: Confirmed Status in “indicator-bluetooth” package in Ubuntu: Confirmed Bug description: In Ubuntu 13.04, the Bluetooth panel icon of the default bluetooth app has a switch for turning Bluetooth on/off, but once you click it (to turn BT off), the icon disappears. One would expect the icon to remain, but just grayed out, and having the switch in the menu in the off position (so that clicking it would turn BT back on). Instead, to re-enable bluetooth, one must currently open System settings and re-enable it from there. Some others have noticed this, too. Useful info here: http://askubuntu.com/questions/293360/bluetooth-indicator-disappears- on-turning-off-bluetooth To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-bluetooth/+bug/1193810/+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
