| View previous topic :: View next topic |
| Author |
Message |
<3
Veteran
Joined: 21 Oct 2004
Posts: 1084
|
 Posted: Sat Oct 22, 2022 3:40 pm Post subject: kde apps are crashing at startup (bug?) |
 |
|
For some reason I can not get KDE apps to start
| Code: | # konqueror
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = konqueror path = /usr/bin pid = 27260
KCrash: Arguments: /usr/bin/konqueror
KCrash: Attempting to start /usr/lib64/libexec/drkonqi
[1]+ Stopped konqueror |
| Code: | # systemsettings
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = systemsettings path = /usr/bin pid = 27343
KCrash: Arguments: /usr/bin/systemsettings
KCrash: Attempting to start /usr/lib64/libexec/drkonqi
[2]+ Stopped systemsettings |
| Code: | # konsole
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = konsole path = /usr/bin pid = 27436
KCrash: Arguments: /usr/bin/konsole
KCrash: Attempting to start /usr/lib64/libexec/drkonqi
[1]+ Stopped konsole |
To make matters worse, no indication of why these are crashing is given. Also sometimes a few seconds later I get this message
[code]Unable to find file for pid 27436 expected at "kcrash-metadata/27436.ini"
QSocketNotifier: Invalid socket 8 and type 'Read', disabling.../code]
I did notice that konqueror managed to cause a segfault message in dmesg but I only received this once and when I tried to run konqueror again I did not receive this message again. Also the other KDE apps did not trigger a segfault message in dmesg.
Can someone help me fix these issues?
Last edited by <3 on Sat Oct 29, 2022 7:33 am; edited 2 times in total |
|
| Back to top |
|
 |
asturm
Developer
Joined: 05 Apr 2007
Posts: 9280
|
| Posted: Sat Oct 22, 2022 3:48 pm Post subject: |
|
|
| Is this a VM? |
|
| Back to top |
|
|
<3
Veteran
Joined: 21 Oct 2004
Posts: 1084
|
| Posted: Sun Oct 23, 2022 3:15 am Post subject: |
|
|
| asturm wrote: | | Is this a VM? |
no |
|
| Back to top |
|
|
<3
Veteran
Joined: 21 Oct 2004
Posts: 1084
|
| Posted: Fri Oct 28, 2022 12:35 pm Post subject: |
|
|
| am I the only person having this issue? No one is responding. |
|
| Back to top |
|
|
<3
Veteran
Joined: 21 Oct 2004
Posts: 1084
|
| Posted: Sat Oct 29, 2022 7:32 am Post subject: |
|
|
I have been dealing with this weird issue for a while that I think may be related, and I notice something just now that could be also related....
For months I have had this weird issue that I've never figured out and since it wasn't that big of a deal I never worried about it. I am running gentoo on my laptop that has and external monitor connected. Generally when the laptop is docked I use plasma systemsettings to disable the laptop's internal monitor and just use the larger external monitor. One reason why I do this is because I get weird things happening, for example when I start yakuake it will only display on the laptops internal monitor and plasma will not allow me to open it on the external monitor, my laptop's monitor is too small to read text from the console so I prefer opening it on the larger external screen. I've found one work around to this issue by disabling the internal monitor thus yakuake will have only the external monitor to display on. When ever I do this yakuake will open on the larger external monitor.
I just noticed that even though I generally keep the lid on my laptop closed for some reason my iinternal monitor's settings had been reset so that the intenal monitor was powered on. Using plasma system settings to disable the internal monitor seemed to fix the problem so now I am able to start these KDE applications with out them crashing. It's funny because the only was I could do this was to first up plug the external monitor so that it was not detected then go start plasma system setting (since system settings would not start if I had the external monitor enabled). Plug back in the external monitor then enable the external monitor and disable the internal monitor then click apply in order for me to get this working again.
My guess is that this is a bug, though I don't know what is causing this bug so I don't know who to submit this bug to. |
|
| Back to top |
|
|
|
Desktop Environments
