Author Topic: KDE SC 4.11.2 arriving to kdenext (Read 17078 times)

ReinerS · « **Reply #30 on:** 2013/10/06, 10:06:50 »

hmm, looks really as this problem, is within my box then :evil:

I made an d-u on an laptop late night and had none of those issues too.
Looks like there is some work forme coming up.

regards

Reiner

spacepenguin · « **Reply #31 on:** 2013/10/06, 14:57:15 »

Quote from: "dibl"

I don't normally change the icon sizes, but I'm going to have a little play with that and see if it shows the issue that spacepenguin saw.

Thanks for testing.

Quote

I'm not sure where in my normal viewing of files I would see "small icons" -- it's not something I use, I guess.

The "small icons" size is used e.g. in the menus, the desktop context menu, the dolphin folder sidebar,...

Quote

But the settings do appear to be working as expected. So I wonder if this has to do with the Cleanlooks style, rather than the KDE settings.

All built in window styles (except Oxygen - is it built in?) do change/ignore the icons size settings for small icons and force the systemsettings main window to use icons size 32 instead of the dialog icon size. The crux is - I do not use one of these styles, but for every user account the style is reset to cleanlooks (without changing the style setting in systemsettings). The window style dependent icon size thingy is a bug (even existed in 4.10), that happens on other distributions too, but as you all don't have your look reset that part has to be something within my system (since the update from 4.11.1 to 4.11.2)...

dibl · « **Reply #32 on:** 2013/10/06, 15:08:27 »

Quote from: "spacepenguin"

The "small icons" size is used e.g. in the menus, the desktop context menu, the dolphin folder sidebar,...

Aha --, so for example the icons on my panel to launch my apps. Good -- I understand now -- thank you.

absolut · « **Reply #33 on:** 2013/10/06, 16:37:34 »

i've finally give me a hard kick and enabled kdenext repo. dist-upgrade went fine. thanks, Santa!

agaida · « **Reply #34 on:** 2013/10/06, 17:43:29 »

@spacepenguin: We do not recommend the use of qtcurve for longer then a year - you will be on your own. We don't support qtcurve related problems since then. As a alternative themeing engine for KDE we recommend (and use in the last releases) oxygen.

This will change with the next release, where we change the gtk engine back to gnome-themes-standard because of problems with several gtk applications, mostly inkscape and iceweasel.

So: Und nun das ganze in Deutsch. Wir haben qtcurve aus dem Relese geworfen, weil es so buggy war, dass ein sinnvolles Arbeiten damit nicht möglich war. Statt dessen haben wir auf gtk-oxygen umgestellt, was wesentlich weniger Fehler verursachte. Leider hat sich herausgestellt, dass auch durch diese Engine sehr viele Fehler in gtk-Applikationen ausgelöst wurden. Ultima ratio war der Wechsel zu gnome-themes-standards, die sind mittlerweile vom Aussehen sehr gut geworden und machen bis jetzt keine bekannten Probleme. Die Integration in KDE ist zwar nicht vollkommen, aber erträglich, noch wichtiger ist allerdings, es funktioniert.

spacepenguin · « **Reply #35 on:** 2013/10/06, 18:50:17 »

@agaida: I was sure that you'd say something like that (and I cannot hear it anymore, sorry). Oxygen cannot deliver a colored menubar for KDE apps so is no alternative for me. I don't use QtCurve for GTK I use it for KDE apps.

As long as it's proven that it is no siduction "feature" (as was the wbar issue and the change of the colortheme and icon sizes (!) after updating siduction-settings-kde or whatever package it was some time ago) by now I don't need any help in finding the cause. Thanks.

I just wonder why it was introduced with KDE SC 4.11.2...

Santa · « **Reply #36 on:** 2013/10/06, 21:13:42 »

With regarding to the cases of storage devices not properly detected in kde, Tom posted this:

Quote from: samoth

Regarding device recognition, please see
http://forum.siduction.org/index.php?msg=32923#32923
Greetings
Tom

Please don't ignore that thread, it's full of useful information. To sum up: I have switched kdelibs to use udisks2 instead of udisks version 1 some time ago, it worked very well for me, however, after seeing that some of you couldn't use some devices anymore I switched to udisks version 1 again. This is obviously a workaround, not a real fix for the problems (which will come back as soon as kdelibs packaging is changed to use udisks2 again). The explanation for the problems you have seen may be:

a) You didn't have udisks2 installed.

or

b) You have expecienced a bug in libsolid-udisks2, udisks2 itself or something else used indirectly by solid or udisks.

So I have built a kdelibs package using udisks2 which is available here:

Code: [Select]

deb http://packages.siduction.org/kdenext udisks2 main

So the persons who have problems with storage devices (as far as I know: clubex, ReinerS, spacepenguin, Crust, dieres) please if you have some free time try to add that line to your sources.list and try again to use the storage devices which didn't work previously. Thanks in advance.

ralul · « **Reply #37 on:** 2013/10/06, 23:01:28 »

@Santa, udisks2 is needed when using systemd-204 !?
Many thanks!

spacepenguin · « **Reply #38 on:** 2013/10/06, 23:47:23 »

My issue is solved. Found the culprit. I already mentioned that the built in window styles are buggy in resetting and ignoring icon sizes and that somehow my window style always gets reset to the built in cleanlooks style. The question was just why that style as I never had used it wittingly.

