[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#763281: konqueror: Session management does not work for Konqueror



On Thu, 02 Oct 2014 22:02:15 -0400 Brendon Higgins 
<brendon@quantumfurball.net> wrote:
> I'm also experiencing this, on three different computers.

Do you know when this behavior started? Are you using testing or unstable? 
According to
https://packages.qa.debian.org/k/kde-baseapps.html
there are not so many possible versions which could introduce this bug in my 
(mainly) testing system:
4:4.14.1-1 at 2014-09-26 or
4:4.14.0-1 at 2014-08-30 or
4:4.13.3-1 at 2014-08-05
I am quite sure, that the bug has not not occurred since or before 2014-05-05.

Given the lack of upstream maintainers, we probably have to care about this 
bug ourselves, if we want to get it fixed for Jessie. I checked
> ~/.kde/share/config/ksmserverrc
and it contains an entry of konqueror, which seems valid to me. This is 
plausible, as konqueror automatically opens when logging in, after all.
Then I checked the files in
> ~/.kde/share/config/session
and current konqueror entries lack nearly all data. So it does not seem to be 
a problem with restoring (reading) the session managemant information, but 
with storing (saving) it.

I found an old entry modified (created) on 2014-08-06 in that directory which 
seems to contain all needed data. According to my /var/log/dpkg.log.1 file, I 
upgraded konqueror  from 4:4.12.4-1 to 4:4.13.3-1 on 2014-08-05 in the 
evening. As I shut my system down later that evening, the correct session file 
must have been created with version 4:4.13.3-1. Thus, I think, the bug must 
have been introduced in KDE with 4:4.14.0-1 or 4:4.14.1-1. It would be 
helpful, if you could narrow it down even more.

By the way, I already downgraded konqueror, kde-baseapps-data, kdepasswd, kde-
baseapps and kde-baseapps-bin to 4:4.14.0-1 versions, but that didn't help. 
Either the problem has already been present in the 4:4.14.0-1 version or 
another KDE component is the culprit, as konqueror probably uses other 
libraries/processes to save its session management data.
Anyway, doing the same with version 4:4.13.3-1 could be interesting, but 
resolving the dependencies could be more tricky. If you want to try it, that 
is the approach for 4:4.14.0-1 (the last one obviously needs root 
permissions):
> debsnap --architecture all kde-baseapps-data 4:4.14.0-1
> debsnap --architecture all kde-baseapps 4:4.14.0-1
> debsnap --architecture amd kde-baseapps-bin 4:4.14.0-1
> debsnap --architecture amd kdepasswd 4:4.14.0-1
> debsnap --architecture amd konqueror 4:4.14.0-1
> find binary* -type f | xargs dpkg -i

Kind regards
Patrick

Attachment: signature.asc
Description: This is a digitally signed message part.


Reply to: