[kde-testing] and [kde-crazy] KDE4 overlays thread (part 4)

one_and_only · Posted: Mon Jan 25, 2010 6:11 pm Post subject:

After upgrade to 4.4 RC2 logout, reboot, shutdown from kde menu stopped working. I'm using kdm with USE="consolekit", consolekit is running. What could be the problem?

NForce · Posted: Mon Jan 25, 2010 7:37 pm Post subject:

asturm · Developer Joined: 05 Apr 2007 Posts: 8938

Same issue, think we'll have to wait for an upstream bugfix.

The Dealy Lama · n00b Joined: 10 Jun 2003 Posts: 35 Location: Da'ath

Got this spiffy error whilst compiling kdelibs-4.3.95:

NForce · Posted: Mon Jan 25, 2010 11:06 pm Post subject:

Could this be wrong redland version? I use 1.0.10-r1.

Also, i had a problem for all the time using gentoo but it really started freaking me out just today. So i want to ask: am I the only who always has old ksplash theme (ksplash from kde 4.3 is using theme from 4.2, ksplash from 4.4 is using theme from kde 4.3)? I know it's not upstream bug, because on another machine with ArchLinux on it everything is normal :evil:

kernelOfTruth · Posted: Mon Jan 25, 2010 11:07 pm Post subject:

The Dealy Lama · n00b Joined: 10 Jun 2003 Posts: 35 Location: Da'ath

Wrong redland version, indeed! Thanks!
_________________
"The shadows of this world are perceived by mortals, and they think they know the Truth, but the Reality which casts the shadows is hidden from them, and they do not perceive the Light." (Sayings 2:2)"

asturm · Developer Joined: 05 Apr 2007 Posts: 8938

(I suppose) a recent sync made korganizer-4.3.95 build.

wrc1944 · Posted: Tue Jan 26, 2010 3:27 pm Post subject:

Can't find an ebuild for needed ~dev-libs/poppler-qt4-0.12.3 in the overlays kde or qting-edge, or portage, thus can't merge okular. Only poppler-qt4-0.10.7 is there- am I just missing it somewhere?

asturm · Developer Joined: 05 Apr 2007 Posts: 8938

Your ebuilds are outdated, layman -s kde and it will work.

Yes, current okular-4.3.95.ebuild reads:

wrc1944 · Posted: Tue Jan 26, 2010 3:46 pm Post subject:

I had just re-sync'd 10 minutes ago, but did so again, and still get this:

wrc1944 · Posted: Tue Jan 26, 2010 3:48 pm Post subject:

OK- I'm doing another emerge -uD @world, and am seeing this at the end

asturm · Developer Joined: 05 Apr 2007 Posts: 8938

wrc1944 · Posted: Wed Feb 03, 2010 1:35 pm Post subject:

I was wondering- when KDE SC 4.4 Final is released (hopefully sometime next week), are all the 4.4 ebuilds in this overlay moved over to portage ~Arch right away, so if one is running kde-4.3.5 4.4 final will show up as a normal portage update?

I seem to recall reading a while back this is the case, but I'm not sure. I maintain two such 4.3.5 installations, in addition to my two kde overlay (~x86 and ~amd64) Gentoo installs, so I was just curious.
_________________
Main box- AsRock x370 Gaming K4
Ryzen 7 3700x, 3.6GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
OpenRC Gentoo ~amd64 plasma, glibc-2.36-r7, gcc-13.2.1_p20230304
kernel-6.8.4 USE=experimental python3_11

Dont Panic · Posted: Wed Feb 03, 2010 2:17 pm Post subject:

They're following their release schedule pretty closely (although it's not etched in stone).

Schedules/KDE4/4.4 Release Schedule

wrc1944 · Posted: Wed Feb 03, 2010 2:27 pm Post subject:

I guess I should rephrase- are the KDE SC 4.4 RC3 ( 4.3.98 ) overlay ebuilds going to be renamed and moved to portage, and become 4.4 in ~Arch, and how soon would this occur after kde releases 4.4? I figure it shouldn't take long, as they work very well as they are.
_________________
Main box- AsRock x370 Gaming K4
Ryzen 7 3700x, 3.6GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
OpenRC Gentoo ~amd64 plasma, glibc-2.36-r7, gcc-13.2.1_p20230304
kernel-6.8.4 USE=experimental python3_11

