[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#477115: marked as done ([kmahjongg] Kmahjongg doesn't run : fatal error during launch)

Your message dated Fri, 16 May 2008 11:21:07 +0200
with message-id <20080516092107.GA6782@pryan.sytes.net>
and subject line Re: Bug#477115: [kmahjongg] Kmahjongg doesn't run : fatal error during launch
has caused the Debian Bug report #477115,
regarding [kmahjongg] Kmahjongg doesn't run : fatal error during launch
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
477115: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=477115
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: kmahjongg
Version: 4:4.0.66+svn791114-1
Severity: grave

--- Please enter the report below this line. ---

When I try to run kmahjongg, the program crashes immediately.

The console output is :
$ kmahjongg
KCrash: Application 'kmahjongg' crashing...

KCrash output is :

A Fatal Error Occurred
The application KMahjongg (kmahjongg) crashed and caused the signal 11 (SIGSEGV). 


Application: KMahjongg (kmahjongg), signal SIGSEGV
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb60c1720 (LWP 11969)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()
[Current thread is 0 (process 11969)]

Thread 1 (Thread 0xb60c1720 (LWP 11969)):
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb6a0fb00 in nanosleep () from /lib/i686/cmov/libc.so.6
#2  0xb6a0f937 in sleep () from /lib/i686/cmov/libc.so.6
#3  0xb7a5537c in ?? () from /usr/lib/libkdeui.so.5
#4  0x00000001 in ?? ()
#5  0x00000000 in ?? ()
#0  0xffffe410 in __kernel_vsyscall ()

--- System information. ---
Architecture: i386
Kernel: Linux 2.6.24-1-686-bigmem

Debian Release: lenny/sid
500 unstable ftp.fr.debian.org
500 testing security.debian.org
500 testing ftp.fr.debian.org
1 experimental ftp.fr.debian.org

--- Package information. ---
Depends (Version) | Installed
====================================================-+-==========================
kdebase-runtime | 4:4.0.68+svn794641-1
kdegames-mahjongg-data (>= 4:4.0.66+svn791114-1) | 4:4.0.66+svn791114-1
kdelibs5 (>= 4:4.0.66+svn790271-1) | 4:4.0.68+svn794641-1
libc6 (>= 2.7-1) | 2.7-10
libkdegames4 | 4:4.0.66+svn791114-1
libqt4-gui (>= 4.4.0~beta1) | 4.4.0~rc1-4
libqtcore4 (>= 4.4.0~beta1) | 4.4.0~rc1-4
libstdc++6 (>= 4.1.1-21) | 4.3.0-3

--- End Message ---
--- Begin Message --- 
On Sun, Apr 20, 2008 at 11:41:39PM +0200, Laurent Vromman wrote:
> Package: kmahjongg
> Version: 4:4.0.66+svn791114-1
> Severity: grave
>
> --- Please enter the report below this line. ---
>
> When I try to run kmahjongg, the program crashes immediately.
>
> The console output is :
> $ kmahjongg
> KCrash: Application 'kmahjongg' crashing...
>
> KCrash output is :
>
> A Fatal Error Occurred
>
> The application KMahjongg (kmahjongg) crashed and caused the signal 11  
> (SIGSEGV).
>

Try updating to latest Qt4 in unstable and kdegames in experimental (4.0.72),
if it still does not work, try renaming temporaly you .kde4 to something like
.kde4-old and try again, I'm almost sure it'll work then. I did have this same
problem until I removed my corrupted .kde4.
If you do not have any valuable configuration under .kde4 you can just remove
it.

Ana

--- End Message ---
Reply to: