You are not logged in.

#1 2012-09-01 02:36:52

whaler
Member
From: Oslo, Norway
Registered: 2008-03-25
Posts: 324

[SOLVED]systemd installed - unable launch Opera, Google Chrome

I changed to 'pure' systemd yesterday and while e.g. Firefox and Thunderbird work as before, Opera and Google Chrome refuse to start. I also strongly suspect openntpd no longer syncs the system clock, but that's another story. I am using KDE.

I reinstalled Opera, but it didn't help, and I have no idea why these two apps will not launch when all other network apps seem to be okay. Any tips?

Last edited by whaler (2012-09-07 16:05:21)

Offline

#2 2012-09-01 04:47:04

Stebalien
Member
Registered: 2010-04-27
Posts: 1,239
Website

Re: [SOLVED]systemd installed - unable launch Opera, Google Chrome

What is the output when you run them on the command line?


Steven [ web : git ]
GPG:  327B 20CE 21EA 68CF A7748675 7C92 3221 5899 410C

Offline

#3 2012-09-01 07:20:18

whaler
Member
From: Oslo, Norway
Registered: 2008-03-25
Posts: 324

Re: [SOLVED]systemd installed - unable launch Opera, Google Chrome

I tried:

# /opt/google/chrome/chrome
/opt/google/chrome/chrome: error while loading shared libraries: libudev.so.0: cannot open shared object file: No such file or directory

Then

# locate libudev.so.0
/opt/google/chrome/libudev.so.0

Then I did:

# export PATH=$PATH:/opt/google/chrome

I then tried again:

# chrome
chrome: error while loading shared libraries: libudev.so.0: cannot open shared object file: No such file or directory

I then tried '# google-chrome', and was told I had to run it as user.

I did:

$ google-chrome
Avbrutt (SIGABRT)

'Avbrutt' means interrupted/broken.

I am at a loss (again)...

Offline

#4 2012-09-01 07:23:00

Awebb
Member
Registered: 2010-05-06
Posts: 6,688

Re: [SOLVED]systemd installed - unable launch Opera, Google Chrome

I bet one of the dependencies of chrome has had an update and your chrome is not built against it. Have you tried chromium? I haven't seen a real difference between chrome and chromium in the last few months.

What is Opera's output?

Offline

#5 2012-09-01 07:44:06

whaler
Member
From: Oslo, Norway
Registered: 2008-03-25
Posts: 324

Re: [SOLVED]systemd installed - unable launch Opera, Google Chrome

The reason I use google-chrome-dev is that it has flash built in and handles a few flash sites which Firefox has lost its grip on (www.aftenposten.no; www.nrk.no, among others).

The strange thing is that Opera and Google Chrome stopped working after my transition to systemd, while Firefox kept running as before...

After my first post I uninstalled Opera and uninstalled/reinstalled Google Chrome. The present Chrome may be a newer version, which conceivably may account for the error, but given that it is the same error as with the former installation, and also that my reinstallation of Opera yesterday gave the same result, I am starting to think that there is a problem elsewhere. E.g.: why did google-chrome-dev not register its own PATH when it was reinstalled?

Offline

#6 2012-09-01 09:46:45

whaler
Member
From: Oslo, Norway
Registered: 2008-03-25
Posts: 324

Re: [SOLVED]systemd installed - unable launch Opera, Google Chrome

I reinstalled Opera. It would not start from KDE GUI or user CLI, but trying it from root, I got this msg:

 # opera
Opera(1015)/kdeui (kdelibs): Session bus not found 
To circumvent this problem try the following command (with Linux and bash) 
export $(dbus-launch) 
KCrash: Application 'Kde4ToolkitLibrary' crashing...
KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit
sock_file=/root/.kde4/socket-Strev/kdeinit4__0
Warning: connect() failed: : Ingen slik fil eller filkatalog
KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi directly
drkonqi(1017)/kdeui (kdelibs): Session bus not found 
To circumvent this problem try the following command (with Linux and bash) 
export $(dbus-launch)

