New 13.1 x86 32-bit install KDE Xorg crashes launching apps

English Install/Boot/Login
#1

New install of openSuSE 13.1 on x86 32-bit server. Installation went smoothly, and all available updates from the default repositories are installed via Yast online update.

If I click on the Firefox or OpenOffice icons on the plasma desktop, X crashes every time, blowing me completely back to the graphical desktop login screen.

This happens on two different motherboard types (one IBM, one Intel) that I have tried it on. Different monitors. Different VGA chips. I see that there were some 32-bit only problems similar to this back in August (pre 13.1 general availability release), but surely these would have been repaired by now in 13.1, wouldn’t they? Reference, for example, https://bugs.kde.org/show_bug.cgi?id=322283

This problem, of course, makes migrating to this release impossible in my environment.

Anybody have any insight on this problem? Known? Being worked on? Nobody cares because it is 32-bit?

The .xsession-error file:

/etc/X11/xim: Checking whether an input method should be started.
sourcing /etc/sysconfig/language to get the value of INPUT_METHOD
INPUT_METHOD is not set or empty (no user selected input method).
Trying to start a default input method for the locale en_US.UTF-8 ...
There is no default input method for the current locale.
Dummy input method "none" (do not use any fancy input method by default)
startkde: Starting up...
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
kbuildsycoca4 running...
This backend is only for XRandR 1.1, your version is:  1 . 3
QObject::connect: Cannot connect (null)::deviceFound(Device*) to BlueDevilDaemon::deviceFound(Device*)
QObject::connect: Cannot connect QTimer::timeout() to (null)::stopDiscovery()
No outputs have backlight property
QDBusConnection: name 'org.kde.kglobalaccel' had owner '' but we thought it was ':1.5'
Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)
Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)
QObject::connect: Cannot connect (null)::resourceScoreUpdated(QString, QString, QString, double) to NepomukPlugin::resourceScoreUpdated(QString, QString, QString, double)
QObject::connect: Cannot connect (null)::recentStatsDeleted(QString, int, QString) to NepomukPlugin::deleteRecentStats(QString, int, QString)
QObject::connect: Cannot connect (null)::earlierStatsDeleted(QString, int) to NepomukPlugin::deleteEarlierStats(QString, int)
QDBusConnection: name 'org.freedesktop.UDisks2' had owner '' but we thought it was ':1.14'
kded(4622) PowerDevil::Core::loadProfile: The profile  "AC" tried to activate "DimDisplay" a non existent action. This is usually due to an installation problem or to a configuration problem. or simlpy the action is not supported
kded(4622) PowerDevil::Core::loadProfile: The profile  "AC" tried to activate "BrightnessControl" a non existent action. This is usually due to an installation problem or to a configuration problem. or simlpy the action is not supported
kwin(4703): ""fsrestore1" - conversion of "0,0,0,0" to QRect failed"
QCoreApplication::sendPostedEvents: Cannot send posted events for objects in another thread
QCoreApplication::sendPostedEvents: Cannot send posted events for objects in another thread
QCoreApplication::sendPostedEvents: Cannot send posted events for objects in another thread
QCoreApplication::sendPostedEvents: Cannot send posted events for objects in another thread
QDBusObjectPath: invalid path ""
plasma-desktop(4706)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability
plasma-desktop(4706)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability
plasma-desktop(4706)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability
plasma-desktop(4706)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability
plasma-desktop(4706)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability
plasma-desktop(4706)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability
Object::connect: No such signal QDBusAbstractInterface::StateChanged(uint)
QGraphicsLinearLayout::insertItem: cannot insert null item
plasma-desktop(4706)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability
QGraphicsLinearLayout::insertItem: cannot insert null item
Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)
Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
========================>  7 0
static bool QDeclarativeMetaType::isModule(const QByteArray&, int, int) Qt 4.7 import detected; please note that Qt 4.7 is directly reusable as QtQuick 1.x with no code changes. Continuing, but startup time will be slower.
file:///usr/lib/kde4/imports/org/kde/plasma/components/Button.qml:194:5: QML Row: Possible anchor loop detected on fill.
file:///usr/lib/kde4/imports/org/kde/plasma/components/Button.qml:194:5: QML Row: Possible anchor loop detected on fill.
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
file:///usr/lib/kde4/imports/org/kde/plasma/components/SectionScroller.qml:103: TypeError: Result of expression 'listView' [null] is not an object.
file:///usr/lib/kde4/imports/org/kde/plasma/components/SectionScroller.qml:175: ReferenceError: Can't find variable: sectionsRepeater
file:///usr/lib/kde4/imports/org/kde/plasma/components/SectionScroller.qml:103: Error: Cannot assign [undefined] to QString
file:///usr/share/kde4/apps/plasma/plasmoids/notifier/contents/ui/devicenotifier.qml:224:13: QML QDeclarativeListView_QML_103: Possible anchor loop detected on fill.
file:///usr/share/kde4/apps/plasma/plasmoids/notifier/contents/ui/devicenotifier.qml:224:13: QML QDeclarativeListView_QML_103: Possible anchor loop detected on fill.
file:///usr/share/kde4/apps/plasma/plasmoids/notifier/contents/ui/devicenotifier.qml:224:13: QML QDeclarativeListView_QML_103: Possible anchor loop detected on fill.
file:///usr/share/kde4/apps/plasma/plasmoids/notifier/contents/ui/devicenotifier.qml:224:13: QML QDeclarativeListView_QML_103: Possible anchor loop detected on fill.
file:///usr/share/kde4/apps/plasma/plasmoids/notifier/contents/ui/devicenotifier.qml:224:13: QML QDeclarativeListView_QML_103: Possible anchor loop detected on fill.
file:///usr/share/kde4/apps/plasma/plasmoids/notifier/contents/ui/devicenotifier.qml:224:13: QML QDeclarativeListView_QML_103: Possible anchor loop detected on fill.
file:///usr/share/kde4/apps/plasma/plasmoids/notifier/contents/ui/devicenotifier.qml:224:13: QML QDeclarativeListView_QML_103: Possible anchor loop detected on fill.
link XMLID_34_ hasn't been detected!
link XMLID_34_ hasn't been detected!
link XMLID_36_ hasn't been detected!
file:///usr/share/kde4/apps/plasma/plasmoids/battery/contents/ui/CompactRepresentation.qml:73:9: QML Column: Cannot specify top, bottom, verticalCenter, fill or centerIn anchors for items inside Column
link XMLID_34_ hasn't been detected!
link XMLID_34_ hasn't been detected!
link XMLID_36_ hasn't been detected!
Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)
Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)
W: [pulseaudio] main.c: This program is not intended to be run as root (unless --system is specified).
W: [pulseaudio] main.c: This program is not intended to be run as root (unless --system is specified).
New PolkitAgentListener  0x8448f90
Adding new listener  PolkitQt1::Agent::Listener(0x8574708) for  0x8448f90
Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)
Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)
Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)
Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)
plasma-desktop(4706)/plasma StatusNotifierItemSource::refreshCallback: DBusMenu disabled for this application
plasma-desktop(4706)/plasma StatusNotifierItemSource::refreshCallback: DBusMenu disabled for this application
Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)
Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)
I/O warning : failed to load external entity "/usr/share/qalculate/prefixes.xml"
I/O warning : failed to load external entity "/usr/share/qalculate/currencies.xml"
I/O warning : failed to load external entity "/usr/share/qalculate/units.xml"
I/O warning : failed to load external entity "/usr/share/qalculate/functions.xml"
I/O warning : failed to load external entity "/usr/share/qalculate/datasets.xml"
I/O warning : failed to load external entity "/usr/share/qalculate/variables.xml"
I/O warning : failed to load external entity "/usr/share/qalculate/currencies.xml"
I/O warning : failed to load external entity "/root/.qalculate/eurofxref-daily.xml"
I/O warning : failed to load external entity "/root/.qalculate/eurofxref-daily.xml"
Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)
Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)
Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)
Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)
kbuildsycoca4 running...
kwalletd: Fatal IO error: client killed
kdeinit4: Fatal IO error: client killed
kdeinit4: sending SIGHUP to children.
kded4: Fatal IO error: client killed
klauncher: Exiting on signal 1
soffice.bin: Fatal IO error: client killed
kglobalaccel: Fatal IO error: client killed
kwin: Fatal IO error: client killed
kdeinit4: Fatal IO error: client killed
kdeinit4: sending SIGHUP to children.
kdeinit4: sending SIGTERM to children.
kdeinit4: Exit.
QProcess: Destroyed while process is still running.
ksmserver: Fatal IO error: client killed
kdeinit4: sending SIGTERM to children.
kdeinit4: Exit.