After the confirmation here in the forum that no-one else has the problem with the reset style and therefore icon sizes I supposed that the installation of RazorQt had caused the trouble (freundliches "Klappe, agaida..."

). RazorQt isn't installed on my system anymore but has presumably left some marks. Apparently RazorQt writes a [Qt] section with some default configuration into the file ~/.config/Trolltech.conf, i.a. "style=Cleanlooks". I have verified that it's RazorQt by looking at the file in a Firestarter RazorQt image in virtualbox. And my fresh Firestarter KDE install in virtualbox doesn't have that entry.

KDE SC seems to use the [Qt] section too. Alas it doesn't write the window style into it - but reads it from there! And obviously gives it - since KDE SC 4.11.2 - a higher priority than the settings the user made in systemsettings.

So after backing up the Trolltech.conf file I have deleted the whole [Qt] part from it and instantly, without re-login, my systemsettings' icons were normal again. Confirmed my "nameless" style of choice in systemsettings and now everything is ok.

Just for your info...

What remains are the buggy built in window styles but that doesn't bother me as I don't use them (wrote bug report on bugs.kde.org).

agaida · « **Reply #39 on:** 2013/10/07, 18:51:32 »

tirili ...

ReinerS · « **Reply #40 on:** 2013/10/07, 18:59:56 »

@santa: Even more strange. Logged in with kde again today and all of those problems I had mentioned before seem to have gone.

Well I did a d-u again late night but cannot remember that there was much in it which shhouldt have caused this. I additionally had installed udisk-glue (?).

regards

Reiner

clubex · « **Reply #41 on:** 2013/10/08, 00:31:05 »

Santa: After the last KDE upgrade automounting of CDROM, card reader and USB flash drive was restored.

Never the less I added your repo and afterwards did a du. Amongst other things kdelibs was upgraded. Unfortunately once again I'm back to having no CDROM and SD card mounting although USB flash drives automount OK.

Throughout this period I've had both udisks and udisks2 installed but I can't find libsolid-udisks2.

dieres · « **Reply #42 on:** 2013/10/08, 03:48:21 »

@santa
no change on my Acer B113. To get my sd card working, I must
unload tg3 modul. The card reader is not usb but connected through bcm57785 chip. It is not udisk2 related. Usb Sticks I see with fdisk -l, but they are not seen in Dolphin or "Geräteüberwachung".

Code: [Select]

root@acerb113:/home/didi# apt-cache policy udisks2
udisks2:
  Installiert:           2.1.1-1
  Installationskandidat: 2.1.1-1
  Versionstabelle:
 *** 2.1.1-1 0
        500 http://http.debian.net/debian/ unstable/main amd64 Packages
        100 /var/lib/dpkg/status

Code: [Select]


root@acerb113:/home/didi# cat /etc/apt/sources.list.d/siduction.list 
# official siduction-lists
deb http://ftp.uni-stuttgart.de/siduction/base unstable main contrib non-free
#deb-src http://ftp.uni-stuttgart.de/siduction/base unstable main

deb http://ftp.uni-stuttgart.de/siduction/extra unstable main contrib non-free
#deb-src http://ftp.uni-stuttgart.de/siduction/extra unstable main

deb http://ftp.uni-stuttgart.de/siduction/fixes unstable main contrib non-free
#deb-src http://ftp.uni-stuttgart.de/siduction/fixes unstable main

deb http://packages.siduction.org/user unstable main contrib non-free

deb http://packages.siduction.org/kdenext udisks2 main
deb http://packages.siduction.org/kdenext unstable main

Is there something wrong with my siduction.list?

clubex · « **Reply #43 on:** 2013/10/08, 21:15:04 »

Santa: Further to my above post RE: your udisks2 version of KDElibs. While merely inserting a media will not automount the media, an application such as Clementine or K3B will.

Rather than reverting to KDE4.11.2-0r1 (which worked for me) it's easier for me to wait for the next upgrade

EDIT: I should have added that media will not appear in Dolphin unless first opened with an application.

spacepenguin · « **Reply #44 on:** 2013/10/13, 10:14:16 »

Quote from: Santa

So I have built a kdelibs package using udisks2 which is available here:
Code: [Select]
deb http://packages.siduction.org/kdenext udisks2 main

I have not tested this and everything works as it should now, all media are recognized by the device manager.

[...]

[Edit]: Now I have enabled the repo and did a d-u: The following packages got installed:

Code: [Select]

Die folgenden Pakete werden aktualisiert (Upgrade):
  kdelibs-bin kdelibs5-data kdelibs5-dev kdelibs5-plugins kdoctools
  libkcmutils4 libkde3support4 libkdeclarative5 libkdecore5 libkdesu5
  libkdeui5 libkdewebkit5 libkdnssd4 libkemoticons4 libkfile4 libkhtml5
  libkidletime4 libkimproxy4 libkio5 libkjsapi4 libkjsembed4 libkmediaplayer4
  libknewstuff2-4 libknewstuff3-4 libknotifyconfig4 libkntlm4 libkparts4
  libkprintutils4 libkpty4 libkrosscore4 libkrossui4 libktexteditor4
  libkunitconversion4 libkutils4 libnepomuk4 libnepomukquery4a
  libnepomukutils4 libplasma3 libsolid4 libthreadweaver4
40 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
Es müssen 15,4 MB an Archiven heruntergeladen werden.
Nach dieser Operation werden 41,0 kB Plattenplatz zusätzlich benutzt.

Alas I cannot test it now as my plasma-desktop always crashes: http://forum.siduction.org/index.php?msg=33085#33085

[Edit 2]: Well, I guess it does not work. I cannot reach the device manager but when I open dolphin and insert some SD- or CF-card into my card reader or some CD/DVD into the drive nothing is shown in dolphin's places. Only when I insert some USB stick it is shown in the sidebar.

I really need to revert that update somehow...!