Bug 492518 - Frozen-bubble 2.2.0 does not start.
Summary: Frozen-bubble 2.2.0 does not start.
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: frozen-bubble
Version: 10
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Matthias Saou
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-03-27 08:14 UTC by atidem
Modified: 2009-03-30 09:28 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-03-28 08:42:14 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description atidem 2009-03-27 08:14:02 UTC
Description of problem:
If I try to run frozen-bubble from gnome terminal or via Applications menu, it does not run.

Version-Release number of selected component (if applicable):  2.2.0


How reproducible:


Steps to Reproduce:
1. Applications
2. Games
3. Frozen Bubble

OR

1. gnome-terminal
2. $ frozen-bubble
  
Actual results:
It stops while loading on: [SDL Init]

Expected results:
Play a game! :-)

Additional info:
Installed packages for dependencies:
a) 4:perl-5.10.0-56.fc10.i386 
b) SDL-1.2.13-7.fc10.i386 
c) SDL_image-1.2.6-6.fc9.i386
d) SDL_mixer-1.2.8-9.fc10.i386 
e) perl-SDL-2.1.3-9.fc9.i386 
f) SDL_Pango-0.1.2-8.i386 

c AND e $releasever = 9 ?
f $arch = ??

Comment 1 atidem 2009-03-28 08:42:14 UTC
(In reply to comment #0)
"Magically", last update of fedora_10 makes frozen-bubble run on my machine. Don't ask me why! ;-)

Comment 2 atidem 2009-03-28 08:45:59 UTC
I don't know if it is relevant but from /var/log/yum.log the latest package updated is libX11-1.1.5-2.fc10.i386.

Bye!

Comment 3 Matthias Saou 2009-03-30 09:28:40 UTC
(In reply to comment #2)
> I don't know if it is relevant but from /var/log/yum.log the latest package
> updated is libX11-1.1.5-2.fc10.i386.

Apparently, the libX11-1.1.5-1.fc10 package had broken a lot of things, and this update fixes it, so it's not that surprising. Glad things work again, though ;-)


Note You need to log in before you can comment on or make changes to this bug.