Bug#910731: kaddressbook: crashes at startup
Hello Sandro, Am 05.03.19 um 00:43 schrieb Sandro Knauß: > Btw. please use the bugnumber-qu...@bugs.debian.org rarely, because than > maintainers like me don't gets any mails, that's why I missed your > conversation. Sorry for using -quiet - Pino Toscano made me already aware to avoid -quiet. One other thing that may be related is that I found using BUGNUMBER-submitter@ very convenient, but I have the impression that then the submitter gets by default the BUGNUMBER-quiet@ as answer to address. Kind regards, Bernhard
Processed: Re: Bug#910731: kaddressbook: crashes at startup
Processing commands for cont...@bugs.debian.org: > retitle 910731 KAdressebook missing to dependency on akonadi Bug #910731 [kaddressbook] kaddressbook: crashes at startup Changed Bug title to 'KAdressebook missing to dependency on akonadi' from 'kaddressbook: crashes at startup'. > thanks Stopping processing here. Please contact me if you need assistance. -- 910731: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910731 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#910731: kaddressbook: crashes at startup
Hey, okay the initial issue is solved, that is great. Btw. please use the bugnumber-qu...@bugs.debian.org rarely, because than maintainers like me don't gets any mails, that's why I missed your conversation. > > I suppose this means that kaddressbook should depend on akonadi-server. thanls for spotting this, I'll fix that soon. Often people use complete kdepim that's why these inter kdepim dependencies are sometimes not complete. hefee signature.asc Description: This is a digitally signed message part.
Bug#910731: kaddressbook: crashes at startup
Hello Francesco, I missed that, sorry about that. On Mon, 26 Nov 2018 15:22:39 +0100 =?utf-8?Q?Francesco_Potort=C3=AC?= wrote: > >can you still observe the crash, or got it fixed by updates > >in mid October? (Like mentioned in #910581) > > It does not crash any more, ... So the initial issue could be seen as resolved. > ...but it shows an error message at startup: > > The Akonadi personal information management service is not running. > This application cannot be used without it. [Start] > > If I press the [Start] button, apparently nothing happens. > > When I launch kaddressbook from a terminal, I see this error message: > > org.kde.pim.akonadicore: Unable to execute akonadi_control, falling back to > D-Bus auto-launch > > appearing twice after startup, and once more each time I press the > [Start] button. > > I suppose this means that kaddressbook should depend on akonadi-server. > > After installing akonadi-server and launching kaddressbook I see a > message telling something about setup, then a new error screen with > message: > > Cannot connect to the Personal Information management service. There > are no Akonadi Agents available. Please verify your KDE PIM > Installation. [Details...] > > On the terminal, I see these messages: > > Connecting to deprecated signal > QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) > akonadi.collectionattributetable OK > akonadi.collectionmimetyperelation OK > akonadi.collectionpimitemrelation OK > akonadi.collectiontableOK > akonadi.flagtable OK > akonadi.mimetypetable OK > akonadi.parttable OK > akonadi.parttypetable OK > akonadi.pimitemflagrelationOK > akonadi.pimitemtable OK > akonadi.pimitemtagrelation OK > akonadi.relationtable OK > akonadi.relationtypetable OK > akonadi.resourcetable OK > akonadi.schemaversiontable OK > akonadi.tagattributetable OK > akonadi.tagremoteidresourcerelationtable OK > akonadi.tagtable OK > akonadi.tagtypetable OK > Connecting to deprecated signal > QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) > org.kde.pim.akonadicore: "" > org.kde.pim.akonadicore: Job error: "" for collection: QVector() > > Pressing the [Details...] button produces no apparent effect. > > After killing and restarting kaddressbook, the initial setup message > does not appear any more, while the error message screen is still > there. Again, pressing the [Details...] button has no visible effect. > No messages are produced on the terminal > This error seems not directly related to the crash and would have maybe deserved its own bug report, as it may be a problem in a different package. Nevertheless, I cannot reproduce this error in a fresh Buster amd64 VM. Instead I get the error described in #910902, that can be worked around by just creating the missing directory. Therefore I am sorry and need to ask again if you still observe this error? Kind regards, Bernhard #910902 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910902 signature.asc Description: OpenPGP digital signature
Bug#910731: kaddressbook: crashes at startup
>can you still observe the crash, or got it fixed by updates >in mid October? (Like mentioned in #910581) It does not crash any more, but it shows an error message at startup: The Akonadi personal information management service is not running. This application cannot be used without it. [Start] If I press the [Start] button, apparently nothing happens. When I launch kaddressbook from a terminal, I see this error message: org.kde.pim.akonadicore: Unable to execute akonadi_control, falling back to D-Bus auto-launch appearing twice after startup, and once more each time I press the [Start] button. I suppose this means that kaddressbook should depend on akonadi-server. After installing akonadi-server and launching kaddressbook I see a message telling something about setup, then a new error screen with message: Cannot connect to the Personal Information management service. There are no Akonadi Agents available. Please verify your KDE PIM Installation. [Details...] On the terminal, I see these messages: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) akonadi.collectionattributetable OK akonadi.collectionmimetyperelation OK akonadi.collectionpimitemrelation OK akonadi.collectiontableOK akonadi.flagtable OK akonadi.mimetypetable OK akonadi.parttable OK akonadi.parttypetable OK akonadi.pimitemflagrelationOK akonadi.pimitemtable OK akonadi.pimitemtagrelation OK akonadi.relationtable OK akonadi.relationtypetable OK akonadi.resourcetable OK akonadi.schemaversiontable OK akonadi.tagattributetable OK akonadi.tagremoteidresourcerelationtable OK akonadi.tagtable OK akonadi.tagtypetable OK Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) org.kde.pim.akonadicore: "" org.kde.pim.akonadicore: Job error: "" for collection: QVector() Pressing the [Details...] button produces no apparent effect. After killing and restarting kaddressbook, the initial setup message does not appear any more, while the error message screen is still there. Again, pressing the [Details...] button has no visible effect. No messages are produced on the terminal -- Francesco Potortì (ricercatore)Voice: +39.050.621.3058 ISTI - Area della ricerca CNR Mobile: +39.348.8283.107 via G. Moruzzi 1, I-56124 Pisa Skype: wnlabisti (entrance 20, 1st floor, room C71) Web:http://fly.isti.cnr.it
Bug#910731: kaddressbook: crashes at startup
Hello Francesco, can you still observe the crash, or got it fixed by updates in mid October? (Like mentioned in #910581) If it is fixed that bug might be closed. Kind regards, Bernhard
Bug#910731: kaddressbook: crashes at startup
Hello Francesco, can you still observe the crash, or got it fixed by updates in mid October? (Like mentioned in #910581) If it is fixed that bug might be closed. Kind regards, Bernhard
Bug#910731: kaddressbook: crashes at startup
Hello Francesco, > Unfortunately, the 17.12.3-1 version is no more available in the > archive, apart from the hurd architecture. So I will wait for a newer > version (I am not going to compile it myself). If one needs old package versions you have a look at snapshot.debian.org [1]. As far as I see you might get away with just installing the two packages [2] and [3] manually. [1] http://snapshot.debian.org/package/kontactinterface/ [2] http://snapshot.debian.org/archive/debian/20180401T155009Z/pool/main/k/kontactinterface/libkf5kontactinterface-data_17.12.3-1_all.deb [3] http://snapshot.debian.org/archive/debian/20180401T155009Z/pool/main/k/kontactinterface/libkf5kontactinterface5_17.12.3-1_amd64.deb (I have not tested it, I am not using that part of KDE.) Kind regards, Bernhard
Bug#910731: kaddressbook: crashes at startup
>Hello Francesco, >just came around and found this could be related to that >bug report [1], related to package libkf5kontactinterface5. > >Kind regards, >Bernhard > >[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910581 I see. Thank you. Unfortunately, the 17.12.3-1 version is no more available in the archive, apart from the hurd architecture. So I will wait for a newer version (I am not going to compile it myself). Sincerely -- Francesco Potortì (ricercatore)Voice: +39.050.621.3058 ISTI - Area della ricerca CNR Mobile: +39.348.8283.107 via G. Moruzzi 1, I-56124 Pisa Skype: wnlabisti (entrance 20, 1st floor, room C71) Web:http://fly.isti.cnr.it
Bug#910731: kaddressbook: crashes at startup
Hello Francesco, just came around and found this could be related to that bug report [1], related to package libkf5kontactinterface5. Kind regards, Bernhard [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910581
Bug#910731: kaddressbook: crashes at startup
Package: kaddressbook Version: 4:17.12.3-1 Severity: grave This is a mate-based Debian testing system. I installed kaddressbook, which loaded a host of KDE libraries, but I cannot make it work: $ kaddressbook KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = kaddressbook path = /usr/bin pid = 11120 KCrash: Arguments: /usr/bin/kaddressbook KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 Warning: connect() failed: : No such file or directory KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi directly kf5.kwidgetsaddons: Invalid pixmap specified. The popup says: Executable: kaddressbook PID: 11120 Signal: Segmentation fault (11) Time: 10/10/18 14:35:10 and the backtrace is: Application: KAddressBook (kaddressbook), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0dc302fa80 (LWP 11120))] Thread 6 (Thread 0x7f0daad23700 (LWP 11128)): #0 0x7f0dcdf87739 in __GI___poll (fds=0x7f0d9c003110, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f0dca892e46 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0dca892f6c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0dce4b124b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f0dce45e25b in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f0dce2ad176 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f0dcdbcf545 in () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f0dce2b6d47 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f0dcbb99f2a in start_thread (arg=0x7f0daad23700) at pthread_create.c:463 #9 0x7f0dcdf91edf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f0dab575700 (LWP 11127)): #0 0x7f0dcbb9fe6c in futex_wait_cancelable (private=, expected=0, futex_word=0x563d0b3b4fc0) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f0dcbb9fe6c in __pthread_cond_wait_common (abstime=0x0, mutex=0x563d0b3b4f70, cond=0x563d0b3b4f98) at pthread_cond_wait.c:502 #2 0x7f0dcbb9fe6c in __pthread_cond_wait (cond=0x563d0b3b4f98, mutex=0x563d0b3b4f70) at pthread_cond_wait.c:655 #3 0x7f0db856790b in () at /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #4 0x7f0db8567637 in () at /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #5 0x7f0dcbb99f2a in start_thread (arg=0x7f0dab575700) at pthread_create.c:463 #6 0x7f0dcdf91edf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f0dabdc7700 (LWP 11126)): #0 0x7f0dcbb9fe6c in futex_wait_cancelable (private=, expected=0, futex_word=0x563d0b5f8da0) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f0dcbb9fe6c in __pthread_cond_wait_common (abstime=0x0, mutex=0x563d0b5f8d50, cond=0x563d0b5f8d78) at pthread_cond_wait.c:502 #2 0x7f0dcbb9fe6c in __pthread_cond_wait (cond=0x563d0b5f8d78, mutex=0x563d0b5f8d50) at pthread_cond_wait.c:655 #3 0x7f0db856790b in () at /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #4 0x7f0db8567637 in () at /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #5 0x7f0dcbb99f2a in start_thread (arg=0x7f0dabdc7700) at pthread_create.c:463 #6 0x7f0dcdf91edf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f0db9d33700 (LWP 11123)): #0 0x7f0dcdf87739 in __GI___poll (fds=0x563d0b2ba670, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f0dca892e46 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0dca8931d2 in g_main_loop_run () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0dbbcd97b6 in () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x7f0dca8bb135 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f0dcbb99f2a in start_thread (arg=0x7f0db9d33700) at pthread_create.c:463 #6 0x7f0dcdf91edf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f0dba585700 (LWP 11122)): #0 0x7f0dcdf87739 in __GI___poll (fds=0x563d0b2988f0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f0dca892e46 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0dca892f6c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0dca892fb1 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f0dca8bb135 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f0dcbb99f2a in start_thread (arg=0x7f0dba585700) at pthread_create.c:463 #6 0x7f0dcdf91edf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f0dc302fa80 (LWP 11120)): [KCrash Handler] #4 0x7f0dce1e7438 in vtable for __cxxabiv1::__si_class_type_info () at /usr/lib/x86
