Gnome 3.14 problems with wayland

Hi everybody,
Today I updated to repo testing to try the Gnome Wayland session. But I can't get it launched.
I followed what's advised on the wiki there:
https://wiki.archlinux.org/index.php/Wa … _libraries
https://wiki.archlinux.org/index.php/Wa … _libraries
https://wiki.gnome.org/Initiatives/Wayland/Applications
I tried to launch it as user (not from gdm) with the following script so it also sets some appropriate env vars:
#!/bin/sh
export GDK_BACKEND=wayland
export SDL_VIDEODRIVER=wayland
export CLUTTER_BACKEND=wayland
# WARNING: Something needed for QT backend? Recompile from git...
# https://wiki.archlinux.org/index.php/Wayland#GUI_libraries
export ECORE_EVAS_ENGINE=wayland_egl
export ELM_ENGINE=wayland_egl
#export ECORE_EVAS_ENGINE=wayland_shm
#export ELM_ENGINE=wayland_shm
gnome-session --session=gnome-wayland
I checked journalctl:
Oct 17 10:23:28 Boltzmann login[295]: LOGIN ON tty1 BY adrien
Oct 17 10:23:39 Boltzmann gnome-session[397]: gnome-session[397]: GLib-CRITICAL: g_environ_setenv: assertion 'value != NULL' failed
Oct 17 10:23:39 Boltzmann gnome-session[397]: GLib-CRITICAL: g_environ_setenv: assertion 'value != NULL' failed
Oct 17 10:23:42 Boltzmann systemd-logind[286]: kernel does not support evdev-revocation
Oct 17 10:23:42 Boltzmann kernel: gnome-shell[406]: segfault at 61 ip 00007f2a7d097455 sp 00007ffff0ab4178 error 4 in libgobject-2.0.so.0.4200.0[7f2a7d064000+4f000]
Oct 17 10:23:42 Boltzmann gnome-session[397]: gnome-session[397]: WARNING: Application 'gnome-shell-wayland.desktop' killed by signal 11
Oct 17 10:23:42 Boltzmann gnome-session[397]: WARNING: Application 'gnome-shell-wayland.desktop' killed by signal 11
Oct 17 10:23:42 Boltzmann gnome-session[397]: Unrecoverable failure in required component gnome-shell-wayland.desktop
Oct 17 10:23:43 Boltzmann kernel: fuse init (API version 7.23)
Oct 17 10:23:43 Boltzmann kernel: cfg80211: Calling CRDA to update world regulatory domain
Oct 17 10:23:45 Boltzmann org.gtk.vfs.Daemon[401]: A connection to the bus can't be made
Oct 17 10:23:45 Boltzmann org.gtk.vfs.Daemon[401]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-erro
Oct 17 10:23:45 Boltzmann ca.desrt.dconf[401]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-qu
Oct 17 10:23:50 Boltzmann systemd-coredump[410]: Process 406 (gnome-shell) of user 1000 dumped core.
And dmesg:
[ 42.954209] gnome-shell[406]: segfault at 61 ip 00007f2a7d097455 sp 00007ffff0ab4178 error 4 in libgobject-2.0.so.0.4200.0[7f2a7d064000+4f000]
Any idea about what I did wrong?

