https://bugs.freedesktop.org/show_bug.cgi?id=60182
--- Comment #37 from Weber K. weber...@yahoo.com.br ---
Hi!
Here RESOLVED.
Sorry for late response, I needed to upgrade my whole system to current for
testing.
I have the same new glxgears messages if closed clicking in the close button.
If
https://bugs.freedesktop.org/show_bug.cgi?id=60182
Michel Dänzer mic...@daenzer.net changed:
What|Removed |Added
Status|NEW |RESOLVED
https://bugs.freedesktop.org/show_bug.cgi?id=60182
--- Comment #34 from Michel Dänzer mic...@daenzer.net ---
(In reply to comment #33)
(which AFAIK is normal, but didn't happen before).
Yes, that's normal and not related to this problem.
Note that the 'Attempted to destroy previously destroyed
https://bugs.freedesktop.org/show_bug.cgi?id=60182
--- Comment #35 from Jose P. lbdkm...@sharklasers.com ---
(In reply to comment #34)
(In reply to comment #33)
(which AFAIK is normal, but didn't happen before).
Yes, that's normal and not related to this problem.
Note that the 'Attempted
https://bugs.freedesktop.org/show_bug.cgi?id=60182
--- Comment #31 from Michel Dänzer mic...@daenzer.net ---
(In reply to comment #30)
This, plus the patch in comment 6, fixed it for me [...]
Thanks, but please try without that other patch. If it's still necessary,
something is still wrong.
--
https://bugs.freedesktop.org/show_bug.cgi?id=60182
--- Comment #32 from Michel Dänzer mic...@daenzer.net ---
Actually, just let us know if you still get any 'Attempted to destroy
previously destroyed buffer.' messages.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=60182
--- Comment #33 from Jose P. lbdkm...@sharklasers.com ---
(In reply to comment #32)
Actually, just let us know if you still get any 'Attempted to destroy
previously destroyed buffer.' messages.
None at all.
I only get 'XIO: fatal IO error 11
https://bugs.freedesktop.org/show_bug.cgi?id=60182
--- Comment #29 from Michel Dänzer mic...@daenzer.net ---
Created attachment 86051
-- https://bugs.freedesktop.org/attachment.cgi?id=86051action=edit
DRI2: Install client callback only once
Does this patch fix the problem?
--
You are
https://bugs.freedesktop.org/show_bug.cgi?id=60182
--- Comment #30 from Jose P. lbdkm...@sharklasers.com ---
(In reply to comment #29)
Created attachment 86051 [details] [review]
DRI2: Install client callback only once
Does this patch fix the problem?
This, plus the patch in comment 6,
https://bugs.freedesktop.org/show_bug.cgi?id=60182
--- Comment #28 from Weber K. weber...@yahoo.com.br ---
Sorry fellows... I my proposal was only a workaround...
Maybe if you have 2 cards, and only the second is radeon, then the callback
will never be scheduled... :(
The solution needs to be
https://bugs.freedesktop.org/show_bug.cgi?id=60182
--- Comment #22 from Alex Deucher ag...@yahoo.com ---
Can you try a vanilla xf86-video-ati rather than the ubuntu version? This
looks like it may be specific to their version.
--
You are receiving this mail because:
You are the assignee for
https://bugs.freedesktop.org/show_bug.cgi?id=60182
--- Comment #21 from Weber K. weber...@yahoo.com.br ---
Hello!
I think I found a workaround!
At this file:
https://github.com/RAOF/xf86-video-ati/blob/master/src/radeon_dri2.c
At line 608:
Changed from:
xorg_list_for_each_entry(ref,
https://bugs.freedesktop.org/show_bug.cgi?id=60182
--- Comment #24 from Weber K. weber...@yahoo.com.br ---
Looking at neuromancer Xorg log, I found out:
[ 7.278] (--) RADEON(0): Chipset: SUMO (ChipID = 0x9641)
[ 7.548] (--) RADEON(G0): Chipset: TURKS (ChipID = 0x6741)
I think its a
https://bugs.freedesktop.org/show_bug.cgi?id=60182
--- Comment #23 from Weber K. weber...@yahoo.com.br ---
Hi!
Ive found that (for me) this layout is causing the error:
Section ServerLayout
Identifier My X Server
Screen 0 LeftScreen 0 0
Screen 1 RightScreen RightOf
https://bugs.freedesktop.org/show_bug.cgi?id=60182
--- Comment #25 from lbdkm...@sharklasers.com ---
Yes, this, aparently, only happens in dual AMD graphics laptops (with llano)...
and I found a workaround:
you have to disable the second (discrete) GPU:
echo OFF
https://bugs.freedesktop.org/show_bug.cgi?id=60182
--- Comment #26 from Weber K. weber...@yahoo.com.br ---
During a test, I needed to issue 2 cont commands at gdb to advance just one
frame at one breakpoint I trapped. And when closing the player, I issued twice
cont at gdb, and only after the
https://bugs.freedesktop.org/show_bug.cgi?id=60182
--- Comment #27 from Weber K. weber...@yahoo.com.br ---
I think Ive got it! :)
Changed this file:
https://github.com/RAOF/xf86-video-ati/blob/master/src/radeon_dri2.c
Line 1404 from:
AddCallback(ClientStateCallback,
https://bugs.freedesktop.org/show_bug.cgi?id=60182
--- Comment #20 from Weber K. weber...@yahoo.com.br ---
Here is what Ive got!
If this dont help, please give me more details and I will try my best!
Thanks in advance!
xf86-video-ati 6.14.4
xorg-server 1.12.4
Program received signal SIGSEGV,
https://bugs.freedesktop.org/show_bug.cgi?id=60182
--- Comment #19 from Weber K. weber...@yahoo.com.br ---
Hi!
This error is happening here also...
Slackware64 linux on AMD Phenom II 1055T, with XFX Radeon HD6850 and open
source drivers radeon.
The X server crash after second close of
https://bugs.freedesktop.org/show_bug.cgi?id=60182
--- Comment #18 from Michel D?nzer ---
Can someone who can reproduce the problem attach gdb to the X server process
and set a breakpoint where it would print 'Attempted to destroy previously
destroyed buffer.'? Then when it triggers, attach the
https://bugs.freedesktop.org/show_bug.cgi?id=60182
--- Comment #18 from Michel Dänzer mic...@daenzer.net ---
Can someone who can reproduce the problem attach gdb to the X server process
and set a breakpoint where it would print 'Attempted to destroy previously
destroyed buffer.'? Then when it
https://bugs.freedesktop.org/show_bug.cgi?id=60182
--- Comment #17 from lbdkmjdf at sharklasers.com ---
sorry, I meant "but it crashed twice" in the previous post.
Yet another backtrace: http://pastebin.com/aVq5Uhyf
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=60182
--- Comment #16 from lbdkmjdf at sharklasers.com ---
(In reply to comment #15)
> Does the patch in comment 6 help?
yes, the patch helped a bit... it made it hard to crash xserver, but it crashes
twice after applying it. although, I'm not sure
https://bugs.freedesktop.org/show_bug.cgi?id=60182
--- Comment #15 from Alex Deucher ---
Does the patch in comment 6 help?
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
https://bugs.freedesktop.org/show_bug.cgi?id=60182
--- Comment #14 from lbdkmjdf at sharklasers.com ---
so I forgot to install the -dbg packages, but... X server will not crash with
these, so it won't help anyway :/ (and I tried to make it crash a lot of times
after installing the -dbg packages).
https://bugs.freedesktop.org/show_bug.cgi?id=60182
--- Comment #13 from lbdkmjdf at sharklasers.com ---
Created attachment 82065
--> https://bugs.freedesktop.org/attachment.cgi?id=82065=edit
X crashlog
I got hit by the same bug... Xorg crashes when closing glxgears (simply press X
and expect X
https://bugs.freedesktop.org/show_bug.cgi?id=60182
--- Comment #13 from lbdkm...@sharklasers.com ---
Created attachment 82065
-- https://bugs.freedesktop.org/attachment.cgi?id=82065action=edit
X crashlog
I got hit by the same bug... Xorg crashes when closing glxgears (simply press X
and expect
https://bugs.freedesktop.org/show_bug.cgi?id=60182
--- Comment #14 from lbdkm...@sharklasers.com ---
so I forgot to install the -dbg packages, but... X server will not crash with
these, so it won't help anyway :/ (and I tried to make it crash a lot of times
after installing the -dbg packages).
https://bugs.freedesktop.org/show_bug.cgi?id=60182
--- Comment #15 from Alex Deucher ag...@yahoo.com ---
Does the patch in comment 6 help?
--
You are receiving this mail because:
You are the assignee for the bug.
___
dri-devel mailing list
https://bugs.freedesktop.org/show_bug.cgi?id=60182
--- Comment #16 from lbdkm...@sharklasers.com ---
(In reply to comment #15)
Does the patch in comment 6 help?
yes, the patch helped a bit... it made it hard to crash xserver, but it crashes
twice after applying it. although, I'm not sure it's
https://bugs.freedesktop.org/show_bug.cgi?id=60182
--- Comment #17 from lbdkm...@sharklasers.com ---
sorry, I meant but it crashed twice in the previous post.
Yet another backtrace: http://pastebin.com/aVq5Uhyf
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=60182
--- Comment #12 from runetmember at gmail.com ---
Created attachment 74464
--> https://bugs.freedesktop.org/attachment.cgi?id=74464=edit
x-0.log LightDM log after crash
LightDM logs in right-after-crash state attached.
--
You are receiving
https://bugs.freedesktop.org/show_bug.cgi?id=60182
--- Comment #11 from runetmember at gmail.com ---
Created attachment 74462
--> https://bugs.freedesktop.org/attachment.cgi?id=74462=edit
lightdm.log after crash
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=60182
--- Comment #11 from runetmem...@gmail.com ---
Created attachment 74462
-- https://bugs.freedesktop.org/attachment.cgi?id=74462action=edit
lightdm.log after crash
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=60182
--- Comment #12 from runetmem...@gmail.com ---
Created attachment 74464
-- https://bugs.freedesktop.org/attachment.cgi?id=74464action=edit
x-0.log LightDM log after crash
LightDM logs in right-after-crash state attached.
--
You are receiving
https://bugs.freedesktop.org/show_bug.cgi?id=60182
--- Comment #10 from runetmember at gmail.com ---
> So I would like you to test if the patch that I posted fixes the problem for
> you.
Unfortunately, I am not developer, I can't check this patch.
> Any additional logs that you can produce in
https://bugs.freedesktop.org/show_bug.cgi?id=60182
--- Comment #9 from Ilija Hadzic ---
(In reply to comment #8)
> So since you find root case, LightDM log is not necessary now, I am correct?
No, I didn't find the root cause. I am only assuming (based on the last message
in your Xorg.0.log
https://bugs.freedesktop.org/show_bug.cgi?id=60182
--- Comment #8 from runetmember at gmail.com ---
So since you find root case, LightDM log is not necessary now, I am correct?
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An
https://bugs.freedesktop.org/show_bug.cgi?id=60182
--- Comment #7 from Ilija Hadzic ---
I have just posted a patch that may help at least prevent the crash. I have
seen this bug on my end too, but I though that I locally introduced it with my
own hacks. The patch does not solve the root cause
https://bugs.freedesktop.org/show_bug.cgi?id=60182
--- Comment #6 from Ilija Hadzic ---
Created attachment 74183
--> https://bugs.freedesktop.org/attachment.cgi?id=74183=edit
Possible "Band-Aid" to get you going.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=60182
--- Comment #5 from runetmember at gmail.com ---
> Is there more information in the kdm log file?
I use LightDM-KDE. I'll look into LightDM log next time.
--
You are receiving this mail because:
You are the assignee for the bug.
--
https://bugs.freedesktop.org/show_bug.cgi?id=60182
--- Comment #4 from Michel D?nzer ---
The attached log ends abruptly. Is there more information in the kdm log file?
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML
https://bugs.freedesktop.org/show_bug.cgi?id=60182
--- Comment #4 from Michel Dänzer mic...@daenzer.net ---
The attached log ends abruptly. Is there more information in the kdm log file?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=60182
--- Comment #5 from runetmem...@gmail.com ---
Is there more information in the kdm log file?
I use LightDM-KDE. I'll look into LightDM log next time.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=60182
--- Comment #6 from Ilija Hadzic ihad...@research.bell-labs.com ---
Created attachment 74183
-- https://bugs.freedesktop.org/attachment.cgi?id=74183action=edit
Possible Band-Aid to get you going.
--
You are receiving this mail because:
You
https://bugs.freedesktop.org/show_bug.cgi?id=60182
--- Comment #7 from Ilija Hadzic ihad...@research.bell-labs.com ---
I have just posted a patch that may help at least prevent the crash. I have
seen this bug on my end too, but I though that I locally introduced it with my
own hacks. The patch
https://bugs.freedesktop.org/show_bug.cgi?id=60182
--- Comment #8 from runetmem...@gmail.com ---
So since you find root case, LightDM log is not necessary now, I am correct?
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freedesktop.org/show_bug.cgi?id=60182
--- Comment #9 from Ilija Hadzic ihad...@research.bell-labs.com ---
(In reply to comment #8)
So since you find root case, LightDM log is not necessary now, I am correct?
No, I didn't find the root cause. I am only assuming (based on the last
https://bugs.freedesktop.org/show_bug.cgi?id=60182
--- Comment #3 from runetmember at gmail.com ---
Also a little bit info, just in case:
Exact GPU model: 1002:6741 Advanced Micro Devices [AMD] nee ATI BeaverCreek
[Mobility Radeon HD 6620G]
VLC version: 2.0.5.
If I need to provide any additional
https://bugs.freedesktop.org/show_bug.cgi?id=60182
--- Comment #2 from runetmember at gmail.com ---
Created attachment 74079
--> https://bugs.freedesktop.org/attachment.cgi?id=74079=edit
dmesg
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part
https://bugs.freedesktop.org/show_bug.cgi?id=60182
--- Comment #1 from runetmember at gmail.com ---
Created attachment 74078
--> https://bugs.freedesktop.org/attachment.cgi?id=74078=edit
Log of terminated X.Org Server
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=60182
--- Comment #1 from runetmem...@gmail.com ---
Created attachment 74078
-- https://bugs.freedesktop.org/attachment.cgi?id=74078action=edit
Log of terminated X.Org Server
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=60182
--- Comment #3 from runetmem...@gmail.com ---
Also a little bit info, just in case:
Exact GPU model: 1002:6741 Advanced Micro Devices [AMD] nee ATI BeaverCreek
[Mobility Radeon HD 6620G]
VLC version: 2.0.5.
If I need to provide any additional
53 matches
Mail list logo
