Bug 134293
Summary: | _gnome_vfs_drive_from_corba segfaults | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Bill Nottingham <notting> |
Component: | gnome-vfs2 | Assignee: | Alexander Larsson <alexl> |
Status: | CLOSED RAWHIDE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | rvokal |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-10-01 14:34:21 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 131589 |
Description
Bill Nottingham
2004-10-01 00:43:56 UTC
Actually, this pretty much happens on any invocation of the file chooser. ('open' in the menu, for instance.) That doesn't happen for me. Both opening pdfs and printing to postscript work fine with gpdf-2.8.0-1 and gtk2-2.4.10-5 This is likely to be due to changes in the internal gnome-vfs corba interface. The lib and daemon changed, but an old daemon is still running. over to gnome-vfs2 then, it was seen in Evolution yesterday too by Walters. I'm not sure what can be done about it. Killall gnome-vfs-daemon or log out/in will fix it. I'll just close it RAWHIDE... Do we want to do the killall on upgrade in %post? Possibly. Although that could cause minor irritation in most cases where the interface didn't change. Gnome-vfs does handle the daemon dying properly, and restarts it. However some things, like authenticated connections, gets lost when the daemon dies. Hmm, actually killall might not help. You need to restart the apps that use the library too. :( Well... if this interface will never change in a stable gnome series (2.8.x, etc.), then I suppose it's not really an issue. If it's going to change at every new 2.8.x, then it's more of a problem. Nah. It'll be stable. |