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.