Gnome 2.16 and dbus 0.93 to Testing

noriko · 2006-10-01 22:26:26

this isn't directed at anyone specific.. just those who experience errors relating to the dbus obj... all that's needed is to link to the new version in /usr/lib

ln -s /usr/lib/libdbus-1.so.3.0.0 /usr/lib/libdbus-1.so.2

Gullible Jones · 2006-10-01 22:31:45

JGC wrote:

Your .xinitrc won't work. What about something like this:
eval `dbus-launch`
your program &
your other program &
exec openbox
<snip>

Nope, that doesn't work. It causes gnome-settings-daemon to crash on start, and I mean really crash... As in the Gnome debugger starts up and complains about it. Here's what the debugger has to say:

Memory status: size: 19968000 vsize: 0 resident: 19968000 share: 0 rss: 6594560 rss_rlim: 0
CPU usage: start_time: 1159741406 rtime: 0 utime: 12 stime: 0 cutime:12 cstime: 0 timeout: 0 it_real_value: 0 frequency: 1

Backtrace was generated from '/opt/gnome/libexec/gnome-settings-daemon'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1226660176 (LWP 2588)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xb7f1b410 in ?? ()
#0  0xb7f1b410 in ?? ()
#1  0xbfd9b7c8 in ?? ()
#2  0x00000000 in ?? ()

Thread 1 (Thread -1226660176 (LWP 2588)):
#0  0xb7f1b410 in ?? ()
No symbol table info available.
#1  0xbfd9b7c8 in ?? ()
No symbol table info available.
#2  0x00000000 in ?? ()
No symbol table info available.
#0  0xb7f1b410 in ?? ()

m123 · 2006-10-02 00:38:17

1/ As of now, the gnomebaker launch issue is solved.

