https://bugs.kde.org/show_bug.cgi?id=456767
BEEDELL ROKE JULIAN LOCKHART <beedellrokejulianlockh...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|WORKSFORME |FIXED
--- Comment #11 from BEEDELL ROKE JULIAN LOCKHART
<beedellrokejulianlockh...@gmail.com> ---
(In reply to Igor Kushnir from comment #10)
> (In reply to BEEDELL ROKE JULIAN LOCKHART from comment #9)
> > (In reply to Igor Kushnir from comment #8)
> > > (In reply to BEEDELL ROKE JULIAN LOCKHART from comment #6)
> > > > "kdevelop -n test-session" correctly invokes kdevelop, and now kdevelop
> > > > appears to invoke correctly. Should this report be closed because this
> > > > was
> > > > somehow caused by me, or should I attempt to provide some
> > > > debug-information
> > > > to you?
> > > KDevelop remembers a last used session. I suppose if you open the previous
> > > session from KDevelop's main menu=>Session, you'll see the same crash
> > > again.
> > > Hard to tell what caused the session corruption and there are plenty more
> > > crashes to fix. I'll close this bug. Reopen when another session gets
> > > corrupted like this in the future.
> >
> > Because of what you said, I created a new session by invoking “kdevelop -n”.
> > It operated. I subsequently deleted that session, and kdevelop correctly
> > allowed me to continue with the previously created test-session. That
> > session operated. However, if I attempt to switch to the “Default:” session,
> > the session-corruption dialogue with the “Clear cache” button appears the
> > first time, and does not appear the subsequent times, yet I remain unable to
> > switch to the default session. If I delete all alternative sessions so that
> > solely the default sessions remain, KDevelop becomes unable to launch,
> > obviously because the default session is corrupt.
> >
> > Even “su -c "dnf reinstall --refresh -y 'kdevelop'"” does not remediate the
> > problem. However, invocation of the graphical session-chooser (“kdevelop
> > --ps”) or textual creation of a new session via “kdevelop -n” allows me to
> > utilize kdevelop, but this may be problematic for new users.
> >
> > I expect that even this is not enough information for you to remediate this
> > problem, but might this be worth reporting to Red Hat?
> This is not a packaging problem. Nothing worth reporting to Red Hat. The
> default session files have been corrupted on your system for some reason.
> You can "fix" your Default session by removing its directory in
> ~/.local/share/kdevelop/sessions
Problem remediated. Thanks a lot.
--
You are receiving this mail because:
You are watching all bug changes.
