[Bug 835299] New: xmessage window content illegible at above average display density
https://bugzilla.novell.com/show_bug.cgi?id=835299 https://bugzilla.novell.com/show_bug.cgi?id=835299#c0 Summary: xmessage window content illegible at above average display density Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 4 Platform: All OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Usability AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: mrmazda@earthlink.net QAContact: qa-bugs@suse.de Found By: --- Blocker: --- Created an attachment (id=552954) --> (http://bugzilla.novell.com/attachment.cgi?id=552954) 144 DPI screenshot of Konsole, font settings, YaST2 & error message window generated by YaST2 failure This isn't new in M4. Actually it is years old. Error message windows generated by YaST2 failures do not heed any of the several configured text sizes specified either in KDE settings, or in Trolltech.conf. They should. That way they should be legible and thus useful. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=835299 https://bugzilla.novell.com/show_bug.cgi?id=835299#c FeiXiang Zhang <fxzhang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |sndirsch@suse.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=835299 https://bugzilla.novell.com/show_bug.cgi?id=835299#c1 Stefan Dirsch <sndirsch@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |fxzhang@suse.com --- Comment #1 from Stefan Dirsch <sndirsch@suse.com> 2013-08-21 13:27:54 UTC --- Why has this bugreport been assigned to me, please? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=835299 https://bugzilla.novell.com/show_bug.cgi?id=835299#c3 Stefan Dirsch <sndirsch@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |mrmazda@earthlink.net --- Comment #3 from Stefan Dirsch <sndirsch@suse.com> 2013-08-22 08:08:23 UTC --- What is this bugreport about? About enhancing xmessage to use clientside fontrendering (via libfonconfig/libXft) or about replacing xmessage with e.g. KDE message, GNOME message (whatever matches the used desktop). Chances that xmessage is going to be enhanced in that way is rather low though (to phrase it positively). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=835299 https://bugzilla.novell.com/show_bug.cgi?id=835299#c5 Felix Miata <mrmazda@earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|mrmazda@earthlink.net | --- Comment #5 from Felix Miata <mrmazda@earthlink.net> 2013-08-22 09:02:04 UTC --- (In reply to comment #3)
What is this bugreport about?
It's about making error message text size legible. Illegible messages are useless. How to go about it I really don't know. Device pixel densities are all over the place now, and getting even more so for the foreseeable future. So, presenting error messages sized using pixels of indefinite size as the xterms that xmessage seems to be using needs to stop. If in fact xterms are simply being called, it seems the caller could find an appropriate point size in a Trolltech.conf or other existing font configuration file and if found call the xterm with -fa. Even if not found, a point size fallback/default of 10 should work a lot better than pixels that could render at 4pt or less. YaST2 is built with a new toolset now, so maybe someone who knows how to use and/or learn that toolset can come up with something that wasn't previously available. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=835299 https://bugzilla.novell.com/show_bug.cgi?id=835299#c6 Egbert Eich <eich@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |eich@suse.com InfoProvider| |mrmazda@earthlink.net AssignedTo|sndirsch@suse.com |coolo@suse.com --- Comment #6 from Egbert Eich <eich@suse.com> 2013-08-22 10:07:59 UTC --- This xmessage window has existed for many years in X sessions started by a display manager which still use the xdm session startup and shutdown scripts. It has been part of those scripts for as long as I use SUSE at least. At the time it was added screen resolutions were low and there was no issue with readability of the default font. xmessage is an application belonging to the set of X.Org applications that still stem from the early days of the X Window System. It uses server side fonts font rendering (core fonts), fonts can only be controlled by Xresources. core fonts don't allow screen resolution dependent font scaling. A solution would be to a. Set a resource before starting xmessage which sets a different and bigger font. However considering the range of screen resolutions we have today, We could not just pick a single font so this would be difficult. b. Replace xmessage with some more modern applcation providing similar services but doing client side fonts. Not sure if such a thing exists. c. Throw away xmessage (ie deleting it from the xdm startup scripts). With an xmessage window no longer showing we will no longer seeing complaints about it not being readable. This is not an xmessage issue as xmessage itself is working as expected but a 'improve openSUSE look and feel'. Thus assigning this to the xmessage package owner is the wrong strategy. In openSUSE a solution like c - although it is a quite harsh approach - has often been employed to get rid of some annoyance. In any case, researching the different options would be something for the openSUSE community to find out. Thus assigning to the openSUSE project manager. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=835299 https://bugzilla.novell.com/show_bug.cgi?id=835299#c Egbert Eich <eich@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|mrmazda@earthlink.net | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=835299 https://bugzilla.novell.com/show_bug.cgi?id=835299#c7 Stephan Kulow <coolo@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |mrmazda@earthlink.net --- Comment #7 from Stephan Kulow <coolo@suse.com> 2013-09-27 10:46:14 CEST --- "error message window generated by YaST2 failure" sounds like the window was not there before yast failed, which makes egbert's statement useless. So I wonder how the xmessage dialog got there, I can't find xmessage in yast sources. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=835299 https://bugzilla.novell.com/show_bug.cgi?id=835299#c8 Felix Miata <mrmazda@earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|mrmazda@earthlink.net | --- Comment #8 from Felix Miata <mrmazda@earthlink.net> 2013-09-27 17:23:52 UTC --- Oops. I should have mentioned in comment 0 what I opened YaST to do. I filed this 7 weeks ago. I have no recollection what I was doing at the time that might have caused YaST to fail. I do remember seeing similar xmessage windows at various times over the years. With the gx62b host I was using then, /usr/share/fontconfig/conf.avail/50-user.conf that /etc/fonts/conf.d/56-user.conf (in the screenshot's xmessage window) symlinks to is now dated 2 Sept. It's not happening today by simply opening YaST, but the host has since been dup'd from M4 to B1, and its X is not operating normally due to bug 841696. I suspect if bug 833437 were fixed this would go away on its own. To recreate an xmessage window generation, maybe rpm -e --nodeps some package YaST depends on might work? ISTR yast2-bootloader (or would that be perl-Bootloader or mkinitrd?) doesn't like having uninstalled mdadm, a package which NAICT is pointless on systems not using RAID (and needlessly swells initrds). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=835299 https://bugzilla.novell.com/show_bug.cgi?id=835299#c9 Stephan Kulow <coolo@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |NORESPONSE --- Comment #9 from Stephan Kulow <coolo@suse.com> 2013-09-30 12:13:46 CEST --- if you don't know, I won't fiddle around with my system. Best is to open a bug that yast uses xmessage at all - so confusions like Egbert's and Stefan's can't happen. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=835299 https://bugzilla.novell.com/show_bug.cgi?id=835299#c10 Felix Miata <mrmazda@earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|NORESPONSE | --- Comment #10 from Felix Miata <mrmazda@earthlink.net> 2013-10-06 05:20:02 UTC --- To see how tiny xmessage text is at above average display density it is necessary only to enter xmessage and some text at a shell prompt, or in run command, using a higher than average DPI display, or emulating a high DPI display via DisplaySize values higher than actual in xorg.conf*. Xmessage is an ordinary arch-specific package in OSS repo, and on which kdebase4-session, kdebase4-workspace, kdm and kwin, among others not including yast2*, depend. Maybe this belongs assigned to KDE maintainers. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=835299 https://bugzilla.novell.com/show_bug.cgi?id=835299#c11 --- Comment #11 from Felix Miata <mrmazda@earthlink.net> 2013-10-15 13:47:10 UTC --- Created an attachment (id=563521) --> (http://bugzilla.novell.com/attachment.cgi?id=563521) screenshot showing xterm font size improvement approaching 60% of desired size by including 'xterm*vt100.initialFont: 6' in ~/.Xresources Note that 6 is the largest size configurable in xterm, which goes by the label "huge". As yet I've been unable to determine how to implement any improvement via /etc/X11/Xresources, /etc/X11/xdm/Xresources or anything else in /etc/X11/, or to get xmessage to incorporate improvement implemented in xterm via ~/.Xresources. (In reply to comment #9)
Best is to open a bug that yast uses xmessage at all
YaST2 apparently uses xmessage because the DE is KDE. 'zypper rm xmessage' wants to remove: kdebase4-openSUSE kdebase4-session kdebase4-workspace kdebase4-workspace-ksysguardd kdebase4-workspace-liboxygenstyle kdm kwin xmessage -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=835299 https://bugzilla.novell.com/show_bug.cgi?id=835299#c12 Stephan Kulow <coolo@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|coolo@suse.com |yast2-maintainers@suse.de --- Comment #12 from Stephan Kulow <coolo@suse.com> 2013-11-11 08:42:45 CET --- Wherever yast is using xmessage for KDE - use kdialog --sorry or similiar -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=835299 https://bugzilla.novell.com/show_bug.cgi?id=835299#c13 Lukas Ocilka <locilka@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|yast2-maintainers@suse.de |mvidner@suse.com --- Comment #13 from Lukas Ocilka <locilka@suse.com> 2013-11-29 15:49:23 UTC --- Martin, one for you -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=835299 https://bugzilla.novell.com/show_bug.cgi?id=835299#c14 Martin Vidner <mvidner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |WONTFIX --- Comment #14 from Martin Vidner <mvidner@suse.com> 2013-12-02 17:06:40 CET --- Actually we have removed that xmessage popup completely in 13.1 ( https://github.com/yast/yast-yast2/commit/232eac7377482d5f539642d78b3d0f474d... ) and now the error messages simply go to ~/.xsession-errors as for other programs without the console. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com