The Xorg.0.log.old file ends with:

   538.135] (EE) 
   538.135] (EE) Backtrace:
   538.157] (EE) 0: /usr/bin/Xorg (xorg_backtrace+0x49) [0x81df3e9]
   538.157] (EE) 1: /usr/bin/Xorg (0x8048000+0x19b174) [0x81e3174]
   538.157] (EE) 2: linux-gate.so.1 (__kernel_rt_sigreturn+0x0) [0xb777240c]
   538.157] (EE) 3: /usr/lib/xorg/modules/drivers/mach64_drv.so (0xb6d2d000+0x1e645) [0xb6d4b645]
   538.157] (EE) 4: /usr/lib/xorg/modules/drivers/mach64_drv.so (0xb6d2d000+0x1e72c) [0xb6d4b72c]
   538.157] (EE) 5: /usr/lib/xorg/modules/libexa.so (0xb6358000+0xc609) [0xb6364609]
   538.157] (EE) 6: /usr/bin/Xorg (0x8048000+0x11a971) [0x8162971]
   538.157] (EE) 7: /usr/bin/Xorg (CompositeGlyphs+0xa6) [0x8150ec6]
   538.157] (EE) 8: /usr/bin/Xorg (0x8048000+0x11411c) [0x815c11c]
   538.157] (EE) 9: /usr/bin/Xorg (0x8048000+0x10fbbd) [0x8157bbd]
   538.157] (EE) 10: /usr/bin/Xorg (0x8048000+0x36ecd) [0x807eecd]
   538.157] (EE) 11: /usr/bin/Xorg (0x8048000+0x24f6a) [0x806cf6a]
   538.157] (EE) 12: /lib/libc.so.6 (__libc_start_main+0xf3) [0xb72749d3]
   538.157] (EE) 13: /usr/bin/Xorg (0x8048000+0x25339) [0x806d339]
   538.157] (EE) 
   538.157] (EE) Segmentation fault at address 0xc
   538.157] (EE) 
