After press maximize button in kmplayer with a rmvb video running, X crash and the system return to login screen.
But, the fullscreen mode, pressing F button, it's ok.
I use KDE SC 4.6.1 and my video card is (lspci):
01:00.0 VGA compatible controller: Silicon Integrated Systems [SiS] 771/671 PCIE VGA Display Adapter (rev 10)
KDE-4.6.2 is already in the repos.
What's the output of the following command:
lspcidrake -v | grep Card
Please _attach_ your /var/log/Xorg.0.log or Xorg.0.log.1 after a crash.
Look for error also in /var/log/gdm/*
Created attachment 243 [details]
Xorg.0.log of my notebook
The log of Xorg after crash in mplayer running.
I updated complete my system.
Thierry, I have attached above. There are no gdm logs on my system.
The lspcidrake | grep Card output is:
$ lspcidrake | grep Card
Card:SiS SiS 670 / 671-based cards: Silicon Integrated Systems [SiS]|771/671 PCIE VGA Display Adapter [DISPLAY_VGA] (rev: 10)
And more: the problem is with mplayer, not with kmplayer. Run mplayer direct also break the X too. I will update the title this bug report.
X break after maximize Kmplayer =>
X break after run mplayer with rmvb video
Ok, I did more tests, with various video players (vlc, mplayer, the mplayer frontend kmplayer and kaffeine) with various video formats (rmvb, avi and ISO dvd) and always crash X server, returning to login screen.
Sometimes, the video running but, in few times (seconds or minutes), the X server crash.
I will update, again, the bug report's title.
X break after run mplayer with rmvb video =>
X crash after run any video player with any video formatSeverity:
There's no error in your /var/log/Xorg.0.log.
If X11 has aleady restarted after the crash, it's /var/log/Xorg.0.log.1 that's needed.
What's would be even better would be :
Please download both https://bugs.mageia.org/attachment.cgi?id=121 and
Then enable the core/debug_release media/repository and install
x11-server-debug, x11-driver-video-sis-debug, glibc-debug
Then just run "sh ./Xgdb2.sh" on a text terminal (not from a terminal within X11!!! use Ctrl+Alt+F1), then switch back to X11 until it segfaults (Ctrl+Alt+F7).
Attachment 243 mime type:
I see this in the Xorg.0.log from comment#3:
(EE) AIGLX error: dlopen of /usr/lib64/dri/sis671_dri.so failed (/usr/lib64/dri/sis671_dri.so: cannot open shared object file: No such file or directory)
That's totally unrelated, it means there's no 3d support for that card and that software fallback will be used, which is totally orthogonal to this issue
Created attachment 274 [details]
X crash log
The log of X crash. Backtrace begin in line 1000.
Thierry, the correct X log attached above.
Attachment 274 mime type:
Please try to provide the GDB trace too
X crash after run any video player with any video format =>
[SisImedia] X crash after run any video player with any video formatSource RPM:
[SisImedia] X crash after run any video player with any video format =>
[Sisimedia] X crash after run any video player with any video format
Please Thierry, explain how to provide the GDB. The first file in comment#6, https://bugs.mageia.org/attachment.cgi?id=121, is "Xgdb2.sh"? And what to do with the second file, (https://bugs.mageia.org/attachment.cgi?id=122)?
Just save both files.
Then just run "sh ./Xgdb2.sh" on a text terminal (not from a terminal within
X11!!! use Ctrl+Alt+F1), then switch back to X11 until it segfaults
Thierry, I am with some doubts.
The second file, https://bugs.mageia.org/attachment.cgi?id=122, is gcmds2 file? If yes, the gdb backtrace result is http://pastebin.ca/2052412
I put in pastebin because this is not the correct backtrace yet.
Yes it is.
But you're using it incorrectly since X is not running and
thus GDB cannot attach to X.
just wanted to note, that my girlfriend and I faced the same(?) problem a few times in the last days - we both have current Mageia repository updates installed and different graphic setting (she has a nvidia card, I have got a radeon card)
for both of us switching flash movies to fullscreen leads to a in most cases reproduceable crash - it does not crash directly but after some mouse interaction (moving a bit, clicking a bit...)
e.g. I was interested in a new add of my favourite drink and so entered their page (irn-bru.co.uk/) the page directly loads the add and opens it up in fullscreen after a few seconds. Without interaction the add just runs fine, moving the mouse a bit and/or clicking most likely leads to a crash.
Both using kde4.6.3 and everything else working as it should, just my girlfrind had to add vmalloc=128M to the kernel call at startup (up to date kernel), as else she was not able to see my skype video transfer during a skype call
ahh just wanted to notice: dragonplayer and vlc work fine in fullscreen, only noticed this problem with flash players - so maybe this is a different bug but similar symptoms?
anyways: she uses a 32bit system I use a 64bit system.
Created attachment 374 [details]
Xorg.0.log from last crash on my radeon machine
here is my Xorg.0.log from after a crash.
And I noticed something else: Both my girlfriends and my pc have a second graphics card for the hdmi output - both are intel graphics card.
Your crash is a totally different problem so please stop commenting on that bug and open another one against x11-driver-video-intel.
Try to get a GDB trace as explained in Comment 6, and attach it to the newly created bug report (not to this bug report).
Just install x11-driver-video-intel-debug instead of x-d-v-sis-debug.
And open another one for the radeon one.
Created attachment 485 [details]
GDB backtrack of X after crash
Attachment 243 is obsolete:
Attachment 274 is obsolete:
Attachment 374 is obsolete:
Finally I did the debug X. I used this tutorial (http://wiki.debian.org/XStrikeForce/XserverDebugging#Obtaining_a_backtrace_with_gdb), with an extra machine accessing my machine via ssh and capturing the backtrack X.
I ran a video with VLC and hit "f" for fullscreen. That broke the X.
The backtack is in Comment 21. I hope it's correct now.
Hello, my attachment 485 [details] in Comment 21 is the correct GDB backtrace of X?
Nothing about this bug?
Assigning to maintainer now that our maintainer's database has an entry for
this package. Please assign back to firstname.lastname@example.org in case of a mistake
Version set to 1 as it's a pre-Mageia 1 issue.
Hello Samuel, thanks.
But I use Mageia Cauldron, and this bug continue in the package.
I will change version to Cauldron.
Created attachment 893 [details]
Output from lspci | grep SiS
Share the list of SiS driven devices on my laptop, which faces the issues described in this bug report.
I had the same problem on Mageia 1 with sis 672 chipset: Playing video with VLC or mlayer in full-screen mode crashed the X-server.
Changing the players video output from xv to x11 brought improvement.
However, there seems to be exactly the same issue with ubuntu but somebody already wrote a patch for the sisimedia driver:
I don't know much about patching drivers and compiling kernels, so it would be really cool if one of the maintainers could have a look at that. Thanks!
I get this from any player on any setting, full screen not required.
I'm running : VGA compatible controller: VIA Technologies, Inc. CN896/VN896/P4M900 [Chrome 9 HC] (rev 01)
Pinging, because nothing has happened with this report for more than 3 months, it still has the status NEW or REOPENED.
I can workaround the issue changing the video output in X11 with SMPlayer or VLC: cannot do the same in Dragon Player (removed) Mageia 2 beta 3 VGA compatible controller: Silicon Integrated Systems [SiS] 771/671 PCIE VGA Display Adapter (rev 10)
This bug was filed against cauldron, but we do not have cauldron at the moment.
Please report whether this bug is still valid for Mageia 2.
I changed my machine, I can not return a feedback about this bug.
(In reply to comment #33)
> I changed my machine, I can not return a feedback about this bug.
(In reply to comment #34)
> Same here.
Thanks for replying.
Closing as OLD
Anyone still suffering from this bug: feel free to reopen and provide additional information