Here is the story about me trying to launch gnome-session under gdb.
First compile it with debug symbols...
Get AUR package gnome-session-git
Modify PKGBUILD so the symbols are kept:
- Add this to options: '!strip'
- Override cflags: make the command autogen.sh launch with this env var:
CFLAGS="-pipe -fstack-protector-strong --param=ssp-buffer-size=4 -g"
Install that package, launch the command:
gdb --args gnome-session --session=gnome-wayland
Before running the program, set a breakpoint on the only function we know is involved in the assert failure:
b g_environ_setenv
Then run the program. GDB does not stop to indicate an assert failed, too bad. However the function g_environ_setenv is entered only 4 times, all of them from lines 1024, 1025 and 1028 of source file gnome-session/gsm-autostart-app.c.
A quick look at the line 1024:
g_app_launch_context_setenv (ctx, "DISPLAY", g_getenv ("DISPLAY"))
It seems to get the env var DISPLAY and save the value in a structure that contains all env vars for future app launch. On my machine, DISPLAY is not set so this line is a very good candidate for failure.
Firts test: set DISPLAY to something. I set :0.0 because I remember nothing about what we are supposed to set. Anyway, a crash still happens, but a completely different one, which seems to reference stuff from X... journalctl says this:
Oct 18 01:05:17 Boltzmann org.a11y.Bus[15403]: Activating service name='org.a11y.atspi.Registry'
Oct 18 01:05:17 Boltzmann org.a11y.Bus[15403]: Successfully activated service 'org.a11y.atspi.Registry'
Oct 18 01:05:17 Boltzmann org.a11y.Bus[15403]: Activating service name='org.a11y.atspi.Registry'
Oct 18 01:05:17 Boltzmann org.a11y.Bus[15403]: Successfully activated service 'org.a11y.atspi.Registry'
Oct 18 01:05:17 Boltzmann org.a11y.Bus[15403]: Activating service name='org.a11y.atspi.Registry'
Oct 18 01:05:17 Boltzmann org.a11y.Bus[15403]: Successfully activated service 'org.a11y.atspi.Registry'
Oct 18 01:05:17 Boltzmann org.a11y.atspi.Registry[15410]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Oct 18 01:05:17 Boltzmann org.a11y.atspi.Registry[15410]: ** (at-spi2-registryd:15413): WARNING **: Could not open X display
Oct 18 01:05:17 Boltzmann org.a11y.atspi.Registry[15410]: ** (at-spi2-registryd:15413): WARNING **: AT-SPI: Cannot open default display
Oct 18 01:05:17 Boltzmann org.a11y.atspi.Registry[15410]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Oct 18 01:05:17 Boltzmann org.a11y.atspi.Registry[15410]: ** (at-spi2-registryd:15416): WARNING **: Could not open X display
Oct 18 01:05:17 Boltzmann org.a11y.atspi.Registry[15410]: ** (at-spi2-registryd:15416): WARNING **: AT-SPI: Cannot open default display
Oct 18 01:05:17 Boltzmann gnome-session[15399]: ** (gnome-session-failed:15418): WARNING **: Could not open X display
Oct 18 01:05:17 Boltzmann gnome-session[15399]: Unable to init server: Could not connect: Connection refused
Oct 18 01:05:17 Boltzmann gnome-session[15399]: ** (gnome-session-failed:15418): WARNING **: Cannot open display:
Oct 18 01:05:17 Boltzmann org.a11y.atspi.Registry[15410]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Oct 18 01:05:17 Boltzmann org.a11y.atspi.Registry[15410]: ** (at-spi2-registryd:15420): WARNING **: Could not open X display
Oct 18 01:05:17 Boltzmann org.a11y.atspi.Registry[15410]: ** (at-spi2-registryd:15420): WARNING **: AT-SPI: Cannot open default display
Second test: comment the line 1024 just to see, recompile, and re-launch. Again, a crash, but journalctl simply says:
Oct 18 01:07:25 Boltzmann gnome-session[16991]: gnome-session[16991]: WARNING: Application 'gnome-shell-wayland.desktop' killed by signal 11
Oct 18 01:07:25 Boltzmann gnome-session[16991]: WARNING: Application 'gnome-shell-wayland.desktop' killed by signal 11
Oct 18 01:07:25 Boltzmann gnome-session[16991]: Unrecoverable failure in required component gnome-shell-wayland.desktop
Really looks like there is still some dirty stuff in gnome-session about wayland...

Similar Messages

Since gnome 3.2 problems with screen updates

Hi!
Since the upgrade to gnome 3.2 I have a very weird problem that the screen doesn't get redrawn.
For example, after login into gnome-shell starting terminator, as soon as I start typing something
the cursor stops blinking and no characters apear. My workaround is to switch to any tty and back to Xorg.
After that the characters are there. this is somewhat anoying and seems to get worse in the last week.
It also seems to happen a lot if I have to input a password e.g. gksudo or wlan password.
I have a hp probook 5320m with intel i915 driver, I'm not sure if the gnome shell triggers some intel bug
or gnome shell is doing something wrong here.
Anyone else has similar issues?
With gnome 3.0 I had no problems.

In the meantime I found the following:
- When I suspend with the power button, the screen is locked, but not when I use the status menu option
- This seems to be related to the screen setting 'Lock screen after'. I had it set to 1 minutes. When I change it to 'after the screen goes blank' the
problem doesn't seem to occur.
So, the way it looks now, it uses the same settings for delaying the locking the screen after the screensaver kicks in when locking the screen before suspend.
Which doesn't make much sense. And then the behaviour is still inconsistent with the power button suspend.

Gnome 2.14 - problem with gconf missing icons

Hi,
I just installed gnome 2.14 and gnome-extra from testing, but when I log in, all icons are missing. Trying to change settings with the theme manager leads to the following error message: The default theme schemas could not be found on your system. This means that you probably don't have metacity installed, or that your gconf is configured incorrectly.
How do I reconfigure gconf correctly? I've tried to fire up gconf-editor, but I can't even see metacity under apps.
I should probably mention, that I've installed this on a freshly installed Arch, with no previous DE's installed
Regards,
Simon

Blaavis, that didn't seem to do the trick, reinstalling xproto had no effect. System is completely up to date with testing repository enabled. If I try to run gnome-theme-manager from the console, I immediately get a pop up window, with the error message as in my first post, there are no error messages otherwise in the terminal.
This appears in /var/log/messages:
Mar 30 18:50:38 myhost (sims-2898): Resolved address "xml:readonly:/opt/gnome/et c/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0
Mar 30 18:50:54 myhost (sims-2898): Resolved address "xml:readwrite:/home/sims/. gconf" to a writable configuration source at position 0
What else could I try?

Ups - Black screened Gnome Session after playing with Gnome Wayland

