On Sun, Nov 2, 2014 at 6:38 AM, Nikos Chantziaras wrote:
> What happened? Where are the KDE settings for my monitor?
from kde-misc/kscreen postinstall:
LOG: postinst
Disable the old screen management:
# qdbus org.kde.kded /kded org.kde.kded.unloadModule randrmonitor
# qdbus org.kde.kded /k
On 04/11/14 18:28, Douglas J Hunley wrote:
On Sun, Nov 2, 2014 at 6:38 AM, Nikos Chantziaras wrote:
What happened? Where are the KDE settings for my monitor?
from kde-misc/kscreen postinstall:
LOG: postinst
Disable the old screen management:
# qdbus org.kde.kded /kded
Hi to Everyone!
I have a DELL Inspiron 6000 and installing KDE I see this error message
printed constantly on the console:
kded: ERROR: KMilo: DellI8kMonitor: ioctl failed in fn_status()
Google doesn't give me any help, so I ask you if someone knows how to solve
this.
Thanks!
i generally kill knotify and kded when they misbehave and haven't encountered
any noticeable problems after doing so. I hate it when i forget to check for
these two before starting an overnight portage update.
also heres a blog post related to the kded problem i seen on planet kde
rec
And, incidentally, I don't know if anybody's interested, but on my
system, I changed this:
if pidof x $PMS > /dev/null ||
( test "$XUSER" != "" && pidof dcopserver > /dev/null &&
test -x /usr/bin/dcop && /usr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mauro Arnoldi wrote:
> Hi to Everyone!
>
> I have a DELL Inspiron 6000 and installing KDE I see this error message
> printed constantly on the console:
>
> kded: ERROR: KMilo: DellI8kMonitor: ioctl failed in fn_status()
>
>
Alle 18:12, domenica 07 maggio 2006, Jeremy Olexa ha scritto:
> Mauro Arnoldi wrote:
> > Hi to Everyone!
> >
> > I have a DELL Inspiron 6000 and installing KDE I see this error message
> > printed constantly on the console:
> >
> > kded: ERROR: KMilo: De
ter readings
like:
ssh: KONSOLESCRIPTS_KONSOLE_sessionName: Name or service not known
ssh: KONSOLESCRIPTS_getCommand: Name or service not known
ssh: type: Name or service not known
bash: [: missing `]'
bash: function: command not found
konsole-12133
konsole-12134
kwin
kicker
kded
knotify
00043360011_1295887108_972511
kdeinit4: preparing to launch /usr/bin/nepomukservicestub
Unknown service name: 10d5eae5690001295882092
0043360012_1295887108_978319
kdeinit4: preparing to launch /usr/lib64/libkdeinit4_konsole.so
Unknown service name: 10d5eae5690001295882092
0043360013_129
io-5.21.0::gentoo" [ebuild])
> (dependency required by "kde-frameworks/kinit-5.21.0::gentoo" [ebuild])
> (dependency required by "kde-frameworks/kded-5.21.0::gentoo" [ebuild])
>
> I have -plasma and -qt5 in make.conf because I'm not ready to go to KDE-5
> yet. Does
uot;
Disable "dri"
Disable "dri2"
Load "glx"
EndSection
If I add exec startkde to the top of the /etc/X11/xinit/xinitrc file,
then startx fails to start. I get the same dri2 error as above, but
also get
startkde: Starting up...
Connecting to deprecated signal
Q
Hi,
I'm using KDE 3.4.
Since few days ago I can't login using KDM.
The login process can't pass the "initializing peripherals" stage.
I can see that there are two processes running kded (one of the is the father
of the other) which I can't kill.
After rebooting th
[EMAIL PROTECTED] wrote:
> What do I need to turn off in kde-3.5 so that mounted or umounted
> devices never show up on my desktop window?
Maybe under KDE Components > Service Manager > Startup Services,
switching off KDED Media Manager? And relogin to KDE.
> I've cleared a
der KDE Components -> Service Manager,
untick the KDED Media Manager, Stop it, and Apply. That stops the
blinking.
Then under Desktop -> Behavior -> Device Icons, untick the Show
device icons, as otherwise upon the next login the Media Manager
will be running again, even though it
List,Here's a new one. I ended up hard booting my system without shutting down first because I spilled beer on my keyboard.. ok, now that you're done laughing, here's the problem:localhost jbdubbs # /usr/kde/3.5/bin/kded
FATAL: DCOP communication problem!AbortedOn session sta
kded mediamanager fullList
This returns:
/org/freedesktop/Hal/devices/usb_device_41e_413e_6D44A22E6B015912_if0
camera
USB Interface
false
false
camera://Creative Zen Vision:[EMAIL PROTECTED]:001,014]/
media/gphoto2camera
Could this be the problem? That the Zen is recongnised as a camera
rvices the KDED Media
Manager has a status of Not Running. If I try to start it manually I just
get a message saying Unable to start service.
I just don't know what to try next - any suggestions?
Thanks
Paul
--
This message has been sent using kmail with gentoo linux
--
gentoo-
"dri"
> Disable "dri2"
> Load "glx"
> EndSection
>
> If I add exec startkde to the top of the /etc/X11/xinit/xinitrc file,
> then startx fails to start. I get the same dri2 error as above, but
> also get
>
> startkde: Starting up...
> Co
Yuval Scharf wrote:
> Hi,
>
> I'm using KDE 3.4.
> Since few days ago I can't login using KDM.
> The login process can't pass the "initializing peripherals" stage.
> I can see that there are two processes running kded (one of the is the father
&
at's running via 'htop'.
This reveals that 'konsole' -- the 1st app I started after Fluxbox --
caused the following processes to start & remain running :
3863 kdeinit running ...
3866 dcopserver [kdeinit] --nosid --suicide
3868 klauncher [kdeinit] --new-startup
3
> 3866 dcopserver [kdeinit] --nosid --suicide
> 3868 klauncher [kdeinit] --new-startup
> 3870 kded [kdeinit] --new-startup
>
> So it looks as if the needed command is 'kdeinit'.
I added 'kdeinit &' to ~/.xinitrc & it made a small difference :
the kded,
saying, it cannot contact DCop Server or connect to the X server. I
downgraded the kernel version until reach the 2.6.18.-r2 version(wich was
the last version used on the machine until the reinstall), and everything
worked fine again ! this is weird ! what could be happening whith
drive).
>
> Thanks
> Francisco
Well the reason I suggested that you look under the service manager is
because the services listed there are kded modules AFAIR, i.e. they are
all clubbed together and run under the process called kded4. Maybe one
of them is acting up.
--
- Yohan Pereira
The
th mkdosfs or mtools.
> My camera formats the card with a volume name of CANON_EOS, so it is
> mounted at /media/CANON_EOS.
Well it does, but it does feel a bit of an ugly hack to have to label all my
cards "camera" just to get hal/kded to behave. Besides, the card isn't the
or,
> when i return to the terminal, i got some messages refering to the kded,
> saying, it cannot contact DCop Server or connect to the X server. I
> downgraded the kernel version until reach the 2.6.18.-r2 version(wich was
> the last version used on the machine until the reinstall),
"The KDE Mediamanager is
> not running" In the control Centre - Service Manager under startup
> Services the KDED Media Manager has a status of Not Running. If I try
> to start it manually I just get a message saying Unable to start
> service.
You probably emerged versions of hal
.
Sean
On Tuesday 12 July 2005 10:46 am, Yuval Scharf wrote:
> Hi,
>
> I'm using KDE 3.4.
> Since few days ago I can't login using KDM.
> The login process can't pass the "initializing peripherals" stage.
> I can see that there are two processes runn
On Tuesday 12 July 2005 18:23, Zac Medico wrote:
> Yuval Scharf wrote:
> > Hi,
> >
> > I'm using KDE 3.4.
> > Since few days ago I can't login using KDM.
> > The login process can't pass the "initializing peripherals" stage.
> > I
th)
Object::connect: No such signal
QDBusAbstractInterface::DeviceRemoved(QDBusObjectPath)
Object::connect: No such signal
QDBusAbstractInterface::DeviceChanged(QDBusObjectPath)
QStringList
Solid::Backends::UDisks::UDisksManager::allDevicesInternal() error:
"org.freedesktop.DBus.Error.Spawn.ExecFail
gt; Hi,
> >
> > I'm using KDE 3.4.
> > Since few days ago I can't login using KDM.
> > The login process can't pass the "initializing peripherals" stage.
> > I can see that there are two processes running kded (one of the is the
> > father
esses to start & remain running :
> >
> > 3863 kdeinit running ...
> > 3866 dcopserver [kdeinit] --nosid --suicide
> > 3868 klauncher [kdeinit] --new-startup
> > 3870 kded [kdeinit] --new-startup
> >
> > So it looks as if the needed command is &#
er startup Services the KDED Media
Manager has a status of Not Running. If I try to start it manually I just
get a message saying Unable to start service.
I just don't know what to try next - any suggestions?
Just got this last night - the problem is that the new dbus/hal chan
quot;The KDE Mediamanager is not running"
> > In the control Centre - Service Manager under startup Services the KDED
> > Media Manager has a status of Not Running. If I try to start it manually
> > I just get a message saying Unable to start service.
> >
> > I ju
kiconthemes-5.21.0::gentoo" [ebuild])
(dependency required by "kde-frameworks/kbookmarks-5.21.0::gentoo" [ebuild])
(dependency required by "kde-frameworks/kio-5.21.0::gentoo" [ebuild])
(dependency required by "kde-frameworks/kinit-5.21.0::gentoo" [ebuild])
(dependency requ
te
All the best
Simon
On Tuesday 12 July 2005 16:23, Zac Medico wrote:
Yuval Scharf wrote:
Hi,
I'm using KDE 3.4.
Since few days ago I can't login using KDM.
The login process can't pass the "initializing peripherals" stage.
I can see that there are two processes runn
Jason Weisberger wrote:
> List,
>
> Here's a new one. I ended up hard booting my system without shutting
> down first because I spilled beer on my keyboard.. ok, now that
> you're done laughing, here's the problem:
>
> localhost jbdubbs # /usr/kde/3.5/
::DeviceChanged(QDBusObjectPath)
> QStringList
> Solid::Backends::UDisks::UDisksManager::allDevicesInternal() error:
> "org.freedesktop.DBus.Error.Spawn.ExecFailed"
> kded(4259)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
> OpenGL vendor string:
is mounted at /media/CANON_EOS.
>
> Well it does, but it does feel a bit of an ugly hack to have to label
> all my cards "camera" just to get hal/kded to behave.
There is a way round this. It is possible, somewhere in the config of
pmount/hal, to have devices mounted
On Tuesday 17 May 2011 09:17:45 Yohan Pereira wrote:
> i generally kill knotify and kded when they misbehave and haven't
> encountered any noticeable problems after doing so.
Yes, same here. Once I kill them, no problem thereafter.
They don't seem to me to be related to some
u're done laughing, here's the problem:
> >
> > localhost jbdubbs # /usr/kde/3.5/bin/kded
> > FATAL: DCOP communication problem!
> > Aborted
> >
> > On session start, KDE show an error:
> >
> > KDE Media Manager not running!
> >
> > I guess
orks/kio-5.21.0::gentoo" [ebuild])
> (dependency required by "kde-frameworks/kinit-5.21.0::gentoo" [ebuild])
> (dependency required by "kde-frameworks/kded-5.21.0::gentoo" [ebuild])
>
> I have -plasma and -qt5 in make.conf because I'm not ready to go to KDE-5
> ye
uot; In
> the control Centre - Service Manager under startup Services the KDED Media
> Manager has a status of Not Running. If I try to start it manually I just
> get a message saying Unable to start service.
>
> I just don't know what to try next - any suggestions?
>
here's the problem:> >> > localhost jbdubbs # /usr/kde/3.5/bin/kded> > FATAL: DCOP communication problem!> > Aborted> >> > On session start, KDE show an error:
> >> > KDE Media Manager not running!> >> > I guess there's somethin
rtsd, xorg, and kded were
eating cpu time. This is the same behaviour as on Kubuntu before. I
suspect the cause was the same, however, I don't remember exactly so I
won't point fingers.
Do any of you know what this is? Do you think if I recompiled xorg,
kde, and arts if it'd fix the
ing had happened.
>
> However, right after this, KDE has been acting *really* slow. Much
> slower than it should. # top revealed that artsd, xorg, and kded were
> eating cpu time. This is the same behaviour as on Kubuntu before. I
> suspect the cause was the same, however, I do
er [kdeinit] --new-startup
7030 ?S 0:01 \_ kio_imap4 [kdeinit] imap /tmp/ksocket-michael/
20306 ?S 0:00 \_ kio_file [kdeinit] file /tmp/ksocket-michael/k
21164 ?S 0:00 \_ kio_smtp [kdeinit] smtp /tmp/ksocket-michael/k
6980 ?S
ins glibc.
~/.xsession-errors however was a little more informative, but only a little.
I've attached the relevant parts, but they don't tell much.
--
Gruß | Greetings | Qapla'
Emacs is a great operating system, which only lacks a good editor.
kdeinit4: preparing to launch /usr/lib/
ed a button that did work: POWER. The system shut
> > down normally! After X11 died, it went back the the framebuffer and
> > acted like nothing had happened.
> >
> > However, right after this, KDE has been acting *really* slow. Much
> > slower than it should. # t
cked a button that did work: POWER. The system shut
> > down normally! After X11 died, it went back the the framebuffer and
> > acted like nothing had happened.
> >
> > However, right after this, KDE has been acting *really* slow. Much
> > slower than it should. # t
ameworks/kbookmarks-5.17.0
~kde-frameworks/kcmutils-5.17.0
~kde-frameworks/kcodecs-5.17.0
~kde-frameworks/kcompletion-5.17.0
~kde-frameworks/kconfig-5.17.0
~kde-frameworks/kconfigwidgets-5.17.0
~kde-frameworks/kcoreaddons-5.17.0
~kde-frameworks/kcrash-5.17.0
~kde-frameworks/kdbusaddons-5.17.0
~kde-frameworks/kde
17 result = 0
DCOP: register 'anonymous-9217' -> number of clients is now 1
DCOP: unregister 'anonymous-9217'
kdeinit: Launched KLauncher, pid = 9221 result = 0
DCOP: register 'klauncher' -> number of clients is now 1
DCOP: new daemon klauncher
kdeinit: ope
uncher [kdeinit] --new-startup
6315 ?S 0:05 kded [kdeinit] --new-startup
6583 ?S 0:00 kwrapper ksmserver
6585 ?S 0:00 ksmserver [kdeinit]
6586 ?
12m kdesktop
10067 0.8 28116 15m4 2364 11m 12m kate
12407 0.7 26192 14m 36 2032 10m 12m kded
12436 0.7 23976 14m 528 2872 8736 11m superkaramba
8482 0.7 25004 14m 36 2172 10m 11m konsole
9112 0.7 24932 14m 36 2100 10m 11m konsole
12438 0.7 24900 14m 60 1812 10m 11m k
er
> 22144 dale 15 0 24012 14m 11m S 0.0 1.4 0:00.98 kppp
> 22150 dale 15 0 27848 13m 10m S 0.0 1.3 0:14.60 konsole
> 22149 dale 15 0 27396 13m 10m S 0.0 1.3 0:00.48 kgpg
> 22160 dale 20 0 23260 12m 11m S 0.0 1.3 0:02.85 kdesu
> 22102 d
cher
kdeinit4: preparing to launch /usr/kde/4.1/bin/kded4
kded(27288) KLocalePrivate::initEncoding: Cannot resolve system
encoding, defaulting to ISO 8859-1.
kdeinit4: preparing to launch /usr/kde/4.1/bin/kbuildsycoca4
kbuildsycoca4(27291) KLocalePrivate::initEncoding: Cannot resolve
system encodin
ntents/ui/ContextMenu.qml
/usr/share/plasma/shells/org.kde.plasma.desktop/contents/configuration/panelconfiguration/MoreSettingsMenu.qml
root@fireball / #
root@fireball / # equery f kde-plasma/plasma-workspace | grep menu
/etc/xdg/autostart/gmenudbusmenuproxy.desktop
/usr/bin/gmenudbusmenuproxy
/usr/lib64/qt5
n/panelconfiguration/MoreSettingsMenu.qml
root@fireball / #
As are these.
root@fireball / # equery f kde-plasma/plasma-workspace | grep menu
/etc/xdg/autostart/gmenudbusmenuproxy.desktop
/usr/bin/gmenudbusmenuproxy
/usr/lib64/qt5/plugins/kf5/kded/appmenu.so
/usr/lib64/qt5/plugins/plasma/applets/plasma_applet_appme
imple
> "/etc/init.d/cupsd restart" will work just fine.
>
> If you upgrade something kde, say kdelibs or some other kde base
> package, then all you need to do is log out of KDE and log back in
> again. Sort of the same with updating xorg, logout, go to a console and
gt; > you have to do is restart the service. It will stop the old service
> > then load up the new service that was just installed. Just a simple
> > "/etc/init.d/cupsd restart" will work just fine.
> >
> > If you upgrade something kde, say kdelibs or some oth
:-)
I absolutely concur with Alan and Dale, I just want to warn a bit about
complex X11-environments like gnome or kde. If you logout and login
again, it is NOT secure, that all gnome/kde/qt apps have been closed.
There are services (gconf, kded, pulse, etc) that take a time to quit,
or som
3.0
kde-frameworks/kemoticons-5.23.0
kde-frameworks/kpeople-5.23.0
kde-frameworks/kconfigwidgets-5.23.0
kde-frameworks/knotifications-5.23.0
kde-frameworks/kiconthemes-5.23.0
kde-plasma/kwrited-5.6.5
kde-plasma/polkit-kde-agent-5.6.5
kde-frameworks/ktextwidgets-5.23.0
kde-frameworks/kwallet-5.
[ 86.9 K ] kaccounts-integration-22.08.1.tar.xz
[ 63.1 K ] kaccounts-providers-22.08.1.tar.xz
[ 71.8 K ] kactivities-5.98.0.tar.xz
[ 88.9 K ] kauth-5.98.0.tar.xz
[ 127.0 K ] kbookmarks-5.98.0.tar.xz
[ 185.0 K ] kcmutils-5.98.0.tar.xz
[ 121.6 K ] kcompletion-5.98.0.tar.xz
[ 2
% -ko% -lt% -lv% -ms% -nb% -nds% -ne% -nl% -nn% -pa% -pl% -pt%
-pt-BR% -ro% -ru% -se% -sk% -sl% -sq% -sv% -th% -tr% -uk% -vi% -zh-CN% -zh-TW%"
LINGUAS="(-ar%) (-be%) (-bg%) (-bs%) (-ca%) (-cs%) (-da%) (-de%) (-el%)
(-en_GB%) (-eo%) (-es%) (-et%) (-eu%) (-fa%) (-fi%) (-fr%) (-ga%) (-gl%)
-test" 850 KiB
[ebuild U ] kde-frameworks/qqc2-desktop-style-5.85.0:5/5.85::gentoo
[5.82.0:5/5.82::gentoo] USE="-debug -test" 60 KiB
[ebuild U ] kde-frameworks/kbookmarks-5.85.0:5/5.85::gentoo
[5.82.0:5/5.82::gentoo] USE="-debug -doc -nls -test" 125 KiB
[ebuild
ring.
Trying to convert empty KLocalizedString to QString.
Trying to convert empty KLocalizedString to QString.
Failed to open layout memory xml file for reading
"/home/vision/.local/share/kded5/keyboard/session/layout_memory.xml" error:
5
System timezone has been changed, new timezone is
resume...
These are the packages that would be merged, in order:
emerge: It seems we have nothing to resume...
These are the packages that would be merged, in order:
emerge: It seems we have nothing to resume...
These are the packages that would be merged, in order:
emerge: It seems we have no
de/3.4/bin/kded: Cannot prelink against non-PIC shared
library /usr/lib/libjpeg.so.62
prelink: /usr/kde/3.4/bin/kioslave: Cannot prelink against non-PIC
shared library /usr/lib/libjpeg.so.62
prelink: /usr/kde/3.4/bin/kwrite: Cannot prelink against non-PIC
shared library /usr/lib/libjpeg.so.62
prelink
:5/5.43 kde-frameworks/kcoreaddons:5/5.43
kde-frameworks/kcrash:5/5.43 kde-frameworks/kdbusaddons:5/5.43
kde-frameworks/kdeclarative:5/5.43 kde-frameworks/kded:5/5.43
kde-frameworks/kdelibs:4/4.14 kde-frameworks/kdelibs-env:4/4.14
kde-frameworks/kdelibs4support:5/5.43
kde-frameworks/kdesignerplugin
Mick wrote:
> 2. If problems show up, forget the script and use 'emerge -avuND world' as
> Mr.
> McKinnon suggested. In most cases this will resolve any conflicts on its
> own.
> You could add '--backtrack=90' if there are unresolved conflicts to get
> portage
> to try harder.
=\
I do rea
e -gmp -gnutls -gsm -iec61883
> -ieee1394 -kvazaar -ladspa -libass -libcaca -libdrm -libilbc -librtmp
> -libsoxr -libv4l -lzma (-mipsdspr1) (-mipsdspr2) (-mipsfpu) (-mmal) -modplug
> -nvenc -openal -opengl -openh264 -openssl -opus -oss -pic -pulseaudio
> -rubberband -samba -sn
70 matches
Mail list logo
