Plasma desktop crashes

Hello everyone.

I’m running OpenSUSE 11.4 (i586) with KDE Desktop 4.6.0 “release 6” on my IBM ThinPad X40. And I have trouble with getting new plasma widgets by internet. To be more concrete, every time I try to install new widget (first I want to view details of that), so when I’m pushing on blue button called “Details”, BOOM and my plasma desktop crashes and after refreshing it generates the dump file for reporting to developers.

As this is quite an annoying bug, I’ve decided to report it, so I’ve installed all the necessary debugging tools, generated the complete bug report and sent it to KDE team. After this, I’ve got mail with link on KDE bug tracking system and found a lot of people being in the same trouble. So, one guy - Dario Andres (I think he’s from KDE team) says: “The bug and the fix are in “libattica”, may be your version of that library is not the latest. (or there wasn’t a release including the fix)” and though after his comment there’s a dozen of other replies with the same problem, all of them are marked as the duplicated bug and has no answer.

Well, even I know that my operating system is always up to dated, anyway I’ve checked that library version on my computer:

giorgi@linux-oary:~> rpm -qa|grep libattica

And I’ve double checked on the Internet and this is the latest version of this library. So, it’s obvious that this BUG 261530 has not solved by this library.

I understand, maybe it’ll be better to post this thread on KDE’s forum, but I have an excellent experience of solving my problems on this forum, so I decided to ask you first, maybe you already know the solution?

Thanks in advance and sorry for a big post.

Hi vojd.

Lets have a look at your configured repos

zypper lr -d

Later versions of libattica0 do exist, but only for those who have Index of /repositories/KDE:/Release:/46/openSUSE_11.4 present and enabled for example. With your posted repo configuration, it will be possible for someone to advise on updating to KDE4.6.X…

Hi deano_ferrari,

Thanks for quick reply. I don’t quite understand what do you mean, I really do not have that repo added in my repository list, but it should happen? As I know Novell and hence Suse community cooperates with KDE team very closely, so I think OpenSUSE official repository should provide all the updates and bug fixes from KDE, shouldn’t they?

O.K. As I’m really new to Linux community (I’ll say I’ve just only user experience in Linux operating system), maybe I don’t understand something. As for my repository list, I decided to take a snapshot of my YaST Configuration, rather then paste console output.

I’m unable to insert picture updated on Picasa, maybe it’s problem of protocol, Picasa web share uses https. O.K. I’ll upload somewhere else and put the link.

maybe I’ll insert the direct link, as when I was trying to insert picture and in pop-up windows I’ve put the link to it, you can see in my previous post, that there’s a blank space, where it should appear my snapshot.

Next time, just cut and paste the output (and use code tags to insert the output in to make it easier to read).

Read this SDB:KDE_upgrade guide. In particular, the ‘Upgrade to Latest Release from Upstream KDE’ section.

zypper ar -f KDE46
zypper dup --from KDE46

See how that goes.

O.K. I’ll try this way, I just afraid that this unsupported and barely tested repository may bring other bugs with it. Anyway, I’ll try to update only that library, if it’ll be possible.

By the way, I didn’t know that method of inserting the console output, I’ll just try to see if I’m doing the right way.

giorgi@linux-oary:~> zypper lr -d
#  | Alias                            | Name                             | Enabled | Refresh | Priority | Type   | URI                                                                       | Service
 1 | DVD                              | DVD                              | No      | No      |   99     | rpm-md |                                      |        
 2 | KDE_-_Updated_applications_only  | KDE - Updated applications only  | No      | No      |   99     | rpm-md | |        
 3 | Kernel_stable                    | Kernel stable                    | Yes     | Yes     |   99     | rpm-md |        |        
 4 | Packman_all_software             | Packman all software             | Yes     | Yes     |   99     | rpm-md |                                |        
 5 | Updates-for-openSUSE-11.4-11.4-0 | Updates for openSUSE 11.4 11.4-0 | Yes     | Yes     |   99     | rpm-md |                                 |        
 6 | games                            | games                            | Yes     | Yes     |   99     | rpm-md |            |        
 7 | google-chrome                    | google-chrome                    | No      | No      |   99     | rpm-md |                         |        
 8 | j.eng                            | j.eng                            | No      | No      |   99     | rpm-md |                                     |        
 9 | openSUSE-11.4-11.4-0             | openSUSE-11.4-11.4-0             | No      | No      |   99     | yast2  | cd:///?devices=/dev/disk/by-id/ata-UJDA765_DVD_CDRW,/dev/sr0              |        
10 | repo-debug                       | openSUSE-11.4-Debug              | No      | No      |   99     | yast2  |            |        
11 | repo-debug-update                | openSUSE-11.4-Update-Debug       | No      | No      |   99     | rpm-md |                           |        
12 | repo-non-oss                     | openSUSE-11.4-Non-Oss            | Yes     | Yes     |   99     | yast2  |              |        
13 | repo-oss                         | openSUSE-11.4-Oss                | Yes     | Yes     |   99     | yast2  |                  |        
14 | repo-source                      | openSUSE-11.4-Source             | No      | No      |   99     | yast2  |           |        

O.K. I’ll try this way, I just afraid that this unsupported and barely tested repository may bring other bugs with it. Anyway, I’ll try to update only that library, if it’ll be possible.

I have 11.4 installed, but with KDE4.6.2 (from KDE Factory) without issue to date, so you should be ok.

As you mention, if you want to be conservative, you could just try updating that library, (although it might drag in a few other updates too), then disable the repo again.