openSUSE Users

users@lists.opensuse.org

38 participants
132452 discussions

by Mark Hounschell

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

2 hours, 54 minutes

Bluetooth pairing, Leap 15.3/KDE-Plasma

by Peter McD

Hi, My USB-Bluetooth adapter can't pair with my bluetooth headset. It worked in Leap 15.2. The bluetooth assistant, i.e. the bluetooth applet searches for the headset, but doesn't find it. hwinfo (below) outputs much information, I hope I found the interesting bit. Any ideas? Peter --------------------------------------------------------------------- ============ start debug info ============ libhd version 21.72 (x86-64) [7688] using /var/lib/hardware kernel version is 5.3 ----- /proc/cmdline ----- BOOT_IMAGE=/boot/vmlinuz-5.3.18-59.5-default root=UUID=adea8b9e-b878-4afa-89c9-337797cc8b56 splash=verbose noresume mitigations=auto ----- /proc/cmdline end ----- ... 77: USB 00.0: 11500 Bluetooth Device [Created at usb.122] Unique ID: POWV.nQKjiuCfL84 Parent ID: k4bc.kNaPe9SZft4 SysFS ID: /devices/pci0000:00/0000:00:01.3/0000:01:00.0/usb1/1-9/1-9:1.0 SysFS BusID: 1-9:1.0 Hardware Class: bluetooth Model: "Cambridge Silicon Radio Bluetooth Dongle (HCI mode)" Hotplug: USB Vendor: usb 0x0a12 "Cambridge Silicon Radio, Ltd" Device: usb 0x0001 "Bluetooth Dongle (HCI mode)" Revision: "88.91" Driver: "btusb" Driver Modules: "btusb" Speed: 12 Mbps Module Alias: "usb:v0A12p0001d8891dcE0dsc01dp01icE0isc01ip01in00" Driver Info #0: Driver Status: btusb is active Driver Activation Cmd: "modprobe btusb" Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #86 (Hub) ---------------------------------------------------------------------

1 day, 3 hours

Boot loader 15.3

by James Knott

My ThinkPad had been configured to have the boot loader on sda3. In updating to 15.3, I accidentally put it on the master boot record on sda. This has created a problem with updates to Windows 10, which I also have on that computer. The major updates will choke if the computer doesn't boot from the Windows partition, so I'd use fdisk to change booting from sda3 to sda1. It would then boot directly into Windows, allowing he update to continue. After my mistake in updating, I can no longer do that. I have used the Yast Boot Loader to move the boot loader to sda3, but the problem continues, no matter which partition I choose to boot from. Any idea how to fix this? tnx jk

1 day, 5 hours

Mailing Lists

by Ianseeks

Whats happened to the list.opensuse.org/archives ? and Factory List? regards Ian -- opensuse:tumbleweed:20210609 Qt: 5.15.2 KDE Frameworks: 5.82.0 - KDE Plasma: 5.22.0 - kwin 5.22.0 kmail2 5.17.1 (21.04.1) - akonadiserver 5.17.1 (21.04.1) - Kernel: 5.12.9-1-default - xf86-video-nouveau: 1.0.17

1 day, 9 hours

SAMBA, Problem in SuSE Leap VERSION = 15.2, with "PRINT COMMAND ="

by Stefan Becker

