Like I have said earlier sometimes my system wakes up from suspend or screen
off (I can't say for sure) it never reaches screen locker. I see black screen
and mouse pointer. In some places mouse pointer changes to input cursor. Other
than that my only recourse is to restart system.
I can't keep losing my data because Fedora or KDE fails to work.
My questions is I am not even sure which log file should I be looking into to
track possible problem if I am to continue using Fedora.
I am on a fully upgraded F24.
I use Save Session with "Restore manually saved session" to try for a
known desktop configuration on login. I say "try" because in various
ways it doesn't completely work, as discussed in other threads. To
attempt to get round some of the issues I also have a number of
programs in Autostart, but it's never been clear to me what relation if
any there is between these two things.
Case in point: if I have program Foo in Autostart, but also save a
session with Foo running, is the desktop after a new login expected to
show two Foo instances or one (or none because of a conflict). Or is
this simply not defined? Or does it depend on Foo itself?
There is/was a discussion on the development list today regarding a problem
running dnf upgrade from a terminal window under a DE, e.g. GNOME or KDE.
of surprised me was that apparently the "official" Fedora stance is use the
GNOME GUI updater
which updates via reboot and that it is unsafe to do it from a terminal
within GNOME or KDE.
I have never encountered any issue so was trying to obtain some stats about
exactly what the risk/benefit is... the only thing I could find was within
the following thread:
"... Updating online works 99.8% of the time. The 0.1%
time it will corrupt random bits of your file-system, and 0.1% of the
time it will leave you vulnerable to the security issue you thought
you just "fixed". The only way to fix this so that online updates are
safe is to redesign the centralised shared package model we use for
distributing applications. The workaround is to use offline updates..."
Also, as I understand it (and this may have changed) is that within
KDE there is no "offline" update solution. Apper basically does it
the same as issuing the command from a terminal.
So, what is the recommended KDE solution for this? I stated on the
development list I thought rebooting for every update was basically
sacrificing system availability for what appears to be a very minor
risk. Perhaps I'm missing another point or am completely off base
here. That is why I'm wanting to know what other KDE users think of
this. I've been entering DNF/YUM UPGRADE from within konsole for many
years and have never encountered any corruption issues.
I try to keep up-to-date with things, but I completely missed this,
and apparently it was introduced in F18.
Using the Status and Notifications widget used to show the battery
level in my Bluetooth mouse. Now it just says there are no batteries.
It's a desktop, so there are indeed no batteries in the system, but
there are in the mouse.
What am I missing?
I'm having problem with browsing Samba shares on my network with Dolphin
I always used to enter in Network -> Samba shares in dolphin left panel
and see a list of servers with samba shares on my network, but now I get
"unable to find a workgroup on your local network. It may be due to
firewall problems" (a rogue translation from Italian).
Now, I've not changed anything in my firewall and I have SMB client
ports opened. In fact, if I point directly to a server IP I can browse
it (for example smb://192.168.1.200 it shows my server), so I don't
think it's a firewall problem.
Is anyone experiencing the same issue?
How is crash detection supposed to work under KDE?
I ask since a crash of ktorrent often gets detected when I click on a magnet link.
ktorrent isn't crashing. So what and why is it being seen as such?
This is on an F24 system and while I'm not running plasma-5.8.0 from copr it was happening
prior to enabling that repository.
You're Welcome Zachary Quinto