I was curious about gnome wayland, and just tried it by selection in gdm, with xorg-server-xwayland installed. It felt warm, spicy, and showed minor glitches and some bleeding edges. To my surprise, when I logged out, and went back to Gnome (without wayland), the gnome session starts up just to see the mouse pinter vanishing in front of a pure, black monitor while the hard drive led shows heavy activity. I went away to have a cup of coffee. Coming back, the hard drive was sleeping, and the monitor was still black. Ctrl - Alt - F2 gave me a console, but no idea what to do, so I decided to go for a reboot, and noticed I still could run Gnome Wayland, but no more Gnome.
Finally, I gave up on finding out what really happened. I guess something in the gnome configurations was messed up with wayland and non-wayland. Adding a new user and starting a new Gnome session showed me the problem was related to my user account. So I purged my .config-gnome-related files and folders, and things are behaving well again.
Therefore, I take this as a proof: running Gnome Wayland will change parts of your configuration, and be warned, Gnome might not be able to turn them back again.
Last edited by Moo-Crumpus (2014-10-27 14:00:28)

I was curious about gnome wayland, and just tried it by selection in gdm, with xorg-server-xwayland installed. It felt warm, spicy, and showed minor glitches and some bleeding edges. To my surprise, when I logged out, and went back to Gnome (without wayland), the gnome session starts up just to see the mouse pinter vanishing in front of a pure, black monitor while the hard drive led shows heavy activity. I went away to have a cup of coffee. Coming back, the hard drive was sleeping, and the monitor was still black. Ctrl - Alt - F2 gave me a console, but no idea what to do, so I decided to go for a reboot, and noticed I still could run Gnome Wayland, but no more Gnome.
Finally, I gave up on finding out what really happened. I guess something in the gnome configurations was messed up with wayland and non-wayland. Adding a new user and starting a new Gnome session showed me the problem was related to my user account. So I purged my .config-gnome-related files and folders, and things are behaving well again.
Therefore, I take this as a proof: running Gnome Wayland will change parts of your configuration, and be warned, Gnome might not be able to turn them back again.
Last edited by Moo-Crumpus (2014-10-27 14:00:28)

No TV sound - Problem with Pulseaudio and Gnome

Hi Community!
Since January 2013 I got big problems with the sound of my tvcard. The card is a Sundtek Media TV Pro. But after all the problems have nothing to to with the card itself!
So far I found out, that the problem is with Pulseaudio.
- Sound works under Windows on same PC.
- Sound don't work under Arch - not with tvtime, not with vlc, etc.
- Problem occurs even on a new installed system with the Arch-2013-02-01 install medium.
cat /etc/mediasrv.log
[1033] Pulseaudio connect reported an error (6 - Connection refused)
[1033] select error() in audio processor (can be caused because of pulseaudio) (Interrupted system call)
After setting up a new Arch installation with just xorg-server, gnome, tvtime and the sundtek driver from AUR I run journalctl -b:
Feb 10 16:25:15 hightower pulseaudio[636]: [pulseaudio] pid.c:
Daemon already running.
With sudo journalctl | grep 'Feb 10 16:2' I get the following output:
Feb 10 16:25:01 hightower rtkit-daemon[489]: Successfully made thread 488 of process 488 (/usr/bin/pulseaudio) owned by '120' high priority at nice level -11.
Feb 10 16:25:14 hightower rtkit-daemon[489]: Successfully made thread 606 of process 606 (/usr/bin/pulseaudio) owned by '1000' high priority at nice level -11.
Feb 10 16:25:15 hightower rtkit-daemon[489]: Successfully made thread 636 of process 636 (/usr/bin/pulseaudio) owned by '1000' high priority at nice level -11.
Feb 10 16:25:15 hightower pulseaudio[636]: [pulseaudio] pid.c: Daemon already running.
Feb 10 16:28:55 hightower pulseaudio[1000]: [pulseaudio] module-jackdbus-detect.c: Unable to contact D-Bus session bus: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
Feb 10 16:28:55 hightower pulseaudio[1000]: [pulseaudio] module.c: Failed to load module "module-jackdbus-detect" (argument:""): initialization failed.
Feb 10 16:28:55 hightower pulseaudio[1000]: [pulseaudio] socket-server.c: bind(): Die Adresse wird bereits verwendet
Feb 10 16:28:55 hightower pulseaudio[1000]: [pulseaudio] module.c: Failed to load module "module-esound-protocol-unix" (argument: ""): initialization failed.
Feb 10 16:28:55 hightower pulseaudio[1000]: [pulseaudio] main.c: Module load failed.
Feb 10 16:28:55 hightower pulseaudio[1000]: [pulseaudio] main.c: Module load failed.
Feb 10 16:28:55 hightower pulseaudio[1000]: [pulseaudio] main.c: Konnte Daemon nicht initialisieren.
Feb 10 16:28:55 hightower pulseaudio[997]: [pulseaudio] main.c: Start des Daemons fehlgeschlagen.
So, if I understand right, pulseaudio is alreade started by the rtkit-daemon and gnome couldn't start it again.
At https://bugs.archlinux.org/task/30926 I found a hint concerning /etc/xdg/autostart/pulseaudio.desktop and /etc/xdg/autostart/pulseaudio-kde.desktop.
After removing them from /etc/xdg/autostart and running journalctl -b there are no more errors.
With sudo journalctl | grep 'pulseaudio' I get:
sudo journalctl | grep 'Feb 10 17:4' | grep 'pulse*'
Feb 10 17:41:42 hightower rtkit-daemon[485]: Successfully made thread 484 of process 484 (/usr/bin/pulseaudio) owned by '120' high priority at nice level -11.
Feb 10 17:41:55 hightower rtkit-daemon[485]: Successfully made thread 625 of process 625 (/usr/bin/pulseaudio) owned by '1000' high priority at nice level -11.
In my opinion all looks ok! I also checked the channels with the alsamixer and it looks good, too.
So I ran vlc v4l2://:dev=/dev/video0:width=720:height=576:tuner-frequency=510750:adev=/dev/null:standard=255 - but still no sound.
With cat /var/log/mediasrv.log I checked the drivers logfile:
2013-02-10 17:48:55 [343] SETTING DVB-C
2013-02-10 17:48:55 [343] switching to analog TV
2013-02-10 17:48:56 [343] SETTING PAL/SECAM
2013-02-10 17:48:58 [343] invalid audio input selected: 2
2013-02-10 17:48:58 [343] Setting frequency: 510750000
2013-02-10 17:48:58 [343] Using settings for Europe
2013-02-10 17:48:58 [343] Set Pixelformat: 0 YUV 4:2:2 (YUYV)
2013-02-10 17:48:58 [1033] Starting audio processor (PID 1033)
2013-02-10 17:48:58 [1033] initializing audio in audio processor
2013-02-10 17:48:58 [1033] loaded local pulseaudio driver
2013-02-10 17:48:58 [1033] select error() in audio processor (can be caused because of pulseaudio) (Interrupted system call)
2013-02-10 17:48:59 [1033] Pulseaudio connect reported an error (6 - Connection refused)
2013-02-10 17:48:59 [1033] select error() in audio processor (can be caused because of pulseaudio) (Interrupted system call)
2013-02-10 17:48:59 [1033] Pulseaudio connect reported an error (6 - Connection refused)
I started tvtime again. This time I ran rm -rf ~/.config/pulse/ and killall pulseaudio to kill the Pulseaudio server. I instantly got a loud noise out of my speakers.
I closed tvtime and re-opened it. And there it was: TV SOUND OUT OF MY SPEAKERS!
But now, when I run pavucontrol I get:
Connection to PulseAudio failed. Automatic retry in 5s.
In this cas this is likely because PULSE_SERVER in the Environment/X11 root Windows Properties or default-server in client.conf is misconfigured.
This situation can also arrise when PulseAudio crashed and left stale details in the X11 Root Windows.
If this is the case, then PuseAudio should autospawn again, or if this is not configured you sould run start-pulseaudio-x11 manually.
I got the information from Sundtek, that Pulseaudio should not be started as system service. Instead, every user should have an own Pulseaudio daemon and that PA was concepted this way. But they don't know how it is implemented in ArchLinux.
I also don't know it exactly. So the question to all you ArchLinu pro's:
How is PA implemented in Arch? And how can I sustainable solve my problem?
Thank you for your time and help!
Durag

