not able to run any GTK Application after a tumbleweed update

English Install/Boot/Login
#1

I recently updated to OS 12.1 KDE 4.9.5 through Tumbleweed Repository ( to have okular updated )

Ever since, I am not able to run any GTK application. I run firefox and get the following error ;

/usr/lib/firefox/firefox: symbol lookup error: /usr/lib/libgdk-x11-2.0.so.0: undefined symbol: _XGetRequest

If I run evolution or evince, I get similar error again:

evince: symbol lookup error: /usr/lib/libgdk-3.so.0: undefined symbol: _XGetRequest

I have seen in Google search similar errors around

_XGetRequest
discussed, but none of the solutions suggested there have worked in my case. I have tried downgrading
libgtk
libraries to original distro version, but has not helped. Any idea?

Thanks in Advance.

#2

On 2013-03-08 20:16, pbhat wrote:
>
> I recently updated to OS 12.1 KDE 4.9.5 through Tumbleweed Repository (
> to have okular updated )

Then please ask in the Tumbleweed subforum. Please ask a moderator to
move your thread there.

–
Cheers / Saludos,

Carlos E. R.
(from 11.4, with Evergreen, x86_64 “Celadon” (Minas Tirith))

#3

CLOSED, will be moved to Tumbleweed.

#4

Moved from Applications and open again.

#5

On 2013-03-08 21:36, hcvv wrote:
>
> hcvv;2533096 Wrote:
>> CLOSED, will be moved to Tumbleweed.
> Moved from Applications and open again.

I just noticed something else - the OP said:

> I recently updated to OS 12.1 KDE 4.9.5 through Tumbleweed Repository (
> to have okular updated )

12.1? The current starting point for Tumbleweed is 12.2, you can not do
it from 12.1. First you have to upgrade to 12.2, then upgrade to
tumbleweed (via zypper dups all the way).

If you have a 12.1 and added “some” tumbleweed repo, then your system is
broken.

Notice that Tumbleweed is not simply a repository that you can add: it
is rather a different openSUSE version.

–
Cheers / Saludos,

Carlos E. R.
(from 11.4, with Evergreen, x86_64 “Celadon” (Minas Tirith))

#6

12.1? The current starting point for Tumbleweed is 12.2, you can not do
it from 12.1. First you have to upgrade to 12.2, then upgrade to
tumbleweed (via zypper dups all the way).

If you have a 12.1 and added “some” tumbleweed repo, then your system is
broken.

No, I have not done an UPDATE with some Tumbleweed repository, but I have done DUP after setting OSS,NON-OSS and UPDATE repos to current and adding Tumbleweed repository as explained in the portal for Tumbleweed for 12.1.

But after the DUP, my system still says it is Opensuse 12.1. But now I begin a DUP with zypper, it shows 'product to upgrade, openSUSE" not clear whether that is 12.2 or still 12.1. I declined after my terrific experience with last DUP.

My only repositories were (and are) before previous DUP run only on Monday, 04/03/2013, and I have done it on a 12.1 install.

linux-gv4m:~ # zypper lr# | Alias | Name | Enabled | Refresh
–±-------------------------±-------------------------±--------±-------
1 | Tumbleweed | Tumbleweed | Yes | Yes
2 | openSUSE Current OSS | openSUSE Current OSS | Yes | Yes
3 | openSUSE Current non-OSS | openSUSE Current non-OSS | Yes | Yes
4 | openSUSE Current updates | openSUSE Current updates | Yes | Yes
5 | packman | Packman_Tumbleweed | Yes | Yes

#7

You should not have started using Tumbleweed if you are not willing to “dup” ever so often.

Also post output of zypper lr -d in between “code” tags.

#8

On 2013-03-09 01:46, pbhat wrote:

> My only repositories were (and are) before previous DUP run only on
> Monday, 04/03/2013, and I have done it on a 12.1 install.

Please repost “zypper lr --details” and make sure it is posted inside a
code tag block. Advanced editor, ‘#’ button.
View this
thread for instructions

–
Cheers / Saludos,

Carlos E. R.
(from 11.4, with Evergreen, x86_64 “Celadon” (Minas Tirith))

#9

It is not being unwilling to do dup often, but immediate last dup left the bootloader broken, what with all grub entries removed, but no new entries for the new kernel, ‘mkinitrd’ compalining with PerlDev2UnixDev not finding a partition etc.,So, I do not want another immediate breakage if I can avoid.