Fatal server error:
   538.157] (EE) Caught signal 11 (Segmentation fault). Server aborting
   538.157] (EE) 
   538.157] (EE) 
Please consult the The X.Org Foundation support 
         at http://wiki.x.org
 for help. 
   538.157] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
   538.157] (EE) 
   538.257] (EE) Server terminated with error (1). Closing log file.


lspci | grep VGA
00:09.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Rage XL PCI (rev 27)

I added nomodeset to the grub defaults per the release notes, but this does not seem related.

grep GRUB_CMDLINE_LINUX_DEFAULT /etc/default/grub
#GRUB_CMDLINE_LINUX_DEFAULT=" video=1024x768 resume=/dev/sdc2 splash=silent quiet showopts vga=0x318"
GRUB_CMDLINE_LINUX_DEFAULT=" video=1024x768 resume=/dev/sdc2 splash=silent quiet showopts nomodeset"
#2

Something like this is caused by a problem with the graphics driver most of the time. It’s just coincidence that it happens on 2 systems with different VGA chips I’d say.

I see that there were some 32-bit only problems similar to this back in August (pre 13.1 general availability release), but surely these would have been repaired by now in 13.1, wouldn’t they? Reference, for example, https://bugs.kde.org/show_bug.cgi?id=322283

The bug you reference has been fixed before 13.1 was released.
And that bug didn’t make X crash. It was about just plasma-desktop crashing on login so you ended up with a black screen and mouse cursor.
Starting plasma-desktop manually (via Alt+F2 f.e.) worked though.

