Hi, all --
I'm running Leap 15.2 (and this has been happening for a while), and
after a round of updates I have to go back to /etc/profile.d and
wipe out files that I don't want (alias.bash + ls.bash in particular).
Different from adding my own run commands to profile.local.sh thereunder,
I want to NOT get the stock stuff.
Is there any way to keep them from being dropped again so that I don't
have to deal with this over and over? *sigh*
TIA & HAND
:-D
--
David T-G
See http://justpickone.org/davidtg/email/
See http://justpickone.org/davidtg/tofu.txt
Hello Everyone:
Yesterday i try to update my tumbleweed system. I perform zypper dup.
The progrm download 8000 packages and when is installing the package number
1000 aprox i made a shutdown by mistake.
Today i write zypper DUP again, and only download and update 107 packages
remaining 6900 downloaded but not installed.
What i can do to tell to the zypper that install all remaining packages?
Best Regards
Christian.
--
Be Free, Be Linux
I don't use Apparmor (installed by default), so I would like to remove it.
There is an Apparmor Pattern which when deleted will remove package
patterns-base-apparmor, but many apparmor packages remain. It appears
all the apparmor packages (except for libapparmor1, a dependency for
systemd) can be individually deleted by YaST, which is what I would prefer.
Is that safe to do?
TIA!
--dg
15.3/Plasma
Hello,
I'm trying to include a picture into an article on the openSUSE-Wiki.
I go to the upload box, select a local file (.png, with rw access), confirm
that it is my work and hit 'upload'.
Result:
Something went wrong
The path at which the stashed file should have been found was invalid.
Are special authorisations required to upload pictures?
Cheers
Axel
Tumbleweed 20220216
NVIDIA GF106 [GeForce GTS 450]
nvidia-computeG04-390.147-51.1.x86_64
kernel-firmware-nvidia-20220119-1.1.noarch
x11-video-nvidiaG04-390.147-51.1.x86_64
nvidia-glG04-390.147-51.1.x86_64
nvidia-gfxG04-kmp-default-390.147_k5.16.8_8-51.2.x86_64
unloaded: fbdev,modesetting,nouveau,vesa
resolution: 1: 1920x1080~60Hz
2: 1920x1080~60Hz
kinfocenter -> graphics -> x-server
provides with one or two monitors attached which are both
1920x1080
5120x2104 pixels (1605x668 millimeters)
3200x2104 pixels (1003x668 millimeters)
with kernel 5.16.5
3840x1080 pixels (1204x343 millimeters)
X display doesn't use ~/.xinitrc
xrandr --output HDMI-0 --auto --output DVI-I-3 --auto --right-of HDMI-0
HDMI-0 is displayed right of DVI-I-3
booting with nomodeset or
initcall_blacklist=simpledrm_platform_driver_init
does not correct display
announced on opensuse-factory by DimStar
* Linux kernel 5.16.8, with full drm support in earlyboot; this will
be disabled again with kernel 5.16.10
will this correct the X display problems?
ps: also (may not be related)
"Selected font has no non-zero height for ISO-8859-1 encoding" error is
provided when trying to open an xterm instance (also tkremind display is
blank)
xterm fails unless I change the font via systemsettings5
noto-sans 10pt
changed to Nimbus Sans L 10pt
applied and then back to noto-sans 10pt
and it works
--
(paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri
http://en.opensuse.org openSUSE Community Member facebook/ptilopteri
Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc
Hi,
after weekend I updated my work TW machine, and MS Teams doesn't start
anymore... No message in console, just white square on screen and not working
tray icon... I'm on KDE if it matters... Any idea what could go on?
--
Vojtěch Zeisek
https://trapa.cz/
Komunita openSUSE GNU/Linuxu
Community of the openSUSE GNU/Linux
https://www.opensuse.org/
From: Vojtěch Zeisek
Sent: Monday, February 21, 2022 10:47
To: support(a)lists.opensuse.org
Subject: Teams broken again?
Hi,
after weekend I updated my work TW machine, and MS Teams doesn't start
anymore... No message in console, just white square on screen and not working
tray icon... I'm on KDE if it matters... Any idea what could go on?
Same here.
Found this: https://docs.microsoft.com/en-us/answers/questions/548771/teams-fails-to-lo…
See towards the end of the thread... several users are reporting issues again since a few days.
Cris
Good morning,
I would like to learn about best practices on how to automate updates for Leap
and trigger a reboot if required.
I understand transactional update & rebootmgr should only be considered for
MicroOS.
In general, a one-liner like
zypper up -l -y && shutdown -r 0
could be triggered by cron job (or systemd-timer).
In case there are conflicts this will most likely get stuck.
I feel for a server an update should be triggered manually, dependng on
requirement and available time-window
Another option, mainly for desktop systems, could be a similar script that
runs as part of the shutdown process.
Any other suggestions/comments?
Thanks
Axel
