Application: kdeinit5 ()
Qt Version: 5.11.0
Frameworks Version: 5.46.0
Operating System: Linux 4.17.1-1-pae i686
Distribution: "openSUSE Tumbleweed"
-- Information about the crash:
First logon after boot. Unable to install debug info automatically, and the web site gave only file names, not package names. I'm running openSUSE TUMBLEWEED.
It doesn't seem like this provides enough information to debug. Was there a stack trace?
Is this an entirely default install? If so, did you try filing this with openSUSE Tumbleweed? If so, can you link to that discussion?
Does this crash actually still happen?
To me it sounds the same as bug#394534 which has been fixed in Plasma 5.13.2.
If you want to install debug symbols, you need to enable the debug repo (in YaST->Software Repositories) first btw.
(In reply to Ben Creasy from comment #1)
> It doesn't seem like this provides enough information to debug. Was there a
> stack trace?
> Is this an entirely default install? If so, did you try filing this with
> openSUSE Tumbleweed? If so, can you link to that discussion?
This was a normal install of Tumbledweed, followed by multiple runs of Yast and zipper dup. I've added the debug repository and installed the debug packages, so if it happens again I should get a good trace. I have not opened an incident with Novell, but can do so if you want me to.
(In reply to Shmuel (Seymour J.) Metz from comment #3)
> I have not
> opened an incident with Novell, but can do so if you want me to.
There's absolutely no indication so far that it actually is an openSUSE-specific problem. (I am using openSUSE btw, and don't get such a crash ;-) )
And without further information, that would be pointless as well anyway.
Btw, kdeinit5 is just a way to start other KDE applications. It's likely not kdeinit5 that crashes, but rather the application that's being started.
And unfortunately, there's not even an indication here which application that would be.
(a stack trace should show this as well though)
No response, assuming it is a duplicate.
*** This bug has been marked as a duplicate of bug 394534 ***