GNOME 2.19 packages available (i686 only)

luciferin · 2007-09-16 11:56:24

roadboy wrote:

Today I see that hal stopped auto mounting drives. Anyone have the same problem?

Yes, I have the same problem. I have to open up the "Computer" directory and mouth them from there. I've had a lot of frustration trying to get auto mount to work about, but with no luck so far.

JGC · 2007-09-16 12:16:13

It seems gnome-volume-manager has died completely. I don't know what exactly is broken, since I haven't been able to extract any information from it yet.

bandan · 2007-09-16 20:56:25

Ahoy,
I've got problems playing music with Rhythmbox. I'm using oss-linux from AUR and Rhythmbox plays everything but with lot's of noise. Totem plays just fine without any noises.
When I disable oss-linux and use alsa, Rhythmbox plays also fine, even with alsas oss emulation.

bandan

MrWeatherbee · 2007-09-16 22:04:07

JGC wrote:

It seems gnome-volume-manager has died completely. I don't know what exactly is broken, since I haven't been able to extract any information from it yet.

I'm still using gnome 2.18 and my gnome-volume-manager (v2.17.0-2) is dead.

"Launching" it from the command line produces zero messages, so I am at a loss for what might be causing the issue. I know this thread is about 2.19, but just thought I'd mention that 2.18 has the same problem, at least for me.

I usually don't use any of the functionality of GVM, but I wanted to test a Python script I wrote yesterday by having it launch when an Audio CD is inserted, and I have been unable to test it on Arch. GVM does work on my Ubuntu setups, so I can test there, but the Arch GVM issue has me stumped.

I tried:

- uninstalling and re-installing gvm
- building and installing gvm from ABS

I came to this thread to see how stable 2.19 appeared to be. I thought I might make back-up images of my partitions and try an upgrade to 2.19 to see if that fixed the issue, and then luckily, I saw your post.

I may try ivman in the meantime.

wonder · 2007-09-17 20:50:11

it seems that gnome 2.20 will be release soon because new packages were uploaded to gnome ftp.

JGC · 2007-09-17 21:24:31

I don't know what's up with gnome-volume-manager, it doesn't print any error messages here, but it exits with a return status of 1, which could be anything (haven't been able to get debug messages out). I haven't tried anything beyond just starting from the commandline and using several debug flags though.

About GNOME 2.20: yes, it's scheduled for tomorrow, but I doubt we'll have it before upcoming sunday. I'm far too busy this week so I'll wait until sunday to update things here.

The packages in the 2.19 repository are quite good, there's almost no packaging bugs in there and the dependencies seem to be fine too. There's only gnome-icon-theme that needs to be added to gtkhtml as dependency and at-spi that would be a dependency for gnome-session (fix the at-spi libexecdir also!).

I'm very happy to get rid of this bloody thing called scrollkeeper, the way that package works has annoyed me as long as I'm using GNOME (which is 6 years from now I think). No more scrollkeeper-update, no more Makefile fixing, scrollkeeper-update is dead, long live rarian!

MrWeatherbee · 2007-09-17 21:59:46

JGC wrote:

I don't know what's up with gnome-volume-manager, it doesn't print any error messages here

Same here regarding the absence of error messages.

It just bails from either Sessions or command line. Running a 'pidof' on gnome-volume-manager after attempting a launch from the command line confirms that 'gvm' did not successfully start.

I have moved on to 'ivman' as I suggested I might. It seems to work easily and well, plus it has the added benefit of not being desktop dependent (as far as that goes, it doesn't even require X).

However, I still would like to get to the bottom of what's wrong with 'gvm' if for no other reason than I dislike issues with unknown causes lurking around.

Thanks for all your work on the gnome packages.

lessthanjake · 2007-09-17 23:08:56

Updatet today. On my laptop everything went smooth, except for the broken auto mounting. But om my Desktop all my menues is now empty, have not figured out how to fix that yet!

lessthanjake · 2007-09-18 09:17:21

Disabeling [testing] and rollback all packages newer than repo fixed my menu problem.

But, I miss the fast-user-switch-applet, it's not in the 2.19 repository as far as I can see.

pressh · 2007-09-18 09:54:59

lessthanjake wrote:

But, I miss the fast-user-switch-applet, it's not in the 2.19 repository as far as I can see.

There has no new version of fast-user-switch-applet been released. Just use the 2.18 version in extra, or, if needed, recompile it

Last edited by pressh (2007-09-18 09:56:52)

lessthanjake · 2007-09-18 11:46:47

Already tried that but it still didn't work. I know 2.18 is latest version, but is still seems to be part of Gnome: http://ftp.gnome.org/pub/GNOME/teams/re … 2/versions And I think it is a pretty important package on a multi user machine. (I know i can launch gdmflexiserver manually, but that isn't a nice solution and not as polished as fusa)

Last edited by lessthanjake (2007-09-18 11:47:20)

pressh · 2007-09-18 14:30:26

fusa 2.20 has just been released so you may want to try that

pressh · 2007-09-18 20:41:02

I got gvm 2.17 running under gnome 2.20 by using the following patch mentioned by someone in debian bug report 428810

