openSUSE Users January 2019

users@lists.opensuse.org

57 participants
79 discussions

[opensuse] libc segfaults attaching an iPad

by Dave Howorth

I just tried to attach an iPad to my openSUSE 15.0 system, via USB. I think I've done it before, but this time it fails. Dmesg has: [9787970.148053] usb 3-9: new high-speed USB device number 96 using xhci_hcd [9787970.302089] usb 3-9: New USB device found, idVendor=05ac, idProduct=12a2 [9787970.302091] usb 3-9: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [9787970.302092] usb 3-9: Product: iPad [9787970.302093] usb 3-9: Manufacturer: Apple Inc. [9787970.302094] usb 3-9: SerialNumber: c4088xxxxxserialxredacted [9787971.044264] ipheth 3-9:4.2: Apple iPhone USB Ethernet device attached [9787991.101146] pool[16789]: segfault at 0 ip 00007f6ada593ef1 sp 00007f6ad6203bd8 error 4 in libc-2.26.so[7f6ada43a000+1b1000] Anybody have any idea what the problem is? Thanks, Dave -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 months, 3 weeks

[opensuse] Raid, Raid6, what file system for good fault tolerance?

by cagsm

Hi list, speaking about software raid, not hardware controller based. I am trying to go for some local OpenSuse machine and adding some storage to it. Was considering Raid6, and now reading about a bit and people left and right scaremongering about the larger the disks these days in the double digit terabyte capacities even, the more likely it is that during a reconstruction of a raid subsequent errors would occur. I would absolutely like to keep my data consistent, and I am not thinking about double digit terabytes either, would stick to 2TB or 4TB disks, with Raid6 thats at least 4 physical drives. Now I am wondering if it possible to use a good robust file system that can add some more parity or check blocks or redundancy on top of the hardware disks, to absolutely be able to always read my data. I can't add multiple machines or like those high availability stuff like clusters and what not I read about DRBD (Distributed Replicated Block Device), or maybe I am just too scared by those technical terms or consider myself to be just a simpleton and wanting to keep it rather simple. My use case here is also not constant availablity, when a disk needs to be replaced, so be it, but I don't want to lose my data that I can not ever read certain parts of it again or such stuff. The thing that came to my mind was, if there is some file systems that would add redundancy and robustness onto the mdraid system of the linux kernel? Anyone with some useful insights? Roughly speaking, I was considering some simple pcie esata interfaced controller card and an external case enclosure with esata port and portmulitplier stuff inside, that can present at least 4 physical disks as JBOD, just a bunch of disks, so that the Linux can seem them all separately. Speed and rebuild times are not my concern, but data persistence and data integrity. Not even number of physical disks, I could live with even one of those 8 bay device enclosures and cases that are out there on the market. Thanks for any help and hints. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

9 months

[opensuse] Issue with smartd