There is just one more thing I found out.
After logging into Gnome and running ps aux | grep pulse I get:
rebel 727 0.7 0.2 444316 10288 ? S<l 03:02 0:00 /usr/bin/pulseaudio --start --log-target=syslog
rebel 731 0.0 0.0 71236 2652 ? S 03:02 0:00 /usr/lib/pulse/gconf-helper
rebel 843 0.0 0.0 17396 1184 pts/0 D+ 03:03 0:00 grep pulse
To get the sound to work I run:
rm -rf .config/pulse/
killall pulseaudio
killall -9 pulseaudio
I again run ps aux | grep pulse
rebel 4016 4.2 0.2 510124 11528 ? Sl 03:06 0:02 /usr/bin/pulseaudio --start --log-target=syslog
rebel 4020 0.0 0.0 71368 2700 ? S 03:06 0:00 /usr/lib/pulse/gconf-helper
rebel 4046 0.0 0.0 19456 1216 pts/0 R+ 03:07 0:00 grep pulse
I can recognize that the STATs have changed. Maybe this can help to solve the problem?

Problem with Gnome and D-Bus

Hi to all, i have a problem with Gnome and D-Bus
Versions:
Arch Release: 0.7.2 Testing
Gnome: 2.14.1-2
D-Bus: 0.61-3
Screenshot explain all:
[URL=http://img366.imageshack.us/my.php?image=gpwned6be.jpg][/URL]

1>then i can't promote garnome on this forum??
yeah you can, but not as a solution to gnome related problem in arch. cause this doesn't resolve anything.
2>You don't have to, garnome2.14.2.1(481kb) download the patches and patch it automatically, just change install dir to /usr
(ONLY if you are using console-linux who want gnome a try). of course there is need small arch related patch.(in my experience 0)
eh, i haven't got a clue what this means, putting patches upstream means they will get include in gargnome and upstream releases. i only tried to say we put a lot of our free time in gnome for arch.
2-1>Well said, so choice is the each one's freedom.
and this category isn't arch, this is Desktop Environments,
i installed arch, BUT THAT DOESN'T MEANS I SHOULD USE gnome FROM ARCH!!!
agreed, but again then we won't support your desktop.
ARCH != gnome
3>some bug stuff about Xorg-7.0, include mine
http://bbs.archlinux.org/viewtopic.php?t=22210[/quote]
ah bugs.archlinux.org so it can be fixed.

Problem with Notifications (Gnome 3.4.1)

Hey guys.
I just installed Arch with Gnome 3.4.1, and everything works fine. I just had two issues. The first one, was the Date/Time, and that i solved by reading another thread here.
The second problem is what i'm worried about...
The default behavior for notifications is to show the notification bar for some seconds, and then hide it, right? Then, if there's more notifications of that same program, put a counter on it.
The thing is, i have no such behavior. The bar don't show, and the notification counter do not work. I use Empathy, and when i receive more than one message, the notification counter doesn't appear, and i think, because of that, some extensions that use notifications counters don't work at all.
Not sure if i was clear, let me know if you need more details. I have vanilla Gnome Shell Theme, Icons and all the extensions are disabled. Everything was installed with 'pacman -S gnome gnome-extra'
Can you guys give me some light on this? Is it a upstream bug? Ubuntu with shell 3.4.1 seemed to work fine, but i really want to use Arch....
Thanks in advance.

m79reed wrote:
@jakobcreutzfeldt,
Try install this extension: https://extensions.gnome.org/extension/ … -notifier/. It's much easier to see how counters is working with that one.
And now...
Counters is not working for me:
1) contacts that have already a chat WINDOW opened (chat window is not active)
2) contact that chat TAB is active (chat window is not active).
Red notification icon blinks only fast and gone - like something marks it as readed.
For any other contacts (someone send a message to you first [no opened chat window with that contact] OR TAB is non-active) notification counters is working fine.
I will try to add a new account and test on it. Mayby something is wrong with old configuraction files from gnome-shell 3.2...
[edit]
OK, i've tested with fresh account and problem exists and sound notification works only for contacts sending a new message.
[edit2]
Just discovered that notification counters is not working when use -a option for notify-send command. Any other options works fine. Ex.:
notify-send -a empathy -i empathy test1 test2 - counter is not working
notify-send -i empathy test1 test2 - counter is working fine
This is my problem exatly. Still not able to figure this out.
No, it's not a problem with extension. Counter notifications is not working without it too.
@jakobcreutzfeldt,
Can you paste yours:
pacman -Qs notification
output?
This is mine:
pacman -Qs notification
local/libevent 2.0.18-1
An event notification library
local/libnotify 0.7.5-1
Desktop notification library
local/notification-daemon 0.7.4-1 (gnome)
Notification daemon for the desktop notifications framework
local/startup-notification 0.12-2
Monitor and display application startup

