Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
udev-197 + chromium + html5 bugs
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
John5788
Advocate
Advocate


Joined: 06 Apr 2004
Posts: 2099
Location: 127.0.0.1

PostPosted: Sun Jan 27, 2013 6:45 am    Post subject: udev-197 + chromium + html5 bugs Reply with quote

Hello,

I just did the update to udev197-r3 as the system update goes. Everything seemed to work smoothly, but I am noticing that anything html5 with chromium causes instability. I am not 100% sure this is related to the udev update, but what I did notice is chromium failing to run on reboot. It asked me to `chmod 1777 /dev/shm`. After completing this command, chromium then started working.

I can easily reproduce the crash, just play any html5 video on YouTube and the browser crashes. Sometimes I get this message:

Code:

NVIDIA: could not open the device file /dev/nvidia0 (Operation not permitted).
NVIDIA: could not open the device file /dev/nvidia0 (Operation not permitted).
NVIDIA: could not open the device file /dev/nvidia0 (Operation not permitted).


However, OpenGL games and glxgears seem to be working just fine. I'm not really sure what is going on. Any help?

List of packages installed with udev:

Code:
Fri Jan 25 20:49:41 2013 >>> dev-python/python-exec-0.2
     Fri Jan 25 20:49:45 2013 >>> sys-power/acpid-2.0.17-r1
     Fri Jan 25 20:49:52 2013 >>> sys-fs/dosfstools-3.0.13
     Fri Jan 25 20:50:07 2013 >>> media-libs/freetype-2.4.11
     Fri Jan 25 20:50:23 2013 >>> dev-libs/nspr-4.9.4
     Fri Jan 25 20:51:57 2013 >>> dev-libs/nss-3.14.1
     Fri Jan 25 21:07:50 2013 >>> sys-devel/gcc-4.6.3
     Fri Jan 25 21:08:08 2013 >>> media-libs/taglib-1.8-r1
     Fri Jan 25 21:08:16 2013 >>> dev-java/java-config-2.1.12-r1
     Fri Jan 25 21:08:27 2013 >>> sys-apps/kmod-12-r1
     Fri Jan 25 21:08:37 2013 >>> media-libs/glew-1.9.0
     Fri Jan 25 21:29:51 2013 >>> www-client/firefox-17.0.2
     Fri Jan 25 21:30:15 2013 >>> sys-auth/polkit-0.110
     Fri Jan 25 21:30:41 2013 >>> sys-fs/udev-197-r3
     Fri Jan 25 21:30:44 2013 >>> virtual/udev-197
     Fri Jan 25 21:30:49 2013 >>> sys-fs/udev-init-scripts-19-r1
     Fri Jan 25 22:11:29 2013 >>> www-client/chromium-24.0.1312.56
     Fri Jan 25 22:11:48 2013 >>> sys-power/upower-0.9.19
     Fri Jan 25 22:12:04 2013 >>> sys-fs/udisks-1.0.4-r4
     Fri Jan 25 23:26:57 2013 >>> media-libs/mesa-9.0.1
     Fri Jan 25 23:27:35 2013 >>> sys-apps/util-linux-2.21.2
     Fri Jan 25 23:28:49 2013 >>> x11-base/xorg-server-1.13.1
     Fri Jan 25 23:29:00 2013 >>> dev-libs/libatasmart-0.19
     Fri Jan 25 23:29:29 2013 >>> sys-fs/lvm2-2.02.97-r1
     Fri Jan 25 23:29:41 2013 >>> x11-drivers/xf86-input-evdev-2.7.3
     Fri Jan 25 23:30:40 2013 >>> media-sound/pulseaudio-2.1-r1
     Fri Jan 25 23:31:00 2013 >>> sys-auth/consolekit-0.4.5_p20120320-r1
     Fri Jan 25 23:31:23 2013 >>> media-libs/libcanberra-0.29
     Fri Jan 25 23:31:51 2013 >>> gnome-base/gvfs-1.12.3

_________________
John5788
Back to top
View user's profile Send private message
John5788
Advocate
Advocate


