Bug 7296 - Konsole in kde4.9 regression: tab bar cannot be controlled any more (Mageia3 Alpha1)
Summary: Konsole in kde4.9 regression: tab bar cannot be controlled any more (Mageia3 ...
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard: 3alpha1
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2012-09-02 18:53 CEST by Juergen Harms
Modified: 2012-09-03 15:08 CEST (History)
0 users

See Also:
Source RPM: konsole-4.9.0-1.mga3.src.rpm
CVE:
Status comment:


Attachments
this is not what you want ? (51.23 KB, image/png)
2012-09-03 11:16 CEST, Manuel Hiebel
Details

Description Juergen Harms 2012-09-02 18:53:01 CEST
Description of problem:

Konsole in KDE always offered the possibilty to hide or show the tab bar, and to determine its place. This is not possible any more in KDE 4.9: the corresponding buttons have disappeared from the "tab" window


Version-Release number of selected component (if applicable): konsole-4.9.0-1


How reproducible:
Always


Steps to Reproduce:
1.open a konsole
2. settings -> edit current profile -> tabs
3.

This may appear to be a secondary feature being suppressed. On devices with small screens the tab bar takes away valuable space, not having the possibility to drop the tab-bar is a serious drawback
Juergen Harms 2012-09-02 18:53:42 CEST

Whiteboard: (none) => 3alpha1

Comment 1 Manuel Hiebel 2012-09-03 11:16:59 CEST
Created attachment 2732 [details]
this is not what you want ?
Manuel Hiebel 2012-09-03 11:17:21 CEST

Keywords: (none) => NEEDINFO

Comment 2 Juergen Harms 2012-09-03 14:52:20 CEST
Great, yes. But took me some time to find where you got this. With pre 4.9 KDE that was at "settings -> edit current profile -> tabs", it is now in a new tab at "settings -> configure konsole ...".

That means that this option (like the show menubar option) is not profile-specific any more, but an option effective for all profiles.

I have no problem with that, you can close the bug.

I will send an email to the mageia discuss list to discuss how users can be made aware of this change.
Comment 3 Manuel Hiebel 2012-09-03 15:08:24 CEST
ok, anyway this is a upstream decision

Status: NEW => RESOLVED
Resolution: (none) => INVALID


Note You need to log in before you can comment on or make changes to this bug.