I have a testing laptop that i also use as a backup device and while i
always used to transfer the files from my main laptop using the windows
OS on both with the Ethernet port, now that i am using F22 KDE, i would
like to learn how to do it on this distro.
I have heard it's a bit harder to do it with Linux, but i would like to
hear suggestions on which is the better way.
I have a ThinkPad T61, with Nvidia G86M [Quadro NVS 140M] GPU.
I like to run Fedora KDE, but my experience with successive Fedora's
has not been happy.
The laptop just about worked with Fedora-21.
It is more or less unusable with Fedora-22,
and completely useless with Fedora-23 beta.
Is there any possibility that it might work with some future version
of Fedora KDE?
Or should I resign to using it as a Windows machine,
which needless to say works perfectly on it.
gayleard /at/ eircom.net
School of Mathematics, Trinity College, Dublin
besides that dialog appears always when use a VMware machine i have it
now repeatly after login and autostarting Firefox, Kopete and SSH-Agent
before press any key
the "deacticate all.." still don't work
i really have enough of that stupid behavior that "show desktop" get
completly reverted when you do *anything* afterwards - the whole purpose
of "show desktop" is to get a ton of open windows minimized and bring a
specific one in the forgeround - the current behavior makes the whole
desktop unusable all day long
well, "show desktop" to rename a file in a folder-view reverting "show
desktop" is just a joke and when the cursor still is there to rename the
previously chosen file and you click the file get opened because
folder-view no longer respects the "Open with double click" settings of
P.S.: which upstream genie decided to come up again with the blue
shadows around windows while at the same time remove the option to
disable that which existed in KDE4? that's nice in the context "look how
cool we are" but annoying and boring after a few days and it's diversionary
I was wondering what the plan for releasing KDE updates in F22 was
following the F23 release?
IIRC, in the past, KDE updates for Fn used to stop when F(n+1) was
released, but F22 could certainly do with continuing KDE updates. Its
not convenient for us all to update to F23.
ah, I see now, yes, that's definitely a problem. :-/
From: kde-bounces(a)lists.fedoraproject.org <kde-bounces(a)lists.fedoraproject.org> on behalf of Kevin Kofler <kevin.kofler(a)chello.at>
Sent: Sunday, October 4, 2015 6:56 AM
Subject: Re: Korganizer does not autostart
Rex Dieter wrote:
> Hrm, I was assuming that plasma5 (still) supported X-KDE-autostart-
> condition. Do you have evidence to the contrary?
Sure, it supports it (I think), but that won't do any help because
KOrganizer is a KDE 4 application and writes to the old settings location
(.kde/share/config) whereas Plasma 5 only looks in .config.
kde mailing list
New to KDE4? - get help from http://userbase.kde.org
I am on Fedora 22, fully updated.
When I start KOrganizer manually, it works fine and there's a systray
entry for the reminder daemon.
The setting "start reminder daemon at login" is enabled in its
But at next login, it does not start. I have to manually start KOrganizer.
In system settings, I've configured for "Start with an empty session",
but that's how it has always been and KOrganizer used to auto-start.
In 'Autostart' tab, KOrganizer is not included, but again, I never had
to add it manually in previous versions.
Is this a bug? Or am I missing something?
Thanks and regards,
Syam Krishnan C.R.
well, wwith the latest updates some things eems to be better, still lags
but not that long, but krunner crashs randomly and given that the
startmenu is just unusaebale without lancelot now breaking ALT+F2 is a joke
am i really the only person who loved lancelot because oyu did not need
to went through the whole strcuture for starting 5 entries of the same
submenu (like 5 vnc-connections to different testing windows or other
testing virtual machines in the network)?
starting krunner manually works ometimes for a while (the need to keep
the terminal open is still a joke - in case of lancelot not refreshing
menues it was no problem for years to tpye "killall lancelot followed by
ALT+F2 lancelot in a running session)
QObject::connect: No such signal
QObject::connect: (receiver name: 'Activities')
I/O warning : failed to load external entity
I/O warning : failed to load external entity
QSocketNotifier: Invalid socket 6 and type 'Read', disabling...
QSocketNotifier: Invalid socket 9 and type 'Read', disabling...
QSocketNotifier: Invalid socket 12 and type 'Read', disabling...
QSocketNotifier: Invalid socket 14 and type 'Exception', disabling...
The X11 connection broke (error 1). Did the X11 server die?
KCrash: Application 'krunner' crashing...
KCrash: Attempting to start /usr/libexec/drkonqi from kdeinit
Unable to start Dr. Konqi