-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
Since a recent update I notice something different in Thunderbird that I
don't like (Using version 91.5.0 on Leap 15.3).
I'm reading the subject lines in the top panel (I don't know its name). It
shows the from, to, subject, date... I go up and down using the wheel on
the mouse. I locate an email I want to read, so in the bottom panel I have
the email. I want to browse it, so I poise the mouse over the panel and
move the wheel... nothing happens. I have to click on the panel first,
then move the wheel, then the mail read panel goes up or down the email.
This did not happen before, the window would follow the wheel as soon as I
move the wheel. On other programs it works, it is just Thunderbird that
has changed behaviour. I thought I would get used to the change, so I
have waited two weeks, but no, it is still a nuisance.
Is there some configuration to change back to the old behaviour?
Is this a bug?
- --
Cheers
Carlos E. R.
(from 15.3 x86_64 at Telcontar)
-----BEGIN PGP SIGNATURE-----
iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCYglXAxwccm9iaW4ubGlz
dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVZsgAn11bqmgJlp1QlAEP/kC/
C0MA0JHoAJ4nwROz4HZqiT+JhwZ91Jeit3eILg==
=P4p1
-----END PGP SIGNATURE-----
Originally installed a test 15.3 system as a simple server, no graphics environment. It's been maybe a decade since I had to install and
configure an X system from scratch.
Added X11 via Yast. Accepted the required additions.
systemctl start xdm.service fails. Due to "dependencies". Did find a few services it needed that were not installed by YAST.
Still failed to start.
Eventually I found it was failing due to "not configured". Suse docs seem to say it does "not normally need to be configured"
and should just work.
I've so far found no configuration utilities to assist. At least none seem to be installed.
Any assistance is appreciated.
joe a.
Hello:
This occurs in openSUSE Leap 15.3 with its default cups installation.
The printer is an Epson AL-M300II connected with USB cable.
There are some documents I cannot print, eg invoices.
Other regular pdf files print OK.
When opening a problematic document with Okular, it says:
"This document has embedded files. Click here to see them or go to File
-> Embedded Files.
This document has forms. Click on the button to interact with them, or
use View -> Show Forms.
This document is digitally signed."
When I print the document, the printer's green led is blinking, but
nothing is printed.
CUPS acces_log file says:
localhost - - [09/Feb/2022:18:14:05 +0100] "POST /printers/epson_usb
HTTP/1.1" 200 605 Create-Job successful-ok
localhost - - [09/Feb/2022:18:14:05 +0100] "POST /printers/epson_usb
HTTP/1.1" 200 1205055 Send-Document successful-ok
lpstat reports a successful print job:
epson_usb-30 user 1205248 Wed 09 Feb 2022 06:14:20
PM CET
What to check or how to fix this?
Thanks,
Istvan
Hi all,
I 've been using Stellarium as a planetarium software and also for
demonstration purposes. For some time, it is blinking, flickering etc,
cannot be enjoyed at all.
This is an elder ASUS laptop with TW and KDE (and XFCE). Is there
somebody out there who also uses Stellarium and observed this unwanted
flickering.
Any idea is welcome.
Thanks, Albert
On a machine I did a "zypper dup" to update from 15.2 to 15.3, the 15.3
does not have sound at bootup.
Sound card is:
# lspci | grep -i audio
16:00.4 Audio device: Advanced Micro Devices, Inc. [AMD]
Starship/Matisse HD Audio Controller
The 15.2 works fine.
15.2:
#dmesg | grep -i audio
[ 0.502138] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
[ 9.892740] snd_hda_codec_realtek hdaudioC0D0: ALC1150: SKU not ready
0x00000000
[ 9.894094] snd_hda_codec_realtek hdaudioC0D0: autoconfig for
ALC1150: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:line
[ 9.894980] snd_hda_codec_realtek hdaudioC0D0: speaker_outs=0
(0x0/0x0/0x0/0x0/0x0)
[ 9.895870] snd_hda_codec_realtek hdaudioC0D0: hp_outs=1
(0x1b/0x0/0x0/0x0/0x0)
[ 9.896760] snd_hda_codec_realtek hdaudioC0D0: mono: mono_out=0x0
[ 9.897662] snd_hda_codec_realtek hdaudioC0D0: dig-out=0x1e/0x0
[ 9.897662] snd_hda_codec_realtek hdaudioC0D0: inputs:
[ 9.897663] snd_hda_codec_realtek hdaudioC0D0: Front Mic=0x19
[ 9.897664] snd_hda_codec_realtek hdaudioC0D0: Rear Mic=0x18
[ 9.897664] snd_hda_codec_realtek hdaudioC0D0: Line=0x1a
[ 9.912613] input: HD-Audio Generic Front Mic as
/devices/pci0000:00/0000:00:08.1/0000:16:00.4/sound/card0/input4
[ 9.913543] input: HD-Audio Generic Rear Mic as
/devices/pci0000:00/0000:00:08.1/0000:16:00.4/sound/card0/input5
[ 9.914476] input: HD-Audio Generic Line as
/devices/pci0000:00/0000:00:08.1/0000:16:00.4/sound/card0/input6
[ 9.915416] input: HD-Audio Generic Line Out as
/devices/pci0000:00/0000:00:08.1/0000:16:00.4/sound/card0/input7
[ 9.916344] input: HD-Audio Generic Front Headphone as
/devices/pci0000:00/0000:00:08.1/0000:16:00.4/sound/card0/input8
On 15.3:
#dmesg | grep -i audio
[ 0.132048] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
[ 5.112574] hdaudio hdaudioC0D0: Unable to bind the codec
Yet when I go into Yast and reconfigure the card, the sound works until
a reboot happens. What am I missing?
Mark
In recent weeks/months I've noticed that if I enter the Yast "Boot Loader Settings"
"Bootloader-Options" tab, there is a long pause because yast immediately
refreshes/downloads all the zypper repo data. Why does changing the boot
loader options require a repo refresh?
And while I'm on the subject of repos, I'm sometimes asked whether I want
to accept new keys (like just five minutes ago). I always answer yes, but is there
an easy way to tell what answer I should give? Or perhaps a way to get zypper
to authoritatively check or re-check keys?
Thanks.
Michael
I am running OpenSuSE 15.3, x64 I am a bit confused, I noticed on Mon
Feb 1, that I received a number of updates, many of which involved samba
bringing it to version
4.15.4-git.324.8332acf1a63150300.3.25.3-SUSE-oS15.0-x86_64. Today (Feb
5) I noticed that autofs on other systems was failing and I traced the
problem back to samba which was failing to export shares because smbd
had crashed. The smb.log file showed this error -
[2022/02/05 18:45:01.852699, 0] ../../source3/smbd/server.c:1734(main)
smbd version 4.15.4-git.324.8332acf1a63150300.3.25.3-SUSE-oS15.0-x86_64 started.
Copyright Andrew Tridgell and the Samba Team 1992-2021
[2022/02/05 18:45:01.867593, 0] ../../lib/util/become_daemon.c:120(exit_daemon)
exit_daemon: daemon failed to start: Samba failed to init printing subsystem, error code 13
Googling this error message lead me to this bug report -
https://bugzilla.opensuse.org/show_bug.cgi?id=1191532 which seems to be
all about fixing this error. The bug is marked resolved/fixed and the
last entries (on Mon Feb 1) are about releasing the fix. So I assume
that the release of this fix corresponds to the updates I got on that
same day. Yet this is when this particular bug started showing up on my
systems!
I have dropped back to version
4.13.13-git.539.fdbc44a85983.20.2-SUSE-oS15.0-x86_64of samba and all is
well again, both autofs and my printers are working again. So what
gives? Did this update fix, or not fix this bug? I admit I do not grok
about 95% of the bug report (didn't take the time to do so) but it seems
pretty coincidental that the bug was was marked as resolved and then
released on the very day I got updates that broke my smbd daemons.
Please don't be harsh on me, I am simply trying to understand what is
going on and would appreciate any suggestions/advise on what to do about
updating Samba.
Marc...
--
*"The Truth is out there" - Spooky*
*_ _ . . . . . . _ _ . _ _ _ _ .
. . . _ . . . . _ _ . _
_ _ . . . . _ _ . _ . . _ . _
_ _ _ . _ . _ . _ . _ . *
Computers: the final frontier.
These are the voyages of the user Marc.
His mission: to explore strange new hardware.
To seek out new software and new applications.
To boldly go where no Marc has gone before!
(/This email is digitally signed and the electronic signature is
attached. If you know how, you can use my public key to prove this email
indeed came from me and has not been modified in transit. My public key,
which can be used for sending encrypted email to me also, can be found
at - https://keys.openpgp.org/search?q=marc@marcchamberlin.com or just
ask me for it and I will send it to you as an attachment. If you don't
understand all this geek speak, no worries, just ignore this explanation
and ignore the signature key attached to this email (it will look like
gibberish if you open it) and/or ask me to explain it further if you like./)
