Gnome-Volume-Manager Fails To Start

MrWeatherbee · 2007-09-19 15:07:34

Problem: Gnome Volume Manager Fails To Start (or exits / terminates prematurely)
Gnome Version: 2.18
Gnome Volume Manager Version: 2.17.0-2

Background
This thread attempts to consolidate the Gnome-Volume-Manager issue which arose in the midst of JGC's topic on Gnome 2.19:

http://bbs.archlinux.org/viewtopic.php?id=36783&p=1

The relevant posts there are:

Page 4 / Post 77 - http://bbs.archlinux.org/viewtopic.php? … 07#p281707
Page 4 / Post 79 - http://bbs.archlinux.org/viewtopic.php? … 49#p281849
Page 4 / Post 81 - http://bbs.archlinux.org/viewtopic.php? … 07#p282107
Page 4 / Post 82 - http://bbs.archlinux.org/viewtopic.php? … 13#p282113
Page 4 / Post 88 - http://bbs.archlinux.org/viewtopic.php? … 81#p282381
Page 4 / Post 89 - http://bbs.archlinux.org/viewtopic.php? … 98#p282398
Page 4 / Post 92 - http://bbs.archlinux.org/viewtopic.php? … 79#p282479

Summary:

A few days ago I attempted to use gnome-volume-manager (gvm) to test a python script that needed to be run when an Audio Disc was inserted into a CDROM drive.

However, I quickly noticed that gvm was not functioning when I made 'rules' for it via its GUI frontend, gnome-volume-properties. I tested in Ubuntu and things worked fine, but in Arch gvm would not work.

As it turned out, attempting to launch gvm in Arch from Sessions and the command line both failed to leave gvm running, and the command line gives no output or indication that gvm has failed to start or was otherwise prematurely terminated / exited. In my search for answers, I checked the ongoing thread about Gnome 2.19 (see links above) to see if 2.19 might be a solution.

However, by chance, the author of that thread, JGC, noted in post #77 that gvm had "died completely" in 2.19 as well (see links above).

The most important follow-up in the gvm-related discussion from JGC's thread was posted by Pressh in which he provided a link to a bug report:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=428810

which fairly accurately describes the same behavior as I had experienced. Pressh continued on by providing a patch for gvm that he says works for him in Gnome 2.20 / GVM 2.17.0-2. The patch was provided in Post #88 of JGCs 2.19 topic (see links above).

However, that patch was successfully applied by me in Gnome 2.18 / GVM 2.17.02, and it did not work (see note below).

Additionally, I am not sure I would want to leave the patch applied even if it had worked and would consider it only a testing patch. Perhaps others may have more confidence in it, but it appears to mostly remove several lines of code from the gvm source without adequate knowledge of what those lines of code were originally intended for.

As for now, I am happily using ivman as a substitute for the functionality of gvm, and it works quite well. It has certain advantages over gvm, and I suspect I will continue using it even if / when the gvm issue is resolved. However, I still think this topic serves a purpose regardless of my ultimate intentions to use gvm or not, even if that purpose is to prevent JGCs topic from being too severely hijacked.

---
Note:
In post #92 of JGCs thread (see links above), Pressh was concerned that perhaps I had failed to properly apply the patch he provided and that could be the cause for it not working. His assertion was based on 'makepkg' output I posted as an indication that it had been applied properly. He correctly pointed out that the output I posted was not necessarily proof that the patch was successfully applied. My mistake in posting that output was only that I failed to include the next several lines, but they were indeed part of the output:

==> Extracting Sources...
   -> tar -xf gnome-volume-manager-2.17.0.tar.bz2
==> Starting build()...
patching file src/manager.c
Hunk #1 succeeded at 1887 (offset 250 lines)

pressh · 2007-09-19 16:53:31

MrWeatherbee I'm still not confident that you applied the patches correctly, as the makepkg output you posted above is from the gvm-mount-async.patch, which is already included in the repo version. You may send me your PKGBUILD (private message/e-mail if you want)

As for the patch I think it is indeed not a clean solution, though it is a working workaround (at least for me) atm. I didn't found any negative side effects so far.

gvm I compiled against gnome 2.20. As I said it may or may not workagainst gnome 2.18 or 2.19

[edit] man that was a long story you wrote

Last edited by pressh (2007-09-19 16:55:46)

MrWeatherbee · 2007-09-19 20:38:30

pressh wrote:

MrWeatherbee I'm still not confident that you applied the patches correctly

Why not, I'm an expert.

Well ... maybe not. I had a "minor" glitch in my PKGBUILD file, so the patch was indeed getting skipped.

Anyway, I corrected the PKGBUILD, but then I was getting errors saying:

patch unexpectedly ends in middle of line

so I made my own patch using 'diff -C5':

*** manager.c_orig    2006-11-07 13:01:17.000000000 -0500
--- manager.c    2007-09-19 15:53:41.000000000 -0400
***************
*** 3291,3319 ****
      }
      
      if (no_daemon)
          daemonize = FALSE;
      
-     if (secret_mode)
-         fprintf (stdout, "Managing volumes since the summer of '89\n");
-     
-     if (daemonize && daemon (0, 0) < 0) {
-         warn ("daemonizing failed: %s", g_strerror (errno));
-         return 1;
-     }
-     
-     client = gnome_master_client ();
-     if (gvm_get_clipboard () && gvm_local_user ()) {
-         gnome_client_set_restart_style (client, GNOME_RESTART_ANYWAY);
-     } else {
-         gnome_client_set_restart_style (client, GNOME_RESTART_NEVER);
-         if (gvm_local_user ())
-             warn ("already running");
-         
-         return 1;
-     }
-     
      g_signal_connect (client, "die", G_CALLBACK (gvm_die), NULL);
      
      if (!(hal_ctx = gvm_hal_init ()))
          return 1;
      
--- 3291,3300 ----

and that worked. Since it is essentially the same patch in code-change content, I guess there might be some issues with whitespace or other characters when creating patches by copying and pasting from the forum?

Anyway, with the corrected PKGBUILD and my patch, GVM starts with a couple of errors, but it does work, i.e., rules created in Gnome Volume Properties are recognized and run.

So, thank you for your patch and your lack of confidence ... it set me on the correct path.

This all will hopefully be moot soon when an official fix is released.

I do appreciate everything, though.

pressh wrote:

[edit] man that was a long story you wrote

Dontcha know it takes some effort to move a discussion from one thread to another (that's just an excuse of course; I'm long-winded most of the time anyway.).

PS

I did not try your uploaded package file. I trust you, but not that much.

abhidg · 2007-10-07 09:06:39

Thanks, pressh! Your package installed fine here on Gnome 2.18 and gvm is working. Could you post the PKGBUILD?

Arch Linux

#1 2007-09-19 15:07:34

Gnome-Volume-Manager Fails To Start

#2 2007-09-19 16:53:31

Re: Gnome-Volume-Manager Fails To Start

#3 2007-09-19 20:38:30

Re: Gnome-Volume-Manager Fails To Start

#4 2007-10-07 09:06:39

Re: Gnome-Volume-Manager Fails To Start

Board footer