Problems with GNOME After The Last Upgrade

I have too many problems these days with my Arch box.. And I don't know when or how these problems are solved but I'm really bored about having problem all the time. I don't know all of these are bugs but if they're I'm ready to enter some bug reports.
1) After the last update, Metacity doesn't start automatically. So everytime, I don't have my mouse theme, my thema of borders of the windows, the notes I took with gnome's note applet doesn't disappear.
2) gnome-power-manager is never the same that I used to.. I just found that killing and rerunning it is at least make it work. But it's menus and options is not rich as I was earlier times. It doesn't say that much as it did in the earlier times.

I've same problem with gnome-power-manager, it works only when i kill it with killall gnome-power-monitor and re-run it.
About metacity i don't have problem with it.

Help - problems with GNOME 2.6 install

I just did a fresh install of Arch base packages, then xfree86. I then did pacman -Sy pacman, pacman -Syu, then pacman -S gnome
Then, while installing GNOME, my screen fills with about 500 lines of the following error:
error while loading shared libraries: libgconf-2.so.4: cannot open shared object file: no such file or directory
Can anyone suggest a fix?

Xentac wrote:
I don't know if these are fatal errors exactly. The problem is that gnome-common installs a script in /etc/profile.d, that hasn't been run yet, to set up things like library paths. Log out and log back in, then try gnome. If that doesn't work then try running ldconfig and try again.
If it still doesn't work then it is indeed a problem that does need looking at. I've got ideas... but they're still just ideas.
Well, the gconf library errors started during the fresh install of GNOME, and all of the other errors I'm seeing when GNOME starts, as far as I can tell, point to gconf. But that's a guess on my part.
Yes, I've tried logging out, restarting, re-installing, ldconfig, but no luck.

Problems with (selfcompiled) gnome-applets

I have experienced problems with gnome-applets. Those that come with a basic gnome installation work fine and there is no problem adding them to the panel. However, when I use selfcompiled applets I always get the following error when trying to add them.
The panel encountered a problem while loading "OAFIID:GNOME_HDAPS_STATUSApplet".
(Where OAFIID: is followed by the applets name.)
I tried pkgbuilds from the AUR like 'ontv' and 'gnome-hdaps-applet' and I've tried compile applets manually. Always the same issue. I don't know what's wrong. I've found threads where people get that error message on any applet but I didn't find a solution to my problem, as all my other applets work fine. Any ideas?

Have you done any Gnome updates since this applet was compiled? I seem to recall having a similar problem with an applet I built and, falling back to the Windows days, did a reboot, rebuilt the applet, and then all was well after I reinstalled the applet.
Not sure if this will help, but it cannot hurt.
Bob

Any known problems with Gnome 2.28 before I update?