2/ I also mentionned a floppy issue. I know, floppies are not top notch but I still use them... The issue is that it takes long for them to mount and
they are mounted as "usbsticks" (that's what appears in the nautilus sidebar and this is the directory created under /media). As a consequence, Nautilus points to another directory because it lost "floppy". However, if one clicks on "usbstick", the content is accessible and correctly displayed. Same thing if you try to open a file on a floppy within an application (gedit for example). I guess it's another hal issue. Any clue?

Also, another quick comment: There should be somewhere a dependency on "eject" (as in kdebase), otherwise CD's and DVD's will not eject.

iphitus · 2006-10-02 07:47:21

noriko wrote:

this isn't directed at anyone specific.. just those who experience errors relating to the dbus obj... all that's needed is to link to the new version in /usr/lib
ln -s /usr/lib/libdbus-1.so.3.0.0 /usr/lib/libdbus-1.so.2

Just letting everyone know, ignore this suggestion. it is not a solution. If you do experience such an error, file a bug so that the developers can promptly recompile the package for the new dbus.

James

aquila_deus · 2006-10-02 10:41:45

iphitus wrote:

noriko wrote:
this isn't directed at anyone specific.. just those who experience errors relating to the dbus obj... all that's needed is to link to the new version in /usr/lib
ln -s /usr/lib/libdbus-1.so.3.0.0 /usr/lib/libdbus-1.so.2
Just letting everyone know, ignore this suggestion. it is not a solution. If you do experience such an error, file a bug so that the developers can promptly recompile the package for the new dbus.
James

It works well for epiphany 2.16 and terminal

cromo · 2006-10-02 12:00:46

While compiling knetworkmanager:

checking for dbus/connection.h... no
configure: WARNING: You need D-Bus/Qt3 bindings

Again, no Qt3 bindings. I guess it is a good idea to ship stripped qt3 bindings than patch every single piece of sofrware that needs it - as I suggested in prev post.

nightfrost · 2006-10-02 12:06:08

iphitus wrote:

noriko wrote:
this isn't directed at anyone specific.. just those who experience errors relating to the dbus obj... all that's needed is to link to the new version in /usr/lib
ln -s /usr/lib/libdbus-1.so.3.0.0 /usr/lib/libdbus-1.so.2
Just letting everyone know, ignore this suggestion. it is not a solution. If you do experience such an error, file a bug so that the developers can promptly recompile the package for the new dbus.
James

The best thing to do in the meantime is just to recompile the package for yourself from the ABS tree. After all, it's not harder than installing with pacman.

makepkg -cis

Cub69 · 2006-10-02 15:18:53

I did this upgrade this morning and now X won't start at all.

Oddly, GDM starts but when I try and log in, X crashes. I looked at the X.0.log and it looks to be a problem with the i810 driver. I'm running on a Dell d620 with a I945 video.

Any suggestions on how to get a better idea where the problem is with this? Has anyone else seen this?

Thanks
Norm
RESOLVED -- permissions issue!?! with my .gconf .gconfd files in my home directory. Very odd...

Phrodo_00 · 2006-10-02 21:37:07

Michel F wrote:

2/ Even though totem and gstreamer plugins have been updated, I'm still unable to read a dvd with totem (gstreamer). Totem xine is ok.

the same happens to me with gstreamer and totem from current :S

Gullible Jones · 2006-10-03 00:39:29

Gullible Jones wrote:

JGC wrote:
Your .xinitrc won't work. What about something like this:
eval `dbus-launch`
your program &
your other program &
exec openbox
<snip>
Nope, that doesn't work. It causes gnome-settings-daemon to crash on start, and I mean really crash... As in the Gnome debugger starts up and complains about it. Here's what the debugger has to say:
<snip>

Hmm, using eval `dbus-launch` or eval `dbus-launch --exit-with-session` definitely creates a dbus session, but the settings daemon can't seem to connect to it, nor can anything else. Still the same with the new version of control-center, etc. Does anyone know what's going wrong?

filoktetes · 2006-10-03 14:39:29

NME wrote:

I was wondering if the composite-support for metacity is compiled in and then how to enable it?

It seems the composite support isn't compiled in.
I'll try to compile metacity with composite support now, and see what happens.

m123 · 2006-10-03 16:30:14

There seems to be another issue with alacarte menu editor. Unable to add or disable anything with it. Is it confirmed?

hjorthboggild · 2006-10-03 17:09:22

How do I obtain the pkgbuild used to build Metacity in testing? When looking here http://www.archlinux.org/packages/11667/ , and pressing the "View CVS Entries" all I get is the following message: Repository cvsroot Testing not configured in viewcvs.conf

Regards,
Simon

JGC · 2006-10-03 17:19:14

Gullible Jones wrote:

Gullible Jones wrote:
JGC wrote:
Your .xinitrc won't work. What about something like this:
eval `dbus-launch`
your program &
your other program &
exec openbox
<snip>
Nope, that doesn't work. It causes gnome-settings-daemon to crash on start, and I mean really crash... As in the Gnome debugger starts up and complains about it. Here's what the debugger has to say:
<snip>
Hmm, using eval `dbus-launch` or eval `dbus-launch --exit-with-session` definitely creates a dbus session, but the settings daemon can't seem to connect to it, nor can anything else. Still the same with the new version of control-center, etc. Does anyone know what's going wrong?

Try using dbus-launch --auto-syntax or one of the specific syntax options. Could be that dbus doesn't generate the correct syntax and your message bus isn't exported.

detto · 2006-10-03 17:51:36

The issue is that it takes long for them to mount and
they are mounted as "usbsticks" (that's what appears in the nautilus sidebar and this is the directory created under /media). As a consequence, Nautilus points to another directory because it lost "floppy". However, if one clicks on "usbstick", the content is accessible and correctly displayed. Same thing if you try to open a file on a floppy within an application (gedit for example). I guess it's another hal issue. Any clue?

Exact same error for me on (S)VideoCD's. But it also doesnt display in sidebar. I can't see in "Places" menu the entry for it neither in sidebar of nautilus. Doubleclicking the drive in "Computer" doesnt work, only way to get to the fiels on the cd is to go to /media/usbstick which is a pretty weird name for a (S)VideoCD
Hope this gets fixed 8)

hussam · 2006-10-03 19:09:43

Can somebody please instruct me on what exactly do I need to install and configure to get suspend to disk working with gnome-power-manager 2.16.1 ?

Blaasvis · 2006-10-03 20:03:05

pacman -S powersave
add yourself to the power group
/etc/rc.d/powersaved restart
and add suspend=/dev/<your> to you kernel boot parameters.

then it should work

hussam · 2006-10-03 20:21:20

Blaasvis wrote:

pacman -S powersave
add yourself to the power group
/etc/rc.d/powersaved restart
and add suspend=/dev/<your> to you kernel boot parameters.
then it should work

ok, I did that and added suspend=/dev/hda2 to boot parameters ( hda2 is my swap ). Now when I click hibernate in gnome-power-manager , all it does is lock the screen. Any log file I can look at?

robertK · 2006-10-03 20:29:45

hussam wrote:

Blaasvis wrote:
pacman -S powersave
add yourself to the power group
/etc/rc.d/powersaved restart
and add suspend=/dev/<your> to you kernel boot parameters.
then it should work
ok, I did that and added suspend=/dev/hda2 to boot parameters ( hda2 is my swap ). Now when I click hibernate in gnome-power-manager , all it does is lock the screen. Any log file I can look at?

And what about suspend? Does it work?

It can be problem connected with your hardware.

powersave didn't work on my HP nx6125 for about four months and it started to work few weeks or days ago, when I installed new gnome and new kernel. After the last update today it fails does not work again :-(

Try powersave -u and then dmesg to locate the problem.

hussam · 2006-10-03 20:36:43

I get suspend to ram not supported.
Still suspend to disk should continue to work
I also did powersave -U but there is not related error output in dmesg.

Blaasvis · 2006-10-03 20:38:57

/var/log/suspend2disk

hussam · 2006-10-03 20:45:02

/proc/cmdline: root=/dev/hda1 ro vga=795 quiet noapic suspend=/dev/hda2
------------------------------------------------------------------------------
========we are going to sleep, preparing.========
Arch linux found
Found ARCH kernel
running kernel is grub menu entry 0 (vmlinuz26)
resume partition is not set up.

hjorthboggild · 2006-10-03 20:48:58

Blaasvis wrote:

pacman -S powersave
add yourself to the power group
/etc/rc.d/powersaved restart
and add suspend=/dev/<your> to you kernel boot parameters.
then it should work

Why is powersave not mentioned as one of the dependencies for gnome-power-manager if it's required?

Regards,
Simon

filoktetes · 2006-10-03 23:54:00

hjorthboggild wrote:

How do I obtain the pkgbuild used to build Metacity in testing? When looking here http://www.archlinux.org/packages/11667/ , and pressing the "View CVS Entries" all I get is the following message: Repository cvsroot Testing not configured in viewcvs.conf
Regards,
Simon

Look here

http://bbs.archlinux.org/viewtopic.php?t=7154

I just tried to build metacity with compositer enabled, but what I get, is a blank blue screen with blank blue windows. The effects work, but there's no content. I've tried to change xorg.conf, but nothing worked. If someone knows what causes this, I'd like to know. I use i915GM

Gullible Jones · 2006-10-04 00:22:19

JGC wrote:

Try using dbus-launch --auto-syntax or one of the specific syntax options. Could be that dbus doesn't generate the correct syntax and your message bus isn't exported.

Thanks, that works... Yep, --foo-syntax seems to be necessary, kind of stupid of me to forget about that.

Arch Linux

#76 2006-10-01 22:26:26

Re: Gnome 2.16 and dbus 0.93 to Testing

#77 2006-10-01 22:31:45

Re: Gnome 2.16 and dbus 0.93 to Testing

#78 2006-10-02 00:38:17

Re: Gnome 2.16 and dbus 0.93 to Testing

#79 2006-10-02 07:47:21

Re: Gnome 2.16 and dbus 0.93 to Testing

#80 2006-10-02 10:41:45

Re: Gnome 2.16 and dbus 0.93 to Testing

#81 2006-10-02 12:00:46

Re: Gnome 2.16 and dbus 0.93 to Testing

#82 2006-10-02 12:06:08

Re: Gnome 2.16 and dbus 0.93 to Testing

#83 2006-10-02 15:18:53

Re: Gnome 2.16 and dbus 0.93 to Testing

#84 2006-10-02 21:37:07

Re: Gnome 2.16 and dbus 0.93 to Testing

#85 2006-10-03 00:39:29

Re: Gnome 2.16 and dbus 0.93 to Testing

#86 2006-10-03 14:39:29

Re: Gnome 2.16 and dbus 0.93 to Testing

#87 2006-10-03 16:30:14

Re: Gnome 2.16 and dbus 0.93 to Testing

#88 2006-10-03 17:09:22

Re: Gnome 2.16 and dbus 0.93 to Testing

#89 2006-10-03 17:19:14

Re: Gnome 2.16 and dbus 0.93 to Testing

#90 2006-10-03 17:51:36

Re: Gnome 2.16 and dbus 0.93 to Testing

#91 2006-10-03 19:09:43

Re: Gnome 2.16 and dbus 0.93 to Testing

#92 2006-10-03 20:03:05

Re: Gnome 2.16 and dbus 0.93 to Testing

#93 2006-10-03 20:21:20

Re: Gnome 2.16 and dbus 0.93 to Testing

#94 2006-10-03 20:29:45

Re: Gnome 2.16 and dbus 0.93 to Testing

#95 2006-10-03 20:36:43

Re: Gnome 2.16 and dbus 0.93 to Testing

#96 2006-10-03 20:38:57

Re: Gnome 2.16 and dbus 0.93 to Testing

#97 2006-10-03 20:45:02

Re: Gnome 2.16 and dbus 0.93 to Testing

#98 2006-10-03 20:48:58

Re: Gnome 2.16 and dbus 0.93 to Testing

#99 2006-10-03 23:54:00

Re: Gnome 2.16 and dbus 0.93 to Testing

#100 2006-10-04 00:22:19

Re: Gnome 2.16 and dbus 0.93 to Testing

Board footer