--- manager.c.old    2007-09-18 22:28:09.000000000 +0200
+++ manager.c    2007-09-18 22:29:06.000000000 +0200
@@ -3296,22 +3296,8 @@
     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 ()))

Hope it is of any help

MrWeatherbee · 2007-09-18 22:47:28

pressh wrote:

I got gvm 2.17 running under gnome 2.20 by using the following patch mentioned by someone in debian bug report 428810
<---- snip patch code --->
Hope it is of any help

Thanks for the link to the bug report. It does seem to describe the problem. However, the patch code you supplied didn't work for me with Gnome 2.18. The patch (named gvm-nostart.patch) was applied correctly as far as I can tell:

[user@computer gnome-volume-manager]$ makepkg -c
==> Entering fakeroot environment
==> Making package: gnome-volume-manager 2.17.0-2 (Tue Sep 18 18:29:12 EDT 2007)
==> Checking Runtime Dependencies...
==> Checking Buildtime Dependencies...
==> Retrieving Sources...
   -> Downloading gnome-volume-manager-2.17.0.tar.bz2
--18:29:12--  http://ftp.gnome.org/pub/GNOME/sources/gnome-volume-manager/2.17/gnome-volume-manager-2.17.0.tar.bz2
           => `gnome-volume-manager-2.17.0.tar.bz2'
Resolving ftp.gnome.org... 130.239.18.137, 2001:6b0:e:2018::137
Connecting to ftp.gnome.org|130.239.18.137|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 341,241 (333K) [application/x-bzip2]

100%[====================================>] 341,241      206.34K/s             

18:29:14 (205.73 KB/s) - `gnome-volume-manager-2.17.0.tar.bz2' saved [341241/341241]

   -> Found gvm-mount-async.patch in build dir
   -> Found gvm-nostart.patch in build dir
==> Validating source files with md5sums
    gnome-volume-manager-2.17.0.tar.bz2 ... Passed
    gvm-mount-async.patch ... Passed
    gvm-nostart.patch ... Passed

This is probably getting way off topic by now (topic being gnome 2.19), but you were kind enough to provide some potentially useful info, so I felt compelled to respond. Any further discussion probably needs to be addressed in a new thread, unless otherwise advised by the OP. Thanks again.

nesl247 · 2007-09-19 00:19:42

JGC, what would you think of incoperating policykit stuff into the gnome 2.20 release? I know at least gnome-power-manager has support for it. And I know Fedora8 is going to be using policykit. I've got pkgbuilds for it already (git, could just create a snapshot, not sure if there is an actual release).

JGC · 2007-09-19 07:31:18

The policykit readme states that it's not ready to be included in a distribution, so we'll hold it off for now.

pressh · 2007-09-19 10:14:07

MrWeatherbee wrote:

Thanks for the link to the bug report. It does seem to describe the problem. However, the patch code you supplied didn't work for me with Gnome 2.18. The patch (named gvm-nostart.patch) was applied correctly as far as I can tell

Too bad I don't have gnome 2.18 installed anymore, so I can't test it on 2.18. I upgraded all packages to the current ones on the gnome ftp server so I don't even know if it works on 2.19.
As I understand correctly you were able to compile with the patch ?
If not I could upload the package somewhere.

If you was able to compile and install with the patch, does

gnome-volume-manager -no-daemon

still give no output?

[edit]
The beginning of the compile code does not indicate that the patch is indeed applied, it should be looking like

==> Starting build()...
patching file src/manager.c
Hunk #1 succeeded at 1887 (offset 250 lines).
patching file manager.c

Not sure if you know how to apply the patch correctly ? I will post part of the PKGBUILD I used (note that the patch is called initial_crash.patch):

source=(http://ftp.gnome.org/pub/GNOME/sources/${pkgname}/2.17/${pkgname}-${pkgver}.tar.bz2
    gvm-mount-async.patch
    initial_crash.patch)

