Bug 102980 - description in runlevel editor
Summary: description in runlevel editor
Status: RESOLVED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Beta 1
Hardware: Other All
: P5 - None : Normal
Target Milestone: ---
Assignee: Lukas Ocilka
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-09 10:31 UTC by Andreas Klein
Modified: 2005-08-18 20:30 UTC (History)
1 user (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
/tmp/runlevel-2-simple-000.png (161.38 KB, image/png)
2005-08-09 10:32 UTC, Andreas Klein
Details
normal screenshot (141.86 KB, image/png)
2005-08-09 13:19 UTC, Lukas Ocilka
Details
smaller screenshot (107.03 KB, image/png)
2005-08-09 13:19 UTC, Lukas Ocilka
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Andreas Klein 2005-08-09 10:31:55 UTC
If the description of a service in the runlevel editor is too long, it can't be
read completely. The scrollbar on the right side does not allow scrolling down
to the end of the description.
This is the case for acpid, hal and various others.
Will attach screenshot
Comment 1 Andreas Klein 2005-08-09 10:32:27 UTC
Created attachment 45262 [details]
/tmp/runlevel-2-simple-000.png
Comment 2 Lukas Ocilka 2005-08-09 10:48:32 UTC
This has been already fixed and works for me. Tested on Beta 1.
I'll test it again after I install new Beta 1 again.
Comment 3 Andreas Klein 2005-08-09 10:52:45 UTC
It only works, if you start the runlevel edit in full-screen mode. If you use it
with the default windowsize, it does not work. The screenshot I attaches was
created on the SUSE 10 beta 1!
Comment 4 Lukas Ocilka 2005-08-09 11:24:09 UTC
I'll attach my screenshot when I got my new Beta1 installed and we could compare.

I saw it in 800x600 Qt window and even smaller and it worked well. It wasn't in
FullScreen mode. I have fixed that already.

Could you, please, write here your yast2-runlevel's version?
`rpm -qa | grep yast2-runlevel`
Comment 5 Andreas Klein 2005-08-09 11:35:30 UTC
yast2-runlevel-2.12.3-2
Comment 6 Lukas Ocilka 2005-08-09 12:06:02 UTC
Funny thing, runlevel in my new Beta installation doesn't work at all because of
some `awk`-related problems parsing the configuration....
Comment 7 Lukas Ocilka 2005-08-09 13:19:20 UTC
Created attachment 45313 [details]
normal screenshot
Comment 8 Lukas Ocilka 2005-08-09 13:19:41 UTC
Created attachment 45314 [details]
smaller screenshot
Comment 9 Lukas Ocilka 2005-08-09 13:23:39 UTC
From my point of view, your yast2-core/UI might be broken (You have reported
another UI-related bug(s)).

And as you can see, my Beta1 (with fixed `awk`-related problem) can display it
well, and also other ones I have seen. Please, decide, whether I could fix it
somehow when it doesn't appear on any other system?
Comment 10 Andreas Klein 2005-08-09 14:05:50 UTC
Ok, I will try to install another machine today or tomorrow. Or do you have
another version installed and I should wait untill beta2?
Comment 11 Lukas Ocilka 2005-08-09 20:16:22 UTC
I think that we use just the same version of the package, but I run it in
another environment. That might be the problem.

Do you use KDE, Gnome or another windowmanager? Which theme is used in the
windowmanager? That might be the difference: take note that although our
screenshots should be the same, fonts, buttons and layout might be a bit
different...

And if it is a problem of visual presentation, it would be rather Qt bug (or
unconsidered feature). It works well in ncurses (textual mode).
Comment 12 Andreas Klein 2005-08-10 09:29:16 UTC
Ok, that's what I did:
- new installation on a clean disk
- software selection: all package categories (Base, KDE, All Of KDE, ...)
- at the end of installation a new user account was created
- login into that account (KDE standard); sux -; yast2
Comment 13 Lukas Ocilka 2005-08-11 07:54:33 UTC
Please, test it in beta2 after it is released...
Thanks
Comment 14 Andreas Klein 2005-08-17 12:40:35 UTC
Ok, will test it with beta2. Maybe the problem is the same as in bug 102981?
Comment 15 Lukas Ocilka 2005-08-17 12:44:22 UTC
Definitely - "might" be :)
But I've enlarged the space for it just before the Beta1.
Let's test it again...
Comment 16 Andreas Klein 2005-08-18 20:30:54 UTC
It works in beta2!