Hi, I would like know is there any known problems with Gnome 2.28?
I read that there are a login/logout time increased, something else?
Thanks in advance!

when I upgraded to 2.28, icons in the menu appeared and I'm not able to disable them... other than that gnome 2.28 seems fine to me.

A few problems with Gnome

Ive installed gnome on a fresh arch install.
Ive got gnome and GDM working now but im having a few problems with some of the apps in gnome.
The first problem ive noticed is when i attempt to open "Apperance Preferances" the bug report is:
Distribution: Unknown
Gnome Release: 2.22.3 2008-07-02 (Archlinux)
BugBuddy Version: 2.22.0
System: Linux 2.6.26-ARCH #1 SMP PREEMPT Tue Aug 26 21:15:43 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome
Memory status: size: 0 vsize: 0 resident: 0 share: 0 rss: 0 rss_rlim: 0
CPU usage: start_time: 0 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0
----------- .xsession-errors ---------------------
(gnome-appearance-properties:3609): Pango-CRITICAL **: pango_color_parse: assertion `spec != NULL' failed
(gnome-appearance-properties:3609): Pango-CRITICAL **: pango_color_parse: assertion `spec != NULL' failed
(gnome-appearance-properties:3609): Pango-CRITICAL **: pango_color_parse: assertion `spec != NULL' failed
(gnome-appearance-properties:3609): Pango-CRITICAL **: pango_color_parse: assertion `spec != NULL' failed
(gnome-appearance-properties:3609): Pango-CRITICAL **: pango_color_parse: assertion `spec != NULL' failed
(gnome-appearance-properties:3609): Pango-CRITICAL **: pango_color_parse: assertion `spec != NULL' failed
(gnome-appearance-properties:3609): Pango-CRITICAL **: pango_color_parse: assertion `spec != NULL' failed
(gnome-appearance-properties:3609): Pango-CRITICAL **: pango_color_parse: assertion `spec != NULL' failed
the next error is when i open the preferances for the file browser
Distribution: Unknown
Gnome Release: 2.22.3 2008-07-02 (Archlinux)
BugBuddy Version: 2.22.0
System: Linux 2.6.26-ARCH #1 SMP PREEMPT Tue Aug 26 21:15:43 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome
Memory status: size: 0 vsize: 0 resident: 0 share: 0 rss: 0 rss_rlim: 0
CPU usage: start_time: 0 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0
----------- .xsession-errors ---------------------
(gnome-appearance-properties:3609): Pango-CRITICAL **: pango_color_parse: assertion `spec != NULL' failed
(gnome-appearance-properties:3609): Pango-CRITICAL **: pango_color_parse: assertion `spec != NULL' failed
(gnome-appearance-properties:3609): Pango-CRITICAL **: pango_color_parse: assertion `spec != NULL' failed
(gnome-appearance-properties:3609): Pango-CRITICAL **: pango_color_parse: assertion `spec != NULL' failed
** Eel:ERROR:(eel-preferences.c:116):preferences_gconf_value_get_string: assertion failed: (value->type == GCONF_VALUE_STRING)
seahorse nautilus module initialized
** (nautilus:3623): WARNING **: Unable to add monitor: Not supported
** Eel:ERROR:(eel-preferences.c:116):preferences_gconf_value_get_string: assertion failed: (value->type == GCONF_VALUE_STRING)

Ive installed gnome on a fresh arch install.
Ive got gnome and GDM working now but im having a few problems with some of the apps in gnome.
The first problem ive noticed is when i attempt to open "Apperance Preferances" the bug report is:
Distribution: Unknown
Gnome Release: 2.22.3 2008-07-02 (Archlinux)
BugBuddy Version: 2.22.0
System: Linux 2.6.26-ARCH #1 SMP PREEMPT Tue Aug 26 21:15:43 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome
Memory status: size: 0 vsize: 0 resident: 0 share: 0 rss: 0 rss_rlim: 0
CPU usage: start_time: 0 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0
----------- .xsession-errors ---------------------
(gnome-appearance-properties:3609): Pango-CRITICAL **: pango_color_parse: assertion `spec != NULL' failed
(gnome-appearance-properties:3609): Pango-CRITICAL **: pango_color_parse: assertion `spec != NULL' failed
(gnome-appearance-properties:3609): Pango-CRITICAL **: pango_color_parse: assertion `spec != NULL' failed
(gnome-appearance-properties:3609): Pango-CRITICAL **: pango_color_parse: assertion `spec != NULL' failed
(gnome-appearance-properties:3609): Pango-CRITICAL **: pango_color_parse: assertion `spec != NULL' failed
(gnome-appearance-properties:3609): Pango-CRITICAL **: pango_color_parse: assertion `spec != NULL' failed
(gnome-appearance-properties:3609): Pango-CRITICAL **: pango_color_parse: assertion `spec != NULL' failed
(gnome-appearance-properties:3609): Pango-CRITICAL **: pango_color_parse: assertion `spec != NULL' failed
the next error is when i open the preferances for the file browser
Distribution: Unknown
Gnome Release: 2.22.3 2008-07-02 (Archlinux)
BugBuddy Version: 2.22.0
System: Linux 2.6.26-ARCH #1 SMP PREEMPT Tue Aug 26 21:15:43 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome
Memory status: size: 0 vsize: 0 resident: 0 share: 0 rss: 0 rss_rlim: 0
CPU usage: start_time: 0 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0
----------- .xsession-errors ---------------------
(gnome-appearance-properties:3609): Pango-CRITICAL **: pango_color_parse: assertion `spec != NULL' failed
(gnome-appearance-properties:3609): Pango-CRITICAL **: pango_color_parse: assertion `spec != NULL' failed
(gnome-appearance-properties:3609): Pango-CRITICAL **: pango_color_parse: assertion `spec != NULL' failed
(gnome-appearance-properties:3609): Pango-CRITICAL **: pango_color_parse: assertion `spec != NULL' failed
** Eel:ERROR:(eel-preferences.c:116):preferences_gconf_value_get_string: assertion failed: (value->type == GCONF_VALUE_STRING)
seahorse nautilus module initialized
** (nautilus:3623): WARNING **: Unable to add monitor: Not supported
** Eel:ERROR:(eel-preferences.c:116):preferences_gconf_value_get_string: assertion failed: (value->type == GCONF_VALUE_STRING)

