[Bug 473737] New: BadRequest when starting F-Spot
https://bugzilla.novell.com/show_bug.cgi?id=473737 Summary: BadRequest when starting F-Spot Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome@forge.provo.novell.com ReportedBy: riggwelter@opensuse.org QAContact: qa@suse.de Found By: --- When starting F-Spot, it starts to draw its window and then crashes. The output from running with --debug is below - there is no --sync command line option to F-Spot of course. # f-spot --debug ** Running f-spot in Debug Mode ** ** Running Mono with --debug ** [Info 20:24:01.948] Initializing DBus [Debug 20:24:02.123] DBusInitialization took 0.15897s [Info 20:24:02.123] Initializing Mono.Addins [Debug 20:24:02.418] Mono.Addins Initialization took 0.295089s [Info 20:24:02.428] Starting new FSpot server [Debug 20:24:02.654] Db Initialization took 0.142909s [Debug 20:24:03.234] QueryToTemp took 0.014316s : SELECT id, time, uri, description, roll_id, default_version_id, rating, md5_sum FROM photos WHERE id NOT IN (SELECT photo_id FROM photo_tags WHERE tag_id = 2) ORDER BY time DESC [Debug 20:24:03.466] Query took 0.022225s : SELECT * FROM photoquery_temp_0 LIMIT 100 OFFSET 0 [Debug 20:24:03.482] PhotosPerMonth took 0.011848s [Debug 20:24:03.485] TimeAdaptor REAL Reload took 0.224384s The program 'f-spot' received an X Window System error. This probably reflects a bug in the program. The error was 'BadRequest (invalid request code or no such operation)'. (Details: serial 330 error_code 1 request_code 143 minor_code 19) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) -- 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=473737 User riggwelter@opensuse.org added comment https://bugzilla.novell.com/show_bug.cgi?id=473737#c1 James Ogley <riggwelter@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|GNOME |X.Org AssignedTo|bnc-team-gnome@forge.provo. |bnc-team-xorg-bugs@forge.pr |novell.com |ovo.novell.com QAContact|qa@suse.de |xorg-maintainer-bugs@forge. | |provo.novell.com --- Comment #1 from James Ogley <riggwelter@opensuse.org> 2009-02-10 05:51:30 MST --- For reference, https://bugs.launchpad.net/ubuntu/+source/f-spot/+bug/297406 suggests it's a problem with radeonhd but I see it with both radeonhd and flgrx. Interestingly, also get a BadRequest when trying to run glxgears so I think this may be an X issue - changing component to X.Org. # fgl_glxgears Using GLX_SGIX_pbuffer X Error of failed request: BadRequest (invalid request code or no such operation) Major opcode of failed request: 143 (GLX) Minor opcode of failed request: 19 (X_GLXQueryServerString) Serial number of failed request: 15 Current serial number in output stream: 15 # glxgears X Error of failed request: BadRequest (invalid request code or no such operation) Major opcode of failed request: 143 (GLX) Minor opcode of failed request: 19 (X_GLXQueryServerString) Serial number of failed request: 15 Current serial number in output stream: 15 -- 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=473737 User sndirsch@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=473737#c2 Stefan Dirsch <sndirsch@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |sndirsch@novell.com Resolution| |INVALID --- Comment #2 from Stefan Dirsch <sndirsch@novell.com> 2009-02-10 06:08:34 MST --- Most likely you have a messed up system, i.e. fglrx driver installed, but using radeonhd. Make sure you uninstall fglrx driver, then reboot system to get rid of fglrx kernel module. -- 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=473737 User sndirsch@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=473737#c3 --- Comment #3 from Stefan Dirsch <sndirsch@novell.com> 2009-02-10 06:12:09 MST --- Or the other way round. You try to run ATI's fgl_glxgears with using radeonhd driver. -- 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=473737 User riggwelter@opensuse.org added comment https://bugzilla.novell.com/show_bug.cgi?id=473737#c4 --- Comment #4 from James Ogley <riggwelter@opensuse.org> 2009-02-10 07:09:10 MST --- Comment #2 was partly right - removing the fglrx drivers altogether and using radeonhd has fixed it. The problem existed when using fglrx as well though. Also, the default configuration at the end of install was that described in comment #2 - fglrx diver installed but X configured to use radeonhd, this is a potential problem. Leaving closed unless Stefan thinks there's something to investigate. -- 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=473737 User sndirsch@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=473737#c5 --- Comment #5 from Stefan Dirsch <sndirsch@novell.com> 2009-02-10 07:53:09 MST ---
Also, the default configuration at the end of install was that described in comment #2 - fglrx diver installed but X configured to use radeonhd, this is a potential problem. Leaving closed unless Stefan thinks there's something to investigate.
Looks like you don't use our RPMs, but ATI's installer. Otherwise SaX2 would have chosen fglrx driver by default. -- 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=473737 User riggwelter@opensuse.org added comment https://bugzilla.novell.com/show_bug.cgi?id=473737#c6 --- Comment #6 from James Ogley <riggwelter@opensuse.org> 2009-02-10 08:13:23 MST --- Nope, using the RPMs as installed by the first online update after install. -- 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=473737 User sndirsch@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=473737#c7 --- Comment #7 from Stefan Dirsch <sndirsch@novell.com> 2009-02-10 09:06:08 MST --- Have the RPMs been autoselected by YaST2? Otherwise the driver does not support the graphics chip at all. The output of 'hwinfo --gfxcard' would help here. -- 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=473737 User riggwelter@opensuse.org added comment https://bugzilla.novell.com/show_bug.cgi?id=473737#c8 --- Comment #8 from James Ogley <riggwelter@opensuse.org> 2009-02-10 11:59:17 MST --- They were autoselected by YaST. # hwinfo --gfxcard 25: PCI 105.0: 0300 VGA compatible controller (VGA) [Created at pci.318] UDI: /org/freedesktop/Hal/devices/pci_1002_7942 Unique ID: ul7N.ns4ZFNHGmS9 Parent ID: vSkL.nzdltcNgfQ3 SysFS ID: /devices/pci0000:00/0000:00:01.0/0000:01:05.0 SysFS BusID: 0000:01:05.0 Hardware Class: graphics card Model: "ATI Radeon Xpress 1200 (M)" Vendor: pci 0x1002 "ATI Technologies Inc" Device: pci 0x7942 "Radeon Xpress 1200 (M)" SubVendor: pci 0x144d "Samsung Electronics Co Ltd" SubDevice: pci 0xc034 Memory Range: 0xc0000000-0xcfffffff (rw,prefetchable) Memory Range: 0xd0000000-0xd000ffff (rw,non-prefetchable) I/O Ports: 0x9000-0x9fff (rw) IRQ: 255 (no events) I/O Ports: 0x3c0-0x3df (rw) Module Alias: "pci:v00001002d00007942sv0000144Dsd0000C034bc03sc00i00" Driver Info #0: XFree86 v4 Server Module: radeonhd Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #9 (PCI bridge) Primary display adapter: #25 -- 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=473737 User sndirsch@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=473737#c9 --- Comment #9 from Stefan Dirsch <sndirsch@novell.com> 2009-02-10 13:17:18 MST --- Yes, this device id is supported by Catalyst 9.1 driver. -- 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