FS#22449 - [frozen-bubble] - Crashes and terminates my KDE session

Attached to Project: Arch Linux
Opened by Musikolo (Musikolo) - Saturday, 15 January 2011, 13:30 GMT
Last edited by Andrea Scarpino (BaSh) - Wednesday, 16 March 2011, 22:30 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan Alexander Steffens (heftig)
Architecture i686
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description: When I launch frozen-bubble the screen gets blank as if it where to start the game, but then it crashes and my KDE session terminates. I've tried to get some sort of log, but it has turned out to be impossible for me. Suprisingly, it works on my x86_64 PC.

Additional info:
* package version(s):
[musikolo@MyPC ~]$ pacman -Qi frozen-bubble
Name : frozen-bubble
Version : 2.2.0-3
URL : http://www.frozen-bubble.org
Licenses : GPL2
Groups : None
Provides : None
Depends On : sdl_perl sdl_mixer perl-locale-gettext sdl_pango
Optional Deps : None
Required By : None
Conflicts With : None
Replaces : None
Installed Size : 29076.00 K
Packager : Jan "heftig" Steffens <jan.steffens@gmail.com>
Architecture : i686
Build Date : Sat 27 Nov 2010 04:20:50 PM CET
Install Date : Sat 15 Jan 2011 02:03:05 PM CET
Install Reason : Explicitly installed
Install Script : No
Description : A game in which you throw colorful bubbles and build groups to destroy the bubbles

[musikolo@MyPC ~]$ sudo pacman -Syu
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
:: Starting full system upgrade...
there is nothing to do

Steps to reproduce:
1.- Login KDE
2.- Open a Konsole
3.- Type 'frozen-bubble' and press Enter.
4.- It crashes and terminates your KDE session.
This task depends upon

Closed by  Andrea Scarpino (BaSh)
Wednesday, 16 March 2011, 22:30 GMT
Reason for closing:  Fixed
Additional comments about closing:  frozen-bubble 2.2.1beta1-1
savage-dri 7.10.1-1
xf86-video-savage 2.3.2-1
Comment by Jan de Groot (JGC) - Thursday, 20 January 2011, 23:51 GMT
Please provide Xorg log files and details about system configuration. It's very likely that frozen-bubble triggers something that makes X crash.
Comment by Musikolo (Musikolo) - Saturday, 22 January 2011, 12:20 GMT
Hi,

I have tried to find something that could help and, in the end, I did it. The problem seems to be what you said, i.e., that X is crashing. Here you have the messages written in /var/log/everything.log after launching frozen-bubble: http://aur.pastebin.com/VZ4r2Eiq

You also have my xorg.conf file, so you know my computer settings. To be more precise, here you the result of issuing lspci -v: http://aur.pastebin.com/v2E5FwjM

I have also tried, using the next switches unsuccessfully:
+ --no-fullscreen
+ --no-sound
+ --very-slow-machine

I hope a solution can be found soon.

Best regards! ;-)
Comment by Musikolo (Musikolo) - Tuesday, 01 February 2011, 21:23 GMT
The same problem persists:

[musikolo@MyPC ~]$ pacman -Q xorg-server kernel26 savage-dri xf86-video-savage
xorg-server 1.9.3.901-1
kernel26 2.6.37-5
savage-dri 7.10-1
xf86-video-savage 2.3.1-4

I hope a solution is found soon!
Comment by Jan Alexander Steffens (heftig) - Wednesday, 02 February 2011, 02:59 GMT
The Xorg log file of a crash would be helpful.
Comment by Musikolo (Musikolo) - Wednesday, 02 February 2011, 21:12 GMT
Hi,

attached you have the Xorg.0.log file as requested. In order to get a clean file, I have removed all log file (/var/log/*) before launching frozen-bubble from konsole. As you can see, there is nothing weird at all, or at least, I haven't found anything interesting. The only interesting thing I have found is that if a create a brand new xorg.conf file (by issuing 'X -configure' as root) and replace the driver 'savage' for 'vesa', frozen-bubble works (although it looks horrible). Thus, I think the problem really relies on the driver, rather on the Xorg server itself. What do you think?

Beside all the above, I have also tried using a new user, logged in KDE and started frozen-bubble, but the problem persists. So, I would assume there is nothing wrong in my personal settings.

If needed anything else, please, just let me know.

Best regards!
Comment by Jan de Groot (JGC) - Wednesday, 02 February 2011, 21:42 GMT
The Xorg.0.log.old file after resuming from a crash would be more useful I think. I think this is just a limitation or bug in the savage DRI driver. Savage hardware is not so common these days, most development is done on nouveau, intel and ati drivers.
Comment by Musikolo (Musikolo) - Wednesday, 02 February 2011, 22:33 GMT
Since I removed all log files before launching frozen-bubble, there is no other Xorg.* file, just the one I have attached. The crash in fronzen-bubble terminates my user session in Xorg server, but it seems not to restart, I think.

I know the savage driver is quite stack mainly because it's quite old and not very common nowadays, but it should be maintained over time anyway.

If you have any sequence of steps you want me to do, please, let me know. I'm all ears!
Comment by Jan de Groot (JGC) - Wednesday, 02 February 2011, 22:39 GMT
You could try disabling desktop effects to see if that changes anything.
Comment by Musikolo (Musikolo) - Wednesday, 02 February 2011, 23:07 GMT
I already had it disabled, in fact it's been this way since I installed KDE 4.x. My poor computer doesn't like them much, mainly because the graphic card can't deal with effects gracefully.
Comment by Musikolo (Musikolo) - Wednesday, 16 March 2011, 22:27 GMT
Hi,

In the end, the problem has disappeared in the last update. Currently, I have the following verions of frozen-bubble and savage driver:

[musikolo@MyPC ~]$ pacman -Q frozen-bubble
frozen-bubble 2.2.1beta1-1
[musikolo@MyPC ~]$ pacman -Qs savage
local/savage-dri 7.10.1-1
Mesa DRI drivers for S3 Sraphics/VIA Savage
local/xf86-video-savage 2.3.2-1 (xorg-drivers xorg)
X.org savage video driver
[musikolo@MyPC ~]$

Thanks a lot!

Loading...