Dont Panic · Posted: Wed Feb 03, 2010 3:42 pm Post subject:

Ah! Sorry.

On reading your question closer, I see it was related to the portage tree timing, and not the release timing.

wrc1944 · Posted: Fri Feb 05, 2010 2:53 pm Post subject:

Hmmm.
I just sync'd the kde overlay on an amd64 box I have 4.3.95 on, wanting to update to RC3 4.3.98, and got this:

rahulthewall · Veteran Joined: 01 Nov 2007 Posts: 1264 Location: Zürich

damoncf · Guru Joined: 05 Oct 2004 Posts: 388 Location: US OH

I am attempting to get 4.4.0 and when it hits oxygen-icons it fails to download the tar ball. It continues to do this with everything following oxygen-icons. Here a partial (very long) output of what happens.

asturm · Developer Joined: 05 Apr 2007 Posts: 8938

The answer, right before your own post: :lol:

Holysword · l33t Joined: 19 Nov 2006 Posts: 946 Location: Greece

There is something annoying me really bad...

Every time I log in a KDE session I must go to systemsettings->keyboard & mouse and re-set the keyboard delay and repeat rate... why can't KDE remember my settings?!?!?!
_________________
"Nolite arbitrari quia venerim mittere pacem in terram non veni pacem mittere sed gladium" (Yeshua Ha Mashiach)

wrc1944 · Posted: Mon Feb 08, 2010 10:53 pm Post subject:

I have had a similar problem on many kde4.x.x installations for about a year, and still do on some of them, except it's with systemsettings->Display not remembering my 1280x1024@85Hz display settings. No matter what xorg.conf settings I have tried, or without xorg.conf at all, or no amount of .kde4 config file edits have ever taken. I've tried all the tricks with removing .kde4 from terminal not while in kde, etc.

It always starts at a much larger setting, like 1600x1200@60Hz, which is not filling the entire screen, and with very small icons and fonts, etc., and requires resetting.

On my main kde4.3.5 install, it has settled down, and while it starts small, it resets itself as the last step in login. This has also happened ocassionally with other distros, but subsequent "updates" revert to the old behavior.

On earlier versions of kde there was always an option in the kde display settings where a simple checkbox for "Apply settings on startup" worked perfectly over whatever distro, xorg version, or kde version for years.
Makes me long for the old days, when this extremely important feature for any self respecting Desktop Environment simply worked, with never a problem. How come every version of Gnome and Xfce have never had this problem, but KDE4 does? It's really disgusting and annoying that this stuff hasn't been addressed in over a year.

Don't get me wrong- I'm a big KDE fan from 2.x days, and long time user and tester of svn versions, but this is ridiculous. :roll:

_________________
Main box- AsRock x370 Gaming K4
Ryzen 7 3700x, 3.6GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
OpenRC Gentoo ~amd64 plasma, glibc-2.36-r7, gcc-13.2.1_p20230304
kernel-6.8.4 USE=experimental python3_11

devsk · Posted: Tue Feb 09, 2010 12:21 am Post subject:

wrc1944 · Posted: Tue Feb 09, 2010 3:12 am Post subject:

In my case, I'm using just a simple generic Gateway EV910 19" CRT monitor which has always configured easily for years with any distro and video card combo I've had, but I've been reading similar stories for months about these things on all sorts of hardware.

Maybe it's a matter of tweaking the settings config files, or minor problems in the System settings code itself that can eventually be worked out. I'd hate to think it's actually a fundamental design flaw in the plasma desktop which I really admire and find very compelling in many ways, but the longer this fundamental problem persists the more that thought creeps into my mind.

Of course that's easy for me to say, and if I had more expertise and could code or work in QT maybe I could help figure it out. I recall in the pre kde-4.0 days I was running kdesvn, and looking in the websvn trunk files one day I saw where the "Apply settings at Startup" feature was removed, and it never came back. IIRC, this was when I started having these display problems, and it was never fixed. I posted several times, but no responses anywhere. I guess the kde devs figure this was covered by new code or settings and wasn't a problem, but for me it wasn't covered, and still isn't, unless I've somehow just missed something.
_________________
Main box- AsRock x370 Gaming K4
Ryzen 7 3700x, 3.6GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
OpenRC Gentoo ~amd64 plasma, glibc-2.36-r7, gcc-13.2.1_p20230304
kernel-6.8.4 USE=experimental python3_11