#725200 toolbars auto-lock after customizing

Package:
konqueror
Source:
konqueror
Description:
advanced file manager, web browser and document viewer
Submitter:
Scott
Date:
2013-10-07 13:51:22 UTC
Severity:
normal
#725200#5
Date:
2013-10-02 17:45:41 UTC
From:
To:
Using konqueror in file manager mode.toolbars can be set not to be locked, but after customizing toolbars, the toolbars become become locked automatically.

What occurs:
 - I set toolbars to un-locked. I now can move the toolbars to different locations.
 - I then customize a toolbar such as removing items and click 'Apply'

 When I clicked 'apply' I immediately noticed toolbars jump to their default location.  I click 'ok' to exit the current customizing dialog box,
  and later notice that toolbars are not only reset to their default location but have been locked.
 Despite the toolbars returning to their original location, the changed items stay intact.

 So far the "toolbars" I have noticed jumping to their original location is the 'Extra' and 'Main' toolbars.

#725200#10
Date:
2013-10-02 20:13:14 UTC
From:
To:
tags 725200 upstream
thanks

Hello,

the bug you reported is a KDE bug. Please report it via
Help -> Report bug... menu item of the respective application
or by visiting https://bugs.kde.org/ and following instructions
to report a new bug.

Debian Qt/KDE maintainers do not have resources to deal with
non Debian-specific bugs and therefore it is unlikely that
your bug will be solved if you do not report it to KDE developers
directly (unless it is/has been reported by somebody else).

Whenever you open a bug report on the KDE bug tracking system, or
you find that the bug has been already reported on it, you can couple
both this Debian bug and the KDE bug together by sending the mail with
the text below to control@bugs.debian.org (replace KDE-BUG-URL with
the address of the bug report on https://bugs.kde.org/)
------------[ copy this ]------------ forwarded 725200 KDE-BUG-URL thanks ------------[ copy this ]------------ Thank you,
#725200#15
Date:
2013-10-02 20:13:14 UTC
From:
To:
tags 725200 upstream
thanks

Hello,

the bug you reported is a KDE bug. Please report it via
Help -> Report bug... menu item of the respective application
or by visiting https://bugs.kde.org/ and following instructions
to report a new bug.

Debian Qt/KDE maintainers do not have resources to deal with
non Debian-specific bugs and therefore it is unlikely that
your bug will be solved if you do not report it to KDE developers
directly (unless it is/has been reported by somebody else).

Whenever you open a bug report on the KDE bug tracking system, or
you find that the bug has been already reported on it, you can couple
both this Debian bug and the KDE bug together by sending the mail with
the text below to control@bugs.debian.org (replace KDE-BUG-URL with
the address of the bug report on https://bugs.kde.org/)
------------[ copy this ]------------ forwarded 725200 KDE-BUG-URL thanks ------------[ copy this ]------------ Thank you,
#725200#20
Date:
2013-10-07 12:51:33 UTC
From:
To:
I just noticed about this after filing a few bug reports to you guys.

I will refer to kde.bugs.org..

Thanks guys.. (sorry if it seemed like I was ignoring the replies)

#725200#25
Date:
2013-10-07 12:51:33 UTC
From:
To:
I just noticed about this after filing a few bug reports to you guys.

I will refer to kde.bugs.org..

Thanks guys.. (sorry if it seemed like I was ignoring the replies)

#725200#28
Date:
2013-10-07 12:51:33 UTC
From:
To:
I just noticed about this after filing a few bug reports to you guys.

I will refer to kde.bugs.org..

Thanks guys.. (sorry if it seemed like I was ignoring the replies)

#725200#33
Date:
2013-10-07 13:49:54 UTC
From:
To:
No problem at all, thanks for pushing this upstream :)
#725200#36
Date:
2013-10-07 13:49:54 UTC
From:
To:
No problem at all, thanks for pushing this upstream :)