openSUSE VERSION = 15.2 SAMBA Version 4.11.14-git.247.8c858f7ee14lp152.3.19.1-SUSE-oS15.0-x86_64 Greetings, this week I've installed a fresh SuSE 15.2 Server via DVD, and updated all services. This server would replace an existing old SuSE Server already in place. My problem is that the printer SHARE on the new Samba Server does not work. The file system shares [HOME] work fine, Just not any Printing shares that use "PRINT COMMAND =" as directive; in order to execute tailored script. My example is a simple PDF-Printer [pdf] printing = sysv comment = PDF Generator path = /tmp read only = no printer name = ps1 guest ok = yes printable = yes browseable = yes print command = /usr/local/lufa/mkpdf %s ~%u //%L/%u %m %I Being able to use "print command =" to submit to script is an important part of many solutions that I need to have in place. (The [PDF] share is just an example, I know that I could solve THIS differently.) Other file server shares like [HOMES] work fine. Just the "print command = " does not execute. Scripting to a log file shows no activity at all, and I receive no error messages, neither from the client nor from the samba server. Does anyone know how to debug the printing service. As to show if samba has a problem, or if the client is trying to submit printing at all. Setting "log level = 10" doesn't show me any usefull, at least any information that I can understand. I do know that "printing = cups" (using cups librarys) will suspend the "print command" completely, but does that mean that the "print command =" won't work at all with other "printing = " directives ? My printers otherwise use "printing = sysv", this has always worked. Can anybody help me with this or advise in what direction to pursue. my best regards, Stefan Becker LUFA Speyer My Script: --------- file: /usr/local/lufa # dir mkpdf -rwxr-xr-x 1 becker users 4299 14. Jun 12:25 mkpdf script: #!/bin/bash #/usr/local/lufa/mkpdf # samba-print-pdf cd /tmp/ ( echo "" echo Time: $(date +"%Y-%m-%d %H:%M:%S") echo Proc: $USER [ $UID ] echo Call: $0 echo File: $1 echo User: $2 echo Para: $3 , $4 , echo Para: $5 , $6 ) >> /tmp/mkpdf.log if [ "$1" = "" ] ; then exit 10 fi # .... the complete smb.conf : --------------------- [global] workgroup = HOME netbios name = SUE log level = 3 realm = HOME.DE passdb backend = tdbsam security = ADS ntlm auth = ntlmv1-permitted min protocol = NT1 interfaces = 127.0.0.0/255.0.0.0 192.168.10.0/255.255.252.0 hosts allow = 127.0.0.0/255.0.0.0 192.168.10.0/255.255.252.0 hosts deny = all bind interfaces only = yes printing = cups printcap name = cups printcap cache time = 750 cups options = raw guest account = nobody guest ok = no logon path = \\%L\profiles\.msprofile logon home = \\%L\%U\.9xprofile logon drive = L: domain logons = No domain master = No prefered master = No wins server = 192.168.10.13 wins support = No allow insecure wide links = yes follow symlinks = yes wide links = yes allow trusted domains = No template homedir = /home/%U template shell = /bin/bash oplocks = No level2 oplocks = No client min protocol = NT1 nt acl support = no inherit acls = no kerberos method = secrets and keytab winbind use default domain = yes winbind enum users = yes winbind enum groups = yes winbind nested groups = No winbind refresh tickets = yes winbind offline logon = yes idmap config HOME : backend = rid idmap config HOME : range = 1000 - 20000 idmap cache time = 20000 unix charset = utf8 dos charset = cp1252 [homes] comment = home valid users = %S, %D%w%S read only = no create mask = 0600 directory mask = 0700 browseable = no printable = no [pdf] printing = sysv comment = PDF Generator path = /tmp read only = no printer name = ps1 guest ok = yes printable = yes browseable = yes print command = /usr/local/lufa/mkpdf %s ~%u //%L/%u %m %I

2 days, 5 hours

rbind mount problem

by Marc Chamberlin

