Hello, I use Mageia release 1 (Official) for x86_64 and Kernel 2.6.38.7-desktop-1.mga on a Dual-processor x86_64. I noticed, since the transition to KDE 4.6.5, a regression with superkaramba: I use four widgets, and every time you restart the PC ,there are Widgets that do not respect their original location. In the folder "~ /. Superkaramba" I edited the four files with the exact dimensions so that Widgets can respect this.But nothing to do at each reboot some widgets have not respected their location. By cons, once Widgets displayed, you have to right click on the Widget ->> Reload this theme<<- to install the widget in the right place. It is embarrassing having to re-handling at each reboot. I attached a screenshot with well placed Widgets and another with the widgets not properly placed. I can confirm with version of kde 4.6.3 there had not this problem. Each time you start the PC, the Widgets have respected their original location. $ kde4-config --version Qt : 4.7.3 Plate-forme de développement de KDE : 4.6.5 (4.6.5) kde4-config : 1.0 $ rpm -qa | grep superkaramba superkaramba-4.6.5-0.1.mga1 lib64superkaramba4-4.6.5-0.1.mga1
Created attachment 804 [details] Good location Widgets
Created attachment 805 [details] Poor location of Widgets
Source RPM: (none) => kdeutils4-4.6.5-0.1.mga1.src.rpm
Assignee: bugsquad => balcaen.john
Did you already try this? (from http://docs.kde.org/stable/en/kdeutils/superkaramba/faq/faq.txt): 3.2. My themes start up in different locations when I start KDE. Close all superkaramba themes and then delete any session files in ~/.kde/share/config/session/ that begin with superkaramba. Restart KDE and start your themes again. Now they will stay in the right place.
CC: (none) => m.van.waes
(In reply to comment #3) > Did you already try this? (from > http://docs.kde.org/stable/en/kdeutils/superkaramba/faq/faq.txt): > > 3.2. My themes start up in different locations when I start KDE. > > Close all superkaramba themes and then delete any session files in > ~/.kde/share/config/session/ that begin with superkaramba. Restart KDE and > start your themes again. Now they will stay in the right place. No I had not still tried that : http://docs.kde.org/stable/en/kdeutils/superkaramba/faq/faq.txt): Now I just tried ,I have close all superkaramba themes but there is no file that begin with superkaramba in ~/.kde/share/config/session/ Here: [david@david ~]$ cd /home/david/.kde4/share/config/session/ [david@david session]$ ls kgpg_1013ef813eca000130729105600000031900029_1316470765_9003 kmix_1013ef813eca000130726960400000034820009_1316470765_8383 konversation_1013ef813eca000131331688300000018530051_1316470765_9408 ktorrent_1013ef813eca000131331389000000018530028_1316470765_9273 kwin_1013ef813eca000130726958200000034820000_1316470765_671038 Another question: Is the package "kdeutils4-4.6.5-0.1.mga1" must be installed? Because I never installed it, never had need.
(In reply to comment #4) > > Another question: Is the package "kdeutils4-4.6.5-0.1.mga1" must be installed? > Because I never installed it, never had need. That package is not in the dependencies: [marja@DenkBlok2 ~]$ rpm -q -R -p ftp://ftp.nluug.nl/ftp/mirror/os/Linux/distr/mageia/distrib/1/x86_64/media/core/updates/superkaramba-4.6.5-0.1.mga1.x86_64.rpm rpmlib(VersionedDependencies) <= 3.0.3-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(CompressedFileNames) <= 3.0.4-1 libQtCore.so.4()(64bit) libQtDBus.so.4()(64bit) libQtGui.so.4()(64bit) libX11.so.6()(64bit) libXrender.so.1()(64bit) libc.so.6()(64bit) libc.so.6(GLIBC_2.2.5)(64bit) libc.so.6(GLIBC_2.3.4)(64bit) libkdecore.so.5()(64bit) libkdeui.so.5()(64bit) libkio.so.5()(64bit) libknewstuff2.so.4()(64bit) libplasma.so.3()(64bit) libstdc++.so.6()(64bit) libstdc++.so.6(GLIBCXX_3.4)(64bit) libsuperkaramba.so.4()(64bit) rtld(GNU_HASH) rpmlib(PayloadIsLzma) <= 4.4.6-1 [marja@DenkBlok2 ~]$ Apart from that, I can't find your four themes (I never used SuperKaramba before, but your screenshots made me curious), I only find one that does about the same as your four: It's called System-Supervisor-1.0 It stays in the place where I put it, but when I choose for it to be visible only on desktop 3, after reboot it is visible on all desktops. At the moment, I tend to think that System-Supervisor-1.0 is meant to replace your widgets. What are the names of your widgets (and which of them move)?
(In reply to comment #5) > > Apart from that, I can't find your four themes (I never used SuperKaramba > before, but your screenshots made me curious), I only find one that does about > the same as your four: It's called System-Supervisor-1.0 > > It stays in the place where I put it, but when I choose for it to be visible > only on desktop 3, after reboot it is visible on all desktops. > > At the moment, I tend to think that System-Supervisor-1.0 is meant to replace > your widgets. > > What are the names of your widgets (and which of them move)? -The name of the Widget is Mandriva Linux Online Widget 1.0 Here: http://kde-look.org/content/show.php/Mandriva+Linux+Online+Widget?content=74612 -I have a little makeover the Widget. >(and which of them move)? -It's random, sometimes just one moved sometimes two moved. By cons, never three or four moved together. Never the same, once a widget 1, once the widget 2 ,etc.....
Could you reproduce with another plugin ? (the idea here is to know if the problem is in superkaramba or eventually in the widget itself )
CC: (none) => balcaen.john
Also it seems this plugin is not available anymore on kde-look. Could you make it available somewhere ?
The Widget is available here : http://dl.free.fr/aDpN6UkGF If need a password to download: david.david I do not think it comes from the widget because it was operating before KDE 4.6.5. Also with Mandriva 2010.2 and KDE 4.4.3 -> 4.4.5-> 4.5.5 it worked perfectly.
> Another question: Is the package "kdeutils4-4.6.5-0.1.mga1" must be installed? > Because I never installed it, never had need. Just FYI: No, it's not needed. But it is the source RPM that builds the superkaramba binary packages. And that's the reason I put its name in the RPM package field.
Hello, I think I can close this bug, for some time now the bug has been fixed. And I think that since the last updates of packages KDE 4.6.5 ,or else package version 4.7.4 in this update: ark 4.6.5 1.1.mga1 x86_64 ktimer 4.6.5 1.1.mga1 x86_64 kwallet 4.6.5 1.1.mga1 x86_64 kcalc 4.6.5 1.1.mga1 x86_64 kcharselect 4.6.5 1.1.mga1 x86_64 kdelibs4-core 4.6.5 1.3.mga1 x86_64 kgpg 4.6.5 1.1.mga1 x86_64 filelight 4.6.5 1.1.mga1 x86_64 lib64katepartinterfaces4 4.6.5 1.3.mga1 x86_64 lib64kcmutils4 4.6.5 1.3.mga1 x86_64 lib64kde3support4 4.6.5 1.3.mga1 x86_64 lib64kdecore5 4.6.5 1.3.mga1 x86_64 lib64kdefakes5 4.6.5 1.3.mga1 x86_64 lib64kdesu5 4.6.5 1.3.mga1 x86_64 lib64kdeui5 4.6.5 1.3.mga1 x86_64 lib64kdewebkit5 4.6.5 1.3.mga1 x86_64 lib64kdnssd4 4.6.5 1.3.mga1 x86_64 lib64kemoticons4 4.6.5 1.3.mga1 x86_64 lib64kerfuffle4 4.6.5 1.1.mga1 x86_64 lib64kfile4 4.6.5 1.3.mga1 x86_64 lib64khtml5 4.6.5 1.3.mga1 x86_64 lib64kidletime4 4.6.5 1.3.mga1 x86_64 lib64kimproxy4 4.6.5 1.3.mga1 x86_64 lib64kio5 4.6.5 1.3.mga1 x86_64 lib64kjs4 4.6.5 1.3.mga1 x86_64 lib64kjsapi4 4.6.5 1.3.mga1 x86_64 lib64kjsembed4 4.6.5 1.3.mga1 x86_64 lib64kmediaplayer4 4.6.5 1.3.mga1 x86_64 lib64knewstuff2_4 4.6.5 1.3.mga1 x86_64 lib64knewstuff3_4 4.6.5 1.3.mga1 x86_64 lib64knotifyconfig4 4.6.5 1.3.mga1 x86_64 lib64kntlm4 4.6.5 1.3.mga1 x86_64 lib64kparts4 4.6.5 1.3.mga1 x86_64 lib64kprintutils4 4.6.5 1.3.mga1 x86_64 lib64kpty4 4.6.5 1.3.mga1 x86_64 lib64krosscore4 4.6.5 1.3.mga1 x86_64 lib64ktexteditor4 4.6.5 1.3.mga1 x86_64 lib64kunitconversion4 4.6.5 1.3.mga1 x86_64 lib64kunittest4 4.6.5 1.3.mga1 x86_64 lib64kutils4 4.6.5 1.3.mga1 x86_64 lib64nepomuk4 4.6.5 1.3.mga1 x86_64 lib64nepomukquery4 4.6.5 1.3.mga1 x86_64 lib64nepomukutils4 4.6.5 1.3.mga1 x86_64 lib64plasma3 4.6.5 1.3.mga1 x86_64 lib64solid4 4.6.5 1.3.mga1 x86_64 lib64superkaramba4 4.6.5 1.1.mga1 x86_64 lib64threadweaver4 4.6.5 1.3.mga1 x86_64 superkaramba 4.6.5 1.1.mga1 x86_64 sweeper 4.6.5 1.1.mga1 x86_64 And this : lib64qt3support4 4.7.4 1.2.mga1 x86_64 lib64qtcore4 4.7.4 1.2.mga1 x86_64 lib64qtdbus4 4.7.4 1.2.mga1 x86_64 lib64qtdeclarative4 4.7.4 1.2.mga1 x86_64 lib64qtdesigner4 4.7.4 1.2.mga1 x86_64 lib64qtgui4 4.7.4 1.2.mga1 x86_64 lib64qtmultimedia4 4.7.4 1.2.mga1 x86_64 lib64qtnetwork4 4.7.4 1.2.mga1 x86_64 lib64qtopengl4 4.7.4 1.2.mga1 x86_64 lib64qtscript4 4.7.4 1.2.mga1 x86_64 lib64qtsql4 4.7.4 1.2.mga1 x86_64 lib64qtsvg4 4.7.4 1.2.mga1 x86_64 lib64qttest4 4.7.4 1.2.mga1 x86_64 lib64qtwebkit4 4.7.4 1.2.mga1 x86_64 lib64qtxml4 4.7.4 1.2.mga1 x86_64 lib64qtxmlpatterns4 4.7.4 1.2.mga1 x86_64 qt4-common 4.7.4 1.2.mga1 x86_64 qt4-database-plugin-mysql 4.7.4 1.2.mga1 x86_64 qt4-database-plugin-sqlite 4.7.4 1.2.mga1 x86_64 qt4-qtdbus 4.7.4 1.2.mga1 x86_64 qt4-xmlpatterns 4.7.4 1.2.mga1 x86_64 libqtcore4 4.7.4 1.2.mga1 i586 libqtdbus4 4.7.4 1.2.mga1 i586 libqtgui4 4.7.4 1.2.mga1 i586 libqtnetwork4 4.7.4 1.2.mga1 i586 libqtsvg4 4.7.4 1.2.mga1 i586 libqtxml4 4.7.4 1.2.mga1 i586 http://pastebin.com/yjUgQHMe So ,this bug is fixed and closed.
Status: NEW => RESOLVEDResolution: (none) => FIXED