So I spilled some hot chocolate on my keyboard
It sticks
What's your best advice on cleaning it?
--
Bob Rea
www.petard.uswww.petard.us/blog
America, it was a wonderful country
Til they took it private
and made it a theme park of itself
Hi all,
I would like to use on Tumbleweed/KDE minidlna to stream
multimedia/pictures to the TV . I installed it from snap, and made
some modifications to the minidlna.config file in /etc. However, I am
not able to use it. When I ask its status, I get:
berci@linux-h9qy:~> systemctl status minidlna
? minidlna.service - MiniDLNA is a DLNA/UPnP-AV server software
Loaded: loaded (/usr/lib/systemd/system/minidlna.service;
enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Tue 2020-11-24 19:48:53
CET; 42s ago
Process: 15219 ExecStart=/usr/sbin/minidlnad -S (code=exited,
status=255/EXCEPTION)
Main PID: 15219 (code=exited, status=255/EXCEPTION)
Could you help what could go wrong?
Thanks: Albert
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
Hello users-list @ opensuse
anyone using current wireguard on current opensuse leap 15.2?
I see very few posts on the list server archives. I read about some
new version 0.3.1 windows client. I suppose wireguard on the server
side is linux only?
How current and up-to-date is wireguard server side on opensuse leap 15.2?
I like the archlinux documentation pages for a lot of topics
<https://wiki.archlinux.org/index.php/WireGuard>
I fail to find some version number or understanding of the linux side
wireguard in terms of release or version numbers. does 0.3.1 on the
windows client side has got to do anything with the server side
version?
Also wondering why
<https://software.opensuse.org/package/wireguard>
apparently leap 15.1 has some official wireguard package that has a
higher version string or date string that leap 15.2 or even
tumbleweed?
I am also trying to dig into site-to-site (both linux) connections.
TY.
Hi users @ list opensuse,
maybe I am old school, but from old days of mails and usenet, I always
came from the concept to post URLs, web-addresses and clickable links
into like angle-brackets < > and make various mail clients and places
be able to fully recognize and respect especially very long URLs URIs
and more. Maybe I never fully grasped the concept, or had some
misunderstanding of them to begin with.
As far as I can now tell, the new HyperKitty (?) mechanism on
https://lists.opensuse.org/archives/
apparently does not render clickable html links when browsing list
posts e.g. on the new archives areas
> https://lists.opensuse.org/archives/list/users@lists.opensuse.org/
vs
> <https://lists.opensuse.org/archives/list/users@lists.opensuse.org/>
Now I was wondering how one should post long links and more safely. I
am writing via google gmail web interface. But also how about other
inbound delivery means e.g. smtp clients etc? What are the exact
technical details about how stuff becomes rendered on this HyperKitty
thingy?
Also, some while ago, I tried to attempt to log-in or register on the
web interface of the lists.opensuse.org server, but it then denied or
spoke about not having implemented accounts yet or something. These
days, it seems that one could log in to it with all sorts of
credential providers, opensuse id, open id, github, gitlab, stack
exchange, google log on.
<https://lists.opensuse.org/accounts/login/>
Registering apparently is still blocked.
<https://lists.opensuse.org/accounts/signup/>
Does this mean we can somehow claim our own account that we already
use (email address as sender) to be able to log into the web interface
as well and post there instead of our own mail clients or mail
concepts? or when will this be available?
TY
Hello,
Since about a month, my Xfce4 desktop crashes when I resume from
hibernate (to disk) overnight.
On good days, the browser window is just black. Killing the chrome
process with --type=gpu-process fixes this.
Anyone else with the same problems? Any suggestions how to proceed?
I tried to enable debug logging for Chrome but I can't see any obvious
problems in the output (see attachment).
Involved versions:
Name       : nvidia-gfxG05-kmp-default
Version    : 450.80.02_k5.3.18_lp152.19
Release    : lp152.37.1
Architecture: x86_64
Name       : google-chrome-stable
Version    : 87.0.4280.66
Release    : 1
Architecture: x86_64
Name       : xfce4-panel
Version    : 4.14.4
Release    : lp152.1.3
Regards,
--
Aaron "Optimizer" Digulla a.k.a. Philmann Dark
"It's not the universe that's limited, it's our imagination.
Follow me and I'll show you something beyond the limits."
http://blog.pdark.de/
Hello list,
i have some process running in a user context. It came via crontab
entry in the users crontab. I see it via
crontab -l
@reboot "/home/username/path/scriptfile" parameter
This spawns a process running after a reboot of the machine. This is
perfectly fine. I created that user and disabled its interactive logon
means, I guess. The user has no password methinks, and the etc/shadow
file has the exclamation mark right after the username:! at the
beginning.
So this script needs to be called again during a shutdown of the
machine, automagically, with a different parameter, to make that
running application terminate gracefully, not mess up the disk and
system and for the machine be happy and reboot, shutdown et al
normally.
Right now, I only su - into root, then su username and then execute
that process or script with parameter to make it shutdown. The user
needs to wait for the process to return back to the shell with its
result that it shut down normally, or to generate its own error codes
or whatnot. So if this would be automated, the actual shutting down
needs to wait for this process to terminate. it always terminates. at
least thats what i experienced.
anyways. so how would I put this into a very simple on-shutdown
concept? I have looked at crontab, but that only knows such stuff as
that @reboot alias or means according to manpages.
The opensuse leap machine has systemd running fine I guess, although
the machine is an older upgraded machine and probably has seen many
previous opensuse releases. systemctl runs fine though.
As far as I have figured by now, is maybe, that the user login
effectively being disabled (! mark in shadow...) the command
systemctl --user status
ran from inside the user (su - first, then: su username , then
executed from there) does not work, it always comes up with an error
message about files or access stuff?
systemctl --user status
Failed to connect to bus: No such file or directory
the user is a normal member of gid=100(users) and groups=100(users)
I am trying to follow along this thread for example on the opensuse forums:
https://forums.opensuse.org/showthread.php/538796-How-to-start-appimaged-vi…
> https://forums.opensuse.org/showthread.php/538796-How-to-start-appimaged-vi…
as an example to begin with.
as a different user, which can log-in to that machine, via ssh for
example, the systemctl --user status
shows results and proper output.
So my gut feeling was that this is gonna be a show stopper further
along the road when following that thread and means to execute a
simple stuff via systemd in a user context.
The thing is, I want to keep this as simple as possible, if possible.
the inverse thing of crontab @reboot would suffice for me I say, but
apparently there is no such thing.
and I dont have a systemd user level service/config file for this
application made, as it created this crontab and @reboot itself etc.
any best practices for this? maybe I am using this deactivated local
user on the linux machine in wrong ways? the user doesnt need to be
used for anything else but to run its script and app it is creating,
it only needs disk and network resources, no gui stuff, except for
shell output if at all. well. then again I am not an expert in this
stuff.
just simply trying to run a certain command properly at shutdown time,
in that users context. thats all.
TY.
Opened up Thunderbird and got the message, "The RETR command
did not succeed. Error receiving a message. Mail server pop.online.net
responded: Message expunged."
This happened twice today; I have never seen it before. Where is the
problem, and is this something I should be concerned about, and if
so, what should be done?
Thanx for your interest--doug
On 2020-11-20 5:45 p.m., Herbert Graeber wrote:
>>> You need a certificate and key and add them in /etc/sysconfig/unifi.
>> Where would I find those?
> You shall generate your own.
>
How do I do that?
tnx jk
I just upgraded a machine to Leap 15.2 only to discover that apparently
openSUSE has dropped support for the nvidia 340 driver; it is not in the
15.2 nvidia repo. Yet according to nvidia, the driver supports the 5.3
kernel. The card is a 9800GTX+ - yes it's old but it still works quite
well on 15.1.
Can anyone confirm that dropping support for this driver version is
intentional, although it is still available for download from nvidia?Â
Since it is not in the repo, I suspect that the download (aka "hard
way") version will have the same issue, too. (And besides, I really
really don't want to get on the re-installation merry-go-round.)
I'd like to know before just assuming nouveau is my best (only) option
with this card.
TIA,
--dg