build() {
  cd ${startdir}/src/${pkgname}-${pkgver}
  patch -Np0 -i ${startdir}/src/gvm-mount-async.patch || return 1
  
  cd $startdir/src/$pkgname-$pkgver/src
  patch -Np0 -i $startdir/src/initial_crash.patch || return 1
  
  cd ..
  
  ./configure --prefix=/usr --sysconfdir=/etc \
              --localstatedir=/var
  make || return 1
  make GCONF_DISABLE_MAKEFILE_SCHEMA_INSTALL=1 DESTDIR=${startdir}/pkg install

  mkdir -p ${startdir}/pkg/usr/share/gconf/schemas
  gconf-merge-schema ${startdir}/pkg/usr/share/gconf/schemas/${pkgname}.schemas ${startdir}/pkg/etc/gconf/schemas/*.schemas
  rm -f ${startdir}/pkg/etc/gconf/schemas/*.schemas
}

Last edited by pressh (2007-09-19 10:19:58)

MrWeatherbee · 2007-09-19 15:09:51

@ pressh

MrWeatherbee wrote:

This is probably getting way off topic by now (topic being gnome 2.19), but you were kind enough to provide some potentially useful info, so I felt compelled to respond. Any further discussion probably needs to be addressed in a new thread, unless otherwise advised by the OP. Thanks again.

I started a new topic about the gvm issue over here:

http://bbs.archlinux.org/viewtopic.php? … 28#p282528

afonic · 2007-09-20 00:21:35

As I am new to Arch and not I have not really witnessed the way it works just yet, since 2.20 is out how would it approximately take until it is available in the repos? (and I mean extra not testing)

pressh · 2007-09-20 05:33:24

afonic wrote:

As I am new to Arch and not I have not really witnessed the way it works just yet, since 2.20 is out how would it approximately take until it is available in the repos? (and I mean extra not testing)

JGC wrote:

About GNOME 2.20: yes, it's scheduled for tomorrow, but I doubt we'll have it before upcoming sunday. I'm far too busy this week so I'll wait until sunday to update things here.

As for testing or extra I'm not sure. It may or may not go directly go into extra, depending on if all bugs are solved before that, i.e. I assume the gvm needs a real solution instead of the temporary workaround I posted above. But really, that is for JGC to decide. Anyway, arch devs are one of the fastest 'available' so you will probably not have to wait very long

Last edited by pressh (2007-09-20 05:34:03)

JGC · 2007-09-20 06:22:42

Gnome-volume-manager should be able to work by fixing the local user check in it, there's multiple reports about it being broken. As for testing or extra: testing. There's sobumps for some common libraries used by other projects and looking at the 2.20.0.1 and 2.20.1 releases I don't think this thing is ready for extra yet. These releases give me the idea that everything is rushed just to get it "in time" (they're late) for GNOME 2.20.

Obi-Lan · 2007-09-21 11:00:56

I have troubles with 2.19 and appearance stuff. I can't change my wallpaper since wallpaper select window wont open. I also tried to change wallpaper trough gnome-appearance-properties, but it crashes when I select wallpaper. I get some errors to cli:

gnome-appearance-properties: symbol lookup error: gnome-appearance-properties: undefined symbol: gdk_color_to_string

After that gnome-appearance-properties process takes 100% CPU until I kill it.

JGC · 2007-09-21 11:16:24

Be sure to install gtk from the gnome 2.19 repository, Older versions than 2.11.6 won't work. You're running 2.10 on your system.

Obi-Lan · 2007-09-21 11:54:40

Oh. I see. Most of my troubles went away with correct version of gtk2. Thanks.

But after I've used gnome-appearance-properties and closed it it still stays in processes eating all CPU time? This time with no errors.

nesl247 · 2007-09-23 06:59:35

JGC, can we get totem built with lirc support? Oh, and why does the main totem package get built with mozilla support, and then the files get removed? I just found it a bit odd.

Last edited by nesl247 (2007-09-23 07:00:00)

Arch Linux

#76 2007-09-16 11:56:24

Re: GNOME 2.19 packages available (i686 only)

#77 2007-09-16 12:16:13

Re: GNOME 2.19 packages available (i686 only)

#78 2007-09-16 20:56:25

Re: GNOME 2.19 packages available (i686 only)

#79 2007-09-16 22:04:07

Re: GNOME 2.19 packages available (i686 only)

#80 2007-09-17 20:50:11

Re: GNOME 2.19 packages available (i686 only)

#81 2007-09-17 21:24:31

Re: GNOME 2.19 packages available (i686 only)

#82 2007-09-17 21:59:46

Re: GNOME 2.19 packages available (i686 only)

#83 2007-09-17 23:08:56

Re: GNOME 2.19 packages available (i686 only)

#84 2007-09-18 09:17:21

Re: GNOME 2.19 packages available (i686 only)

#85 2007-09-18 09:54:59

Re: GNOME 2.19 packages available (i686 only)

#86 2007-09-18 11:46:47

Re: GNOME 2.19 packages available (i686 only)

#87 2007-09-18 14:30:26

Re: GNOME 2.19 packages available (i686 only)

#88 2007-09-18 20:41:02

Re: GNOME 2.19 packages available (i686 only)

#89 2007-09-18 22:47:28

Re: GNOME 2.19 packages available (i686 only)

#90 2007-09-19 00:19:42

Re: GNOME 2.19 packages available (i686 only)

#91 2007-09-19 07:31:18

Re: GNOME 2.19 packages available (i686 only)

#92 2007-09-19 10:14:07

Re: GNOME 2.19 packages available (i686 only)

#93 2007-09-19 15:09:51

Re: GNOME 2.19 packages available (i686 only)

#94 2007-09-20 00:21:35

Re: GNOME 2.19 packages available (i686 only)

#95 2007-09-20 05:33:24

Re: GNOME 2.19 packages available (i686 only)

#96 2007-09-20 06:22:42

Re: GNOME 2.19 packages available (i686 only)

#97 2007-09-21 11:00:56

Re: GNOME 2.19 packages available (i686 only)

#98 2007-09-21 11:16:24

Re: GNOME 2.19 packages available (i686 only)

#99 2007-09-21 11:54:40

Re: GNOME 2.19 packages available (i686 only)

#100 2007-09-23 06:59:35

Re: GNOME 2.19 packages available (i686 only)

Board footer