[arch-general] [trinity-devel] x86_64 kdesktop.kcrash [SOLVED - it is glibc]

[David C. Rankin]

On 02/21/2011 08:41 PM, David C. Rankin wrote:
> On 02/21/2011 05:09 PM, PICCORO McKAY Lenz wrote:
>> uff i reading this
>> http://lists.freedesktop.org/archives/xcb/2010-March/005818.html and
>> seem like that!
>>
>> any help fron anybody here!
>>
> 
> I'll follow up there. I can't believe that an libxcb problem would still be
> around a year later. 
<snip>

Guys,

  The problem is glibc-2.13-4. I have about 5 Arch/Trinity Virtualbox VMs. On
one I had not updated, I started Trinity x86_64 and there was NO kdesktop crash.
I then proceeded to update the VM to the current Arch packages which included:

[2011-02-22 11:13] Generating locales...
[2011-02-22 11:13]   en_US.UTF-8... done
[2011-02-22 11:13]   en_US.ISO-8859-1... done
[2011-02-22 11:13] Generation complete.
[2011-02-22 11:13] upgraded glibc (2.13-3 -> 2.13-4)
<snip>
[2011-02-22 11:17] upgraded kernel26 (2.6.37-6 -> 2.6.37.1-1)
[2011-02-22 11:17] upgraded kernel26-headers (2.6.37-6 -> 2.6.37.1-1)
<snip>
[2011-02-22 11:18] upgraded trinity-kdelibs (1220926-1 -> 1222098-1)
[2011-02-22 11:18] upgraded trinity-kdebase (1221507-1 -> 1221588-1)

  On next reboot/restart, I got the kdesktop.kcrash (attached). So then I
downgraded glibc (2.13-4 -> 2.13-3), restarted Trinity -> perfect No
kdesktop,kcrash. It looks like this is a glibc issue, so I'll follow up (below)
with Arch to make sure it looks like glibc and not a package issue. Thanks for
your help.

cc: arch-general

  Arch devs - Do you think this could be a packaging/patch issue with Arch, or
do you think is going to be glibc itself? It looks like glibc to me, but I
thought I'd ask first before going to the glibc folks.


-- 
David C. Rankin, J.D.,P.E.
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: kdesktop-alchemy.kcrash
URL: <http://mailman.archlinux.org/pipermail/arch-general/attachments/20110222/75fb093d/attachment-0001.ksh>