| Author |
Message |
|
|
|
Post subject: Kopete crash by connect with msn.
 Posted: Nov 09, 2007 - 01:49 PM
|
|
Joined: Dec 05, 2006
Posts: 23
Status: Offline
|
|
Hello,
I have reported this as bug to Debian, but they dont care as I use sidux.
I find that Ubuntu have the same problem and make a new version from: kdelibs4c2a_3.5.8-0ubuntu3_i386.deb
bugreport:http://www.kdedevelopers.org/node/3041
Some one have a solution to this on sidux?
Best regards. |
|
|
| |
|
|
|
 |
|
|
|
Post subject: RE: Kopete crash by connect with msn.
Posted: Nov 09, 2007 - 04:44 PM
|
|
Joined: Dec 02, 2006
Posts: 1905
Status: Offline
|
|
| Kopete works for me with MSN |
|
|
| |
|
|
|
|
|
|
|
Post subject: Re: Kopete crash by connect with msn.
Posted: Nov 09, 2007 - 06:02 PM
|
|
Joined: Nov 30, 2006
Posts: 3436
Location: Budapest
Status: Offline
|
|
|
|
|
|
|
|
|
Post subject:
Posted: Nov 09, 2007 - 06:58 PM
|
|
Joined: Dec 05, 2006
Posts: 23
Status: Offline
|
|
|
|
|
|
|
|
|
Post subject:
Posted: Nov 09, 2007 - 08:55 PM
|
|
Joined: Nov 30, 2006
Posts: 3436
Location: Budapest
Status: Offline
|
|
ok, I see, was looking for the wrong package.
He is right that reportbug is the right way to go, because it gives all the system infos he wants. He might not even be rude, it is possible, that he does not know sidux or that it is based on Debian. reportbug gives him the distribution which is lenny/sid in our case, your apt-cache policy (might be unstable 500 if you do not have a /etc/apt/preferences) and the installed version of the package including the installed dependencies/recommends/suggestions. That it is sidux he might notice by the version number of the kernel, but he will not be interested in that.
It will crudely look like that:
Code:
Subject: kdebase: kdfja
Package: kdebase
Version: 4:3.5.8.dfsg.1-1
Severity: normal
*** Please type your report below this line ***
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.23.1-slh-smp-19 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
apt-get install reportbug
Luckily there is now a graphical interface with reportbug as well:
apt-get install reportbug-ng
hubi |
_________________
Bonitas stultitiaque sodales sunt.
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Nov 10, 2007 - 07:44 AM
|
|
Joined: Dec 05, 2006
Posts: 23
Status: Offline
|
|
Ok hubi,
what do you think is the best, make a new report or complete this in thr right way?
ferenc. |
|
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Nov 10, 2007 - 02:10 PM
|
|
Joined: Nov 30, 2006
Posts: 3436
Location: Budapest
Status: Offline
|
|
ferenc,
just try to add your system info to the existing bug report, so that the guy sees that you are running Debian. I did it just with reportbug, and put --paranoid as option, because you don't want to send anything. There must be another way as well to retrieve this information, but I don't know how actually.
What also might help: start kopete in a console and see if there is an output when it crashes. This is helpful as well. If there is nothing try start kopete this way:
Code:
strace -o backstrace.kopete.txt kopete
All system calls are saved in this text file 'backstrace.kopete.txt' (can become big) which is in ~/ in this case, and when it crashes it is logged what has happened.
The parts in the end when kopete is crashing is important for the developer. You can send that as file as well, just try to have kopete crashed as soon as possible, or just copy the relevant pieces at the end of this file into a new text file. You don't want to send a 100 MB text file as bug report 
Greetings,
hubi |
_________________
Bonitas stultitiaque sodales sunt.
|
| |
|
|
|
|
|
|