Anybody have any insight on this problem? Known? Being worked on? Nobody cares because it is 32-bit?

Neither of this is true I would say. I don’t think this is a 32bit specific problem, it seems to be related to the gfx driver, see also your X log.
mach64 is quite old and not very well maintained anymore.

The Xorg.0.log.old file ends with:

   538.135] (EE) 
   538.135] (EE) Backtrace:
   538.157] (EE) 0: /usr/bin/Xorg (xorg_backtrace+0x49) [0x81df3e9]
   538.157] (EE) 1: /usr/bin/Xorg (0x8048000+0x19b174) [0x81e3174]
   538.157] (EE) 2: linux-gate.so.1 (__kernel_rt_sigreturn+0x0) [0xb777240c]
   538.157] (EE) 3: /usr/lib/xorg/modules/drivers/mach64_drv.so (0xb6d2d000+0x1e645) [0xb6d4b645]
   538.157] (EE) 4: /usr/lib/xorg/modules/drivers/mach64_drv.so (0xb6d2d000+0x1e72c) [0xb6d4b72c]
   538.157] (EE) 5: /usr/lib/xorg/modules/libexa.so (0xb6358000+0xc609) [0xb6364609]
   538.157] (EE) 6: /usr/bin/Xorg (0x8048000+0x11a971) [0x8162971]
   538.157] (EE) 7: /usr/bin/Xorg (CompositeGlyphs+0xa6) [0x8150ec6]
   538.157] (EE) 8: /usr/bin/Xorg (0x8048000+0x11411c) [0x815c11c]
   538.157] (EE) 9: /usr/bin/Xorg (0x8048000+0x10fbbd) [0x8157bbd]
   538.157] (EE) 10: /usr/bin/Xorg (0x8048000+0x36ecd) [0x807eecd]
   538.157] (EE) 11: /usr/bin/Xorg (0x8048000+0x24f6a) [0x806cf6a]
   538.157] (EE) 12: /lib/libc.so.6 (__libc_start_main+0xf3) [0xb72749d3]
   538.157] (EE) 13: /usr/bin/Xorg (0x8048000+0x25339) [0x806d339]
   538.157] (EE) 
   538.157] (EE) Segmentation fault at address 0xc
   538.157] (EE) 
Fatal server error:
   538.157] (EE) Caught signal 11 (Segmentation fault). Server aborting
   538.157] (EE) 
   538.157] (EE) 
Please consult the The X.Org Foundation support 
         at http://wiki.x.org
 for help. 
   538.157] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
   538.157] (EE) 
   538.257] (EE) Server terminated with error (1). Closing log file.

lspci | grep VGA
00:09.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Rage XL PCI (rev 27)

I added nomodeset to the grub defaults per the release notes, but this does not seem related.

grep GRUB_CMDLINE_LINUX_DEFAULT /etc/default/grub
#GRUB_CMDLINE_LINUX_DEFAULT=" video=1024x768 resume=/dev/sdc2 splash=silent quiet showopts vga=0x318"
GRUB_CMDLINE_LINUX_DEFAULT=" video=1024x768 resume=/dev/sdc2 splash=silent quiet showopts nomodeset"