by Carlos E. R.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I have one disk that is giving me problems with the smartd daemon. I get this in the log: <3.6> 2018-10-21T13:45:23.829155+02:00 Isengard smartd 1173 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], state written to /var/lib/smartmontools/smartd.WDC_WD80EZAZ_11TDBA0-2TKST2SD.ata.state <3.6> 2018-10-21T13:45:24.483719+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], opened <3.6> 2018-10-21T13:45:24.484570+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], WDC WD80EZAZ-11TDBA0, S/N:2TKST2SD, WWN:5-000cca-26af51579, FW:83.H0A83, 8.00 TB <3.6> 2018-10-21T13:45:24.503334+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], not found in smartd database. <3.6> 2018-10-21T13:45:24.525071+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], enabled SMART Attribute Autosave. <3.6> 2018-10-21T13:45:24.530486+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], enabled SMART Automatic Offline Testing. <3.6> 2018-10-21T13:45:24.535003+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], is SMART capable. Adding to "monitor" list. <3.6> 2018-10-21T13:45:24.535627+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], state read from /var/lib/smartmontools/smartd.WDC_WD80EZAZ_11TDBA0-2TKST2SD.ata.state <3.6> 2018-10-21T13:45:24.880219+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], state written to /var/lib/smartmontools/smartd.WDC_WD80EZAZ_11TDBA0-2TKST2SD.ata.state <3.6> 2018-10-21T14:15:25.233525+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 147 to 144 <3.6> 2018-10-21T15:45:31.681938+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], not capable of SMART self-check <3.2> 2018-10-21T15:45:33.632399+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], failed to read SMART Attribute Data <3.6> 2018-10-21T16:15:24.678100+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], read SMART Attribute Data worked again, warning condition reset after 1 email <3.6> 2018-10-21T18:15:31.767150+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], not capable of SMART self-check <3.2> 2018-10-21T18:15:33.717688+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], failed to read SMART Attribute Data <3.6> 2018-10-21T18:45:24.587304+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], read SMART Attribute Data worked again, warning condition reset after 1 email It intermitently but periodically fail to read atributes, triggering hundreds of emails sent to me to warn of the problem: +++------------ Subject: SMART error (FailedReadSmartData) detected on host: Isengard This message was generated by the smartd daemon running on: host name: Isengard DNS domain: valinor The following warning/error was logged by the smartd daemon: Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], failed to read SMART Attribute Data Device info: WDC WD80EZAZ-11TDBA0, S/N:2TKST2SD, WWN:5-000cca-26af51579, FW:83.H0A83, 8.00 TB For details see host's SYSLOG. You can also use the smartctl utility for further investigation. Another message will be sent in 24 hours if the problem persists. - ------------++- The disk is indeed smart capable and it works fine, as long as I call smartctl with "-d sat,16", which I do: Isengard:~ # smartctl --test=short -d sat,16 /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0\:0 smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.4.155-68-default] (SUSE RPM) Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org === START OF OFFLINE IMMEDIATE AND SELF-TEST SECTION === Sending command: "Execute SMART Short self-test routine immediately in off-line mode". Drive command "Execute SMART Short self-test routine immediately in off-line mode" successful. Testing has begun. Please wait 2 minutes for test to complete. Test will complete after Sun Oct 21 13:50:18 2018 Use smartctl -X to abort test. Isengard:~ # Isengard:~ # smartctl --health -d sat,16 /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0\:0 smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.4.155-68-default] (SUSE RPM) Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED Isengard:~ # It is crucial to use "-d sat,16" or it fails: Isengard:~ # smartctl --health /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0\:0 smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.4.155-68-default] (SUSE RPM) Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0: Unknown USB bridge [0x1058:0x25ee (0x4004)] Please specify device type with the -d option. Use smartctl -h to get a usage summary Isengard:~ # Of course I use that option on the config: Isengard:~ # cat /etc/smartd.conf | egrep -v "^[[:space:]]*$|^#" /dev/sda -a -o on -S on -s (S/../.././02|L/../../6/03) -m root(a)telcontar.valinor /dev/disk/by-id/wwn-0x5000000000000001 -a -o on -S on -s (S/../.././02|L/../../6/03) -m root(a)telcontar.valinor /dev/disk/by-id/wwn-0x5000c5009399305f -a -o on -S on -s (S/../.././02|L/../../6/03) -m root(a)telcontar.valinor /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 -d sat,16 -a -o on -S on -s (S/../.././02|L/../../6/03) -m root(a)telcontar.valinor Isengard:~ # What else am I missing? Is smartd not using "-d sat,16" somewhere else? Is it some other problem? Isengard:~ # rpm -q smartmontools smartmontools-6.6-135.1.x86_64 Isengard:~ # - -- Cheers Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlvM5UMACgkQtTMYHG2NR9WCwQCePjOt8PSMKsx6DwSe9bZJRhHf 2lQAn02eBTrtfAqmEg5ydZVagvMfW2r6 =eIzR -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

11 months

[opensuse] oS 13.1 : "gnome keyring socket is not owned with the same credentials as the user"

by ellanios82

Hello List am using Xfce : - in /var/log/warn : i see warning " The gnome keyring socket is not owned with the same credentials as the user login: /run/user/1000/keyring-4i77r7/control 2013-11-27T13:27:17.434100+02:00 su: gkr-pam: couldn't unlock the login keyring " ............... - any ideas how to fix ? thanks -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 years, 1 month

Re: [opensuse] Mapping and re-mapping Keyboard Keys

by Paul Groves

On 27/06/17 12:22, Paul Groves wrote: > > On 27/06/17 08:34, Aaron Digulla wrote: >> xmodmap -pke | less > > These keycodes do not seem to match the system. For example in the > output of this command it says: > > keycode 158 = XF86WWW NoSymbol XF86WWW > > I ran setkeycodes e020 158 > > When I press the e020 (Internet) button xev says I have pressed code > 166 (Back button). > > How on earth has this happened? I specified 158 not 166. What have I > done wrong? > > Just been emailed this link: https://unix.stackexchange.com/questions/49650/how-to-get-keycodes-for-xmod… To quote this article: Here you can see keycode 97 is unused on my system: |keycode 94 = less greater less greater bar brokenbar keycode 95 = F11 XF86Switch_VT_11 F11 XF86Switch_VT_11 keycode 96 = F12 XF86Switch_VT_12 F12 XF86Switch_VT_12 keycode 97 = keycode 98 = Katakana NoSymbol Katakana keycode 99 = Hiragana NoSymbol Hiragana | The keycode X uses and the keycode the kernel uses are OFF BY 8 for "historical reasons". So take 97 - 8 = 89 and use 89 with the setkeycodes command (again as root): So to make my vol - button work (xmodmap keycode 122 -8 = 114) setkeycodes e01e 114 This has worked! I have re-mapped apl the buttons apart from my hotkeys. >> No but there are lots of uncommon keycodes which you can use. For >> example, F13-F35 or KP_F1...KP_F4. > > In the output of the command xmodmap -pke | less there are no codes > for F13-F35 or KP_F1 etc > > I would like to set HK1 - HK4 to F13 - F16 How do I find the keycodes > for these buttons Still looking for the keycodes for F13-16 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 years, 6 months

[opensuse] Spec'ing a 50 TB dedicated storage subsystem and room to grow?

