Ubuntu
kdenetwork package

Kopete-KDE4 crashes after changing behavior settings

Bug #199984 reported by ZdadrDeM
16
Affects Status Importance Assigned to Milestone
kdenetwork (Ubuntu)
Invalid
Low
Unassigned

Bug Description

After changing the options in Settings --> Behavior --> General Kopete crashes with signal 6
By the way: Kopete doesn't remember the option "Open messages instantly". After the crash no option is checked but Kopete uses the message queue.

Kubuntu 7.10
KDE: 4.0.2 (from kubuntu.org)

the konsole output:

user@pc:~/.kde4/share/config$ /usr/lib/kde4/bin/kopete
user@pc:~/.kde4/share/config$ CLIENT: Task: Task::done()
CLIENT: Task: emitting finished
kopete(16181) StatisticsContact::onlineStatusChanged: statistics - status change for "ICQProtocol:2XXXXXXXX:2XXXXXXXX" : "50"
ASSERT failure in QList<T>::operator[]: "index out of range", file /usr/include/qt4/QtCore/qlist.h, line 394
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = kopete path = <unknown> pid = 16181
sock_file=/home/user/.kde4/socket-zdadrdem/kdeinit4__0
kdeinit4: Got EXEC_NEW '/usr/lib/kde4/lib/kde4/libexec/drkonqi' from socket.
kdeinit4: preparing to launch /usr/lib/kde4/lib/kde4/libexec/drkonqi
kdeinit4: PID 16267 terminated.

Revision history for this message
Lydia Pintscher (lydia-pintscher) wrote :

Can you please try to reporduce the crash with KDE 4.0.3 when it is released?
Please try to get a backtrace if it is reproducable.

The problem with the message settings is known.

Thank you.

Changed in kdenetwork-kde4:
status: New → Incomplete
Revision history for this message
ZdadrDeM (zdadr-dem) wrote :

Hi,
the crash still happens every time I try to change the message behaviour.
I attached a strace output.

Revision history for this message
Lydia Pintscher (lydia-pintscher) wrote :

Thank you.

(The problem with message handling is fixed for me now btw.)

Changed in kdenetwork-kde4:
importance: Undecided → Low
status: Incomplete → Triaged
Revision history for this message
ZdadrDeM (zdadr-dem) wrote :

Hi,
yes, now the option stays checked, but there is still a problem: it opens the messages instantly AND displays the window to accept or ignore the message.
I think this is another bug.

Revision history for this message
Harald Sitter (apachelogger) wrote :

Please report a new bug if it is one :)
Clsoing this one as the original issue seems to be fixed.

Changed in kdenetwork-kde4:
status: Triaged → Fix Released
Revision history for this message
ZdadrDeM (zdadr-dem) wrote :

No, for me it is not fixed. Kopete still crashes after changing the behaviour settings. Now the options stays checked, but it still chrashes.

Revision history for this message
BlackFire (criscio) wrote :

I can confirm. Crashes as soon as I click apply, and does not actually cares about the configuration since when I restart it's still creating popup.
Any workaround? I't annoying (plus, the OSD is now on the top of the screen instead of the bottom :P )

ZdadrDeM (zdadr-dem)
Changed in kdenetwork-kde4:
status: Fix Released → Confirmed
Revision history for this message
Lydia Pintscher (lydia-pintscher) wrote :

Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down the problem.

Changed in kdenetwork-kde4:
status: Confirmed → Incomplete
Revision history for this message
BlackFire (criscio) wrote :

I tried to follow the instructions but my debugging fu are not so good. As soon as I start kopete from gdb it seems to detach and gdb reports a "program exited normally". I don't know if it's forking or what, but gdb simply loses it.
I need guidance on how to perform a more complete backtrace :(

I've attached the resulting output, but there's nothing new (and a typo :) ).

Revision history for this message
dberger (cc-tresh) wrote :

I can reproduce the same problem under KDE 4.0.3, using Kopete 0.50.1. I also have the same problem as BlackFire. As soon as i start kopete under gdb it detaches and gdb somehow loses it.

I added my strace output, maybe it has something conclusive in it.

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

I can't reproduce this with KDE 4.1.0. Can anyone else?

Revision history for this message
Paco Ros (fros-bitel) wrote :

Mine hangs when I click "Preferences" menu option and leaves a eternally "wait" cursor

Even if I kill -9 kopete it leaves a defunct process and doesn't start again until a full system reboot is performed.
Using KDE 4.1.1 from ppa.launchpad.net/kubuntu-members-kde4.

After various Google searches it seems not to happen to anybody else, so, any help will be appreciated and if you need more information, please, ask for it.

Thank you.

Revision history for this message
Giuseppe Pennisi (giupenni78) wrote :

I have upgrade to kde 4.1.1 but the problem persists.

gp

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Could anybody who can reproduce this install kdenetwork-kde4-dbg and get a backtrace?
After that we need to forward the bug on to KDE.

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Migrating bug to Intrepid package name.

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in kdenetwork:
status: Incomplete → Invalid
Revision history for this message
Paco Ros (fros-bitel) wrote :

The problem happens on PCs with Web Cam or TV card installed.
Kopete tries to open a capture device and hangs.

Same KDE 4.1.1 Kopete is running fine in another PC without TV card.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.