Bug 301142 - Black band of 2 and 1/2 inches comes on the screen with "Update Information - KDE Daemon" on fresh boot
Summary: Black band of 2 and 1/2 inches comes on the screen with "Update Information -...
Status: RESOLVED DUPLICATE of bug 213267
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-06-04 06:32 UTC by Indian Art
Modified: 2012-06-04 18:28 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Error Screenshot (443.81 KB, image/png)
2012-06-04 06:34 UTC, Indian Art
Details
Text from Konsole on running command of Thomas (8.55 KB, application/rtf)
2012-06-04 15:29 UTC, Indian Art
Details
KDE Daemon Error Snapshot before the problem was resolved (319.40 KB, image/png)
2012-06-04 15:31 UTC, Indian Art
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Indian Art 2012-06-04 06:32:45 UTC
I get the error which can be shown very well if I can upload the Screen Shot. Please let me know how I can upload it.

Reproducible: Always

Steps to Reproduce:
1. On fresh booting a icon of a yellow incandescent light bulb shows up on the task bar.
2. Clicking it shows a black band of 2 and 1/2 inches comes on the screen with "Update Information - KDE Daemon" text on the bottom panel.
3. Right  clicking & closing makes it goes away till next reboot.
Actual Results:  
No text, just a black band.

Expected Results:  
Expect text with message.

Want to upload image of error.
Comment 1 Indian Art 2012-06-04 06:34:01 UTC
Created attachment 71557 [details]
Error Screenshot
Comment 2 Thomas Lübking 2012-06-04 12:17:57 UTC
Press shift+alt+f12 to make the contents visible

when it shows up next time, open a terminal (konsole) and run "xprop > window.props", click the window (the black band) and attach the resulting file "window.props" to this bug.

(i think we've had this before with the ubuntu update damon thing - the window is just incredibly large - makes me wonder whether we should perform a sanity check on window dimensions, yes - is working around buggy clients...)
Comment 3 Indian Art 2012-06-04 15:26:17 UTC
Thank you Thomas for your quick response,

I followed your instructions & rebooted & the problem seems to have gone. Thanks. 

However, the screenshot before the reboot is attached along with the file when I ran your command.

Once I could read the text I clicked on "Run this action now", which seems to have helped. 

Please let me know if I need to do anything more.

(In reply to comment #2)
> Press shift+alt+f12 to make the contents visible
> 
> when it shows up next time, open a terminal (konsole) and run "xprop >
> window.props", click the window (the black band) and attach the resulting
> file "window.props" to this bug.
> 
> (i think we've had this before with the ubuntu update damon thing - the
> window is just incredibly large - makes me wonder whether we should perform
> a sanity check on window dimensions, yes - is working around buggy
> clients...)
Comment 4 Indian Art 2012-06-04 15:29:02 UTC
Created attachment 71577 [details]
Text from Konsole on running command of Thomas
Comment 5 Indian Art 2012-06-04 15:31:58 UTC
Created attachment 71578 [details]
KDE Daemon Error Snapshot before the problem was resolved
Comment 6 Thomas Lübking 2012-06-04 18:28:35 UTC
the attachment is no props but some rtf (please in general safe as plain text) containing the konsole debug while the updater was running - the command should have produced a file "window.props" itself, containing relevant informations about the window.

However: it is  precisely the issue from the ubuntu updater with the dialog and the enormously long string containing the arabian (style, i can't read that ;-) text

-> The window turns far too large to be mapped into a texture (which can only be 2048 or 4096px wide - ask "glxinfo -l | grep MAX" if you care)

*** This bug has been marked as a duplicate of bug 213267 ***