kwin and plasma configuration files list
by Robin Laing
I am having weird issues on my system and it is pointing to a
configuration issue. May be related to old config files or just a
really weird configuration that is causing the issues.
Is there a list of all the config files used for plasma and kwin that
can affect keyboard operation and screen issues.
I have had weird lockups between accounts. Full screen freezing on some
accounts requiring a reboot.
Moving from SDDM to GDM has stopped the weird black screen on logouts.
The most recent issue is no keyboard operation in one account if
Clementine is open. Works okay in other accounts.
I really don't want to wipe out all the configuration files again as I
have done in the past.
Robin
3 years
Re: [Test-Announce] Fedora 34 Candidate RC-1.1 Available Now!
by Adam Williamson
On Thu, 2021-04-22 at 03:00 +0000, rawhide(a)fedoraproject.org wrote:
> According to the schedule [1], Fedora 34 Candidate RC-1.1 is now
> available for testing. Please help us complete all the validation
> testing! For more information on release validation testing, see:
> https://fedoraproject.org/wiki/QA:Release_validation_test_plan
Hey folks! This is the real-deal first RC for F34 Final, with all known
blockers fixed. We only have a short time before the go/no-go meeting,
but I am going to see if we can push that to Friday without impacting
the schedule. In the meantime, please do help test it as much as
possible. Thanks!
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
3 years
ssh ask pass on F34 not working on entry
by José Abílio Matos
For a long time I have a script in ~/.config/autostart-scripts/ksshaskpass
#!/bin/sh
export SSH_ASKPASS=/usr/bin/ksshaskpass
ssh-add xxxxx_key < /dev/null
For F34 this is not working out of the box.
That is after entering the plasma session using ssh always asks for the pass
phrase.
On the other hand if I run the last line directly, after the startup stage,
then the agent is added and it works from there.
It almost looks like that kwallet it is not opened when the autostart script
runs.
BTW in terms of F34 I have two other small nags. The first is that some
windows forget their placement and are sent to the first desktop when booting.
The other issue is that, at least for this account, plasma (wayland) freezes
the machine while gnome (wayland) works. Although it had some issues there was
no freeze in Fedora 33.
Where can I find further informations to debug these issues?
Best regards,
--
José Abílio
3 years
Pulseaudio - mutliuser issues.
by Robin Laing
I use multiple accounts and recently a major headache has occurred with
pulseaudio. My problem started last weekend.
From what I have found so far is that one account takes over a media
output device.
On my present system, I use the onboard sound for all audio but the HDMI
says that it has audio. Both computer monitors do have an audio output
jack. Sound card is connected to 5.1 speaker system.
On average, I have two or three accounts open for work and private stuff
which has worked for many years with no problems. Recently, the issue
has arose that the one account I use for general day to day stuff has
taken over the sound card for only it's usage.
The second account that is for work has tried to use the HDMI output but
cannot even see the sound card as an option. If I restart pulseaudio,
then no devices are found until I at least lock the account and log back in.
If I open a third account which I have to use for online related work, I
have no sound device to use until I do a reboot.
I have looked at trouble shooting this but I am lost. Most online
troubleshooting help is geared to a single account being used.
To add to the issue, I use mplayer as my main player and in the second
account, it refused to work if I had tried to restart pulseaudio. It
works with no sound if the HDMI/Display port is the only device as there
are no speakers It is not an mplayer configuration as I have cloned the
configuration from the account that works.
No changes to the /etc/pulse/* files since last November which would
have been the upgrade to F33.
Where do I start?
Robin
3 years
Disk authentication required to start up???
by Mark ＠ GMail
On starting up (or rebooting, obviously) this machine it always
presents me with a box with the heading
Authentication is required to mount WDC
WD20EARX-00PASB0 (/dev/sda1)
(screenshot attached).
I'm running the latest versions of everything (F33 workstation, KDE
5.20.5) presented to me but this has been happening for a long time, I
don't even remember how many Fedora versions (I started at F15 I
think).
It appears after the KDE login (I autostart KDE), but doesn't happen at
all if I simply log out of my KDE session and then log back in.
Normally I give it my password (not the supervisor password, though my
account is in the sudo-ers group) and carry on. To send this message I
have purposely *not* given it the password and haven't closed the
window, so it's still there but everything seems to function normally,
so it's even not true, the disk must be mounted (it's the only hard
drive mounted) so the authentication is *not* required. Just closing
the window seems to be fine, too.
Any idea what's being upset here?
TIA
3 years
