[Desktop-packages] [Bug 1426174] [NEW] Messaging Menu integration causes endless imap refresh at high message counts
Public bug reported: The Messaging Menu and Unity Launcher integration 1.3.1 extension causes Thunderbird 31.4.0 to endlessly refresh imap folders as message count nears 10 in a folder. This is not a regression. Yesterday and again today, Google throttled my imap access because of excessive imap requests, which was odd because I only use one machine (ie., no other devices) for that account's email. My usage is somewhat outside the norm in that I subscribe to several high-volume mailings (necessary as a kernel developer) which exceed 2 emails a month. These emails are server-filtered and so appear to be delivered directly to the subscribed folder. There are 23 folders, each for a different mailing list, tagged for update checks (via Folder Properties/General Information/When getting new messages...). These folders are not marked for offline sync and storage. As of today, I have 9 emails in a just single folder and that's after deleting email prior to Oct 1. Yesterday, after Google had disabled my imap access for 2 hrs, I reduced the number of cached connections from 5 to 1 (I had occasionally seen errors about too many imap connections when starting up, at least for the last 2 mos or so). For the last several hours, Thunderbird has almost constantly been refreshing folders. I stopped and restarted Thunderbird several times but the constant refresh continued. So I captured an imap log (122MB within several minutes) and noted what appears to be redundant fetches. For example, -1906690176[7fb48d217580]: considering playing queued url:imap://pe...@hurleysoftware.com@imap.gmail.com:993/select/mailing lists/linux-arm -1906690176[7fb48d217580]: creating protocol instance to play queued url:imap://pe...@hurleysoftware.com@imap.gmail.com:993/select/mailing lists/linux-arm -1906690176[7fb48d217580]: proposed url = mailing lists/linux-arm folder for connection personal/mary has To Wait = FALSE can run = FALSE -1906690176[7fb48d217580]: playing queued url:imap://pe...@hurleysoftware.com@imap.gmail.com:993/select/mailing lists/linux-arm 1766131456[7fb45d732580]: 547f2800:imap.gmail.com:S-personal/mary:ProcessCurrentURL: entering 1766131456[7fb45d732580]: 547f2800:imap.gmail.com:S-personal/mary:ProcessCurrentURL:imap://peter%40hurleysoftware%2e...@imap.gmail.com:993/select%3E/mailing%20lists/linux-arm: = currentUrl 1766131456[7fb45d732580]: 547f2800:imap.gmail.com:S-personal/mary:SendData: 20 select mailing lists/linux-arm 1766131456[7fb45d732580]: ReadNextLine [stream=3ee29f80 nb=83 needmore=0] 1766131456[7fb45d732580]: 547f2800:imap.gmail.com:S-mailing lists/linux-arm:CreateNewLineFromSocket: * FLAGS (\Answered \Flagged \Draft \Deleted \Seen $Phishing $label1 $NotPhishing) 1766131456[7fb45d732580]: ReadNextLine [stream=3ee29f80 nb=117 needmore=0] 1766131456[7fb45d732580]: 547f2800:imap.gmail.com:S-mailing lists/linux-arm:CreateNewLineFromSocket: * OK [PERMANENTFLAGS (\Answered \Flagged \Draft \Deleted \Seen $Phishing $label1 $NotPhishing \*)] Flags permitted. 1766131456[7fb45d732580]: ReadNextLine [stream=3ee29f80 nb=36 needmore=0] 1766131456[7fb45d732580]: 547f2800:imap.gmail.com:S-mailing lists/linux-arm:CreateNewLineFromSocket: * OK [UIDVALIDITY 220] UIDs valid. 1766131456[7fb45d732580]: ReadNextLine [stream=3ee29f80 nb=16 needmore=0] 1766131456[7fb45d732580]: 547f2800:imap.gmail.com:S-mailing lists/linux-arm:CreateNewLineFromSocket: * 30314 EXISTS 1766131456[7fb45d732580]: ReadNextLine [stream=3ee29f80 nb=12 needmore=0] 1766131456[7fb45d732580]: 547f2800:imap.gmail.com:S-mailing lists/linux-arm:CreateNewLineFromSocket: * 0 RECENT 1766131456[7fb45d732580]: ReadNextLine [stream=3ee29f80 nb=42 needmore=0] 1766131456[7fb45d732580]: 547f2800:imap.gmail.com:S-mailing lists/linux-arm:CreateNewLineFromSocket: * OK [UIDNEXT 30319] Predicted next UID. 1766131456[7fb45d732580]: ReadNextLine [stream=3ee29f80 nb=31 needmore=0] 1766131456[7fb45d732580]: 547f2800:imap.gmail.com:S-mailing lists/linux-arm:CreateNewLineFromSocket: * OK [HIGHESTMODSEQ 16017829] 1766131456[7fb45d732580]: ReadNextLine [stream=3ee29f80 nb=76 needmore=0] 1766131456[7fb45d732580]: 547f2800:imap.gmail.com:S-mailing lists/linux-arm:CreateNewLineFromSocket: 20 OK [READ-WRITE] mailing lists/linux-arm selected. (Success) [THROTTLED] 1766131456[7fb45d732580]: 547f2800:imap.gmail.com:S-mailing lists/linux-arm:SendData: 21 getquotaroot mailing lists/linux-arm 1766131456[7fb45d732580]: ReadNextLine [stream=3ee29f80 nb=42 needmore=0] 1766131456[7fb45d732580]: 547f2800:imap.gmail.com:S-mailing lists/linux-arm:CreateNewLineFromSocket: * QUOTAROOT mailing lists/linux-arm 1766131456[7fb45d732580]: ReadNextLine [stream=3ee29f80 nb=39 needmore=0] 1766131456[7fb45d732580]: 547f2800:imap.gmail.com:S-mailing lists/linux-arm:CreateNewLineFromSocket: * QUOTA (STORAGE 1863907 31457280) 1766131456[7fb45d732580]: ReadNextLine [stream=3ee29f80 nb=27 needmore=0] 1766131456[7fb45d732580]: 547f2800:imap.gmail.com:S-mailing
[Desktop-packages] [Bug 1111884]
(In reply to comment #46) I tried to fix this a few months ago but failed. If someone with the right skills and time want to have a look at this problem, I'd be happy to give away a laptop with this chipset. Shipment cost on me. I can prepare a linux installation with sources of the kernel at the regression point. Contact me if you are up to the task. Don't do that. Read here: https://wiki.ubuntu.com/Kernel/KernelBisection If you can follow those Ubuntu-specific instructions, that will narrow down the problem. If you can't follow those instructions, have you filed a Launchpad bug? If so, please post the link or bug # (double-check that it's a public bug or say it's private). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/884 Title: 10de:0611 nouveau fails at suspend/resume - PAGE_NOT_PRESENT Status in The Linux Kernel: Invalid Status in Accelerated Xorg driver for nVidia cards: Confirmed Status in “xserver-xorg-video-nouveau” package in Ubuntu: Triaged Bug description: Happens when resuming from standby. Can be reproduced. Every time. nouveau E[ PFB][:05:00.0] trapped read at 0x002001a020 on channel 0x0001fae9 SEMAPHORE_BG/PFIFO_READ/00 reason: PAGE_NOT_PRESENT nouveau E[ PFB][:05:00.0] trapped write at 0x002001a020 on channel 0x0001fae9 PFIFO/PFIFO_READ/SEMAPHORE reason: PAGE_NOT_PRESENT nouveau E[ PGRAPH][:05:00.0] TRAP_TPDMA_2D - TP 0 - Unknown fault at address 00449b nouveau E[ PGRAPH][:05:00.0] TRAP_TPDMA_2D - TP 0 - e0c: , e18: , e1c: , e20: 0011, e24: 0c03 nouveau E[ PGRAPH][:05:00.0] TRAP nouveau E[ PGRAPH][:05:00.0] ch 2 [0x001fae9000] subc 2 class 0x502d mthd 0x060c data 0x04b0 nouveau E[ PFB][:05:00.0] trapped write at 0x00449b on channel 0x0001fae9 PGRAPH/PROP/DST2D reason: PAGE_NOT_PRESENT nouveau E[ PGRAPH][:05:00.0] magic set 0: nouveau E[ PGRAPH][:05:00.0] 0x00408904: 0x20087701 nouveau E[ PGRAPH][:05:00.0] 0x00408908: 0x00449b00 nouveau E[ PGRAPH][:05:00.0] 0x0040890c: 0x8432 nouveau E[ PGRAPH][:05:00.0] 0x00408910: 0x9b00 nouveau E[ PGRAPH][:05:00.0] TRAP_TEXTURE - TP0: Unhandled ustatus 0x0003 nouveau E[ PGRAPH][:05:00.0] TRAP ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: xserver-xorg-core 2:1.13.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-2.6-generic 3.8.0-rc4 Uname: Linux 3.8.0-2-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.8-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CrashCounter: 1 Date: Thu Jan 31 22:17:49 2013 DistUpgraded: 2013-01-30 03:34:50,679 DEBUG enabling apt cron job DistroCodename: raring DistroVariant: ubuntu ExecutablePath: /usr/bin/Xorg ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G92 [GeForce 8800 GT] [10de:0611] (rev a2) (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:2330] MachineType: System manufacturer System Product Name MarkForUpload: True ProcCmdline: /usr/bin/X :0 -core -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch -background none ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-2-generic root=UUID=615f02d8-8bf1-4c07-bf26-9f8b2230d6d6 ro pcie_aspm=force Signal: 6 SourcePackage: xorg-server StacktraceTop: ?? () from /usr/lib/xorg/modules/libexa.so ?? () from /usr/lib/xorg/modules/libexa.so ?? () from /usr/lib/xorg/modules/libexa.so ?? () from /usr/lib/xorg/modules/libexa.so ?? () from /usr/lib/xorg/modules/libexa.so Title: Xorg crashed with SIGABRT UpgradeStatus: Upgraded to raring on 2013-01-30 (1 days ago) UserGroups: dmi.bios.date: 12/24/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0806 dmi.board.name: P5WD2-Premium dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0806:bd12/24/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WD2-Premium:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.9~daily13.01.25-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.41-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1 version.xserver-xorg-core:
[Desktop-packages] [Bug 1111884]
(In reply to comment #48) (In reply to comment #47) (In reply to comment #46) I tried to fix this a few months ago but failed. If someone with the right skills and time want to have a look at this problem, I'd be happy to give away a laptop with this chipset. Shipment cost on me. I can prepare a linux installation with sources of the kernel at the regression point. Contact me if you are up to the task. Don't do that. Read here: https://wiki.ubuntu.com/Kernel/KernelBisection If you can follow those Ubuntu-specific instructions, that will narrow down the problem. If you can't follow those instructions, have you filed a Launchpad bug? If so, please post the link or bug # (double-check that it's a public bug or say it's private). The problem is already bisected. The commit that introduces the regression switches nv50 to use nvc0's disp implementation. The commit is basically deleting all the nv50 code and changing a few function pointers to use the nvc0 implementation. I tried pin pointing what the problem was (see comment 34) but I was not able to fix the problem. I saw Ben Gamari's bisection log (from 3.7-3.8), but I didn't realize that you had duplicated the bisection; I only saw your bump 4 months later, on 3.13. The OP reported this for a Dell Latitude E6400 with G98; are you running similar hardware? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/884 Title: 10de:0611 nouveau fails at suspend/resume - PAGE_NOT_PRESENT Status in The Linux Kernel: Invalid Status in Accelerated Xorg driver for nVidia cards: Confirmed Status in “xserver-xorg-video-nouveau” package in Ubuntu: Triaged Bug description: Happens when resuming from standby. Can be reproduced. Every time. nouveau E[ PFB][:05:00.0] trapped read at 0x002001a020 on channel 0x0001fae9 SEMAPHORE_BG/PFIFO_READ/00 reason: PAGE_NOT_PRESENT nouveau E[ PFB][:05:00.0] trapped write at 0x002001a020 on channel 0x0001fae9 PFIFO/PFIFO_READ/SEMAPHORE reason: PAGE_NOT_PRESENT nouveau E[ PGRAPH][:05:00.0] TRAP_TPDMA_2D - TP 0 - Unknown fault at address 00449b nouveau E[ PGRAPH][:05:00.0] TRAP_TPDMA_2D - TP 0 - e0c: , e18: , e1c: , e20: 0011, e24: 0c03 nouveau E[ PGRAPH][:05:00.0] TRAP nouveau E[ PGRAPH][:05:00.0] ch 2 [0x001fae9000] subc 2 class 0x502d mthd 0x060c data 0x04b0 nouveau E[ PFB][:05:00.0] trapped write at 0x00449b on channel 0x0001fae9 PGRAPH/PROP/DST2D reason: PAGE_NOT_PRESENT nouveau E[ PGRAPH][:05:00.0] magic set 0: nouveau E[ PGRAPH][:05:00.0] 0x00408904: 0x20087701 nouveau E[ PGRAPH][:05:00.0] 0x00408908: 0x00449b00 nouveau E[ PGRAPH][:05:00.0] 0x0040890c: 0x8432 nouveau E[ PGRAPH][:05:00.0] 0x00408910: 0x9b00 nouveau E[ PGRAPH][:05:00.0] TRAP_TEXTURE - TP0: Unhandled ustatus 0x0003 nouveau E[ PGRAPH][:05:00.0] TRAP ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: xserver-xorg-core 2:1.13.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-2.6-generic 3.8.0-rc4 Uname: Linux 3.8.0-2-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.8-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CrashCounter: 1 Date: Thu Jan 31 22:17:49 2013 DistUpgraded: 2013-01-30 03:34:50,679 DEBUG enabling apt cron job DistroCodename: raring DistroVariant: ubuntu ExecutablePath: /usr/bin/Xorg ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G92 [GeForce 8800 GT] [10de:0611] (rev a2) (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:2330] MachineType: System manufacturer System Product Name MarkForUpload: True ProcCmdline: /usr/bin/X :0 -core -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch -background none ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-2-generic root=UUID=615f02d8-8bf1-4c07-bf26-9f8b2230d6d6 ro pcie_aspm=force Signal: 6 SourcePackage: xorg-server StacktraceTop: ?? () from /usr/lib/xorg/modules/libexa.so ?? () from /usr/lib/xorg/modules/libexa.so ?? () from /usr/lib/xorg/modules/libexa.so ?? () from /usr/lib/xorg/modules/libexa.so ?? () from /usr/lib/xorg/modules/libexa.so Title: Xorg crashed with SIGABRT UpgradeStatus: Upgraded to raring on 2013-01-30 (1 days ago) UserGroups: dmi.bios.date: 12/24/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0806 dmi.board.name: P5WD2-Premium dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version
[Desktop-packages] [Bug 1132045] Re: Xorg crashed with SIGABRT
*** This bug is a duplicate of bug 1033533 *** https://bugs.launchpad.net/bugs/1033533 ** This bug is no longer a duplicate of bug 1130122 Xorg crashed with SIGABRT - exaMemcpyBox ** This bug has been marked a duplicate of bug 1033533 Xorg crashed with SIGABRT: exaMemcpyBox with src=0x0 on nouveau with SW rendering -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1132045 Title: Xorg crashed with SIGABRT Status in “xorg-server” package in Ubuntu: New Bug description: Testing Raring ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: xserver-xorg-core 2:1.13.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-7.15-generic 3.8.0 Uname: Linux 3.8.0-7-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.8-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CrashCounter: 1 CurrentDmesg: [ 17.280254] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Date: Sat Feb 23 10:29:08 2013 Disassembly: = 0x7f42ac596037: Cannot access memory at address 0x7f42ac596037 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu ExecutablePath: /usr/bin/Xorg GraphicsCard: NVIDIA Corporation G92 [GeForce 8800 GT] [10de:0611] (rev a2) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2013-01-25 (29 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130124) MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7360 MarkForUpload: True ProcCmdline: /usr/bin/X :0 -core -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch -background none ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-7-generic root=UUID=21c3c020-ae9c-412e-97a0-44c550370d50 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server Stacktrace: #0 0x7f42ac596037 in ?? () No symbol table info available. Cannot access memory at address 0x7fff2fbdb7c8 StacktraceTop: ?? () ThreadStacktrace: . Thread 1 (LWP 1000): #0 0x7f42ac596037 in ?? () No symbol table info available. Cannot access memory at address 0x7fff2fbdb7c8 Title: Xorg crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 11/11/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.10 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MS-7360 dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.10:bd11/11/2008:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7360:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7360:rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0: dmi.product.name: MS-7360 dmi.product.version: 1.0 dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD version.compiz: compiz 1:0.9.9~daily13.02.19-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.42-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.2-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.6-0ubuntu3 xserver.bootTime: Sat Feb 23 10:31:13 2013 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputAT Translated Set 2 keyboard KEYBOARD, id 8 inputImPS/2 Generic Wheel Mouse MOUSE, id 9 xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.2-0ubuntu2 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1132045/+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 1130122] Re: Xorg crashed with SIGABRT - exaMemcpyBox
*** This bug is a duplicate of bug 1033533 ***
https://bugs.launchpad.net/bugs/1033533
** This bug has been marked a duplicate of bug 1033533
Xorg crashed with SIGABRT: exaMemcpyBox with src=0x0 on nouveau with SW
rendering
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.net/bugs/1130122
Title:
Xorg crashed with SIGABRT - exaMemcpyBox
Status in “xserver-xorg-video-nouveau” package in Ubuntu:
Confirmed
Bug description:
Testing Raring. Suspend works ok. Resume not so much: I get the PC up,
my screen is working but my mouse is almost freeze. Keyboard not
working.
#4 0x7fe492f24f32 in AbortServer () at ../../os/log.c:652
#5 0x7fe492f257cd in FatalError (
f=f@entry=0x7fe492f4f3c8 Caught signal %d (%s). Server aborting\n) at
../../os/log.c:793
args = {{gp_offset = 24, fp_offset = 48, overflow_arg_area =
0x7fff22e86aa0,
reg_save_area = 0x7fff22e869e0}}
args2 = {{gp_offset = 8, fp_offset = 48, overflow_arg_area =
0x7fff22e86aa0,
reg_save_area = 0x7fff22e869e0}}
beenhere = 1
#6 0x7fe492f1dd8e in OsSigHandler (sip=optimized out, signo=11,
unused=optimized out)
at ../../os/osinit.c:146
#7 OsSigHandler (signo=11, sip=optimized out, unused=optimized out) at
../../os/osinit.c:107
#8 signal handler called
#9 __memcpy_ssse3 () at ../sysdeps/x86_64/multiarch/memcpy-ssse3.S:90
#10 0x7fe48e8b885e in memcpy (__len=1488, __src=0x0,
__dest=0x7fe494fee2d0)
at /usr/include/x86_64-linux-gnu/bits/string3.h:51
#11 exaMemcpyBox (pbox=pbox@entry=0x7fff22e86fa0, src=0x0, src_pitch=1536,
dst=0x7fe494fee2d0 X\357\345\220\344\177, dst_pitch=1488,
pPixmap=0x7fe494eee7a0)
at ../../exa/exa_migration_classic.c:59
i = 92
bytes = 1488
#12 0x7fe48e8b8d13 in exaCopyDirty (migrate=migrate@entry=0x7fff22e87000,
pValidDst=0x7fe494eee840, pValidSrc=0x7fe494eee850,
transfer=0x7fe48f718e90 nouveau_exa_upload_to_screen+1776,
fallback_index=fallback_index@entry=1, sync=0x7fe48e8b7790 exaWaitSync)
at ../../exa/exa_migration_classic.c:240
pPixmap = 0x7fe494eee7a0
pExaPixmap = 0x7fe494eee800
CopyReg = {extents = {x1 = 0, y1 = 0, x2 = 372, y2 = 92}, data = 0x0}
save_use_gpu_copy = 1
save_pitch = 1536
pBox = 0x7fff22e86fa0
nbox = 1
access_prepared = 1
need_sync = 0
#13 0x7fe48e8b8f42 in exaCopyDirtyToSys
(migrate=migrate@entry=0x7fff22e87000)
at ../../exa/exa_migration_classic.c:285
pExaScr = 0x7fe494fee2d0
pExaPixmap = 0x0
#14 0x7fe48e8bb52a in exaPrepareAccessReg_mixed (pPixmap=0x7fe494eee7a0,
index=optimized out,
pReg=0x7fff22e870b0) at ../../exa/exa_migration_mixed.c:254
as_dst = 1
pixmaps = {{as_dst = 0, as_src = 1, pPix = 0x7fe494eee7a0, pReg =
0x0}}
pExaPixmap = 0x7fe494eee800
has_gpu_copy = optimized out
success = optimized out
#15 0x7fe48e8c40e0 in ExaCheckCopyNtoN (pSrc=0x7fe494e926a0,
pDst=0x7fe494f12110,
pGC=0x7fe494eb97f0, pbox=0x7fff22e87210, nbox=1, dx=-1551, dy=-100,
reverse=0, upsidedown=0,
bitplane=0, closure=0x0) at ../../exa/exa_unaccel.c:152
pPixmap = optimized out
reg = {extents = {x1 = 0, y1 = 0, x2 = 372, y2 = 92}, data = 0x0}
xoff = -1551
yoff = -100
pExaScr = 0x7fe49378ca90
pExaGC = 0x7fe494eb98c8
#16 0x7fe492ef9445 in miCopyRegion
(pSrcDrawable=pSrcDrawable@entry=0x7fe494e926a0,
pDstDrawable=pDstDrawable@entry=0x7fe494f12110,
pGC=pGC@entry=0x7fe494eb97f0,
pDstRegion=pDstRegion@entry=0x7fff22e87210, dx=dx@entry=-1551,
dy=dy@entry=-100,
copyProc=copyProc@entry=0x7fe48e8bd460 exaCopyNtoN,
bitPlane=bitPlane@entry=0,
closure=closure@entry=0x0) at ../../mi/micopy.c:121
reverse = 0
pbox = 0x7fff22e87210
nbox = 1
#17 0x7fe492ef99e6 in miDoCopy (pSrcDrawable=0x7fe494e926a0,
pDstDrawable=0x7fe494f12110,
pGC=0x7fe494eb97f0, xIn=0, yIn=0, widthSrc=372,
heightSrc=heightSrc@entry=92, xOut=1551,
xOut@entry=0, yOut=100, yOut@entry=0,
copyProc=copyProc@entry=0x7fe48e8bd460 exaCopyNtoN,
bitPlane=bitPlane@entry=0, closure=closure@entry=0x0) at
../../mi/micopy.c:297
prgnSrcClip = 0x0
freeSrcClip = 0
prgnExposed = 0x0
rgnDst = {extents = {x1 = 1551, y1 = 100, x2 = 1923, y2 = 192}, data
= 0x0}
dx = -1551
dy = -100
#18 0x7fe48e8bb636 in exaCopyArea (dsty=0, dstx=0, height=92,
width=optimized out,
srcy=optimized out, srcx=optimized out, pGC=optimized out,
pDstDrawable=optimized out,
pSrcDrawable=optimized out) at ../../exa/exa_accel.c:608
#19 exaCopyArea (pSrcDrawable=optimized out,
[Desktop-packages] [Bug 1033533] Re: Xorg crashed with SIGABRT: exaMemcpyBox with src=0x0 on nouveau with SW rendering
For me, this bug is easily reproducible (happens within 1 min. of user
session start) on xserver-xorg-video-nouveau 1.0.2
My user X session is compiz + classic + upstream gnome-panel + Radiance
theme on NV84.
The stack trace is nearly identical to the original reporter's (I do get
'Failed to idle' or 'Unexpected page flip' at other times but those seem
unrelated to this bug). This bug has been low-priority for me because it
doesn't seem to affect stability.
This bug is _not_ reproducible with ppa:mlankhorst/ppa xserver-xorg-
video-nouveau 1.0.6+spam~quantal2. Let me know if bisect is required.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.net/bugs/1033533
Title:
Xorg crashed with SIGABRT: exaMemcpyBox with src=0x0 on nouveau with
SW rendering
Status in “xserver-xorg-video-nouveau” package in Ubuntu:
Confirmed
Status in “xserver-xorg-video-nouveau” source package in Quantal:
Confirmed
Status in “xserver-xorg-video-nouveau” source package in Raring:
Confirmed
Bug description:
Crash doing memcpy in EXA on nouveau, with software rendering
activated.
#8 signal handler called
No symbol table info available.
#9 __memcpy_sse2 () at ../sysdeps/x86_64/multiarch/../memcpy.S:72
No locals.
#10 0x7f570e63684e in memcpy (__len=23, __src=0x0, __dest=0x7f5713877100)
at /usr/include/x86_64-linux-gnu/bits/string3.h:52
No locals.
#11 exaMemcpyBox (pbox=pbox@entry=0x7fffef000de0, src=0x0, src_pitch=64,
dst=0x7f5713877100 , dst_pitch=24, pPixmap=error reading variable: Unhandled
dwarf expression opcode 0xfa) at ../../exa/exa_migration_classic.c:59
i = 16
cpp = optimized out
bytes = 23
#12 0x7f570e636d03 in exaCopyDirty (migrate=migrate@entry=0x7fffef000e40,
pValidDst=0x7f5713dc3e40, pValidSrc=0x7f5713dc3e50, transfer=0x7f570f28b7f0
nouveau_exa_download_from_screen, fallback_index=fallback_index@entry=1,
sync=0x7f570e635780 exaWaitSync) at ../../exa/exa_migration_classic.c:240
pPixmap = 0x7f5713dc3da0
pExaPixmap = 0x7f5713dc3e00
damage = optimized out
CopyReg = {extents = {x1 = 0, y1 = 0, x2 = 23, y2 = 16}, data = 0x0}
save_use_gpu_copy = 1
save_pitch = 64
pBox = 0x7fffef000de0
nbox = 1
access_prepared = 1
need_sync = 0
#13 0x7f570e636f32 in exaCopyDirtyToSys
(migrate=migrate@entry=0x7fffef000e40) at ../../exa/exa_migration_classic.c:285
pPixmap = optimized out
pExaScr = 0x7f5713877100
pExaPixmap = 0x0
#14 0x7f570e63951a in exaPrepareAccessReg_mixed (pPixmap=0x7f5713dc3da0,
index=optimized out, pReg=0x0) at ../../exa/exa_migration_mixed.c:254
as_dst = 1
pixmaps = {{as_dst = 0, as_src = 1, pPix = 0x7f5713dc3da0, pReg =
0x0}}
pExaPixmap = 0x7f5713dc3e00
has_gpu_copy = optimized out
success = optimized out
[Original Report]
The crash report started immediately after login.
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: xserver-xorg-core 2:1.12.99.902-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-8.8-generic 3.5.0
Uname: Linux 3.5.0-8-generic x86_64
.tmp.unity.support.test.0:
ApportVersion: 2.4-0ubuntu6
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CrashCounter: 1
Date: Sun Aug 5 14:46:44 2012
DistUpgraded: Fresh install
DistroCodename: quantal
DistroVariant: ubuntu
DkmsStatus:
virtualbox, 4.1.18, 3.5.0-6-generic, x86_64: installed
virtualbox, 4.1.18, 3.5.0-8-generic, x86_64: installed
ExecutablePath: /usr/bin/Xorg
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
NVIDIA Corporation C61 [GeForce 6100 nForce 400] [10de:03d2] (rev a2)
(prog-if 00 [VGA controller])
Subsystem: NVIDIA Corporation Device [10de:cb84]
InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120519)
Lsusb:
Bus 001 Device 002: ID 18ec:3399 Arkmicro Technologies Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
ProcCmdline: /usr/bin/X :0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7
-novtswitch -background none
ProcEnviron:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-8-generic
root=UUID=a80eff25-65c3-4db0-adad-31d8ea95823b ro quiet splash vt.handoff=7
Renderer: Software
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
?? () from /lib/x86_64-linux-gnu/libc.so.6
?? () from /usr/lib/xorg/modules/libexa.so
?? () from /usr/lib/xorg/modules/libexa.so
?? () from /usr/lib/xorg/modules/libexa.so
?? () from /usr/lib/xorg/modules/libexa.so
Title: Xorg crashed with SIGABRT
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
[Desktop-packages] [Bug 1091702] Re: upower fails to recognize hid devices with new kernels
Upstreamed. On Sat, 2012-12-29 at 13:11 +, Richard Hughes wrote: On 26 December 2012 18:51, Peter Hurley pe...@hurleysoftware.com wrote: In recent kernels, hiddev* devices now have class usbmisc, rather than usb (see http://www.spinics.net/lists/linux-usb/msg62276.html). This change translates into a change in SUBSYSTEM matching for hiddev* devices. This fix addresses this for recent kernels while retaining existing behavior. For reference, here is an attribute-walk for a CyberPower CPS 1500C on kernel 3.7.0: Applied to master, thanks! Richard. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1091702 Title: upower fails to recognize hid devices with new kernels Status in “upower” package in Ubuntu: New Bug description: In newer kernels, hiddev* devices now have class usbmisc, rather than usb (for reference see http://www.spinics.net/lists/linux- usb/msg62276.html ). Attached is a patch that fixes this without changing existing behavior for older kernels. The patch commit message contains an example attribute-walk on 3.7.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1091702/+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 1094061] [NEW] trivial build products should not be in source package
Public bug reported:
Packaging trivial build products such as shell/cc-shell-marshal.{c,h}
unnecessarily complicates building from source, __especially__ since
debian/patches/60_ubuntu_nav_bar.patch renders the originals invalid
anyway.
Consider the typical approach for shadowing the package with additional patches:
$ apt-get source gnome-control-center
$ cd gnome-control-center-3.4.2
$ git init
$ git add .
$ git commit -m Base package
$ dpkg-buildpackage -b -rfakeroot -us -uc
. everything builds fine, now cleanup and rebuild .
$ git reset --hard HEAD
$ git clean -xdf
$ dpkg-buildpackage -b -rfakeroot -us -uc
. build fails because trivial build products have current datetime so won't
be rebuilt :(
** Affects: gnome-control-center (Ubuntu)
Importance: Undecided
Status: New
--
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/1094061
Title:
trivial build products should not be in source package
Status in “gnome-control-center” package in Ubuntu:
New
Bug description:
Packaging trivial build products such as shell/cc-shell-marshal.{c,h}
unnecessarily complicates building from source, __especially__ since
debian/patches/60_ubuntu_nav_bar.patch renders the originals invalid
anyway.
Consider the typical approach for shadowing the package with additional
patches:
$ apt-get source gnome-control-center
$ cd gnome-control-center-3.4.2
$ git init
$ git add .
$ git commit -m Base package
$ dpkg-buildpackage -b -rfakeroot -us -uc
. everything builds fine, now cleanup and rebuild .
$ git reset --hard HEAD
$ git clean -xdf
$ dpkg-buildpackage -b -rfakeroot -us -uc
. build fails because trivial build products have current datetime so
won't be rebuilt :(
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1094061/+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 1094075] [NEW] gnome-control-center should not have hard dependency on gnome-icon-theme-symbolic
Public bug reported: A hard dependency on a icon theme package makes replacing that package impossible (or ugly in the extreme by using Breaks). At most, use a Recommends dependency. Even better would be to use a virtual package for symbolic icons ;) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- 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/1094075 Title: gnome-control-center should not have hard dependency on gnome-icon- theme-symbolic Status in “gnome-control-center” package in Ubuntu: New Bug description: A hard dependency on a icon theme package makes replacing that package impossible (or ugly in the extreme by using Breaks). At most, use a Recommends dependency. Even better would be to use a virtual package for symbolic icons ;) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1094075/+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 1093938] Re: gnome-panel should not have hard dependency to gnome-icon-theme-symbolic
Hi Jeremy,
Firstly, I think you didn't look closely at the code snippet that I
included. As packaged, gnome-panel does not render the icons for the
user menu, so it doesn't really matter if the icons are found or not
(that is, no functionality is broken by not having gnome-icon-theme-
symbolic installed).
Secondly, I think the purpose of symbolic icons has wandered from its original
mission. Excerpted from the README of gnome-icon-theme-symbolic:
Icons follow the naming specification, but have a -symbolic suffix, so only
applications specifically looking up these symbolic icons will render them. If
a -symbolic icon is missing, the app will fall back to the regular name.
If you'd prefer, I could change this bug (and similarly for g-c-c and
totem) to package should use g_themed_icon_new_from_names() for
symbolic icons.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-panel in Ubuntu.
https://bugs.launchpad.net/bugs/1093938
Title:
gnome-panel should not have hard dependency to gnome-icon-theme-
symbolic
Status in “gnome-panel” package in Ubuntu:
New
Bug description:
1. An icon theme file should not be a hard dependency. How would a different
icon theme provide alternate icons?
2. The 4 symbolic icons referred to are part of the now-defunct User menu,
which no longer draws the icons anyway:
static GtkWidget *
panel_menu_item_presence_new (..)
{
..
#if 0
if (use_icon) {
GtkWidget *image;
image = gtk_image_new_from_icon_name (icon,
panel_menu_icon_get_size
());
gtk_container_add (GTK_CONTAINER (item), image);
}
#endif
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1093938/+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 1091702] Re: upower fails to recognize hid devices with new kernels
This patch supersedes earlier patch. ** Summary changed: - udev rules fail to match hid devices with new kernels + upower fails to recognize hid devices with new kernels ** Patch added: [PATCH v2] Fix device matching for recent kernels https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1091702/+attachment/3468318/+files/0001-Fix-device-matching-for-recent-kernels.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1091702 Title: upower fails to recognize hid devices with new kernels Status in “upower” package in Ubuntu: New Bug description: In newer kernels, hiddev* devices now have class usbmisc, rather than usb (for reference see http://www.spinics.net/lists/linux- usb/msg62276.html ). Attached is a patch that fixes this without changing existing behavior for older kernels. The patch commit message contains an example attribute-walk on 3.7.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1091702/+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 1093938] [NEW] gnome-panel should not have hard dependency to gnome-icon-theme-symbolic
Public bug reported:
1. An icon theme file should not be a hard dependency. How would a different
icon theme provide alternate icons?
2. The 4 symbolic icons referred to are part of the now-defunct User menu,
which no longer draws the icons anyway:
static GtkWidget *
panel_menu_item_presence_new (..)
{
..
#if 0
if (use_icon) {
GtkWidget *image;
image = gtk_image_new_from_icon_name (icon,
panel_menu_icon_get_size
());
gtk_container_add (GTK_CONTAINER (item), image);
}
#endif
** Affects: gnome-panel (Ubuntu)
Importance: Undecided
Status: New
** Patch added: patch to debian/control.in
https://bugs.launchpad.net/bugs/1093938/+attachment/3468592/+files/0001-Remove-bogus-dependency-on-gnome-icon-theme-symbolic.patch
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-panel in Ubuntu.
https://bugs.launchpad.net/bugs/1093938
Title:
gnome-panel should not have hard dependency to gnome-icon-theme-
symbolic
Status in “gnome-panel” package in Ubuntu:
New
Bug description:
1. An icon theme file should not be a hard dependency. How would a different
icon theme provide alternate icons?
2. The 4 symbolic icons referred to are part of the now-defunct User menu,
which no longer draws the icons anyway:
static GtkWidget *
panel_menu_item_presence_new (..)
{
..
#if 0
if (use_icon) {
GtkWidget *image;
image = gtk_image_new_from_icon_name (icon,
panel_menu_icon_get_size
());
gtk_container_add (GTK_CONTAINER (item), image);
}
#endif
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1093938/+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 1091702] [NEW] udev rules fail to match hid devices with new kernels
Public bug reported: In newer kernels, hiddev* devices now have class usbmisc, rather than usb (for reference see http://www.spinics.net/lists/linux- usb/msg62276.html ). Attached is a patch that fixes this without changing existing behavior for older kernels. The patch commit message contains an example attribute-walk on 3.7.0 ** Affects: upower (Ubuntu) Importance: Undecided Status: New ** Patch added: [PATCH] Fix device matching for recent kernels https://bugs.launchpad.net/bugs/1091702/+attachment/3463003/+files/0001-Fix-device-matching-for-recent-kernels.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1091702 Title: udev rules fail to match hid devices with new kernels Status in “upower” package in Ubuntu: New Bug description: In newer kernels, hiddev* devices now have class usbmisc, rather than usb (for reference see http://www.spinics.net/lists/linux- usb/msg62276.html ). Attached is a patch that fixes this without changing existing behavior for older kernels. The patch commit message contains an example attribute-walk on 3.7.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1091702/+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 970024] Re: lightDM has purple backgroundcolor before the background image is loaded
As Michael Coupet points out, the bug here is that the default background is drawn at all. It's only because another size_allocate signal is received for the background that the user-configured gsettings background is drawn. Here's a clip from the attached greeter log which shows a span of 0.25 seconds between the MainWindow being shown and the correct, user-specified background being drawn (note the Regenerating backgrounds message): [+1.03s] DEBUG: unity-greeter.vala:350: Showing main window [+1.03s] DEBUG: New style for time label [+1.03s] DEBUG: Evaluating bitmask for '%l:%M %p' [+1.03s] DEBUG: Checking against 2 possible times [+1.03s] DEBUG: Guessing max time width: 62 [+1.04s] DEBUG: background.vala:315: Regenerating backgrounds [+1.04s] DEBUG: background.vala:67: Making background /usr/share/backgrounds/Winter_Morning_by_Shannon_Lucas.jpg at 1280x1024,1680x1050 [+1.04s] DEBUG: New style for time label [+1.04s] DEBUG: Evaluating bitmask for '%l:%M %p' [+1.04s] DEBUG: Checking against 2 possible times [+1.04s] DEBUG: Guessing max time width: 62 [+1.05s] DEBUG: unity-greeter.vala:891: Starting main loop [+1.05s] DEBUG: Read 8 bytes from daemon [+1.05s] DEBUG: Read 26 bytes from daemon [+1.05s] DEBUG: Prompt user with 1 message(s) [+1.08s] DEBUG: unity-greeter.vala:310: starting system-ready sound . [+1.29s] DEBUG: background.vala:116: Render of background /usr/share/backgrounds/Winter_Morning_by_Shannon_Lucas.jpg complete ** Attachment added: /var/log/lightdm/x-0-greeter.log https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/970024/+attachment/3057158/+files/x-0-greeter.log -- 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/970024 Title: lightDM has purple backgroundcolor before the background image is loaded Status in Light Display Manager: New Status in Unity Greeter: Confirmed Status in “lightdm” package in Ubuntu: Confirmed Bug description: Im using Precise with the latest updates and lightdm 1.1.9-0ubuntu1. Whenever lightdm is starting on bootup or logging out, there is a purple background shown before the real background image is loaded. I have attached a video demonstrates the problem. Thats pretty annoying when you chose not to use the default pinky purple background image. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lightdm 1.1.9-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13 Uname: Linux 3.2.0-21-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0-0ubuntu2 Architecture: amd64 Date: Sat Mar 31 15:01:12 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120209) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/970024/+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 962479] Re: Crash report cannot be processed due to outdated debug packages on daily-live
Hi Martin, Wait -- this situation makes no sense. Look at the debug symbol packages it's complaining about: they're not old by 1 version, but instead really old. Since the dbgsyms are on your side, how can upgrading to the latest binary packages impact the dbgsym archive?? For example, here's what apport retracing had to say regarding bug # 973450: Thank you for your report! However, processing it in order to get sufficient information for the developers failed (it does not generate a useful symbolic stack trace). This might be caused by some outdated packages which were installed on your system at the time of the report: outdated debug symbol package for dmidecode: package version 2.11-4 dbgsym version 2.9-1.2build1 outdated debug symbol package for cryptsetup: package version 2:1.4.1-2ubuntu2 dbgsym version 2:1.1.3-4ubuntu2 Look carefully; dmidecode is still at 2.11-4 !! ** Changed in: apport (Ubuntu) Status: Invalid = New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/962479 Title: Crash report cannot be processed due to outdated debug packages on daily-live Status in “apport” package in Ubuntu: New Bug description: Debug symbol packages are outdated on latest Live CD 22/03/12 - apport cannot generated useful stack trace. See bug# 962455. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/962479/+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 962479] Re: Crash report cannot be processed due to outdated debug packages on daily-live
After debugging the original problem myself, it turns out the the apport retracing message is just a red herring. The inability to get a stack backtrace for the original bug has nothing to do with outdated debug symbol packages. It's because parted_server (a binary from the ubiquity package) does not have debug symbols or a debug symbol package. ** Changed in: apport (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/962479 Title: Crash report cannot be processed due to outdated debug packages on daily-live Status in “apport” package in Ubuntu: Invalid Bug description: Debug symbol packages are outdated on latest Live CD 22/03/12 - apport cannot generated useful stack trace. See bug# 962455. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/962479/+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 962458] Re: [power]: gnome-settings-daemon crashed with SIGSEGV
@Sebastien, Before I report this upstream, is there a reason why you believe this is an upstream bug and not related to any of the *over 6000 lines* of debian + ubuntu patches? -- 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/962458 Title: [power]: gnome-settings-daemon crashed with SIGSEGV Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Bug description: This crash occurs immediately after the parted_server crashes while installing Precise Beta 1 22/03/12 from LiveCD. See bug# 962455. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gnome-settings-daemon 3.3.92-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-19.31-generic 3.2.12 Uname: Linux 3.2.0-19-generic x86_64 ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 CasperVersion: 1.312 Date: Thu Mar 22 19:12:57 2012 ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon LiveMediaBuild: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120322) ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon ProcEnviron: LANGUAGE= TERM=linux PATH=(custom, no user) LANG= SegvAnalysis: Segfault happened at: 0x7f809f5f0bba:mov0x8(%rbp),%r11d PC (0x7f809f5f0bba) ok source 0x8(%rbp) (0x0008) not located in a known VMA region (needed readable region)! destination %r11d ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-settings-daemon StacktraceTop: ?? () from /usr/lib/gnome-settings-daemon-3.0/libpower.so ?? () from /usr/lib/gnome-settings-daemon-3.0/libpower.so ?? () from /usr/lib/gnome-settings-daemon-3.0/libpower.so ?? () from /usr/lib/gnome-settings-daemon-3.0/libpower.so ?? () from /usr/lib/gnome-settings-daemon-3.0/libpower.so Title: [power]: gnome-settings-daemon crashed with SIGSEGV 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/gnome-settings-daemon/+bug/962458/+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 968769] [NEW] Symbolic power icons look out-of-place with non-symbolic theme
Public bug reported: The power plug-in preferentially selects '*-symbolic' icons first (in plugins/power/gpm-common.c:gpm_upower_get_device_icon). This looks out-of-place with non-symbolic indicators -- see attached screenshot. ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New -- 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/968769 Title: Symbolic power icons look out-of-place with non-symbolic theme Status in “gnome-settings-daemon” package in Ubuntu: New Bug description: The power plug-in preferentially selects '*-symbolic' icons first (in plugins/power/gpm-common.c:gpm_upower_get_device_icon). This looks out-of-place with non-symbolic indicators -- see attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/968769/+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 968769] Re: Symbolic power icons look out-of-place with non-symbolic theme
Attached is a screenshot of notification area with appropriate icon usage (icons are from gnome-power-manager). ** Attachment added: UPS icon from gnome-power-manager https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/968769/+attachment/2964322/+files/icons_from_gnome_power_manager.png -- 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/968769 Title: Symbolic power icons look out-of-place with non-symbolic theme Status in “gnome-settings-daemon” package in Ubuntu: New Bug description: The power plug-in preferentially selects '*-symbolic' icons first (in plugins/power/gpm-common.c:gpm_upower_get_device_icon). This looks out-of-place with non-symbolic indicators -- see attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/968769/+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 968769] Re: Symbolic power icons look out-of-place with non-symbolic theme
** Attachment added: Screenshot of notification area https://bugs.launchpad.net/bugs/968769/+attachment/2964321/+files/symbolic_power_icons_seem_wrong.png -- 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/968769 Title: Symbolic power icons look out-of-place with non-symbolic theme Status in “gnome-settings-daemon” package in Ubuntu: New Bug description: The power plug-in preferentially selects '*-symbolic' icons first (in plugins/power/gpm-common.c:gpm_upower_get_device_icon). This looks out-of-place with non-symbolic indicators -- see attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/968769/+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 968772] [NEW] gnome-power-manager icons should be part of theme
Public bug reported: Now that gnome-power-manager is no longer part of the notification/indicator subsystem, it's status icon set should be moved into the 'gnome' icon theme. The absence of appropriate icons is forcing devs to economize with poor substitutions. For example, the power plug-in of gnome-settings-daemon uses 'battery-*-symbolic' icon names preferentially now, which looks terrible. See attached screenshot. ** Affects: gnome-icon-theme (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/968772 Title: gnome-power-manager icons should be part of theme Status in “gnome-icon-theme” package in Ubuntu: New Bug description: Now that gnome-power-manager is no longer part of the notification/indicator subsystem, it's status icon set should be moved into the 'gnome' icon theme. The absence of appropriate icons is forcing devs to economize with poor substitutions. For example, the power plug-in of gnome-settings- daemon uses 'battery-*-symbolic' icon names preferentially now, which looks terrible. See attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-icon-theme/+bug/968772/+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 968772] Re: gnome-power-manager icons should be part of theme
** Attachment added: Screenshot of 'UPS charged' notification with 'gnome' icon theme https://bugs.launchpad.net/bugs/968772/+attachment/2964338/+files/symbolic_power_icons_seem_wrong.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/968772 Title: gnome-power-manager icons should be part of theme Status in “gnome-icon-theme” package in Ubuntu: New Bug description: Now that gnome-power-manager is no longer part of the notification/indicator subsystem, it's status icon set should be moved into the 'gnome' icon theme. The absence of appropriate icons is forcing devs to economize with poor substitutions. For example, the power plug-in of gnome-settings- daemon uses 'battery-*-symbolic' icon names preferentially now, which looks terrible. See attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-icon-theme/+bug/968772/+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 968772] Re: gnome-power-manager icons should be part of theme
** Attachment added: Screenshot with gnome-power-manager icons substituted https://bugs.launchpad.net/ubuntu/+source/gnome-icon-theme/+bug/968772/+attachment/2964339/+files/icons_from_gnome_power_manager.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/968772 Title: gnome-power-manager icons should be part of theme Status in “gnome-icon-theme” package in Ubuntu: New Bug description: Now that gnome-power-manager is no longer part of the notification/indicator subsystem, it's status icon set should be moved into the 'gnome' icon theme. The absence of appropriate icons is forcing devs to economize with poor substitutions. For example, the power plug-in of gnome-settings- daemon uses 'battery-*-symbolic' icon names preferentially now, which looks terrible. See attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-icon-theme/+bug/968772/+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 968772] Re: gnome-power-manager icons should be part of theme
Cross-reference to corresponding bug #968769 in gnome-settings-daemon wrt using '*-symbolic' icon names. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/968772 Title: gnome-power-manager icons should be part of theme Status in “gnome-icon-theme” package in Ubuntu: New Bug description: Now that gnome-power-manager is no longer part of the notification/indicator subsystem, it's status icon set should be moved into the 'gnome' icon theme. The absence of appropriate icons is forcing devs to economize with poor substitutions. For example, the power plug-in of gnome-settings- daemon uses 'battery-*-symbolic' icon names preferentially now, which looks terrible. See attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-icon-theme/+bug/968772/+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 965487] Re: [power]: gnome-settings-daemon crashed with SIGSEGV in engine_update_composite_device()
@RedSingularity, As I expected and noted, this bug is *not* a duplicate of bug# 962458, as confirmed by the completed i386 stack backtrace. This bug dies in engine_update_composite_device, whereas the amd64 stack backtrace for bug# 962458 indicates that crash @ engine_get_icon_priv. In the future, please don't assume that two bugs are related because they crash in the same binary. -- 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/965487 Title: [power]: gnome-settings-daemon crashed with SIGSEGV in engine_update_composite_device() Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Bug description: Happens while in a live session. Easily reproducible. Boot a live session and choose to install ubuntu. Wait a few seconds and the message will come up. ProblemType: CrashDistroRelease: Ubuntu 12.04 Package: gnome-settings-daemon 3.3.92-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic-pae 3.2.12 Uname: Linux 3.2.0-20-generic-pae i686 ApportVersion: 1.95-0ubuntu1 Architecture: i386 CasperVersion: 1.312 Date: Mon Mar 26 16:44:10 2012 ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon LiveMediaBuild: Ubuntu 12.04 LTS Precise Pangolin - Alpha i386 (20120325) ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SegvReason: reading NULL VMASignal: 11SourcePackage: gnome-settings-daemon Title: [power]: gnome-settings-daemon crashed with SIGSEGV in g_cclosure_marshal_VOID__OBJECTv() 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/gnome-settings-daemon/+bug/965487/+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 962458] Re: [power]: gnome-settings-daemon crashed with SIGSEGV
** This bug is no longer a duplicate of bug 965487 [power]: gnome-settings-daemon crashed with SIGSEGV in engine_update_composite_device() -- 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/962458 Title: [power]: gnome-settings-daemon crashed with SIGSEGV Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Bug description: This crash occurs immediately after the parted_server crashes while installing Precise Beta 1 22/03/12 from LiveCD. See bug# 962455. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gnome-settings-daemon 3.3.92-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-19.31-generic 3.2.12 Uname: Linux 3.2.0-19-generic x86_64 ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 CasperVersion: 1.312 Date: Thu Mar 22 19:12:57 2012 ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon LiveMediaBuild: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120322) ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon ProcEnviron: LANGUAGE= TERM=linux PATH=(custom, no user) LANG= SegvAnalysis: Segfault happened at: 0x7f809f5f0bba:mov0x8(%rbp),%r11d PC (0x7f809f5f0bba) ok source 0x8(%rbp) (0x0008) not located in a known VMA region (needed readable region)! destination %r11d ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-settings-daemon StacktraceTop: ?? () from /usr/lib/gnome-settings-daemon-3.0/libpower.so ?? () from /usr/lib/gnome-settings-daemon-3.0/libpower.so ?? () from /usr/lib/gnome-settings-daemon-3.0/libpower.so ?? () from /usr/lib/gnome-settings-daemon-3.0/libpower.so ?? () from /usr/lib/gnome-settings-daemon-3.0/libpower.so Title: [power]: gnome-settings-daemon crashed with SIGSEGV 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/gnome-settings-daemon/+bug/962458/+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 966697] [NEW] Transparent panel has themed widgets
Public bug reported: GTK+ 3.4 has introduced a bug with transparent panels. Specifically, upstream gtk+ commit 7603e6e4 breaks setting the background-image style property to a cairo pattern. This is the method that gnome-panel uses to simulate transparent backgrounds. ** Affects: gnome-panel Importance: Unknown Status: Unknown ** Affects: gnome-panel (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/966697 Title: Transparent panel has themed widgets Status in Desktop panel for GNOME: Unknown Status in “gnome-panel” package in Ubuntu: New Bug description: GTK+ 3.4 has introduced a bug with transparent panels. Specifically, upstream gtk+ commit 7603e6e4 breaks setting the background-image style property to a cairo pattern. This is the method that gnome- panel uses to simulate transparent backgrounds. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-panel/+bug/966697/+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 966697] Re: Transparent panel has themed widgets
NB: I logged this bug against gnome-panel because that's where it's going to be seen, but it's actually a bug in GTK -- the upstream bug is against GTK. ** Bug watch added: GNOME Bug Tracker #672858 https://bugzilla.gnome.org/show_bug.cgi?id=672858 ** Also affects: gnome-panel via https://bugzilla.gnome.org/show_bug.cgi?id=672858 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/966697 Title: Transparent panel has themed widgets Status in Desktop panel for GNOME: Unknown Status in “gnome-panel” package in Ubuntu: New Bug description: GTK+ 3.4 has introduced a bug with transparent panels. Specifically, upstream gtk+ commit 7603e6e4 breaks setting the background-image style property to a cairo pattern. This is the method that gnome- panel uses to simulate transparent backgrounds. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-panel/+bug/966697/+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 962458] Re: [power]: gnome-settings-daemon crashed with SIGSEGV
*** This bug is a duplicate of bug 965487 *** https://bugs.launchpad.net/bugs/965487 Bug 964654 may not be a duplicate. That report has no valid stack backtrace to confirm that it even originates from the same function, and it's on a different arch. Please un-duplicate this bug. -- 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/962458 Title: [power]: gnome-settings-daemon crashed with SIGSEGV Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Bug description: This crash occurs immediately after the parted_server crashes while installing Precise Beta 1 22/03/12 from LiveCD. See bug# 962455. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gnome-settings-daemon 3.3.92-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-19.31-generic 3.2.12 Uname: Linux 3.2.0-19-generic x86_64 ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 CasperVersion: 1.312 Date: Thu Mar 22 19:12:57 2012 ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon LiveMediaBuild: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120322) ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon ProcEnviron: LANGUAGE= TERM=linux PATH=(custom, no user) LANG= SegvAnalysis: Segfault happened at: 0x7f809f5f0bba:mov0x8(%rbp),%r11d PC (0x7f809f5f0bba) ok source 0x8(%rbp) (0x0008) not located in a known VMA region (needed readable region)! destination %r11d ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-settings-daemon StacktraceTop: ?? () from /usr/lib/gnome-settings-daemon-3.0/libpower.so ?? () from /usr/lib/gnome-settings-daemon-3.0/libpower.so ?? () from /usr/lib/gnome-settings-daemon-3.0/libpower.so ?? () from /usr/lib/gnome-settings-daemon-3.0/libpower.so ?? () from /usr/lib/gnome-settings-daemon-3.0/libpower.so Title: [power]: gnome-settings-daemon crashed with SIGSEGV 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/gnome-settings-daemon/+bug/962458/+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 960757] Re: whoopsie crashed with SIGSEGV in g_object_newv()
This crash happened while trying to install Precise Beta 1 22/03/12 from LiveCd. See bug# 962455 and bug# 962458. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/960757 Title: whoopsie crashed with SIGSEGV in g_object_newv() Status in “glib2.0” package in Ubuntu: Confirmed Status in “whoopsie-daisy” package in Ubuntu: Confirmed Status in “glib2.0” source package in Precise: Confirmed Status in “whoopsie-daisy” source package in Precise: Confirmed Bug description: Rebooted, greated with error. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: whoopsie 0.1.18 ProcVersionSignature: Ubuntu 3.2.0-19.30-generic 3.2.11 Uname: Linux 3.2.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 Date: Tue Mar 20 17:36:36 2012 ExecutablePath: /usr/bin/whoopsie InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) ProcCmdline: whoopsie ProcEnviron: PATH=(custom, no user) TERM=linux SegvAnalysis: Segfault happened at: 0x7fdb71d1f92b g_string_sized_new+43:movq $0x0,0x10(%rax) PC (0x7fdb71d1f92b) ok source $0x0 ok destination 0x10(%rax) (0x7fdb72300db4) in non-writable VMA region: 0x7fdb72201000-0x7fdb72356000 r-xp /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.3122.0 SegvReason: writing VMA /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.3122.0 Signal: 11 SourcePackage: whoopsie-daisy StacktraceTop: g_object_newv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: whoopsie crashed with SIGSEGV in g_object_newv() UpgradeStatus: Upgraded to precise on 2012-02-13 (36 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/960757/+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 828392] Re: light-themes don't display well in gnome-panel 3+
It seems that this bug is becoming sort of a meta-bug for several issues in different packages. Bug 885691 (which was marked a duplicate of this) specifically addressed the themed background gradient not drawn correctly. A patch to gnome- panel was submitted for that bug and the upstream bug, gnome-bugs 663397, on remote watch here. The original reporter of this bug seems to refer primarily to the gradient background issue as being the impetus for this report. There are certainly other bugs that impact the visual quality of light-themes with gnome-panel 3. I would be happy to cross-ref those here if that's helpful. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/828392 Title: light-themes don't display well in gnome-panel 3+ Status in Desktop panel for GNOME: New Status in The Unico Gtk+ Theming Engine: New Status in “gnome-panel” package in Ubuntu: Triaged Status in “gtk3-engines-unico” package in Ubuntu: New Bug description: Please see the attached screenshots. Adwaita looks lovely in Gnome Fallback (aka Gnome Classic or gnome-panel) but Ambiance Radiance do not blend right. It's probably worth looking at Adwaita's code to see what they do exactly to support Gnome Shell Fallback. Perhaps light- themes uses too many hacks that don't all work well with the Gnome 3 switch. This is a high priority as a decent amount of upgraders who will try to keep using Gnome Fallback even though little developer time is spent to keep it working. And since there is not an obvious way to change the theme in Gnome 3, they may not know that switching to Adwaita will improve the appearance, or know how to do that either. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: light-themes 0.1.8.21 ProcVersionSignature: Ubuntu 3.0.0-8.11-generic 3.0.1 Uname: Linux 3.0.0-8-generic x86_64 Architecture: amd64 Date: Wed Aug 17 18:21:31 2011 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) PackageArchitecture: all SourcePackage: light-themes UpgradeStatus: Upgraded to oneiric on 2011-06-17 (61 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-panel/+bug/828392/+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 913637] [NEW] --with-sub-version build option is always - (should be -revision)
Public bug reported: An error in debian/rules causes the -with-sub-version build option to always be set to -, regardless of the changelog version. NB: debian/rules is a makefile and make *always* expands $. To prevent $ expansion (so that awk substitution works), use $$ instead. ** Affects: evolution (Ubuntu) Importance: Undecided Status: New -- 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/913637 Title: --with-sub-version build option is always - (should be -revision) Status in “evolution” package in Ubuntu: New Bug description: An error in debian/rules causes the -with-sub-version build option to always be set to -, regardless of the changelog version. NB: debian/rules is a makefile and make *always* expands $. To prevent $ expansion (so that awk substitution works), use $$ instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/913637/+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 913637] Re: --with-sub-version build option is always - (should be -revision)
** Patch added: Fix_blank_sub_version.patch https://bugs.launchpad.net/bugs/913637/+attachment/2663657/+files/Fix_blank_sub_version.patch -- 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/913637 Title: --with-sub-version build option is always - (should be -revision) Status in “evolution” package in Ubuntu: New Bug description: An error in debian/rules causes the -with-sub-version build option to always be set to -, regardless of the changelog version. NB: debian/rules is a makefile and make *always* expands $. To prevent $ expansion (so that awk substitution works), use $$ instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/913637/+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
