On 02/19/2011 01:18 PM, David C. Rankin wrote: > On 02/19/2011 03:23 AM, Rémy Oudompheng wrote: >> On 2011/2/19 David C. Rankin <drankinatty@xxxxxxxxxxxxxxxxxx> wrote: >>> Guys, >>> >>> I have run into an issue that is only causing problems on x86_64. It looks >>> like libxcb. The kcrash file is here: >>> >>> [2k] >>> http://www.3111skyline.com/dl/dt/trinity/errors/x86_64/kdesktop-1.kcrash current kdesktop.kcrash: http://www.3111skyline.com/dl/dt/trinity/arch/err/x86_64/kdesktop-alchemy.kcrash >>> I need to figure out if this is an upstream libxcb issue or possibly a package >>> issue. How do I figure this out? >> <snip> > > Could this be further up in libc? Details from Trinity List Discussion: 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 (see current link above). So then I downgraded glibc (2.13-4 -> 2.13-3), restarted Trinity -> perfect! No kdesktop,kcrash. 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 here before going to the glibc folks in case it was something that you guys wanted to look at. Thanks. -- David C. Rankin, J.D.,P.E.
