On 02/24/2011 06:38 PM, David C. Rankin wrote:
> OK,
>
> That's good info, but why then does Fluxbox exhibit the same pixelation
> desktop crash when an xterm is launched?
>
> I can start fluxbox and I can look at the menus (change config settings in
> the
> menu), but as soon as I launch an
On 02/24/2011 01:17 PM, Wieland Hoffmann wrote:
I have no idea what this error is. Something is going wrong somewhere on
> x86_64 with either glibc or libxcb. I don't know if the output from the
startx
> command and its backtrace will help narrow this down, but it seems to be a
> generic X
On 24.02.2011 19:10, David C. Rankin wrote:
>
> COP: unregister 'kaccess'
> X Error: BadWindow (invalid Window parameter) 3
> Major opcode: 7
> Minor opcode: 0
> Resource id: 0x206
> X Error: BadWindow (invalid Window parameter) 3
> Major opcode: 6
> Minor opcode: 0
> Resource
On 02/23/2011 08:37 PM, David C. Rankin wrote:
> On 02/23/2011 07:38 PM, Allan McRae wrote:
>> On 24/02/11 10:15, David C. Rankin wrote:
>>> On 02/23/2011 04:53 PM, David C. Rankin wrote:
I have no idea what the error means, but it looks like malloc is
complaining
about corruption?
On Thu, 24 Feb 2011 11:38:42 +1000 Allan McRae wrote:
> If this is virtualbox specific, I'd try qemu-kvm.
If you want to do this than this can save your time:
http://blog.bodhizazen.net/linux/convert-virtualbox-vdi-to-kvm-qcow
Personally i would use qed with the new qemu-kmv 0.14.0 instead of
q
On 02/23/2011 07:38 PM, Allan McRae wrote:
> On 24/02/11 10:15, David C. Rankin wrote:
>> On 02/23/2011 04:53 PM, David C. Rankin wrote:
>>> I have no idea what the error means, but it looks like malloc is complaining
>>> about corruption?
>>>
>>> #8 0x7f3550d27b96 in malloc_printerr (action=3
On 24/02/11 10:15, David C. Rankin wrote:
On 02/23/2011 04:53 PM, David C. Rankin wrote:
I have no idea what the error means, but it looks like malloc is complaining
about corruption?
#8 0x7f3550d27b96 in malloc_printerr (action=3, str=0x7f3550dd6a2e
"malloc(): memory corruption", ptr=) at
On 02/23/2011 04:53 PM, David C. Rankin wrote:
> I have no idea what the error means, but it looks like malloc is complaining
> about corruption?
>
> #8 0x7f3550d27b96 in malloc_printerr (action=3, str=0x7f3550dd6a2e
> "malloc(): memory corruption", ptr=) at malloc.c:6283
> #9 0x7f3550d2
On 02/23/2011 01:38 PM, David C. Rankin wrote:
> On 02/22/2011 06:41 PM, Allan McRae wrote:
>> That prelink patch is very, very unlikely to cause the issue. It was also
>> the
>> only change between 2.13-3 and 2.13-4... As I pointed out, there are other
>> distros using that patch without report
On 02/22/2011 06:41 PM, Allan McRae wrote:
> That prelink patch is very, very unlikely to cause the issue. It was also the
> only change between 2.13-3 and 2.13-4... As I pointed out, there are other
> distros using that patch without reported issue and it is now in glibc
> mainline
> so nothing
On Tuesday, February 22, 2011 07:41:53 PM Allan McRae wrote:
>
> That prelink patch is very, very unlikely to cause the issue. It was
> also the only change between 2.13-3 and 2.13-4... As I pointed out,
> there are other distros using that patch without reported issue and it
> is now in glibc m
On 23/02/11 10:13, David C. Rankin wrote:
On 02/22/2011 05:07 PM, Allan McRae wrote:
On 23/02/11 04:23, Lukas Fleischer wrote:
On Tue, Feb 22, 2011 at 11:41:12AM -0600, David C. Rankin wrote:
On next reboot/restart, I got the kdesktop.kcrash (attached). So then I
downgraded glibc (2.13-4 -
On 02/22/2011 05:07 PM, Allan McRae wrote:
> On 23/02/11 04:23, Lukas Fleischer wrote:
>> On Tue, Feb 22, 2011 at 11:41:12AM -0600, David C. Rankin wrote:
>>>On next reboot/restart, I got the kdesktop.kcrash (attached). So then I
>>> downgraded glibc (2.13-4 -> 2.13-3), restarted Trinity -> p
On 23/02/11 04:23, Lukas Fleischer wrote:
On Tue, Feb 22, 2011 at 11:41:12AM -0600, David C. Rankin wrote:
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 gl
On 02/22/2011 11:41 AM, David C. Rankin wrote:
>
>
> 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 whic
On 02/22/2011 12:23 PM, Lukas Fleischer wrote:
> No, seriously... glibc 2.13-4 introduced a patch from the Fedora glibc
> branch that is not included in mainline glibc and fixes issues with
> prelink [1]. Obviously, this has some side effects. Seems like it
> requires some more investigation.
>
>
On 02/22/2011 12:23 PM, Lukas Fleischer wrote:
> Allan broke it!
>
> No, seriously... glibc 2.13-4 introduced a patch from the Fedora glibc
> branch that is not included in mainline glibc and fixes issues with
> prelink [1]. Obviously, this has some side effects. Seems like it
> requires some more
On Tue, Feb 22, 2011 at 11:41:12AM -0600, David C. Rankin wrote:
> 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)
>
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
19 matches
Mail list logo