Hello - I am running OpenSuSE Leap 15.2 and am encountering a problem with doing an rbind mount on the root / directory that I cannot find a solution to. I run a SOHO network and only my wife and I are users. (She is NOT Linux savoy so not a threat! LOL) In my /etc/fstab file I mount the root / directory at /slash using the following configuration - > /slash none rbind,x-systemd.automount,x-systemd.idle-timeout=300 0 0 The trouble I am having occurs when I try to set up a relative link in a sub-directory that uses slash. So for example I have a directory at /srv/samba/etc as accessed and shown here - > marcslaptop:~ # cd /srv/samba/etc/ > marcslaptop:/srv/samba/etc # ll > total 20 > lrwxrwxrwx 1 root root 20 Jun 11 09:17 dhcp.conf -> /etc/samba/dhcp.conf > lrwxrwxrwx 1 root root 32 Jun 13 14:52 lmhosts -> > ../../../slash/etc/samba/lmhosts > lrwxrwxrwx 1 root root 33 Jun 12 22:21 smb.conf -> > ../../../slash/etc/samba/smb.conf > lrwxrwxrwx 1 root root 27 Jun 13 15:34 smbusers -> > ../../../etc/samba/smbusers and all is fine and works as expected. However if I cd to this same directory via the /slash mount things go to pot! - > marcslaptop:/srv/samba/etc # cd /slash/srv/samba/etc/ > marcslaptop:/slash/srv/samba/etc # ll > total 20 > lrwxrwxrwx 1 root root 20 Jun 11 09:17 dhcp.conf -> /etc/samba/dhcp.conf > lrwxrwxrwx 1 root root 32 Jun 13 14:52 lmhosts -> > ../../../slash/etc/samba/lmhosts <-- Highlighted in red > lrwxrwxrwx 1 root root 33 Jun 12 22:21 smb.conf -> > ../../../slash/etc/samba/smb.conf <-- Highlighted in red > lrwxrwxrwx 1 root root 27 Jun 13 15:34 smbusers -> > ../../../etc/samba/smbusers > The color coding is missing but it shows that the links for lmhosts and smb.conf are broken. I can demonstrate this - > marcslaptop:/slash/srv/samba/etc # more smb.conf > more: stat of smb.conf failed: Too many levels of symbolic links > marcslaptop:/slash/srv/samba/etc # more lmhosts > more: stat of lmhosts failed: Too many levels of symbolic links I don't know if the relative links for lmhosts and smb.conf are broken because I cd via the /slash mount point or something else is haywired, but the error message telling me that there are "Too many levels of symbolic links" makes me think that an indefinite recursion loop is occurring somewhere. I can't grok why that would be the case, and after 5 days of Googling and reading man pages, I give up and hopefully a guru here has solved this or something similar and will be able to point me in the right direction and tell me how to get these links to work. I can't find any options for autofs, automount, cifs file systems etc that would solve this either. (Yes I am using cifs because there are Windoz systems on my SOHO network also and I want to be able to access the /slash share from them as well.) While this is NOT a complete or precise explanation for why I need these relative links to work via the /slash mount point, I want the /srv directory to contain all the links to various configuration files, for each service I run on each of my systems. This way I will be able to export a samba share for both /slash and /srv and use a tool like Beyond Compare to manage and maintain these files and keep them in sync when I update or make changes to a configuration file that should be propagated to each system on my network. Using relative links will allow me to access these configuration via the remote host's /slash mount and not via the local host's /slash mount. Thanks as always in advance for your time and efforts! Marc...

2 days, 14 hours

please consider fixing update system thank you

by paolo brusasco

Thank you for opensuse 15.3. Updating a brand new x64 opensuse install kde and gnome, as for now, fails and it's well known all over the internet. Zyppering and rezyppering updates something but doesn't fix. I'm sorry for the annoyance but I think this item should be on the top of the forum till the fix, and users should be openly informed of the fixing process on top of every official page of the project. Great, long lasting distribution, we wish and hope well. Thank you, best regards, Paolo Brusasco

3 days, 5 hours

Every time I try to install the proprietry Nvidia drivers X11 KDE Plasma completely fails to start

by Simon Connah

Hi, As the title really. I have no idea what is going on. It happened after the UsrMerge update and now I can't install the propriety drivers at all without completely killing my GUI. Is this a known issue at all? I don't want to try again because I haven't been able to fix it. Simon.

6 days, 12 hours

Handbrake is broken for what is sound - how to report a bug to packman?

by Stakanov

Handbrake is a coversion program for movies. The current version is broken apparently for sound. It creates conversions without. Now, I tried to understand, but found not bugzilla for them, so I wondered where to report a bug with them?

6 days, 23 hours

Update error - Leap 15.3 KDE

by James Knott

I'm getting update errors "patch:SUSE-2021-1526-1.noarch conflicts with readline-doc". When I try using online update it shows it wants to uninstall LibreOffice. If I allow it to do that, it leaves me without LibreOffice. The error still occurs after reinstalling it. Anyone else see this? tnx jk

1 week

Jump to page:

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

1996

1995

1994

1993

1992

openSUSE Users