I performed a routine update via YaST2’s Software Management yesterday (2 August), and after rebooting, I tried to log in but I keep getting sent back to the login screen. I use lxdm, but gdm (and possibly every other DM) also fail to log me in.
Below is my .xsession-errors file:
/etc/X11/xim: Checking whether an input method should be started.
/etc/profile.d/xdg-environment.sh:24: no matches found: /etc/opt/*/share
sourcing /etc/sysconfig/language to get the value of INPUT_METHOD
INPUT_METHOD is not set or empty (no user selected input method).
Trying to start a default input method for the locale en_GB.UTF-8 ...
Checking for a default input method in /etc/X11/xim.d/en/
sourcing /etc/X11/xim.d/en/49-scim-bridge ...
Smart Common Input Method 1.4.7
Launching a SCIM daemon with Socket FrontEnd...
Loading simple Config module ...
Creating backend ...
Loading socket FrontEnd module ...
Starting SCIM as daemon ...
Launching a SCIM process with x11...
Loading socket Config module ...
Creating backend ...
Loading x11 FrontEnd module ...
GTK Panel of SCIM 1.4.7
Starting SCIM as daemon ...
SCIM has been successfully launched.
/etc/X11/xim.d/en/49-scim-bridge started sucessfully
/usr/bin/gpg-agent: relocation error: /usr/bin/gpg-agent: symbol __assuan_socket, version LIBASSUAN_1.0 not defined in file libassuan.so.0 with link time reference
I believe that gpg2 was part of that update, to say the least. aaa_base was definitely updated, so I suspect that can be a cause?
Glad I’m not alone with this problem. I thought it might be a KDE 4.7 repo issue, but it looks as if the not-so-official KDE 4.7 repos are not the culprit.
On 04.08.2011 07:06, Larx wrote:
>
> Larx;2371288 Wrote:
>> And which package is the culprit?
>
> In reply to myself: Downgrading all gpg-related packages solves the
> problem.
>
>
I can confirm that.
It’s those or one/some of those.
Vahis
http://waxborg.servepics.com
openSUSE 11.2 (x86_64) 2.6.31.14-0.8-default “Evergreen” main host
openSUSE 11.4 (x86_64) 2.6.37.6-0.5-desktop in VirtualBox
openSUSE 11.4 (i586) 3.0.0-39-desktop “Tumbleweed” in EeePC 900
The main package of interest transited as follows, only upgrades,
30-Jul-2011 mkinitrd-2.7.0-25.1.x86_64
02-Aug-2011 mkinitrd-2.7.0-27.1.x86_64
03-Aug-2011 mkinitrd-2.7.0-31.1.x86_64
The gpg packages, only upgrades,
30-Jul-2011 gpg2-2.0.17-6.1.x86_64 gpg2-lang-2.0.17-6.1.noarch gpgme-1.3.0-18.1.x86_64
03-Aug-2011 gpg2-2.0.17-6.2.x86_64 gpg2-lang-2.0.17-6.2.noarch gpgme-1.3.1-18.1.x86_64
On 04.08.2011 12:46, keellambert wrote:
>
> My observations are as follows,
>
> The main package of interest transited as follows, only upgrades,
> 30-Jul-2011 mkinitrd-2.7.0-25.1.x86_64
> 02-Aug-2011 mkinitrd-2.7.0-27.1.x86_64
> 03-Aug-2011 mkinitrd-2.7.0-31.1.x86_64
>
> The gpg packages, only upgrades,
> 30-Jul-2011 gpg2-2.0.17-6.1.x86_64 gpg2-lang-2.0.17-6.1.noarch
> gpgme-1.3.0-18.1.x86_64
> 03-Aug-2011 gpg2-2.0.17-6.2.x86_64 gpg2-lang-2.0.17-6.2.noarch
> gpgme-1.3.1-18.1.x86_64
>
>
The gpg packages need the libassuan package from tumbleweed repo.
When all those are up to date everything works here.
Vahis
http://waxborg.servepics.com
openSUSE 11.2 (x86_64) 2.6.31.14-0.8-default “Evergreen” main host
openSUSE 11.4 (x86_64) 2.6.37.6-0.5-desktop in VirtualBox
openSUSE 11.4 (i586) 3.0.0-39-desktop “Tumbleweed” in EeePC 900
The gpg packages need the libassuan package from tumbleweed repo.
When all those are up to date everything works here.
Isn’t that what dependencies are for?
Which leads me to a question: Using graphical YaST sw management, I don’t even notice if a package which I have still installed from 11.4 OSS is available in a updated version in Tumbleweed, although Tumbleweed has a higher priority. So in this case, I would not even have noticed that a newer libassuan is available in Tumbleweed.
Yes, I have switched the system packages to Tumbleweed, but this only goes for those packages which where in Tumbleweed at that, long past, moment. Why won’t YaST tell me when new and updated packages are available in a preferred repository? Or am I doing something wrong?
On 04.08.2011 19:46, Larx wrote:
>
>>
>> The gpg packages need the libassuan package from tumbleweed repo.
>> When all those are up to date everything works here.
>>
>
> Isn’t that what dependencies are for?
>
> Which leads me to a question: Using graphical YaST sw management, I
> don’t even notice if a package which I have still installed from 11.4
> OSS is available in a updated version in Tumbleweed, although Tumbleweed
> has a higher priority. So in this case, I would not even have noticed
> that a newer libassuan is available in Tumbleweed.
> Yes, I have switched the system packages to Tumbleweed, but this only
> goes for those packages which where in Tumbleweed at that, long past,
> moment. Why won’t YaST tell me when new and updated packages are
> available in a preferred repository? Or am I doing something wrong?
>
>
I’m not sure what happened (here).
I assume that I happened to update at a moment where the older libassuan
was not yet replaced in the repo.
It is a dependency, yes, but it seems that the others get installed even
with the older libassuan.
But I’m not sure, really don’t know, but this is a rare case.
I can’t say never before but I haven’t seen many like this one before.
Vahis
http://waxborg.servepics.com
openSUSE 11.2 (x86_64) 2.6.31.14-0.8-default “Evergreen” main host
openSUSE 11.4 (x86_64) 2.6.37.6-0.5-desktop in VirtualBox
openSUSE 11.4 (i586) 3.0.0-39-desktop “Tumbleweed” in EeePC 900
– http://waxborg.servepics.com
openSUSE 11.2 (x86_64) 2.6.31.14-0.8-default “Evergreen” main host
openSUSE 11.4 (x86_64) 2.6.37.6-0.7-desktop in VirtualBox
openSUSE 11.4 (i586) 3.0.0-39-desktop “Tumbleweed” in EeePC 900
I had the very same issue today. I can confirm that gpg2-2.0.17-6.2.x86_64.rpm from the Tumbleweed repo caused my problem. Downgrading it to gpg2-2.0.16-7.1.x86_64.rpm from the standard OpenSUSE 11.4 repo fixed it.
However, my installed version of libassuan is 2.0.1-4.1 from the standard repo, while 2.0.2-4.1 is available from Tumbleweed (Why was it not selected along with the other Tumbleweed updates ?). I’m gonna update libassuan then gpg2 again from Tumbleweed and see if it does any good.
EDIT :
Yup, that did it !
Make sure that gpg2 and libassuan come from the same repo.
I’m having trouble doing this from the console. Using yast2, I gave the Tumbleweed repo a priority 97 and forced an update. It did not fix the problem. In the gui, I can see (and change) which versions are selected. Can’t figure that out from the console.