by Greg Freemyer

All, I bought a used iSCSI based Drobo in 2016 with 50TB in it. It works great, but it isn't fast by today's standards. (100 MB/sec absolute max). And I never got it to work from openSUSE (Windows and Mac did work). I now need to buy something similar, but with fast I/O and Linux support: 10 Gbit Ethernet and fibre-channel may be my only options? Or are there point-to-point SAS external racks I should consider? Also, I will likely want to put a SSD based cache in the mix at some point. It could be integrated into the storage subsystem, or I could use something like bcache and have the SSD be in the server,. It just needs to be reliable and fast. Recommendations? (I'm thinking used and $10K at the high-end for the subsystem including PCIx cards and switches, if needed.) == details I need to buy a server with 50TB usable disk for a production environment. A high speed disk subsystem is critical. And the project may scale up over time. It doesn't need to be a fail-over cluster, just a single server. I'm looking at used equipment most likely. I was thinking one with 4 CPU sockets would let me start with 2 CPUs and then expand to 4 later on. Lots of RAM capacity would also be great. My first thought was to get a Dell R920 and throw a bunch of disks in it. https://goo.gl/images/x3Rfj2 24 disk slots! But then I looked at what size drives are available for those slots: 2.5 inch. I only see 2TB drives max. I'm hoping to use a Dell server because it's the preferred brand at my (new) job. Unless I'm missing something a standalone rack mount Dell won't work. So, now I'm looking at a used R820 most likely and some sort of disk subsystem to support it. I picked it because it is only a 5-year old design and it has 4 CPU sockets I can expand into as the server demand increases over time. Also 3TB max ram is way above what this will require, even long term. https://media.adn.de/media/DE/DocLib/Poweredge_Easy_Matrix.pdf A used, barebones R820 can be had for under $2K. Just add CPUs and ram. Greg -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 years, 6 months

[opensuse] I have lost sound after upgrading to 15.0

by Carlos E. R.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 That's it, no sound at all. Hardware is the same. On 42.3 it worked perfectly; nothing now. YaST produces no sound after going through the configuration. The mixer says there is no card to configure. Log: <10.3> 2019-01-10 19:43:12 Telcontar gnomesu-pam-backend - - - The gnome keyring socket is not owned with the same credentials as the user login: /run/user/1000/keyring/control <10.3> 2019-01-10 19:43:12 Telcontar gnomesu-pam-backend - - - gkr-pam: couldn't unlock the login keyring. <10.7> 2019-01-10 19:43:12 Telcontar gnomesu-pam-backend - - - pam_systemd(gnomesu-pam:session): Cannot create session: Already running in a session or user slice <10.6> 2019-01-10 19:43:12 Telcontar gnomesu-pam-backend - - - pam_unix(gnomesu-pam:session): session opened for user root by (uid=1000) <1.4> 2019-01-10 19:43:12 Telcontar y2controlcenter 24515 - - QStandardPaths: XDG_RUNTIME_DIR points to non-existing path '/run/user/0', please create it with 0700 permissions. <1.4> 2019-01-10 19:43:12 Telcontar y2controlcenter 24515 - - QStandardPaths: XDG_RUNTIME_DIR points to non-existing path '/run/user/0', please create it with 0700 permissions. <1.4> 2019-01-10 19:43:12 Telcontar y2controlcenter 24515 - - Qt: Session management error: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed <3.6> 2019-01-10 19:43:17 Telcontar dbus-daemon 1455 - - [system] Activating service name='org.opensuse.Snapper' requested by ':1.1597' (uid=0 pid=24553 comm="/usr/bin/snapper create --type=pre --cleanup-algor") (using servicehelper) <3.6> 2019-01-10 19:43:17 Telcontar dbus-daemon 1455 - - [system] Successfully activated service 'org.opensuse.Snapper' <1.4> 2019-01-10 19:44:40 Telcontar baloo_file 5397 - - QObject::connect: invalid null parameter <0.3> 2019-01-10 19:44:40 Telcontar kernel - - - [115233.342868] snd_hda_intel 0000:03:00.0: CORB reset timeout#1, CORBRP = 0 <0.6> 2019-01-10 19:44:40 Telcontar kernel - - - [115233.486423] snd_hda_codec_ca0110 hdaudioC0D1: autoconfig for CA0110-IBG: line_outs=4 (0xb/0xd/0xc/0xe/0x0) type:line <0.6> 2019-01-10 19:44:40 Telcontar kernel - - - [115233.486427] snd_hda_codec_ca0110 hdaudioC0D1: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) <0.6> 2019-01-10 19:44:40 Telcontar kernel - - - [115233.486429] snd_hda_codec_ca0110 hdaudioC0D1: hp_outs=1 (0xf/0x0/0x0/0x0/0x0) <0.6> 2019-01-10 19:44:40 Telcontar kernel - - - [115233.486431] snd_hda_codec_ca0110 hdaudioC0D1: mono: mono_out=0x0 <0.6> 2019-01-10 19:44:40 Telcontar kernel - - - [115233.486433] snd_hda_codec_ca0110 hdaudioC0D1: dig-out=0x12/0x0 <0.6> 2019-01-10 19:44:40 Telcontar kernel - - - [115233.486435] snd_hda_codec_ca0110 hdaudioC0D1: inputs: <0.6> 2019-01-10 19:44:40 Telcontar kernel - - - [115233.486438] snd_hda_codec_ca0110 hdaudioC0D1: Front Mic=0x11 <0.6> 2019-01-10 19:44:40 Telcontar kernel - - - [115233.486440] snd_hda_codec_ca0110 hdaudioC0D1: Rear Mic=0x10 <0.6> 2019-01-10 19:44:40 Telcontar kernel - - - [115233.486442] snd_hda_codec_ca0110 hdaudioC0D1: dig-in=0x13 <0.6> 2019-01-10 19:44:41 Telcontar kernel - - - [115234.667476] input: HDA Creative Front Mic as /devices/pci0000:00/0000:00:1c.0/0000:02:00.0/0000:03:00.0/sound/card0/input17 <0.6> 2019-01-10 19:44:41 Telcontar kernel - - - [115234.667568] input: HDA Creative Rear Mic as /devices/pci0000:00/0000:00:1c.0/0000:02:00.0/0000:03:00.0/sound/card0/input18 <0.6> 2019-01-10 19:44:41 Telcontar kernel - - - [115234.667663] input: HDA Creative Line Out Front as /devices/pci0000:00/0000:00:1c.0/0000:02:00.0/0000:03:00.0/sound/card0/input19 <0.6> 2019-01-10 19:44:41 Telcontar kernel - - - [115234.667754] input: HDA Creative Line Out Surround as /devices/pci0000:00/0000:00:1c.0/0000:02:00.0/0000:03:00.0/sound/card0/input20 <0.6> 2019-01-10 19:44:41 Telcontar kernel - - - [115234.667845] input: HDA Creative Line Out CLFE as /devices/pci0000:00/0000:00:1c.0/0000:02:00.0/0000:03:00.0/sound/card0/input21 <0.6> 2019-01-10 19:44:41 Telcontar kernel - - - [115234.667935] input: HDA Creative Line Out Side as /devices/pci0000:00/0000:00:1c.0/0000:02:00.0/0000:03:00.0/sound/card0/input22 <0.6> 2019-01-10 19:44:41 Telcontar kernel - - - [115234.668034] input: HDA Creative Front Headphone as /devices/pci0000:00/0000:00:1c.0/0000:02:00.0/0000:03:00.0/sound/card0/input23 <1.4> 2019-01-10 19:44:41 Telcontar baloo_file 5397 - - message repeated 8 times: [ QObject::connect: invalid null parameter] <3.6> 2019-01-10 19:44:41 Telcontar systemd 1 - - Starting Save/Restore Sound Card State... <1.4> 2019-01-10 19:44:41 Telcontar baloo_file 5397 - - QObject::connect: invalid null parameter <3.6> 2019-01-10 19:44:41 Telcontar systemd 1 - - Started Save/Restore Sound Card State. <3.6> 2019-01-10 19:44:41 Telcontar systemd 1 - - Reached target Sound Card. <1.3> 2019-01-10 19:44:42 Telcontar pulseaudio 5099 - - [pulseaudio] module-alsa-card.c: Failed to find a working profile. <1.3> 2019-01-10 19:44:42 Telcontar pulseaudio 5099 - - [pulseaudio] module.c: Failed to load module "module-alsa-card" (argument: "device_id="0" name="pci-0000_03_00.0" card_name="alsa_card.pci-0000_03_00.0" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes card_properties="module-udev-detect.discovered=1""): initialization failed. <3.6> 2019-01-10 19:45:04 Telcontar systemd-udevd 661 - - Network interface NamePolicy= disabled by default. <3.6> 2019-01-10 19:45:04 Telcontar systemd 1 - - sound.target: Unit not needed anymore. Stopping. <3.6> 2019-01-10 19:45:04 Telcontar systemd 1 - - Stopped target Sound Card. <1.4> 2019-01-10 19:45:05 Telcontar baloo_file 5397 - - QObject::connect: invalid null parameter <0.3> 2019-01-10 19:45:05 Telcontar kernel - - - [115258.230993] snd_hda_intel 0000:03:00.0: CORB reset timeout#1, CORBRP = 0 <0.6> 2019-01-10 19:45:05 Telcontar kernel - - - [115258.371950] snd_hda_codec_ca0110 hdaudioC0D1: autoconfig for CA0110-IBG: line_outs=4 (0xb/0xd/0xc/0xe/0x0) type:line <0.6> 2019-01-10 19:45:05 Telcontar kernel - - - [115258.371953] snd_hda_codec_ca0110 hdaudioC0D1: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) <0.6> 2019-01-10 19:45:05 Telcontar kernel - - - [115258.371955] snd_hda_codec_ca0110 hdaudioC0D1: hp_outs=1 (0xf/0x0/0x0/0x0/0x0) <0.6> 2019-01-10 19:45:05 Telcontar kernel - - - [115258.371957] snd_hda_codec_ca0110 hdaudioC0D1: mono: mono_out=0x0 <0.6> 2019-01-10 19:45:05 Telcontar kernel - - - [115258.371958] snd_hda_codec_ca0110 hdaudioC0D1: dig-out=0x12/0x0 <0.6> 2019-01-10 19:45:05 Telcontar kernel - - - [115258.371959] snd_hda_codec_ca0110 hdaudioC0D1: inputs: <0.6> 2019-01-10 19:45:05 Telcontar kernel - - - [115258.371962] snd_hda_codec_ca0110 hdaudioC0D1: Front Mic=0x11 <0.6> 2019-01-10 19:45:05 Telcontar kernel - - - [115258.371964] snd_hda_codec_ca0110 hdaudioC0D1: Rear Mic=0x10 <0.6> 2019-01-10 19:45:05 Telcontar kernel - - - [115258.371965] snd_hda_codec_ca0110 hdaudioC0D1: dig-in=0x13 <1.4> 2019-01-10 19:45:05 Telcontar baloo_file 5397 - - QObject::connect: invalid null parameter <3.6> 2019-01-10 19:45:05 Telcontar systemd 1 - - Reloading. <3.4> 2019-01-10 19:45:05 Telcontar systemd 1 - - nss-lookup.target: Dependency Before=nss-lookup.target dropped <0.6> 2019-01-10 19:45:06 Telcontar kernel - - - [115259.606863] input: HDA Creative Front Mic as /devices/pci0000:00/0000:00:1c.0/0000:02:00.0/0000:03:00.0/sound/card0/input24 <1.4> 2019-01-10 19:45:06 Telcontar baloo_file 5397 - - QObject::connect: invalid null parameter <3.6> 2019-01-10 19:45:06 Telcontar systemd 1 - - Reached target Sound Card. <0.6> 2019-01-10 19:45:06 Telcontar kernel - - - [115259.608040] input: HDA Creative Rear Mic as /devices/pci0000:00/0000:00:1c.0/0000:02:00.0/0000:03:00.0/sound/card0/input25 <0.6> 2019-01-10 19:45:06 Telcontar kernel - - - [115259.609035] input: HDA Creative Line Out Front as /devices/pci0000:00/0000:00:1c.0/0000:02:00.0/0000:03:00.0/sound/card0/input26 <0.6> 2019-01-10 19:45:06 Telcontar kernel - - - [115259.609530] input: HDA Creative Line Out Surround as /devices/pci0000:00/0000:00:1c.0/0000:02:00.0/0000:03:00.0/sound/card0/input27 <0.6> 2019-01-10 19:45:06 Telcontar kernel - - - [115259.611352] input: HDA Creative Line Out CLFE as /devices/pci0000:00/0000:00:1c.0/0000:02:00.0/0000:03:00.0/sound/card0/input28 <0.6> 2019-01-10 19:45:06 Telcontar kernel - - - [115259.613443] input: HDA Creative Line Out Side as /devices/pci0000:00/0000:00:1c.0/0000:02:00.0/0000:03:00.0/sound/card0/input29 <0.6> 2019-01-10 19:45:06 Telcontar kernel - - - [115259.614868] input: HDA Creative Front Headphone as /devices/pci0000:00/0000:00:1c.0/0000:02:00.0/0000:03:00.0/sound/card0/input30 <1.4> 2019-01-10 19:45:06 Telcontar baloo_file 5397 - - QObject::connect: invalid null parameter <1.4> 2019-01-10 19:45:06 Telcontar baloo_file 5397 - - message repeated 9 times: [ QObject::connect: invalid null parameter] <1.3> 2019-01-10 19:45:06 Telcontar pulseaudio 5099 - - [pulseaudio] module-alsa-card.c: Failed to find a working profile. <1.3> 2019-01-10 19:45:06 Telcontar pulseaudio 5099 - - [pulseaudio] module.c: Failed to load module "module-alsa-card" (argument: "device_id="0" name="pci-0000_03_00.0" card_name="alsa_card.pci-0000_03_00.0" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes card_properties="module-udev-detect.discovered=1""): initialization failed. <10.6> 2019-01-10 19:45:10 Telcontar gnomesu-pam-backend - - - pam_unix(gnomesu-pam:session): session closed for user root <10.3> 2019-01-10 19:46:33 Telcontar gnomesu-pam-backend - - - The gnome keyring socket is not owned with the same credentials as the user login: /run/user/1000/keyring/control <10.3> 2019-01-10 19:46:33 Telcontar gnomesu-pam-backend - - - gkr-pam: couldn't unlock the login keyring. <10.7> 2019-01-10 19:46:33 Telcontar gnomesu-pam-backend - - - pam_systemd(gnomesu-pam:session): Cannot create session: Already running in a session or user slice <10.6> 2019-01-10 19:46:33 Telcontar gnomesu-pam-backend - - - pam_unix(gnomesu-pam:session): session opened for user root by (uid=1000) <1.4> 2019-01-10 19:46:33 Telcontar y2controlcenter 25189 - - QStandardPaths: XDG_RUNTIME_DIR points to non-existing path '/run/user/0', please create it with 0700 permissions. <1.4> 2019-01-10 19:46:34 Telcontar y2controlcenter 25189 - - QStandardPaths: XDG_RUNTIME_DIR points to non-existing path '/run/user/0', please create it with 0700 permissions. <1.4> 2019-01-10 19:46:34 Telcontar y2controlcenter 25189 - - Qt: Session management error: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed <3.6> 2019-01-10 19:46:37 Telcontar dbus-daemon 1455 - - [system] Activating service name='org.opensuse.Snapper' requested by ':1.1603' (uid=0 pid=25227 comm="/usr/bin/snapper create --type=pre --cleanup-algor") (using servicehelper) <3.6> 2019-01-10 19:46:37 Telcontar dbus-daemon 1455 - - [system] Successfully activated service 'org.opensuse.Snapper' <3.6> 2019-01-10 19:46:49 Telcontar systemd 1 - - sound.target: Unit not needed anymore. Stopping. <3.6> 2019-01-10 19:46:49 Telcontar systemd 1 - - Stopped target Sound Card. <1.4> 2019-01-10 19:46:50 Telcontar baloo_file 5397 - - QObject::connect: invalid null parameter <0.3> 2019-01-10 19:47:07 Telcontar kernel - - - [115379.811402] snd_hda_intel 0000:03:00.0: CORB reset timeout#1, CORBRP = 0 <0.6> 2019-01-10 19:47:07 Telcontar kernel - - - [115379.960117] snd_hda_codec_ca0110 hdaudioC0D1: autoconfig for CA0110-IBG: line_outs=4 (0xb/0xd/0xc/0xe/0x0) type:line <0.6> 2019-01-10 19:47:07 Telcontar kernel - - - [115379.960120] snd_hda_codec_ca0110 hdaudioC0D1: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) <0.6> 2019-01-10 19:47:07 Telcontar kernel - - - [115379.960123] snd_hda_codec_ca0110 hdaudioC0D1: hp_outs=1 (0xf/0x0/0x0/0x0/0x0) <0.6> 2019-01-10 19:47:07 Telcontar kernel - - - [115379.960125] snd_hda_codec_ca0110 hdaudioC0D1: mono: mono_out=0x0 <0.6> 2019-01-10 19:47:07 Telcontar kernel - - - [115379.960127] snd_hda_codec_ca0110 hdaudioC0D1: dig-out=0x12/0x0 <0.6> 2019-01-10 19:47:07 Telcontar kernel - - - [115379.960129] snd_hda_codec_ca0110 hdaudioC0D1: inputs: <0.6> 2019-01-10 19:47:07 Telcontar kernel - - - [115379.960132] snd_hda_codec_ca0110 hdaudioC0D1: Front Mic=0x11 <0.6> 2019-01-10 19:47:07 Telcontar kernel - - - [115379.960134] snd_hda_codec_ca0110 hdaudioC0D1: Rear Mic=0x10 <0.6> 2019-01-10 19:47:07 Telcontar kernel - - - [115379.960136] snd_hda_codec_ca0110 hdaudioC0D1: dig-in=0x13 <0.6> 2019-01-10 19:47:08 Telcontar kernel - - - [115381.149513] input: HDA Creative Front Mic as /devices/pci0000:00/0000:00:1c.0/0000:02:00.0/0000:03:00.0/sound/card0/input31 <0.6> 2019-01-10 19:47:08 Telcontar kernel - - - [115381.149602] input: HDA Creative Rear Mic as /devices/pci0000:00/0000:00:1c.0/0000:02:00.0/0000:03:00.0/sound/card0/input32 <0.6> 2019-01-10 19:47:08 Telcontar kernel - - - [115381.149686] input: HDA Creative Line Out Front as /devices/pci0000:00/0000:00:1c.0/0000:02:00.0/0000:03:00.0/sound/card0/input33 <0.6> 2019-01-10 19:47:08 Telcontar kernel - - - [115381.149768] input: HDA Creative Line Out Surround as /devices/pci0000:00/0000:00:1c.0/0000:02:00.0/0000:03:00.0/sound/card0/input34 <0.6> 2019-01-10 19:47:08 Telcontar kernel - - - [115381.149850] input: HDA Creative Line Out CLFE as /devices/pci0000:00/0000:00:1c.0/0000:02:00.0/0000:03:00.0/sound/card0/input35 <0.6> 2019-01-10 19:47:08 Telcontar kernel - - - [115381.153903] input: HDA Creative Line Out Side as /devices/pci0000:00/0000:00:1c.0/0000:02:00.0/0000:03:00.0/sound/card0/input36 <0.6> 2019-01-10 19:47:08 Telcontar kernel - - - [115381.154014] input: HDA Creative Front Headphone as /devices/pci0000:00/0000:00:1c.0/0000:02:00.0/0000:03:00.0/sound/card0/input37 <1.4> 2019-01-10 19:47:08 Telcontar baloo_file 5397 - - message repeated 4 times: [ QObject::connect: invalid null parameter] <3.6> 2019-01-10 19:47:08 Telcontar systemd 1 - - Reached target Sound Card. <1.4> 2019-01-10 19:47:08 Telcontar baloo_file 5397 - - QObject::connect: invalid null parameter <1.4> 2019-01-10 19:47:08 Telcontar baloo_file 5397 - - message repeated 6 times: [ QObject::connect: invalid null parameter] <1.3> 2019-01-10 19:47:08 Telcontar pulseaudio 5099 - - [pulseaudio] module-alsa-card.c: Failed to find a working profile. <1.3> 2019-01-10 19:47:08 Telcontar pulseaudio 5099 - - [pulseaudio] module.c: Failed to load module "module-alsa-card" (argument: "device_id="0" name="pci-0000_03_00.0" card_name="alsa_card.pci-0000_03_00.0" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes card_properties="module-udev-detect.discovered=1""): initialization failed. <3.6> 2019-01-10 19:47:41 Telcontar systemd-udevd 661 - - Network interface NamePolicy= disabled by default. <3.6> 2019-01-10 19:47:41 Telcontar systemd 1 - - sound.target: Unit not needed anymore. Stopping. <3.6> 2019-01-10 19:47:41 Telcontar systemd 1 - - Stopped target Sound Card. <1.4> 2019-01-10 19:47:42 Telcontar baloo_file 5397 - - QObject::connect: invalid null parameter <0.3> 2019-01-10 19:47:42 Telcontar kernel - - - [115414.829952] snd_hda_intel 0000:03:00.0: CORB reset timeout#1, CORBRP = 0 <0.6> 2019-01-10 19:47:42 Telcontar kernel - - - [115414.977490] snd_hda_codec_ca0110 hdaudioC0D1: autoconfig for CA0110-IBG: line_outs=4 (0xb/0xd/0xc/0xe/0x0) type:line <0.6> 2019-01-10 19:47:42 Telcontar kernel - - - [115414.977493] snd_hda_codec_ca0110 hdaudioC0D1: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) <0.6> 2019-01-10 19:47:42 Telcontar kernel - - - [115414.977495] snd_hda_codec_ca0110 hdaudioC0D1: hp_outs=1 (0xf/0x0/0x0/0x0/0x0) <0.6> 2019-01-10 19:47:42 Telcontar kernel - - - [115414.977496] snd_hda_codec_ca0110 hdaudioC0D1: mono: mono_out=0x0 <0.6> 2019-01-10 19:47:42 Telcontar kernel - - - [115414.977498] snd_hda_codec_ca0110 hdaudioC0D1: dig-out=0x12/0x0 <0.6> 2019-01-10 19:47:42 Telcontar kernel - - - [115414.977499] snd_hda_codec_ca0110 hdaudioC0D1: inputs: <0.6> 2019-01-10 19:47:42 Telcontar kernel - - - [115414.977501] snd_hda_codec_ca0110 hdaudioC0D1: Front Mic=0x11 <0.6> 2019-01-10 19:47:42 Telcontar kernel - - - [115414.977503] snd_hda_codec_ca0110 hdaudioC0D1: Rear Mic=0x10 <0.6> 2019-01-10 19:47:42 Telcontar kernel - - - [115414.977504] snd_hda_codec_ca0110 hdaudioC0D1: dig-in=0x13 <1.4> 2019-01-10 19:47:42 Telcontar baloo_file 5397 - - QObject::connect: invalid null parameter <3.6> 2019-01-10 19:47:42 Telcontar systemd 1 - - Reloading. <3.4> 2019-01-10 19:47:42 Telcontar systemd 1 - - nss-lookup.target: Dependency Before=nss-lookup.target dropped <1.4> 2019-01-10 19:47:43 Telcontar baloo_file 5397 - - QObject::connect: invalid null parameter <0.6> 2019-01-10 19:47:43 Telcontar kernel - - - [115416.224217] input: HDA Creative Front Mic as /devices/pci0000:00/0000:00:1c.0/0000:02:00.0/0000:03:00.0/sound/card0/input38 <0.6> 2019-01-10 19:47:43 Telcontar kernel - - - [115416.224305] input: HDA Creative Rear Mic as /devices/pci0000:00/0000:00:1c.0/0000:02:00.0/0000:03:00.0/sound/card0/input39 <0.6> 2019-01-10 19:47:43 Telcontar kernel - - - [115416.224928] input: HDA Creative Line Out Front as /devices/pci0000:00/0000:00:1c.0/0000:02:00.0/0000:03:00.0/sound/card0/input40 <0.6> 2019-01-10 19:47:43 Telcontar kernel - - - [115416.225048] input: HDA Creative Line Out Surround as /devices/pci0000:00/0000:00:1c.0/0000:02:00.0/0000:03:00.0/sound/card0/input41 <0.6> 2019-01-10 19:47:43 Telcontar kernel - - - [115416.225137] input: HDA Creative Line Out CLFE as /devices/pci0000:00/0000:00:1c.0/0000:02:00.0/0000:03:00.0/sound/card0/input42 <0.6> 2019-01-10 19:47:43 Telcontar kernel - - - [115416.225220] input: HDA Creative Line Out Side as /devices/pci0000:00/0000:00:1c.0/0000:02:00.0/0000:03:00.0/sound/card0/input43 <0.6> 2019-01-10 19:47:43 Telcontar kernel - - - [115416.225305] input: HDA Creative Front Headphone as /devices/pci0000:00/0000:00:1c.0/0000:02:00.0/0000:03:00.0/sound/card0/input44 <1.4> 2019-01-10 19:47:43 Telcontar baloo_file 5397 - - message repeated 3 times: [ QObject::connect: invalid null parameter] <3.6> 2019-01-10 19:47:43 Telcontar systemd 1 - - Reached target Sound Card. <1.4> 2019-01-10 19:47:43 Telcontar baloo_file 5397 - - QObject::connect: invalid null parameter <1.4> 2019-01-10 19:47:43 Telcontar baloo_file 5397 - - message repeated 6 times: [ QObject::connect: invalid null parameter] <1.3> 2019-01-10 19:47:43 Telcontar pulseaudio 5099 - - [pulseaudio] module-alsa-card.c: Failed to find a working profile. <1.3> 2019-01-10 19:47:43 Telcontar pulseaudio 5099 - - [pulseaudio] module.c: Failed to load module "module-alsa-card" (argument: "device_id="0" name="pci-0000_03_00.0" card_name="alsa_card.pci-0000_03_00.0" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes card_properties="module-udev-detect.discovered=1""): initialization failed. The relevant line seems to be: <1.3> 2019-01-10 19:47:43 Telcontar pulseaudio 5099 - - [pulseaudio] module.c: Failed to load module "module-alsa-card" (argument: "device_id="0" name="pci-0000_03_00.0" card_name="alsa_card.pci-0000_03_00.0" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes card_properties="module-udev-detect.discovered=1""): initialization failed. - -- Cheers Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXDeV2Rwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfV32oAnjkBdKbi6mTEkRSQ+Yan Il2jykIIAKCFh482bGobF4eLqWJ46BReQjp9vw== =8XD2 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 years, 6 months

[opensuse] Discard vs. dm-crypt

by Matthias Bach

Hi, On multiple of my machines I have the root filesystem on a dm-crypt device placed on an SSD. Now, I would like to use `fstrim /`. Now, I know about the security implications. But, as encryption for me primarily is a way to be able to throw out disks without further effort, I don't consider those a problem for me. Sadly, on any system I installed directly with Leap 15.0 I cannot get this to work. Despite having `rd.luks.options=discard` in my kernel arguments I get the following output from `lsblk`: # lsblk --discard /dev/sda NAME DISC-ALN DISC-GRAN DISC-MAX DISC-ZERO sda 0 512B 2G 0 ├─sda1 0 512B 2G 0 ├─sda2 0 512B 2G 0 └─sda3 0 512B 2G 0 └─cr_sda3 0 0B 0B 0 Curiously the same works on a different systems which has been upgraded through various versions of Leap and is now also running on 15.0. # lsblk --discard /dev/sda NAME DISC-ALN DISC-GRAN DISC-MAX DISC-ZERO sda 0 512B 2G 0 ├─sda1 0 512B 2G 0 ├─sda2 0 512B 2G 0 ├─sda3 0 512B 2G 0 ├─sda4 0 512B 2G 0 ├─sda5 0 512B 2G 0 └─sda6 0 512B 2G 0 └─luks-081…3e1 0 512B 2G 0 The only difference I can see between the systems is, that the older system uses the UUID instead of the name, and for some reason the newer system does have the device containing root in `/etc/crypttab` while the old system does not. Any hints on what might be causing the different behavior? Kind Regards, Matthias -- Dr. Matthias Bach www.marix.org „Der einzige Weg, die Grenzen des Möglichen zu finden, ist ein klein wenig über diese hinaus in das Unmögliche vorzustoßen.“ - Arthur C. Clarke

2 years, 7 months

[opensuse] gcc 4.8 needed?

by Richmond

Seamonkey does not compile properly with gcc 7. Although it works superficially, it crashes on a website. Leap 15 does not have 4.8. We need a backward compatible compiler don't we? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 years, 7 months

[opensuse] What is this problem and how to solve it?

by Basil Chupin

I am trying to update my wife's Leap 15.0 system and get this error when using either zypper or Yast2. I am using the kernel from the ../Kernel:/stable/standard/ repository on my Leap 15.0 as well as hers but I am not having this hassle. When using zypper to update I get this error msg (pls see attached zypper_error-31.png) and when using Yast I get the error msg in the attached Yast_error-31.png. Yesterday when I tried to do same, the 'zypper up' got a lot further in the installation - pls see attached zypper_error.png. I have run 'zypper clean -a' and 'zypper refresh -fdb' but this hasn't helped. Anyone please suggest what is causing this problem and how to how to get rid of the cause of this problem? BC -- 'When I use a word', Humpty Dumpty said, in a rather scornful tone, 'it means just what I choose it to mean.' Lewis Carroll, Through the Looking-Glass

2 years, 7 months

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 January 2019