I really think this is a bug in the mach64 driver. I causes X to crash.
“nomodeset” doesn’t help in this case, because “mach64” doesn’t support KMS anyway.

As a first step you could try to disable Desktop effects (Alt+Shift+F12). Does it still crash then?
Or try to uninstall the mach64 driver (package “xf86-video-mach64”). Then a fallback driver should be used which hopefully doesn’t crash.

Another possibility would be to turn off Acceleration (since that’s what apparently crashes), by setting this in the Xorg configuration:

Option "noaccel"

And what graphics chip does the other system have?
The intel driver shipped with 13.1 has known bugs that can cause such crashes, but they have been fixed already.
In that case installing all updates should help.

#3

PS: You could also try to add “x11failsafe” in addition to “nomodeset” to the boot options instead of uninstalling the mach64 driver.

#4

The “other” system (an Intel SAI2 motherboard) apparently has the same VGA chip as the IBM motherboard from which info in my original post came.

From the Intel SAI2 system…

lspci | grep VGA
00:02.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Rage XL PCI (rev 27)

It, however, has not also been tried with nomodeset.

grep GRUB_CMDLINE_LINUX_DEFAULT /etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT=" video=1024x768 resume=/dev/disk/by-id/scsi-1AMCC_42208571D81EC700B05A-part2 splash=silent quiet showopts"

I will try your suggestions as quickly as I can. Things just got really busy here.

#5

Ah, ok. But you spoke about different VGA chips in your post, so I wasn’t sure.

It, however, has not also been tried with nomodeset.

To repeat, “nomodeset” alone doesn’t change anything when using the mach64 driver.
You should try to add “x11failsafe” as well.

#6

Yes, sorry about the initial “different chips” statement. Bad assumption on my part since the boards are from different manufacturers. My access to the SAI2 system is only via remote ssh login and via phone calls to remote colleagues.

I had already turned off “desktop effects” via “configure desktop -> desktop effects -> uncheck desktop effects at startup” yesterday.

I added “x11failsafe” to the boot options. This did allow both firefox and openoffice to open without crashing X. Undesired side effects of x11failsafe such as reduced-size or no task bar were also present. So that yielded a pretty good clue.

Will move on to the other suggestions next, but after a few hours.

#7

For my next test, I removed x11failsafe from the boot options, and using yast deleted “xf86-video-mach64”.

In this configuration, I was able to start firefox and openoffice without having it crash X. All of the screen graphics looked ok except for the task panel. Three problems with it.

  1. It does not stretch from screen edge to screen edge.
  2. The colors show a lot of gray and white instead of the expected colors. Sort of gray and white stripey.
  3. The menu does not seem on the scale as the mouse. That is, the mouse has to be further right than something desired to be clicked upon.

If I could fix the problem with the task bar, then this might be a good circumvention.

I tried deleting the panel and adding a new one, but the replacement had the same problems.

I saved a screen shot of what I was trying to describe above, but I don’t see a way to upload it and do not have a website from which I could provide a link.

#8

Did you use “nomodeset” or not in this case? If not, try to add it, of yes try to remove it.
Did you try to disable the desktop effects in that case? Again, you could also try to enable them. And maybe changing the settings on the “Advanced” tab would have effect too (OpenGL vs. XRender, Raster vs. Native).

Also you could try with a different driver.
There are those general ones available: modesetting, fbdev, vesa.
If you specify “nomodeset”, either “fbdev” or “vesa” will be used, “modesetting” otherwise.
IIUYC “fbdev” seems to have a problem with displaying the panel, so try to force your system to use one of the other two, either by removing “nomodeset” again (should cause the “modesetting” driver to be used), or by leaving “nomodeset” specified and uninstalling xf86-video-fbdev (vesa should be used then automatically).

I saved a screen shot of what I was trying to describe above, but I don’t see a way to upload it and do not have a website from which I could provide a link.

Upload it to http://susepaste.org or any other image hosting site and post a link.

You might want to file a bug report for the mach64 driver crash though, since apparently it’s easily reproducable.
Either at http://bugzilla.novell.com/ or (maybe better, as openSUSE doesn’t make any changes to the driver) directly upstream at http://bugs.freedesktop.org.
And don’t forget to add the X backtrace to the report.

#9

I uploaded a screenshot illustrating what I was describing to here: http://susepaste.org/37549727

The boot for Linux from which it was taken was with “nomodeset” but without “x11failsafe” with the mach64 driver rpm having been deleted. Will gather more per your suggestions.

#10

With “mach64” having been deleted…
Turning on or off display effects has no effect on the ugly gray panel.
Turning on or off “nomodeset” as a boot parameter has no effect on the ugly gray panel.
I tried all combinations of the “nomodeset” with/without display effects.

Yast does not want to let me delete the fbdev driver as it seems to be a hard requirement for Xorg.


Problem
  xorg-x11-driver-video-7.6_1-11.1.2.i586 requires xf86-video-fbdev, but this requirement cannot be provided  
Possible Solutions │  
   ] deinstallation of xorg-x11-driver-video-7.6_1-11.1.2.i586   
   ]keep xf86-video-fbdev-0.4.3-6.1.2.i586    
   ]break xorg-x11-driver-video-7.6_1-11.1.2.i586 by ignoring some of its dependencies

I elected to not delete it and break things.

#11

xorg-x11-driver-video is not really necessary either, as it only contains configuration examples. It’s mainly “a metapackage, created for compatibility” that pulls in the other driver packages.But ok, let’s try it in a different way:
Create a file /etc/X11/xorg.conf.d/50-mydevice.conf (the exact name doesn’t really matter) with the following content:

Section "Device"

  Identifier "Default Device"

  Driver "vesa"
EndSection

And boot with “nomodeset”. The vesa driver should be used then.
Maybe this one works better?

And what I would try as well, is to use the mach64 driver without acceleration. For that install “xf86-video-mach64” and change that file to:

Section "Device"

  Identifier "Default Device"

  Driver "mach64"
  Option "noaccel"
EndSection

And one last question: do you have “xf86-video-modesetting” installed?
If not, this would explain why “nomodeset” had no effect in your latest test, i.e. the fbdev driver was used.
You may want to install and try that one as well. In that case make sure you don’t have “nomodeset” specified, and set the “Driver” option to “modesetting”.

#12

Btw, I found a thread with the same Xorg crash backtrace as you:
http://antix.freeforums.org/trying-to-login-after-x-starts-but-it-logs-right-out-t4746-15.html

Unfortunately there’s not really a solution there, but at least the vesa driver seemed to work, albeit slow of course.

#13

On 2014-02-23 00:36, eheman wrote:

> Yast does not want to let me delete the fbdev driver as it seems to be a
> hard requirement for Xorg.
>
> Code:
> --------------------
>
> Problem
> xorg-x11-driver-video-7.6_1-11.1.2.i586 requires xf86-video-fbdev, but this requirement cannot be provided
> Possible Solutions │
> ] deinstallation of xorg-x11-driver-video-7.6_1-11.1.2.i586
> ]keep xf86-video-fbdev-0.4.3-6.1.2.i586
> ]break xorg-x11-driver-video-7.6_1-11.1.2.i586 by ignoring some of its dependencies
>
> --------------------

Use option 3.
It is a test, after all…

If it does not work, you can reinstall it again using yast in text mode.

–
Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))

#14

[QUOTE=wolfi323;2626617]xorg-x11-driver-video is not really necessary either, as it only contains configuration examples. It’s mainly “a metapackage, created for compatibility” that pulls in the other driver packages.But ok, let’s try it in a different way:
Create a file /etc/X11/xorg.conf.d/50-mydevice.conf (the exact name doesn’t really matter) with the following content:

Section "Device"
  Identifier "Default Device"
  Driver "vesa"