[GNOME] problem with gvfsd-metada

I have problems with gvfs. My computer sometimes crash. I already have upgraded gvfs to version 1.5 but still the same. Can someone help me?
>everything.log
Nov 18 01:47:51 myhost NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete.
Nov 18 01:48:47 myhost kernel: gvfsd-metadata[2171]: segfault at 8 ip 0804c9ba sp bfef3b40 error 4 in gvfsd-metadata[8048000+b000]
Nov 18 02:10:17 myhost -- MARK --
Nov 18 02:11:18 myhost kernel: gvfsd-metadata[16155]: segfault at 8 ip 0804c9ba sp bfbc7650 error 4 in gvfsd-metadata[8048000+b000]
Nov 18 02:16:37 myhost kernel: gvfsd-metadata[30265]: segfault at 8 ip 0804c9ba sp bf841b60 error 4 in gvfsd-metadata[8048000+b000]
Nov 18 02:26:09 myhost kernel: gvfsd-metadata[13060]: segfault at 8 ip 0804c9ba sp bf85a740 error 4 in gvfsd-metadata[8048000+b000]
Nov 18 02:53:58 myhost kernel: gvfsd-metadata[18275]: segfault at 8 ip 0804c9ba sp bff7fea0 error 4 in gvfsd-metadata[8048000+b000]
Nov 18 02:55:03 myhost kernel: gvfsd-metadata[21812]: segfault at 8 ip 0804c9ba sp bffdb110 error 4 in gvfsd-metadata[8048000+b000]
Nov 18 03:10:37 myhost NetworkManager: <info> (eth0): supplicant connection state: completed -> disconnected
Nov 18 03:10:37 myhost NetworkManager: <info> (eth0): supplicant connection state: disconnected -> scanning

Btw, it only happens if you specify that you want JFrame and JDialog decorated:
setDefaultLookAndFeelDecorated(true)
As much as I like the new 1.5 Swing decorations I guess I will have to stick to no decorations under Linux.

[SOLVED] Gnome - problem with sound

