[Bug 464214] New: Yast2 missing font dependency
https://bugzilla.novell.com/show_bug.cgi?id=464214 Summary: Yast2 missing font dependency Product: openSUSE 11.1 Version: Final Platform: Other OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: volker3204@paradise.net.nz QAContact: jsrain@novell.com Found By: --- I installed a system without desktop but with minimal X, so GUI programs can be run, but as the system will only ever be used remotely an X server would be pointless. Yast2 then does not start. First xauth is missing for ssh. Then IIRC it crashes until some missing X stuff is installed, and then it's unusable because the header font is 10 metres wide and off the screen, and the normal text font isn't right either. On another system with desktop I get # grep -i font strace-yast | grep -i open | grep -i pfb 24044 open("/usr/share/fonts/URW/n019003l.pfb", O_RDONLY) = 14 24044 open("/usr/share/fonts/URW/n019004l.pfb", O_RDONLY) = 15 24125 open("/usr/share/fonts/URW/n019003l.pfb", O_RDONLY) = 14 24125 open("/usr/share/fonts/URW/n019004l.pfb", O_RDONLY) = 14 # grep -i font strace-yast | grep -i open | grep -i ttf 23981 open("/usr/share/fonts/truetype/DejaVuSans.ttf", O_RDONLY) = 4 24044 open("/usr/share/fonts/truetype/LiberationSans-Bold.ttf", O_RDONLY) = 14 24125 open("/usr/share/fonts/truetype/LiberationSans-Bold.ttf", O_RDONLY) = 14 24125 open("/usr/share/fonts/truetype/DejaVuSans.ttf", O_RDONLY <unfinished ..> After manually installing xorg-x11-fonts-core and liberation-fonts yast2 still doesn't look quite right with the fonts but it's usable. -- 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=464214 Cyril Hrubis <chrubis@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |yast2-maintainers@suse.de -- 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=464214 User tgoettlicher@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464214#c1 Thomas Göttlicher <tgoettlicher@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tgoettlicher@novell.com AssignedTo|yast2-maintainers@suse.de |sh@novell.com --- Comment #1 from Thomas Göttlicher <tgoettlicher@novell.com> 2009-01-12 04:13:31 MST --- Should we add some font requirements to the yast2-qt's spec file? One the one hand it might solve problems on untypical systems without x11 base, on the other hand it blows up dependencies. Stefan, what do you think? -- 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=464214 User volker3204@paradise.net.nz added comment https://bugzilla.novell.com/show_bug.cgi?id=464214#c2 Volker Kuhlmann <volker3204@paradise.net.nz> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |volker3204@paradise.net.nz --- Comment #2 from Volker Kuhlmann <volker3204@paradise.net.nz> 2009-01-12 13:15:58 MST --- Just crashing when missing some fonts is not a good approach. This was before I guessed that the missing fonts were indeed the first problem - and before the situation where the fonts are unuseably big. Could this be alleviated by printing an error saying which packages to install to make yast2 work, instead of printing a stack trace? Perhaps the real problem is with the pattern. Without desktop but with X implies that X programs can be run via a remote connection, e.g. ssh. Obviously that doesn't need an X server, even less a desktop, but X apps need to run. (And "with X" doesn't really say whether an X server is included or whether that refers only to X apps.) It is also not an unusual or weird system, it is very common to set up Linux systems without desktop since on a server in the corner that is not needed, but having X apps available is IMHO opinion required to stay up with the competition from France, South Africa, or Redmond. -- 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=464214 User sh@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464214#c3 Stefan Hundhammer <sh@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Yast2 missing font |YaST2 Qt crashes if some |dependency |X11 fonts are not installed --- Comment #3 from Stefan Hundhammer <sh@novell.com> 2009-01-13 04:08:58 MST --- That subject is way off-topic. What we seem to know is that there is a crash if some fonts are not installed. But we don't even know what crashes and what does not. Drawing conclusions that it's a YaST2 Qt problem and that it's due to missing font requirements is nothing but speculation. How do other Qt applications behave? How about the Qt examples? -- 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=464214 Stefan Hundhammer <sh@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |volker3204@paradise.net.nz Status Whiteboard| |#6da4 -- 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=464214 User volker3204@paradise.net.nz added comment https://bugzilla.novell.com/show_bug.cgi?id=464214#c4 Volker Kuhlmann <volker3204@paradise.net.nz> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|volker3204@paradise.net.nz | --- Comment #4 from Volker Kuhlmann <volker3204@paradise.net.nz> 2009-01-13 12:48:23 MST --- Going through with ldd I could find only 3 other qt apps: qdbus, qdbusviewer, qtconfig. qtconfig and qdbusviewer bring up a window, and let me interact with their GUI elements. There is nothing unusual about the fonts in these apps that I can see. I'll attach the changes of rpms since the crashing, you may see something obvious. I have yast logs too should they be 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=464214 User volker3204@paradise.net.nz added comment https://bugzilla.novell.com/show_bug.cgi?id=464214#c5 --- Comment #5 from Volker Kuhlmann <volker3204@paradise.net.nz> 2009-01-13 12:50:02 MST --- Created an attachment (id=264846) --> (https://bugzilla.novell.com/attachment.cgi?id=264846) Changes in installed rpms (makes crash disappear) -- 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=464214 User sh@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464214#c6 --- Comment #6 from Stefan Hundhammer <sh@novell.com> 2009-01-14 04:03:32 MST --- OK, thanks. Does YaST2 leave a backtrace in the log (/var/log/YaST2/y2log) when it crashes? Does it happen with a simple YCP example, too, or just with a full-blown YaST2 module? Minimal test case: HelloWorld.ycp http://svn.opensuse.org/svn/yast/trunk/ycp-ui-bindings/examples/HelloWorld.y... Start with: /usr/lib/YaST2/bin/y2base ./HelloWorld.ycp qt Test case with a little bit more bells and whistles: http://svn.opensuse.org/svn/yast/trunk/ycp-ui-bindings/examples/Wizard3.ycp Start with: /usr/lib/YaST2/bin/y2base ./Wizard3.ycp qt or with colorful installation theme (using different fonts - this might give a hint): export Y2STYLE=installation.qss /usr/lib/YaST2/bin/y2base ./Wizard3.ycp qt If you'd like to give that a try: The libqt4-devel-doc package includes more Qt examples (without the YaST2 framework around it) below /usr/lib/qt4/examples . -- 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=464214 Stefan Hundhammer <sh@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED -- 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=464214 User sh@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464214#c7 Stefan Hundhammer <sh@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mhopf@novell.com --- Comment #7 from Stefan Hundhammer <sh@novell.com> 2009-01-14 08:10:30 MST ---
From the package installation history of attachment #264846 (from comment #5) I don't see anything obviously suspicious.
Even though xorg-x11.rpm was missing, that should not be a problem AFAICS (Mike?). I am not sure why xorg-x11-fonts would change anything as long as there is no X font server running: X11 fonts are X server resources. The X server has to provide them. AFAIK, if it doesn't, then having the fonts on the machine where the X client (the application) is running won't have any effect. Unless, of course, that machine provides an X font server, and the X server gets the fonts from that server. -- 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=464214 User mfabian@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464214#c8 --- Comment #8 from Mike Fabian <mfabian@novell.com> 2009-01-14 08:46:34 MST --- I’m not sure whether I understand the situation correctly. Is the following correct: Machine foo: minimal system with some fonts and (parts?) of X missing. Machine bar: some fully installed system with all bells and whistles.
From "bar" ssh to "foo" with X-forwarding, start the graphical YaST2 (Qt 3/4) there, display is on "bar".
Is this correct? -- 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=464214 User mfabian@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464214#c9 --- Comment #9 from Mike Fabian <mfabian@novell.com> 2009-01-14 08:47:55 MST --- If the above situation is correct, YaST2, a Qt application, uses client side font rendering, i.e. the fonts on machine "foo" (minimal system) are used although the window is displayed on the X-server on "bar". -- 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=464214 User mfabian@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464214#c10 --- Comment #10 from Mike Fabian <mfabian@novell.com> 2009-01-14 10:39:27 MST --- Thomas Göttlicher> Should we add some font requirements to the Thomas Göttlicher> yast2-qt's spec file? No, I don’t think so. If fonts should be required at all then certainly not by YaST2 but by Qt. But I doubt that this makes sense either. -- 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=464214 User mfabian@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464214#c11 --- Comment #11 from Mike Fabian <mfabian@novell.com> 2009-01-14 10:53:53 MST --- I guess that it worked after adding the packages in the attachment to comment#5 is caused by the “fonts-config” package. If “fonts-config” is installed and SuSEconfig is run, fontconfig cache files are generated in /var/cache/fontconfig. If these caches don’t exist, the application (here YaST2 via Qt) creates caches transparently on the fly in ~/.fontconfig. As these two cases differ, I think it is possible that in one case a crash happens, in the other not. This might not be the fault of YaST2. I am not sure what will happen if no fonts at all are installed. Can you please get your system back into the state where the problem happens? Maybe you can reproduce it by uninstalling the rpms from comment#5 again and deleting all the caches in /var/cache/fontconfig and ~/.fontconfig. What is the output of fc-match and fc-list in the state of the system when the problem occurs? Do you have any fonts at all in that state or no fonts at all? -- 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=464214 User sh@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464214#c12 --- Comment #12 from Stefan Hundhammer <sh@novell.com> 2009-01-14 12:09:09 MST --- (In reply to comment #7)
X11 fonts are X server resources. The X server has to provide them. AFAIK, if it doesn't, then having the fonts on the machine where the X client (the application) is running won't have any effect.
Disregard this. This is outdated information; Mike explained it to me. These days, modern toolkits like Qt do client-side font rendering, i.e. the fonts are loaded from the machine the X client (the application) runs on. -- 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=464214 User volker3204@paradise.net.nz added comment https://bugzilla.novell.com/show_bug.cgi?id=464214#c13 --- Comment #13 from Volker Kuhlmann <volker3204@paradise.net.nz> 2009-01-14 12:32:33 MST --- The situation in comment #8 by Mike is correct. Thanks for all the suggestions, I will try them out, last ones first, after uninstalling those newer packages. -- 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=464214 User sh@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464214#c14 Stefan Hundhammer <sh@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |volker3204@paradise.net.nz --- Comment #14 from Stefan Hundhammer <sh@novell.com> 2009-01-15 03:46:23 MST --- OK, then let's wait what the outcome of this will be. Please remove NEEDINFO when you are done. -- 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=464214 Stefan Hundhammer <sh@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P4 - Low -- 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=464214 User volker3204@paradise.net.nz added comment https://bugzilla.novell.com/show_bug.cgi?id=464214#c15 Volker Kuhlmann <volker3204@paradise.net.nz> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|volker3204@paradise.net.nz | --- Comment #15 from Volker Kuhlmann <volker3204@paradise.net.nz> 2009-01-25 02:02:10 MST --- Ok I uninstalled these rpms: dbus-1-x11-1.2.4-5.1 fonts-config-20080121-25.34 ft2demos-2.3.7-24.1 gtk-1.2.10-1084.3 icewm-1.2.36-1.20 icewm-default-1.2.36-1.20 imlib-1.9.14-359.59 liberation-fonts-1.03-1.3 qt3-3.3.8b-87.11 xdg-menu-0.2-191.9 xorg-x11-7.4-8.13 xorg-x11-fonts-core-7.4-1.32 xterm-236-1.50.1 yast2-control-center-2.17.3-1.8 yast2-control-center-qt-2.17.3-1.8 and assume openmotif-libs, giflib, glib, cpp etc have no influence on the problem. This gives: # yast2 YaST got signal 11 at YCP file /usr/share/YaST2/clients/menu.ycp:32 /sbin/yast2: line 437: 17117 Segmentation fault $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS Exit 139 Even without deleting all files in /var/cache/fontconfig. There is no ~/.fontconfig. Both fc-list and fc-match produce no output, guess that means there are no fonts. The backtrace in y2log is attached (y2log-backtrace-yast2). # /usr/lib/YaST2/bin/y2base ./HelloWorld.ycp qt YaST got signal 11 at YCP file /tmp/root/HelloWorld.ycp:2 Segmentation fault Exit 139 This backtrace also attached (y2log-backtrace-helloworld). Installing fonts-config (pulls in ft2demos) again and running SuSEconfig makes no difference. Installing xorg-x11-fonts-core makes the yast2 crash disappear, though the displayed fonts look pretty shocking. This still looks like a font problem to me - no fonts, no X apps. Does this give enough info? I'm happy to run more tests. -- 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=464214 User volker3204@paradise.net.nz added comment https://bugzilla.novell.com/show_bug.cgi?id=464214#c16 --- Comment #16 from Volker Kuhlmann <volker3204@paradise.net.nz> 2009-01-25 02:04:43 MST --- Created an attachment (id=267492) --> (https://bugzilla.novell.com/attachment.cgi?id=267492) y2log-backtrace-yast2 -- 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=464214 User volker3204@paradise.net.nz added comment https://bugzilla.novell.com/show_bug.cgi?id=464214#c17 --- Comment #17 from Volker Kuhlmann <volker3204@paradise.net.nz> 2009-01-25 02:05:17 MST --- Created an attachment (id=267493) --> (https://bugzilla.novell.com/attachment.cgi?id=267493) y2log-backtrace-helloworld -- 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=464214 User sh@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464214#c18 Stefan Hundhammer <sh@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|sh@novell.com |dmueller@novell.com --- Comment #18 from Stefan Hundhammer <sh@novell.com> 2009-01-27 08:06:20 MST --- Yes, thanks, that information looks very informative. Mike: This looks very much like what we discussed. IMHO this is a Qt4 problem.
From the backtraces:
Frame 3: /usr/lib/libQtGui.so.4 QFontDatabase::load(QFontPrivate const*, int) Frame 4: /usr/lib/libQtGui.so.4 QFontPrivate::engineForScript(int) const Frame 5: /usr/lib/libQtGui.so.4 QFontMetricsF::leading() const Frame 6: /usr/lib/libQtGui.so.4 [0x41303973] Frame 7: /usr/lib/libQtGui.so.4 [0x41304031] Frame 8: /usr/lib/libQtGui.so.4 QFontMetrics::boundingRect(QRect const&, int, QString const&, int, int*) const Frame 9: /usr/lib/libQtGui.so.4 [0x4158d884] Frame 10: /usr/lib/libQtGui.so.4 QLabel::minimumSizeHint() const Frame 11: /usr/lib/libQtGui.so.4 QLabel::sizeHint() const Frame 12: /usr/lib/YaST2/plugin/libpy2qt.so.2 YQLabel::preferredHeight() Frame 13: /usr/lib/libyui.so.3 YWidget::preferredSize(YUIDimension) Frame 3: /usr/lib/libQtGui.so.4 QFontDatabase::load(QFontPrivate const*, int) Frame 4: /usr/lib/libQtGui.so.4 QFontPrivate::engineForScript(int) const Frame 5: /usr/lib/libQtGui.so.4 QFontMetricsF::leading() const Frame 6: /usr/lib/libQtGui.so.4 [0x4133a973] Frame 7: /usr/lib/libQtGui.so.4 [0x4133b031] Frame 8: /usr/lib/libQtGui.so.4 QFontMetrics::boundingRect(QRect const&, int, QString const&, int, int*) const Frame 9: /usr/lib/libQtGui.so.4 [0x415c4884] Frame 10: /usr/lib/libQtGui.so.4 QLabel::minimumSizeHint() const Frame 11: /usr/lib/libQtGui.so.4 QLabel::sizeHint() const Frame 12: /usr/lib/YaST2/plugin/libpy2qt.so.2 YQLabel::preferredHeight() Frame 13: /usr/lib/libyui.so.3 YWidget::preferredSize(YUIDimension) -- 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=464214 User sh@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464214#c19 Stefan Hundhammer <sh@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sh@novell.com --- Comment #19 from Stefan Hundhammer <sh@novell.com> 2009-01-27 08:17:09 MST --- Dirk, I am not sure how we could fix or prevent that. If Qt relies on presence of client-side fonts, IMHO libqt4 package (not the yast2-qt package) should require at least one font package. To do that, our X11 font packages would have to provide a symbol like "X11-font" that libqt4 or other similar packages (libgtk2 ?) require. -- 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=464214 User tgoettlicher@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464214#c20 --- Comment #20 from Thomas Göttlicher <tgoettlicher@novell.com> 2009-03-17 10:22:08 MST --- *** Bug 461136 has been marked as a duplicate of this bug. *** https://bugzilla.novell.com/show_bug.cgi?id=461136 -- 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=464214 User david.casson@ntlworld.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464214#c21 David Casson <david.casson@ntlworld.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |david.casson@ntlworld.com --- Comment #21 from David Casson <david.casson@ntlworld.com> 2009-03-18 08:53:52 MST --- It seems to fail for me using a text only console screen on the local machine. -- 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.
From a user perspective I've been able to try a few tests today that led to some more info. Don't know if it will help but it concerns the Repositories
https://bugzilla.novell.com/show_bug.cgi?id=464214 User david.casson@ntlworld.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464214#c22 --- Comment #22 from David Casson <david.casson@ntlworld.com> 2009-03-20 14:14:34 MST --- that are configured and enabled. After reading a few posts on the open SuSE forums it seemed some users had a degree of success with changing configured repositories. So I gave it a try and disabled all of mine except Packman.org and the problem is still there. - Segfault as soon as yast2 tries to build the repository cache. Next I tried disabling all repositories and apart from a whinge about no repositories I go no segfault crash! (The first time I've seen yast software management working on this machine since the beginning of the year.) So I next tried just enabling the Main (OSS) repository at download.opensuse.org with complete success. yast also now works from a root console login (TRL-ALT-F2). Further investigation revealed that the following repositories work in either the X11 GUI or on a console login: Main Repository (OSS) Main Repository (Non-OSS) Open Office for SuSE 10.3 STABLE Virtualisation: VirtualBox SuSE 11.1 The following would apparently work as far as setting up the repository details and enabling them but all caused the software management module to segfault in either the X11 GUI or on a console login. I included trying various different mirrors and protocols but to no avail. Open SuSE : Tools Mozilla Packman Repository VideoLan Repository Packman (Unixheads.org) Updates Repository (SuSE 10.3) When the cause is discovered it would be great if someone could give a brief guide for the inexperienced to implement the fix as many relaatively new users seem to have lost the yast functionality to apply any update through this bug so perhaps it is also (IMHO) worth considering an upgrade of the current importance of the bug to somewhat higher than 4 . -- 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.
From a user perspective I've been able to try a few tests today that led to some more info. Don't know if it will help but it concerns the Repositories
https://bugzilla.novell.com/show_bug.cgi?id=464214 User david.casson@ntlworld.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464214#c23 --- Comment #23 from David Casson <david.casson@ntlworld.com> 2009-03-20 14:19:32 MST --- that are configured and enabled. After reading a few posts on the open SuSE forums it seemed some users had a degree of success with changing configured repositories. So I gave it a try and disabled all of mine except Packman.org and the problem is still there. - Segfault as soon as yast2 tries to build the repository cache. Next I tried disabling all repositories and apart from a whinge about no repositories I go no segfault crash! (The first time I've seen yast software management working on this machine since the beginning of the year.) So I next tried just enabling the Main (OSS) repository at download.opensuse.org with complete success. yast also now works from a root console login (TRL-ALT-F2). Further investigation revealed that the following repositories work in either the X11 GUI or on a console login: Main Repository (OSS) Main Repository (Non-OSS) Open Office for SuSE 10.3 STABLE Virtualisation: VirtualBox SuSE 11.1 The following would apparently work as far as setting up the repository details and enabling them but all caused the software management module to segfault in either the X11 GUI or on a console login. I included trying various different mirrors and protocols but to no avail. Open SuSE : Tools Mozilla Packman Repository VideoLan Repository Packman (Unixheads.org) Updates Repository (SuSE 10.3) When the cause is discovered it would be great if someone could give a brief guide for the inexperienced to implement the fix as many relaatively new users seem to have lost the yast functionality to apply any update through this bug so perhaps it is also (IMHO) worth considering an upgrade of the current importance of the bug to somewhat higher than 4 . I would further suggest that while there does seem to be a link with a fonts issue my system displays the problem in spite of having some fonts installed for "X" so perhaps the title of the bug could be misleading to "some" readers too, DC -- 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.
From a user perspective I've been able to try a few tests today that led to some more info. Don't know if it will help but it concerns the Repositories
https://bugzilla.novell.com/show_bug.cgi?id=464214 User david.casson@ntlworld.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464214#c24 --- Comment #24 from David Casson <david.casson@ntlworld.com> 2009-03-20 14:21:05 MST --- that are configured and enabled. After reading a few posts on the open SuSE forums it seemed some users had a degree of success with changing configured repositories. So I gave it a try and disabled all of mine except Packman.org and the problem is still there. - Segfault as soon as yast2 tries to build the repository cache. Next I tried disabling all repositories and apart from a whinge about no repositories I got no segfault crash! (The first time I've seen yast software management working on this machine since the beginning of the year.) So I next tried just enabling the Main (OSS) repository at download.opensuse.org with complete success. yast also now works from a root console login (TRL-ALT-F2). Further investigation revealed that the following repositories work in either the X11 GUI or on a console login: Main Repository (OSS) Main Repository (Non-OSS) Open Office for SuSE 10.3 STABLE Virtualisation: VirtualBox SuSE 11.1 The following would apparently work as far as setting up the repository details and enabling them but all caused the software management module to segfault in either the X11 GUI or on a console login. I included trying various different mirrors and protocols but to no avail. Open SuSE : Tools Mozilla Packman Repository VideoLan Repository Packman (Unixheads.org) Updates Repository (SuSE 10.3) When the cause is discovered it would be great if someone could give a brief guide for the inexperienced to implement the fix as many relaatively new users seem to have lost the yast functionality to apply any update through this bug so perhaps it is also (IMHO) worth considering an upgrade of the current importance of the bug to somewhat higher than 4 . I would further suggest that while there does seem to be a link with a fonts issue my system displays the problem in spite of having some fonts installed for "X" so perhaps the title of the bug could be misleading to "some" readers too, DC -- 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=464214 User david.casson@ntlworld.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464214#c25 --- Comment #25 from David Casson <david.casson@ntlworld.com> 2009-03-20 14:23:57 MST --- Apologies for the multiple postings. As a new poster I didn't realise that editing would not overwrite the earlier ones but would send again. mea culpa. -- 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=464214 User teuniz@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464214#c26 T. van Beelen <teuniz@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |teuniz@gmail.com --- Comment #26 from T. van Beelen <teuniz@gmail.com> 2009-03-23 13:06:06 MST --- Just for your information: I'm using OpenSUSE 11.0 with KDE 3.5.9. I installed libqt4 version 4.5.0.via Yast by adding the repo download.opensuse.org/repositories/KDE%3a/Qt45/openSUSE_11.0. After the installation has finished, when I started Yast again and choose "software", Yast crashes with the following message: YaST got signal 11 at YCP file /usr/share/YaST2/clients/inst_packages.ycp:36 /sbin/yast2: line 421: 3545 Segmentation fault $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS I repaired this by using yast in textmode and changed the repo for the qt-libs back to: download.opensuse.org/repositories/KDE%3a/Qt44/openSUSE_11.0. Than I installed the former version of libqt4 (4.4.3). Now I can use Yast in graphical mode again. -- 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=464214 User david.casson@ntlworld.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464214#c27 --- Comment #27 from David Casson <david.casson@ntlworld.com> 2009-03-24 02:46:45 MST --- Using openSuSE10.3, when I attempt to add the repository: http://download.opensuse.org/repositories/KDE:/Qt44/openSUSE_10.3/ yast2 segfaults even attempting to enable that repository. -- 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=464214 User teuniz@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464214#c28 --- Comment #28 from T. van Beelen <teuniz@gmail.com> 2009-03-24 02:52:26 MST --- David, use the console, login as root and start yast in textmode by typing "yast", not "yast2". -- 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=464214 User david.casson@ntlworld.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464214#c29 --- Comment #29 from David Casson <david.casson@ntlworld.com> 2009-03-24 04:35:56 MST --- Thanks T ... That was a typo sorry. I did use yast from a root console login which then brings up a text character based version of Yast2 on a CTRL-ALT-F2 screen. Even though I type in "yast" the top line of the program identifies itself as Yast2. I don't get the X-server crash on a console of course but yast still calls the repo management module and the software management modules and when either of those executes the repository cache building process they both still fail as above on my earlier posts. I did discover last week that the problem seems to be repository dependent too but I'm not sure that makes much sense? I did document it above though, (3 times unfortunately) and it could really do with an admin tidying it up a bit removing the first 2 almost duplicates. I'm using SuSE 10.3 with KDE 3.5.7 and I believe the problem only began to occur after an automatic update back in January. -- 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