EndSection

And boot with “nomodeset”. The vesa driver should be used then.
Maybe this one works better?

And what I would try as well, is to use the mach64 driver without acceleration. For that install “xf86-video-mach64” and change that file to:

Section "Device"
  Identifier "Default Device"
  Driver "mach64"
  Option "noaccel"
EndSection

And one last question: do you have “xf86-video-modesetting” installed?
If not, this would explain why “nomodeset” had no effect in your latest test, i.e. the fbdev driver was used.
You may want to install and try that one as well. In that case make sure you don’t have “nomodeset” specified, and set the “Driver” option to “modesetting”.

#15

Tried the first suggestion of booting with nomodeset and having the 50-mydevice.conf file specifying vesa driver. That got me an “out of range” on the display when it tried to switch the monitor to the xdm login. I pasted the /var/log/Xorg.0.log file at http://susepaste.org/75051501

I’ll move on to the next suggestion of reinstalling mach64 but adding your config with noaccel

#16

Good news, I think.

After reinstalling the xf86-video-mach64 driver package that was deleted earlier, and then adding your suggested /etc/X11/xorg.conf.d/50-mydevice.conf quoted above, the problem seems to be circumvented. Clicking on the firefox or Libreoffice icons on the plasma desktop causes them to open as expected and not crash X. I have only tested this on the IBM motherboard equipped system thus far, but will get someone at the remote site to work with me to test it on the Intel motherboard with the same chip to see if it resolves it there too.

I tried it with and without the boot option “nomodeset” and with and without Desktop effects enabled. The desktop effects are pretty slow and draggy (as they have always been on this system, thus normally turned off at startup), but they did work when enabled. You asked earlier if “xf86-video-modesetting” was installed. The answer is yes it was always installed.

I really appreciate the help and suggestions provided thus far.

#17

As I said, “nomodeset” makes no difference with the mach64 driver, as it doesn’t support/use KMS anyway.

I really appreciate the help and suggestions provided thus far.

Glad it works now. :slight_smile:

I found this in the meantime, so apparently the problem is known:
http://lists.x.org/archives/xorg-devel/2013-January/035107.html
I’m not sure if that’s the exact same issue though.

Can you try if

Option "ExaNoComposite" "true"

instead of

Option "noaccel"

fixes the crashes as well?

I also found this bug report https://bugs.freedesktop.org/show_bug.cgi?id=70556, which contains a backtrace similar to yours (but not exactly the same). It states that this should be fixed with the next release of the driver.
If you want to try, I could create RPM packages with this fix.

#18

The alternative option “ExaNoComposite” “true” instead of “nocaccel” worked, too.

Because I am working in a test environment, I could try an rpm for you. Am I understanding correctly that this would be the “mach64” driver rpm, and it would be tested by omitting the special options that seem to be circumventing the problem?

#19

Good, as this doesn’t disable the acceleration completely.

Because I am working in a test environment, I could try an rpm for you. Am I understanding correctly that this would be the “mach64” driver rpm, and it would be tested by omitting the special options that seem to be circumventing the problem?

Yes, you would have to install an updated “xf86-video-mach64” rpm and remove that /etc/X11/xorg.conf.d/50-mydevice.conf file created earlier to see if that fix works for you.

I will create the package then, and report back when it’s ready.

#20

The packages are ready: http://software.opensuse.org/download.html?project=home%3Awolfi323%3Abranches%3AopenSUSE%3A13.1%3AUpdate&package=xf86-video-mach64

You can just install the 32bit package by running:

sudo rpm -U http://download.opensuse.org/repositories/home:/wolfi323:/branches:/openSUSE:/13.1:/Update/standard/i586/xf86-video-mach64-6.9.4-6.5.1.i586.rpm

Then remove /etc/X11/xorg.conf.d/50-mydevice.conf and reboot.

Does X still crash then or not?