hi! i have a problem with my eee pc 1000. i have no sound only from my right speaker... here is my amixer result:
Simple mixer control 'PCM',0
Capabilities: pvolume
Playback channels: Front Left - Front Right
Limits: Playback 0 - 255
Mono:
Front Left: Playback 255 [100%] [0.00dB]
Front Right: Playback 255 [100%] [0.00dB]
Simple mixer control 'LineOut',0
Capabilities: pvolume pswitch
Playback channels: Front Left - Front Right
Limits: Playback 0 - 64
Mono:
Front Left: Playback 64 [100%] [1.00dB] [on]
Front Right: Playback 64 [100%] [1.00dB] [on]
Simple mixer control 'Mic Boost',0
Capabilities: volume
Playback channels: Front Left - Front Right
Capture channels: Front Left - Front Right
Limits: 0 - 3
Front Left: 0 [0%]
Front Right: 0 [0%]
Simple mixer control 'Capture',0
Capabilities: cvolume cswitch
Capture channels: Front Left - Front Right
Limits: Capture 0 - 46
Front Left: Capture 25 [54%] [8.00dB] [on]
Front Right: Capture 25 [54%] [8.00dB] [on]
Simple mixer control 'iSpeaker',0
Capabilities: pswitch
Playback channels: Front Left - Front Right
Mono:
Front Left: Playback [on]
Front Right: Playback [on]
[manolos@arch Desktop]$ cd /
[manolos@arch /]$ amixer
Simple mixer control 'PCM',0
Capabilities: pvolume
Playback channels: Front Left - Front Right
Limits: Playback 0 - 255
Mono:
Front Left: Playback 255 [100%] [0.00dB]
Front Right: Playback 255 [100%] [0.00dB]
Simple mixer control 'LineOut',0
Capabilities: pvolume pswitch
Playback channels: Front Left - Front Right
Limits: Playback 0 - 64
Mono:
Front Left: Playback 64 [100%] [1.00dB] [on]
Front Right: Playback 64 [100%] [1.00dB] [on]
Simple mixer control 'Mic Boost',0
Capabilities: volume
Playback channels: Front Left - Front Right
Capture channels: Front Left - Front Right
Limits: 0 - 3
Front Left: 0 [0%]
Front Right: 0 [0%]
Simple mixer control 'Capture',0
Capabilities: cvolume cswitch
Capture channels: Front Left - Front Right
Limits: Capture 0 - 46
Front Left: Capture 25 [54%] [8.00dB] [on]
Front Right: Capture 25 [54%] [8.00dB] [on]
Simple mixer control 'iSpeaker',0
Capabilities: pswitch
Playback channels: Front Left - Front Right
Mono:
Front Left: Playback [on]
Front Right: Playback [on]
[manolos@arch /]$ clear
[manolos@arch /]$ amixer
Simple mixer control 'PCM',0
Capabilities: pvolume
Playback channels: Front Left - Front Right
Limits: Playback 0 - 255
Mono:
Front Left: Playback 255 [100%] [0.00dB]
Front Right: Playback 255 [100%] [0.00dB]
Simple mixer control 'LineOut',0
Capabilities: pvolume pswitch
Playback channels: Front Left - Front Right
Limits: Playback 0 - 64
Mono:
Front Left: Playback 64 [100%] [1.00dB] [on]
Front Right: Playback 64 [100%] [1.00dB] [on]
Simple mixer control 'Mic Boost',0
Capabilities: volume
Playback channels: Front Left - Front Right
Capture channels: Front Left - Front Right
Limits: 0 - 3
Front Left: 0 [0%]
Front Right: 0 [0%]
Simple mixer control 'Capture',0
Capabilities: cvolume cswitch
Capture channels: Front Left - Front Right
Limits: Capture 0 - 46
Front Left: Capture 25 [54%] [8.00dB] [on]
Front Right: Capture 25 [54%] [8.00dB] [on]
Simple mixer control 'iSpeaker',0
Capabilities: pswitch
Playback channels: Front Left - Front Right
Mono:
Front Left: Playback [on]
Front Right: Playback [on]
i have sound from both speaker in headset... its weird.
please tell me what setting is wrong! thanks for your time
problem solved! I dont know how...
Last edited by manolos (2009-06-11 13:40:08)

Just tryed playing a wav with aplay and it didn't give me any errors, but I didn't hear anything if that helps anymore. Running a amixer set MASTER 70% unmute also gives me the unable to find simple control 'MASTER',0 error too, though I can change the volume fine with alsamixer so I'm not sure why that is. The correct module is loaded (snd-hda-intel). Otherwise I'm at a complete loss.
edit: amixer set MASTER 70% gives me the same error on an ubuntu livecd where sound does work so that seems normal. I don't know what changed, but I can now open the volume control so the gstreamer error goes away, however I still can't get any sound, be it with aplay or something else. I'm starting to think the solution may be to pass on arch and move to something better.
Last edited by kryptobs2000 (2010-07-10 16:37:47)

Problem with Gnome3 and/or graphics card Nvidia 8600M GT

Feb 22 07:40:21 localhost dbus[712]: [system] Failed to activate service 'org.freedesktop.Avahi': timed out
Feb 22 07:50:30 localhost kernel: [ 679.031379] gnome-shell[1277]: segfault at 10 ip 00007f3bbd305c0f sp 00007f3b84ff86d8 error 6 in libnvidia-tls.so.295.20[7f3bbd305000+3000]
Feb 22 07:50:31 localhost gnome-session[888]: WARNING: Application 'gnome-shell.desktop' killed by signal
Feb 22 07:50:35 localhost kernel: [ 683.420948] gnome-shell[1300]: segfault at 10 ip 00007f43bc84dc0f sp 00007f43877fd6d8 error 6 in libnvidia-tls.so.295.20[7f43bc84d000+3000]
Feb 22 07:50:35 localhost gnome-session[888]: WARNING: Application 'gnome-shell.desktop' killed by signal
Feb 22 07:50:35 localhost gnome-session[888]: WARNING: App 'gnome-shell.desktop' respawning too quickly
Feb 22 06:52:39 localhost rtkit-daemon[1004]: Successfully made thread 1420 of process 1420 (/usr/bin/pulseaudio) owned by '1000' high priority at nice level -11.
Feb 22 07:52:39 localhost goa[1441]: goa-daemon version 3.2.1 starting [main.c:112, main()]
Feb 22 07:58:22 localhost kernel: [ 1150.316794] CE: hpet increased min_delta_ns to 20113 nsec
Hi,
Here is my /var/log/messages.log output.
Since several days my computer repeatedly restarts programs that require at least a bit memory, such as firefox ('segmentation fault'), skype, virtualbox, generaly gnome 3 environment. Sometimes it happens that the system hangs and I can't do nothing, although I can hear that hard disk is working - at that moment only hard reset helps.
I know that the Dell Inspiron laptops (1720) have problems with Nvidia 8600M GT (the cold solder). Is it like that this time? Or maybe something wrong with the memory, CPU (Core Duo) cache memory?
I will be happy to add any additional information.
Regards,
Lukasz

Did you update the nividia driver recently?
there are some threads on this

Gnome 3.14 problems with wayland

Similar Messages

Maybe you are looking for