Joined: 06 Apr 2004
Posts: 2099
Location: 127.0.0.1

PostPosted: Sun Jan 27, 2013 6:54 am    Post subject: Reply with quote

Managed to get some more error messages out:

Code:

[10600:10623:0126/225341:ERROR:bus.cc(307)] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[10600:10623:0126/225341:ERROR:power_save_blocker_linux.cc(253)] No response to Inhibit() request!
[10600:10623:0126/225344:ERROR:bus.cc(307)] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[10600:10623:0126/225344:ERROR:power_save_blocker_linux.cc(289)] No response to Uninhibit() request!


This is while running chromium as root. Any help on this would be appreciated
_________________
John5788
Back to top
View user's profile Send private message
ssuominen
Developer
Developer


Joined: 30 Sep 2005
Posts: 2131
Location: Finland

PostPosted: Sun Jan 27, 2013 7:38 am    Post subject: Reply with quote

Are you sure you didn't hit http://bugs.gentoo.org/451128?

You need at least >=sec-policy/selinux-base-2.20120725-r10, see ChangeLog of selinux-base saying:

Quote:

16 Jan 2013; Sven Vermeulen <swift@gentoo.org>
selinux-base-2.20120725-r10.ebuild:
Stabilizing

*selinux-base-2.20120725-r10 (16 Jan 2013)

16 Jan 2013; Sven Vermeulen <swift@gentoo.org>
+selinux-base-2.20120725-r10.ebuild:
Bumping with fix for #451128


I've made udev's ebuild block older versions than -r10 just to be sure nobody hits bug 421128 again.

Do you have /dev/shm in /etc/fstab, and if you do, then why? I don't recommend having such line there. Works here fine without one, as you can see:

Code:

$ mount |grep shm
shm on /dev/shm type tmpfs (rw,nosuid,nodev,noexec,relatime)
Back to top
View user's profile Send private message
ssuominen
Developer
Developer


Joined: 30 Sep 2005
Posts: 2131
Location: Finland

PostPosted: Sun Jan 27, 2013 7:48 am    Post subject: Re: udev-197 + chromium + html5 bugs Reply with quote

John5788 wrote:
Code:
NVIDIA: could not open the device file /dev/nvidia0 (Operation not permitted).


Are you sure you are in the 'video' group?

Code:

$ ls -ld /dev/nvidia*
crw-rw---- 1 root video 195,   0 Jan 21 14:17 /dev/nvidia0
crw-rw---- 1 root video 195, 255 Jan 21 14:17 /dev/nvidiactl
$ id
uid=1000(ssuominen) gid=1000(ssuominen) groups=1000(ssuominen),10(wheel),11(floppy),18(audio),19(cdrom),27(video),35(games),80(cdrw),85(usb),100(users),250(portage)
Back to top
View user's profile Send private message
John5788
Advocate
Advocate


Joined: 06 Apr 2004
Posts: 2099
Location: 127.0.0.1

PostPosted: Sun Jan 27, 2013 8:15 am    Post subject: Reply with quote

I don't even have selinux-base emerged on my system. Should I have it?

ssuominen wrote:
Do you have /dev/shm in /etc/fstab, and if you do, then why? I don't recommend having such line there. Works here fine without one, as you can see:


Not sure why I have this. Then again, my install of this system was done in 2010, might have just been an old configuration.

Code:
$ cat /etc/fstab | grep shm
# glibc 2.2 and above expects tmpfs to be mounted at /dev/shm for
# POSIX shared memory (shm_open, shm_unlink).
shm         /dev/shm   devtmpfs        nodev,nosuid,noexec   0 0



Code:
$ ls -ld /dev/nvidia*
crw-rw---- 1 root video 195,   0 Jan 26 14:31 /dev/nvidia0
crw-rw---- 1 root video 195, 255 Jan 26 14:31 /dev/nvidiactl

$ id
uid=1000(john5788) gid=1000(john5788) groups=1000(john5788),10(wheel),18(audio),19(cdrom),27(video),35(games),85(usb),100(users),102(vboxusers),103(android),193(plugdev),250(portage),997(wireshark)

