[plasmashell] [Bug 483044] Plasmashell crashes inPipeWireSourceStream::~PipeWireSourceStream() after relogin
https://bugs.kde.org/show_bug.cgi?id=483044 --- Comment #4 from Andreas Hencke --- @Nate Graham: No, I did nothing like that. -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 481402] question mark icons shown in systray when oxygen icon theme
https://bugs.kde.org/show_bug.cgi?id=481402 Andreas Hencke changed: What|Removed |Added CC||andreas.hen...@mailbox.org --- Comment #3 from Andreas Hencke --- Same here (I'm the 2nd guy on the thread mentioned by firewalker). When I go to systemsettings --> colors and designs --> icons and change to Adwaita --> apply then instantanously back to Oxygen --> apply the icons (monochrome in black) appear when hovering with the mousepointer. One'll have to redo after a reboot. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483044] Plasmashell crashes after relogin
https://bugs.kde.org/show_bug.cgi?id=483044 --- Comment #1 from Andreas Hencke --- Created attachment 166833 --> https://bugs.kde.org/attachment.cgi?id=166833=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483044] New: Plasmashell crashes after relogin
https://bugs.kde.org/show_bug.cgi?id=483044 Bug ID: 483044 Summary: Plasmashell crashes after relogin Classification: Plasma Product: plasmashell Version: 6.0.1 Platform: Arch Linux OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: andreas.hen...@mailbox.org Target Milestone: 1.0 Application: plasmashell (6.0.1) Qt Version: 6.6.2 Frameworks Version: 6.0.0 Operating System: Linux 6.7.9-arch1-1 x86_64 Windowing System: Wayland Distribution: "Arch Linux" DrKonqi: 6.0.1 [CoredumpBackend] -- Information about the crash: The screen was locked after a period of inactivity. After login plasmashell crashed immediatelly . The crash can be reproduced sometimes. -- Backtrace (Reduced): #5 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 #6 0x76890e6ab393 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78 #7 0x76890e65a6c8 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x76890e6424b8 in __GI_abort () at abort.c:79 #9 0x76890e643395 in __libc_message_impl (fmt=fmt@entry=0x76890e7bb2ea "%s\n") at ../sysdeps/posix/libc_fatal.c:132 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kpackagekit] [Bug 269791] KPackageKit: an unexpected error
https://bugs.kde.org/show_bug.cgi?id=269791 Andreas Hencke changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kpackagekit] [Bug 265119] KPackage Kit:Unexpected internal system error occured after I clicked the update-button
https://bugs.kde.org/show_bug.cgi?id=265119 Andreas Hencke changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 413740] Korganizer crashes when setting categories colors
https://bugs.kde.org/show_bug.cgi?id=413740 --- Comment #10 from Andreas Hencke --- No more problems so far. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 458116] Articles spilling from one feed to another
https://bugs.kde.org/show_bug.cgi?id=458116 --- Comment #21 from Andreas Hencke --- (In reply to Colin J Thomson from comment #20) > Confirmed it is happening again after the update to 5.99, frameworks 5.98 > was fine. Yes, received the update to 5.99 today and straight afterwards it happens again! Anoying. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 417195] Kontact crashes when opening a special mail
https://bugs.kde.org/show_bug.cgi?id=417195 Andreas Hencke changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #2 from Andreas Hencke --- No, I can't reproduce the issue anymore. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 417072] Kontact crashes again for no apparent reason
https://bugs.kde.org/show_bug.cgi?id=417072 Andreas Hencke changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #3 from Andreas Hencke --- No, I can't reproduce the issue anymore. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 415997] Kontact had crashed when I returned to machine
https://bugs.kde.org/show_bug.cgi?id=415997 Andreas Hencke changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #3 from Andreas Hencke --- I can't reproduce the issue anymore. Thank you for looking after the issue! -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 411687] Kontact crashes when I click somewhere
https://bugs.kde.org/show_bug.cgi?id=411687 Andreas Hencke changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #2 from Andreas Hencke --- No, I can't reproduce the issue with Kontact 5.21.1 -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 458116] Articles spilling from one feed to another
https://bugs.kde.org/show_bug.cgi?id=458116 --- Comment #15 from Andreas Hencke --- (In reply to Colin J Thomson from comment #14) > I'll tentatively say with today's update of Frameworks to 5.98 from > zawertun's COPR this has fixed it for me on this Fedora 36 box. Seemed to be fixed with the Frameworks update on my arch machine. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 458912] New: Akregator fetches old feeds and stores them in wrong news folders
https://bugs.kde.org/show_bug.cgi?id=458912 Bug ID: 458912 Summary: Akregator fetches old feeds and stores them in wrong news folders Product: akregator Version: 5.21.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kontact plugin Assignee: kdepim-b...@kde.org Reporter: andreas.hen...@mailbox.org Target Milestone: --- SUMMARY Since about two weeks, akregator fetches old feeds and stores them in wrong news folders. Today eg. I had to delete about 500 old (already read) feeds stored in wrong folders. For example 198 feeds from https://www.swr3.de/~podcast/musik/die-groessten-hits-und-ihre-geschichte/index.xml stored in the folder forum.archlinux.de. The feeds fetched vary and the folders where they are stored, too. Also the amount of fetched feeds vary. STEPS TO REPRODUCE 1. Start Kontact/Akregator 2. Wait 3. OBSERVED RESULT Somtime, it takes minutes or hours akregator starts fetching feeds. For the most part the machine is in an idle state when this happens. I observed that some folders are marked in red (no connection) but these are not the folders where old feeds are fetched from nor stored. This happens at different times EXPECTED RESULT Works normally SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 422159] Akonadi crashes often and can't be restarted
https://bugs.kde.org/show_bug.cgi?id=422159 Andreas Hencke changed: What|Removed |Added Attachment #128899|0 |1 is obsolete|| --- Comment #6 from Andreas Hencke --- Created attachment 128920 --> https://bugs.kde.org/attachment.cgi?id=128920=edit Here is the missing backtrace Sorry, forr sending the the wrong content as an attachment. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 422159] Akonadi crashes often and can't be restarted
https://bugs.kde.org/show_bug.cgi?id=422159 --- Comment #4 from Andreas Hencke --- This is a backtrace from my other Desktop machine. It has a MSI A320m motherboard and a Ryzen5 2400G CPU. / and /home are splitted as in the other machine. One point might be importandt: On this machine I installed Kubuntu 20.04 in January from a daily iso, Up to the official release of Kubuntu 20.04 akonadi was working prperly without an issue. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 422159] Akonadi crashes often and can't be restarted
https://bugs.kde.org/show_bug.cgi?id=422159 --- Comment #3 from Andreas Hencke --- Created attachment 128899 --> https://bugs.kde.org/attachment.cgi?id=128899=edit Backtrace from Dr Konqi -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 422159] Akonadi crashes often and can't be restarted
https://bugs.kde.org/show_bug.cgi?id=422159 --- Comment #2 from Andreas Hencke --- Not yet, because of the backtraces were marked as useless so I didn't saved one. Right now akonadi crashed again, this time dr. konqi didn't start aswell. I tryed to start akonadi via Konsole and got this output: andreas@rex-PC:~$ akonadictl stop Akonadi is not running. andreas@rex-PC:~$ akonadictl start org.kde.pim.akonadicontrol: Service org.freedesktop.Akonadi.Control.lock already registered, terminating now. Error: akonadi_control was started but didn't register at D-Bus session bus. Make sure your system is set up correctly! I'll report a backtrace asap! -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 422159] New: Akonadi crashes often and can't be restarted
https://bugs.kde.org/show_bug.cgi?id=422159 Bug ID: 422159 Summary: Akonadi crashes often and can't be restarted Product: Akonadi Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: andreas.hen...@mailbox.org Target Milestone: --- SUMMARY Since I installed Kubuntu 20.04, akonadi has crashed once a day and cannot be started again. Akonadi only runs again after a reboot.But it is getting worse, today akonadi has crashed three times. According to the crash tracking, the data of the backtrace are useless STEPS TO REPRODUCE 1.Start akonadi (Kontact) 2.Wait (work with the machine or do nothing) 3. OBSERVED RESULT After a while, akonadi crashes. EXPECTED RESULT Working akonadi SOFTWARE/OS VERSIONS Kubuntu 20.04 LTS Focal Fossa Linux/KDE Plasma:5.4.0-31 generic/5.18.5 (available in About System) KDE Plasma Version:5.18.5 KDE Frameworks Version: 5.68.0 Qt Version:5.12.8 ADDITIONAL INFORMATION Maybe the information about my machine is useful: CPU: AMD Ryzen 5 2400G Motherboard: MSI B450 Gaming pro Carbon ac RAM:16 GB Separate / and / home directory on / dev / nvme0n1 (Samsung SSD 970 EVO Plus 500GB) -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 417195] New: Kontact crashes when opening a special mail
https://bugs.kde.org/show_bug.cgi?id=417195 Bug ID: 417195 Summary: Kontact crashes when opening a special mail Product: kontact Version: 5.11.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: andreas.hen...@mailbox.org Target Milestone: --- Application: kontact (5.11.3) Qt Version: 5.12.4 Frameworks Version: 5.66.0 Operating System: Linux 5.3.0-29-generic x86_64 Distribution: Ubuntu 19.10 -- Information about the crash: - What I was doing when the application crashed: On KMail I've got four E-Mail accounts but only the posteo.de account is affected and there one Mail (received twice, first at 14:01 o'clock and second at 14:03 o'clock today) When I click to one of these mails Kontact crashes immediatelly, every time I try to. The received mails are from no-re...@deutschepost.de The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4b72833f00 (LWP 6934))] Thread 53 (Thread 0x7f49eaefd700 (LWP 7049)): #0 0x7f4b85b5dc2f in __GI___poll (fds=0x7f49e00029e0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f4b8420ea3e in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f4b8420eb73 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f4b861206c3 in QEventDispatcherGlib::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f4b860c763b in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f4b85f00a75 in QThread::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f4b85f01cc2 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f4b84b60669 in start_thread (arg=) at pthread_create.c:479 #8 0x7f4b85b6a323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 52 (Thread 0x7f49eb7fe700 (LWP 7046)): #0 0x7f4b84b672c6 in futex_wait_cancelable (private=, expected=0, futex_word=0x55a7ec635338) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 0x7f4b84b672c6 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55a7ec6352e8, cond=0x55a7ec635310) at pthread_cond_wait.c:508 #2 0x7f4b84b672c6 in __pthread_cond_wait (cond=0x55a7ec635310, mutex=0x55a7ec6352e8) at pthread_cond_wait.c:638 #3 0x7f4b6b2b591b in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f4b6b2b553b in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f4b84b60669 in start_thread (arg=) at pthread_create.c:479 #6 0x7f4b85b6a323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 51 (Thread 0x7f49ebfff700 (LWP 7045)): #0 0x7f4b84b672c6 in futex_wait_cancelable (private=, expected=0, futex_word=0x55a7ec53d498) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 0x7f4b84b672c6 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55a7ec53d448, cond=0x55a7ec53d470) at pthread_cond_wait.c:508 #2 0x7f4b84b672c6 in __pthread_cond_wait (cond=0x55a7ec53d470, mutex=0x55a7ec53d448) at pthread_cond_wait.c:638 #3 0x7f4b6b2b591b in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f4b6b2b553b in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f4b84b60669 in start_thread (arg=) at pthread_create.c:479 #6 0x7f4b85b6a323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 50 (Thread 0x7f4a0c8f9700 (LWP 7043)): #0 0x7f4b84b676e0 in futex_abstimed_wait_cancelable (private=, abstime=0x7f4a0c8f8470, clockid=, expected=0, futex_word=0x7f4a0c8f85b8) at ../sysdeps/unix/sysv/linux/futex-internal.h:208 #1 0x7f4b84b676e0 in __pthread_cond_wait_common (abstime=0x7f4a0c8f8470, clockid=, mutex=0x7f4a0c8f8568, cond=0x7f4a0c8f8590) at pthread_cond_wait.c:520 #2 0x7f4b84b676e0 in __pthread_cond_timedwait (cond=0x7f4a0c8f8590, mutex=0x7f4a0c8f8568, abstime=0x7f4a0c8f8470) at pthread_cond_wait.c:656 #3 0x7f4b7e6ac10b in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f4b7e6acab2 in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f4b7e6acba6 in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f4b7e66e705 in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f4b7e670c6b in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f4b7e671258 in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f4b7e6aec75 in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f4b84b60669 in start_thread (arg=) at pthread_create.c:479 #11 0x7f4b85b6a323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 49 (Thread 0x7f4a0d0fa700 (LWP 7041)): #0
[kontact] [Bug 417072] New: Kontact crashes again for no apparent reason
https://bugs.kde.org/show_bug.cgi?id=417072 Bug ID: 417072 Summary: Kontact crashes again for no apparent reason Product: kontact Version: 5.11.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: andreas.hen...@mailbox.org Target Milestone: --- Application: kontact (5.11.3) Qt Version: 5.12.4 Frameworks Version: 5.66.0 Operating System: Linux 5.3.0-29-generic x86_64 Distribution: Ubuntu 19.10 -- Information about the crash: - What I was doing when the application crashed: I was away from machine, when I returned kontacht had crashed. I couldn't find out wether it is a duplicate from bug 416307 and/or bug 415997 The crash can be reproduced sometimes. -- Backtrace (Reduced): #6 0x in () #7 0x7f997ad3e8ea in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f997ad3e9fa in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f997ad3ea29 in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f997d1b5779 in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 Possible duplicates by query: bug 416986, bug 416900, bug 416816, bug 416730, bug 416721. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 417072] Kontact crashes again for no apparent reason
https://bugs.kde.org/show_bug.cgi?id=417072 --- Comment #1 from Andreas Hencke --- Created attachment 125625 --> https://bugs.kde.org/attachment.cgi?id=125625=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 416307] New: Kontact crashed for no apparent reason
https://bugs.kde.org/show_bug.cgi?id=416307 Bug ID: 416307 Summary: Kontact crashed for no apparent reason Product: kontact Version: 5.11.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: andreas.hen...@mailbox.org Target Milestone: --- Application: kontact (5.11.3) Qt Version: 5.12.4 Frameworks Version: 5.66.0 Operating System: Linux 5.3.0-26-generic x86_64 Distribution: Ubuntu 19.10 -- Information about the crash: - What I was doing when the application crashed: Kontact was running while I was reading an Newspaper article using Google Chrome -- Backtrace (Reduced): #6 0x7fc7010ab8d5 in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7fc7010ab9fa in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7fc7010aba29 in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7fc703522779 in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7fc703521264 in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 The reporter indicates this bug may be a duplicate of or related to bug 415997. Possible duplicates by query: bug 416254, bug 416136, bug 416113, bug 415997, bug 415991. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 415997] New: Kontact had crashed when I returned to machine
https://bugs.kde.org/show_bug.cgi?id=415997 Bug ID: 415997 Summary: Kontact had crashed when I returned to machine Product: kontact Version: 5.11.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: andreas.hen...@mailbox.org Target Milestone: --- Application: kontact (5.11.3) Qt Version: 5.12.4 Frameworks Version: 5.65.0 Operating System: Linux 5.3.0-26-generic x86_64 Distribution: Ubuntu 19.10 -- Information about the crash: - What I was doing when the application crashed: I made a coffee when I returned to the computer and Kontact crashed - Unusual behavior I noticed: For a few days (before the kernel update) it takes a few seconds (2-3 seconds) when I click on an email in the message list until the message text appears. -- Backtrace (Reduced): #6 0x in () #7 0x7f1087bb88ea in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f1087bb89fa in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f1087bb8a29 in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f108a02f779 in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 Possible duplicates by query: bug 415991, bug 415973, bug 415962, bug 415960, bug 415956. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 415997] Kontact had crashed when I returned to machine
https://bugs.kde.org/show_bug.cgi?id=415997 --- Comment #1 from Andreas Hencke --- Created attachment 124968 --> https://bugs.kde.org/attachment.cgi?id=124968=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 413740] Korganizer crashes when setting catergories colors
https://bugs.kde.org/show_bug.cgi?id=413740 --- Comment #3 from Andreas Hencke --- Created attachment 124278 --> https://bugs.kde.org/attachment.cgi?id=124278=edit New crash information added by DrKonqi kontact (5.11.3) using Qt 5.12.4 - What I was doing when the application crashed I imported a new .ics calendar an merged it to an existing calendar. Afterwards I opened korganizer/cusomize/colors and fonts to set the category colors. After clickin the "set" (in german Anwenden) button Kontact/Korganizer crashed. This happens everytime. -- Backtrace (Reduced): #6 0x7ff49aa4ec53 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7ff49aa49411 in QAbstractItemModelPrivate::itemsMoved(QModelIndex const&, int, int, QModelIndex const&, int, Qt::Orientation) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7ff49aa4bc1b in QAbstractItemModel::endMoveRows() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7ff49a2cda0e in () at /lib/x86_64-linux-gnu/libKF5AkonadiCore.so.5abi1 #10 0x7ff49a2cab0c in () at /lib/x86_64-linux-gnu/libKF5AkonadiCore.so.5abi1 -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 413740] Korganizer crashes when setting catergories colors
https://bugs.kde.org/show_bug.cgi?id=413740 Andreas Hencke changed: What|Removed |Added CC||andreas.hen...@mailbox.org -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 411687] New: Kontact crashes when I click somewhere
https://bugs.kde.org/show_bug.cgi?id=411687 Bug ID: 411687 Summary: Kontact crashes when I click somewhere Product: kontact Version: 5.11.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: andreas.hen...@mailbox.org Target Milestone: --- Application: kontact (5.11.3) Qt Version: 5.12.4 Frameworks Version: 5.61.0 Operating System: Linux 5.2.0-15-generic x86_64 Distribution: Ubuntu Eoan Ermine (development branch) -- Information about the crash: - What I was doing when the application crashed: I was using Kmail within Kontact and I clicked at an inbox icon to view an other inbox when Kontact crashed. The same happens if I use Akregator or an other part of Kontact. SOFTWARE/OS VERSIONS Linux: Kubuntu 19.10 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.61.0 Qt Version: 5.12.4 The crash can be reproduced sometimes. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f345c846f00 (LWP 25567))] Thread 24 (Thread 0x7f3436ffd700 (LWP 25704)): #0 futex_abstimed_wait_cancelable (private=, abstime=0x7f3436ffc470, clockid=, expected=0, futex_word=0x7f3436ffc5b8) at ../sysdeps/unix/sysv/linux/futex-internal.h:208 #1 __pthread_cond_wait_common (abstime=0x7f3436ffc470, clockid=, mutex=0x7f3436ffc568, cond=0x7f3436ffc590) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x7f3436ffc590, mutex=0x7f3436ffc568, abstime=0x7f3436ffc470) at pthread_cond_wait.c:656 #3 0x7f34686df10b in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f34686dfab2 in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f34686dfba6 in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f34686a1705 in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f34686a3f96 in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f34686a4258 in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f34686e1c75 in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f346eb21669 in start_thread (arg=) at pthread_create.c:479 #11 0x7f346fb6b2f3 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 23 (Thread 0x7f333d776700 (LWP 25656)): #0 0x7f346fb5ebff in __GI___poll (fds=0x7f33300029e0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f346e1cda4e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f346e1cdb83 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f3470121573 in QEventDispatcherGlib::processEvents (this=0x7f333b60, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7f34700c856b in QEventLoop::exec (this=this@entry=0x7f333d7756a0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #5 0x7f346ff01a35 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #6 0x7f346ff02c82 in QThreadPrivate::start (arg=0x55aecad46990) at thread/qthread_unix.cpp:361 #7 0x7f346eb21669 in start_thread (arg=) at pthread_create.c:479 #8 0x7f346fb6b2f3 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 22 (Thread 0x7f33525d4700 (LWP 25615)): #0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x7f346ff05071 in QtLinuxFutex::_q_futex (val3=0, addr2=0x0, val2=0, val=, op=0, addr=) at thread/qfutex_p.h:105 #2 QtLinuxFutex::futexWait > (expectedValue=, futex=...) at thread/qfutex_p.h:107 #3 futexSemaphoreTryAcquire_loop (timeout=-1, nn=8589934593, curValue=, u=...) at thread/qsemaphore.cpp:219 #4 futexSemaphoreTryAcquire (timeout=-1, n=, u=...) at thread/qsemaphore.cpp:262 #5 QSemaphore::acquire (this=0x55aebec51f28, n=) at thread/qsemaphore.cpp:326 #6 0x7f3352be5fec in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/texttospeech/libqttexttospeech_flite.so #7 0x7f346ff02c82 in QThreadPrivate::start (arg=0x55aebec51ef0) at thread/qthread_unix.cpp:361 #8 0x7f346eb21669 in start_thread (arg=) at pthread_create.c:479 #9 0x7f346fb6b2f3 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 21 (Thread 0x7f335345a700 (LWP 25613)): #0 0x7f346fb5ebff in __GI___poll (fds=0x7f33480025e0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f346e1cda4e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f346e1cdb83 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f3470121573 in QEventDispatcherGlib::processEvents (this=0x7f3348000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7f34700c856b in
[kdeconnect] [Bug 410026] New: kdeconnectd crashes without being in use
https://bugs.kde.org/show_bug.cgi?id=410026 Bug ID: 410026 Summary: kdeconnectd crashes without being in use Product: kdeconnect Version: 1.3.4 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: andreas.hen...@mailbox.org Target Milestone: --- SUMMARY Kdeconnect crashes without being used an being in use STEPS TO REPRODUCE 1. Start Kubuntu, after some time DrKonqi and/or Apport/woopsie will report the crash 2.Open kdeconnect 3. OBSERVED RESULT DrKonqi reports the crash EXPECTED RESULT Working kdeconntect SOFTWARE/OS VERSIONS Linux/KDE Plasma:5.0.0.20-generic/Kubuntu 19.04 KDE Plasma Version: 5.16.3 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION DrKonqi's report, Common Tab We are very sorry; the program kdeconnectd was terminated unexpectedly. You can not report this error because the kdeconnectd application does not provide an address for reporting errors. Details: Executable file:kdeconnectd PID: 15228 Signal: Segmentation fault (11) Date: 20.07.19 11:24:03 Developer information Application: kdeconnectd (kdeconnectd), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd31361e800 (LWP 15228))] Thread 4 (Thread 0x7fd30b7fe700 (LWP 15232)): #0 __libc_enable_asynccancel () at ../sysdeps/unix/sysv/linux/x86_64/cancellation.S:56 #1 0x7fd31794d716 in __GI___poll (fds=0x7fd2fc004a30, nfds=1, timeout=10371) at ../sysdeps/unix/sysv/linux/poll.c:29 #2 0x7fd3160b8bf6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fd3160b8d1c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fd317ecf063 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fd317e7a5bb in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fd317cc52c6 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fd317cc6612 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fd3168d3182 in start_thread (arg=) at pthread_create.c:486 #9 0x7fd317959b1f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7fd30bfff700 (LWP 15231)): #0 0x7fd3160b824c in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fd3160b8b2b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fd3160b8d1c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fd317ecf063 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fd317e7a5bb in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fd317cc52c6 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fd31720e565 in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7fd317cc6612 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fd3168d3182 in start_thread (arg=) at pthread_create.c:486 #9 0x7fd317959b1f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7fd31231b700 (LWP 15230)): #0 0x7fd31794d729 in __GI___poll (fds=0x7fd31231aca8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fd315d56917 in ?? () from /lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7fd315d5853a in xcb_wait_for_event () from /lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7fd312f106a8 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7fd317cc6612 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fd3168d3182 in start_thread (arg=) at pthread_create.c:486 #6 0x7fd317959b1f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7fd31361e800 (LWP 15228)): [KCrash Handler] #6 0x7fd317d44f23 in operator==(QString const&, QString const&) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fd318dc27bc in KNotification::setTitle(QString const&) () from /lib/x86_64-linux-gnu/libKF5Notifications.so.5 #8 0x7fd31008c009 in Notification::createKNotification (this=this@entry=0x55e91daa8320, update=, np=...) at ./plugins/notifications/notification.cpp:95 #9 0x7fd31008cbad in Notification::update (this=this@entry=0x55e91daa8320, np=...) at ./plugins/notifications/notification.cpp:81 #10 0x7fd310093a2d in NotificationsDbusInterface::processPacket (this=0x55e91da385b0, np=...) at ./plugins/notifications/notificationsdbusinterface.cpp:91 #11 0x7fd31008f7ea in NotificationsPlugin::receivePacket (this=0x55e91d9e2450, np=...) at ./plugins/notifications/notificationsplugin.cpp:59 #12 0x7fd318fa8488 in Device::privateReceivedPacket (this=, np=...) at ./core/device.cpp:341 #13 0x7fd317ea5563 in
[kdeconnect] [Bug 401561] KDEConnect fails to open remote phone directory: Modul "kio_kdeconnect" not found
https://bugs.kde.org/show_bug.cgi?id=401561 --- Comment #1 from Andreas Hencke --- Hi all, I'm a bit late but I want to report that, after installation/ update to kdeconnect 1.3.3 a reboot fixes the problem. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 401561] KDEConnect fails to open remote phone directory: Modul "kio_kdeconnect" not found
https://bugs.kde.org/show_bug.cgi?id=401561 Andreas Hencke changed: What|Removed |Added CC||andreas.hen...@mailbox.org -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 401561] New: KDEConnect fails to open remote phone directory: Modul "kio_kdeconnect" not found
https://bugs.kde.org/show_bug.cgi?id=401561 Bug ID: 401561 Summary: KDEConnect fails to open remote phone directory: Modul "kio_kdeconnect" not found Product: kdeconnect Version: 1.10 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: andreas.hen...@mailbox.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Device(s) and Computer paired 2. In Dolphin, click on the name of the device created by Kdeconnect 3. OBSERVED RESULT Creating of the in/outputmodule not possible. Report by klauncher: The module "kio_kdeconnect" was not found. (translated from german, origin report below) Erstellung des Ein-/Ausgabemoduls nicht möglich. Meldung von klauncher: Das Modul „kio_kdeconnect“ wurde nicht gefunden. EXPECTED RESULT Acces to sdcard/extsdcard of the device SOFTWARE/OS VERSIONS Windows: none MacOS: none Linux/KDE Plasma: (available in About System) Kubuntu 18.04.1 KDE Plasma Version: 5.12.7 KDE Frameworks Version: 5.47.0 Qt Version: 5.9.5 ADDITIONAL INFORMATION I found this bug as another member of ubuntuusers.de was asking for help to upgrade from kdeconnect 1.3.1 to 1.3.2. I tried to access the internal of my Sony XZ Premium and failed. As the other guy managed to upgrade to v1.3.3 he's got the same error. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 401560] New: KDEConnect fails to open remote phone directory: Modul "kio_kdeconnect" not found
https://bugs.kde.org/show_bug.cgi?id=401560 Bug ID: 401560 Summary: KDEConnect fails to open remote phone directory: Modul "kio_kdeconnect" not found Product: kdeconnect Version: 1.10 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: andreas.hen...@mailbox.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 357707] New: Kontact crashed while reading news in akregator
https://bugs.kde.org/show_bug.cgi?id=357707 Bug ID: 357707 Summary: Kontact crashed while reading news in akregator Product: kontact Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: andreas.hen...@outlook.com Application: kontact (4.14.3) KDE Platform Version: 4.14.13 Qt Version: 4.8.6 Operating System: Linux 3.19.0-43-generic x86_64 Distribution: Ubuntu 14.04.3 LTS -- Information about the crash: - What I was doing when the application crashed: I closed some sub windows in akregator as kontact crashed. Akgregator was pretty slow closing the windows -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fbb0db8c800 (LWP 3548))] Thread 6 (Thread 0x7fbaee302700 (LWP 3549)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fbb0893381d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7fbb08933859 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7fbb05054182 in start_thread (arg=0x7fbaee302700) at pthread_create.c:312 #4 0x7fbb0b10747d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 5 (Thread 0x7fbaad9e7700 (LWP 3550)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fbb0867420d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7fbb08962fd6 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7fbb05054182 in start_thread (arg=0x7fbaad9e7700) at pthread_create.c:312 #4 0x7fbb0b10747d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 4 (Thread 0x7fba9db31700 (LWP 3574)): #0 0x7fbb04b723ef in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fbb04b749bb in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fbb04b74f7b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fbb04b750ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fbb0b8807be in QEventDispatcherGlib::processEvents (this=0x7fba980008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436 #5 0x7fbb0b8520af in QEventLoop::processEvents (this=this@entry=0x7fba9db30de0, flags=...) at kernel/qeventloop.cpp:149 #6 0x7fbb0b8523a5 in QEventLoop::exec (this=this@entry=0x7fba9db30de0, flags=...) at kernel/qeventloop.cpp:204 #7 0x7fbb0b74ec5f in QThread::exec (this=) at thread/qthread.cpp:537 #8 0x7fbb0b75132f in QThreadPrivate::start (arg=0xf5bc00) at thread/qthread_unix.cpp:349 #9 0x7fbb05054182 in start_thread (arg=0x7fba9db31700) at pthread_create.c:312 #10 0x7fbb0b10747d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 3 (Thread 0x7fba97b8e700 (LWP 3587)): #0 0x7ffcd5daec28 in ?? () #1 0x7fbb0db8e210 in ?? () #2 0x0001 in ?? () #3 0x00010b747244 in ?? () #4 0x7fba90002f30 in ?? () #5 0x7fba97b8dbe8 in ?? () #6 0x7fba97b8db80 in ?? () #7 0x7fff in ?? () #8 0x7fba97b8dbf0 in ?? () #9 0x7fbb0b11592d in __GI___clock_gettime (clock_id=, tp=) at ../sysdeps/unix/clock_gettime.c:115 #10 0x7fbb0b7a5ad7 in do_gettime (frac=0x7fba97b8db30, sec=0x7fba97b8db28) at tools/qelapsedtimer_unix.cpp:127 #11 qt_gettime () at tools/qelapsedtimer_unix.cpp:144 #12 0x7fbb0b881f05 in updateCurrentTime (this=0x1) at kernel/qeventdispatcher_unix.cpp:354 #13 QTimerInfoList::timerWait (this=0x1, tm=...) at kernel/qeventdispatcher_unix.cpp:460 #14 0x7fbb0b88067c in timerSourcePrepareHelper (src=, timeout=0x7fba97b8dbe4) at kernel/qeventdispatcher_glib.cpp:143 #15 0x7fbb0b880725 in timerSourcePrepare (source=, timeout=) at kernel/qeventdispatcher_glib.cpp:176 #16 0x7fbb04b7468d in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x7fbb04b74f03 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #18 0x7fbb04b750ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x7fbb0b8807be in QEventDispatcherGlib::processEvents (this=0x7fba98c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436 #20 0x7fbb0b8520af in QEventLoop::processEvents (this=this@entry=0x7fba97b8dda0, flags=...) at kernel/qeventloop.cpp:149 #21 0x7fbb0b8523a5 in QEventLoop::exec (this=this@entry=0x7fba97b8dda0, flags=...) at kernel/qeventloop.cpp:204 #22 0x7fbb0b74ec5f in QThread::exec (this=this@entry=0x1d0b3b0) at thread/qthread.cpp:537 #23 0x7fbb0b833823 in QInotifyFileSystemWatcherEngine::run (this=0x1d0b3b0) at io/qfilesystemwatcher_inotify.cpp:265 #24
