Bug 284844 - Width of Yakuake at 100% runs off edge of screen due to Unity
Summary: Width of Yakuake at 100% runs off edge of screen due to Unity
Status: RESOLVED FIXED
Alias: None
Product: yakuake
Classification: Applications
Component: general (other bugs)
Version First Reported In: 2.9.8
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Eike Hein
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-24 05:51 UTC by Jiawei Li
Modified: 2012-02-07 13:53 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Screenshot of situation. (447.82 KB, image/png)
2011-10-24 05:51 UTC, Jiawei Li 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Jiawei Li 2011-10-24 05:51:27 UTC 
Created attachment 64825 [details]
Screenshot of situation.

Version:           2.9.8
OS:                Linux

Setting the width of the Yakuake console to more than 90% makes it run off the right side of the screen.  It seems to start at the right edge of the Unity bar.

Unable to change it back except by modifying config file at ~/.kde/share/config/yakuakerc

Reproducible: Always

Steps to Reproduce:
Install Yakuake.
Set width to 100%.

Actual Results:  
Runs off the right edge of the screen.

Expected Results:  
Fill up the entire width of the screen.  Should be "on top" of the Unity bar.

OS: Linux (x86_64) release 3.0.0-12-generic
Compiler: gcc
Comment 1 Jekyll Wu 2011-10-25 05:29:09 UTC 
That happens if the Unity bar is visible when yakuake is started.
Comment 2 Jiawei Li 2011-10-25 05:36:03 UTC 
(In reply to comment #1)
> That happens if the Unity bar is visible when yakuake is started.

I've tried starting Yakuake when the Unity bar is not visible, and the same issue occurs.

I should mention that this occurs only on Ubuntu 11.10.  It worked correctly on Ubuntu 11.04.
Comment 3 Eike Hein 2011-10-25 22:59:03 UTC 
Probably a dupe of bug 265818, would be nice if one of you could check with the patch there.
Comment 4 Eike Hein 2012-02-07 13:53:51 UTC 
This should hopefully be fixed in git master and the upcoming 2.9.9 release.