What happened to kpackage?
by Anne Wilson
I need a screenshot for UserBase, but when I try to launch it I just get
KPackageKit. Kdeadmin is installed - I thought it was part of that?
Anne
--
New to KDE4? - get help from http://userbase.kde.org
Just found a cool new feature? Add it to UserBase
15 years, 1 month
nVidia 'binary blob' drivers
by Clive Messer
The recently released "stable" nVidia 180.44 driver contains a fix for OpenGL
crashing when running plasma. Obviously relevant to this list. rpmfusion
latest f10 package was for 180.29. (I think 180.37 was only packaged for dev.)
Anyway, it might be worth asking if they can upgrade the f10 build.
I've been running 180.44 on f10 with GTX295, GTX260, 8800GTX & 7900GTO, using
CUDA, mplayer with vdpau, and OpenGL games on top of KDE (de enabled), without
a single crash or hang so far. Certainly not the case, pre 180.44! Just
thought I'd mention it.
Regards
Clive
--
Clive Messer <clive(a)vacuumtube.org.uk>
15 years, 1 month
Lost systray icons
by Anne Wilson
Since a crash yesterday I have lost most of the systray icons. I've tried
renaming plasma-appletsrc, and lost even more. Now I only see the icons for
battery/mains power and knetworkmanager icons (before the rename I also had
the NM-applet and half! of the notifier). Hovering over the space left shows
the popup for all the icons I'd expect to see. Restarting plasma after the
rename gives
[anne@AA1 config]$ plasma
QLayout: Attempting to add QLayout "" to QWidget "", which already has a
layout
plasma(9264)/kdecore (KService) KServicePrivate::init: The desktop entry file
"/usr/share/kde4/services/sysinfo.protocol" has Type= "Application" but no
Exec line
Object::connect: Attempt to bind non-signal
TaskManager::TaskGroup::editRequest()
QCoreApplication::postEvent: Unexpected null receiver
QCoreApplication::postEvent: Unexpected null receiver
plasma(9264)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size QSizeF(-22,
26)
plasma(9264)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size QSizeF(0,
0)
plasma(9264)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size QSizeF(-22,
26)
plasma(9264)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size QSizeF(0,
0)
QCoreApplication::postEvent: Unexpected null receiver
[anne@AA1 config]$ QCoreApplication::postEvent: Unexpected null receiver
QCoreApplication::postEvent: Unexpected null receiver
QCoreApplication::postEvent: Unexpected null receiver
QCoreApplication::postEvent: Unexpected null receiver
QCoreApplication::postEvent: Unexpected null receiver
Any ideas for recovering the icons?
Anne
--
New to KDE4? - get help from http://userbase.kde.org
Just found a cool new feature? Add it to UserBase
15 years, 1 month
much of KDE freezes for 20 seconds (includes strace output)
by Hans Ecke
Hi there-
Ever since I switched from KDE 3.5 (F8) to KDE 4.2 (F10) I have this
problem:
When:
* starting a KDE application, for instance konqueror
* opening the start menu
* attempting to add a new event in korganizer
What happens: (example: new konqui instance)
Konqueror appears. By default for me it appears in a blank window.
However when trying to input anything in the location bar it does not
take any input. In fact, it does not even redraw itself if I minimize it
and then restore. It remains frozen like this for about 20 seconds. Then
everything is normal again.
Once that happens everything is fine for a while (10 minutes or so). New
konqueror windows come up and are responsive just fine. But if I don't
do anything for a while the problem reappears.
What happens: (example: new event in korganizer)
I double-click on a time in korganizer. A "New Event" window comes up.
Similar to the konqueror example, it draws itself completely, but then
becomes nonresponsive and does not redraw itself. Becomes responsive
again after about 20 seconds.
What happens: (example: start menu)
I click on the start menu. It appears as a black square with rounded
corners, obscuring the desktop and windows underneath. In other words,
different from the examples above it does not draw itself before
freezing. It unfreezes after 20 seconds.
Speculation:
Some service is failing and KDE takes 20 seconds to notice that or to
try and start it.
How do I debug that? I attached an strace log, but that is very opaque.
Scroll down the timestamps and you see the big jump at 07:50:38.674661
and at 07:50:49.615261. Two select() calls that take 10 and 15 seconds,
respectively. I guess file descriptor 7 is its connection to DBUS?
Any help would be appreciated. This is very frustrating.....
Cheers
Hans
15 years, 1 month