Issuing 'export $(dbus-launch)' made Opera start from root CLI, but from nowhere else.
Google Chrome will not start from anywhere, even with the PATH set.
BTW, I now have 3 dbus-daemons and 1 dbus-launch running...

So I reinstalled KDE in the hope of getting back the file 'kdeinit4__0', but no such luck.

If this is the missing file responsible, where can it be found and how may I get it back???

Offline

#7 2012-09-01 10:14:28

tomegun
Developer
From: France
Registered: 2010-05-28
Posts: 661

Re: [SOLVED]systemd installed - unable launch Opera, Google Chrome

Your chrome is built against an old udev/systemd release. You need to rebuild it against the most recent version (we are now on libudev.so.1, not .0).

Offline

#8 2012-09-01 10:55:54

Awebb
Member
Registered: 2010-05-06
Posts: 6,688

Re: [SOLVED]systemd installed - unable launch Opera, Google Chrome

I just tested Chrome as well as Opera on a systemd Arch, X started by xinit. They both worked. I only asked wether you had tried Chromium to see if it produces the same errors. It's up to you what you want to use ;-)

How do you start KDE? How do you start KDM?

Offline

#9 2012-09-01 10:58:41

whaler
Member
From: Oslo, Norway
Registered: 2008-03-25
Posts: 324

Re: [SOLVED]systemd installed - unable launch Opera, Google Chrome

tomegun wrote:

Your chrome is built against an old udev/systemd release. You need to rebuild it against the most recent version (we are now on libudev.so.1, not .0).

It was reinstalled from AUR today, and I find the following libudev files on my system: /usr/lib/libudev.so.1,
/usr/lib/libudev.so.1.1.0. However, Dolphin does not start from root CLI either, as it used to under sysvinit, nor does Opera. BTW, I *do* have the 'kdeinit4__0' file (0 bytes), but 'locate' does not find it. Of course it doesn't.

But why does KDE report this:

KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit
sock_file=/root/.kde4/socket-Strev/kdeinit4__0
Warning: connect() failed: : No such file or directory

Offline

#10 2012-09-02 18:11:42

whaler
Member
From: Oslo, Norway
Registered: 2008-03-25
Posts: 324

Re: [SOLVED]systemd installed - unable launch Opera, Google Chrome

I may have come closer to the problem, but I don't know how to proceed:

Since 2009 /root/.kde4/socket-Strev and /root/.kde4/tmp-Strev
have been symlinked to /tmp/ksocket-root and /tmp/kde-root, respectively.
They still are.
However, /tmp/ksocket-root and /tmp/kde-root no longer exist and seem
to have been replaced by /tmp/ksocket-pelagos og /tmp/kde-pelagos.
IOW, systemd seems to have changed 'targets' from root to user,
making /root/.kde4/socket-Strev and /root/.kde4/tmp-Strev point to files
which no longer exist.

Is this change correct, or is it caused by an error in the system or by myself?
Can I just alter the symlinks manually, or is this something that must be done
by the system, in which case, how do I initiate that?

All guidance much appreciated!

Offline

#11 2012-09-07 16:04:30

whaler
Member
From: Oslo, Norway
Registered: 2008-03-25
Posts: 324

Re: [SOLVED]systemd installed - unable launch Opera, Google Chrome

Thanks to amckee
https://bbs.archlinux.org/viewtopic.php?id=148509
for this:

find -type d -iname "*chrom*" -exec ls -ld {} \;

which prompted me to have a go again. Much appreciated.

Meanwhile a number of apps have been upgraded and I have tried to improve my systemd configuration, so not sure what solved it, but Opera and Google Chrome now launch and work impeccably.

Offline

#12 2012-09-28 02:31:57

caerolle
Member
Registered: 2012-09-28
Posts: 19

Re: [SOLVED]systemd installed - unable launch Opera, Google Chrome

I am having this same trouble with Chromium, Sorry, but I don't understand how you fixed it? Could you give a bit of explanation? Thanks!  smile

Offline

Board footer

Powered by FluxBB