[Desktop-packages] [Bug 1021374] Re: colord crashed with SIGSEGV in cd_device_register_object()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: colord (Ubuntu Precise) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1021374 Title: colord crashed with SIGSEGV in cd_device_register_object() Status in Colord: Confirmed Status in “colord” package in Ubuntu: Triaged Status in “colord” source package in Precise: Confirmed Status in “colord” source package in Quantal: Triaged Status in “colord” package in Debian: Confirmed Bug description: colord crashed with SIGSEGV in cd_device_register_object() ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: colord 0.1.21-1 ProcVersionSignature: Ubuntu 3.5.0-3.3-generic 3.5.0-rc5 Uname: Linux 3.5.0-3-generic x86_64 ApportVersion: 2.2.5-0ubuntu2 Architecture: amd64 CrashCounter: 1 Date: Thu Jul 5 09:30:50 2012 ExecutablePath: /usr/lib/x86_64-linux-gnu/colord/colord ProcCmdline: /usr/lib/x86_64-linux-gnu/colord/colord ProcEnviron: SegvAnalysis: Segfault happened at: 0x40b1dd cd_device_register_object+157: mov 0x8(%rax),%rbx PC (0x0040b1dd) ok source 0x8(%rax) (0x0008) not located in a known VMA region (needed readable region)! destination %rbx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: colord StacktraceTop: cd_device_register_object () ?? () ?? () ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: colord crashed with SIGSEGV in cd_device_register_object() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/colord/+bug/1021374/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1050202] Re: Cherrypick xrandr list providers to complete DRI2 offloading graphics stack
** Bug watch added: freedesktop.org Bugzilla #54840 https://bugs.freedesktop.org/show_bug.cgi?id=54840 ** Also affects: xorg-server via https://bugs.freedesktop.org/show_bug.cgi?id=54840 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to x11-xserver-utils in Ubuntu. https://bugs.launchpad.net/bugs/1050202 Title: Cherrypick xrandr list providers to complete DRI2 offloading graphics stack Status in X.Org X server: Unknown Status in “x11-xserver-utils” package in Ubuntu: New Bug description: Assuming that Intel 2.20.7 and Nouveau 1.0.2 land for Quantal, we will have 99% of the components needed for Phase 1 PRIME support referred to as DRI2 offloading. The only missing piece would be a single commit for xrandr. http://cgit.freedesktop.org/xorg/app/xrandr/commit/?id=7cb20881991c8bcf7e8fa0af6ad0f85682f98e1f Phase 2 stuff like power management and auto-switching aren't going to be ready until 13.04, but we can do Phase 1 rather easily in this cycle since everything else (dri2proto, xserver, mesa, etc) is ready. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: x11-xserver-utils 7.7~3 [modified: usr/bin/xkeystone usr/bin/xrandr] Uname: Linux 3.6.0-rc4-prime-pm x86_64 ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 Date: Thu Sep 13 01:35:09 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:1500] NVIDIA Corporation GF106 [GeForce GT 555M] [10de:0dce] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:1500] InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120606.2) MachineType: CLEVO CO. W150HRM ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.0-rc4-prime-pm root=UUID=3cdf2528-bb9d-4f05-8654-b8d0f2bc560a ro quiet splash acpi_osi= vt.handoff=7 SourcePackage: x11-xserver-utils UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/24/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: W150HRM dmi.board.vendor: CLEVO CO. dmi.board.version: N/A dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 9 dmi.chassis.vendor: CLEVO CO. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd11/24/2011:svnCLEVOCO.:pnW150HRM:pvrN/A:rvnCLEVOCO.:rnW150HRM:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A: dmi.product.name: W150HRM dmi.product.version: N/A dmi.sys.vendor: CLEVO CO. version.compiz: compiz 1:0.9.8.0-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.39+git20120910.b925022a-0ubuntu0ricotz version.libgl1-mesa-dri: libgl1-mesa-dri 9.0~git20120910+9.0.7f011e20-0ubuntu0ricotz version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0~git20120910+9.0.7f011e20-0ubuntu0ricotz version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99+git20120816.cdf522f5-0ubuntu0sarvatt version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.6-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.1+git20120816.3aa9a296-0ubuntu0sarvatt To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1050202/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1022464] Re: kernel upgrade from 3.0.0-14 to 3.0.0-22 makes incorrect display position on dell vostro 3560
It has the same problem after upgrading to kernel 3.0.0.25. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1022464 Title: kernel upgrade from 3.0.0-14 to 3.0.0-22 makes incorrect display position on dell vostro 3560 Status in “xorg” package in Ubuntu: New Bug description: I have a Dell Vostro 3560 machine. It was deployed with Ubuntu 11.10. After last kernel update from 3.0.0-14 to 3.0.0-22, the screen has a 2mm width band blinking at the top - almost in cyan. Cannot move the mouse into this band. It seems if screen would be incorrectly positioned. When booted back to 3.0.0-14 the screen is fine again To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1022464/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1032433] Re: Using WEP 128-bit Passphrase, Ad-hoc connection cannot be established
** Tags removed: rls-q-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1032433 Title: Using WEP 128-bit Passphrase, Ad-hoc connection cannot be established Status in OEM Priority Project: Incomplete Status in OEM Priority Project precise series: Incomplete Status in “network-manager” package in Ubuntu: Incomplete Bug description: When setting up an ad-hoc wifi connection, if choose WEP 128-bit Passphrase, the connection cannot be established. If choose None or WEP 40/128-bit Key, it can be established successfully. Steps to reproduce: 1. Choose Create new Wireless Network in network applet 2. Choose WEP 128-bit Passphrase and create an ad-hoc connection 3. Use another computer to connect the same ad-hoc ESSID 4. The connection cannot be established To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1032433/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1031176] Re: evolution crashed with SIGSEGV in imapx_command_copy_messages_step_done()
Mathieu, when you have a minute, can you look at that one please? ** Changed in: evolution (Ubuntu) Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl) ** Changed in: evolution (Ubuntu) Status: New = Confirmed ** Changed in: evolution (Ubuntu) Milestone: None = ubuntu-12.10 ** Also affects: evolution (Ubuntu Quantal) Importance: Medium Assignee: Mathieu Trudel-Lapierre (mathieu-tl) Status: Confirmed ** Tags removed: rls-q-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1031176 Title: evolution crashed with SIGSEGV in imapx_command_copy_messages_step_done() Status in “evolution” package in Ubuntu: Confirmed Status in “evolution” source package in Quantal: Confirmed Bug description: This, like so many of my evolution crashes, occurred while Evolution was calmly processing email in the background. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: evolution 3.5.4-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-6.6-generic 3.5.0 Uname: Linux 3.5.0-6-generic x86_64 ApportVersion: 2.4-0ubuntu6 Architecture: amd64 CrashCounter: 1 Date: Tue Jul 31 10:52:08 2012 ExecutablePath: /usr/bin/evolution InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120521) ProcCmdline: evolution ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, user) LANG=en_AU.UTF-8 SHELL=/bin/zsh SegvAnalysis: Segfault happened at: 0x7f5ded032c68:cmpl $0x9,0x4(%rax) PC (0x7f5ded032c68) ok source $0x9 ok destination 0x4(%rax) (0x0004) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: evolution StacktraceTop: ?? () from /usr/lib/libcamel-1.2.so.39 ?? () from /usr/lib/libcamel-1.2.so.39 g_thread_proxy (data=0x7f5dac2b7800) at /build/buildd/glib2.0-2.33.6/./glib/gthread.c:801 start_thread (arg=0x7f5da3fff700) at pthread_create.c:308 clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 Title: evolution crashed with SIGSEGV in g_thread_proxy() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: lpadmin sbuild sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1031176/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1037669] Re: gst-plugin-scanner and browser plugins are used when opening certain emails
@Mathieu: can you please have a look at this when you have a minute? Can we disable it for release? ** Also affects: evolution (Ubuntu Quantal) Importance: High Status: Confirmed ** Changed in: evolution (Ubuntu Quantal) Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl) ** Changed in: evolution (Ubuntu Quantal) Milestone: None = ubuntu-12.10-beta-2 ** Tags removed: rls-q-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1037669 Title: gst-plugin-scanner and browser plugins are used when opening certain emails Status in “evolution” package in Ubuntu: Confirmed Status in “evolution” source package in Quantal: Confirmed Status in “evolution” package in Debian: New Bug description: Evolution now uses webkit for html mail in 12.10. On launch, it tries to access the google-talkplugin. When looking at a certain messages in preview mode (a google calendar invite), it tries to launch /usr/lib/x86_64-linux-gnu/gstreamer0.10/gstreamer-0.10/gst-plugin- scanner. Interestingly, this is happening even though I have 'Only ever show plain text' configured in Preferences/Mail Preferences/HTML Messages (I do have 'Show suppressed HTML parts as attachments' selected). This suggests that evolution: - would gladly use plugins - that javascript is possibly enabled (for the plugin finder) - that the WebKit HTML renderer is being invoked even though 'Only ever show plain text' is selected Webkit is an immensely powerful renderer and it is being used to render completely untrusted input from anyone who can send an email. We need to make sure that plugins and javascript are disabled and that the renderer is not being used at all when 'Only ever show plain text' is enabled (it could be used to deliver text/plain, but it seems that it is processing the HTML then discarding it). This would bring it in line with Thunderbird's policies. I noticed this because I use AppArmor to confine evolution. Unfortunately in my situation, evolution hung on the message that invoked the plugin finder because the plugin finder failed to launch. I have rules now that will prevent the hang, but evolution isn't handling this error condition gracefully either. This should be considered an important security regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1037669/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1016824] Re: Ubuntu wallpapers are low quality (low resolution, JPEG artefacts, noise)
Still seeing this in the latest quantal wallpaper. The default purple wallpaper is grainy and looks low quality. The others in quantal are better than precise though. ** Description changed: Ubuntu wallpapers are low quality. They often are low resolution, have JPEG artefacts and/or visible noise. This degrades the quality feel of the desktop itself. The low resolution is self explanatory. Many people use a monitor resolution that is 1920 pixels wide. This should be easy to support as even the lowest quality digital camera is higher resolution than that. By comparison, gnome-backgrounds uses mostly 2560x1600 or 1920x1200. Often JPEG artefacts are visible in areas of very slight gradation. Though in precise I think there is a bigger problem with noise. Neither of these should be visible on the desktop. Please increase the JPEG encoding quality, and the image smoothness before that. Compare ubuntu-wallpapers with those from gnome-backgrounds. Though gnome-backgrounds are not great quality either, they are far better prepared than ubuntu-wallpapers. - - I repeat: This degrades the quality feel of the desktop. ** Also affects: ubuntu-wallpapers Importance: Undecided Status: New ** Also affects: ayatana-design Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1016824 Title: Ubuntu wallpapers are low quality (low resolution, JPEG artefacts, noise) Status in Ayatana Design: New Status in Ubuntu Wallpapers: New Status in “ubuntu-wallpapers” package in Ubuntu: New Bug description: Ubuntu wallpapers are low quality. They often are low resolution, have JPEG artefacts and/or visible noise. This degrades the quality feel of the desktop itself. The low resolution is self explanatory. Many people use a monitor resolution that is 1920 pixels wide. This should be easy to support as even the lowest quality digital camera is higher resolution than that. By comparison, gnome-backgrounds uses mostly 2560x1600 or 1920x1200. Often JPEG artefacts are visible in areas of very slight gradation. Though in precise I think there is a bigger problem with noise. Neither of these should be visible on the desktop. Please increase the JPEG encoding quality, and the image smoothness before that. Compare ubuntu-wallpapers with those from gnome-backgrounds. Though gnome-backgrounds are not great quality either, they are far better prepared than ubuntu-wallpapers. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1016824/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1048606] Re: refactor gtk sections from asyncconn for use by print-manager
I think Till did that this week. Can you please check that Jonathan? ** Changed in: system-config-printer (Ubuntu Quantal) Status: New = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1048606 Title: refactor gtk sections from asyncconn for use by print-manager Status in “system-config-printer” package in Ubuntu: Fix Released Status in “system-config-printer” source package in Quantal: Fix Released Bug description: KDE's new print tool uses /usr/bin/scp-dbus-service which uses asyncconn/asyncipp/asyncpk1 from system-config-printer-gtk, these files need to learn how to cope without gtk around and be moved into system-config-printer-common (then print-manager needs to depend on s-c-p-common) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1048606/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1021374] Re: colord crashed with SIGSEGV in cd_device_register_object()
** Changed in: colord (Ubuntu Quantal) Importance: High = Medium ** Changed in: colord (Ubuntu Quantal) Milestone: None = ubuntu-12.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1021374 Title: colord crashed with SIGSEGV in cd_device_register_object() Status in Colord: Confirmed Status in “colord” package in Ubuntu: Triaged Status in “colord” source package in Precise: Confirmed Status in “colord” source package in Quantal: Triaged Status in “colord” package in Debian: Confirmed Bug description: colord crashed with SIGSEGV in cd_device_register_object() ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: colord 0.1.21-1 ProcVersionSignature: Ubuntu 3.5.0-3.3-generic 3.5.0-rc5 Uname: Linux 3.5.0-3-generic x86_64 ApportVersion: 2.2.5-0ubuntu2 Architecture: amd64 CrashCounter: 1 Date: Thu Jul 5 09:30:50 2012 ExecutablePath: /usr/lib/x86_64-linux-gnu/colord/colord ProcCmdline: /usr/lib/x86_64-linux-gnu/colord/colord ProcEnviron: SegvAnalysis: Segfault happened at: 0x40b1dd cd_device_register_object+157: mov 0x8(%rax),%rbx PC (0x0040b1dd) ok source 0x8(%rax) (0x0008) not located in a known VMA region (needed readable region)! destination %rbx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: colord StacktraceTop: cd_device_register_object () ?? () ?? () ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: colord crashed with SIGSEGV in cd_device_register_object() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/colord/+bug/1021374/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1016470] Re: colord crashed with SIGSEGV in __opendirat()
** Changed in: colord (Ubuntu) Assignee: (unassigned) = Chris Halse Rogers (raof) ** Changed in: colord (Ubuntu) Milestone: None = ubuntu-12.10-beta-2 ** Tags removed: rls-q-incoming ** Also affects: colord (Ubuntu Quantal) Importance: Medium Assignee: Chris Halse Rogers (raof) Status: Confirmed ** Changed in: colord (Ubuntu Quantal) Milestone: ubuntu-12.10-beta-2 = ubuntu-12.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1016470 Title: colord crashed with SIGSEGV in __opendirat() Status in “colord” package in Ubuntu: Confirmed Status in “colord” source package in Quantal: Confirmed Bug description: Ubuntu Desktop 20120622 Crashed on login on a live session ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: colord 0.1.16-2 ProcVersionSignature: Ubuntu 3.5.0-1.1-generic 3.5.0-rc3 Uname: Linux 3.5.0-1-generic x86_64 ApportVersion: 2.2.5-0ubuntu1 Architecture: amd64 CasperVersion: 1.318 Date: Fri Jun 22 10:27:01 2012 ExecutablePath: /usr/lib/x86_64-linux-gnu/colord/colord LiveMediaBuild: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120622) ProcCmdline: /usr/lib/x86_64-linux-gnu/colord/colord ProcEnviron: SegvAnalysis: Segfault happened at: 0x7fb1b9569dc4:cmpb $0x0,(%rsi) PC (0x7fb1b9569dc4) ok source $0x0 ok destination (%rsi) (0x) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: colord StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libc.so.6 ?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0 libusb_get_device_list () from /lib/x86_64-linux-gnu/libusb-1.0.so.0 ?? () from /usr/lib/libhpmud.so.0 hpmud_probe_devices () from /usr/lib/libhpmud.so.0 Title: colord crashed with SIGSEGV in libusb_get_device_list() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1016470/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1026520] Re: colord-sane crashed with SIGSEGV in __opendirat()
** Changed in: colord (Ubuntu Quantal) Importance: High = Medium ** Changed in: colord (Ubuntu Quantal) Milestone: None = ubuntu-12.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1026520 Title: colord-sane crashed with SIGSEGV in __opendirat() Status in “colord” package in Ubuntu: Confirmed Status in “colord” source package in Quantal: Confirmed Bug description: happened after upgrade ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: colord 0.1.21-1 ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6 Uname: Linux 3.5.0-4-generic i686 ApportVersion: 2.4-0ubuntu2 Architecture: i386 Date: Thu Jul 19 09:16:09 2012 ExecutablePath: /usr/lib/i386-linux-gnu/colord/colord-sane InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha i386 (20120514) ProcCmdline: /usr/lib/i386-linux-gnu/colord/colord-sane ProcEnviron: SegvAnalysis: Segfault happened at: 0xb734314f:cmpb $0x0,(%edx) PC (0xb734314f) ok source $0x0 ok destination (%edx) (0x) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: colord StacktraceTop: ?? () from /lib/i386-linux-gnu/libc.so.6 opendir () from /lib/i386-linux-gnu/libc.so.6 ?? () from /lib/i386-linux-gnu/libusb-1.0.so.0 libusb_get_device_list () from /lib/i386-linux-gnu/libusb-1.0.so.0 ?? () from /usr/lib/libhpmud.so.0 Title: colord-sane crashed with SIGSEGV in opendir() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1026520/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 844286] Re: colord crashed with SIGSEGV in dbus_message_get_reply_serial()
** Changed in: colord (Ubuntu Quantal) Importance: High = Medium ** Changed in: colord (Ubuntu Quantal) Milestone: None = ubuntu-12.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/844286 Title: colord crashed with SIGSEGV in dbus_message_get_reply_serial() Status in “colord” package in Ubuntu: Confirmed Status in “colord” source package in Precise: Confirmed Status in “colord” source package in Quantal: Confirmed Bug description: [Impact] This causes frequent crashes of the colord daemon for some users. For most users, the visible result of this will be an apport popup. For users who have calibrated their monitors, this will unset the calibration, causing the screen colours to change. [Test Case] I'm not able to reproduce this myself. However, this crash (and crashes like it) are pretty much *all* of the colord crash reports for 0.1.16-2 on errors.ubuntu.com. This should cook in -proposed until we're reasonably certain that these crashes no longer show up there. [Regression Potential] Low. The upload adds a single call to dbus_threads_init_default() at the start of main. Given that colord is currently using libdbus without threadsafe support, enabling threadsafe support is unlikely to break anything. There is no explicit synchronisation between the dbus-using threads, so deadlocks are unlikely. The colord daemon is run as an unprivileged user, so even in the incredibly unlikely event that this opens a security hole it's a limited threat. [Development release] This code is split out of the colord daemon in the development release; the same fix applies to colord-sane, however, and will be uploaded shortly. [Original report] crashes at startup ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: colord 0.1.11-1ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4 Uname: Linux 3.0.0-10-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Wed Sep 7 14:06:00 2011 ExecutablePath: /usr/lib/x86_64-linux-gnu/colord/colord InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha amd64 (20110829.2) ProcCmdline: /usr/lib/x86_64-linux-gnu/colord/colord ProcEnviron: SegvAnalysis: Segfault happened at: 0x7f15e33888a5:mov(%r12,%rdx,1),%edx PC (0x7f15e33888a5) ok source (%r12,%rdx,1) (0x017a) not located in a known VMA region (needed readable region)! destination %edx ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: colord StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 dbus_message_get_reply_serial () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 Title: colord crashed with SIGSEGV in dbus_message_get_reply_serial() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: scanner To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/844286/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1049428] Re: Thunderbird 15.0.1 stable update tracking bug
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: thunderbird (Ubuntu Natty) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1049428 Title: Thunderbird 15.0.1 stable update tracking bug Status in “thunderbird” package in Ubuntu: Invalid Status in “thunderbird” source package in Lucid: In Progress Status in “thunderbird” source package in Natty: Confirmed Status in “thunderbird” source package in Oneiric: Confirmed Status in “thunderbird” source package in Precise: Confirmed Bug description: USN information here after release workflow bug, do not touch This upload will address the following issues per http://www.mozilla.org/en-US/thunderbird/15.0.1/releasenotes/: FIXED Stability issues causing crashes when searching emails and forwarding emails (770262, 780908) FIXED Find and replace and some other actions in the compose window were not working correctly (787673) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1049428/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1049428] Re: Thunderbird 15.0.1 stable update tracking bug
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: thunderbird (Ubuntu Precise) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1049428 Title: Thunderbird 15.0.1 stable update tracking bug Status in “thunderbird” package in Ubuntu: Invalid Status in “thunderbird” source package in Lucid: In Progress Status in “thunderbird” source package in Natty: Confirmed Status in “thunderbird” source package in Oneiric: Confirmed Status in “thunderbird” source package in Precise: Confirmed Bug description: USN information here after release workflow bug, do not touch This upload will address the following issues per http://www.mozilla.org/en-US/thunderbird/15.0.1/releasenotes/: FIXED Stability issues causing crashes when searching emails and forwarding emails (770262, 780908) FIXED Find and replace and some other actions in the compose window were not working correctly (787673) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1049428/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1049428] Re: Thunderbird 15.0.1 stable update tracking bug
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: thunderbird (Ubuntu Oneiric) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1049428 Title: Thunderbird 15.0.1 stable update tracking bug Status in “thunderbird” package in Ubuntu: Invalid Status in “thunderbird” source package in Lucid: In Progress Status in “thunderbird” source package in Natty: Confirmed Status in “thunderbird” source package in Oneiric: Confirmed Status in “thunderbird” source package in Precise: Confirmed Bug description: USN information here after release workflow bug, do not touch This upload will address the following issues per http://www.mozilla.org/en-US/thunderbird/15.0.1/releasenotes/: FIXED Stability issues causing crashes when searching emails and forwarding emails (770262, 780908) FIXED Find and replace and some other actions in the compose window were not working correctly (787673) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1049428/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1045661] Re: High CPU usage
According to the mozilla irc #maildev people, 15.0.1 should fix this behaviour. Ubuntu update is being tracked here: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1049428 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1045661 Title: High CPU usage Status in “thunderbird” package in Ubuntu: Confirmed Bug description: Thunderbird CPU usage goes up to 100% and keep it that way after an unknown event. I tried using it in safe mode, but the problem is still there. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: thunderbird 15.0+build1-0ubuntu0.12.04.1 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Uname: Linux 3.2.0-29-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu12 Architecture: amd64 BuildID: 20120827103657 Date: Tue Sep 4 08:44:15 2012 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=hu_HU.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=Safe Mode/Safe Mode (Out of date) SourcePackage: thunderbird UpgradeStatus: Upgraded to precise on 2012-04-26 (130 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1045661/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 995372] Re: switching external monitors impossible
This was working fine until Monday... today when I tried to login my configuration with two monitors will only show them as mirror and will not let me to set another way... here is the error message I get when I try to change it... GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface `org.gnome.SettingsDaemon.XRANDR_2' on object at path /org/gnome/SettingsDaemon/XRANDR -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/995372 Title: switching external monitors impossible Status in “xserver-xorg-video-intel” package in Ubuntu: Confirmed Bug description: after upgrading to 12.04 I've encountered the following problem with gnome3 desktop: I have 2 screens for my laptop (dell xps502z), one at home and one at work. they have different resolutions, and both connected via the mini-displayPort socket (the hdmi socket on this dell doesn't work due to Nvidia Optimus crap). When moving from one monitor to the other, the monitor doesn't get a signal. Opening the display manager shows the screen blackened, and trying to enable it brings about the following error: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface `org.gnome.SettingsDaemon.XRANDR_2' on object at path /org/gnome/SettingsDaemon/XRANDR restarting X11 solves this, but of course means I have to exit any open window, and reconfigure my dual monitor layout each time. this was 100% fine in 11.10. this happens when moving from either screen to the other. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-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 295.40 Thu Apr 5 21:37:00 PDT 2012 GCC version: gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: None Date: Sun May 6 09:44:35 2012 DistUpgraded: 2012-04-26 20:34:17,071 DEBUG enabling apt cron job DistroCodename: precise DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:050e] NVIDIA Corporation GF108 [GeForce GT 540M] [10de:0df4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:050e] InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) MachineType: Dell Inc. Dell System XPS L502X ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic root=UUID=dfe5ec0d-3e6c-49ab-9149-ba8b2c9217f2 ro quiet splash elevator=deadline vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to precise on 2012-04-26 (9 days ago) dmi.bios.date: 02/15/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.asset.tag: Base Board Asset Tag dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA01:bd02/15/2011:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L502X dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.7.6-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu35 version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental 8.0.2-0ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1 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 N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/995372/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1007588] Re: [mouse]: gnome-settings-daemon SIGSEGV in gdk_device_manager_list_devices@plt()
I just got this problem! I can't enable the second monitor as a separete monitor. I only get it as a mirror... :-/ GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface `org.gnome.SettingsDaemon.XRANDR_2' on object at path /org/gnome/SettingsDaemon/XRANDR -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1007588 Title: [mouse]: gnome-settings-daemon SIGSEGV in gdk_device_manager_list_devices@plt() Status in “gnome-settings-daemon” package in Ubuntu: Fix Released Status in “gnome-settings-daemon” source package in Precise: Fix Released Status in “gnome-settings-daemon” source package in Quantal: Fix Released Bug description: [Impact] One of the patch we ship is obviously buggy and lead to stack corruption issues which turned to segfault on quantal, it could lead to other weird bugs on precise [Test Case] None, the issue is an obvious code error which leads to invalid writes, that can turn to random effect depending of what got overwriten. Just test that the update works correctly. [Regression Potential] None, the patch is just increase by 1 the size of a table which was 1 element too short To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1007588/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1050216] [NEW] button-layout should default to Ubuntu's default button layout
Public bug reported: button-layout seems to be defined to ':minimize,maximize,close', while in Ubuntu it should be 'close,minimize,maximize'. This comes into effect as compiz has gtk-window-decorator ported to GSettings. ** Affects: gsettings-desktop-schemas (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1050216 Title: button-layout should default to Ubuntu's default button layout Status in “gsettings-desktop-schemas” package in Ubuntu: New Bug description: button-layout seems to be defined to ':minimize,maximize,close', while in Ubuntu it should be 'close,minimize,maximize'. This comes into effect as compiz has gtk-window-decorator ported to GSettings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1050216/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1050215] [NEW] Greeter is drawn incorrectly in dual screen setup
Public bug reported: The area of the greeter where one chooses the user to login as is incorrectly drawn whenever the greeter switches from one screen to another. I created a series of photos to illustrate the behaviour. If I choose ANOTHER user, the greeter is redrawn correctly. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: lightdm 1.3.3-0ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-14.16-generic 3.5.3 Uname: Linux 3.5.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 Date: Thu Sep 13 08:27:57 2012 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: Upgraded to quantal on 2012-09-07 (6 days ago) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug quantal running-unity -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1050215 Title: Greeter is drawn incorrectly in dual screen setup Status in “lightdm” package in Ubuntu: New Bug description: The area of the greeter where one chooses the user to login as is incorrectly drawn whenever the greeter switches from one screen to another. I created a series of photos to illustrate the behaviour. If I choose ANOTHER user, the greeter is redrawn correctly. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: lightdm 1.3.3-0ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-14.16-generic 3.5.3 Uname: Linux 3.5.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 Date: Thu Sep 13 08:27:57 2012 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: Upgraded to quantal on 2012-09-07 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1050215/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1050215] Re: Greeter is drawn incorrectly in dual screen setup
** Attachment added: Greeter on secondary screen (drawn incorrectly) https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1050215/+attachment/3311800/+files/2012-09-13%2008.27.05.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1050215 Title: Greeter is drawn incorrectly in dual screen setup Status in “lightdm” package in Ubuntu: New Bug description: The area of the greeter where one chooses the user to login as is incorrectly drawn whenever the greeter switches from one screen to another. I created a series of photos to illustrate the behaviour. If I choose ANOTHER user, the greeter is redrawn correctly. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: lightdm 1.3.3-0ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-14.16-generic 3.5.3 Uname: Linux 3.5.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 Date: Thu Sep 13 08:27:57 2012 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: Upgraded to quantal on 2012-09-07 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1050215/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1050215] Re: Greeter is drawn incorrectly in dual screen setup
** Attachment added: Greeter on main screen (drawn correctly) https://bugs.launchpad.net/bugs/1050215/+attachment/3311798/+files/2012-09-13%2008.26.58.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1050215 Title: Greeter is drawn incorrectly in dual screen setup Status in “lightdm” package in Ubuntu: New Bug description: The area of the greeter where one chooses the user to login as is incorrectly drawn whenever the greeter switches from one screen to another. I created a series of photos to illustrate the behaviour. If I choose ANOTHER user, the greeter is redrawn correctly. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: lightdm 1.3.3-0ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-14.16-generic 3.5.3 Uname: Linux 3.5.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 Date: Thu Sep 13 08:27:57 2012 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: Upgraded to quantal on 2012-09-07 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1050215/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1050216] Re: button-layout should default to Ubuntu's default button layout
Workaround/fix: gsettings set org.gnome.desktop.wm.preferences button-layout 'close,minimize,maximize:' -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1050216 Title: button-layout should default to Ubuntu's default button layout Status in “gsettings-desktop-schemas” package in Ubuntu: New Bug description: button-layout seems to be defined to ':minimize,maximize,close', while in Ubuntu it should be 'close,minimize,maximize'. This comes into effect as compiz has gtk-window-decorator ported to GSettings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1050216/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1050215] Re: Greeter is drawn incorrectly in dual screen setup
** Attachment added: Changing the user on secondary screen (redrawn correctly) https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1050215/+attachment/3311801/+files/2012-09-13%2008.27.17.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1050215 Title: Greeter is drawn incorrectly in dual screen setup Status in “lightdm” package in Ubuntu: New Bug description: The area of the greeter where one chooses the user to login as is incorrectly drawn whenever the greeter switches from one screen to another. I created a series of photos to illustrate the behaviour. If I choose ANOTHER user, the greeter is redrawn correctly. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: lightdm 1.3.3-0ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-14.16-generic 3.5.3 Uname: Linux 3.5.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 Date: Thu Sep 13 08:27:57 2012 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: Upgraded to quantal on 2012-09-07 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1050215/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1050215] Re: Greeter is drawn incorrectly in dual screen setup
** Attachment added: Switchin to main screen, greeter drawn incorrectly https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1050215/+attachment/3311803/+files/2012-09-13%2008.27.28.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1050215 Title: Greeter is drawn incorrectly in dual screen setup Status in “lightdm” package in Ubuntu: New Bug description: The area of the greeter where one chooses the user to login as is incorrectly drawn whenever the greeter switches from one screen to another. I created a series of photos to illustrate the behaviour. If I choose ANOTHER user, the greeter is redrawn correctly. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: lightdm 1.3.3-0ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-14.16-generic 3.5.3 Uname: Linux 3.5.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 Date: Thu Sep 13 08:27:57 2012 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: Upgraded to quantal on 2012-09-07 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1050215/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1045661] Re: High CPU usage
I can reproduce this issue as well.. CPU usage is very high with 15.0. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1045661 Title: High CPU usage Status in “thunderbird” package in Ubuntu: Confirmed Bug description: Thunderbird CPU usage goes up to 100% and keep it that way after an unknown event. I tried using it in safe mode, but the problem is still there. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: thunderbird 15.0+build1-0ubuntu0.12.04.1 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Uname: Linux 3.2.0-29-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu12 Architecture: amd64 BuildID: 20120827103657 Date: Tue Sep 4 08:44:15 2012 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=hu_HU.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=Safe Mode/Safe Mode (Out of date) SourcePackage: thunderbird UpgradeStatus: Upgraded to precise on 2012-04-26 (130 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1045661/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1050221] Re: submit_review_gtk3.py crashed with SIGSEGV in g_main_context_dispatch()
*** This bug is a duplicate of bug 1048886 *** https://bugs.launchpad.net/bugs/1048886 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1048886, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1050221/+attachment/3311820/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1050221/+attachment/3311822/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1050221/+attachment/3311823/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1050221/+attachment/3311824/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1050221/+attachment/3311825/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1050221/+attachment/3311827/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1050221/+attachment/3311828/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1048886 ** Visibility changed to: Public ** Tags removed: need-i386-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-center in Ubuntu. https://bugs.launchpad.net/bugs/1050221 Title: submit_review_gtk3.py crashed with SIGSEGV in g_main_context_dispatch() Status in “software-center” package in Ubuntu: New Bug description: Hello, i was trying to add comment to software i download it(it was Chromium Web Browser) from Ubuntu Software Center and this bug reporter popup and then i came here My OS 12.10 daily build 32 Bit Thank you :) ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: software-center 5.3.12 ProcVersionSignature: Ubuntu 3.5.0-14.16-generic 3.5.3 Uname: Linux 3.5.0-14-generic i686 ApportVersion: 2.5.1-0ubuntu7 Architecture: i386 Date: Wed Sep 12 23:37:32 2012 ExecutablePath: /usr/share/software-center/submit_review_gtk3.py InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha i386 (20120913) InterpreterPath: /usr/bin/python2.7 PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/share/software-center/submit_review_gtk3.py --pkgname chromium-browser --iconname chromium-browser --parent-xid --version 20.0.1132.47~r144678-0ubuntu5 --origin ubuntu --datadir /usr/share/software-center/ --appname Chromium\ Web\ Browser ProcEnviron: PATH=(custom, no user) LANG=ar_EG.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x80a2f9d: addl $0x1,0x54(%ebp) PC (0x080a2f9d) ok source $0x1 ok destination 0x54(%ebp) (0x0054) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: software-center StacktraceTop: ?? () ?? () ?? () from /usr/lib/python2.7/dist-packages/gi/_glib/_glib.so ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0 Title: submit_review_gtk3.py crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1050221/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1050216] Re: button-layout should default to Ubuntu's default button layout
** Branch linked: lp:~timo-jyrinki/gsettings-desktop- schemas/fix_ubuntu_button_layout -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1050216 Title: button-layout should default to Ubuntu's default button layout Status in “gsettings-desktop-schemas” package in Ubuntu: New Bug description: button-layout seems to be defined to ':minimize,maximize,close', while in Ubuntu it should be 'close,minimize,maximize'. This comes into effect as compiz has gtk-window-decorator ported to GSettings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1050216/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1049225] Re: gedit crashed with signal 5 in _XReply()
I removed the duplicate mark, because the link is dead. ** This bug is no longer a duplicate of private bug 1047431 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1049225 Title: gedit crashed with signal 5 in _XReply() Status in “gedit” package in Ubuntu: Incomplete Bug description: If i want to open a locale File and another out of FileZilla gedit crashed silas@silas-UX31A:~$ gedit (gedit:22767): Gdk-ERROR **: The program 'gedit' received an X Window System error. This probably reflects a bug in the program. The error was 'BadWindow (invalid Window parameter)'. (Details: serial 252 error_code 3 request_code 18 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Trace/Breakpoint ausgelöst (Speicherabzug geschrieben) silas@silas-UX31A:~$ ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: gedit 3.5.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-14.15-generic 3.5.3 Uname: Linux 3.5.0-14-generic x86_64 ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 CrashCounter: 1 Date: Tue Sep 11 17:38:14 2012 ExecutablePath: /usr/bin/gedit InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120729.1) ProcCmdline: gedit /home/username/Downloads/transfer/Unbenanntes\ Dokument Signal: 5 SourcePackage: gedit StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XInternAtom () from /usr/lib/x86_64-linux-gnu/libX11.so.6 gdk_x11_atom_to_xatom_for_display () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gedit crashed with signal 5 in _XReply() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1049225/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1040839] Re: Thunderbird hangs accessing eds on startup
** Changed in: thunderbird (Ubuntu Quantal) Status: Fix Released = Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1040839 Title: Thunderbird hangs accessing eds on startup Status in “thunderbird” package in Ubuntu: Fix Committed Status in “thunderbird-couchdb” package in Ubuntu: Fix Released Status in “thunderbird” source package in Quantal: Fix Committed Status in “thunderbird-couchdb” source package in Quantal: Fix Released Bug description: Thunderbird 15.0~b4+build1-0ubuntu1 always hangs on startup on my 12.10 system. The hang renders thunderbird unusable. This is a recent regression; downgrading to 15.0~b1+build1-0ubuntu1 solves the problem on my machine. The hang is in accessing/initializing libedataserver; see attached stack dump (which has been slightly redacted to hide mail addresses) ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: thunderbird 15.0~b4+build1-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2 Uname: Linux 3.5.0-11-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.5.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steve 2188 F pulseaudio BuildID: 20120820154157 Channel: Unavailable Date: Thu Aug 23 15:13:26 2012 ForcedLayersAccel: False IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1) IpRoute: default via 10.0.1.1 dev wlan0 proto static 10.0.1.0/24 dev wlan0 proto kernel scope link src 10.0.1.121 metric 9 169.254.0.0/16 dev wlan0 scope link metric 1000 MostRecentCrashID: bp-35c21ea2-f9e2-42f3-aded-2d9ea2120823 PrefSources: prefs.js ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=15.0/20120820154157 (In use) RelatedPackageVersions: rhythmbox-mozilla 2.97-1ubuntu3 google-talkplugin 3.2.4.0-1 totem-mozilla 3.4.3-0ubuntu1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no RunningIncompatibleAddons: False SourcePackage: thunderbird SubmittedCrashIDs: bp-35c21ea2-f9e2-42f3-aded-2d9ea2120823 bp-06578412-5f07-4f11-a583-3f4332120123 UpgradeStatus: Upgraded to quantal on 2012-08-07 (16 days ago) dmi.bios.date: 03/05/08 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP31.88Z.0070.B07.0803051658 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F4238BC8 dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 2 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F4238BC8 dmi.modalias: dmi:bvnAppleInc.:bvrMBP31.88Z.0070.B07.0803051658:bd03/05/08:svnAppleInc.:pnMacBookPro3,1:pvr1.0:rvnAppleInc.:rnMac-F4238BC8:rvrPVT:cvnAppleInc.:ct2:cvrMac-F4238BC8: dmi.product.name: MacBookPro3,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1040839/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1021374] Re: colord crashed with SIGSEGV in cd_device_register_object()
This bug was fixed in the package colord - 0.1.21-1ubuntu1 --- colord (0.1.21-1ubuntu1) quantal; urgency=low * Parallel upload of 0.1.21-2 to quantal * debian/patches/also_sanitise_username_for_dbus.patch: - Sanitise username when used as a component of a DBus object path. Fixes crash in cd_device_register_object (Closes: 675852) (LP: #1021374) * debian/patches/fix_colord-sane_dbus_threading.patch: - Initialise libdbus threadsafety in colord-sane. (Probably) fixes multiple crashes from colord-sane in libdbus (LP: #844286). Plausibly fixes other bad colord-sane behaviour, such as 100% CPU usage (Closes: 668325) * debian/rules: * debian/control: - Add dh_autoreconf to pick up the build system changes from fix_colord-sane_dbus_threading.patch and add all the various build-depends required. -- Christopher James Halse Rogers r...@ubuntu.com Wed, 12 Sep 2012 18:28:06 +1000 ** Changed in: colord (Ubuntu Quantal) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1021374 Title: colord crashed with SIGSEGV in cd_device_register_object() Status in Colord: Confirmed Status in “colord” package in Ubuntu: Fix Released Status in “colord” source package in Precise: Confirmed Status in “colord” source package in Quantal: Fix Released Status in “colord” package in Debian: Confirmed Bug description: colord crashed with SIGSEGV in cd_device_register_object() ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: colord 0.1.21-1 ProcVersionSignature: Ubuntu 3.5.0-3.3-generic 3.5.0-rc5 Uname: Linux 3.5.0-3-generic x86_64 ApportVersion: 2.2.5-0ubuntu2 Architecture: amd64 CrashCounter: 1 Date: Thu Jul 5 09:30:50 2012 ExecutablePath: /usr/lib/x86_64-linux-gnu/colord/colord ProcCmdline: /usr/lib/x86_64-linux-gnu/colord/colord ProcEnviron: SegvAnalysis: Segfault happened at: 0x40b1dd cd_device_register_object+157: mov 0x8(%rax),%rbx PC (0x0040b1dd) ok source 0x8(%rax) (0x0008) not located in a known VMA region (needed readable region)! destination %rbx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: colord StacktraceTop: cd_device_register_object () ?? () ?? () ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: colord crashed with SIGSEGV in cd_device_register_object() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/colord/+bug/1021374/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 844286] Re: colord crashed with SIGSEGV in dbus_message_get_reply_serial()
This bug was fixed in the package colord - 0.1.21-1ubuntu1 --- colord (0.1.21-1ubuntu1) quantal; urgency=low * Parallel upload of 0.1.21-2 to quantal * debian/patches/also_sanitise_username_for_dbus.patch: - Sanitise username when used as a component of a DBus object path. Fixes crash in cd_device_register_object (Closes: 675852) (LP: #1021374) * debian/patches/fix_colord-sane_dbus_threading.patch: - Initialise libdbus threadsafety in colord-sane. (Probably) fixes multiple crashes from colord-sane in libdbus (LP: #844286). Plausibly fixes other bad colord-sane behaviour, such as 100% CPU usage (Closes: 668325) * debian/rules: * debian/control: - Add dh_autoreconf to pick up the build system changes from fix_colord-sane_dbus_threading.patch and add all the various build-depends required. -- Christopher James Halse Rogers r...@ubuntu.com Wed, 12 Sep 2012 18:28:06 +1000 ** Changed in: colord (Ubuntu Quantal) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/844286 Title: colord crashed with SIGSEGV in dbus_message_get_reply_serial() Status in “colord” package in Ubuntu: Fix Released Status in “colord” source package in Precise: Confirmed Status in “colord” source package in Quantal: Fix Released Bug description: [Impact] This causes frequent crashes of the colord daemon for some users. For most users, the visible result of this will be an apport popup. For users who have calibrated their monitors, this will unset the calibration, causing the screen colours to change. [Test Case] I'm not able to reproduce this myself. However, this crash (and crashes like it) are pretty much *all* of the colord crash reports for 0.1.16-2 on errors.ubuntu.com. This should cook in -proposed until we're reasonably certain that these crashes no longer show up there. [Regression Potential] Low. The upload adds a single call to dbus_threads_init_default() at the start of main. Given that colord is currently using libdbus without threadsafe support, enabling threadsafe support is unlikely to break anything. There is no explicit synchronisation between the dbus-using threads, so deadlocks are unlikely. The colord daemon is run as an unprivileged user, so even in the incredibly unlikely event that this opens a security hole it's a limited threat. [Development release] This code is split out of the colord daemon in the development release; the same fix applies to colord-sane, however, and will be uploaded shortly. [Original report] crashes at startup ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: colord 0.1.11-1ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4 Uname: Linux 3.0.0-10-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Wed Sep 7 14:06:00 2011 ExecutablePath: /usr/lib/x86_64-linux-gnu/colord/colord InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha amd64 (20110829.2) ProcCmdline: /usr/lib/x86_64-linux-gnu/colord/colord ProcEnviron: SegvAnalysis: Segfault happened at: 0x7f15e33888a5:mov(%r12,%rdx,1),%edx PC (0x7f15e33888a5) ok source (%r12,%rdx,1) (0x017a) not located in a known VMA region (needed readable region)! destination %edx ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: colord StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 dbus_message_get_reply_serial () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 Title: colord crashed with SIGSEGV in dbus_message_get_reply_serial() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: scanner To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/844286/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1050224] Re: telepathy-gabble crashed with SIGSEGV in tp_base_channel_close()
*** This bug is a duplicate of bug 1020317 *** https://bugs.launchpad.net/bugs/1020317 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1020317, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1050224/+attachment/3311833/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1050224/+attachment/3311835/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1050224/+attachment/3311837/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1050224/+attachment/3311838/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1050224/+attachment/3311839/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1050224/+attachment/3311840/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1050224/+attachment/3311841/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1020317 telepathy-gabble crashed with SIGSEGV in tp_base_channel_close() ** Visibility changed to: Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to telepathy-gabble in Ubuntu. https://bugs.launchpad.net/bugs/1050224 Title: telepathy-gabble crashed with SIGSEGV in tp_base_channel_close() Status in “telepathy-gabble” package in Ubuntu: New Bug description: No idea what happened. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: telepathy-gabble 0.16.1-1 ProcVersionSignature: Ubuntu 3.5.0-14.16-generic 3.5.3 Uname: Linux 3.5.0-14-generic x86_64 ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 CheckboxSubmission: 2f383a1679e8525d7196eb2518a1921f CheckboxSystem: bb422ca46d02494cdbc459927a98bc2f CrashCounter: 1 Date: Thu Sep 13 08:46:04 2012 ExecutablePath: /usr/lib/telepathy/telepathy-gabble InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha amd64 (20110817) ProcCmdline: /usr/lib/telepathy/telepathy-gabble SegvAnalysis: Segfault happened at: 0x7f77a818e78e tp_base_channel_close+14: mov (%rdi),%rbp PC (0x7f77a818e78e) ok source (%rdi) (0x742f656c62626167) not located in a known VMA region (needed readable region)! destination %rbp ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: telepathy-gabble StacktraceTop: tp_base_channel_close () from /usr/lib/x86_64-linux-gnu/libtelepathy-glib.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 Title: telepathy-gabble crashed with SIGSEGV in tp_base_channel_close() UpgradeStatus: Upgraded to quantal on 2012-06-27 (77 days ago) UserGroups: adm admin audio cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-gabble/+bug/1050224/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1050216] Re: button-layout should default to Ubuntu's default button layout
** Branch linked: lp:~timo-jyrinki/ubuntu/quantal/gsettings-desktop- schemas/fix_button_layout -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1050216 Title: button-layout should default to Ubuntu's default button layout Status in “gsettings-desktop-schemas” package in Ubuntu: New Bug description: button-layout seems to be defined to ':minimize,maximize,close', while in Ubuntu it should be 'close,minimize,maximize:'. This comes into effect as compiz has gtk-window-decorator ported to GSettings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1050216/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1050216] Re: button-layout should default to Ubuntu's default button layout
** Description changed: button-layout seems to be defined to ':minimize,maximize,close', while - in Ubuntu it should be 'close,minimize,maximize'. This comes into effect - as compiz has gtk-window-decorator ported to GSettings. + in Ubuntu it should be 'close,minimize,maximize:'. This comes into + effect as compiz has gtk-window-decorator ported to GSettings. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1050216 Title: button-layout should default to Ubuntu's default button layout Status in “gsettings-desktop-schemas” package in Ubuntu: Invalid Bug description: button-layout seems to be defined to ':minimize,maximize,close', while in Ubuntu it should be 'close,minimize,maximize:'. This comes into effect as compiz has gtk-window-decorator ported to GSettings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1050216/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1050216] Re: button-layout should default to Ubuntu's default button layout
Found out that I was not having ubuntu-desktop meta-package anymore and therefore also missing ubuntu-default-settings. ** Changed in: gsettings-desktop-schemas (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1050216 Title: button-layout should default to Ubuntu's default button layout Status in “gsettings-desktop-schemas” package in Ubuntu: Invalid Bug description: button-layout seems to be defined to ':minimize,maximize,close', while in Ubuntu it should be 'close,minimize,maximize:'. This comes into effect as compiz has gtk-window-decorator ported to GSettings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1050216/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1050216] Re: button-layout should default to Ubuntu's default button layout
Mirv | anyone trying out compiz 0.9.8.2 will bump into this bug | https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1050216 ubot5 | Ubuntu bug 1050216 in gsettings-desktop-schemas (Ubuntu) button-layout should default to Ubuntu's default button | layout [Undecided,New] Mirv | can be fixed manually by gsettings set org.gnome.desktop.wm.preferences button-layout 'close,minimize,maximize' didrocks | Mirv: the default is 'close,minimize,maximize:' didrocks | what did you test exactly? Mirv | didrocks: ah, should be : in the end? didrocks | Mirv: yeah, but that's the default Mirv | didrocks: it's not after gtk-window-decorator starts using gsettings and the default from gsettings-desktop.schemas Mirv | so if one upgrades to 0.9.8.2 from eg. ppa:timo-jyrinki/compiz-withoutgconf then buttons are on the right side didrocks | Mirv: are you sure you had the default set? Mirv | didrocks: what do you mean, where? the buttons are on the right side also in guest session. didrocks | Mirv: I think your bug is different, the default is already close,minimize,maximize: Mirv | didrocks: it's not in the schema file of gsettins-desktop-schemas didrocks | so maybe compiz is not reading the real value didrocks | Mirv: because it doesn't work like that, we don't sed the schemas didrocks | we have overrides files didrocks | try this: didrocks | gsettings reset org.gnome.desktop.wm.preferences button-layout didrocks | gsettings get org.gnome.desktop.wm.preferences button-layout didrocks | what do you get? Mirv | didrocks: on current quantal version, in guest session, :minimize,maximize,close Mirv | with | https://code.launchpad.net/~timo-jyrinki/ubuntu/quantal/gsettings-desktop-schemas/fix_button_layout/+merge/124106 , | the correct one didrocks | Mirv: do you have /usr/share/glib-2.0/schemas/10_ubuntu-default-settings.gschema.override installed? Mirv | didrocks: no, it does not look so didrocks | Mirv: so, this is your bug, you need to have ubuntu-default-settings installed didrocks | it's a dep of ubuntu-desktop metapackage Mirv | didrocks: ah.. suddenly things start to make sense. at some point I've lost ubuntu-desktop. marking bug as invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1050216 Title: button-layout should default to Ubuntu's default button layout Status in “gsettings-desktop-schemas” package in Ubuntu: Invalid Bug description: button-layout seems to be defined to ':minimize,maximize,close', while in Ubuntu it should be 'close,minimize,maximize:'. This comes into effect as compiz has gtk-window-decorator ported to GSettings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1050216/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1050231] [NEW] Geting errors while moving, deleting and in getting mails
Public bug reported: You have the information, check this. I am not a technical person ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: evolution 2.30.3-1ubuntu7.3 ProcVersionSignature: Ubuntu 2.6.35-32.67-generic 2.6.35.14 Uname: Linux 2.6.35-32-generic i686 Architecture: i386 Date: Thu Sep 13 12:30:26 2012 ExecutablePath: /usr/bin/evolution InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) ProcEnviron: SHELL=/bin/bash LANG=en_US.utf8 SourcePackage: evolution XsessionErrors: (gnome-power-manager:1562): Gtk-WARNING **: A floating object was finalized. This means that someone (polkit-gnome-authentication-agent-1:1627): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed (nm-applet:1626): Gdk-CRITICAL **: IA__gdk_window_thaw_toplevel_updates_libgtk_only: assertion `private-update_and_descendants_freeze_count 0' failed (nautilus:1617): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 maverick -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1050231 Title: Geting errors while moving, deleting and in getting mails Status in “evolution” package in Ubuntu: New Bug description: You have the information, check this. I am not a technical person ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: evolution 2.30.3-1ubuntu7.3 ProcVersionSignature: Ubuntu 2.6.35-32.67-generic 2.6.35.14 Uname: Linux 2.6.35-32-generic i686 Architecture: i386 Date: Thu Sep 13 12:30:26 2012 ExecutablePath: /usr/bin/evolution InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) ProcEnviron: SHELL=/bin/bash LANG=en_US.utf8 SourcePackage: evolution XsessionErrors: (gnome-power-manager:1562): Gtk-WARNING **: A floating object was finalized. This means that someone (polkit-gnome-authentication-agent-1:1627): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed (nm-applet:1626): Gdk-CRITICAL **: IA__gdk_window_thaw_toplevel_updates_libgtk_only: assertion `private-update_and_descendants_freeze_count 0' failed (nautilus:1617): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1050231/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1047368] Re: [feature request] ring chart resource analysis
** Changed in: gnome-system-monitor (Ubuntu) Importance: Undecided = Wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1047368 Title: [feature request] ring chart resource analysis Status in The GNOME System Monitor: Unknown Status in “gnome-system-monitor” package in Ubuntu: Triaged Bug description: After having used Baobab to graphically assess data usage, I have become likened to the idea of a ring chart for analysing resource usage in System Monitor. I am not a great coder but I would like to help make this feature request happen, if there is enough support for the idea. Any advice or feedback is welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-system-monitor/+bug/1047368/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1050231] Re: Geting errors while moving, deleting and in getting mails
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1050231 Title: Geting errors while moving, deleting and in getting mails Status in “evolution” package in Ubuntu: New Bug description: You have the information, check this. I am not a technical person ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: evolution 2.30.3-1ubuntu7.3 ProcVersionSignature: Ubuntu 2.6.35-32.67-generic 2.6.35.14 Uname: Linux 2.6.35-32-generic i686 Architecture: i386 Date: Thu Sep 13 12:30:26 2012 ExecutablePath: /usr/bin/evolution InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) ProcEnviron: SHELL=/bin/bash LANG=en_US.utf8 SourcePackage: evolution XsessionErrors: (gnome-power-manager:1562): Gtk-WARNING **: A floating object was finalized. This means that someone (polkit-gnome-authentication-agent-1:1627): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed (nm-applet:1626): Gdk-CRITICAL **: IA__gdk_window_thaw_toplevel_updates_libgtk_only: assertion `private-update_and_descendants_freeze_count 0' failed (nautilus:1617): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1050231/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1047368] Re: [feature request] ring chart resource analysis
I'm sure there is support for the idea, as there is a 4 years old upstream bug already for this, see https://bugzilla.gnome.org/show_bug.cgi?id=525288. I am sure this would be a valuable contribution to Ubuntu and GNOME, so please work on it, and propose a patch, I will happily review and promote it for inclusion in System Monitor upstream. ** Bug watch added: GNOME Bug Tracker #525288 https://bugzilla.gnome.org/show_bug.cgi?id=525288 ** Changed in: gnome-system-monitor (Ubuntu) Status: New = Triaged ** Also affects: gnome-system-monitor via https://bugzilla.gnome.org/show_bug.cgi?id=525288 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1047368 Title: [feature request] ring chart resource analysis Status in The GNOME System Monitor: Unknown Status in “gnome-system-monitor” package in Ubuntu: Triaged Bug description: After having used Baobab to graphically assess data usage, I have become likened to the idea of a ring chart for analysing resource usage in System Monitor. I am not a great coder but I would like to help make this feature request happen, if there is enough support for the idea. Any advice or feedback is welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-system-monitor/+bug/1047368/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 927168] Re: compiz crashed with SIGSEGV in memmove() from drisw_update_tex_buffer() from dri_set_tex_buffer2() from drisw_bind_tex_image() from __glXBindTexImageEXT() from TfpT
Confirmed in Mesa again. I'm not 100% sure this is only the fault of compiz/decor. I've just reproduced a similar crash with LLVMpipe, but slightly different below drisw_update_tex_buffer. ** Changed in: mesa (Ubuntu Quantal) Status: Invalid = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/927168 Title: compiz crashed with SIGSEGV in memmove() from drisw_update_tex_buffer() from dri_set_tex_buffer2() from drisw_bind_tex_image() from __glXBindTexImageEXT() from TfpTexture::enable() from enableFragmentOperationsAndDrawGeometry() Status in Compiz: Triaged Status in Compiz Core: Confirmed Status in “compiz” package in Ubuntu: Confirmed Status in “mesa” package in Ubuntu: Confirmed Status in “compiz” source package in Quantal: Confirmed Status in “mesa” source package in Quantal: Confirmed Bug description: . ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity 5.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-12.21-generic 3.2.2 Uname: Linux 3.2.0-12-generic i686 ApportVersion: 1.91-0ubuntu1 Architecture: i386 Date: Sun Feb 5 12:47:01 2012 ExecutablePath: /usr/bin/compiz InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha i386 (2029.1) ProcCmdline: compiz ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x558360: movdqu (%eax),%xmm0 PC (0x00558360) ok source (%eax) (0x81577fc0) not located in a known VMA region (needed readable region)! destination %xmm0 ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: unity StacktraceTop: ?? () from /lib/i386-linux-gnu/libc.so.6 ?? () from /usr/lib/i386-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/i386-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/i386-linux-gnu/mesa/libGL.so.1 ?? () from /usr/lib/i386-linux-gnu/mesa/libGL.so.1 Title: compiz crashed with SIGSEGV UpgradeStatus: Upgraded to precise on 2012-02-04 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/927168/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1042506] Re: Info box gets too tall too fast
*** This bug is a duplicate of bug 1028360 *** https://bugs.launchpad.net/bugs/1028360 ** This bug has been marked a duplicate of bug 1028360 Window has double(?) heigh -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zenity in Ubuntu. https://bugs.launchpad.net/bugs/1042506 Title: Info box gets too tall too fast Status in “zenity” package in Ubuntu: Confirmed Bug description: ~$ zenity --version 3.4.0 ~$ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=12.04 DISTRIB_CODENAME=precise DISTRIB_DESCRIPTION=Ubuntu 12.04.1 LTS From what I can tell it appears to be this bug: https://bugzilla.redhat.com/show_bug.cgi?id=754431 Reproduce: zenity --title Fortune --info --text `fortune` You can gradually wach it get bigger with this a=_;i=1;while [ true ];do zenity --info --title $i --text $a;i=$(($i+2));a=$a _;done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zenity/+bug/1042506/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 999899] Re: system monitor 3.4.1 shows incorrect numbers for more than 3.0 GiB/s
** Changed in: gnome-system-monitor (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/999899 Title: system monitor 3.4.1 shows incorrect numbers for more than 3.0 GiB/s Status in The GNOME System Monitor: Fix Released Status in “gnome-system-monitor” package in Ubuntu: Fix Released Bug description: See screenshot attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-system-monitor/+bug/999899/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1042506] Re: Info box gets too tall too fast
*** This bug is a duplicate of bug 1028360 *** https://bugs.launchpad.net/bugs/1028360 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: zenity (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zenity in Ubuntu. https://bugs.launchpad.net/bugs/1042506 Title: Info box gets too tall too fast Status in “zenity” package in Ubuntu: Confirmed Bug description: ~$ zenity --version 3.4.0 ~$ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=12.04 DISTRIB_CODENAME=precise DISTRIB_DESCRIPTION=Ubuntu 12.04.1 LTS From what I can tell it appears to be this bug: https://bugzilla.redhat.com/show_bug.cgi?id=754431 Reproduce: zenity --title Fortune --info --text `fortune` You can gradually wach it get bigger with this a=_;i=1;while [ true ];do zenity --info --title $i --text $a;i=$(($i+2));a=$a _;done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zenity/+bug/1042506/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 992971] Re: libavformat53 Mismatching header version
** Also affects: mplayer (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libav in Ubuntu. https://bugs.launchpad.net/bugs/992971 Title: libavformat53 Mismatching header version Status in “libav” package in Ubuntu: Confirmed Status in “mplayer” package in Ubuntu: Confirmed Bug description: Version details should be in the auto-loaded Apport file. $ mplayer blah_blah.mov MPlayer svn r34540 (Ubuntu), built with gcc-4.6 (C) 2000-2012 MPlayer Team Playing blah_blah.mov. libavformat version 53.21.0 (external) Mismatching header version 53.19.0 libavformat file format detected. [snip] ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libavformat53 4:0.8.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Tue May 1 20:24:45 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libav UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libav/+bug/992971/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 992971] Re: libavformat53 Mismatching header version
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mplayer (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libav in Ubuntu. https://bugs.launchpad.net/bugs/992971 Title: libavformat53 Mismatching header version Status in “libav” package in Ubuntu: Confirmed Status in “mplayer” package in Ubuntu: Confirmed Bug description: Version details should be in the auto-loaded Apport file. $ mplayer blah_blah.mov MPlayer svn r34540 (Ubuntu), built with gcc-4.6 (C) 2000-2012 MPlayer Team Playing blah_blah.mov. libavformat version 53.21.0 (external) Mismatching header version 53.19.0 libavformat file format detected. [snip] ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libavformat53 4:0.8.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Tue May 1 20:24:45 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libav UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libav/+bug/992971/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 984424] Re: Xerox WorkCentre 6015 wrong colors cups 1.5.2
Chris, Gyuris, can you attach the error_log and captured print data files of Fedora and OpenSUSE here. Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/984424 Title: Xerox WorkCentre 6015 wrong colors cups 1.5.2 Status in “cups” package in Ubuntu: Incomplete Bug description: Xerox WorkCentre 6015 Ubuntu 12.04 cups 1.5.2 sends the wrong colors to printer. Works well in Ubuntu 10.04 cups 1.4.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/984424/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 449191] Re: GNOME System Monitor sometimes doesn't follow the memory usage order even if desired
Setting as Invalid as there has been no response in the last month, feel free to reopen after providing a confirmation that the issue still exists in system monitor version 3.4 or above. ** Changed in: gnome-system-monitor (Ubuntu) Status: Incomplete = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/449191 Title: GNOME System Monitor sometimes doesn't follow the memory usage order even if desired Status in The GNOME System Monitor: Expired Status in “gnome-system-monitor” package in Ubuntu: Invalid Bug description: Binary package hint: gnome-system-monitor Sorting processes list by memory usage on Processes tab in System Monitor usually works but after a period of time there are sometimes mistakes that can be corrected only by clicking on a Memory tab twice (first click sorts properly, but in reverse order). Screenshot attached. ProblemType: Bug Architecture: amd64 Date: Mon Oct 12 03:29:55 2009 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 Karmic Koala - Alpha amd64 (20091008) Package: gnome-system-monitor 2.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.31-13.44-generic SourcePackage: gnome-system-monitor Uname: Linux 2.6.31-13-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-system-monitor/+bug/449191/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1021374] Re: colord crashed with SIGSEGV in cd_device_register_object()
** Description changed: + [Impact] + This causes the colord daemon to crash when a user with a username containing characters not in [a..z][A..Z][0..9] logs in. Since we use usernames with a ‘-’ in them in Ubuntu for the guest session (and possibly in Ubiquity?), this is a fairly common crash to hit. + + It results in (among other things) display calibration (either applying + existing profiles, or attempting to generate a new one) failing to work. + + [Test Case] + Log into a guest session. colord will crash, due to the username being guest-$SOMETHING + + [Regression Potential] + Low. If regressions appear, they're likely to be crashes rather than bad behaviour, so they should be obvious. + + [Original report] + crashes at startup + colord crashed with SIGSEGV in cd_device_register_object() ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: colord 0.1.21-1 ProcVersionSignature: Ubuntu 3.5.0-3.3-generic 3.5.0-rc5 Uname: Linux 3.5.0-3-generic x86_64 ApportVersion: 2.2.5-0ubuntu2 Architecture: amd64 CrashCounter: 1 Date: Thu Jul 5 09:30:50 2012 ExecutablePath: /usr/lib/x86_64-linux-gnu/colord/colord ProcCmdline: /usr/lib/x86_64-linux-gnu/colord/colord ProcEnviron: - + SegvAnalysis: - Segfault happened at: 0x40b1dd cd_device_register_object+157: mov 0x8(%rax),%rbx - PC (0x0040b1dd) ok - source 0x8(%rax) (0x0008) not located in a known VMA region (needed readable region)! - destination %rbx ok + Segfault happened at: 0x40b1dd cd_device_register_object+157: mov 0x8(%rax),%rbx + PC (0x0040b1dd) ok + source 0x8(%rax) (0x0008) not located in a known VMA region (needed readable region)! + destination %rbx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: colord StacktraceTop: - cd_device_register_object () - ?? () - ?? () - ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 - g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 + cd_device_register_object () + ?? () + ?? () + ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 + g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: colord crashed with SIGSEGV in cd_device_register_object() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: ** Changed in: colord (Ubuntu Precise) Status: Confirmed = Invalid ** Description changed: - [Impact] - This causes the colord daemon to crash when a user with a username containing characters not in [a..z][A..Z][0..9] logs in. Since we use usernames with a ‘-’ in them in Ubuntu for the guest session (and possibly in Ubiquity?), this is a fairly common crash to hit. - - It results in (among other things) display calibration (either applying - existing profiles, or attempting to generate a new one) failing to work. - - [Test Case] - Log into a guest session. colord will crash, due to the username being guest-$SOMETHING - - [Regression Potential] - Low. If regressions appear, they're likely to be crashes rather than bad behaviour, so they should be obvious. - - [Original report] crashes at startup colord crashed with SIGSEGV in cd_device_register_object() ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: colord 0.1.21-1 ProcVersionSignature: Ubuntu 3.5.0-3.3-generic 3.5.0-rc5 Uname: Linux 3.5.0-3-generic x86_64 ApportVersion: 2.2.5-0ubuntu2 Architecture: amd64 CrashCounter: 1 Date: Thu Jul 5 09:30:50 2012 ExecutablePath: /usr/lib/x86_64-linux-gnu/colord/colord ProcCmdline: /usr/lib/x86_64-linux-gnu/colord/colord ProcEnviron: SegvAnalysis: Segfault happened at: 0x40b1dd cd_device_register_object+157: mov 0x8(%rax),%rbx PC (0x0040b1dd) ok source 0x8(%rax) (0x0008) not located in a known VMA region (needed readable region)! destination %rbx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: colord StacktraceTop: cd_device_register_object () ?? () ?? () ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: colord crashed with SIGSEGV in cd_device_register_object() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1021374 Title: colord crashed with SIGSEGV in cd_device_register_object() Status in Colord: Confirmed Status in “colord” package in Ubuntu: Fix Released Status in “colord” source package in Precise: Invalid Status in “colord” source package in Quantal: Fix Released Status in “colord” package in Debian: Confirmed Bug description: crashes at startup colord crashed with SIGSEGV in cd_device_register_object() ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: colord 0.1.21-1 ProcVersionSignature: Ubuntu 3.5.0-3.3-generic 3.5.0-rc5
[Desktop-packages] [Bug 980519] Re: Random log off in Ubuntu 12.04 LTS
My system has been rock solid since #124. i7/nvidia 250gtx - dual monitor Thanks for the fix. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/980519 Title: Random log off in Ubuntu 12.04 LTS Status in Unity: Fix Released Status in “nvidia-graphics-drivers” package in Ubuntu: Fix Released Status in “xorg” package in Ubuntu: Fix Released Status in Fedora: New Bug description: I get logged off from Ubuntu sometimes. There is no error message or any indication that it is going to log off. The screen goes black, and after 2-4 seconds, i get presented with the Ubuntu Log On Screen. There is no clear pattern (or at least if have not noticed any). One time i am working with Netbeans, another time i am using firefox. This also means that at present i can not clearly say what package might be causing this behaviour. I am fairly sure the problem lies in 12.04 (or more precise - the combination of 12.04 and the hardware i am using). I do not have the same problem running 11.04 or 11.10. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/980519/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1021374] Re: colord crashed with SIGSEGV in cd_device_register_object()
** Branch linked: lp:ubuntu/colord -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1021374 Title: colord crashed with SIGSEGV in cd_device_register_object() Status in Colord: Confirmed Status in “colord” package in Ubuntu: Fix Released Status in “colord” source package in Precise: Invalid Status in “colord” source package in Quantal: Fix Released Status in “colord” package in Debian: Confirmed Bug description: crashes at startup colord crashed with SIGSEGV in cd_device_register_object() ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: colord 0.1.21-1 ProcVersionSignature: Ubuntu 3.5.0-3.3-generic 3.5.0-rc5 Uname: Linux 3.5.0-3-generic x86_64 ApportVersion: 2.2.5-0ubuntu2 Architecture: amd64 CrashCounter: 1 Date: Thu Jul 5 09:30:50 2012 ExecutablePath: /usr/lib/x86_64-linux-gnu/colord/colord ProcCmdline: /usr/lib/x86_64-linux-gnu/colord/colord ProcEnviron: SegvAnalysis: Segfault happened at: 0x40b1dd cd_device_register_object+157: mov 0x8(%rax),%rbx PC (0x0040b1dd) ok source 0x8(%rax) (0x0008) not located in a known VMA region (needed readable region)! destination %rbx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: colord StacktraceTop: cd_device_register_object () ?? () ?? () ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: colord crashed with SIGSEGV in cd_device_register_object() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/colord/+bug/1021374/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 844286] Re: colord crashed with SIGSEGV in dbus_message_get_reply_serial()
** Branch linked: lp:ubuntu/colord -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/844286 Title: colord crashed with SIGSEGV in dbus_message_get_reply_serial() Status in “colord” package in Ubuntu: Fix Released Status in “colord” source package in Precise: Confirmed Status in “colord” source package in Quantal: Fix Released Bug description: [Impact] This causes frequent crashes of the colord daemon for some users. For most users, the visible result of this will be an apport popup. For users who have calibrated their monitors, this will unset the calibration, causing the screen colours to change. [Test Case] I'm not able to reproduce this myself. However, this crash (and crashes like it) are pretty much *all* of the colord crash reports for 0.1.16-2 on errors.ubuntu.com. This should cook in -proposed until we're reasonably certain that these crashes no longer show up there. [Regression Potential] Low. The upload adds a single call to dbus_threads_init_default() at the start of main. Given that colord is currently using libdbus without threadsafe support, enabling threadsafe support is unlikely to break anything. There is no explicit synchronisation between the dbus-using threads, so deadlocks are unlikely. The colord daemon is run as an unprivileged user, so even in the incredibly unlikely event that this opens a security hole it's a limited threat. [Development release] This code is split out of the colord daemon in the development release; the same fix applies to colord-sane, however, and will be uploaded shortly. [Original report] crashes at startup ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: colord 0.1.11-1ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4 Uname: Linux 3.0.0-10-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Wed Sep 7 14:06:00 2011 ExecutablePath: /usr/lib/x86_64-linux-gnu/colord/colord InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha amd64 (20110829.2) ProcCmdline: /usr/lib/x86_64-linux-gnu/colord/colord ProcEnviron: SegvAnalysis: Segfault happened at: 0x7f15e33888a5:mov(%r12,%rdx,1),%edx PC (0x7f15e33888a5) ok source (%r12,%rdx,1) (0x017a) not located in a known VMA region (needed readable region)! destination %edx ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: colord StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 dbus_message_get_reply_serial () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 Title: colord crashed with SIGSEGV in dbus_message_get_reply_serial() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: scanner To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/844286/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1050242] [NEW] Xorg freeze
Public bug reported: System freeze, while just using Google Chrome on 5-6 websites (including Gmail, no WebGL, no Flash) no CTRL+ALT+F* effect, even ALT+Syst+REISUB does not react. Had to *hard* reboot (5s power button)... Thanks for any help. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-30.48-generic-pae 3.2.27 Uname: Linux 3.2.0-30-generic-pae i686 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 Kernel Module 295.40 Thu Apr 5 21:28:09 PDT 2012 GCC version: gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu13 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,workarounds,scale,expo,ezoom] CompositorRunning: None Date: Thu Sep 13 14:35:55 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu ExtraDebuggingInterest: Yes, GpuHangFrequency: Once a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: NVIDIA Corporation GF119 [Quadro NVS 4200M] [10de:1056] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0494] InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) JockeyStatus: kmod:wl - Broadcom STA wireless driver (Proprietary, Disabled, Not in use) [auto-install] kmod:nvidia_current - nvidia_current (Proprietary, Enabled, Not in use) kmod:nvidia_current_updates - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) MachineType: Dell Inc. Latitude E6520 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-30-generic-pae root=UUID=050c2748-8fe4-4da5-9dfe-4b4c33648a35 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0J4TFW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd05/11/2011:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0J4TFW:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6520 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.7.8-0ubuntu1.4 version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.3+8.0.2-0ubuntu3.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.3+8.0.2-0ubuntu3.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2 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.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug freeze i386 precise ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1050242 Title: Xorg freeze Status in “xorg” package in Ubuntu: New Bug description: System freeze, while just using Google Chrome on 5-6 websites (including Gmail, no WebGL, no Flash) no CTRL+ALT+F* effect, even ALT+Syst+REISUB does not react. Had to *hard* reboot (5s power button)... Thanks for any help. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-30.48-generic-pae 3.2.27 Uname: Linux 3.2.0-30-generic-pae i686 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 Kernel Module 295.40 Thu Apr 5 21:28:09 PDT 2012 GCC version: gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu13 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,workarounds,scale,expo,ezoom] CompositorRunning: None Date: Thu Sep 13 14:35:55 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu ExtraDebuggingInterest: Yes,
[Desktop-packages] [Bug 1050242] Re: Xorg freeze
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1050242 Title: Xorg freeze Status in “xorg” package in Ubuntu: New Bug description: System freeze, while just using Google Chrome on 5-6 websites (including Gmail, no WebGL, no Flash) no CTRL+ALT+F* effect, even ALT+Syst+REISUB does not react. Had to *hard* reboot (5s power button)... Thanks for any help. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-30.48-generic-pae 3.2.27 Uname: Linux 3.2.0-30-generic-pae i686 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 Kernel Module 295.40 Thu Apr 5 21:28:09 PDT 2012 GCC version: gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu13 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,workarounds,scale,expo,ezoom] CompositorRunning: None Date: Thu Sep 13 14:35:55 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu ExtraDebuggingInterest: Yes, GpuHangFrequency: Once a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: NVIDIA Corporation GF119 [Quadro NVS 4200M] [10de:1056] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0494] InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) JockeyStatus: kmod:wl - Broadcom STA wireless driver (Proprietary, Disabled, Not in use) [auto-install] kmod:nvidia_current - nvidia_current (Proprietary, Enabled, Not in use) kmod:nvidia_current_updates - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) MachineType: Dell Inc. Latitude E6520 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-30-generic-pae root=UUID=050c2748-8fe4-4da5-9dfe-4b4c33648a35 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0J4TFW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd05/11/2011:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0J4TFW:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6520 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.7.8-0ubuntu1.4 version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.3+8.0.2-0ubuntu3.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.3+8.0.2-0ubuntu3.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2 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.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1050242/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1050243] [NEW] unable to retype login details on lightdm with userlist disabled
Public bug reported: Its impossible to retype the login details if a mistake during login on lightdm with userlist disabled. I noticed this problem on Xubuntu 12.04. This bug can be reproduced always. I noticed it while trying to setup a laptop image for my institute. We disabled the userlist for lightdm for security purpose so that users would have to manually type in their username. I noticed that if I made a mistake while typing the user credentials (whether in the password or username) the lightdm gives me the username/password incorrect error but it does not provide me the username dialog box so that I can start all over again. What I get instead is a message that asks me to retype the password (which should not be the case because sometimes the mistake was in the username not the password) When this happens the best way to login is either to switch to console mode and restart lightdm, or to reboot the computer completely. I think this is a major bug which will affect many people who use Ubuntu (or in my case xubuntu) in enterprise. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lightdm 1.2.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.2.0-30.48-generic 3.2.27 Uname: Linux 3.2.0-30-generic i686 ApportVersion: 2.0.1-0ubuntu12 Architecture: i386 Date: Thu Sep 13 08:33:50 2012 InstallationMedia: Xubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.lightdm.users.conf: 2012-09-13T08:05:01.783164 ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1050243 Title: unable to retype login details on lightdm with userlist disabled Status in “lightdm” package in Ubuntu: New Bug description: Its impossible to retype the login details if a mistake during login on lightdm with userlist disabled. I noticed this problem on Xubuntu 12.04. This bug can be reproduced always. I noticed it while trying to setup a laptop image for my institute. We disabled the userlist for lightdm for security purpose so that users would have to manually type in their username. I noticed that if I made a mistake while typing the user credentials (whether in the password or username) the lightdm gives me the username/password incorrect error but it does not provide me the username dialog box so that I can start all over again. What I get instead is a message that asks me to retype the password (which should not be the case because sometimes the mistake was in the username not the password) When this happens the best way to login is either to switch to console mode and restart lightdm, or to reboot the computer completely. I think this is a major bug which will affect many people who use Ubuntu (or in my case xubuntu) in enterprise. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lightdm 1.2.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.2.0-30.48-generic 3.2.27 Uname: Linux 3.2.0-30-generic i686 ApportVersion: 2.0.1-0ubuntu12 Architecture: i386 Date: Thu Sep 13 08:33:50 2012 InstallationMedia: Xubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.lightdm.users.conf: 2012-09-13T08:05:01.783164 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1050243/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1050243] Re: unable to retype login details on lightdm with userlist disabled
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1050243 Title: unable to retype login details on lightdm with userlist disabled Status in “lightdm” package in Ubuntu: New Bug description: Its impossible to retype the login details if a mistake during login on lightdm with userlist disabled. I noticed this problem on Xubuntu 12.04. This bug can be reproduced always. I noticed it while trying to setup a laptop image for my institute. We disabled the userlist for lightdm for security purpose so that users would have to manually type in their username. I noticed that if I made a mistake while typing the user credentials (whether in the password or username) the lightdm gives me the username/password incorrect error but it does not provide me the username dialog box so that I can start all over again. What I get instead is a message that asks me to retype the password (which should not be the case because sometimes the mistake was in the username not the password) When this happens the best way to login is either to switch to console mode and restart lightdm, or to reboot the computer completely. I think this is a major bug which will affect many people who use Ubuntu (or in my case xubuntu) in enterprise. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lightdm 1.2.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.2.0-30.48-generic 3.2.27 Uname: Linux 3.2.0-30-generic i686 ApportVersion: 2.0.1-0ubuntu12 Architecture: i386 Date: Thu Sep 13 08:33:50 2012 InstallationMedia: Xubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.lightdm.users.conf: 2012-09-13T08:05:01.783164 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1050243/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1048606] Re: refactor gtk sections from asyncconn for use by print-manager
*** This bug is a duplicate of bug 902762 *** https://bugs.launchpad.net/bugs/902762 Yes, I did this, but based on bug 902762, marking this one as duplicate ... ** This bug has been marked a duplicate of bug 902762 scp-dbus-service.py crashed with ImportError in __main__: No module named asyncconn -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1048606 Title: refactor gtk sections from asyncconn for use by print-manager Status in “system-config-printer” package in Ubuntu: Fix Released Status in “system-config-printer” source package in Quantal: Fix Released Bug description: KDE's new print tool uses /usr/bin/scp-dbus-service which uses asyncconn/asyncipp/asyncpk1 from system-config-printer-gtk, these files need to learn how to cope without gtk around and be moved into system-config-printer-common (then print-manager needs to depend on s-c-p-common) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1048606/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1050243] Re: unable to retype login details on lightdm with userlist disabled
Just want to add that if I typed the right username and only make a mistake in typing the password. The lightdm greeter gives an incorrect password message and continues to give this error until the right password is given. I think this is a serious security flaw. A username should be part of the security of a user, hence it is not ideal for the login manager to give any intruder an idea that the right username has been entered. The normal way is to give a username or password may be incorrect error message and then reset the login screen to allow the user re-enter the login details. I have added an image to better explain the issue ** Attachment added: screenshot https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1050243/+attachment/3311940/+files/IMG_20120913_084825.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1050243 Title: unable to retype login details on lightdm with userlist disabled Status in “lightdm” package in Ubuntu: New Bug description: Its impossible to retype the login details if a mistake during login on lightdm with userlist disabled. I noticed this problem on Xubuntu 12.04. This bug can be reproduced always. I noticed it while trying to setup a laptop image for my institute. We disabled the userlist for lightdm for security purpose so that users would have to manually type in their username. I noticed that if I made a mistake while typing the user credentials (whether in the password or username) the lightdm gives me the username/password incorrect error but it does not provide me the username dialog box so that I can start all over again. What I get instead is a message that asks me to retype the password (which should not be the case because sometimes the mistake was in the username not the password) When this happens the best way to login is either to switch to console mode and restart lightdm, or to reboot the computer completely. I think this is a major bug which will affect many people who use Ubuntu (or in my case xubuntu) in enterprise. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lightdm 1.2.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.2.0-30.48-generic 3.2.27 Uname: Linux 3.2.0-30-generic i686 ApportVersion: 2.0.1-0ubuntu12 Architecture: i386 Date: Thu Sep 13 08:33:50 2012 InstallationMedia: Xubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.lightdm.users.conf: 2012-09-13T08:05:01.783164 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1050243/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 915468] Re: the unity-greeter keyboard's selection doesn't respect the user config
This is still an issue in Ubuntu Precise fully updated.
1) If I use autologin, everything is fine, my keyboard layout is the same as
the system default, En/El.
2) If I use the greeter:
* I only have En available in the greeter,
* I only have En available in the session,
* I don't get a keyboard layout panel applet in the session.
System settings:
alkisg@server:~$ cat /var/lib/AccountsService/users/alkisg
[User]
XSession=ubuntu
XKeyboardLayouts=
Icon=/usr/share/pixmaps/faces/guitar.jpg
alkisg@server:~$ cat .dmrc
[Desktop]
Session=ubuntu
alkisg@server:~$ cat /etc/default/keyboard
# Check /usr/share/doc/keyboard-configuration/README.Debian for
# documentation on what to do after having modified this file.
# The following variables describe your keyboard and can have the same
# values as the XkbModel, XkbLayout, XkbVariant and XkbOptions options
# in /etc/X11/xorg.conf.
XKBMODEL=pc105
XKBLAYOUT=us,gr
XKBVARIANT=,
XKBOPTIONS=grp:alt_shift_toggle,grp_led:scroll
# If you don't want to use the XKB layout on the console, you can
# specify an alternative keymap. Make sure it will be accessible
# before /usr is mounted.
# KMAP=/etc/console-setup/defkeymap.kmap.gz
Result with autologin (no greeter, no problem):
===
alkisg@server:~$ setxkbmap -print
xkb_keymap {
xkb_keycodes { include evdev+aliases(qwerty) };
xkb_types { include complete };
xkb_compat{ include complete+ledscroll(group_lock)};
xkb_symbols { include
pc+us+gr:2+inet(evdev)+group(alt_shift_toggle)};
xkb_geometry { include pc(pc105) };
};
Result with lightdm-greeter (problem):
==
alkisg@server:~$ setxkbmap -print
xkb_keymap {
xkb_keycodes { include evdev+aliases(qwerty) };
xkb_types { include complete };
xkb_compat{ include complete };
xkb_symbols { include pc+us+inet(evdev) };
xkb_geometry { include pc(pc105) };
};
** Changed in: unity-greeter (Ubuntu Precise)
Status: Fix Released = Triaged
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/915468
Title:
the unity-greeter keyboard's selection doesn't respect the user config
Status in “accountsservice” package in Ubuntu:
Fix Released
Status in “gnome-settings-daemon” package in Ubuntu:
Fix Released
Status in “lightdm” package in Ubuntu:
Fix Released
Status in “unity-greeter” package in Ubuntu:
Fix Released
Status in “accountsservice” source package in Precise:
Fix Released
Status in “gnome-settings-daemon” source package in Precise:
Fix Released
Status in “lightdm” source package in Precise:
Fix Released
Status in “unity-greeter” source package in Precise:
Triaged
Bug description:
Using the current trunk from lightdm and unity-greeter, unity-greeter
display a keyboard indicator but default to en where my system and
user .dmrc are set to fr.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/915468/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1045259] Re: Message count wrong in launcher and indicator
I have those as well. This bug happens even if none of the email I receive matches those filters. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1045259 Title: Message count wrong in launcher and indicator Status in “thunderbird” package in Ubuntu: Incomplete Status in “thunderbird” source package in Quantal: Incomplete Bug description: The launcher and indicator menu display a number of unread messages. This is very often (but not always) incorrect. See the attached image for an example. There are no unread messages anywhere in my Thunderbird folders, but the launcher icon shows 199. The indicator menu does the same. There are several bugs with incorrect number being displayed on them. This is different to all of them. Bug 850229 claims to have been fixed in oneiric. This still happens on quantal. Bug 856642 is about the launcher showing too small a number (new as opposed to unread). In this bug the number is shown even if all messages are read. Bug 848774 seems to be consistent. This bug happens quite often but not all the time. Otherwise the descriptions are very similar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1045259/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1011055] Re: Please merge libao from Debian unstable (1.1.0-2)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libao (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libao in Ubuntu. https://bugs.launchpad.net/bugs/1011055 Title: Please merge libao from Debian unstable (1.1.0-2) Status in “libao” package in Ubuntu: Confirmed Bug description: Debian sid has released libao 1.1.0-2 while Ubuntu quantal has libao 1.1.0-1ubuntu2 . The new changes in 1.1.0-2 can be seen at http://packages.debian.org/changelogs/pool/main/liba/libao/libao_1.1.0-2/changelog . Please see http://packages.debian.org/source/sid/libao for more information To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libao/+bug/1011055/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 876105] Re: Remote Desktop Viewer (vinagre) does not remember passwords
Using 64-bit Ubuntu 12.04 LTS with all updates and still same problem - passwords are not saved. But I moved to Remmina too - great tool. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vinagre in Ubuntu. https://bugs.launchpad.net/bugs/876105 Title: Remote Desktop Viewer (vinagre) does not remember passwords Status in “vinagre” package in Ubuntu: Confirmed Bug description: I'm using Vinagre in Ubuntu 11.10 AMD64, and have found that it does not remember passwords (when told to via the Remember this credential checkbox), except when a connection has been established, disconnected, then the Remote - Recent Connections menu is used (without closing Vinagre; after being closed it will not remember the password). Give this a go: (#4 is the only combination that works for remembering passwords) 1. Connect to site - enter password - check Remember this credential - connect. Bookmark site. Close and restart vinagre. Bookmarks - bookmarked site. Password not remembered. 2. Start vinagre. Bookmarks menu - last site. Password not remembered. 3. Start vinagre. Remote menu - Recent Connections - last site. Password not remembered. 4. Connect to site - enter password - check Remember this credential - connect. Click disconnect. Remote menu - Recent Connections - last site. *Password REMEMBERED*. (this is the only case where I've got Vinagre to remember the password) This wasn't a problem in Ubuntu 11.04. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: vinagre 3.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Mon Oct 17 10:02:50 2011 ExecutablePath: /usr/bin/vinagre InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: vinagre UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vinagre/+bug/876105/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1050248] [NEW] obsolete config files of apturl-common left after the lucid 2 precise upgrade
Public bug reported: lucid to precise upgrade : desktop | main | universe arch: i386 | amd64 obsolete config file: apturl-common /etc/firefox-3.0/pref/apturl.js Link to the tests: http://10.98.0.1:8080/view/Precise/view/Upgrade/job/precise-upgrade-lucid-desktop/247/ http://10.98.0.1:8080/view/Precise/view/Upgrade/job/precise-upgrade-lucid-main/235/ http://10.98.0.1:8080/view/Precise/view/Upgrade/job/precise-upgrade-lucid-universe/233/ ** Affects: apturl (Ubuntu) Importance: Undecided Status: New ** Tags: dist-upgrade lucid2precise precise qa-daily-testing ** Package changed: brltty (Ubuntu) = apturl (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1050248 Title: obsolete config files of apturl-common left after the lucid 2 precise upgrade Status in “apturl” package in Ubuntu: New Bug description: lucid to precise upgrade : desktop | main | universe arch: i386 | amd64 obsolete config file: apturl-common /etc/firefox-3.0/pref/apturl.js Link to the tests: http://10.98.0.1:8080/view/Precise/view/Upgrade/job/precise-upgrade-lucid-desktop/247/ http://10.98.0.1:8080/view/Precise/view/Upgrade/job/precise-upgrade-lucid-main/235/ http://10.98.0.1:8080/view/Precise/view/Upgrade/job/precise-upgrade-lucid-universe/233/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apturl/+bug/1050248/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1037774] Re: colord crashed with SIGSEGV in cd_profile_register_object()
** Visibility changed to: Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1037774 Title: colord crashed with SIGSEGV in cd_profile_register_object() Status in “colord” package in Ubuntu: Confirmed Bug description: I did nothing special. Resume from suspend, perhaps. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: colord 0.1.21-1 ProcVersionSignature: Ubuntu 3.5.0-10.10-generic 3.5.1 Uname: Linux 3.5.0-10-generic x86_64 ApportVersion: 2.4-0ubuntu6 Architecture: amd64 CrashCounter: 1 Date: Thu Aug 16 20:12:00 2012 ExecutablePath: /usr/lib/x86_64-linux-gnu/colord/colord InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120627) ProcCmdline: /usr/lib/x86_64-linux-gnu/colord/colord ProcEnviron: SegvAnalysis: Segfault happened at: 0x40ea42 cd_profile_register_object+98: mov 0x8(%rax),%rbx PC (0x0040ea42) ok source 0x8(%rax) (0x0008) not located in a known VMA region (needed readable region)! destination %rbx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: colord StacktraceTop: cd_profile_register_object () ?? () ?? () ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: colord crashed with SIGSEGV in cd_profile_register_object() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1037774/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1049738] Re: Exception: No schema value for /apps/metacity/general/theme
you are right Jeremy, so should i declare that metacity report as
invalid ?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to metacity in Ubuntu.
https://bugs.launchpad.net/bugs/1049738
Title:
Exception: No schema value for /apps/metacity/general/theme
Status in “metacity” package in Ubuntu:
New
Bug description:
quantal i386 logged as gnome-classic
got lot of garbage while using ubuntu-tweak
Traceback (most recent call last):
File /usr/lib/python2.7/dist-packages/ubuntutweak/factory.py, line 77, in
do_composite_create
reverse=reverse)
File /usr/lib/python2.7/dist-packages/ubuntutweak/gui/widgets.py, line
161, in __init__
self.set_tooltip_text(_('Reset setting to default value: %s') %
self.get_default_value())
File /usr/lib/python2.7/dist-packages/ubuntutweak/gui/widgets.py, line
164, in get_default_value
schema_value = self._setting.get_schema_value()
File
/usr/lib/python2.7/dist-packages/ubuntutweak/settings/gconfsettings.py, line
130, in get_schema_value
raise Exception(No schema value for %s % self.key)
Exception: No schema value for /apps/metacity/general/theme
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: metacity 1:2.34.8-0ubuntu4
Uname: Linux 3.6.0-030600rc5-generic i686
ApportVersion: 2.5.1-0ubuntu7
Architecture: i386
Date: Wed Sep 12 15:21:36 2012
SourcePackage: metacity
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1049738/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1034507] Re: New windows does not have default keyboard layout
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-control-center (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1034507 Title: New windows does not have default keyboard layout Status in “gnome-control-center” package in Ubuntu: Confirmed Bug description: With checked both Alow different layouts for individual windows and New windows use the default layout i get new windows with previous layout. I think default layout is topmost in list? So i have first English (US) next Russian. For instance i'm typing in Russian layout in browser window than open Gedit. In Gedit i still have Russian layout while it must become English now. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-control-center 1:3.4.2-0ubuntu0.4 ProcVersionSignature: Ubuntu 3.2.0-27.43-generic-pae 3.2.21 Uname: Linux 3.2.0-27-generic-pae i686 ApportVersion: 2.0.1-0ubuntu12 Architecture: i386 Date: Wed Aug 8 21:02:38 2012 ExecutablePath: /usr/bin/gnome-control-center InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu3 deja-dup22.0-0ubuntu2 gnome-bluetooth 3.2.2-0ubuntu5 indicator-datetime 0.3.94-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1034507/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1050259] [NEW] obsolete config files of gnome-settings-daemon left after the lucid 2 precise upgrade
You have been subscribed to a public bug: lucid to precise upgrade : desktop | main | universe arch: i386 | amd64 obsolete config file: gnome-settings-daemon /etc/gnome/config/Xaw.ad /etc/gnome/config/Tk.ad /etc/gnome/config/General.ad /etc/gnome/config/Emacs.ad /etc/gnome/config/Motif.ad /etc/gnome/config/Editres.ad Link to the tests: http://10.98.0.1:8080/view/Precise/view/Upgrade/job/precise-upgrade-lucid-desktop/247/ http://10.98.0.1:8080/view/Precise/view/Upgrade/job/precise-upgrade-lucid-main/235/ http://10.98.0.1:8080/view/Precise/view/Upgrade/job/precise-upgrade-lucid-universe/233/ ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: dist-upgrade lucid2precise precise qa-daily-testing -- obsolete config files of gnome-settings-daemon left after the lucid 2 precise upgrade https://bugs.launchpad.net/bugs/1050259 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1050250] Re: file-roller crashed with SIGSEGV in g_simple_async_result_complete()
*** This bug is a duplicate of bug 1036878 *** https://bugs.launchpad.net/bugs/1036878 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1036878, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1050250/+attachment/3311941/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1050250/+attachment/3311943/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1050250/+attachment/3311944/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1050250/+attachment/3311945/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1050250/+attachment/3311946/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1050250/+attachment/3311947/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1050250/+attachment/3311948/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1036878 file-roller crashed with SIGSEGV in dlg_package_installer() ** Visibility changed to: Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1050250 Title: file-roller crashed with SIGSEGV in g_simple_async_result_complete() Status in “file-roller” package in Ubuntu: New Bug description: File-roller crashes when trying to extract a 7z archive without having p7zip installed ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: file-roller 3.5.91-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-14.16-generic 3.5.3 Uname: Linux 3.5.0-14-generic x86_64 ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 Date: Thu Sep 13 10:00:02 2012 ExecutablePath: /usr/bin/file-roller InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64+mac (20120905.2) ProcCmdline: file-roller /media/username/J-Daten/SchoolMessOrganizer.7z ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x4199e3: mov0x20(%rax),%rdi PC (0x004199e3) ok source 0x20(%rax) (0x0020) not located in a known VMA region (needed readable region)! destination %rdi ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: file-roller StacktraceTop: ?? () ?? () ?? () ?? () g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: file-roller crashed with SIGSEGV in g_simple_async_result_complete() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1050250/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 682788] Re: Improve Unity menus
Development stopped, because there are lots of ***disagreements*** between us all. There were three alternatives. [] global menu on [] global menu off [] global menu only on maximized windows We came up with new alternatives. [] mockup 1 [] mockup 2 [] LIM we need to: - vote on the new alternatives / mockups until 100 votes - count votes - ***decide*** the lead alternative The Ubuntu Community must pressure the Ubuntu team a lot to get the lead alternative implemented. By the way, here is my vote: [x] LIM -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/682788 Title: Improve Unity menus Status in Ayatana Design: Fix Committed Status in Compiz: Triaged Status in Unity: Triaged Status in “compiz” package in Ubuntu: Triaged Status in “metacity” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Status in Baltix GNU/Linux: Confirmed Bug description: ===+++ _ ! ALL USERS ! _ +++=== ===+++ READ THIS BEFORE MAKING A COMMENT OR MODIFICATION +++=== IMPORTANT 1: Please don't post any me too message; use the Does this bug affect you? feature you can find a bit above this bug description on Launchpad. IMPORTANT 2: Do not post anything if you haven't read all comments to verify that your point hasn't been made. If you feel tempted to stop reading because there are too many messages, that is a strong indicator that you shouldn't add even more comments. Developers have a tough time to find anything if you post redundant stuff. So please abstain from doing that. = Global menu in general (not only in Unity) is very unergonomic on large screens (see the attached screenshot) because if you have a small window somewhere near the low right corner you have to move the cursor all the way up to to panel to reach the menu. I understand why the global menu was used for the netbook edition (it saves space and most windows are maximized), but since Unity is intended to be for the desktop edition there should be an option to switch to the traditional position of the app menu. It would be welcomed by many desktop users. A commonly suggested solution is: [ ] Global Menu on [ ] Global Menu off [ ] Global Menu only for maximized windows The default is usually suggested as either the first (on) or last (on only for maximized windows). - Desired change: Implement the 'Enhanced Menu' project for 12.10. This project will address the issue described in this bug and also issues described in the duplicates of this bus. Note this is the 'official' bug that tracks the implementation of this project. The following options will be added to 'System Settings/Appearance': --- Menus Location:Global/Local Visibility: Hidden/Always displayed --- To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/682788/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1050259] [NEW] obsolete config files of gnome-settings-daemon left after the lucid 2 precise upgrade
Public bug reported: lucid to precise upgrade : desktop | main | universe arch: i386 | amd64 obsolete config file: gnome-settings-daemon /etc/gnome/config/Xaw.ad /etc/gnome/config/Tk.ad /etc/gnome/config/General.ad /etc/gnome/config/Emacs.ad /etc/gnome/config/Motif.ad /etc/gnome/config/Editres.ad Link to the tests: http://10.98.0.1:8080/view/Precise/view/Upgrade/job/precise-upgrade-lucid-desktop/247/ http://10.98.0.1:8080/view/Precise/view/Upgrade/job/precise-upgrade-lucid-main/235/ http://10.98.0.1:8080/view/Precise/view/Upgrade/job/precise-upgrade-lucid-universe/233/ ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: dist-upgrade lucid2precise precise qa-daily-testing ** Package changed: byobu (Ubuntu) = gnome-settings-daemon (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1050259 Title: obsolete config files of gnome-settings-daemon left after the lucid 2 precise upgrade Status in “gnome-settings-daemon” package in Ubuntu: New Bug description: lucid to precise upgrade : desktop | main | universe arch: i386 | amd64 obsolete config file: gnome-settings-daemon /etc/gnome/config/Xaw.ad /etc/gnome/config/Tk.ad /etc/gnome/config/General.ad /etc/gnome/config/Emacs.ad /etc/gnome/config/Motif.ad /etc/gnome/config/Editres.ad Link to the tests: http://10.98.0.1:8080/view/Precise/view/Upgrade/job/precise-upgrade-lucid-desktop/247/ http://10.98.0.1:8080/view/Precise/view/Upgrade/job/precise-upgrade-lucid-main/235/ http://10.98.0.1:8080/view/Precise/view/Upgrade/job/precise-upgrade-lucid-universe/233/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1050259/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1050261] [NEW] Can't change filename pattern of gnome-screenshot
Public bug reported: In older versions gnome-screenshot just created files named like screenshot-1.png which was fine. But in newer versions it is always named with a long pattern that even includes the time and therefore a : on my system. This makes it impossible to upload the image to several hosts without manually renaming it. So i was looking to change the filename pattern which seams to be impossible without compiling my own version. I would strongly suggest to allow the user to define an own pattern or to avoid any format that includes the : character. ** Affects: gnome-utils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-utils in Ubuntu. https://bugs.launchpad.net/bugs/1050261 Title: Can't change filename pattern of gnome-screenshot Status in “gnome-utils” package in Ubuntu: New Bug description: In older versions gnome-screenshot just created files named like screenshot-1.png which was fine. But in newer versions it is always named with a long pattern that even includes the time and therefore a : on my system. This makes it impossible to upload the image to several hosts without manually renaming it. So i was looking to change the filename pattern which seams to be impossible without compiling my own version. I would strongly suggest to allow the user to define an own pattern or to avoid any format that includes the : character. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-utils/+bug/1050261/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1047839] Re: The sip acconunt didn't remember my password after package update
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: empathy (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1047839 Title: The sip acconunt didn't remember my password after package update Status in “empathy” package in Ubuntu: Confirmed Bug description: Today (08/09/2012) there was a update to all the account-plugins. Everything was fine except for account-plugin-sip that seemed to drop my password from it's settings. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: account-plugin-sip 3.5.91-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-14.15-generic 3.5.3 Uname: Linux 3.5.0-14-generic x86_64 ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 Date: Sat Sep 8 13:48:04 2012 InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120830) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: empathy UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1047839/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 850850] Re: Can't undo accidental declining of ttf-mscorefonts-installer
** Description changed: - wine 1.2.2-0ubuntu7, debconf 1.5.40ubuntu1 + debconf 1.5.40ubuntu1 1. In Ubuntu Software Center, navigate to Wine and start installing it. 2. When the Debconf prompt appears for installing the Microsoft Core Fonts, decline it. 3. When Wine finishes installing, remove it. 4. When Wine finishes uninstalling, install it again. What happens: The second time you install Wine, you don't get the chance to choose whether to install the Microsoft fonts. Debconf shows a window saying If you do not agree to the 'TrueType core fonts for the Web EULA ' license terms you cannot install this software. The installation of this package will be canceled. What should happen: You are asked whether you want to install the fonts, just as you were the first time. + + This problem is not specific to wine: it also occurs with oracle- + java7-installer, for example. + http://www.reddit.com/r/Ubuntu/comments/zqerb/i_accidentally_hit_next_without_clicking_i_agree/ ** Summary changed: - Can't undo accidental declining of ttf-mscorefonts-installer + Can't undo accidental declining of EULA in debconf prompt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-center in Ubuntu. https://bugs.launchpad.net/bugs/850850 Title: Can't undo accidental declining of EULA in debconf prompt Status in “software-center” package in Ubuntu: Confirmed Bug description: debconf 1.5.40ubuntu1 1. In Ubuntu Software Center, navigate to Wine and start installing it. 2. When the Debconf prompt appears for installing the Microsoft Core Fonts, decline it. 3. When Wine finishes installing, remove it. 4. When Wine finishes uninstalling, install it again. What happens: The second time you install Wine, you don't get the chance to choose whether to install the Microsoft fonts. Debconf shows a window saying If you do not agree to the 'TrueType core fonts for the Web EULA ' license terms you cannot install this software. The installation of this package will be canceled. What should happen: You are asked whether you want to install the fonts, just as you were the first time. This problem is not specific to wine: it also occurs with oracle- java7-installer, for example. http://www.reddit.com/r/Ubuntu/comments/zqerb/i_accidentally_hit_next_without_clicking_i_agree/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/850850/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 682788] Re: Improve Unity menus
Disagreement can be solved by having configuration options. Only the default must be agreed upon (or decided by Canonical). If even that is hard, the user could be asked at first login. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/682788 Title: Improve Unity menus Status in Ayatana Design: Fix Committed Status in Compiz: Triaged Status in Unity: Triaged Status in “compiz” package in Ubuntu: Triaged Status in “metacity” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Status in Baltix GNU/Linux: Confirmed Bug description: ===+++ _ ! ALL USERS ! _ +++=== ===+++ READ THIS BEFORE MAKING A COMMENT OR MODIFICATION +++=== IMPORTANT 1: Please don't post any me too message; use the Does this bug affect you? feature you can find a bit above this bug description on Launchpad. IMPORTANT 2: Do not post anything if you haven't read all comments to verify that your point hasn't been made. If you feel tempted to stop reading because there are too many messages, that is a strong indicator that you shouldn't add even more comments. Developers have a tough time to find anything if you post redundant stuff. So please abstain from doing that. = Global menu in general (not only in Unity) is very unergonomic on large screens (see the attached screenshot) because if you have a small window somewhere near the low right corner you have to move the cursor all the way up to to panel to reach the menu. I understand why the global menu was used for the netbook edition (it saves space and most windows are maximized), but since Unity is intended to be for the desktop edition there should be an option to switch to the traditional position of the app menu. It would be welcomed by many desktop users. A commonly suggested solution is: [ ] Global Menu on [ ] Global Menu off [ ] Global Menu only for maximized windows The default is usually suggested as either the first (on) or last (on only for maximized windows). - Desired change: Implement the 'Enhanced Menu' project for 12.10. This project will address the issue described in this bug and also issues described in the duplicates of this bus. Note this is the 'official' bug that tracks the implementation of this project. The following options will be added to 'System Settings/Appearance': --- Menus Location:Global/Local Visibility: Hidden/Always displayed --- To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/682788/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1025897] Re: Ctrl+Alt+0 does not work as advertised
Confirmed. (I'm not using Ubuntu at the moment. If anyone else feels there's a bug here - discoverability, documentation, or just plain not a good idea - feel free to reopen). ** Changed in: metacity (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1025897 Title: Ctrl+Alt+0 does not work as advertised Status in “metacity” package in Ubuntu: Invalid Bug description: I'm using unity-2d. Press alt+space, and I see a window menu. On the right hand side of the menu, it shows keyboard shortcuts - e.g. next to close, it shows Alt+F4. Next to minimize, it shows Ctrl+Alt+0. All the other keyboard shortcuts seem to work ok. (Once you know that Super means the windows key). But pressing Ctrl+Alt+0 doesn't seem to work. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: metacity 1:2.34.1-1ubuntu11 ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19 Uname: Linux 3.2.0-26-generic x86_64 ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Tue Jul 17 22:22:12 2012 ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: metacity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1025897/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 927168] Re: compiz crashed with SIGSEGV in memmove() from drisw_update_tex_buffer() from dri_set_tex_buffer2() from drisw_bind_tex_image() from __glXBindTexImageEXT() from TfpT
smspillaz: Would it make sense to keep the pixmap allocation in the decorator, but move all pixmap frees into the decor plugin? That should ensure any pixmap passed to decor is still valid. Assuming that is the problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/927168 Title: compiz crashed with SIGSEGV in memmove() from drisw_update_tex_buffer() from dri_set_tex_buffer2() from drisw_bind_tex_image() from __glXBindTexImageEXT() from TfpTexture::enable() from enableFragmentOperationsAndDrawGeometry() Status in Compiz: Triaged Status in Compiz Core: Confirmed Status in “compiz” package in Ubuntu: Confirmed Status in “mesa” package in Ubuntu: Confirmed Status in “compiz” source package in Quantal: Confirmed Status in “mesa” source package in Quantal: Confirmed Bug description: . ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity 5.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-12.21-generic 3.2.2 Uname: Linux 3.2.0-12-generic i686 ApportVersion: 1.91-0ubuntu1 Architecture: i386 Date: Sun Feb 5 12:47:01 2012 ExecutablePath: /usr/bin/compiz InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha i386 (2029.1) ProcCmdline: compiz ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x558360: movdqu (%eax),%xmm0 PC (0x00558360) ok source (%eax) (0x81577fc0) not located in a known VMA region (needed readable region)! destination %xmm0 ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: unity StacktraceTop: ?? () from /lib/i386-linux-gnu/libc.so.6 ?? () from /usr/lib/i386-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/i386-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/i386-linux-gnu/mesa/libGL.so.1 ?? () from /usr/lib/i386-linux-gnu/mesa/libGL.so.1 Title: compiz crashed with SIGSEGV UpgradeStatus: Upgraded to precise on 2012-02-04 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/927168/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 980519] Re: Random log off in Ubuntu 12.04 LTS
Don't throw a comment just because you see a crash. The issue with Nvidia have been fixed in the latest nvidia drivers. If you are on fglrx then you are totally facing a different issue, try switching between the drivers and see if that proves of any help to you. me too in this type of bug reports is useless. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/980519 Title: Random log off in Ubuntu 12.04 LTS Status in Unity: Fix Released Status in “nvidia-graphics-drivers” package in Ubuntu: Fix Released Status in “xorg” package in Ubuntu: Fix Released Status in Fedora: New Bug description: I get logged off from Ubuntu sometimes. There is no error message or any indication that it is going to log off. The screen goes black, and after 2-4 seconds, i get presented with the Ubuntu Log On Screen. There is no clear pattern (or at least if have not noticed any). One time i am working with Netbeans, another time i am using firefox. This also means that at present i can not clearly say what package might be causing this behaviour. I am fairly sure the problem lies in 12.04 (or more precise - the combination of 12.04 and the hardware i am using). I do not have the same problem running 11.04 or 11.10. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/980519/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 682788] Re: Improve Unity menus
What I do not understand is that the official design decision has been made by the Ayatana team (John Lea). So I do not see why the disagreements should stop the development. Besides can't the final decision be made after user testing this like in other situations? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/682788 Title: Improve Unity menus Status in Ayatana Design: Fix Committed Status in Compiz: Triaged Status in Unity: Triaged Status in “compiz” package in Ubuntu: Triaged Status in “metacity” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Status in Baltix GNU/Linux: Confirmed Bug description: ===+++ _ ! ALL USERS ! _ +++=== ===+++ READ THIS BEFORE MAKING A COMMENT OR MODIFICATION +++=== IMPORTANT 1: Please don't post any me too message; use the Does this bug affect you? feature you can find a bit above this bug description on Launchpad. IMPORTANT 2: Do not post anything if you haven't read all comments to verify that your point hasn't been made. If you feel tempted to stop reading because there are too many messages, that is a strong indicator that you shouldn't add even more comments. Developers have a tough time to find anything if you post redundant stuff. So please abstain from doing that. = Global menu in general (not only in Unity) is very unergonomic on large screens (see the attached screenshot) because if you have a small window somewhere near the low right corner you have to move the cursor all the way up to to panel to reach the menu. I understand why the global menu was used for the netbook edition (it saves space and most windows are maximized), but since Unity is intended to be for the desktop edition there should be an option to switch to the traditional position of the app menu. It would be welcomed by many desktop users. A commonly suggested solution is: [ ] Global Menu on [ ] Global Menu off [ ] Global Menu only for maximized windows The default is usually suggested as either the first (on) or last (on only for maximized windows). - Desired change: Implement the 'Enhanced Menu' project for 12.10. This project will address the issue described in this bug and also issues described in the duplicates of this bus. Note this is the 'official' bug that tracks the implementation of this project. The following options will be added to 'System Settings/Appearance': --- Menus Location:Global/Local Visibility: Hidden/Always displayed --- To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/682788/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1050281] Re: soffice.bin crashed with SIGSEGV in g_main_context_dispatch()
*** This bug is a duplicate of bug 1042070 *** https://bugs.launchpad.net/bugs/1042070 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1042070, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1050281/+attachment/3312023/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1050281/+attachment/3312025/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1050281/+attachment/3312026/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1050281/+attachment/3312027/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1050281/+attachment/3312028/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1050281/+attachment/3312029/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1050281/+attachment/3312030/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1042070 ** Visibility changed to: Public ** Tags removed: need-i386-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1050281 Title: soffice.bin crashed with SIGSEGV in g_main_context_dispatch() Status in “libreoffice” package in Ubuntu: New Bug description: :( ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: libreoffice-core 1:3.6.1~rc2-1ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-14.16-generic 3.5.3 Uname: Linux 3.5.0-14-generic i686 NonfreeKernelModules: fglrx ApportVersion: 2.5.1-0ubuntu7 Architecture: i386 CheckboxSubmission: 9e7798609bdac4548d4b24ca236698e3 CheckboxSystem: b8f3ec504801f13fc208edb5c785b099 CrashCounter: 1 Date: Thu Sep 13 10:44:49 2012 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --calc --splash-pipe=6 ProcEnviron: PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0xb5943757:mov0x10(%eax),%ecx PC (0xb5943757) ok source 0x10(%eax) (0x0010) not located in a known VMA region (needed readable region)! destination %ecx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: libreoffice StacktraceTop: ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0 Title: soffice.bin crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: Upgraded to quantal on 2012-08-26 (17 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1050281/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 682788] Re: Improve Unity menus
Oh shit, how this simple issue might be so complex? Please provide a way to have local menus for apps like terminals and stop copycat Apple shitty approaches. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/682788 Title: Improve Unity menus Status in Ayatana Design: Fix Committed Status in Compiz: Triaged Status in Unity: Triaged Status in “compiz” package in Ubuntu: Triaged Status in “metacity” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Status in Baltix GNU/Linux: Confirmed Bug description: ===+++ _ ! ALL USERS ! _ +++=== ===+++ READ THIS BEFORE MAKING A COMMENT OR MODIFICATION +++=== IMPORTANT 1: Please don't post any me too message; use the Does this bug affect you? feature you can find a bit above this bug description on Launchpad. IMPORTANT 2: Do not post anything if you haven't read all comments to verify that your point hasn't been made. If you feel tempted to stop reading because there are too many messages, that is a strong indicator that you shouldn't add even more comments. Developers have a tough time to find anything if you post redundant stuff. So please abstain from doing that. = Global menu in general (not only in Unity) is very unergonomic on large screens (see the attached screenshot) because if you have a small window somewhere near the low right corner you have to move the cursor all the way up to to panel to reach the menu. I understand why the global menu was used for the netbook edition (it saves space and most windows are maximized), but since Unity is intended to be for the desktop edition there should be an option to switch to the traditional position of the app menu. It would be welcomed by many desktop users. A commonly suggested solution is: [ ] Global Menu on [ ] Global Menu off [ ] Global Menu only for maximized windows The default is usually suggested as either the first (on) or last (on only for maximized windows). - Desired change: Implement the 'Enhanced Menu' project for 12.10. This project will address the issue described in this bug and also issues described in the duplicates of this bus. Note this is the 'official' bug that tracks the implementation of this project. The following options will be added to 'System Settings/Appearance': --- Menus Location:Global/Local Visibility: Hidden/Always displayed --- To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/682788/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1049277] Re: inkscape crashed with SIGSEGV in Inkscape::Preferences::_getNode()
** Also affects: inkscape Importance: Undecided Status: New ** Changed in: inkscape Importance: Undecided = High ** Tags added: crash -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/1049277 Title: inkscape crashed with SIGSEGV in Inkscape::Preferences::_getNode() Status in Inkscape: A Vector Drawing Tool: New Status in “inkscape” package in Ubuntu: New Bug description: I was drawing something with Draw Bezier curves and straight line, when suddenly, Inkscape closed itself. I am using 12.10 Quantal Quetzal. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: inkscape 0.48.3.1-1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-14.15-generic 3.5.3 Uname: Linux 3.5.0-14-generic i686 ApportVersion: 2.5.1-0ubuntu7 Architecture: i386 Date: Tue Sep 11 19:43:47 2012 ExecutablePath: /usr/bin/inkscape InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha i386 (20120724.2) ProcCmdline: inkscape ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 11 SourcePackage: inkscape StacktraceTop: Inkscape::Preferences::_getNode(Glib::ustring const, bool) () Inkscape::Preferences::_getRawValue(Glib::ustring const, char const*) () Inkscape::Preferences::getEntry(Glib::ustring const) () Inkscape::Preferences::getBool(Glib::ustring const, bool) () ?? () Title: inkscape crashed with SIGSEGV in Inkscape::Preferences::_getNode() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XsessionErrors: (inkscape:17132): GLib-GObject-WARNING **: invalid unclassed pointer in cast to `GtkBin' To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1049277/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1034507] Re: New windows does not have default keyboard layout
*** This bug is a duplicate of bug 622965 *** https://bugs.launchpad.net/bugs/622965 ** This bug has been marked a duplicate of bug 622965 New windows always use active window's layout -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1034507 Title: New windows does not have default keyboard layout Status in “gnome-control-center” package in Ubuntu: Confirmed Bug description: With checked both Alow different layouts for individual windows and New windows use the default layout i get new windows with previous layout. I think default layout is topmost in list? So i have first English (US) next Russian. For instance i'm typing in Russian layout in browser window than open Gedit. In Gedit i still have Russian layout while it must become English now. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-control-center 1:3.4.2-0ubuntu0.4 ProcVersionSignature: Ubuntu 3.2.0-27.43-generic-pae 3.2.21 Uname: Linux 3.2.0-27-generic-pae i686 ApportVersion: 2.0.1-0ubuntu12 Architecture: i386 Date: Wed Aug 8 21:02:38 2012 ExecutablePath: /usr/bin/gnome-control-center InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu3 deja-dup22.0-0ubuntu2 gnome-bluetooth 3.2.2-0ubuntu5 indicator-datetime 0.3.94-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1034507/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1047748] Re: inkscape crashed with SIGSEGV in sp_dtw_color_profile_event()
*** This bug is a duplicate of bug 966441 *** https://bugs.launchpad.net/bugs/966441 ** Visibility changed to: Public ** This bug has been marked a duplicate of bug 966441 inkscape crashed with SIGSEGV in sp_dtw_color_profile_event() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/1047748 Title: inkscape crashed with SIGSEGV in sp_dtw_color_profile_event() Status in “inkscape” package in Ubuntu: New Bug description: Possible duplicate of Bug #102780. Inkscape crashed, but it seemed totally random. I wasn't doing anything unusual in particular, so I'm not sure how useful this bug report is... I'll add more information if it happens again, and I notice any trend. (Feel free to close it if this is not useful.) ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: inkscape 0.48.3.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-30.48-generic 3.2.27 Uname: Linux 3.2.0-30-generic x86_64 ApportVersion: 2.0.1-0ubuntu12 Architecture: amd64 Date: Sat Sep 8 16:59:39 2012 ExecutablePath: /usr/bin/inkscape InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) ProcCmdline: inkscape /home/username/Documents/Work/PhD/AS-regulatory\ proteins/qRT-PCR/120822/MyosinB\\C\ graph.svg SegvAnalysis: Segfault happened at: 0x8ca876: mov0x50(%rax),%rsi PC (0x008ca876) ok source 0x50(%rax) (0x0050) not located in a known VMA region (needed readable region)! destination %rsi ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: inkscape StacktraceTop: ?? () ?? () 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 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 handle_property_change(_GdkScreen*, char const*) () Title: inkscape crashed with SIGSEGV in g_signal_emit_valist() UpgradeStatus: Upgraded to precise on 2012-04-29 (132 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/1047748/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 600039] Re: NVIDIA changes resolution of virtual terminals VT1 thru VT6. Also makes splash screen 640x480
We're closing this bug since there has not been a response from the original reporter. However, the issue still exists please feel free to reopen with the requested information. If you're not the original reporter, we'd prefer you file a new bug report. Some tips: * Report X.org bugs via the command: `ubuntu-bug xorg` * Test against the latest development Ubuntu. http://cdimage.ubuntu.com/daily-live/ Bugs marked as affecting the development version tend to get priority attention. * The `xdiagnose` utility has functionality for enabling debugging and analyzing a few common X problems. * Tag your bugs with the Ubuntu versions you have reproduced the issue in. * See https://wiki.ubuntu.com/X/Reporting for tips on writing good bug reports. ** Changed in: nvidia-graphics-drivers (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/600039 Title: NVIDIA changes resolution of virtual terminals VT1 thru VT6. Also makes splash screen 640x480 Status in “nvidia-graphics-drivers” package in Ubuntu: Expired Bug description: Binary package hint: xorg The installation of the NVIDIA drivers changes the resolution of the boot splash screen and also of the virtual terminals. I need the NVIDIA drivers to provide 3d support unless there is a way to get the noveau drivers to provide the 3d support. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: xorg 1:7.5+5ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic i686 NonfreeKernelModules: nvidia wl Architecture: i386 Date: Tue Jun 29 20:36:55 2010 DkmsStatus: nvidia-current, 195.36.24, 2.6.32-22-generic, i686: installed bcmwl, 5.60.48.36+bdcom, 2.6.32-22-generic, i686: installed bcmwl, 5.60.48.36+bdcom, 2.6.32-21-generic, i686: installed InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) Lsusb: Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP Pavilion dv6000 (RP165UA#ABA) ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=95d00efd-a366-4dcc-8870-af204351517a ro quiet splash ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: xorg Symptom: display dmi.bios.date: 03/09/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.42 dmi.board.name: 30B7 dmi.board.vendor: Quanta dmi.board.version: 65.2C dmi.chassis.type: 10 dmi.chassis.vendor: Quanta dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.42:bd03/09/2009:svnHewlett-Packard:pnHPPaviliondv6000(RP165UA#ABA):pvrRev1:rvnQuanta:rn30B7:rvr65.2C:cvnQuanta:ct10:cvrN/A: dmi.product.name: HP Pavilion dv6000 (RP165UA#ABA) dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard glxinfo: Error: [Errno 2] No such file or directory system: distro: Ubuntu codename: lucid architecture: i686 kernel: 2.6.32-22-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/600039/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1038384] Re: Desktop starts new
We're closing this bug since there has not been a response from the original reporter. However, the issue still exists please feel free to reopen with the requested information. If you're not the original reporter, we'd prefer you file a new bug report. Some tips: * Report X.org bugs via the command: `ubuntu-bug xorg` * Test against the latest development Ubuntu. http://cdimage.ubuntu.com/daily-live/ Bugs marked as affecting the development version tend to get priority attention. * The `xdiagnose` utility has functionality for enabling debugging and analyzing a few common X problems. * Tag your bugs with the Ubuntu versions you have reproduced the issue in. * See https://wiki.ubuntu.com/X/Reporting for tips on writing good bug reports. ** Changed in: xserver-xorg-video-ati (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1038384 Title: Desktop starts new Status in “xserver-xorg-video-ati” package in Ubuntu: Expired Bug description: when i want to view a picture the logon-screen coms again ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Uname: Linux 3.2.0-29-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu12 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz Date: Sat Aug 18 08:54:39 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu DkmsStatus: virtualbox, 4.1.12, 3.2.0-29-generic, x86_64: installed GraphicsCard: Advanced Micro Devices [AMD] nee ATI M64-S [Mobility Radeon X2300] [1002:7188] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 6910p [103c:30c1] InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MachineType: Hewlett-Packard HP Compaq 6910p PccardctlIdent: Socket 0: no product info available Socket 1: no product info available PccardctlStatus: Socket 0: no card Socket 1: no card ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-29-generic root=UUID=18541420-83ea-4a2a-8256-42b495b6aec5 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MCD Ver. F.19 dmi.board.name: 30C1 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 68.36 dmi.chassis.asset.tag: MZ240269JD dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MCDVer.F.19:bd07/06/2010:svnHewlett-Packard:pnHPCompaq6910p:pvrF.19:rvnHewlett-Packard:rn30C1:rvrKBCVersion68.36:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP Compaq 6910p dmi.product.version: F.19 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.7.8-0ubuntu1.4 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.3+8.0.2-0ubuntu3.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.3+8.0.2-0ubuntu3.2 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2 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.1 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/ubuntu/+source/xserver-xorg-video-ati/+bug/1038384/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 955623] Re: keyboard layout is switched to default after window change
*** This bug is a duplicate of bug 885730 *** https://bugs.launchpad.net/bugs/885730 ** This bug has been marked a duplicate of bug 885730 keyboard layout indicator reacts incorrectly -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/955623 Title: keyboard layout is switched to default after window change Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Bug description: At least two keyboard layouts configured. Different keyboard layouts for every application. Let's say en is a default layout (loaded on start-up, in new window...) Sometimes this happens: Window is opened and layout different to default is set. Then switch to another window and work there for a while (no need for typing there). Then come back to the former window and find out that default layout is set which is incorrect. I was not able to find steps to reproduce it since it has never happened after immediate switch of windows. When you just open them and spend a while by switching them waiting for the bug, it won't happen (or at least not for me). Its after some time (few minutes is enough) when it does. I am running xfce now installed over gnome unity. The bug is in unity environment too. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-settings-daemon 3.2.2-0ubuntu2.1 ProcVersionSignature: Ubuntu 3.0.0-16.29-generic 3.0.20 Uname: Linux 3.0.0-16-generic i686 ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Thu Mar 15 01:28:43 2012 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012) 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/955623/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1049839] Re: after some operations, menu entries are disabled
*** This bug is a duplicate of bug 1045372 *** https://bugs.launchpad.net/bugs/1045372 It seems a duplicate of bug #1045372 ** This bug has been marked a duplicate of bug 1045372 libreoffice unity menu bars greyed out after opening any dialog or switching window -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1049839 Title: after some operations, menu entries are disabled Status in “libreoffice” package in Ubuntu: New Bug description: If you for example want to create a pivot table (Data - Pivot Table - Create), many entries in the menu are disabled afterwards. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: libreoffice 1:3.6.1~rc2-1ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-14.16-generic 3.5.3 Uname: Linux 3.5.0-14-generic i686 ApportVersion: 2.5.1-0ubuntu7 Architecture: i386 Date: Wed Sep 12 15:58:47 2012 InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha i386 (20120724.2) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1049839/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1047443] Re: No menubar when open a document in Libreoffice
*** This bug is a duplicate of bug 1045372 *** https://bugs.launchpad.net/bugs/1045372 ** This bug is no longer a duplicate of bug 1047496 Unity menu integration stops working 12.10 Beta 1 ** This bug has been marked a duplicate of bug 1045372 libreoffice unity menu bars greyed out after opening any dialog or switching window -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1047443 Title: No menubar when open a document in Libreoffice Status in “libreoffice” package in Ubuntu: New Bug description: text on the terminal: Fontconfig warning: /usr/lib/libreoffice/share/fonts/truetype/fc_local.conf, line 13: Having multiple family in alias isn't supported and may not works as expected p11-kit: duplicate configured module: gnome-keyring.module: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so When a pop-up window opens (fonts, help, ...), links the title bar become dark and some links may no longer be used. They are before the appearance of the pop-up window. or the menubar don't here. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: libreoffice 1:3.6.1~rc2-1ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3 Uname: Linux 3.5.0-13-generic x86_64 ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 CheckboxSubmission: 66e54d393ca03a77c19a7e5d2298386f CheckboxSystem: 669b662da410063cc918e0f60cf6cddf Date: Fri Sep 7 16:54:22 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to quantal on 2012-09-07 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1047443/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1047496] Re: Unity menu integration stops working 12.10 Beta 1
*** This bug is a duplicate of bug 1045372 *** https://bugs.launchpad.net/bugs/1045372 This seems more to be a duplicate of bug #1045372 ** This bug has been marked a duplicate of bug 1045372 libreoffice unity menu bars greyed out after opening any dialog or switching window -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1047496 Title: Unity menu integration stops working 12.10 Beta 1 Status in “libreoffice” package in Ubuntu: Confirmed Status in “libreoffice” source package in Quantal: Confirmed Bug description: Trying out Libre Office in Quantal and I notice what appears to be a bug in the integration with Unity's menu. An example: 1. start up Writer 2. menu items in Unity menu are generally accessible (for example, Help) 3. insert a table in the empty document page 4. menu items in Unity menu are no longer accessible (for example, Help) I do not have a way to recover normal menu behaviour except to restart the application. We discussed this a bit on ubuntu-qa on 7 September 2012; the following additional comment was offered (I have not verified it): I noticed this issue too on Quantal, not only with tables but any libreoffice menu, like if they can be used only once then almost all the items are disabled. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3 Uname: Linux 3.5.0-13-generic i686 ApportVersion: 2.5.1-0ubuntu7 Architecture: i386 Date: Fri Sep 7 09:08:40 2012 InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha i386 (20120905.2) ProcEnviron: LANGUAGE=en_CA:en TERM=xterm PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1047496/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 976534] Re: Rhythmbox cummulates memory in precise - probably memory leak
I build latest rhythmbox from quantal reps for precise with patches from git which fixes memory leaks. You can install it from my ppa https://launchpad.net/~edgar2705/+archive/my-ppa and test it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/976534 Title: Rhythmbox cummulates memory in precise - probably memory leak Status in The Rhythmbox Music Management Application: Confirmed Status in “rhythmbox” package in Ubuntu: Confirmed Bug description: Rhythmbox memory usage is constantly increasing during long playing - hours. After one day allocates over 1GB of memory and never frees. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: rhythmbox 2.96-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14 Uname: Linux 3.2.0-22-generic i686 NonfreeKernelModules: wl ApportVersion: 2.0-0ubuntu4 Architecture: i386 Date: Sun Apr 8 14:19:34 2012 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) SourcePackage: rhythmbox UpgradeStatus: Upgraded to precise on 2012-02-06 (61 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/rhythmbox/+bug/976534/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1049277] Re: inkscape crashed with SIGSEGV in Inkscape::Preferences::_getNode()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: inkscape (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/1049277 Title: inkscape crashed with SIGSEGV in Inkscape::Preferences::_getNode() Status in Inkscape: A Vector Drawing Tool: New Status in “inkscape” package in Ubuntu: Confirmed Bug description: I was drawing something with Draw Bezier curves and straight line, when suddenly, Inkscape closed itself. I am using 12.10 Quantal Quetzal. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: inkscape 0.48.3.1-1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-14.15-generic 3.5.3 Uname: Linux 3.5.0-14-generic i686 ApportVersion: 2.5.1-0ubuntu7 Architecture: i386 Date: Tue Sep 11 19:43:47 2012 ExecutablePath: /usr/bin/inkscape InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha i386 (20120724.2) ProcCmdline: inkscape ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 11 SourcePackage: inkscape StacktraceTop: Inkscape::Preferences::_getNode(Glib::ustring const, bool) () Inkscape::Preferences::_getRawValue(Glib::ustring const, char const*) () Inkscape::Preferences::getEntry(Glib::ustring const) () Inkscape::Preferences::getBool(Glib::ustring const, bool) () ?? () Title: inkscape crashed with SIGSEGV in Inkscape::Preferences::_getNode() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XsessionErrors: (inkscape:17132): GLib-GObject-WARNING **: invalid unclassed pointer in cast to `GtkBin' To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1049277/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 927168] Re: compiz crashed with SIGSEGV in memmove() from drisw_update_tex_buffer() from dri_set_tex_buffer2() from drisw_bind_tex_image() from __glXBindTexImageEXT() from TfpT
Yes, that will work, however we'll need to be careful about not leaking in the decorator in that case. That will probably involve compiz creating a session window as well for the decorator, which isn't a difficult task -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/927168 Title: compiz crashed with SIGSEGV in memmove() from drisw_update_tex_buffer() from dri_set_tex_buffer2() from drisw_bind_tex_image() from __glXBindTexImageEXT() from TfpTexture::enable() from enableFragmentOperationsAndDrawGeometry() Status in Compiz: Triaged Status in Compiz Core: Confirmed Status in “compiz” package in Ubuntu: Confirmed Status in “mesa” package in Ubuntu: Confirmed Status in “compiz” source package in Quantal: Confirmed Status in “mesa” source package in Quantal: Confirmed Bug description: . ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity 5.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-12.21-generic 3.2.2 Uname: Linux 3.2.0-12-generic i686 ApportVersion: 1.91-0ubuntu1 Architecture: i386 Date: Sun Feb 5 12:47:01 2012 ExecutablePath: /usr/bin/compiz InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha i386 (2029.1) ProcCmdline: compiz ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x558360: movdqu (%eax),%xmm0 PC (0x00558360) ok source (%eax) (0x81577fc0) not located in a known VMA region (needed readable region)! destination %xmm0 ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: unity StacktraceTop: ?? () from /lib/i386-linux-gnu/libc.so.6 ?? () from /usr/lib/i386-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/i386-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/i386-linux-gnu/mesa/libGL.so.1 ?? () from /usr/lib/i386-linux-gnu/mesa/libGL.so.1 Title: compiz crashed with SIGSEGV UpgradeStatus: Upgraded to precise on 2012-02-04 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/927168/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 927168] Re: compiz crashed with SIGSEGV in memmove() from drisw_update_tex_buffer() from dri_set_tex_buffer2() from drisw_bind_tex_image() from __glXBindTexImageEXT() from TfpT
sorry, leaking the pixmap. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/927168 Title: compiz crashed with SIGSEGV in memmove() from drisw_update_tex_buffer() from dri_set_tex_buffer2() from drisw_bind_tex_image() from __glXBindTexImageEXT() from TfpTexture::enable() from enableFragmentOperationsAndDrawGeometry() Status in Compiz: Triaged Status in Compiz Core: Confirmed Status in “compiz” package in Ubuntu: Confirmed Status in “mesa” package in Ubuntu: Confirmed Status in “compiz” source package in Quantal: Confirmed Status in “mesa” source package in Quantal: Confirmed Bug description: . ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity 5.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-12.21-generic 3.2.2 Uname: Linux 3.2.0-12-generic i686 ApportVersion: 1.91-0ubuntu1 Architecture: i386 Date: Sun Feb 5 12:47:01 2012 ExecutablePath: /usr/bin/compiz InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha i386 (2029.1) ProcCmdline: compiz ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x558360: movdqu (%eax),%xmm0 PC (0x00558360) ok source (%eax) (0x81577fc0) not located in a known VMA region (needed readable region)! destination %xmm0 ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: unity StacktraceTop: ?? () from /lib/i386-linux-gnu/libc.so.6 ?? () from /usr/lib/i386-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/i386-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/i386-linux-gnu/mesa/libGL.so.1 ?? () from /usr/lib/i386-linux-gnu/mesa/libGL.so.1 Title: compiz crashed with SIGSEGV UpgradeStatus: Upgraded to precise on 2012-02-04 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/927168/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 817672] Re: indicator-weather crashed with SIGSEGV in dbusmenu_menuitem_get_children()
I'm setting this back to confirmed, since the change to opinion wasn't substantiated. ** Changed in: indicator-weather (Ubuntu) Status: Opinion = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to indicator-weather in Ubuntu. https://bugs.launchpad.net/bugs/817672 Title: indicator-weather crashed with SIGSEGV in dbusmenu_menuitem_get_children() Status in “indicator-weather” package in Ubuntu: Confirmed Bug description: Description: Ubuntu oneiric (development branch) Release: 11.10 indicator-weather: Installed: 11.05.31-0ubuntu1 Candidate: 11.05.31-0ubuntu1 Version table: *** 11.05.31-0ubuntu1 0 500 http://ru.archive.ubuntu.com/ubuntu/ oneiric/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: indicator-weather 11.05.31-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-7.8-generic 3.0.0 Uname: Linux 3.0.0-7-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Thu Jul 28 22:53:44 2011 ExecutablePath: /usr/bin/indicator-weather InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) InterpreterPath: /usr/bin/python2.7 PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/bin/indicator-weather SegvAnalysis: Segfault happened at: 0x7f13836e78e6 dbusmenu_menuitem_get_children+22: cmp%rax,(%rdx) PC (0x7f13836e78e6) ok source %rax ok destination (%rdx) (0x70008) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: indicator-weather StacktraceTop: dbusmenu_menuitem_get_children () from /usr/lib/libdbusmenu-glib.so.4 dbusmenu_menuitem_build_variant () from /usr/lib/libdbusmenu-glib.so.4 dbusmenu_menuitem_build_variant () from /usr/lib/libdbusmenu-glib.so.4 ?? () from /usr/lib/libdbusmenu-glib.so.4 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: indicator-weather crashed with SIGSEGV in dbusmenu_menuitem_get_children() UpgradeStatus: Upgraded to oneiric on 2011-07-27 (1 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-weather/+bug/817672/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1050311] [NEW] playback progress bar gets stuck although song is still playing
Public bug reported: While doing the laptop tests for beta 1, I encountered a weird bug on Rhythmbox's UI. I tried to move the playback forward using the progress bar on the top right, but missed the bar and ended up clicking a little bit too high. The results were: 1) song kept playing as if nothing happened (good since I apparently missed the progress bar click zone), 2) the playback progress bar got stuck at the playback poisition at which I made the click. The song eventually kept going until the end, with the playback progress still stuck somewhere in the middle in the song. See screenshot attached, that displays the invalid playback position although the song playback had already finished. Steps to reproduce this bug: 1) Launch a song with Rhythmbox. Mine was the one contained in the example folder in my home folder. 2) Click the playback progress bar on the top right corner of the UI to move the song forward. That should work as expected. 3) Click again but aim to a position lower or higher than the bar, your pointer should turn into a hand for a fraction of second if the manipulation succeeded. 4) The playback should resume but the progress bar should now be stuck. 5) Restarting the song does not unlock the progress bar, for me I had to correctly register a click on the bar as in step #2 to get the progress bar alive again. Expected behaviour: Not too sure about this one. If correct registration of the progress bar click is assumed to be when one clicks ON the bar itself, then aiming a little too under or upper should not do anything. However, if the registration zone is expected to cover the height of the playback tool bar (i.e. the height of the Pause button), then wherever I click in the progress bar zone should move the progress bar at the right position (i.e. the registered relative x-position of my mouse pointer) and keep the playback and its progress alive. As usual, let me know whether further testing is required. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: rhythmbox 2.97-1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-14.16-generic 3.5.3 Uname: Linux 3.5.0-14-generic x86_64 ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 Date: Thu Sep 13 10:17:22 2012 InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120905.2) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug quantal rhythmbox running-unity -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1050311 Title: playback progress bar gets stuck although song is still playing Status in “rhythmbox” package in Ubuntu: New Bug description: While doing the laptop tests for beta 1, I encountered a weird bug on Rhythmbox's UI. I tried to move the playback forward using the progress bar on the top right, but missed the bar and ended up clicking a little bit too high. The results were: 1) song kept playing as if nothing happened (good since I apparently missed the progress bar click zone), 2) the playback progress bar got stuck at the playback poisition at which I made the click. The song eventually kept going until the end, with the playback progress still stuck somewhere in the middle in the song. See screenshot attached, that displays the invalid playback position although the song playback had already finished. Steps to reproduce this bug: 1) Launch a song with Rhythmbox. Mine was the one contained in the example folder in my home folder. 2) Click the playback progress bar on the top right corner of the UI to move the song forward. That should work as expected. 3) Click again but aim to a position lower or higher than the bar, your pointer should turn into a hand for a fraction of second if the manipulation succeeded. 4) The playback should resume but the progress bar should now be stuck. 5) Restarting the song does not unlock the progress bar, for me I had to correctly register a click on the bar as in step #2 to get the progress bar alive again. Expected behaviour: Not too sure about this one. If correct registration of the progress bar click is assumed to be when one clicks ON the bar itself, then aiming a little too under or upper should not do anything. However, if the registration zone is expected to cover the height of the playback tool bar (i.e. the height of the Pause button), then wherever I click in the progress bar zone should move the progress bar at the right position (i.e. the registered relative x-position of my mouse pointer) and keep the playback and its progress alive. As usual, let me know whether further testing is required. ProblemType: Bug DistroRelease: Ubuntu
[Desktop-packages] [Bug 1050311] Re: playback progress bar gets stuck although song is still playing
** Attachment added: playback_control_problem.png https://bugs.launchpad.net/bugs/1050311/+attachment/3312088/+files/playback_control_problem.png ** Tags added: rhythmbox -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1050311 Title: playback progress bar gets stuck although song is still playing Status in “rhythmbox” package in Ubuntu: New Bug description: While doing the laptop tests for beta 1, I encountered a weird bug on Rhythmbox's UI. I tried to move the playback forward using the progress bar on the top right, but missed the bar and ended up clicking a little bit too high. The results were: 1) song kept playing as if nothing happened (good since I apparently missed the progress bar click zone), 2) the playback progress bar got stuck at the playback poisition at which I made the click. The song eventually kept going until the end, with the playback progress still stuck somewhere in the middle in the song. See screenshot attached, that displays the invalid playback position although the song playback had already finished. Steps to reproduce this bug: 1) Launch a song with Rhythmbox. Mine was the one contained in the example folder in my home folder. 2) Click the playback progress bar on the top right corner of the UI to move the song forward. That should work as expected. 3) Click again but aim to a position lower or higher than the bar, your pointer should turn into a hand for a fraction of second if the manipulation succeeded. 4) The playback should resume but the progress bar should now be stuck. 5) Restarting the song does not unlock the progress bar, for me I had to correctly register a click on the bar as in step #2 to get the progress bar alive again. Expected behaviour: Not too sure about this one. If correct registration of the progress bar click is assumed to be when one clicks ON the bar itself, then aiming a little too under or upper should not do anything. However, if the registration zone is expected to cover the height of the playback tool bar (i.e. the height of the Pause button), then wherever I click in the progress bar zone should move the progress bar at the right position (i.e. the registered relative x-position of my mouse pointer) and keep the playback and its progress alive. As usual, let me know whether further testing is required. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: rhythmbox 2.97-1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-14.16-generic 3.5.3 Uname: Linux 3.5.0-14-generic x86_64 ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 Date: Thu Sep 13 10:17:22 2012 InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120905.2) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1050311/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 969273] Re: Searching for a purchased app results in 3 results for it
** Tags added: ca-escalated
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to software-center in Ubuntu.
https://bugs.launchpad.net/bugs/969273
Title:
Searching for a purchased app results in 3 results for it
Status in “software-center” package in Ubuntu:
In Progress
Bug description:
TEST CASE:
1. use software-center and install at least one purchase (can be a $0
purchase)
2. click on File/Reinstall previous purchases in the menu
3. wait until the list of previous purchases is available
4. click on All Software in the menubar
5. search for the *pkgname* of the purchased app (e.g. vendetta-online)
6. verify that there are three items now in the search results
Original description:
If you purchase an app (say, Braid) or click on reinstall previous
purchases, then search for it from the main screen, you'll see 3
results for it:
1) One will have no icon, will have ratings, and no price
2) One will look normal (icon, ratings, price)
3) One will say (already purchased) and not have a price
Screenshot attached. Happens for other purchased apps too.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: software-center 5.1.13.2
ProcVersionSignature: Ubuntu 3.2.0-20.32-generic-pae 3.2.12
Uname: Linux 3.2.0-20-generic-pae i686
ApportVersion: 2.0-0ubuntu1
Architecture: i386
CheckboxSubmission: 9a284f3f6b4f7829abbe27ad9573a709
CheckboxSystem: 3935143777c965daaa64b51f0134f712
Date: Fri Mar 30 10:33:00 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110422)
PackageArchitecture: all
SoftwareCenterLog: 2012-03-30 10:32:12,713 -
softwarecenter.ui.gtk3.widgets.recommendations - WARNING - Error while
accessing the recommender agent for the details view recommendations:
WARNING:__main__:404: {'status': '404', 'content-length': '56', 'via': '1.1
rec.ubuntu.com', '-content-encoding': 'gzip', 'strict-transport-security':
'max-age=2592000', 'vary': 'Accept-Encoding', 'server': 'Apache/2.2.14
(Ubuntu)', 'etag': '3a2e1651ce93e615205a896a25390a36', 'cache-control':
'max-age=300', 'date': 'Fri, 30 Mar 2012 14:32:12 GMT', 'content-type':
'text/html; charset=utf-8'}
SourcePackage: software-center
UpgradeStatus: Upgraded to precise on 2011-11-05 (145 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/969273/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1050322] Re: colord crashed with SIGSEGV in cd_device_register_object()
*** This bug is a duplicate of bug 1021374 *** https://bugs.launchpad.net/bugs/1021374 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1021374, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1050322/+attachment/3312106/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1050322/+attachment/3312108/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1050322/+attachment/3312109/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1050322/+attachment/3312110/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1050322/+attachment/3312111/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1050322/+attachment/3312112/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1050322/+attachment/3312113/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1021374 colord crashed with SIGSEGV in cd_device_register_object() ** Visibility changed to: Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1050322 Title: colord crashed with SIGSEGV in cd_device_register_object() Status in “colord” package in Ubuntu: New Bug description: it always appears when im browsing ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: colord 0.1.21-1 ProcVersionSignature: Ubuntu 3.5.0-14.16-generic 3.5.3 Uname: Linux 3.5.0-14-generic x86_64 ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 CrashCounter: 1 Date: Tue Sep 11 17:07:12 2012 ExecutablePath: /usr/lib/x86_64-linux-gnu/colord/colord InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) ProcCmdline: /usr/lib/x86_64-linux-gnu/colord/colord ProcEnviron: SegvAnalysis: Segfault happened at: 0x40b1dd cd_device_register_object+157: mov 0x8(%rax),%rbx PC (0x0040b1dd) ok source 0x8(%rax) (0x0008) not located in a known VMA region (needed readable region)! destination %rbx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: colord StacktraceTop: cd_device_register_object () ?? () ?? () ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: colord crashed with SIGSEGV in cd_device_register_object() UpgradeStatus: Upgraded to quantal on 2012-09-07 (5 days ago) UserGroups: scanner To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1050322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1049277] Re: inkscape crashed with SIGSEGV in Inkscape::Preferences::_getNode()
Possibly this is similar to - Bug #937835 “inkscape crashed with SIGSEGV in Inkscape::Preferences::_getNode()” (and Bug #983843 “inkscape crashed with SIGSEGV in Inkscape::Preferences::_getNode()”) a duplicate of - Bug #941317 “inkscape crashed with SIGSEGV in getObject()” https://bugs.launchpad.net/inkscape/+bug/937835 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/1049277 Title: inkscape crashed with SIGSEGV in Inkscape::Preferences::_getNode() Status in Inkscape: A Vector Drawing Tool: New Status in “inkscape” package in Ubuntu: Confirmed Bug description: I was drawing something with Draw Bezier curves and straight line, when suddenly, Inkscape closed itself. I am using 12.10 Quantal Quetzal. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: inkscape 0.48.3.1-1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-14.15-generic 3.5.3 Uname: Linux 3.5.0-14-generic i686 ApportVersion: 2.5.1-0ubuntu7 Architecture: i386 Date: Tue Sep 11 19:43:47 2012 ExecutablePath: /usr/bin/inkscape InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha i386 (20120724.2) ProcCmdline: inkscape ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 11 SourcePackage: inkscape StacktraceTop: Inkscape::Preferences::_getNode(Glib::ustring const, bool) () Inkscape::Preferences::_getRawValue(Glib::ustring const, char const*) () Inkscape::Preferences::getEntry(Glib::ustring const) () Inkscape::Preferences::getBool(Glib::ustring const, bool) () ?? () Title: inkscape crashed with SIGSEGV in Inkscape::Preferences::_getNode() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XsessionErrors: (inkscape:17132): GLib-GObject-WARNING **: invalid unclassed pointer in cast to `GtkBin' To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1049277/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