_________________
John5788
Back to top
View user's profile Send private message
ssuominen
Developer
Developer


Joined: 30 Sep 2005
Posts: 2131
Location: Finland

PostPosted: Sun Jan 27, 2013 8:46 am    Post subject: Reply with quote

John5788 wrote:
I don't even have selinux-base emerged on my system. Should I have it?


It's the one setting the required permission for udev on selinux systems, so I'd assume so. I don't use selinux myself, but that particular bug I was referring to was in fact
marked as a "blocker" for the udev stabilization. Since it's now marked resolved and is in stable, the case is closed.

So your system is configured for selinux or did you just slap "selinux" in USE of make.conf and selected some selinux profile using 'eselect profile list (eselect profile set...) or what...
If so, I guess now would be a good time to upgrade the selinux related packages.
Back to top
View user's profile Send private message
John5788
Advocate
Advocate


Joined: 06 Apr 2004
Posts: 2099
Location: 127.0.0.1

PostPosted: Mon Jan 28, 2013 8:07 am    Post subject: Reply with quote

ssuominen wrote:
John5788 wrote:
I don't even have selinux-base emerged on my system. Should I have it?


It's the one setting the required permission for udev on selinux systems, so I'd assume so. I don't use selinux myself, but that particular bug I was referring to was in fact
marked as a "blocker" for the udev stabilization. Since it's now marked resolved and is in stable, the case is closed.

So your system is configured for selinux or did you just slap "selinux" in USE of make.conf and selected some selinux profile using 'eselect profile list (eselect profile set...) or what...
If so, I guess now would be a good time to upgrade the selinux related packages.


I've never configured my system for selinux. I don't think that bug applies to me. I don't boot my system with an enforcing mode. Is there something in my post that clues you to selinux?
_________________
John5788
Back to top
View user's profile Send private message
ssuominen
Developer
Developer


Joined: 30 Sep 2005
Posts: 2131
Location: Finland

PostPosted: Mon Jan 28, 2013 8:14 am    Post subject: Reply with quote

John5788 wrote:
ssuominen wrote:
John5788 wrote:
I don't even have selinux-base emerged on my system. Should I have it?


It's the one setting the required permission for udev on selinux systems, so I'd assume so. I don't use selinux myself, but that particular bug I was referring to was in fact
marked as a "blocker" for the udev stabilization. Since it's now marked resolved and is in stable, the case is closed.

So your system is configured for selinux or did you just slap "selinux" in USE of make.conf and selected some selinux profile using 'eselect profile list (eselect profile set...) or what...
If so, I guess now would be a good time to upgrade the selinux related packages.


I've never configured my system for selinux. I don't think that bug applies to me. I don't boot my system with an enforcing mode. Is there something in my post that clues you to selinux?


I might have misread or understood the earlier comment about "... security policy blocked the reply...", sorry about that.

Are dbus and consolekit in the runlevels to ensure they start early enough?

Code:

# rc-update show


How do you start your desktop? Display manager? startx? What's in .xsession or .xinitrc?`I'm asking because you might be missing the user dbus session entirely, or it might have started too late.

Does the workaround of `dbus-launch chromium` (or whatever the binary for chromium is called) help when launched from terminal?

Do you have /dev/shm in /etc/fstab? If so, then remove it because the defaults should be already fine and set 1777 long as fstab doesn't get in the way.
Back to top
View user's profile Send private message
lostpaperclips
n00b
n00b


Joined: 19 Jun 2011
Posts: 9
Location: United States

PostPosted: Tue Jan 29, 2013 7:45 am    Post subject: Reply with quote

Quote:
Does the workaround of `dbus-launch chromium` (or whatever the binary for chromium is called) help when launched from terminal?


Quote:
Do you have /dev/shm in /etc/fstab? If so, then remove it because the defaults should be already fine and set 1777 long as fstab doesn't get in the way.