Second, you are right I should not and would not be in Tumbleweed, though I know Linux not so bad. It was a calculated risk in the circumstances, knowing Linux never kills, though occssional fights and bruises happen.

My Repositories,

pappa@linux-gv4m:~>sudo zypper lr -droot's password:
# | Alias                   | Name                     | Enabled | Refresh | Priority | Type  | URI                                                                     | Service
--+--------------------------+--------------------------+---------+---------+----------+--------+--------------------------------------------------------------------------+--------
1 | Tumbleweed              | Tumbleweed               | Yes     | Yes     |   99     | rpm-md|http://download.opensuse.org/repositories/openSUSE:/Tumbleweed/standard/|        
2 | openSUSE Current OSS    | openSUSE Current OSS     | Yes     | Yes     |   99     | yast2 |http://download.opensuse.org/distribution/openSUSE-current/repo/oss/    |        
3 | openSUSE Currentnon-OSS | openSUSE Current non-OSS | Yes     | Yes     |   99     |yast2  |http://download.opensuse.org/distribution/openSUSE-current/repo/non-oss/|        
4 | openSUSE Currentupdates | openSUSE Current updates | Yes     | Yes     |   99     |rpm-md | http://download.opensuse.org/update/openSUSE-current/                   |        
5 | packman                 | Packman_Tumbleweed       | Yes     | Yes     |   99     | rpm-md| http://packman.inode.at/suse/openSUSE_Tumbleweed

I am just looking at the possibility of returning to working firefox, finish my current restoration task and then do next dup.

Thanks.

#10

You seem to be missing this

sudo zypper ar --refresh \ [Index of /update/openSUSE-non-oss-current](http://download.opensuse.org/update/openSUSE-non-oss-current/) \ 'openSUSE Current non-OSS updates'

source:- https://en.opensuse.org/Portal:Tumbleweed

It is not being unwilling to do dup often, but immediate last dup left the bootloader broken, what with all grub entries removed, but no new entries for the new kernel, ‘mkinitrd’ compalining with PerlDev2UnixDev not finding a partition etc.,So, I do not want another immediate breakage if I can avoid.

Are you using legacy version of grub ?

#11

You are right. I added it now, though I should think that would not cause any harm as I have no non-oss application.

What came with 12.1, that is Grub1. My last dup did not upgrade grub.

But the problem was grub devicemap file. Following does not work,

linux-gv4m:~ # cat /boot/grub/device.map.old2
(hd0)   /dev/disk/by-id/ata-ST980811AS_5LYAZFR1

wheraes the following will work

linux-gv4m:~ # cat /boot/grub/device.map.old(fd0)   /dev/fd0
(hd0)   /dev/sda

though they seem to mean the same thing. Anyways, that was fixed.

#12

I am providing here the update

I did a second ‘dup --from Tumbleweed’, it did not help the problem, though it did not break more.

While doing ‘dup --from Tumbleweed’, I had observed just ‘dup’ had a different list. So, after ‘dup --from Tumbleweed’ dried up, offering no more, I did a simple ‘dup’ which brought in another big set of changes and at the end, all gtk applications started functioning again.

Obviously, ‘current UPDATES’ holds newer packages than Tumbleweed itself. Also, till I did a plain ‘dup’ my product was not upgraded to OpenSuSE 12.2 (from 12.1). I carefully chose to do only ‘dup --from Tumbleweed’ as per the recommendation at https://en.opensuse.org/Portal:Tumbleweed. This is the second time that recommendation is tripping me.

Or,have I understood it wrong?

#13

I found that the page recommends “sudo zypper dup” and it recommends “sudo zypper dup --from Tumbleweed” only when you have other unofficial repos

#14

The result would still be same,right? Because the product upgrade itself is held “Current Updates”,not “Tumbleweed”.

Perhaps if you are doing regular ‘dup’, then ‘dup --from Tumbleweed’ will get you the updates which are tested. But when there is a product upgrade that has to happen, it is not there in Tumbleweed and ‘dup --from Tumbleweed’ actually breaks as in my case. The zypper itself is not able to distinguish between update and upgrade, it is not able to choose product upgrade over update when both are available in repos. OR it should have been at least able to offer choice of ‘UPDATE’ or ‘UPGRADE’.

I think Tumbleweed infrastructure and zypper have not taken this into account.