Bug 512461 - type array 97 not a basic type
Summary: type array 97 not a basic type
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: gvfs
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-07-17 19:20 UTC by Christopher Aillon
Modified: 2015-03-03 22:40 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-09-26 17:55:20 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Christopher Aillon 2009-07-17 19:20:46 UTC
% gedit
process 6686: type array 97 not a basic type
  D-Bus not built with -rdynamic so unable to print a backtrace
zsh: exit 1     gedit

% rpm -qa dbus* gedit
gedit-2.27.2-1.fc12.x86_64
dbus-devel-1.2.14-2.fc12.x86_64
dbus-1.2.14-2.fc12.x86_64
dbus-glib-0.80-3.fc12.x86_64
dbus-x11-1.2.14-2.fc12.x86_64
dbus-glib-devel-0.80-3.fc12.x86_64
dbus-libs-1.2.14-2.fc12.x86_64
dbus-python-0.83.0-5.fc11.x86_64

Comment 1 Matthew Barnes 2009-07-29 22:10:48 UTC
I think the problem is in gvfs.  Building against git master causes just about everything to abort with this error.  Uninstalling it and falling back to F-11 gvfs fixes the problem.  Reassigning.

Comment 2 Michel Lind 2009-08-10 06:19:36 UTC
Experienced this after upgrading a box from F-11 to Rawhide (gvfs 1.3.3-2); killing active gvfs* processes fix the issue. This bug could probably be closed?

Comment 3 Alexander Larsson 2009-09-26 17:55:20 UTC
Yeah, this is due to protocol changes in gvfs unstable releases. Easiest way to fix is to log out + in, harder version is to kill all gvfs-* processes and restart all apps that use gvfs.

Comment 4 Yann Vernier 2009-09-29 13:20:45 UTC
"Not a bug" is hardly an appropriate response to something that crashes every GUI program when you try to save your work, with a totally unhelpful error message the user most likely won't even see. 
gvfs should have had a version check and sane fallback behaviour.


Note You need to log in before you can comment on or make changes to this bug.