I am experiencing a similar problem and the above suggestions have not helped. :( BTW: Right now the best site that I have to replicate the problem is Google+. Below is the terminal output from chromium. I wonder, has anyone seen the last line about the 'GPU hang' on there box?

Code:
user@host ~ $ chromium
[3692:3726:0128/230545:ERROR:object_proxy.cc(608)] Failed to get name owner. Got org.freedesktop.DBus.Error.NameHasNoOwner: Could not get owner of name 'org.freedesktop.NetworkManager': no such name
[3692:3758:0128/230550:ERROR:object_proxy.cc(608)] Failed to get name owner. Got org.freedesktop.DBus.Error.NameHasNoOwner: Could not get owner of name 'org.chromium.Mtpd': no such name
[3692:3758:0128/230550:ERROR:object_proxy.cc(608)] Failed to get name owner. Got org.freedesktop.DBus.Error.NameHasNoOwner: Could not get owner of name 'org.chromium.Mtpd': no such name
[3692:3692:0128/230554:ERROR:object_proxy.cc(513)] Failed to call method: org.chromium.Mtpd.EnumerateStorage: object_path= /org/chromium/Mtpd: org.freedesktop.DBus.Error.ServiceUnknown: The name org.chromium.Mtpd was not provided by any .service files
[3692:3753:0128/230555:ERROR:object_proxy.cc(513)] Failed to call method: org.kde.KWallet.isEnabled: object_path= /modules/kwalletd: org.freedesktop.DBus.Error.ServiceUnknown: The name org.kde.kwalletd was not provided by any .service files
[3692:3753:0128/230555:ERROR:native_backend_kwallet_x.cc(227)] Error contacting kwalletd (isEnabled)
No bp log location saved, using default.
[000:000] Browser XEmbed support present: 1
[000:000] Browser toolkit is Gtk2.
[000:000] Using Gtk2 toolkit
[000:010] Starting client channel.
[000:010] Warning(clientchannel.cc:435): Unreadable or no port file.  Could not initiate GoogleTalkPlugin connection
[000:011] Warning(clientchannel.cc:410): Could not initiate GoogleTalkPlugin connection
[000:011] GoogleTalkPlugin not running. Starting new process...
[000:011] Warning(pluginutils.cc:268): Failed to get GoogleTalkPlugin path. Trying default.
[000:012] Started GoogleTalkPlugin, path=/opt/google/talkplugin/GoogleTalkPlugin
[000:012] Waiting for GoogleTalkPlugin to start...
[001:107] Attempting to connect to GoogleTalkPlugin...
[001:107] Warning(clientchannel.cc:435): Unreadable or no port file.  Could not initiate GoogleTalkPlugin connection
[001:107] Warning(clientchannel.cc:410): Could not initiate GoogleTalkPlugin connection
[001:107] Waiting for GoogleTalkPlugin to start...
[002:109] Attempting to connect to GoogleTalkPlugin...
[002:109] Read port file, port=57518
[002:109] Initiated connection to GoogleTalkPlugin
[002:109] Socket connection established
[002:109] ScheduleOnlineCheck: Online check in 5000ms
[002:210] Got cookie response, socket is authorized
[002:210] AUTHORIZED; socket handshake complete
[007:118] HandleOnlineCheck: Starting check
[007:118] HandleOnlineCheck: OK; current state: 3
[3951:4000:0129/072628:ERROR:gpu_watchdog_thread.cc(201)] The GPU process hung. Terminating after 10000 ms.
Back to top
View user's profile Send private message
John5788
Advocate
Advocate


Joined: 06 Apr 2004
Posts: 2099
Location: 127.0.0.1

PostPosted: Tue Jan 29, 2013 7:55 am    Post subject: Reply with quote

ssuominen wrote:

I might have misread or understood the earlier comment about "... security policy blocked the reply...", sorry about that.

Are dbus and consolekit in the runlevels to ensure they start early enough?

Code:

# rc-update show


How do you start your desktop? Display manager? startx? What's in .xsession or .xinitrc?`I'm asking because you might be missing the user dbus session entirely, or it might have started too late.

Does the workaround of `dbus-launch chromium` (or whatever the binary for chromium is called) help when launched from terminal?

Do you have /dev/shm in /etc/fstab? If so, then remove it because the defaults should be already fine and set 1777 long as fstab doesn't get in the way.


Code:
# rc-update show
            alsasound | boot                                         
             bootmisc | boot                                         
          consolefont | boot                                         
                cupsd |      default                                 
                 dbus |      default                                 
                devfs |                                        sysinit
        device-mapper | boot                                         
                dmesg |                                        sysinit
                 fsck | boot                                         
             hostname | boot                                         
              hwclock | boot                                         
              keymaps | boot                                         
            killprocs |                        shutdown               
           lm_sensors |      default                                 
                local |      default nonetwork                       
           localmount | boot                                         
                  lvm | boot                                         
              modules | boot                                         
             mount-ro |                        shutdown               
                 mtab | boot                                         
             net.eth0 |      default                                 
               net.lo | boot                                         
             netmount |      default                                 
              numlock |      default                                 
               procfs | boot                                         
                rdate |      default                                 
                 root | boot                                         
            savecache |                        shutdown               
                 sshd |      default                                 
                 swap | boot                                         
            swapfiles | boot                                         
               sysctl | boot                                         
                sysfs |                                        sysinit
            syslog-ng |      default                                 
         termencoding | boot                                         
       tmpfiles.setup | boot                                         
                 udev |                                        sysinit
           udev-mount |                                        sysinit
              urandom | boot                                         
           vixie-cron |      default                                 
                  xdm |      default 


No consolekit here. Should dbus be at boot level or is default ok?

I use SLiM for a login manager with xfce4. Nothing special here:

Code:
$ cat /etc/slim.conf | grep sessiondir
sessiondir           /etc/X11/Sessions

$ cat /etc/X11/Sessions/Xfce4
startxfce4


Launching chromium with dbus-launcher doesn't solve the problem. I've removed /dev/shm from fstab, but I haven't rebooted my system yet.

I'm at least glad to see I'm not the only one with this problem now.
_________________
John5788
Back to top
View user's profile Send private message
ssuominen
Developer
Developer


Joined: 30 Sep 2005
Posts: 2131
Location: Finland

PostPosted: Tue Jan 29, 2013 2:33 pm    Post subject: Reply with quote

John5788 wrote:
I've removed /dev/shm from fstab, but I haven't rebooted my system yet. I'm at least glad to see I'm not the only one with this problem now.


I've so far heard it fixed issues for four users, one of them had issues specifically with chromium. Let me know.
In doubt, you can `emerge strace` and then strace it... you might, possibly, see it can't access /dev/shm.
Back to top
View user's profile Send private message
houqp
n00b
n00b


Joined: 22 Feb 2011
Posts: 28
Location: China

PostPosted: Tue Feb 05, 2013 5:47 am    Post subject: Reply with quote

removing /dev/shm works for me, thanks!
Back to top
View user's profile Send private message
lostpaperclips
n00b
n00b


Joined: 19 Jun 2011
Posts: 9
Location: United States

PostPosted: Tue Feb 05, 2013 8:09 am    Post subject: Reply with quote

It would appear that my problem was actually a kernel configuration as I have the ati-drivers installed and had (mistakenly) enabled DRM. Disabling it and re-compiling the kernel solved my issue.
Back to top
View user's profile Send private message
monsm
Guru
Guru


Joined: 26 Sep 2007
Posts: 463
Location: London, UK

PostPosted: Sat Feb 16, 2013 3:15 pm    Post subject: Reply with quote

houqp wrote:
removing /dev/shm works for me, thanks!


++

Had the same problem on Google Chrome v.24 and this worked for me too :D
Thanks again.

Mons
Back to top
View user's profile Send private message
darkphader
Veteran
Veteran


Joined: 09 May 2002
Posts: 1135
Location: Motown

PostPosted: Wed Jun 19, 2013 10:17 pm    Post subject: Reply with quote

I have this problem but no /dev/shm in fstab.

Both consolekit and dbus start in default.

I boot to terminal and then start KDE with startx. The .xinitrc contains:
Code:
exec ck-launch-session startkde

_________________
What I need is an exact list of specific unknown problems we might encounter.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Desktop Environments All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum