System crashed during the second part of upgrade, where files were
reporting "done." Crash occurred at
966/2162 Installing shim _15 + git47-222222222.2.x86_64
Rebooted to blank (black) screen with message as follows:
GNU GRUB VERSION 2.04
Minimal BASH-like line editing is supported. For the first word, TAB
lists possible command completion.
Anywhere else TAB lists possible device file completetions.
Is it possible to save this, and if so, how? Have left computer in this
condition awaiting answer.
At boot, my /tmp directory is being cleaned out. However, /var/tmp/
still has ~3000 folders, containing ~300 files. All but 2 of the
folders are named zypp.*, created over the past 2 years and appear to
contain mostly public/private keys and associated files.
My /etc/tmpfiles.d/tmp.conf looks like (as recommended on the Forums):
D! /tmp 1777 root root 1d
D! /var/tmp 1777 root root 1d
So it would appear that the first line for /tmp is being used (I presume
by a systemd unit), but the second line is not. My
d /tmp 1777 root root -
d /var/tmp 1777 root root -
which I have understood is the installed default and is not used when
tmp.conf exists under /etc/tmpfiles.d/ (?).
What am I missing?
Leap 15.2 w/KDE
The HP_LaserJet_Pro_M201dw installed and worked via YaST, but now is
giving me trouble: if I send it a print job, the panel light goes on and
and the green printer horseshoe light come on but the printer doesn't
lpstat shows the file has been sent:
HP_LaserJet_Pro_M201dw-363 doug 15360 Sun 28 Mar 2021
03:17:28 PM EDT
How do I trouble shoot this and fix it, please?
on my notebook I use a small script to handle the connected graphics ports via
xrandr. This script has to be run before sddm-greeter gets started.
For a long time now the script was started from [/usr]/etc/X11/xdm/Xsetup,
because I couldn't find a better place for it.
It is annoying, though, that Xsetup gets overwritten with every update of xdm.
What's more annoying, is the fact, that no .rpmsave file is created during
update, despite the fact I had modified the file.
Is there a better/proper place for a script like that, where it can survive an
Something like Xsetup.d/?
Hi, all --
I'm still a bit hung up on systemd :-( I've created a simple unit file
diskfarm:~ # cat /etc/systemd/system/disks-timeout-set.service
Description=Set disk timeouts if needed
which calls the script, which runs and exits. The script runs happily,
and I can even
it with apparent success. I've tried to enable it
diskfarm:~ # systemctl enable disks-timeout-set.service
Failed to enable unit: Invalid argument
without any luck, though.
1) A service is really what I want for a simple run-and-exit script,
right? No other unit type makes sense.
2) So what's the error and how do I debug? I've surfed like crazy, but
everything presumes a daemon and all of the "enable" examples always
TIA & HANN
Somehow I have accidentally set Thunderbird to open without a password.
It's wonderful! It was a royal pita! Now in case it changes back, or if
dup changes it back, I'd like to know how to do it on purpose. I have no
to need a password for my email. I have no secrets on it, and no porn. If
someone should get in and read it, so what? And there's nobody here
to read it but me anyway.
(my system details are in mi sig.)
Since some weeks I notice a wrong battery parameters measurement,
despite it being apparently healthy and still owning its normal duration
I tried to reset it and the Linux energy management as suggested by
several sources by discharging and recharging it, as well as by pressing
the computer power button for 15 seconds, without success.
The problem is that kernel reads the full-charged value a lot over the
battery design capacity for this reason it looks as the charging never
See the picture: https://1drv.ms/u/s!AoEY5BnM7ZYpbaHdbSRF2zgMcQM?e=lwNo6T
Anybody have faced similar issue?
And any eventual solution for that?
Build: openSUSE Tumbleweed 20210321
Desktop: XFCE (4.16.0)
A slightly off-the-wall request, but does anyone know how to tame the
mouse/peripheral battery nags under Plasma with Leap 15.2?
I've a Logitech M705 mouse which has 2xAA 2450mAh rechargeable
batteries. Somewhere in the Leap 15.1 update cycle (I think) I started
getting nags about low-battery in the mouse. At first I thought "how
helpful" as the same type of geniunely flat batteries in my wireless
keyboard sent me on an epic wild-goose chase a few years ago (hint, no
probs in the graphic driver). Twice. Here's the notification message:
Mouse Battery Low (10% Remaining)
The battery in ("Marathon Mouse/Performance Plus M705") is running
low, and the device may turn off at any time. Please recharge or
replace the battery.
I'm guessing the slightly lower voltage in low self-discharge
rechargeable batteries is confusing upower, but I can't find where/if it
can be tuned. The level is reported regularly by the mouse itself, as it
returns from low power/auto sleep mode. Yes, I've tried a fresh set of
rechargeables, after their 20hr topup. Regular AA's are rated for three
years in the mouse, so would expect at least 12 with high capacity
upower --dump reports (for this device):
model: Marathon Mouse/Performance Plus M705
power supply: no
updated: Fri 26 Mar 2021 18:07:57 GMT (12 seconds ago)
has history: yes
has statistics: yes
percentage: 10% (should be ignored)
10% is clearly wrong and something needs re-calibrating.
There seems to be no way to change the preference for incoming pdf
files. Okular has not been able to read a couple of
recent pdf attachments. I wish to make the preference for pdf ALWAYS
Master PDF Editor 5, which can read the files OK.
How do I get to a place where I can change this preference?
Thanx for your help--doug
Hi, all --
I have an existing Leap 15.2 system with an nvme SSD, and I'm happy with
how it boots. It does not, such that I have ever noticed, exhibit this
However, I have also just built another Leap 15.2
diskfarm:~ # grep . /etc/SUSE-brand /etc/os-release ; uname -a
/etc/SUSE-brand:VERSION = 15.2
/etc/os-release:PRETTY_NAME="openSUSE Leap 15.2"
Linux diskfarm 5.3.18-lp152.63-default #1 SMP Mon Feb 1 17:31:55 UTC 2021 (98caa86) x86_64 x86_64 x86_64 GNU/Linux
system on a single SATA SSD, and as it boots is reports
[ slider ] A start job is running for dev-disk-by\x2dlabel-System.device (nns / 1min 30s)
that always runs to the 90-second timeout and then fails. What is that,
and how do I make it not?!?
TIA & HAND