Bug 381400

Summary:	Using plasma5 and booting into a saved session konsole doesn't start if session saved with now nonexistent usb drive.
Product:	[Applications] konsole	Reporter:	davejplater@gmail.com <plater>
Component:	general	Assignee:	Konsole Developer <konsole-devel>
Status:	RESOLVED FIXED
Severity:	normal	CC:	wbauer1
Priority:	NOR
Version:	16.08.2
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:	https://cgit.kde.org/konsole.git/commit/?h=Applications/16.12&id=6e2d3f4e7e952a342ed91bf93d4487bd51a331ea	Version Fixed In:	16.12.0
Sentry Crash Report:

Description davejplater@gmail.com 2017-06-19 15:27:29 UTC

I manually save my plasma5 sessions from time to time. If I had a removable drive open in one of my konsole tabs when I save the session then konsole refuses to start on the next boot. If I then plug in and mount a usb drive and it's mounted by plasma5 with the same drive descriptor and log out and log in then the saved konsole will start. If I start xterm and start konsole from there, I can get a new konsole instance. I can't find any error messages konsole just silently refuses to start.

Comment 1 Kurt Hindenburg 2017-06-25 22:05:49 UTC

I'm assuming that you had cd into the removed drive?  So in the ~/.config/session/konsole* file you have 'WorkingDir[$e]=nonexistancedrive'

I thought this had been fix but I'll check again.

If you can reproduce on your system can you post the WorkingDir line?

Comment 2 davejplater@gmail.com 2017-06-26 06:10:06 UTC

This is fixed in 17.04.2, is there a patch available for 16.08.02 or is it fixed in a later 16.08 version? I'll file am openSUSE bug to force an update. Going to try the official openSUSE:Leap:42.2 version again.
The directory entry in
~/.config/session/konsole_10149dad0e4000148707992600000017800011_1498456552_181102 is:
 WorkingDir[$e]=/run/media/davepl/DAVEWDE/vending/cypress/FX3_SDK/cyusb_linux_1.0.4

Comment 3 Wolfgang Bauer 2017-06-26 07:40:54 UTC

(In reply to Kurt Hindenburg from comment #1)
> I thought this had been fix but I'll check again.

I suppose this should be fixed by https://cgit.kde.org/konsole.git/commit/?h=Applications/16.12&id=6e2d3f4e7e952a342ed91bf93d4487bd51a331ea

But that's only in 16.12 (or later) and didn't get backported to 16.08...

Comment 4 davejplater@gmail.com 2017-06-26 10:06:34 UTC

It seems that this fix wasn't backported to Leap:42.2 and has now been rectified.
https://bugzilla.opensuse.org/show_bug.cgi?id=1045914
Thanks for your help.

Comment 5 Wolfgang Bauer 2017-06-26 10:40:47 UTC

I suppose this can be closed then.

Resolving as FIXED, as it is not really a downstream problem. It was a bug in 16.08.2 that has been fixed in later versions (16.12).