October 2019 - openSUSE Users - openSUSE Mailing Lists

Sorry SuSE: 9.1 is Waste of time and money!
by Terje J. Hanssen 17 May '24

17 May '24

I am sorry to conclude that my upgrade from SuSE 9.0 Pro to 9.1 Pro has been waste of time and money for me, so far. The same I have to say about the free SuSE "Installation support". The reason is that my SuSE 9.1 installation only detects 1 of my 3 SCSCI devices (as I wrote in another subject on this forum: http://lists.suse.com/archive/suse-linux-e/2004-May/3254.html) Yamaha 4416S CDRW recorder detected HP DVD Writer 100i NOT detected Epson 1640SU scanner NOT detected It's rather stupid. I have installed 9.1 using the DVD disk just in the HP DVD drive, but after the installation of 9.1, the KDE/Konqueror /media/recorder cannot access it and YaST2 cannot install additional software from it. Only one "Cdrecorder" is found in My computer and that is the Yamaha 4416 drive, which the KDE/Konqueror file manager assign as /media/recorder11. I am sure 9.1 is the reason, as I hadn't this problems with 9.0. I have tried both an update and two several new installation of 9.1. Neither SJDS nor Windows on the same multiboot PC have problems to detect these devices. In my opinion SuSE should therefore debug 9.1 better and longer, and not leave the problems to the customers. I see SuSE notes on their web saying that they know SCSI scanners are not detected in 9.1. But regarding my HP DVD writer problem, the SuSE support (as usual) don't take the responsibility and argue that this problem (a combination of IDE disk and SCSI devices) isn't included in their free installation support! This sounds remarkable, and I have never had a modern PC of so simple model or configuration that it has fitted the limited rules for the free installation support. Terje J. Hanssen

17 29

[opensuse] Project management software question for project managers
by Ted Byers 15 Apr '24

15 Apr '24

I am looking for project management software I can install on my Suse box. Alas, there are quite a number of prducts that claim to be suitable project management products, but I am hoping to obtain a little help separating the wheat from the chaffe. Basically, when I open the project management software, I want to be able to choose from among a number of projects that are under way, and then see the relation between a client's wish list and the functional requirements specs, and then how these specs relate to the UML diagrams that have been created, and from there, what tasks have been defined for each requirement and the identity of all persons involved, the developers and their managers, and the person who designed the code that supports the requirement. And with that, I want to be able to see the project's timeline, the related bugs, &c. I would even want to be able to open the source code files and examine the code that was actually written. Here is my wish list: 1) a web application that stores data in either PostgreSQL or MySQL. 2) easy integration with UML tool (or has it's own UML tool that supports round trip engineering) 3) resource management (e.g. computers, and development tools, that can be used, personelle assigned to each task) 4) documentation of relation between functional requirements specs to specific tasks and specific unit and integration tests. 5) time/effort tracking 6) bug tracking, including data relating the existance of the bug, and effort required to fix it, to the person who wrote the original code, the person who supervised him or her, and the person who designed the 'feature' in question, the time taken to complete the original task, and the technologies used (to imprrove accountability as well as to determine retraining and continuing education needs (people aren't disposable, so instead of taking a harsh aproach to problems identified, I prefer to use education as a corrective, but I can't design corrective instruction without knowing precisely what the need is). I also need to know if a developer has a higher than normal bug rate simply because he doesn't take enough time to ensure the job is done right, or because I haven't adequately trained him, or because of a poor choice of tools, or somethng else that may be my fault. 7) use of task effort tracking history to generate provisional effort/cost estimates from new project's functional requirements 8) easy integration with open source ERP products like OFBiz (which may make trakcing resources and manpower easier, as well as connect real production data to the enterprise's accounting systems) 9) easy integration with CMS products, like Wordpress (especally for production documentation, includng degin documentation and user guides and reference manuals) 10) easy integration with verion control systems such as subversion. If there is a decent product that supports all of this, great (and language used to implement it doesn't matter), but if I have to write code to add missing requirements, then I am limited to those implemented using Perl or Java (and running on Tomcat). I don't know PHP well enough, and I don't know Ruby at all; and I really don't want to think about implementing this sort of thing in C++ (though I could if absolutely necessary). If you have project management experience, and use tools that are available for Suse Linux, what software product(s) did you use, and with what result? While I await relies, I will continue to review web documentation for those products I have found so far, to see if any of them are a) suitable for use in production and b) to see to what extent they support the features I am after. I have seen a number of products so far in my search, that deserve to be nameless, because they provide no way to relate cost estimates to one's team's track record, or to the details of the design, and seem satisfied with production of a pretty gantt chart (which is why I have formed the view that there is a whole lots of chaffe in the set of applications that call themselves project menement software - I have yet to find anything that really has the potential of being labelled wheat). Thanks Ted -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 4

[SLE] RealPlayer G2 on SuSe 6.2
by yh＠ottawa.com 03 Apr '24

03 Apr '24

Yesterday, I finally got sound going on my Linux setup. I downloaded RealPlayer G2 and it worked beautifully. Today, RealPlayer run but no sound coming out. All other sound functions still work. I can still play my CD, have system sound BUT no sound when I run RealPlayer. /var/log/message said kernel: Sound: DMA (output) timed out - IRQ/DRQ config error? but KDE sound still work. I have re-installed RealPlayer 3 times now, still no sound when I run the RealPlayer. Any help is appreciated. Ying yh(a)ottawa.com -- To unsubscribe send e-mail to suse-linux-e-unsubscribe(a)suse.com For additional commands send e-mail to suse-linux-e-help(a)suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/

3 2

Creating a new user for a deamon
by Rowan Reid 15 Jan '24

15 Jan '24

I'm setting up a cron job for a analysis tool, I'm trying to use the SuSE tools where possible but YAST doent' allow you to create new user without a home I tried /dev/null is there a proper way to do this ? Rowan Reid Job Captain, Systems Administrator STUDIO 3 ARCHITECTS 909 982 1717

3 2

[opensuse] Kernel compilation the openSUSE way?
by Bjoern Voigt 28 Nov '21

28 Nov '21

I usually take the newest openSUSE kernel (from repository Kernel_stable). But since some month I have a DVB T2 HD card, which requires a patch (see https://bugzilla.kernel.org/show_bug.cgi?id=194171). So I need to compile kernels myself. I have a working compilation path. But the current path has 12 steps! It takes some time. I wonder, why it is so complicated to configure, compile and install a Kernel under openSUSE. Is there a better/easier/automated way to configure, compile and install a Kernel under openSUSE? I know this blog article. But the article uses Vanilla kernels and also needs 6 steps. With additional patches (4 steps), third-party modules (2 steps) and cleanup (1 step) the article would also need 13 steps: Compiling the Linux Kernel, the SUSE way https://www.suse.com/communities/blog/compiling-de-linux-kernel-suse-way/ This is my Kernel configuration, compilation and installation path: 1. Update kernel-source and kernel-default from Kernel_stable repository 2. Save kernel-source: cp -a /usr/src/linux-4.x.y-... /usr/src/linux-4.x.y-my 3. Apply my patches cd /usr/src/linux-4.x.y-my patch -b -p1 < ~myuser/.../my-kernel-patch.patch 4. Copy standard configuration: cd /usr/src/linux-4.x.y-my cp -v /boot/config-4.11.4-1.gcba98ee-default .config 5. Edit .config: remove CONFIG_LOCALVERSION, CONFIG_DEBUG_KERNEL, CONFIG_EXPERT remove some hardware-dependent settings 6. edit configuration interactively: Disable CONFIG_EXPERT and CONFIG_DEBUG_KERNEL, because otherwise "make binrpm-pkg" creates huge kernel binaries. make oldconfig [...] Local version - append to kernel release (LOCALVERSION) [] (NEW) -my1 * * Configure standard kernel features (expert users) * Configure standard kernel features (expert users) (EXPERT) [N/y/?] (NEW) Kernel debugging (DEBUG_KERNEL) [N/y/?] (NEW) make menuconfig Do some additional configuration. 7. Compile kernel (-j4 for four processor cores, ionice and nice to reduce the load, binrpm-pkg for RPM without source-RPM) make clean nice ionice -c idle make -j4 binrpm-pkg 8. Install the kernel RPM package rpm -Uvh /usr/src/packages/RPMS/x86_64/kernel-4.x.y_my1-....x86_64.rpm 9. Install necessary symbolic links for "dkms" cd /lib/modules/4.x.y-my1 ln -sv /usr/src/linux-4.x.y-my source ln -sv /usr/src/linux-4.x.y-my build 10. Update third-party modules (e.g. Nvidia driver): dkms install -m nvidia -v 375.66 -k 4.x.y-my1 11. Cleanup cd /usr/src/linux-4.x.y-my make clean 12. Select Grub configuration and reboot grub2-once --list | less grub2-once 2 reboot Greetings, Björn -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

7 13

Web Site Standards
by Bryan Tyson 25 Sep '21

25 Sep '21

On Wednesday 03 July 2002 03:38, Michael wrote: > I tried to visit this site. > http://www.bet365.com > The result upset me so much i sent them this. I sent the letter below, and I encourage everyone on the list to send a similar letter. ----------------------------------------- Subject: Create a Real Web Site Please From: Bryan S. Tyson <bryantyson(a)earthlink.net> To: webmaster(a)bet365.com When attempting to view your site using Konqueror 2.2.1 and Mozilla 0.9.4, both Linux web browsers, I was curtly informed that my browser is "incompatible." Your site, sir, is what is "incompatible." Stick with established standards and real html, not Microsoft proprietary "features." *************************************************** Powered by SuSE Linux 7.3 Professional KDE 2.2.1 KMail 1.3.1 This is a Microsoft-free computer Bryan S. Tyson bryantyson(a)earthlink.net ***************************************************

10 9

Mount Windows NT(NTFS) drive as drive Z: for all users
by Keith Jacobs 25 Sep '21

25 Sep '21

We have an winNT server and need to auto mount a shared folder as if it were a windose mapped drive Z: on SuSE8 Could someone please explain how to do this and how to make sure it is set-up for every user everytime the system is booted. Thanks Regards Keith Jacobs New to Linux

3 2

[opensuse] libc segfaults attaching an iPad
by Dave Howorth 26 Mar '21

26 Mar '21

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

4 7

[opensuse] Raid, Raid6, what file system for good fault tolerance?
by cagsm 21 Dec '20

21 Dec '20

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 23

[opensuse] Issue with smartd
by Carlos E. R. 21 Oct '20

21 Oct '20

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

3 7

[opensuse] Re: questions about webpin
by Knurpht-openSUSE 16 May '20

16 May '20

Try zypper in opi Then f.e. opi dog -- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

6 15

[opensuse] Thunderbird fails to GPG sign S/MIME messages
by Carlos E. R. 10 Nov '19

10 Nov '19

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I suddenly have a problem signing messages on Thunderbird. It pops a message box that says: unable to (save or send) You specified that this message should be digitally signed, but the application either failed to find the signing certificate specified in your Mail & Newsgroup Account Settings, or the certificate has expired which is not true. However, I noticed that if in account settings, where it says: If both, Enigmail and S/MIME encryption are possible, then (*)Prefer S/MIME ( )Prefer Enigmail(OpenPGP) it fails with S/MIME and works with OpenPGP. - -- Cheers Carlos E. R. (from 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXbLXNxwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVx44AoIE9H+5EChAbz9WhwvPu OZGVYwoJAJ4onLFwft0Sz3WQ/obugiqct6gpmg== =3IBI -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 2

[opensuse] imagemagick convert
by David C. Rankin 01 Nov '19

01 Nov '19

Wow!, ImageMagick is now crippled by default. You have to change security policy to convert a .pdf to a .jpg. I attempted to convert: $ convert 20191030_Gohmert.pdf -resize 151 -quality 90 -background white 20191030_Gohmert_thumb.png convert: not authorized `20191030_Gohmert.pdf' @ error/constitute.c/ReadImage/464. convert: no images defined `20191030_Gohmert_thumb.jpg' @ error/convert.c/ConvertImageCommand/3149. What? I'm not authorized to use convert?? Sadly, it seems that is so: https://stackoverflow.com/questions/42928765/convertnot-authorized-aaaa-err… Changing the security policy file and I can now use it. Do we really want to ship a broken imagemagick by default? -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 7

[opensuse] Discontinuation Notice on 15.0 - No longer plan to support it until 16.0 released?
by David C. Rankin 01 Nov '19

01 Nov '19

All, Just for clarification, in an earlier thread on this list, the plan (likely) was to support 15.0 with updates until the release of 16.0. On the Security and Announce lists, Marcus gave Advance Notice of discontinuation of 15.0 at the end of November. It is no longer the plan to extend 15.0 until 16.0 is release? As it is, that will leave 15.1 as the only release, 15.2 isn't scheduled for release until May?? -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

6 8

[opensuse] disable overwriting grub.cfg
by Istvan Gabor 31 Oct '19

31 Oct '19

Hello: My question applies to all openSUSE versions that use grub2 and dracut/mkintird. Currently I use Leap 15.1, and 42.2. I do not like the default grub configuration therefore I adjust /boot/grub2/grub.cfg manually. When I update the kernel or use mkinitrd, grub.cfg is regenerated, and my settings are overwritten. How can I disable regeneration of grub.cfg? I want to take care of grub.cfg myself. Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

10 14

[opensuse] systemctl command line completion is very slow
by Carlos E. R. 31 Oct '19

31 Oct '19

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Suppose I type: systemctl status smart[tab][tab] and I get nothing. One second, two seconds... so I insist and hit tab several times, and after several seconds I get (one line per second): Isengard:~ # systemctl status smart smartcard.target smartd.service smartd_generate_opts.path smartd_generate_opts.service Isengard:~ # systemctl status smart smartcard.target smartd.service smartd_generate_opts.path smartd_generate_opts.service Isengard:~ # systemctl status smart smartcard.target smartd.service smartd_generate_opts.path smartd_generate_opts.service Isengard:~ # systemctl status smart and then I can type "d" and enter. Why is it that slow? It is an M2 disk. ie, SSD technology. It responds instantly when completing a normal command: Isengard:~ # smart smart_agetty smartctl smartd Isengard:~ # smart And that system is not busy at all, load 0.20 - -- Cheers Carlos E. R. (from 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXbWH4Bwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVGVsAn0iKRPoFDlOYkwmj9Y7r OFv4Mt0qAJ9IUPwXKdECRzNyJaD5HiR1dZU6Yg== =lB6T -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

9 15

Re: [opensuse] Trying to make audio play under a different user, with pulse? Solved.
by Michael Hamilton 31 Oct '19

31 Oct '19

On Tuesday 29 October 2019, Carlos E. R. wrote: > > Hi, > > I bumped into this post from 2014 that says how to do the above: > > <http://billauer.co.il/blog/2014/01/pa-multiple-users/> > > basically, he says to: > > cp /etc/pulse/default.pa ~/.pulse/ > > and then edit ~/.pulse/default.pa and add this line: > > load-module module-native-protocol-tcp auth-ip-acl=127.0.0.1 > > > > And on the second user, edit ./-pulse/client.conf and add: > > default-server = 127.0.0.1 > > > The comments say of some modifications. It is now not directory .pulse, > but "/.config/pulse/", and I assume file "default.pa". And on the other > user, it is /.config/pulse/client.conf > > So now I have (two users; cer has the desktop): > > cer@Isengard:~> cat .config/pulse/default.pa | grep 127 > load-module module-native-protocol-tcp auth-ip-acl=127.0.0.1 > cer@Isengard:~> > > cer-g@Isengard:~> cat .config/pulse/client.conf > default-server = 127.0.0.1 > cer-g@Isengard:~> > > I logout, login, and try - does not work: > > cer-g@Isengard:~> paplay /usr/share/sounds/purple/login.wav > Connection failure: Connection refused > pa_context_connect() failed: Connection refused > cer-g@Isengard:~> > > (paplay is the pulseaudio command to play sounds) > > (paplay does work as "cer" - but not via ssh) > > > I was going to ask here for ideas, then found this comment from 2016: > > +++--------------- > Note that you can also set network access using paprefs (Debian package of > same name). In paprefs, choose Network server => Enable network access to > local sound devices & Don’t require authentication. > There’s no need to copy/edit default.pa or to create a client.conf for the > secondary user(s). > > Paprefs uses gconf and stores its config in > ~/.gconf/system/pulseaudio/modules/remote-access/\%gconf.xml (you’d better > remember this if you also use a default.pa and are wondering why something > doesn’t work). > ---------------+++ > > So I undid what I had done so far (delete those two new config files), > installed paprefs, did that change, tested, and it works! I can play > "kodi" as another user :-) > > (I want kodi as another user as a trick to test a different kodi config) > > > > The worry now is that any user (local, I hope) can play sound. No security > control. > > I have some notes I wrote up when I last wanted to do this on Leap and it still seems to be working on tumbleweed. Your devices will differ, but maybe the rest would apply. - Sound, remote sound use UNIX sockets - server user /home/michael/.pulse/default.pa .include /etc/pulse/default.pa # Share this server load-module module-native-protocol-unix auth-anonymous=1 socket=/tmp/share-pulse # Default output to analog onboard sound and usb fiio load-module module-combine-sink sink_name=combined slaves=alsa_output.pci-0000_00_14.2.analog-stereo,alsa_output.usb-FiiO_DigiHug_USB_Audio-01.analog-stereo set-default-sink combined KDE default order of outputs Settings->hardware->audio and video Select audio-playback (to configure all playback sources) Reorder Prefer/Defer to put devices in prefered order. X11 client shared audio Find prefered sink name: pactl list short sources Put in /home/clientuser/.pulse/client.conf default-server = unix:/tmp/share-pulse default-sink = alsa_output.usb-FiiO_DigiHug_USB_Audio-01.analog-stereo Set alsa to use pulse in /home/clientuser/.asoundrc (but need to figure out how to avoid looping if logged in locally - perhaps define alsa fallbacks) pcm.!default { type pulse device "alsa_output.usb-FiiO_DigiHug_USB_Audio-01.analog-stereo" } ctl.!default { type pulse } I hope this helps. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Advice for NVIDIA and Tumbleweed
by Roger Oberholtzer 30 Oct '19

30 Oct '19

I need to use a GPU/CUDA for some deep learning work. It should result in at least a 100x speedup compared to using the CPU. So, I will be needing to use the NVIDIA drivers instead of Noveau. I have a couple questions: 1. I see that the kernel drivers on https://download.nvidia.com/opensuse/tumbleweed/x86_64/ are for kernel-default-5.3.6-1.1.x86_64, while the current one (on my system) is kernel-default-5.3.7-1.2.x86_64. I know that the NVIDIA stuff is usually a little behind. When doing a zypper dup, has it worked that the kernel does not get updated until all dependencies (e.g. NVIDIA) are present? Or does one need to do something else to keep these two things consistent? 2. Are there any things one should consider related to CUDA? Any kernel options so set? Anyone else compiling/running CUDA code on Tumbleweed? https://en.opensuse.org/SDB:NVIDIA_drivers says a little bit. But I don't see much about this there. TIA for any shared experiences. -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 2

[opensuse] Dark theme forced on XFCE
by Carlos E. R. 29 Oct '19

29 Oct '19

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, when I upgraded my "server" to 15.1 from 15.0, the XFCE desktop "Appeareance" got switched to "Mint-Y-Darker-Teal". I hate dark themes, I can not read things. The borders are so dark that I don't know where a window ends to catch the border with the mouse. But the thing is, if I go to settings/Appearance and choose a light theme such as Aswaita or Clearlooks, or Crux, the tittle bar of the windows stays dark. Is this a bug? Something I can do to force change of the title bar? - -- Cheers Carlos E. R. (from 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXbg4shwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVyZYAn35dsYkpTQYXKPYNdukd Ix0fNVugAJ4xqD+XXWIgU1vkJpvpgBXjM9vWRg== =A1ng -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 2

[opensuse] os-en
by Carlos E. R. 29 Oct '19

29 Oct '19

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Just after I login (XFCE, 15.1), I get 100% CPU, and this in the log - hundreds of coredumps, non stop: .... <3.6> 2019-10-25 12:07:44 Telcontar dbus-daemon 4500 - - [session uid=1000 pid=4500] Activating via systemd: service name='org.freedesktop.Tracker1' unit='tracker-store.service' requested by ':1.67' (uid=1000 pid=5669 comm="gdbus call -e -d org.freedesktop.DBus -o /org/free") <3.6> 2019-10-25 12:07:44 Telcontar dbus-daemon 4500 - - [session uid=1000 pid=4500] Successfully activated service 'org.freedesktop.Tracker1' <3.6> 2019-10-25 12:07:44 Telcontar dbus-daemon 4500 - - [session uid=1000 pid=4500] Activating via systemd: service name='org.gnome.zeitgeist.Engine' unit='zeitgeist.service' requested by ':1.70' (uid=1000 pid=5662 comm="zeitgeist-datahub ") <3.6> 2019-10-25 12:07:45 Telcontar dbus-daemon 4500 - - [session uid=1000 pid=4500] Activating via systemd: service name='org.gnome.zeitgeist.SimpleIndexer' unit='zeitgeist-fts.service' requested by ':1.71' (uid=1000 pid=5690 comm="/usr/bin/zeitgeist-daemon ") <3.6> 2019-10-25 12:07:45 Telcontar dbus-daemon 4500 - - [session uid=1000 pid=4500] Successfully activated service 'org.gnome.zeitgeist.Engine' <3.6> 2019-10-25 12:07:45 Telcontar dbus-daemon 4500 - - [session uid=1000 pid=4500] Successfully activated service 'org.freedesktop.thumbnails.Thumbnailer1' <1.4> 2019-10-25 12:07:45 Telcontar zeitgeist-datah 5732 - - zeitgeist-datahub.vala:224: Unable to get name "org.gnome.zeitgeist.datahub" on the bus! <3.6> 2019-10-25 12:07:45 Telcontar dbus-daemon 4500 - - [session uid=1000 pid=4500] Successfully activated service 'org.gnome.zeitgeist.SimpleIndexer' <1.4> 2019-10-25 12:07:49 Telcontar zeitgeist-fts 5729 - - Unable to get info on application://kde-noteedit.desktop <1.4> 2019-10-25 12:07:57 Telcontar baloo_file 5989 - - Failed to register via dbus. Another instance is running <1.7> 2019-10-25 12:07:57 Telcontar drkonqi 5990 - - found lsb_release <1.7> 2019-10-25 12:07:57 Telcontar drkonqi 5990 - - Using /proc to determine executable path <1.7> 2019-10-25 12:07:57 Telcontar drkonqi 5990 - - Executable is: "/usr/bin/baloo_file" <1.7> 2019-10-25 12:07:57 Telcontar drkonqi 5990 - - Executable exists: true <1.7> 2019-10-25 12:07:57 Telcontar drkonqi 5990 - - Enabling drkonqi crash catching <1.4> 2019-10-25 12:07:57 Telcontar drkonqi 5990 - - QSystemTrayIcon::setVisible: No Icon set <1.7> 2019-10-25 12:07:59 Telcontar drkonqi 5990 - - Sending SIGSTOP to process <3.6> 2019-10-25 12:08:02 Telcontar systemd 1 - - Created slice system-systemd\x2dcoredump.slice. <3.6> 2019-10-25 12:08:02 Telcontar systemd 1 - - Started Process Core Dump (PID 6040/UID 0). <3.6> 2019-10-25 12:08:02 Telcontar systemd 1 - - Started Process Core Dump (PID 6050/UID 0). <1.2> 2019-10-25 12:08:02 Telcontar systemd-coredump 6041 - - Process 6039 (single) of user 1000 dumped core. <3.6> 2019-10-25 12:08:03 Telcontar systemd 1 - - Started Process Core Dump (PID 6060/UID 0). <1.2> 2019-10-25 12:08:03 Telcontar systemd-coredump 6051 - - Process 6049 (single) of user 1000 dumped core. <3.6> 2019-10-25 12:08:03 Telcontar systemd 1 - - Started Process Core Dump (PID 6080/UID 0). <1.2> 2019-10-25 12:08:03 Telcontar systemd-coredump 6061 - - Process 6059 (single) of user 1000 dumped core. <3.6> 2019-10-25 12:08:03 Telcontar systemd 1 - - Started Process Core Dump (PID 6091/UID 0). <1.2> 2019-10-25 12:08:04 Telcontar systemd-coredump 6082 - - Process 6079 (single) of user 1000 dumped core. <3.6> 2019-10-25 12:08:04 Telcontar systemd 1 - - Started Process Core Dump (PID 6102/UID 0). <1.2> 2019-10-25 12:08:04 Telcontar systemd-coredump 6092 - - Process 6090 (single) of user 1000 dumped core. <3.6> 2019-10-25 12:08:04 Telcontar systemd 1 - - Started Process Core Dump (PID 6112/UID 0). <1.2> 2019-10-25 12:08:04 Telcontar systemd-coredump 6103 - - Process 6101 (single) of user 1000 dumped core. <3.6> 2019-10-25 12:08:05 Telcontar systemd 1 - - Started Process Core Dump (PID 6121/UID 0). <1.2> 2019-10-25 12:08:05 Telcontar systemd-coredump 6113 - - Process 6111 (single) of user 1000 dumped core. <3.6> 2019-10-25 12:08:05 Telcontar pulseaudio 4571 - - E: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. <4.5> 2019-10-25 12:08:05 Telcontar dbus-daemon 1535 - - [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) <3.6> 2019-10-25 12:08:05 Telcontar systemd 1 - - Started Process Core Dump (PID 6128/UID 0). <1.2> 2019-10-25 12:08:05 Telcontar systemd-coredump 6122 - - Process 6120 (single) of user 1000 dumped core. <3.6> 2019-10-25 12:08:06 Telcontar systemd 1 - - Started Process Core Dump (PID 6135/UID 0). <1.2> 2019-10-25 12:08:06 Telcontar systemd-coredump 6129 - - Process 6127 (single) of user 1000 dumped core. <3.6> 2019-10-25 12:08:06 Telcontar systemd 1 - - Started Process Core Dump (PID 6142/UID 0). <1.2> 2019-10-25 12:08:06 Telcontar systemd-coredump 6136 - - Process 6134 (single) of user 1000 dumped core. <3.6> 2019-10-25 12:08:06 Telcontar systemd 1 - - Started Process Core Dump (PID 6149/UID 0). <1.2> 2019-10-25 12:08:07 Telcontar systemd-coredump 6143 - - Process 6141 (single) of user 1000 dumped core. <3.6> 2019-10-25 12:08:07 Telcontar systemd 1 - - Started Process Core Dump (PID 6159/UID 0). <1.2> 2019-10-25 12:08:07 Telcontar systemd-coredump 6150 - - Process 6148 (single) of user 1000 dumped core. <3.6> 2019-10-25 12:08:07 Telcontar systemd 1 - - Started Process Core Dump (PID 6166/UID 0). <1.2> 2019-10-25 12:08:08 Telcontar systemd-coredump 6160 - - Process 6158 (single) of user 1000 dumped core. <3.6> 2019-10-25 12:08:08 Telcontar systemd 1 - - Started Process Core Dump (PID 6178/UID 0). <1.2> 2019-10-25 12:08:08 Telcontar systemd-coredump 6167 - - Process 6165 (single) of user 1000 dumped core. <3.6> 2019-10-25 12:08:08 Telcontar systemd 1 - - Started Process Core Dump (PID 6185/UID 0). <1.2> 2019-10-25 12:08:08 Telcontar systemd-coredump 6179 - - Process 6177 (single) of user 1000 dumped core. <3.6> 2019-10-25 12:08:09 Telcontar systemd 1 - - Started Process Core Dump (PID 6192/UID 0). <1.2> 2019-10-25 12:08:09 Telcontar systemd-coredump 6186 - - Process 6184 (single) of user 1000 dumped core. <3.6> 2019-10-25 12:08:09 Telcontar systemd 1 - - Started Process Core Dump (PID 6203/UID 0). <1.2> 2019-10-25 12:08:09 Telcontar systemd-coredump 6193 - - Process 6191 (single) of user 1000 dumped core. <3.6> 2019-10-25 12:08:10 Telcontar systemd 1 - - Started Process Core Dump (PID 6226/UID 0). <1.2> 2019-10-25 12:08:10 Telcontar systemd-coredump 6205 - - Process 6202 (single) of user 1000 dumped core. <3.6> 2019-10-25 12:08:10 Telcontar systemd 1 - - Started Process Core Dump (PID 6235/UID 0). <1.2> 2019-10-25 12:08:10 Telcontar systemd-coredump 6227 - - Process 6225 (single) of user 1000 dumped core. <3.6> 2019-10-25 12:08:10 Telcontar systemd 1 - - Started Process Core Dump (PID 6244/UID 0). <1.2> 2019-10-25 12:08:11 Telcontar systemd-coredump 6236 - - Process 6234 (single) of user 1000 dumped core. <3.6> 2019-10-25 12:08:11 Telcontar systemd 1 - - Started Process Core Dump (PID 6251/UID 0). <1.2> 2019-10-25 12:08:11 Telcontar systemd-coredump 6245 - - Process 6243 (single) of user 1000 dumped core. And it goes, it goes... till I do: killall tracker-store tracker-extract tracker-miner-apps tracker-miner-fs Telcontar:~ # coredumpctl TIME PID UID GID SIG COREFILE EXE Fri 2019-10-25 12:08:02 CEST 6039 1000 100 31 present /usr/lib/tracker-extract Fri 2019-10-25 12:08:03 CEST 6049 1000 100 31 present /usr/lib/tracker-extract Fri 2019-10-25 12:08:03 CEST 6059 1000 100 31 present /usr/lib/tracker-extract Fri 2019-10-25 12:08:04 CEST 6079 1000 100 31 present /usr/lib/tracker-extract Fri 2019-10-25 12:08:04 CEST 6090 1000 100 31 present /usr/lib/tracker-extract Fri 2019-10-25 12:08:04 CEST 6101 1000 100 31 present /usr/lib/tracker-extract Fri 2019-10-25 12:08:05 CEST 6111 1000 100 31 present /usr/lib/tracker-extract Fri 2019-10-25 12:08:05 CEST 6120 1000 100 31 present /usr/lib/tracker-extract Fri 2019-10-25 12:08:06 CEST 6127 1000 100 31 present /usr/lib/tracker-extract Fri 2019-10-25 12:08:06 CEST 6134 1000 100 31 present /usr/lib/tracker-extract Fri 2019-10-25 12:08:07 CEST 6141 1000 100 31 present /usr/lib/tracker-extract Fri 2019-10-25 12:08:07 CEST 6148 1000 100 31 present /usr/lib/tracker-extract Fri 2019-10-25 12:08:08 CEST 6158 1000 100 31 present /usr/lib/tracker-extract Fri 2019-10-25 12:08:08 CEST 6165 1000 100 31 present /usr/lib/tracker-extract Fri 2019-10-25 12:08:08 CEST 6177 1000 100 31 present /usr/lib/tracker-extract Fri 2019-10-25 12:08:09 CEST 6184 1000 100 31 present /usr/lib/tracker-extract Fri 2019-10-25 12:08:09 CEST 6191 1000 100 31 present /usr/lib/tracker-extract Fri 2019-10-25 12:08:10 CEST 6202 1000 100 31 present /usr/lib/tracker-extract Fri 2019-10-25 12:08:10 CEST 6225 1000 100 31 present /usr/lib/tracker-extract Fri 2019-10-25 12:08:11 CEST 6234 1000 100 31 present /usr/lib/tracker-extract Fri 2019-10-25 12:08:11 CEST 6243 1000 100 31 present /usr/lib/tracker-extract ... Fri 2019-10-25 12:09:42 CEST 8215 1000 100 31 present /usr/lib/tracker-extract Fri 2019-10-25 12:09:42 CEST 8223 1000 100 31 present /usr/lib/tracker-extract Fri 2019-10-25 12:09:43 CEST 8233 1000 100 31 present /usr/lib/tracker-extract Fri 2019-10-25 12:09:43 CEST 8240 1000 100 31 present /usr/lib/tracker-extract lines 172-226/226 (END) Telcontar:~ # coredumpctl info 8240 PID: 8240 (single) UID: 1000 (cer) GID: 100 (users) Signal: 31 (SYS) Timestamp: Fri 2019-10-25 12:09:42 CEST (12min ago) Command Line: /usr/lib/tracker-extract Executable: /usr/lib/tracker-extract Control Group: /user.slice/user-1000.slice/session-4.scope Unit: session-4.scope Slice: user-1000.slice Session: 4 Owner UID: 1000 (cer) Boot ID: 279fde7586254db6b3d727f045ecd8e5 Machine ID: 2ce1d54548517a7307c1c2bc38206d00 Hostname: Telcontar Storage: /var/lib/systemd/coredump/core.single.1000.279fde7586254db6b3d727f045ecd8e5.8240.1571998182000000.lz4 Message: Process 8240 (single) of user 1000 dumped core. Telcontar:~ # Telcontar:~ # coredumpctl dump 8240 > coredumpof8240_tracker-extract PID: 8240 (single) UID: 1000 (cer) GID: 100 (users) Signal: 31 (SYS) Timestamp: Fri 2019-10-25 12:09:42 CEST (15min ago) Command Line: /usr/lib/tracker-extract Executable: /usr/lib/tracker-extract Control Group: /user.slice/user-1000.slice/session-4.scope Unit: session-4.scope Slice: user-1000.slice Session: 4 Owner UID: 1000 (cer) Boot ID: 279fde7586254db6b3d727f045ecd8e5 Machine ID: 2ce1d54548517a7307c1c2bc38206d00 Hostname: Telcontar Storage: /var/lib/systemd/coredump/core.single.1000.279fde7586254db6b3d727f045ecd8e5.8240.1571998182000000.lz4 Message: Process 8240 (single) of user 1000 dumped core. Telcontar:~ # l -h coredumpof8240_tracker-extract - -rw-r--r-- 1 root root 183M Oct 25 12:24 coredumpof8240_tracker-extract Telcontar:~ # less coredumpof8240_tracker-extract "coredumpof8240_tracker-extract" may be a binary file. See it anyway? Telcontar:~ # Telcontar:~ # locate tracker-extract | grep service /usr/lib/systemd/user/tracker-extract.service Telcontar:~ # Telcontar:~ # cat /usr/lib/systemd/user/tracker-extract.service [Unit] Description=Tracker metadata extractor [Service] Type=dbus BusName=org.freedesktop.Tracker1.Miner.Extract ExecStart=/usr/lib/tracker-extract Restart=on-failure # Don't restart after tracker daemon -k (aka tracker-control -k) RestartPreventExitStatus=SIGKILL Telcontar:~ # How can I make it not enter a fast crash loop? - -- Cheers Carlos E. R. (from 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXbLOvxwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVsN4AoJZ/RcnfpYieG4YTHSFj 6eNPSGwOAJ4ldsq/U8zQAKgZDYfAX5p4saY+cg== =MC/K -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 11

[opensuse] Self-destruct in 5 seconds. Have a nice day...
by Carlos E. R. 29 Oct '19

29 Oct '19

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Huh? I notice the above in the warning log, with a bit more detail in the messages log: <1.5> 2019-10-28T22:50:42.623834+01:00 Isengard RPM - - install paprefs-lang-0.9.10-lp151.2.3.noarch: success <1.5> 2019-10-28T22:50:42.626233+01:00 Isengard RPM - - install paprefs-lang-0.9.10-lp151.2.3.noarch: success <1.5> 2019-10-28T22:50:42.626740+01:00 Isengard RPM - - Transaction ID 5db762b2 finished: 0 <3.6> 2019-10-28T22:55:58.063198+01:00 Isengard systemd 1 - - Unmounting /var/cache/zypp/nfs_packages... <0.4> 2019-10-28T22:55:58.093851+01:00 Isengard kernel - - - [194307.441511] VFS: Busy inodes after unmount of 0:54. Self-destruct in 5 seconds. Have a nice day... <3.6> 2019-10-28T22:55:58.149233+01:00 Isengard systemd 1 - - Unmounted /var/cache/zypp/nfs_packages. <4.5> 2019-10-28T22:59:38.383442+01:00 Isengard sudo - - - cer : TTY=pts/9 ; PWD=/home/cer ; USER=root ; COMMAND=/usr/sbin/iotop -o -d 3.3333 It may refer to the automated umounting of "/var/cache/zypp/nfs_packages", via nfs - fstab: telcontar.valinor:/data/storage_c/repositorios_zypp/ /var/cache/zypp/nfs_packages nfs noauto,nofail,x-systemd.automount,x-systemd.idle-timeout=300,_netdev,nfsvers=4 0 0 I see no message in the server at that timeframe. What does it mean? What will selfdestruct, my computer? :-o - -- Cheers Carlos E. R. (from 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXbdm6Rwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfV6tEAn1fWIH/RaltA1eXYvzJs TJ5eGjUfAJ9D52D2G9RnlqPS9Xk4jMKX5/oeww== =/qsB -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 10

[opensuse] Trying to make audio play under a different user, with pulse? Solved.
by Carlos E. R. 29 Oct '19

29 Oct '19

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I bumped into this post from 2014 that says how to do the above: <http://billauer.co.il/blog/2014/01/pa-multiple-users/> basically, he says to: cp /etc/pulse/default.pa ~/.pulse/ and then edit ~/.pulse/default.pa and add this line: load-module module-native-protocol-tcp auth-ip-acl=127.0.0.1 And on the second user, edit ./-pulse/client.conf and add: default-server = 127.0.0.1 The comments say of some modifications. It is now not directory .pulse, but "/.config/pulse/", and I assume file "default.pa". And on the other user, it is /.config/pulse/client.conf So now I have (two users; cer has the desktop): cer@Isengard:~> cat .config/pulse/default.pa | grep 127 load-module module-native-protocol-tcp auth-ip-acl=127.0.0.1 cer@Isengard:~> cer-g@Isengard:~> cat .config/pulse/client.conf default-server = 127.0.0.1 cer-g@Isengard:~> I logout, login, and try - does not work: cer-g@Isengard:~> paplay /usr/share/sounds/purple/login.wav Connection failure: Connection refused pa_context_connect() failed: Connection refused cer-g@Isengard:~> (paplay is the pulseaudio command to play sounds) (paplay does work as "cer" - but not via ssh) I was going to ask here for ideas, then found this comment from 2016: +++--------------- Note that you can also set network access using paprefs (Debian package of same name). In paprefs, choose Network server => Enable network access to local sound devices & Don’t require authentication. There’s no need to copy/edit default.pa or to create a client.conf for the secondary user(s). Paprefs uses gconf and stores its config in ~/.gconf/system/pulseaudio/modules/remote-access/\%gconf.xml (you’d better remember this if you also use a default.pa and are wondering why something doesn’t work). - ---------------+++ So I undid what I had done so far (delete those two new config files), installed paprefs, did that change, tested, and it works! I can play "kodi" as another user :-) (I want kodi as another user as a trick to test a different kodi config) The worry now is that any user (local, I hope) can play sound. No security control. - -- Cheers Carlos E. R. (from 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXbdlZBwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVpNQAnRBV0aWBK/sZmKBZSUVU /BOf3mQcAJ9LEAnbdMP8QHiIpp73aMV5HRkIJw== =WCOy -----END PGP SIGNATURE-----

3 2

[opensuse] NetworkManager, dhcp -> "NTP_SERVER_LIST" empty
by mh＠mike.franken.de 28 Oct '19

28 Oct '19

Hi *, on my dhcp clients using NetworkManager "NTP_SERVER_LIST" is empty. So they always fall back to a static ntp policy. Looking into the lease files, they contain option ntp-servers 192.168.1.1; But this information isn't used obviously. Is this a bug or some kind of misconfiguration? I experimented with and without chrony, systemd-timedated ... To my understanding systemd-timedated should use chrony, if it is installed and an appropriate file exists in /usr/lib/systemd/ntp-units.d. chrony in turn should be provided with a list of ntp servers in /var/run/netconfig/chrony.servers, but this file remains empty, because NetworkManager never sees the above mentioned option. Any idea? TIA. Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 4

[opensuse] Repository search page problem
by Carlos E. R. 28 Oct '19

28 Oct '19

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm trying to search for a newer smartmontools package than the official one for Leap, as the current one has problems with one of my disks. So I use the Firefox search thing for openSUSE packages, and it takes me to a changed search page. First URL is: <https://software.opensuse.org/package/smartmontools?search_term=smartmontoo…> Clicking on community packages for 15 one, I see a few, so on the line for " home:plater" I click on "expert download". This takes me to a confusing page: <https://software.opensuse.org/download/package?package=smartmontools&projec…> but apparently it is asking to select openSUSE or SLE (what, doesn't it already know from the preceding page?). More confusion, and I click on "Add repository and install manually". This opens a list for all distributions, and I find this paragraph: For Leap 15.1 run the following as root: zypper addrepo https://download.opensuse.org/repositories/home:plater/Leap_15.1/home:plate… zypper refresh zypper install smartmontools So I do: Isengard:~ # zypper ar -k -f -n "OBSH Platter" "https://download.opensuse.org/repositories/home:plater/Leap_15.1/home:plate…" "OBSH_platter" Adding repository 'OBSH Platter' .....................................................................................................[done] Repository 'OBSH Platter' successfully added URI : https://download.opensuse.org/repositories/home:plater/Leap_15.1/home:plate… Enabled : Yes GPG Check : Yes Autorefresh : Yes Priority : 99 (default priority) Repository priorities in effect: (See 'zypper lr -P' for details) 90 (raised priority) : 1 repository 98 (raised priority) : 1 repository 99 (default priority) : 7 repositories Isengard:~ # zypper ref Repository 'Packman Repository' is up to date. Repository 'Local Repo' is up to date. Retrieving repository 'OBSH Platter' metadata .......................................................................................[error] Repository 'OBSH Platter' is invalid. [OBSH_platter|https://download.opensuse.org/repositories/home:plater/Leap_15…] Valid metadata not found at specified URL Please check if the URIs defined for this repository are pointing to a valid repository. Skipping repository 'OBSH Platter' because of the above error. Repository 'OBS: security' is up to date. Repository 'Main Repository (NON-OSS)' is up to date. Repository 'Update Repository (Non-Oss)' is up to date. Repository 'Main Repository (OSS)' is up to date. Repository 'Main Update Repository' is up to date. Repository 'google-chrome' is up to date. Some of the repositories have not been refreshed because of an error. Isengard:~ # As you see, it fails, invalid URL for a repo. The correct URL for 15.1 is: https://download.opensuse.org/repositories/home:plater/Leap_15.1/ Now, where can one report this error? - -- Cheers Carlos E. R. (from 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXbWE1Rwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVu2AAmgO1atNZg3h+3+RIkdzE nLg73udNAJ9FB0BJm6P4+RaRIkM8cHcy5CjKWA== =fcpr -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 6

[opensuse] [Leap 15] RawTherapee in Leap15.1
by Bob Williams 24 Oct '19

24 Oct '19

I'm trying to install RawTherapee on a Leap 15.1 machine. There is no package in the openSUSE repositories, and the download on the RawTherapee website is a 97MB *.appimage file. I'm not sure what to do with an .appimage. Any suggestions, please? Bob -- Bob Williams System: Linux 4.12.14-lp151.28.20-default Desktop: KDE Frameworks: 5.55.0, Qt: 5.9.7 and Plasma: 5.12.8

3 3

[opensuse] How do I install ocs-url on Leap 15.1?
by Lance Drager 24 Oct '19

24 Oct '19

There is a package on obs for 15.0, which (of course) doesn't work. Can't seem to locate source for ocs-url. Thanks. Lance Drager

2 1

[opensuse] systemd service unit with instance not working ? (leap 42.3)
by Per Jessen 23 Oct '19

23 Oct '19

I'm sure this is a case of needing another pair of eyes. Mine are getting tired. I have the following service unit: ------------------------ systemctl cat firewall@ipv4 # /etc/systemd/system/firewall@.service [Unit] Description=firewall %i After=network.target [Service] Type=oneshot ExecStart=/usr/local/bin/firewall-%i ExecStop=/usr/local/bin/firewall-%i stop RemainAfterExit=yes [Install] WantedBy=multi-user.target ---------------------------- When I try to start it, it fails: systemd[1]: Starting firewall ipv4... systemd[1094]: firewall(a)ipv4.service: Failed at step EXEC spawning /usr/local/bin/firewall-%i: No such file or directory systemd[1]: firewall(a)ipv4.service: Main process exited, code=exited, status=203/EXEC systemd[1]: Failed to start firewall ipv4. Despite the '/usr/local/bin/firewall-%i: No such file or directory', that script _does_ exist: # ls -lF /usr/local/bin/firewal* -rwxr-xr-x 1 root root 5651 Oct 22 15:08 /usr/local/bin/firewall-ipv4* -rwxr-xr-x 1 root root 2522 May 20 17:41 /usr/local/bin/firewall-ipv6* Remarkably, the exact same works just fine on Leap 15.0. Can anyone help me spot my mistake? Thanks. -- Per Jessen, Zürich (11.8°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 5

[opensuse] changes between openssh 6.6p1 (leap42.1) and openssh 7.2p2 (Leap 42.3) ?
by Per Jessen 23 Oct '19

23 Oct '19

I'm moving a customer to Leap42.3 (they require php5 which we don't seem to build for leap151) - they are now unable to login, public key ssh. Failed publickey for 'brian' from 1.2.3.4 port 33188 ssh2: RSA SHA256:snip Is anyone aware of any significant/incompatible changes between 6.6p1 and 7.2p2 ? With 6.6, the message looked quite different: Accepted publickey for brian from 1.2.3.4 port 56047 ssh2: RSA 57:ba:49:2c:3e:42:cf:78:38:a0:74:83:2c:6a:40:9c [MD5] The client is: Client protocol version 2.0; client software version OpenSSH_6.7p1 Ubuntu-5ubuntu1.4 -- Per Jessen, Zürich (11.8°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 2

[opensuse] Youtube viewing on Chrome based browsers
by Ianseeks 23 Oct '19

23 Oct '19

Hi Is it just me or does Firefox produce better and smoother youtube viewing experience than the Chrome based browsers? I seem to get a lot of image splitting, blanking and shuddering watching youtube videos in Chrome based browsers. Ian -- opensuse:tumbleweed:20191018 Qt: 5.13.1 KDE Frameworks: 5.63.0 - KDE Plasma: 5.17.0 - kwin 5.17.0 kmail2 5.12.2 - akonadiserver 5.12.2 - Kernel: 5.3.6-1-default - xf86-video-nouveau: 1.0.15 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] KDE3 and KDE4/plasma5 in Leap 15.1
by Istvan Gabor 23 Oct '19

23 Oct '19

Hello: I have installed openSUSE Leap 15.1 with KDE3 and it works nicely. Unfortunately there are a few programs (eg digikam) a little bit obsolete for my purposes and I'd prefer to use newer versions, either KDE4 or plasma 5 versions. In openSUSE Leap 42.3 it was possible to install KDE4 programs from a wolfi323 repo. I wonder if it is possible to install KDE4 in Leap 15.1 as well. I am really confused by the terms plasma and KDE frameworks, therefore I don't know what to search for. Plasma 5 would be OK as well but in Leap 15.0 KDE3 and plasma 5 can not coexist. If I remember correctly both KDE3 and plasma 5 use the same .kde dir for their settings. Is there any change regarding this in 15.1? Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 6

[opensuse] looking for portable ssd
by Doug McGarrett 23 Oct '19

23 Oct '19

Saw a Samsung portable 500G ssd, but it spoke about s/w for Windows and Mac. I'd like to have a removable ssd to backup my TW system. Is there some kind of software I need to do this, and if so, where do I find it? What is the simplest software to do the job? I'm running on just one partition (not my choice, but openSuse's). The internal drive is multi-boot with Win 10. (I don't care if Windows is backed up.) All information welcome. Thanx--doug -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

15 44

[opensuse] smartctl usage & GSmartControl
by Dave Howorth 22 Oct '19

22 Oct '19

Prompted by recent discussions about SSD vs HDD I decided to check out my devices with smartctl. But I'm overwhelmed by the smartctl man page! My main disk - sda - is reported to be fine :) My backup disk - sdb - is not found # smartctl -P show /dev/sdb smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.12.14-lp150.12.7-default] (SUSE RPM) Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org /dev/sdb: Unknown USB bridge [0x4971:0xce23 (0x000)] Please specify device type with the -d option. Use smartctl -h to get a usage summary So I tried telling it that the disk is SATA and with that it can find it: # smartctl -P show -d sat /dev/sdb smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.12.14-lp150.12.7-default] (SUSE RPM) Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org Drive found in smartmontools Database. Drive identity strings: MODEL: Hitachi HDS721010CLA332 FIRMWARE: JP4OA3EA match smartmontools Drive Database entry: MODEL REGEXP: (Hitachi )?HDS7210((16|25)CLA[36]82|(32|50)CLA[36]62|(64|75|10)CLA[36]3[02]) FIRMWARE REGEXP: .* MODEL FAMILY: Hitachi Deskstar 7K1000.C ATTRIBUTE OPTIONS: None preset; no -v options are required. but how do I get it to actually scan it regularly like my main disk? I installed GSmartControl in the hope it would be simpler to use. But the Help/Help button does nothing, and for my backup disk it says: Drive information: /dev/sdb (scsi), 1.00 TB, HDS721010CLA332 Basic health check: Unknown Model family: Unknown and the checkboxes to Enable SMART and to Enable Offline Data Collection are both greyed out. So how come it doesn't seem to be able to access the same data as smartctl? Does anybody use it, or is it really as useless as it seems? YaST Partitioner can see it without me having to do anything special, why can't smart? Similar questions also apply to an SD card I happen to have plugged in at the moment! -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 2

[opensuse] Tumbleweed boot difficulty
by Roger Oberholtzer 22 Oct '19

22 Oct '19

I have done a new Tumbleweed install. All went fine. But booting is a problem. I need to run the original installer + update to get it to boot. Then, after doing the update (basically installing any new packages), it boots in to the OS fine. But on it's own, I get the graphic boot menu. Then a black window that lists the name of the kernel, and the name if the initrd file. Then ... nothing. No complaint. It just waits. No keys can do anything (e.g., an alternative console) When it boots, it is working fine, I can do most everything I have tried. I see that /proc/cmdline says: BOOT_IMAGE=/boot/vmlinuz-5.3.2-1-default root=UUID=02e67b6d-c8b5-4de1-8ac5-96a13174a855 splash=silent resume=/dev/disk/by-id/ata-WDC_WD10EARS-003BB1_WD-WCAV5J249635-part3 quiet splash=silent resume=/dev/disk/by-id/ata-WDC_WD10EARS-003BB1_WD-WCAV5J249635-part3 quiet mitigations=off The devices and UUID look correct. I'm just curious why the resume= and quite are listed twice. Could that be the problem? I know that the kernel was updated in all of this. The dracut is whatever the kernel packages does. I have not changed anything. I have tried various boot alternatives (rescue, a snapshot, etc). All do the same. This is a new one on me. -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

7 18

[opensuse] Help Reading Serial Device /dev/bus/usb/001/010
by David C. Rankin 22 Oct '19

22 Oct '19

All, I have a small ARM board that I am working with: http://processors.wiki.ti.com/index.php/LAUNCHXL2-RM46 I can build for the board using gcc-arm-none-eabi and flash the firmware with the TI UniFlash software. However I cannot figure out how to connect a serial device to it. The manual says I should be able to: Configure Baud Rate: 19200, Data Bits: 8, Stop Bits: 2 and Parity: None http://processors.wiki.ti.com/index.php/LAUNCHXL2_RM46:_Project_1 When connected there are two /dev/tty devices created: crw-rw-rw- 1 root dialout 166, 0 Oct 12 21:55 /dev/ttyACM0 crw-rw-rw- 1 root dialout 166, 1 Oct 12 21:55 /dev/ttyACM1 These are in some manner related to: /sys/devices/pci0000\:00/0000\:00\:1c.7/0000\:26\:00.0/usb1/1-1 and the character device /dev/char/189:9 I have tried minicom through /dev/ttyACM0, without success. I can find the device and query it through: # udevadm test /sys/devices/pci0000\:00/0000\:00\:1c.7/0000\:26\:00.0/usb1/1-1 calling: test version 228 This program is for debugging only, it does not run any program specified by a RUN key. It may show incorrect results, because some values may be different, or not available at a simulation run. === trie on-disk === tool version: 228 file size: 7007575 bytes header size 80 bytes strings 1743863 bytes nodes 5263632 bytes Load module index <snip> starting '/usr/lib/udev/mtp-probe /sys/devices/pci0000:00/0000:00:1c.7/0000:26:00.0/usb1/1-1 1 10' '/usr/lib/udev/mtp-probe /sys/devices/pci0000:00/0000:00:1c.7/0000:26:00.0/usb1/1-1 1 10'(out) '0' Process '/usr/lib/udev/mtp-probe /sys/devices/pci0000:00/0000:00:1c.7/0000:26:00.0/usb1/1-1 1 10' succeeded. MODE 0666 /etc/udev/rules.d/71-ti-permissions.rules:10 handling device node '/dev/bus/usb/001/010', devnum=c189:9, mode=0666, uid=0, gid=0 preserve permissions /dev/bus/usb/001/010, 020666, uid=0, gid=0 preserve already existing symlink '/dev/char/189:9' to '../bus/usb/001/010' created db file '/run/udev/data/c189:9' for '/devices/pci0000:00/0000:00:1c.7/0000:26:00.0/usb1/1-1' ACTION=add BUSNUM=001 DEVNAME=/dev/bus/usb/001/010 DEVNUM=010 DEVPATH=/devices/pci0000:00/0000:00:1c.7/0000:26:00.0/usb1/1-1 DEVTYPE=usb_device DRIVER=usb ID_BUS=usb ID_MODEL=XDS110__03.00.00.02__Embed_with_CMSIS-DAP ID_MODEL_ENC=XDS110\x20\x2803.00.00.02\x29\x20Embed\x20with\x20CMSIS-DAP ID_MODEL_ID=bef3 ID_REVISION=0100 ID_SERIAL=Texas_Instruments_XDS110__03.00.00.02__Embed_with_CMSIS-DAP_HLR46000 ID_SERIAL_SHORT=HLR46000 ID_USB_INTERFACES=:020201:0a0000:ff0000:030000: ID_VENDOR=Texas_Instruments ID_VENDOR_ENC=Texas\x20Instruments ID_VENDOR_FROM_DATABASE=Texas Instruments, Inc. ID_VENDOR_ID=0451 MAJOR=189 MINOR=9 PRODUCT=451/bef3/100 SUBSYSTEM=usb TYPE=239/2/1 USEC_INITIALIZED=120561513447 run: '/usr/lib/virtualbox/VBoxCreateUSBNode.sh 189 9 ef' Unload module index Unloaded link configuration context. This is the correct udev rule for the device, but that is where I am stuck. What I need to do is get a serial console open to it so that when I load an executable that reads/writes to stdin/stdout I can see the output and provide the input. (blinking diodes are the board are nice, but worthless for providing user authentication through) Connecting a serial console seems like a simple process, but I must be missing something stupid simple about it. Minicom can be configured for either /dev/ttyACM0 or /dev/ttyACM1 (and N82 19200) but there is nothing ever output on either (even after loading a program that generates output to stdout) Yes, the flash goes fine and I can load different executables to make the diodes respond in varying ways -- so the fact that the code is loaded and running correctly if verified, but how do I interface with the serial terminal on this thing? Anybody been down this road before? -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 9

[opensuse] restoring efi boot / home after failed SSD
by gumb 20 Oct '19

20 Oct '19

I recently suffered a cataclysmic SSD failure. This machine has two SSD drives, the M.2 drive (sdb) holds the root partition (sdb1) and swap, which is all still intact, whilst the SATA drive which failed (sda) held the boot/efi partition in addition to the /home partition, and hence all my personal data. I've installed a new replacement SATA SSD, booted the openSUSE rescue system from a USB stick, changed root to the original oS installation on sdb1 and then, from within yast2, created a new /boot/efi partition (sda1) and /home (sda2) on the new disk. What is the next step to get this to boot? Currently I'm at the error: no such device: /efi/boot/fallback.efi -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

[opensuse] SSH Public Key Authentication Broken By Upgrade [zypper dup]
by Adam Tauno Williams 19 Oct '19

19 Oct '19

After doing a zypper dup to 15.1 all appears to be working great - as expected - except however for SSH public key authentication. GNOME does not prompt for the passphrase and authentication falls back to password mode [assuming the server allows it]. Tips / pointers? __agent is running, correctly linked in environment__ awilliam@beast01:~> ps ax | grep key ... 7245 ? S 0:00 /usr/bin/ssh-agent -D -a /run/user/1000/keyring/.ssh awilliam@beast01:~> ls -l /run/user/1000/keyring/.ssh srw------- 1 awilliam users 0 Oct 17 08:39 /run/user/1000/keyring/.ssh awilliam@beast01:~> env | grep SSH SSH_AUTH_SOCK=/run/user/1000/keyring/ssh SSH_ASKPASS=/usr/lib/ssh/ssh-askpass SSH_AGENT_PID=3113 __OS Relase__ awilliam@beast01:/etc> cat os-release NAME="openSUSE Leap" VERSION="15.1 " ID="opensuse-leap" ID_LIKE="suse opensuse" VERSION_ID="15.1" PRETTY_NAME="openSUSE Leap 15.1" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:leap:15.1" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" __agent knows the keys__ awilliam@beast01:/etc> ssh-add -l 1024 SHA256:Mom8WjkrR5gYjlRXsH4ROtA7HcsvC0UI/2c+BFsEp0U ogo(a)workflow.mormail.com (DSA) 1024 SHA256:xVXJ4TscK0z/lZRf6t6n/9yt3G9sIxy46bmGd2RDCr4 awilliam(a)linux-yu4c.site (DSA) 1024 SHA256:ZNRZeqkdHCI266I72nNCOiwagJ85XLScOkmEtwYIilk awilliam(a)linux-86wr.site (DSA) __entering the passphrase 'works' but is not effective__ awilliam@beast01:/etc> ssh-add Enter passphrase for /home/awilliam/.ssh/id_dsa: Identity added: /home/awilliam/.ssh/id_dsa (/home/awilliam/.ssh/id_dsa) __gcr-ssh-askpass is installed__ awilliam@beast01:~> ls -l /usr/lib/gcr-ssh-askpass -rwxr-xr-x 1 root root 43920 Feb 24 2019 /usr/lib/gcr-ssh-askpass awilliam@beast01:~> rpm -qf /usr/lib/gcr-ssh-askpass gcr-ssh-askpass-3.28.1-lp151.1.1.x86_64 -- Adam Tauno Williams <mailto:awilliam@whitemice.org> GPG D95ED383 OpenGroupware Developer <http://www.opengroupware.us/> -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

6 10

[opensuse] SegFault 7-times today just to retrieve packages during Zypper Up (no fix yet?)
by David C. Rankin 19 Oct '19

19 Oct '19

All, This is bizarre. Today on Leap 15, I went to zypper up and it SegFaulted 7 times before it finally downloaded all packages. It would download 3-4 packages, then segfault. This was apparently already reported as a bug several weeks ago. Is a fix or workaround out? -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 2

[opensuse] Run script when a program ends
by Istvan Gabor 17 Oct '19

17 Oct '19

Hello: I have a program which saves data in a file. It writes the file when the user quits the program. I would like to automatically save a copy of the data file when/after the program quits. How can I achieve that? I could write a script that makes a copy of the file, but don't know how to start the script when the program quits. Any idea or solution is welcomed. Thanks in advance, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

7 12

[opensuse] urgent help needed: Leap 15.1, firewalld, router not forwarding IPv6
by Mathias Homann 15 Oct '19

15 Oct '19

Hi, I just upgraded my firewall/router from 15.0 to 15.1 with zypper, and now it's not forwarding IPv6 anymore. I have not changed anything about the firewall settings (internal interface is in trusted, external in external, masquerade is on in external), before the upgrade I could talk IPv6 from any internal host just fine, now i can't. I can talk IPv6 from the router itself, but not from any machines behind it. Any ideas? Cheers *Mathias Homann* Mathias.Homann@openSUSE:.org[1] irc: [Lemmy] @ freenode, ircnet obs: lemmy04 *gpg key fingerprint: 8029 2240 F4DD 7776 E7D2 C042 6B8E 029E 13F2 C102* -------- [1] mailto:Mathias.Homann@eregion.de

3 4

[opensuse] sig 7 bus error
by David T-G 14 Oct '19

14 Oct '19

Hi again, all -- This time I do have a real problem. I shut down my laptop davidtg@wench:~> uname -a ; cat /etc/os-release Linux wench 4.4.140-62-default #1 SMP Tue Jul 17 12:14:34 UTC 2018 (951943d) x86_64 x86_64 x86_64 GNU/Linux NAME="openSUSE Leap" VERSION="42.3" ID=opensuse ID_LIKE="suse" VERSION_ID="42.3" PRETTY_NAME="openSUSE Leap 42.3" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:leap:42.3" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" to bring it home, and when I brought it back up I suddenly couldn't run Chrome (Chromium); it pops up its window but then immediately dies. Here's what it throws: davidtg@wench:~> /usr/bin/chromium --disable-gpu --user-data-dir=/mnt/data/home/davidtg/.chromium/profiles/gift [5387:5387:1004/222017.561228:ERROR:gpu_process_transport_factory.cc(1016)] Lost UI shared context. libva info: VA-API version 0.39.4 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib64/dri/i965_drv_video.so libva info: va_openDriver() returns -1 [5471:5471:1004/222017.875318:ERROR:vaapi_wrapper.cc(323)] vaInitialize failed: unknown libva error Received signal 7 BUS_ADRERR 7f4faef5c1bc #0 0x556ce6714fae <unknown> #1 0x556ce41f78a0 <unknown> #2 0x556ce6715367 <unknown> #3 0x7f4fc5203c10 <unknown> #4 0x556ce6a23f9a <unknown> #5 0x556ce6a2423c <unknown> #6 0x556ce6a1eb51 <unknown> #7 0x556ce6a1ed17 <unknown> #8 0x556ce6a1f6da <unknown> #9 0x556ce69e2275 <unknown> #10 0x556ce67846ec <unknown> #11 0x556ce6784859 <unknown> #12 0x556ce6785423 <unknown> #13 0x556ce7d28569 <unknown> #14 0x556ce7d419d0 <unknown> #15 0x556ce7d41f6c <unknown> #16 0x556ce9b89991 <unknown> #17 0x556ce668e448 <unknown> #18 0x556ce66e5afd <unknown> #19 0x556ce6721ff2 <unknown> #20 0x556ce66e769e <unknown> #21 0x556ce67373a4 <unknown> #22 0x556ce6737904 <unknown> #23 0x556ce6722621 <unknown> #24 0x7f4fc51fb724 start_thread #25 0x7f4fbc645e8d __clone r8: 00007f4f9269ccc8 r9: 0000556ceb968721 r10: 0000556ce6a231f0 r11: 0000000000000014 r12: 000008e930b9c928 r13: 00007f4f9269cd80 r14: 00007f4f9269cec4 r15: 0000556ceb90ef38 di: 000008e930b9c928 si: 0000000000000002 bp: 00007f4f9269ccb0 bx: 000008e930b9c928 dx: 00007f4faef5a600 ax: 00007f4faef5c1bc cx: 0000556ceb968721 sp: 00007f4f9269cc50 ip: 0000556ce6a23f9a efl: 0000000000010202 cgf: 0000000000000033 erf: 0000000000000004 trp: 000000000000000e msk: 0000000000000000 cr2: 00007f4faef5c1bc [end of stack trace] Calling _exit(1). Core file will not be generated. Firefox gives me a much shorter error with similar disappearing-window results: davidtg@wench:~> /usr/bin/firefox -p gift ExceptionHandler::GenerateDump cloned child 6233 ExceptionHandler::SendContinueSignalToChild sent continue signal to child ExceptionHandler::WaitForContinueSignal waiting for continue signal... Bus error (core dumped) I've actually bounced the box a few times with no better luck. I know that I tried something else that failed, but I don't recall just what it was. Dolphin works, though, and shotcut will view a video file, so it isn't simply all graphics stuff. Um, what did I miss here?!? TIA & HANN :-D -- David T-G See http://justpickone.org/davidtg/email/ See http://justpickone.org/davidtg/tofu.txt -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 11

[opensuse] close lid => suspend => can't boot
by David T-G 14 Oct '19

14 Oct '19

Hi, all -- This stupid laptop really has me ticked off this morning. I took it from the desk to bed where I'm home for a sick day (yes, my patience is already thin!) and found, much to my surprise, that it suddenly goes to sleep when I close the lid. ?!? Well, fine; I just won't close the lid when I put it back later, right? But I opeend it and it failed to resume, so I had to power-cycle it ... and it still won't boot! ARRRRRGH!!! Whether I try a normal boot or recovery mode, I only get as far as [ 5.214975] radeon 0000:01:00.0: failed VCE resume (-110). after a few very brief flashes of boot scroll that I can't catch. I went googling around for how to disable the sleep thing, but if I can't get it running again then that part is moot. Any idea how I can get this unstuck? TIA again :-D -- David T-G See http://justpickone.org/davidtg/email/ See http://justpickone.org/davidtg/tofu.txt -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 1

[opensuse] Help: System hangs on graphical login in Leap-15.1
by Josef Wolf 14 Oct '19

14 Oct '19

Hello, I have installed Leap-15.1 about two months ago. (Almost) everything was working fine. Today, I booted up this system again, and can no longer login to KDE. I can type username/password, but then nothing happens. Keyboard is dead. Only mouse can be mooved. Even CTRL-ALT-F1 won't work to switch to a virtual console. As long as I do not try to login to KDE, I can switch to virtual console via CTRL-ALT-F1 and login as root and/or ordinary user. When I switch back to CTRL-ALT-F7 and try to login to KDE, keyboard is dead again and login screen won't vanish. Below is /var/log/messages of the login attempt. For me, only the lines marked with "(*)" look suspicous. Maybe somebody else can get more clues out of this? Any ideas how to track this down? 2019-10-08T13:35:10.670863+02:00 kiste nmbd[1457]: [2019/10/08 13:35:10.643933, 0] ../source3/nmbd/asyncdns.c:158(start_async_dns) 2019-10-08T13:35:10.671282+02:00 kiste nmbd[1457]: started asyncdns process 1575 2019-10-08T13:35:10.671658+02:00 kiste nmbd[1457]: [2019/10/08 13:35:10.671547, 0] ../lib/util/become_daemon.c:149(daemon_status) 2019-10-08T13:35:10.671950+02:00 kiste nmbd[1457]: daemon_status: STATUS=daemon 'nmbd' : No local IPv4 non-loopback interfaces available, waiting for interface ... 2019-10-08T13:35:10.672210+02:00 kiste nmbd[1457]: [2019/10/08 13:35:10.671621, 0] ../source3/nmbd/nmbd_subnetdb.c:254(create_subnets) 2019-10-08T13:35:10.672456+02:00 kiste nmbd[1457]: NOTE: NetBIOS name resolution is not supported for Internet Protocol Version 6 (IPv6). 2019-10-08T13:35:10.864172+02:00 kiste systemd[1]: Started Permit User Sessions. 2019-10-08T13:35:10.866111+02:00 kiste systemd[1]: Starting Hold until boot process finishes up... 2019-10-08T13:35:10.867905+02:00 kiste systemd[1]: Starting X Display Manager... 2019-10-08T13:35:11.032281+02:00 kiste kernel: [ 102.623966] Netfilter messages via NETLINK v0.30. 2019-10-08T13:35:11.075739+02:00 kiste kernel: [ 102.666024] ip_set: protocol 6 2019-10-08T13:35:11.171413+02:00 kiste systemd[1]: Started Backup /etc/sysconfig directory. 2019-10-08T13:35:11.190968+02:00 kiste display-manager[1582]: /etc/vconsole.conf available 2019-10-08T13:35:11.191376+02:00 kiste display-manager[1582]: KEYMAP: de-nodeadkeys 2019-10-08T13:35:11.191628+02:00 kiste display-manager[1582]: Command: localectl set-keymap de-nodeadkeys 2019-10-08T13:35:11.233687+02:00 kiste display-manager[1582]: I: Using systemd /usr/share/systemd/kbd-model-map mapping 2019-10-08T13:35:11.328999+02:00 kiste dbus-daemon[1150]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service' requested by ':1.10' (uid=0 pid=1613 comm="localectl set-keymap de-nodeadkeys ") 2019-10-08T13:35:11.392201+02:00 kiste systemd[1]: Starting Locale Service... 2019-10-08T13:35:11.488261+02:00 kiste dbus-daemon[1150]: [system] Successfully activated service 'org.freedesktop.locale1' 2019-10-08T13:35:11.489584+02:00 kiste systemd[1]: Started Locale Service. 2019-10-08T13:35:11.520151+02:00 kiste systemd[1]: Received SIGRTMIN+21 from PID 346 (plymouthd). 2019-10-08T13:35:11.532712+02:00 kiste systemd[1]: Received SIGRTMIN+21 from PID 346 (plymouthd). 2019-10-08T13:35:11.540350+02:00 kiste systemd[1]: Started Hold until boot process finishes up. 2019-10-08T13:35:11.540792+02:00 kiste systemd[1]: Started Getty on tty1. 2019-10-08T13:35:11.541069+02:00 kiste systemd[1]: Reached target Login Prompts. 2019-10-08T13:35:12.313170+02:00 kiste display-manager[1582]: Starting service sddm..done 2019-10-08T13:35:12.313800+02:00 kiste systemd[1]: display-manager.service: PID file /var/run/displaymanager.pid not readable (yet?) after start: No such file or directory 2019-10-08T13:35:12.401725+02:00 kiste sddm[1632]: Initializing... 2019-10-08T13:35:12.402959+02:00 kiste systemd[1]: Started X Display Manager. 2019-10-08T13:35:12.420681+02:00 kiste sddm[1632]: Starting... 2019-10-08T13:35:12.421341+02:00 kiste sddm[1632]: Logind interface found 2019-10-08T13:35:12.423233+02:00 kiste sddm[1632]: Adding new display on vt 7 ... 2019-10-08T13:35:12.438520+02:00 kiste sddm[1632]: Loading theme configuration from "" 2019-10-08T13:35:12.438898+02:00 kiste sddm[1632]: Display server starting... 2019-10-08T13:35:12.439431+02:00 kiste sddm[1632]: Running: /usr/bin/X -nolisten tcp -auth /run/sddm/{fb5032f4-34cb-4c7b-8da9-481c487f169d} -background none -noreset -displayfd 18 -seat seat0 vt7 2019-10-08T13:35:12.856612+02:00 kiste nscd: 1164 Prüfe auf überwachte Datei »/etc/resolv.conf«: Datei oder Verzeichnis nicht gefunden 2019-10-08T13:35:13.703788+02:00 kiste systemd[1]: Started Postfix Mail Transport Agent. 2019-10-08T13:35:13.704251+02:00 kiste systemd[1]: Started Command Scheduler. 2019-10-08T13:35:13.817417+02:00 kiste cron[1719]: (CRON) INFO (RANDOM_DELAY will be scaled with factor 9% if used.) 2019-10-08T13:35:13.850132+02:00 kiste cron[1719]: (CRON) INFO (running with inotify support) 2019-10-08T13:35:16.959753+02:00 kiste kernel: [ 108.548292] NET: Registered protocol family 17 2019-10-08T13:35:17.521220+02:00 kiste sddm[1632]: Setting default cursor 2019-10-08T13:35:17.650558+02:00 kiste sddm[1632]: Running display setup script "/etc/X11/xdm/Xsetup" 2019-10-08T13:35:17.848230+02:00 kiste avahi-daemon[1253]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::ca37:49b7:d23b:8919. 2019-10-08T13:35:17.848623+02:00 kiste avahi-daemon[1253]: New relevant interface eth0.IPv6 for mDNS. 2019-10-08T13:35:17.848877+02:00 kiste avahi-daemon[1253]: Registering new address record for fe80::ca37:49b7:d23b:8919 on eth0.*. 2019-10-08T13:35:18.727285+02:00 kiste sddm[1632]: Display server started. 2019-10-08T13:35:18.727706+02:00 kiste sddm[1632]: Socket server starting... 2019-10-08T13:35:18.727995+02:00 kiste sddm[1632]: Socket server started. 2019-10-08T13:35:18.803225+02:00 kiste sddm[1632]: Loading theme configuration from "/usr/share/sddm/themes/breeze-openSUSE/theme.conf" 2019-10-08T13:35:18.805662+02:00 kiste sddm[1632]: Greeter starting... 2019-10-08T13:35:18.806825+02:00 kiste sddm[1632]: Adding cookie to "/run/sddm/{fb5032f4-34cb-4c7b-8da9-481c487f169d}" 2019-10-08T13:35:19.145112+02:00 kiste sddm-helper[1893]: [PAM] Starting... 2019-10-08T13:35:19.145558+02:00 kiste sddm-helper[1893]: [PAM] Authenticating... 2019-10-08T13:35:19.145847+02:00 kiste sddm-helper[1893]: [PAM] returning. 2019-10-08T13:35:19.154847+02:00 kiste systemd[1]: Created slice User Slice of sddm. 2019-10-08T13:35:19.168396+02:00 kiste systemd[1]: Starting User Manager for UID 466... 2019-10-08T13:35:19.174255+02:00 kiste systemd-logind[1269]: New session 1 of user sddm. 2019-10-08T13:35:19.174616+02:00 kiste systemd[1]: Started Session 1 of user sddm. 2019-10-08T13:35:19.395922+02:00 kiste systemd: pam_unix(systemd-user:session): session opened for user sddm by (uid=0) 2019-10-08T13:35:19.867398+02:00 kiste systemd[1898]: Reached target Paths. 2019-10-08T13:35:19.867823+02:00 kiste systemd[1898]: Reached target Timers. 2019-10-08T13:35:19.871844+02:00 kiste systemd[1898]: Starting D-Bus User Message Bus Socket. 2019-10-08T13:35:19.882726+02:00 kiste systemd[1898]: Listening on D-Bus User Message Bus Socket. 2019-10-08T13:35:19.883092+02:00 kiste systemd[1898]: Reached target Sockets. 2019-10-08T13:35:19.883396+02:00 kiste systemd[1898]: Reached target Basic System. 2019-10-08T13:35:19.883687+02:00 kiste systemd[1]: Started User Manager for UID 466. 2019-10-08T13:35:19.885024+02:00 kiste systemd[1898]: Reached target Default. 2019-10-08T13:35:19.885402+02:00 kiste systemd[1898]: Startup finished in 465ms. 2019-10-08T13:35:19.886071+02:00 kiste sddm-helper: pam_unix(sddm-greeter:session): session opened for user sddm by (uid=0) 2019-10-08T13:35:19.923721+02:00 kiste sddm[1632]: Greeter session started successfully 2019-10-08T13:35:20.285814+02:00 kiste sddm-greeter[1907]: High-DPI autoscaling Enabled 2019-10-08T13:35:20.908362+02:00 kiste sddm-greeter[1907]: Reading from "/usr/share/xsessions/icewm.desktop" 2019-10-08T13:35:20.915208+02:00 kiste sddm-greeter[1907]: Reading from "/usr/share/xsessions/plasma5.desktop" 2019-10-08T13:35:20.915537+02:00 kiste sddm-greeter[1907]: Reading from "/usr/share/xsessions/twm.desktop" 2019-10-08T13:35:20.932063+02:00 kiste sddm-greeter[1907]: Reading from "/usr/share/wayland-sessions/plasmawayland.desktop" 2019-10-08T13:35:20.933421+02:00 kiste sddm-greeter[1907]: Loading theme configuration from "/usr/share/sddm/themes/breeze-openSUSE/theme.conf" 2019-10-08T13:35:20.936324+02:00 kiste systemd[1898]: Started D-Bus User Message Bus. 2019-10-08T13:35:21.169366+02:00 kiste sddm-greeter[1907]: Connected to the daemon. 2019-10-08T13:35:21.169847+02:00 kiste sddm[1632]: Message received from greeter: Connect 2019-10-08T13:35:21.630264+02:00 kiste sddm-greeter[1907]: Loading file:///usr/share/sddm/themes/breeze-openSUSE/Main.qml... 2019-10-08T13:35:22.000177+02:00 kiste avahi-daemon[1253]: Joining mDNS multicast group on interface eth0.IPv4 with address 10.116.41.67. 2019-10-08T13:35:22.000714+02:00 kiste avahi-daemon[1253]: New relevant interface eth0.IPv4 for mDNS. 2019-10-08T13:35:22.001214+02:00 kiste avahi-daemon[1253]: Registering new address record for 10.116.41.67 on eth0.IPv4. 2019-10-08T13:35:23.254576+02:00 kiste sddm-greeter[1907]: QObject: Cannot create children for a parent that is in a different thread.#012(Parent is QGuiApplication(0x7ffd767832b0), parent's thread is QThread(0x55d8029640f0), current thread is QThread(0x55d802a625b0) 2019-10-08T13:35:23.426199+02:00 kiste sddm-greeter[1907]: message repeated 2 times: [ QObject: Cannot create children for a parent that is in a different thread.#012(Parent is QGuiApplication(0x7ffd767832b0), parent's thread is QThread(0x55d8029640f0), current thread is QThread(0x55d802a625b0)] 2019-10-08T13:35:23.426691+02:00 kiste sddm-greeter[1907]: QObject::installEventFilter(): Cannot filter events for objects in a different thread. 2019-10-08T13:35:23.774088+02:00 kiste dbus-daemon[1150]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.7' (uid=0 pid=1416 comm="/usr/sbin/NetworkManager --no-daemon ") 2019-10-08T13:35:23.778716+02:00 kiste systemd[1]: Starting Network Manager Script Dispatcher Service... 2019-10-08T13:35:23.796683+02:00 kiste dbus-daemon[1150]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' 2019-10-08T13:35:23.798023+02:00 kiste systemd[1]: Started Network Manager Script Dispatcher Service. 2019-10-08T13:35:25.726735+02:00 kiste nmbd[1457]: [2019/10/08 13:35:25.724150, 0] ../lib/util/become_daemon.c:138(daemon_ready) 2019-10-08T13:35:25.727121+02:00 kiste systemd[1]: Started Samba NMB Daemon. 2019-10-08T13:35:25.727373+02:00 kiste nmbd[1457]: daemon_ready: STATUS=daemon 'nmbd' finished starting up and ready to serve connections 2019-10-08T13:35:25.727623+02:00 kiste systemd[1]: Starting Samba SMB Daemon... 2019-10-08T13:35:26.528968+02:00 kiste systemd[1]: Started Do daily mandb update. 2019-10-08T13:35:27.646114+02:00 kiste systemd[1]: Started Samba SMB Daemon. 2019-10-08T13:35:27.657520+02:00 kiste smbd[2073]: [2019/10/08 13:35:27.647886, 0] ../lib/util/become_daemon.c:138(daemon_ready) 2019-10-08T13:35:27.657900+02:00 kiste smbd[2073]: daemon_ready: STATUS=daemon 'smbd' finished starting up and ready to serve connections 2019-10-08T13:35:28.580437+02:00 kiste dbus-daemon[1150]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='udisks2.service' requested by ':1.18' (uid=466 pid=1907 comm="/usr/bin/sddm-greeter --socket /tmp/sddm-:0-AFAhGT") 2019-10-08T13:35:28.597525+02:00 kiste systemd[1]: Starting Disk Manager... 2019-10-08T13:35:28.663717+02:00 kiste udisksd[2080]: udisks daemon version 2.6.5 starting 2019-10-08T13:35:28.681463+02:00 kiste udisksd[2080]: Can't load configuration file /etc/udisks2/udisks2.conf 2019-10-08T13:35:28.836546+02:00 kiste dbus-daemon[1150]: [system] Successfully activated service 'org.freedesktop.UDisks2' 2019-10-08T13:35:28.839893+02:00 kiste systemd[1]: Started Disk Manager. 2019-10-08T13:35:28.840974+02:00 kiste dbus-daemon[1150]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service' requested by ':1.18' (uid=466 pid=1907 comm="/usr/bin/sddm-greeter --socket /tmp/sddm-:0-AFAhGT") 2019-10-08T13:35:28.841593+02:00 kiste udisksd[2080]: Acquired the name org.freedesktop.UDisks2 on the system message bus 2019-10-08T13:35:28.864286+02:00 kiste systemd[1]: Starting Daemon for power management... 2019-10-08T13:35:29.349177+02:00 kiste dbus-daemon[1150]: [system] Successfully activated service 'org.freedesktop.UPower' 2019-10-08T13:35:29.350963+02:00 kiste systemd[1]: Started Daemon for power management. 2019-10-08T13:35:32.886654+02:00 kiste sddm-greeter[1907]: Adding view for "DVI-I-1" QRect(0,0 1920x1200) 2019-10-08T13:35:34.114542+02:00 kiste sddm-greeter[1907]: QDBusConnection: name 'org.freedesktop.UDisks2' had owner '' but we thought it was ':1.19' 2019-10-08T13:35:34.177210+02:00 kiste sddm-greeter[1907]: Message received from daemon: Capabilities 2019-10-08T13:35:34.177664+02:00 kiste sddm-greeter[1907]: Message received from daemon: HostName 2019-10-08T13:35:37.213857+02:00 kiste [RPM][2122]: Transaction ID 5d9c7489 started 2019-10-08T13:35:47.009586+02:00 kiste [RPM][2122]: erase kernel-default-4.12.14-lp151.28.7.1.x86_64: success 2019-10-08T13:35:48.592374+02:00 kiste login: pam_unix(login:auth): authentication failure; logname=LOGIN uid=0 euid=0 tty=tty1 ruser= rhost= user=root 2019-10-08T13:35:50.135875+02:00 kiste login: FAILED LOGIN 1 FROM tty1 FOR root, Authentication failure 2019-10-08T13:35:50.895103+02:00 kiste nmbd[1457]: [2019/10/08 13:35:50.894192, 0] ../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2) 2019-10-08T13:35:50.895482+02:00 kiste nmbd[1457]: ***** 2019-10-08T13:35:50.895740+02:00 kiste nmbd[1457]: 2019-10-08T13:35:50.895990+02:00 kiste nmbd[1457]: Samba name server KISTE is now a local master browser for workgroup TUX-NET on subnet 10.116.41.67 2019-10-08T13:35:50.896226+02:00 kiste nmbd[1457]: 2019-10-08T13:35:50.896458+02:00 kiste nmbd[1457]: ***** 2019-10-08T13:35:54.413249+02:00 kiste dbus-daemon[1150]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.7' (uid=0 pid=1416 comm="/usr/sbin/NetworkManager --no-daemon ") 2019-10-08T13:35:54.423850+02:00 kiste systemd[1]: Starting Network Manager Script Dispatcher Service... 2019-10-08T13:35:54.434078+02:00 kiste dbus-daemon[1150]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' 2019-10-08T13:35:54.489920+02:00 kiste systemd[1]: Started Network Manager Script Dispatcher Service. 2019-10-08T13:35:56.735740+02:00 kiste kernel: [ 148.326393] fuse init (API version 7.26) 2019-10-08T13:35:56.740078+02:00 kiste systemd[1]: Mounting FUSE Control File System... 2019-10-08T13:35:56.749373+02:00 kiste systemd[1]: Mounted FUSE Control File System. 2019-10-08T13:35:58.577553+02:00 kiste login: FAILED LOGIN 2 FROM tty1 FOR root, Authentication failure 2019-10-08T13:35:59.195743+02:00 kiste kernel: [ 150.785099] sr 1:0:0:0: [sr0] tag#19 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE 2019-10-08T13:35:59.195758+02:00 kiste kernel: [ 150.785104] sr 1:0:0:0: [sr0] tag#19 Sense Key : Illegal Request [current] 2019-10-08T13:35:59.195761+02:00 kiste kernel: [ 150.785108] sr 1:0:0:0: [sr0] tag#19 Add. Sense: Illegal mode for this track 2019-10-08T13:35:59.195763+02:00 kiste kernel: [ 150.785112] sr 1:0:0:0: [sr0] tag#19 CDB: Read(10) 28 00 00 03 98 00 00 00 02 00 2019-10-08T13:35:59.195767+02:00 kiste kernel: [ 150.785115] print_req_error: I/O error, dev sr0, sector 942080 2019-10-08T13:35:59.315741+02:00 kiste kernel: [ 150.905889] sr 1:0:0:0: [sr0] tag#20 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE 2019-10-08T13:35:59.315755+02:00 kiste kernel: [ 150.905892] sr 1:0:0:0: [sr0] tag#20 Sense Key : Illegal Request [current] 2019-10-08T13:35:59.315757+02:00 kiste kernel: [ 150.905897] sr 1:0:0:0: [sr0] tag#20 Add. Sense: Illegal mode for this track 2019-10-08T13:35:59.315759+02:00 kiste kernel: [ 150.905900] sr 1:0:0:0: [sr0] tag#20 CDB: Read(10) 28 00 00 03 98 00 00 00 02 00 2019-10-08T13:35:59.315761+02:00 kiste kernel: [ 150.905902] print_req_error: I/O error, dev sr0, sector 942080 2019-10-08T13:35:59.315762+02:00 kiste kernel: [ 150.905905] Buffer I/O error on dev sr0, logical block 117760, async page read 2019-10-08T13:36:00.794947+02:00 kiste os-prober: debug: running /usr/lib/os-probes/50mounted-tests on /dev/sda10 2019-10-08T13:36:00.828743+02:00 kiste 50mounted-tests: debug: /dev/sda10 is a LUKS partition; skipping 2019-10-08T13:36:00.832050+02:00 kiste os-prober: debug: os detected by /usr/lib/os-probes/50mounted-tests 2019-10-08T13:36:00.862411+02:00 kiste os-prober: debug: running /usr/lib/os-probes/mounted/05efi on mounted /dev/sda2 2019-10-08T13:36:00.874315+02:00 kiste 05efi: debug: Not on UEFI platform 2019-10-08T13:36:00.877794+02:00 kiste os-prober: debug: running /usr/lib/os-probes/mounted/10freedos on mounted /dev/sda2 2019-10-08T13:36:00.885314+02:00 kiste 10freedos: debug: /dev/sda2 is not a FAT partition: exiting 2019-10-08T13:36:00.888860+02:00 kiste os-prober: debug: running /usr/lib/os-probes/mounted/10qnx on mounted /dev/sda2 2019-10-08T13:36:00.896476+02:00 kiste 10qnx: debug: /dev/sda2 is not a QNX4 partition: exiting 2019-10-08T13:36:00.900088+02:00 kiste os-prober: debug: running /usr/lib/os-probes/mounted/20macosx on mounted /dev/sda2 2019-10-08T13:36:00.907742+02:00 kiste macosx-prober: debug: /dev/sda2 is not an HFS+ partition: exiting 2019-10-08T13:36:00.911250+02:00 kiste os-prober: debug: running /usr/lib/os-probes/mounted/20microsoft on mounted /dev/sda2 2019-10-08T13:36:00.919087+02:00 kiste 20microsoft: debug: /dev/sda2 is not a MS partition: exiting 2019-10-08T13:36:00.922621+02:00 kiste os-prober: debug: running /usr/lib/os-probes/mounted/30utility on mounted /dev/sda2 2019-10-08T13:36:00.930231+02:00 kiste 30utility: debug: /dev/sda2 is not a FAT partition: exiting 2019-10-08T13:36:00.933766+02:00 kiste os-prober: debug: running /usr/lib/os-probes/mounted/40lsb on mounted /dev/sda2 2019-10-08T13:36:00.941994+02:00 kiste os-prober: debug: running /usr/lib/os-probes/mounted/70hurd on mounted /dev/sda2 2019-10-08T13:36:00.950128+02:00 kiste os-prober: debug: running /usr/lib/os-probes/mounted/80minix on mounted /dev/sda2 2019-10-08T13:36:00.964139+02:00 kiste os-prober: debug: running /usr/lib/os-probes/mounted/83haiku on mounted /dev/sda2 2019-10-08T13:36:00.973654+02:00 kiste 83haiku: debug: /dev/sda2 is not a BeFS partition: exiting 2019-10-08T13:36:00.976990+02:00 kiste os-prober: debug: running /usr/lib/os-probes/mounted/90linux-distro on mounted /dev/sda2 2019-10-08T13:36:00.987795+02:00 kiste os-prober: debug: running /usr/lib/os-probes/mounted/90solaris on mounted /dev/sda2 2019-10-08T13:36:01.083123+02:00 kiste os-prober: debug: running /usr/lib/os-probes/50mounted-tests on /dev/sda3 2019-10-08T13:36:01.754612+02:00 kiste 50mounted-tests: debug: mounted using GRUB ext2 filesystem driver 2019-10-08T13:36:01.758179+02:00 kiste 50mounted-tests: debug: running subtest /usr/lib/os-probes/mounted/05efi 2019-10-08T13:36:01.765753+02:00 kiste 05efi: debug: Not on UEFI platform 2019-10-08T13:36:01.769111+02:00 kiste 50mounted-tests: debug: running subtest /usr/lib/os-probes/mounted/10freedos 2019-10-08T13:36:01.776428+02:00 kiste 10freedos: debug: /dev/sda3 is not a FAT partition: exiting 2019-10-08T13:36:01.779633+02:00 kiste 50mounted-tests: debug: running subtest /usr/lib/os-probes/mounted/10qnx 2019-10-08T13:36:01.786960+02:00 kiste 10qnx: debug: /dev/sda3 is not a QNX4 partition: exiting 2019-10-08T13:36:01.790249+02:00 kiste 50mounted-tests: debug: running subtest /usr/lib/os-probes/mounted/20macosx 2019-10-08T13:36:01.797636+02:00 kiste macosx-prober: debug: /dev/sda3 is not an HFS+ partition: exiting 2019-10-08T13:36:01.801057+02:00 kiste 50mounted-tests: debug: running subtest /usr/lib/os-probes/mounted/20microsoft 2019-10-08T13:36:01.808467+02:00 kiste 20microsoft: debug: /dev/sda3 is not a MS partition: exiting 2019-10-08T13:36:01.811658+02:00 kiste 50mounted-tests: debug: running subtest /usr/lib/os-probes/mounted/30utility 2019-10-08T13:36:01.819012+02:00 kiste 30utility: debug: /dev/sda3 is not a FAT partition: exiting 2019-10-08T13:36:01.822242+02:00 kiste 50mounted-tests: debug: running subtest /usr/lib/os-probes/mounted/40lsb 2019-10-08T13:36:01.845454+02:00 kiste 50mounted-tests: debug: running subtest /usr/lib/os-probes/mounted/70hurd 2019-10-08T13:36:01.853185+02:00 kiste 50mounted-tests: debug: running subtest /usr/lib/os-probes/mounted/80minix 2019-10-08T13:36:01.861111+02:00 kiste 50mounted-tests: debug: running subtest /usr/lib/os-probes/mounted/83haiku 2019-10-08T13:36:01.868334+02:00 kiste 83haiku: debug: /dev/sda3 is not a BeFS partition: exiting 2019-10-08T13:36:01.871550+02:00 kiste 50mounted-tests: debug: running subtest /usr/lib/os-probes/mounted/90linux-distro 2019-10-08T13:36:01.885187+02:00 kiste 50mounted-tests: debug: running subtest /usr/lib/os-probes/mounted/90solaris 2019-10-08T13:36:01.893434+02:00 kiste 50mounted-tests: debug: running subtest /usr/lib/os-probes/mounted/efi 2019-10-08T13:36:01.905467+02:00 kiste nmbd[1457]: [2019/10/08 13:36:01.905325, 0] ../source3/nmbd/nmbd_browsesync.c:354(find_domain_master_name_query_fail) 2019-10-08T13:36:01.905837+02:00 kiste nmbd[1457]: find_domain_master_name_query_fail: 2019-10-08T13:36:01.906082+02:00 kiste nmbd[1457]: Unable to find the Domain Master Browser name TUX-NET<1b> for the workgroup TUX-NET. 2019-10-08T13:36:01.906353+02:00 kiste nmbd[1457]: Unable to sync browse lists in this workgroup. 2019-10-08T13:36:02.000008+02:00 kiste os-prober: debug: running /usr/lib/os-probes/50mounted-tests on /dev/sda4 2019-10-08T13:36:02.017944+02:00 kiste 50mounted-tests: debug: /dev/sda4 type not recognised; skipping 2019-10-08T13:36:02.021411+02:00 kiste os-prober: debug: os detected by /usr/lib/os-probes/50mounted-tests 2019-10-08T13:36:02.103099+02:00 kiste os-prober: debug: running /usr/lib/os-probes/50mounted-tests on /dev/sda5 2019-10-08T13:36:02.603493+02:00 kiste 50mounted-tests: debug: mounted using GRUB ext2 filesystem driver 2019-10-08T13:36:02.607095+02:00 kiste 50mounted-tests: debug: running subtest /usr/lib/os-probes/mounted/05efi 2019-10-08T13:36:02.614739+02:00 kiste 05efi: debug: Not on UEFI platform 2019-10-08T13:36:02.617985+02:00 kiste 50mounted-tests: debug: running subtest /usr/lib/os-probes/mounted/10freedos 2019-10-08T13:36:02.625590+02:00 kiste 10freedos: debug: /dev/sda5 is not a FAT partition: exiting 2019-10-08T13:36:02.628939+02:00 kiste 50mounted-tests: debug: running subtest /usr/lib/os-probes/mounted/10qnx 2019-10-08T13:36:02.636345+02:00 kiste 10qnx: debug: /dev/sda5 is not a QNX4 partition: exiting 2019-10-08T13:36:02.639774+02:00 kiste 50mounted-tests: debug: running subtest /usr/lib/os-probes/mounted/20macosx 2019-10-08T13:36:02.647040+02:00 kiste macosx-prober: debug: /dev/sda5 is not an HFS+ partition: exiting 2019-10-08T13:36:02.650281+02:00 kiste 50mounted-tests: debug: running subtest /usr/lib/os-probes/mounted/20microsoft 2019-10-08T13:36:02.657843+02:00 kiste 20microsoft: debug: /dev/sda5 is not a MS partition: exiting 2019-10-08T13:36:02.661156+02:00 kiste 50mounted-tests: debug: running subtest /usr/lib/os-probes/mounted/30utility 2019-10-08T13:36:02.668556+02:00 kiste 30utility: debug: /dev/sda5 is not a FAT partition: exiting 2019-10-08T13:36:02.671983+02:00 kiste 50mounted-tests: debug: running subtest /usr/lib/os-probes/mounted/40lsb 2019-10-08T13:36:02.809204+02:00 kiste 50mounted-tests: debug: running subtest /usr/lib/os-probes/mounted/70hurd 2019-10-08T13:36:02.882565+02:00 kiste 50mounted-tests: debug: running subtest /usr/lib/os-probes/mounted/80minix 2019-10-08T13:36:02.904418+02:00 kiste 50mounted-tests: debug: running subtest /usr/lib/os-probes/mounted/83haiku 2019-10-08T13:36:02.911632+02:00 kiste 83haiku: debug: /dev/sda5 is not a BeFS partition: exiting 2019-10-08T13:36:02.914886+02:00 kiste 50mounted-tests: debug: running subtest /usr/lib/os-probes/mounted/90linux-distro 2019-10-08T13:36:02.988729+02:00 kiste 90linux-distro: result: /dev/sda5:openSUSE Leap 15.1:openSUSE:linux 2019-10-08T13:36:02.992066+02:00 kiste 50mounted-tests: debug: os found by subtest /usr/lib/os-probes/mounted/90linux-distro 2019-10-08T13:36:03.003944+02:00 kiste os-prober: debug: os detected by /usr/lib/os-probes/50mounted-tests 2019-10-08T13:36:03.091374+02:00 kiste os-prober: debug: running /usr/lib/os-probes/50mounted-tests on /dev/sda6 2019-10-08T13:36:03.106500+02:00 kiste 50mounted-tests: debug: /dev/sda6 is a LUKS partition; skipping 2019-10-08T13:36:03.110016+02:00 kiste os-prober: debug: os detected by /usr/lib/os-probes/50mounted-tests 2019-10-08T13:36:03.187464+02:00 kiste os-prober: debug: running /usr/lib/os-probes/50mounted-tests on /dev/sda7 2019-10-08T13:36:03.207625+02:00 kiste 50mounted-tests: debug: /dev/sda7 type not recognised; skipping 2019-10-08T13:36:03.210944+02:00 kiste os-prober: debug: os detected by /usr/lib/os-probes/50mounted-tests 2019-10-08T13:36:03.232898+02:00 kiste os-prober: debug: running /usr/lib/os-probes/50mounted-tests on /dev/sda8 2019-10-08T13:36:03.246690+02:00 kiste 50mounted-tests: debug: /dev/sda8 is a LUKS partition; skipping 2019-10-08T13:36:03.250001+02:00 kiste os-prober: debug: os detected by /usr/lib/os-probes/50mounted-tests 2019-10-08T13:36:03.275939+02:00 kiste os-prober: debug: running /usr/lib/os-probes/50mounted-tests on /dev/sda9 2019-10-08T13:36:03.299443+02:00 kiste 50mounted-tests: debug: /dev/sda9 is a LUKS partition; skipping 2019-10-08T13:36:03.302920+02:00 kiste os-prober: debug: os detected by /usr/lib/os-probes/50mounted-tests 2019-10-08T13:36:03.689347+02:00 kiste linux-boot-prober: debug: running /usr/lib/linux-boot-probes/50mounted-tests 2019-10-08T13:36:04.943742+02:00 kiste kernel: [ 156.532331] sr 1:0:0:0: [sr0] tag#28 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE 2019-10-08T13:36:04.943773+02:00 kiste kernel: [ 156.532334] sr 1:0:0:0: [sr0] tag#28 Sense Key : Illegal Request [current] 2019-10-08T13:36:04.943775+02:00 kiste kernel: [ 156.532338] sr 1:0:0:0: [sr0] tag#28 Add. Sense: Illegal mode for this track 2019-10-08T13:36:04.943777+02:00 kiste kernel: [ 156.532342] sr 1:0:0:0: [sr0] tag#28 CDB: Read(10) 28 00 00 03 98 00 00 00 02 00 2019-10-08T13:36:04.943779+02:00 kiste kernel: [ 156.532344] print_req_error: I/O error, dev sr0, sector 942080 2019-10-08T13:36:05.075741+02:00 kiste kernel: [ 156.665417] sr 1:0:0:0: [sr0] tag#29 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE 2019-10-08T13:36:05.075753+02:00 kiste kernel: [ 156.665420] sr 1:0:0:0: [sr0] tag#29 Sense Key : Illegal Request [current] 2019-10-08T13:36:05.075756+02:00 kiste kernel: [ 156.665424] sr 1:0:0:0: [sr0] tag#29 Add. Sense: Illegal mode for this track 2019-10-08T13:36:05.075759+02:00 kiste kernel: [ 156.665428] sr 1:0:0:0: [sr0] tag#29 CDB: Read(10) 28 00 00 03 98 00 00 00 02 00 2019-10-08T13:36:05.075761+02:00 kiste kernel: [ 156.665430] print_req_error: I/O error, dev sr0, sector 942080 2019-10-08T13:36:05.075763+02:00 kiste kernel: [ 156.665432] Buffer I/O error on dev sr0, logical block 117760, async page read 2019-10-08T13:36:05.966121+02:00 kiste systemd[1]: Created slice User Slice of root. 2019-10-08T13:36:05.991129+02:00 kiste systemd[1]: Starting User Manager for UID 0... 2019-10-08T13:36:06.000842+02:00 kiste systemd-logind[1269]: New session 2 of user root. 2019-10-08T13:36:06.002291+02:00 kiste systemd[1]: Started Session 2 of user root. 2019-10-08T13:36:06.004650+02:00 kiste systemd: pam_unix(systemd-user:session): session opened for user root by (uid=0) 2019-10-08T13:36:06.125166+02:00 kiste systemd[3228]: Starting D-Bus User Message Bus Socket. 2019-10-08T13:36:06.125554+02:00 kiste systemd[3228]: Reached target Paths. 2019-10-08T13:36:06.125838+02:00 kiste systemd[3228]: Reached target Timers. 2019-10-08T13:36:06.139400+02:00 kiste systemd[3228]: Listening on D-Bus User Message Bus Socket. 2019-10-08T13:36:06.139830+02:00 kiste systemd[3228]: Reached target Sockets. 2019-10-08T13:36:06.140138+02:00 kiste systemd[3228]: Reached target Basic System. 2019-10-08T13:36:06.140422+02:00 kiste systemd[1]: Started User Manager for UID 0. 2019-10-08T13:36:06.142301+02:00 kiste login: pam_unix(login:session): session opened for user root by LOGIN(uid=0) 2019-10-08T13:36:06.142686+02:00 kiste systemd[3228]: Reached target Default. 2019-10-08T13:36:06.143011+02:00 kiste systemd[3228]: Startup finished in 128ms. 2019-10-08T13:36:06.218702+02:00 kiste 50mounted-tests: debug: mapped UUID=2c080be0-510c-4ca8-a7b4-f7e249922090 to /dev/sda2 2019-10-08T13:36:06.603991+02:00 kiste 50mounted-tests: debug: running /usr/lib/linux-boot-probes/mounted/40grub /dev/sda5 /dev/sda2 /tmp/linux-boot-probes-50mounted-tests.DpPRYX ext2 2019-10-08T13:36:06.650483+02:00 kiste 50mounted-tests: debug: running /usr/lib/linux-boot-probes/mounted/40grub2 /dev/sda5 /dev/sda2 /tmp/linux-boot-probes-50mounted-tests.DpPRYX ext2 2019-10-08T13:36:06.701104+02:00 kiste 40grub2: debug: parsing grub.cfg 2019-10-08T13:36:06.713026+02:00 kiste 40grub2: debug: parsing: # 2019-10-08T13:36:06.716008+02:00 kiste 40grub2: debug: parsing: # DO NOT EDIT THIS FILE 2019-10-08T13:36:06.718919+02:00 kiste 40grub2: debug: parsing: # 2019-10-08T13:36:06.721998+02:00 kiste 40grub2: debug: parsing: # It is automatically generated by grub2-mkconfig using templates 2019-10-08T13:36:06.724984+02:00 kiste 40grub2: debug: parsing: # from /etc/grub.d and settings from /etc/default/grub 2019-10-08T13:36:06.727908+02:00 kiste 40grub2: debug: parsing: # 2019-10-08T13:36:06.730773+02:00 kiste 40grub2: debug: parsing: 2019-10-08T13:36:06.733796+02:00 kiste 40grub2: debug: parsing: ### BEGIN /etc/grub.d/00_header ### 2019-10-08T13:36:06.736762+02:00 kiste 40grub2: debug: parsing: if [ -f ${config_directory}/grubenv ]; then 2019-10-08T13:36:06.739685+02:00 kiste 40grub2: debug: parsing: load_env -f ${config_directory}/grubenv 2019-10-08T13:36:06.742706+02:00 kiste 40grub2: debug: parsing: elif [ -s $prefix/grubenv ]; then 2019-10-08T13:36:06.743160+02:00 kiste login: ROOT LOGIN ON tty1 2019-10-08T13:36:06.746450+02:00 kiste 40grub2: debug: parsing: load_env 2019-10-08T13:36:06.749432+02:00 kiste 40grub2: debug: parsing: fi 2019-10-08T13:36:06.752351+02:00 kiste 40grub2: debug: parsing: 2019-10-08T13:36:06.755559+02:00 kiste 40grub2: debug: parsing: if [ "${env_block}" ] ; then 2019-10-08T13:36:06.759403+02:00 kiste 40grub2: debug: parsing: set env_block="(${root})${env_block}" 2019-10-08T13:36:06.762968+02:00 kiste 40grub2: debug: parsing: export env_block 2019-10-08T13:36:06.765941+02:00 kiste 40grub2: debug: parsing: load_env -f "${env_block}" 2019-10-08T13:36:06.768859+02:00 kiste 40grub2: debug: parsing: fi 2019-10-08T13:36:06.771824+02:00 kiste 40grub2: debug: parsing: 2019-10-08T13:36:06.774714+02:00 kiste 40grub2: debug: parsing: if [ "${next_entry}" ] ; then 2019-10-08T13:36:06.777636+02:00 kiste 40grub2: debug: parsing: set default="${next_entry}" 2019-10-08T13:36:06.780632+02:00 kiste 40grub2: debug: parsing: set next_entry= 2019-10-08T13:36:06.783570+02:00 kiste 40grub2: debug: parsing: save_env next_entry 2019-10-08T13:36:06.786543+02:00 kiste 40grub2: debug: parsing: if [ "${env_block}" ] ; then 2019-10-08T13:36:06.789614+02:00 kiste 40grub2: debug: parsing: save_env -f "${env_block}" next_entry 2019-10-08T13:36:06.792564+02:00 kiste 40grub2: debug: parsing: fi 2019-10-08T13:36:06.795420+02:00 kiste 40grub2: debug: parsing: set boot_once=true 2019-10-08T13:36:06.798371+02:00 kiste 40grub2: debug: parsing: else 2019-10-08T13:36:06.801295+02:00 kiste 40grub2: debug: parsing: set default="${saved_entry}" 2019-10-08T13:36:06.804303+02:00 kiste 40grub2: debug: parsing: fi 2019-10-08T13:36:06.807189+02:00 kiste 40grub2: debug: parsing: 2019-10-08T13:36:06.810122+02:00 kiste 40grub2: debug: parsing: if [ x"${feature_menuentry_id}" = xy ]; then 2019-10-08T13:36:06.813100+02:00 kiste 40grub2: debug: parsing: menuentry_id_option="--id" 2019-10-08T13:36:06.816118+02:00 kiste 40grub2: debug: parsing: else 2019-10-08T13:36:06.819010+02:00 kiste 40grub2: debug: parsing: menuentry_id_option="" 2019-10-08T13:36:06.821929+02:00 kiste 40grub2: debug: parsing: fi 2019-10-08T13:36:06.824900+02:00 kiste 40grub2: debug: parsing: 2019-10-08T13:36:06.827842+02:00 kiste 40grub2: debug: parsing: export menuentry_id_option 2019-10-08T13:36:06.830761+02:00 kiste 40grub2: debug: parsing: 2019-10-08T13:36:06.833683+02:00 kiste 40grub2: debug: parsing: if [ "${prev_saved_entry}" ]; then 2019-10-08T13:36:06.836620+02:00 kiste 40grub2: debug: parsing: set saved_entry="${prev_saved_entry}" 2019-10-08T13:36:06.839526+02:00 kiste 40grub2: debug: parsing: save_env saved_entry 2019-10-08T13:36:06.842472+02:00 kiste 40grub2: debug: parsing: set prev_saved_entry= 2019-10-08T13:36:06.845425+02:00 kiste 40grub2: debug: parsing: save_env prev_saved_entry 2019-10-08T13:36:06.848402+02:00 kiste 40grub2: debug: parsing: set boot_once=true 2019-10-08T13:36:06.851313+02:00 kiste 40grub2: debug: parsing: fi 2019-10-08T13:36:06.854302+02:00 kiste 40grub2: debug: parsing: 2019-10-08T13:36:06.857191+02:00 kiste 40grub2: debug: parsing: function savedefault { 2019-10-08T13:36:06.860125+02:00 kiste 40grub2: debug: parsing: if [ -z "${boot_once}" ]; then 2019-10-08T13:36:06.863027+02:00 kiste 40grub2: debug: parsing: saved_entry="${chosen}" 2019-10-08T13:36:06.865974+02:00 kiste 40grub2: debug: parsing: if [ "${env_block}" ] ; then 2019-10-08T13:36:06.868895+02:00 kiste 40grub2: debug: parsing: save_env -f "${env_block}" saved_entry 2019-10-08T13:36:06.871879+02:00 kiste 40grub2: debug: parsing: else 2019-10-08T13:36:06.874791+02:00 kiste 40grub2: debug: parsing: save_env saved_entry 2019-10-08T13:36:06.877751+02:00 kiste 40grub2: debug: parsing: fi 2019-10-08T13:36:06.880680+02:00 kiste 40grub2: debug: parsing: 2019-10-08T13:36:06.883559+02:00 kiste 40grub2: debug: parsing: fi 2019-10-08T13:36:06.886476+02:00 kiste 40grub2: debug: parsing: } 2019-10-08T13:36:06.889509+02:00 kiste 40grub2: debug: parsing: 2019-10-08T13:36:06.892491+02:00 kiste 40grub2: debug: parsing: function load_video { 2019-10-08T13:36:06.895405+02:00 kiste 40grub2: debug: parsing: if [ x$feature_all_video_module = xy ]; then 2019-10-08T13:36:06.898352+02:00 kiste 40grub2: debug: parsing: insmod all_video 2019-10-08T13:36:06.901273+02:00 kiste 40grub2: debug: parsing: else 2019-10-08T13:36:06.904210+02:00 kiste 40grub2: debug: parsing: insmod efi_gop 2019-10-08T13:36:06.907116+02:00 kiste 40grub2: debug: parsing: insmod efi_uga 2019-10-08T13:36:06.910091+02:00 kiste 40grub2: debug: parsing: insmod ieee1275_fb 2019-10-08T13:36:06.913091+02:00 kiste 40grub2: debug: parsing: insmod vbe 2019-10-08T13:36:06.916112+02:00 kiste 40grub2: debug: parsing: insmod vga 2019-10-08T13:36:06.919008+02:00 kiste 40grub2: debug: parsing: insmod video_bochs 2019-10-08T13:36:06.922016+02:00 kiste 40grub2: debug: parsing: insmod video_cirrus 2019-10-08T13:36:06.924932+02:00 kiste 40grub2: debug: parsing: fi 2019-10-08T13:36:06.927866+02:00 kiste 40grub2: debug: parsing: } 2019-10-08T13:36:06.930830+02:00 kiste 40grub2: debug: parsing: 2019-10-08T13:36:06.933804+02:00 kiste 40grub2: debug: parsing: if loadfont unicode ; then 2019-10-08T13:36:06.936749+02:00 kiste 40grub2: debug: parsing: set gfxmode=auto 2019-10-08T13:36:06.939763+02:00 kiste 40grub2: debug: parsing: load_video 2019-10-08T13:36:06.942714+02:00 kiste 40grub2: debug: parsing: insmod gfxterm 2019-10-08T13:36:06.945718+02:00 kiste 40grub2: debug: parsing: fi 2019-10-08T13:36:06.948692+02:00 kiste 40grub2: debug: parsing: terminal_output gfxterm 2019-10-08T13:36:06.951570+02:00 kiste 40grub2: debug: parsing: insmod part_msdos 2019-10-08T13:36:06.954567+02:00 kiste 40grub2: debug: parsing: insmod ext2 2019-10-08T13:36:06.957565+02:00 kiste 40grub2: debug: parsing: set root='hd0,msdos2' 2019-10-08T13:36:06.960556+02:00 kiste 40grub2: debug: parsing: if [ x$feature_platform_search_hint = xy ]; then 2019-10-08T13:36:06.963501+02:00 kiste 40grub2: debug: parsing: search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2 --hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2 --hint='hd0,msdos2' 2c080be0-510c-4ca8-a7b4-f7e249922090 2019-10-08T13:36:06.966480+02:00 kiste 40grub2: debug: parsing: else 2019-10-08T13:36:06.969433+02:00 kiste 40grub2: debug: parsing: search --no-floppy --fs-uuid --set=root 2c080be0-510c-4ca8-a7b4-f7e249922090 2019-10-08T13:36:06.972386+02:00 kiste 40grub2: debug: parsing: fi 2019-10-08T13:36:06.975271+02:00 kiste 40grub2: debug: parsing: insmod gfxmenu 2019-10-08T13:36:06.978280+02:00 kiste 40grub2: debug: parsing: loadfont ($root)/grub2/themes/openSUSE/DejaVuSans-Bold14.pf2 2019-10-08T13:36:06.981251+02:00 kiste 40grub2: debug: parsing: loadfont ($root)/grub2/themes/openSUSE/DejaVuSans10.pf2 2019-10-08T13:36:06.984191+02:00 kiste 40grub2: debug: parsing: loadfont ($root)/grub2/themes/openSUSE/DejaVuSans12.pf2 2019-10-08T13:36:06.987092+02:00 kiste 40grub2: debug: parsing: loadfont ($root)/grub2/themes/openSUSE/ascii.pf2 2019-10-08T13:36:06.990043+02:00 kiste 40grub2: debug: parsing: insmod png 2019-10-08T13:36:06.993157+02:00 kiste 40grub2: debug: parsing: set theme=($root)/grub2/themes/openSUSE/theme.txt 2019-10-08T13:36:06.996204+02:00 kiste 40grub2: debug: parsing: export theme 2019-10-08T13:36:06.999102+02:00 kiste 40grub2: debug: parsing: if [ x${boot_once} = xtrue ]; then 2019-10-08T13:36:07.002036+02:00 kiste 40grub2: debug: parsing: set timeout=0 2019-10-08T13:36:07.005033+02:00 kiste 40grub2: debug: parsing: elif [ x$feature_timeout_style = xy ] ; then 2019-10-08T13:36:07.007962+02:00 kiste 40grub2: debug: parsing: set timeout_style=menu 2019-10-08T13:36:07.010834+02:00 kiste 40grub2: debug: parsing: set timeout=2 2019-10-08T13:36:07.013819+02:00 kiste 40grub2: debug: parsing: # Fallback normal timeout code in case the timeout_style feature is 2019-10-08T13:36:07.016789+02:00 kiste 40grub2: debug: parsing: # unavailable. 2019-10-08T13:36:07.019682+02:00 kiste 40grub2: debug: parsing: else 2019-10-08T13:36:07.022603+02:00 kiste 40grub2: debug: parsing: set timeout=2 2019-10-08T13:36:07.025533+02:00 kiste 40grub2: debug: parsing: fi 2019-10-08T13:36:07.028486+02:00 kiste 40grub2: debug: parsing: ### END /etc/grub.d/00_header ### 2019-10-08T13:36:07.031388+02:00 kiste 40grub2: debug: parsing: 2019-10-08T13:36:07.034298+02:00 kiste 40grub2: debug: parsing: ### BEGIN /etc/grub.d/00_tuned ### 2019-10-08T13:36:07.037344+02:00 kiste 40grub2: debug: parsing: set tuned_params="" 2019-10-08T13:36:07.040324+02:00 kiste 40grub2: debug: parsing: set tuned_initrd="" 2019-10-08T13:36:07.043250+02:00 kiste 40grub2: debug: parsing: ### END /etc/grub.d/00_tuned ### 2019-10-08T13:36:07.046219+02:00 kiste 40grub2: debug: parsing: 2019-10-08T13:36:07.049142+02:00 kiste 40grub2: debug: parsing: ### BEGIN /etc/grub.d/10_linux ### 2019-10-08T13:36:07.052118+02:00 kiste 40grub2: debug: parsing: menuentry 'openSUSE Leap 15.1 ' --class opensuse --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-12c94c4b-cbe9-46f9-9bc4-4b984a202901' { 2019-10-08T13:36:07.069349+02:00 kiste 40grub2: debug: parsing: load_video 2019-10-08T13:36:07.072541+02:00 kiste 40grub2: debug: parsing: set gfxpayload=keep 2019-10-08T13:36:07.075680+02:00 kiste 40grub2: debug: parsing: insmod gzio 2019-10-08T13:36:07.078814+02:00 kiste 40grub2: debug: parsing: insmod part_msdos 2019-10-08T13:36:07.081935+02:00 kiste 40grub2: debug: parsing: insmod ext2 2019-10-08T13:36:07.085104+02:00 kiste 40grub2: debug: parsing: set root='hd0,msdos2' 2019-10-08T13:36:07.088306+02:00 kiste 40grub2: debug: parsing: if [ x$feature_platform_search_hint = xy ]; then 2019-10-08T13:36:07.091439+02:00 kiste 40grub2: debug: parsing: search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2 --hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2 --hint='hd0,msdos2' 2c080be0-510c-4ca8-a7b4-f7e249922090 2019-10-08T13:36:07.094681+02:00 kiste 40grub2: debug: parsing: else 2019-10-08T13:36:07.097830+02:00 kiste 40grub2: debug: parsing: search --no-floppy --fs-uuid --set=root 2c080be0-510c-4ca8-a7b4-f7e249922090 2019-10-08T13:36:07.100961+02:00 kiste 40grub2: debug: parsing: fi 2019-10-08T13:36:07.104133+02:00 kiste 40grub2: debug: parsing: echo#011'Loading Linux 4.12.14-lp151.28.16-default ...' 2019-10-08T13:36:07.107297+02:00 kiste 40grub2: debug: parsing: linux#011/vmlinuz-4.12.14-lp151.28.16-default root=UUID=12c94c4b-cbe9-46f9-9bc4-4b984a202901 net.ifnames=0 2019-10-08T13:36:07.113550+02:00 kiste 40grub2: debug: parsing: echo#011'Loading initial ramdisk ...' 2019-10-08T13:36:07.116517+02:00 kiste 40grub2: debug: parsing: initrd#011/initrd-4.12.14-lp151.28.16-default 2019-10-08T13:36:07.125741+02:00 kiste 40grub2: debug: parsing: } 2019-10-08T13:36:07.128962+02:00 kiste 40grub2: result: /dev/sda5:/dev/sda2:openSUSE Leap 15.1 :/boot/vmlinuz-4.12.14-lp151.28.16-default:/boot/initrd-4.12.14-lp151.28.16-default:root=UUID=12c94c4b-cbe9-46f9-9bc4-4b984a202901 net.ifnames=0 2019-10-08T13:36:07.132227+02:00 kiste 40grub2: debug: parsing: submenu 'Advanced options for openSUSE Leap 15.1 ' --hotkey=1 $menuentry_id_option 'gnulinux-advanced-12c94c4b-cbe9-46f9-9bc4-4b984a202901' { 2019-10-08T13:36:07.135394+02:00 kiste 40grub2: debug: parsing: menuentry 'openSUSE Leap 15.1 , with Linux 4.12.14-lp151.28.16-default' --hotkey=2 --class opensuse --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.12.14-lp151.28.16-default-advanced-12c94c4b-cbe9-46f9-9bc4-4b984a202901' { 2019-10-08T13:36:07.153168+02:00 kiste 40grub2: debug: parsing: load_video 2019-10-08T13:36:07.156320+02:00 kiste 40grub2: debug: parsing: set gfxpayload=keep 2019-10-08T13:36:07.159403+02:00 kiste 40grub2: debug: parsing: insmod gzio 2019-10-08T13:36:07.162523+02:00 kiste 40grub2: debug: parsing: insmod part_msdos 2019-10-08T13:36:07.165656+02:00 kiste 40grub2: debug: parsing: insmod ext2 2019-10-08T13:36:07.168830+02:00 kiste 40grub2: debug: parsing: set root='hd0,msdos2' 2019-10-08T13:36:07.172066+02:00 kiste 40grub2: debug: parsing: if [ x$feature_platform_search_hint = xy ]; then 2019-10-08T13:36:07.175333+02:00 kiste 40grub2: debug: parsing: search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2 --hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2 --hint='hd0,msdos2' 2c080be0-510c-4ca8-a7b4-f7e249922090 2019-10-08T13:36:07.178515+02:00 kiste 40grub2: debug: parsing: else 2019-10-08T13:36:07.181666+02:00 kiste 40grub2: debug: parsing: search --no-floppy --fs-uuid --set=root 2c080be0-510c-4ca8-a7b4-f7e249922090 2019-10-08T13:36:07.184818+02:00 kiste 40grub2: debug: parsing: fi 2019-10-08T13:36:07.188054+02:00 kiste 40grub2: debug: parsing: echo#011'Loading Linux 4.12.14-lp151.28.16-default ...' 2019-10-08T13:36:07.191192+02:00 kiste 40grub2: debug: parsing: linux#011/vmlinuz-4.12.14-lp151.28.16-default root=UUID=12c94c4b-cbe9-46f9-9bc4-4b984a202901 net.ifnames=0 2019-10-08T13:36:07.197498+02:00 kiste 40grub2: debug: parsing: echo#011'Loading initial ramdisk ...' 2019-10-08T13:36:07.200568+02:00 kiste 40grub2: debug: parsing: initrd#011/initrd-4.12.14-lp151.28.16-default 2019-10-08T13:36:07.209716+02:00 kiste 40grub2: debug: parsing: } 2019-10-08T13:36:07.212914+02:00 kiste 40grub2: result: /dev/sda5:/dev/sda2:openSUSE Leap 15.1 , with Linux 4.12.14-lp151.28.16-default:/boot/vmlinuz-4.12.14-lp151.28.16-default:/boot/initrd-4.12.14-lp151.28.16-default:root=UUID=12c94c4b-cbe9-46f9-9bc4-4b984a202901 net.ifnames=0 2019-10-08T13:36:07.216104+02:00 kiste 40grub2: debug: parsing: menuentry 'openSUSE Leap 15.1 , with Linux 4.12.14-lp151.28.16-default (recovery mode)' --hotkey=3 --class opensuse --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.12.14-lp151.28.16-default-recovery-12c94c4b-cbe9-46f9-9bc4-4b984a202901' { 2019-10-08T13:36:07.234058+02:00 kiste 40grub2: debug: parsing: load_video 2019-10-08T13:36:07.237286+02:00 kiste 40grub2: debug: parsing: set gfxpayload=keep 2019-10-08T13:36:07.240491+02:00 kiste 40grub2: debug: parsing: insmod gzio 2019-10-08T13:36:07.243596+02:00 kiste 40grub2: debug: parsing: insmod part_msdos 2019-10-08T13:36:07.246674+02:00 kiste 40grub2: debug: parsing: insmod ext2 2019-10-08T13:36:07.249754+02:00 kiste 40grub2: debug: parsing: set root='hd0,msdos2' 2019-10-08T13:36:07.252731+02:00 kiste 40grub2: debug: parsing: if [ x$feature_platform_search_hint = xy ]; then 2019-10-08T13:36:07.255872+02:00 kiste 40grub2: debug: parsing: search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2 --hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2 --hint='hd0,msdos2' 2c080be0-510c-4ca8-a7b4-f7e249922090 2019-10-08T13:36:07.258953+02:00 kiste 40grub2: debug: parsing: else 2019-10-08T13:36:07.262086+02:00 kiste 40grub2: debug: parsing: search --no-floppy --fs-uuid --set=root 2c080be0-510c-4ca8-a7b4-f7e249922090 2019-10-08T13:36:07.265186+02:00 kiste 40grub2: debug: parsing: fi 2019-10-08T13:36:07.268291+02:00 kiste 40grub2: debug: parsing: echo#011'Loading Linux 4.12.14-lp151.28.16-default ...' 2019-10-08T13:36:07.271398+02:00 kiste 40grub2: debug: parsing: linux#011/vmlinuz-4.12.14-lp151.28.16-default root=UUID=12c94c4b-cbe9-46f9-9bc4-4b984a202901 2019-10-08T13:36:07.277661+02:00 kiste 40grub2: debug: parsing: echo#011'Loading initial ramdisk ...' 2019-10-08T13:36:07.280656+02:00 kiste 40grub2: debug: parsing: initrd#011/initrd-4.12.14-lp151.28.16-default 2019-10-08T13:36:07.290036+02:00 kiste 40grub2: debug: parsing: } 2019-10-08T13:36:07.293222+02:00 kiste 40grub2: result: /dev/sda5:/dev/sda2:openSUSE Leap 15.1 , with Linux 4.12.14-lp151.28.16-default (recovery mode):/boot/vmlinuz-4.12.14-lp151.28.16-default:/boot/initrd-4.12.14-lp151.28.16-default:root=UUID=12c94c4b-cbe9-46f9-9bc4-4b984a202901 2019-10-08T13:36:07.296372+02:00 kiste 40grub2: debug: parsing: menuentry 'openSUSE Leap 15.1 , with Linux 4.12.14-lp151.28.13-default' --class opensuse --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.12.14-lp151.28.13-default-advanced-12c94c4b-cbe9-46f9-9bc4-4b984a202901' { 2019-10-08T13:36:07.313994+02:00 kiste 40grub2: debug: parsing: load_video 2019-10-08T13:36:07.317083+02:00 kiste 40grub2: debug: parsing: set gfxpayload=keep 2019-10-08T13:36:07.320140+02:00 kiste 40grub2: debug: parsing: insmod gzio 2019-10-08T13:36:07.323234+02:00 kiste 40grub2: debug: parsing: insmod part_msdos 2019-10-08T13:36:07.326347+02:00 kiste 40grub2: debug: parsing: insmod ext2 2019-10-08T13:36:07.329487+02:00 kiste 40grub2: debug: parsing: set root='hd0,msdos2' 2019-10-08T13:36:07.332642+02:00 kiste 40grub2: debug: parsing: if [ x$feature_platform_search_hint = xy ]; then 2019-10-08T13:36:07.335825+02:00 kiste 40grub2: debug: parsing: search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2 --hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2 --hint='hd0,msdos2' 2c080be0-510c-4ca8-a7b4-f7e249922090 2019-10-08T13:36:07.338908+02:00 kiste 40grub2: debug: parsing: else 2019-10-08T13:36:07.341869+02:00 kiste 40grub2: debug: parsing: search --no-floppy --fs-uuid --set=root 2c080be0-510c-4ca8-a7b4-f7e249922090 2019-10-08T13:36:07.345099+02:00 kiste 40grub2: debug: parsing: fi 2019-10-08T13:36:07.348265+02:00 kiste 40grub2: debug: parsing: echo#011'Loading Linux 4.12.14-lp151.28.13-default ...' 2019-10-08T13:36:07.351369+02:00 kiste 40grub2: debug: parsing: linux#011/vmlinuz-4.12.14-lp151.28.13-default root=UUID=12c94c4b-cbe9-46f9-9bc4-4b984a202901 net.ifnames=0 2019-10-08T13:36:07.357693+02:00 kiste 40grub2: debug: parsing: echo#011'Loading initial ramdisk ...' 2019-10-08T13:36:07.360649+02:00 kiste 40grub2: debug: parsing: initrd#011/initrd-4.12.14-lp151.28.13-default 2019-10-08T13:36:07.369947+02:00 kiste 40grub2: debug: parsing: } 2019-10-08T13:36:07.373178+02:00 kiste 40grub2: result: /dev/sda5:/dev/sda2:openSUSE Leap 15.1 , with Linux 4.12.14-lp151.28.13-default:/boot/vmlinuz-4.12.14-lp151.28.13-default:/boot/initrd-4.12.14-lp151.28.13-default:root=UUID=12c94c4b-cbe9-46f9-9bc4-4b984a202901 net.ifnames=0 2019-10-08T13:36:07.376362+02:00 kiste 40grub2: debug: parsing: menuentry 'openSUSE Leap 15.1 , with Linux 4.12.14-lp151.28.13-default (recovery mode)' --hotkey=1 --class opensuse --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.12.14-lp151.28.13-default-recovery-12c94c4b-cbe9-46f9-9bc4-4b984a202901' { 2019-10-08T13:36:07.394090+02:00 kiste 40grub2: debug: parsing: load_video 2019-10-08T13:36:07.397257+02:00 kiste 40grub2: debug: parsing: set gfxpayload=keep 2019-10-08T13:36:07.400329+02:00 kiste 40grub2: debug: parsing: insmod gzio 2019-10-08T13:36:07.403403+02:00 kiste 40grub2: debug: parsing: insmod part_msdos 2019-10-08T13:36:07.406535+02:00 kiste 40grub2: debug: parsing: insmod ext2 2019-10-08T13:36:07.409619+02:00 kiste 40grub2: debug: parsing: set root='hd0,msdos2' 2019-10-08T13:36:07.412762+02:00 kiste 40grub2: debug: parsing: if [ x$feature_platform_search_hint = xy ]; then 2019-10-08T13:36:07.415896+02:00 kiste 40grub2: debug: parsing: search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2 --hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2 --hint='hd0,msdos2' 2c080be0-510c-4ca8-a7b4-f7e249922090 2019-10-08T13:36:07.419012+02:00 kiste 40grub2: debug: parsing: else 2019-10-08T13:36:07.422215+02:00 kiste 40grub2: debug: parsing: search --no-floppy --fs-uuid --set=root 2c080be0-510c-4ca8-a7b4-f7e249922090 2019-10-08T13:36:07.425309+02:00 kiste 40grub2: debug: parsing: fi 2019-10-08T13:36:07.428461+02:00 kiste 40grub2: debug: parsing: echo#011'Loading Linux 4.12.14-lp151.28.13-default ...' 2019-10-08T13:36:07.431586+02:00 kiste 40grub2: debug: parsing: linux#011/vmlinuz-4.12.14-lp151.28.13-default root=UUID=12c94c4b-cbe9-46f9-9bc4-4b984a202901 2019-10-08T13:36:07.437949+02:00 kiste 40grub2: debug: parsing: echo#011'Loading initial ramdisk ...' 2019-10-08T13:36:07.441135+02:00 kiste 40grub2: debug: parsing: initrd#011/initrd-4.12.14-lp151.28.13-default 2019-10-08T13:36:07.450581+02:00 kiste 40grub2: debug: parsing: } 2019-10-08T13:36:07.453643+02:00 kiste 40grub2: result: /dev/sda5:/dev/sda2:openSUSE Leap 15.1 , with Linux 4.12.14-lp151.28.13-default (recovery mode):/boot/vmlinuz-4.12.14-lp151.28.13-default:/boot/initrd-4.12.14-lp151.28.13-default:root=UUID=12c94c4b-cbe9-46f9-9bc4-4b984a202901 2019-10-08T13:36:07.456823+02:00 kiste 40grub2: debug: parsing: menuentry 'openSUSE Leap 15.1 , with Linux 4.12.14-lp151.28.7-default' --class opensuse --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.12.14-lp151.28.7-default-advanced-12c94c4b-cbe9-46f9-9bc4-4b984a202901' { 2019-10-08T13:36:07.474760+02:00 kiste 40grub2: debug: parsing: load_video 2019-10-08T13:36:07.477867+02:00 kiste 40grub2: debug: parsing: set gfxpayload=keep 2019-10-08T13:36:07.480876+02:00 kiste 40grub2: debug: parsing: insmod gzio 2019-10-08T13:36:07.483975+02:00 kiste 40grub2: debug: parsing: insmod part_msdos 2019-10-08T13:36:07.487066+02:00 kiste 40grub2: debug: parsing: insmod ext2 2019-10-08T13:36:07.490207+02:00 kiste 40grub2: debug: parsing: set root='hd0,msdos2' 2019-10-08T13:36:07.493712+02:00 kiste 40grub2: debug: parsing: if [ x$feature_platform_search_hint = xy ]; then 2019-10-08T13:36:07.497146+02:00 kiste 40grub2: debug: parsing: search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2 --hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2 --hint='hd0,msdos2' 2c080be0-510c-4ca8-a7b4-f7e249922090 2019-10-08T13:36:07.500765+02:00 kiste 40grub2: debug: parsing: else 2019-10-08T13:36:07.503956+02:00 kiste 40grub2: debug: parsing: search --no-floppy --fs-uuid --set=root 2c080be0-510c-4ca8-a7b4-f7e249922090 2019-10-08T13:36:07.507038+02:00 kiste 40grub2: debug: parsing: fi 2019-10-08T13:36:07.510167+02:00 kiste 40grub2: debug: parsing: echo#011'Loading Linux 4.12.14-lp151.28.7-default ...' 2019-10-08T13:36:07.513401+02:00 kiste 40grub2: debug: parsing: linux#011/vmlinuz-4.12.14-lp151.28.7-default root=UUID=12c94c4b-cbe9-46f9-9bc4-4b984a202901 net.ifnames=0 2019-10-08T13:36:07.519654+02:00 kiste 40grub2: debug: parsing: echo#011'Loading initial ramdisk ...' 2019-10-08T13:36:07.523226+02:00 kiste 40grub2: debug: parsing: initrd#011/initrd-4.12.14-lp151.28.7-default 2019-10-08T13:36:07.533687+02:00 kiste 40grub2: debug: parsing: } 2019-10-08T13:36:07.537550+02:00 kiste 40grub2: debug: parsing: menuentry 'openSUSE Leap 15.1 , with Linux 4.12.14-lp151.28.7-default (recovery mode)' --hotkey=1 --class opensuse --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.12.14-lp151.28.7-default-recovery-12c94c4b-cbe9-46f9-9bc4-4b984a202901' { 2019-10-08T13:36:07.556597+02:00 kiste 40grub2: debug: parsing: load_video 2019-10-08T13:36:07.559578+02:00 kiste 40grub2: debug: parsing: set gfxpayload=keep 2019-10-08T13:36:07.562723+02:00 kiste 40grub2: debug: parsing: insmod gzio 2019-10-08T13:36:07.565856+02:00 kiste 40grub2: debug: parsing: insmod part_msdos 2019-10-08T13:36:07.568950+02:00 kiste 40grub2: debug: parsing: insmod ext2 2019-10-08T13:36:07.572082+02:00 kiste 40grub2: debug: parsing: set root='hd0,msdos2' 2019-10-08T13:36:07.575186+02:00 kiste 40grub2: debug: parsing: if [ x$feature_platform_search_hint = xy ]; then 2019-10-08T13:36:07.578311+02:00 kiste 40grub2: debug: parsing: search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2 --hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2 --hint='hd0,msdos2' 2c080be0-510c-4ca8-a7b4-f7e249922090 2019-10-08T13:36:07.581452+02:00 kiste 40grub2: debug: parsing: else 2019-10-08T13:36:07.584570+02:00 kiste 40grub2: debug: parsing: search --no-floppy --fs-uuid --set=root 2c080be0-510c-4ca8-a7b4-f7e249922090 2019-10-08T13:36:07.587633+02:00 kiste 40grub2: debug: parsing: fi 2019-10-08T13:36:07.591191+02:00 kiste 40grub2: debug: parsing: echo#011'Loading Linux 4.12.14-lp151.28.7-default ...' 2019-10-08T13:36:07.594554+02:00 kiste 40grub2: debug: parsing: linux#011/vmlinuz-4.12.14-lp151.28.7-default root=UUID=12c94c4b-cbe9-46f9-9bc4-4b984a202901 2019-10-08T13:36:07.601278+02:00 kiste 40grub2: debug: parsing: echo#011'Loading initial ramdisk ...' 2019-10-08T13:36:07.604359+02:00 kiste 40grub2: debug: parsing: initrd#011/initrd-4.12.14-lp151.28.7-default 2019-10-08T13:36:07.613759+02:00 kiste 40grub2: debug: parsing: } 2019-10-08T13:36:07.617011+02:00 kiste 40grub2: debug: parsing: } 2019-10-08T13:36:07.620022+02:00 kiste 40grub2: debug: parsing: 2019-10-08T13:36:07.623175+02:00 kiste 40grub2: debug: parsing: ### END /etc/grub.d/10_linux ### 2019-10-08T13:36:07.626503+02:00 kiste 40grub2: debug: parsing: 2019-10-08T13:36:07.629621+02:00 kiste 40grub2: debug: parsing: ### BEGIN /etc/grub.d/20_linux_xen ### 2019-10-08T13:36:07.632763+02:00 kiste 40grub2: debug: parsing: 2019-10-08T13:36:07.636051+02:00 kiste 40grub2: debug: parsing: ### END /etc/grub.d/20_linux_xen ### 2019-10-08T13:36:07.638995+02:00 kiste 40grub2: debug: parsing: 2019-10-08T13:36:07.642760+02:00 kiste 40grub2: debug: parsing: ### BEGIN /etc/grub.d/20_memtest86+ ### 2019-10-08T13:36:07.645766+02:00 kiste 40grub2: debug: parsing: ### END /etc/grub.d/20_memtest86+ ### 2019-10-08T13:36:07.649097+02:00 kiste 40grub2: debug: parsing: 2019-10-08T13:36:07.652171+02:00 kiste 40grub2: debug: parsing: ### BEGIN /etc/grub.d/30_os-prober ### 2019-10-08T13:36:07.655192+02:00 kiste 40grub2: debug: parsing: menuentry 'openSUSE Leap 15.1 (on /dev/sda5)' --class opensuse --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-332d07b6-ba9f-4f2b-8c79-e112d194fd7e' { 2019-10-08T13:36:07.675504+02:00 kiste 40grub2: Skipping entry 'openSUSE Leap 15.1 (on /dev/sda5)': 2019-10-08T13:36:07.678682+02:00 kiste 40grub2: appears to be an automatic reference taken from another grub.cfg 2019-10-08T13:36:07.681913+02:00 kiste 40grub2: debug: parsing: insmod part_msdos 2019-10-08T13:36:07.685134+02:00 kiste 40grub2: debug: parsing: insmod ext2 2019-10-08T13:36:07.688442+02:00 kiste 40grub2: debug: parsing: set root='hd0,msdos2' 2019-10-08T13:36:07.691494+02:00 kiste 40grub2: debug: parsing: if [ x$feature_platform_search_hint = xy ]; then 2019-10-08T13:36:07.694817+02:00 kiste 40grub2: debug: parsing: search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2 --hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2 --hint='hd0,msdos2' 2c080be0-510c-4ca8-a7b4-f7e249922090 2019-10-08T13:36:07.698107+02:00 kiste 40grub2: debug: parsing: else 2019-10-08T13:36:07.701379+02:00 kiste 40grub2: debug: parsing: search --no-floppy --fs-uuid --set=root 2c080be0-510c-4ca8-a7b4-f7e249922090 2019-10-08T13:36:07.704844+02:00 kiste 40grub2: debug: parsing: fi 2019-10-08T13:36:07.708143+02:00 kiste 40grub2: debug: parsing: linux /vmlinuz-4.12.14-lp151.28.16-default root=UUID=12c94c4b-cbe9-46f9-9bc4-4b984a202901 net.ifnames=0 2019-10-08T13:36:07.714381+02:00 kiste 40grub2: debug: parsing: initrd /initrd-4.12.14-lp151.28.16-default 2019-10-08T13:36:07.724074+02:00 kiste 40grub2: debug: parsing: } 2019-10-08T13:36:07.727471+02:00 kiste 40grub2: debug: parsing: submenu 'Advanced options for openSUSE Leap 15.1 (on /dev/sda5)' $menuentry_id_option 'osprober-gnulinux-advanced-332d07b6-ba9f-4f2b-8c79-e112d194fd7e' { 2019-10-08T13:36:07.730878+02:00 kiste 40grub2: debug: parsing: menuentry 'openSUSE Leap 15.1 (on /dev/sda5)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/vmlinuz-4.12.14-lp151.28.16-default--332d07b6-ba9f-4f2b-8c79-e112d194fd7e' { 2019-10-08T13:36:07.747231+02:00 kiste 40grub2: Skipping entry 'openSUSE Leap 15.1 (on /dev/sda5)': 2019-10-08T13:36:07.750274+02:00 kiste 40grub2: appears to be an automatic reference taken from another grub.cfg 2019-10-08T13:36:07.753400+02:00 kiste 40grub2: debug: parsing: insmod part_msdos 2019-10-08T13:36:07.756546+02:00 kiste 40grub2: debug: parsing: insmod ext2 2019-10-08T13:36:07.759653+02:00 kiste 40grub2: debug: parsing: set root='hd0,msdos2' 2019-10-08T13:36:07.762860+02:00 kiste 40grub2: debug: parsing: if [ x$feature_platform_search_hint = xy ]; then 2019-10-08T13:36:07.766083+02:00 kiste 40grub2: debug: parsing: search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2 --hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2 --hint='hd0,msdos2' 2c080be0-510c-4ca8-a7b4-f7e249922090 2019-10-08T13:36:07.769267+02:00 kiste 40grub2: debug: parsing: else 2019-10-08T13:36:07.772420+02:00 kiste 40grub2: debug: parsing: search --no-floppy --fs-uuid --set=root 2c080be0-510c-4ca8-a7b4-f7e249922090 2019-10-08T13:36:07.775507+02:00 kiste 40grub2: debug: parsing: fi 2019-10-08T13:36:07.778639+02:00 kiste 40grub2: debug: parsing: linux /vmlinuz-4.12.14-lp151.28.16-default root=UUID=12c94c4b-cbe9-46f9-9bc4-4b984a202901 net.ifnames=0 2019-10-08T13:36:07.785046+02:00 kiste 40grub2: debug: parsing: initrd /initrd-4.12.14-lp151.28.16-default 2019-10-08T13:36:07.794392+02:00 kiste 40grub2: debug: parsing: } 2019-10-08T13:36:07.797649+02:00 kiste 40grub2: debug: parsing: menuentry 'openSUSE Leap 15.1 , with Linux 4.12.14-lp151.28.16-default (on /dev/sda5)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/vmlinuz-4.12.14-lp151.28.16-default--332d07b6-ba9f-4f2b-8c79-e112d194fd7e' { 2019-10-08T13:36:07.815212+02:00 kiste 40grub2: Skipping entry 'openSUSE Leap 15.1 , with Linux 4.12.14-lp151.28.16-default (on /dev/sda5)': 2019-10-08T13:36:07.818195+02:00 kiste 40grub2: appears to be an automatic reference taken from another grub.cfg 2019-10-08T13:36:07.821324+02:00 kiste 40grub2: debug: parsing: insmod part_msdos 2019-10-08T13:36:07.824588+02:00 kiste 40grub2: debug: parsing: insmod ext2 2019-10-08T13:36:07.827512+02:00 kiste 40grub2: debug: parsing: set root='hd0,msdos2' 2019-10-08T13:36:07.830579+02:00 kiste 40grub2: debug: parsing: if [ x$feature_platform_search_hint = xy ]; then 2019-10-08T13:36:07.833779+02:00 kiste 40grub2: debug: parsing: search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2 --hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2 --hint='hd0,msdos2' 2c080be0-510c-4ca8-a7b4-f7e249922090 2019-10-08T13:36:07.837042+02:00 kiste 40grub2: debug: parsing: else 2019-10-08T13:36:07.840046+02:00 kiste 40grub2: debug: parsing: search --no-floppy --fs-uuid --set=root 2c080be0-510c-4ca8-a7b4-f7e249922090 2019-10-08T13:36:07.843126+02:00 kiste 40grub2: debug: parsing: fi 2019-10-08T13:36:07.846250+02:00 kiste 40grub2: debug: parsing: linux /vmlinuz-4.12.14-lp151.28.16-default root=UUID=12c94c4b-cbe9-46f9-9bc4-4b984a202901 net.ifnames=0 2019-10-08T13:36:07.852654+02:00 kiste 40grub2: debug: parsing: initrd /initrd-4.12.14-lp151.28.16-default 2019-10-08T13:36:07.862009+02:00 kiste 40grub2: debug: parsing: } 2019-10-08T13:36:07.865264+02:00 kiste 40grub2: debug: parsing: menuentry 'openSUSE Leap 15.1 , with Linux 4.12.14-lp151.28.16-default (recovery mode) (on /dev/sda5)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/vmlinuz-4.12.14-lp151.28.16-default--332d07b6-ba9f-4f2b-8c79-e112d194fd7e' { 2019-10-08T13:36:07.881230+02:00 kiste 40grub2: Skipping entry 'openSUSE Leap 15.1 , with Linux 4.12.14-lp151.28.16-default (recovery mode) (on /dev/sda5)': 2019-10-08T13:36:07.884363+02:00 kiste 40grub2: appears to be an automatic reference taken from another grub.cfg 2019-10-08T13:36:07.887455+02:00 kiste 40grub2: debug: parsing: insmod part_msdos 2019-10-08T13:36:07.890585+02:00 kiste 40grub2: debug: parsing: insmod ext2 2019-10-08T13:36:07.893743+02:00 kiste 40grub2: debug: parsing: set root='hd0,msdos2' 2019-10-08T13:36:07.896912+02:00 kiste 40grub2: debug: parsing: if [ x$feature_platform_search_hint = xy ]; then 2019-10-08T13:36:07.900109+02:00 kiste 40grub2: debug: parsing: search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2 --hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2 --hint='hd0,msdos2' 2c080be0-510c-4ca8-a7b4-f7e249922090 2019-10-08T13:36:07.903262+02:00 kiste 40grub2: debug: parsing: else 2019-10-08T13:36:07.906418+02:00 kiste 40grub2: debug: parsing: search --no-floppy --fs-uuid --set=root 2c080be0-510c-4ca8-a7b4-f7e249922090 2019-10-08T13:36:07.909573+02:00 kiste 40grub2: debug: parsing: fi 2019-10-08T13:36:07.912763+02:00 kiste 40grub2: debug: parsing: linux /vmlinuz-4.12.14-lp151.28.16-default root=UUID=12c94c4b-cbe9-46f9-9bc4-4b984a202901 2019-10-08T13:36:07.919046+02:00 kiste 40grub2: debug: parsing: initrd /initrd-4.12.14-lp151.28.16-default 2019-10-08T13:36:07.928554+02:00 kiste 40grub2: debug: parsing: } 2019-10-08T13:36:07.931621+02:00 kiste 40grub2: debug: parsing: menuentry 'openSUSE Leap 15.1 , with Linux 4.12.14-lp151.28.13-default (on /dev/sda5)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/vmlinuz-4.12.14-lp151.28.13-default--332d07b6-ba9f-4f2b-8c79-e112d194fd7e' { 2019-10-08T13:36:07.947877+02:00 kiste 40grub2: Skipping entry 'openSUSE Leap 15.1 , with Linux 4.12.14-lp151.28.13-default (on /dev/sda5)': 2019-10-08T13:36:07.950812+02:00 kiste 40grub2: appears to be an automatic reference taken from another grub.cfg 2019-10-08T13:36:07.953852+02:00 kiste 40grub2: debug: parsing: insmod part_msdos 2019-10-08T13:36:07.957009+02:00 kiste 40grub2: debug: parsing: insmod ext2 2019-10-08T13:36:07.960231+02:00 kiste 40grub2: debug: parsing: set root='hd0,msdos2' 2019-10-08T13:36:07.963326+02:00 kiste 40grub2: debug: parsing: if [ x$feature_platform_search_hint = xy ]; then 2019-10-08T13:36:07.966456+02:00 kiste 40grub2: debug: parsing: search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2 --hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2 --hint='hd0,msdos2' 2c080be0-510c-4ca8-a7b4-f7e249922090 2019-10-08T13:36:07.969618+02:00 kiste 40grub2: debug: parsing: else 2019-10-08T13:36:07.972758+02:00 kiste 40grub2: debug: parsing: search --no-floppy --fs-uuid --set=root 2c080be0-510c-4ca8-a7b4-f7e249922090 2019-10-08T13:36:07.975969+02:00 kiste 40grub2: debug: parsing: fi 2019-10-08T13:36:07.979193+02:00 kiste 40grub2: debug: parsing: linux /vmlinuz-4.12.14-lp151.28.13-default root=UUID=12c94c4b-cbe9-46f9-9bc4-4b984a202901 net.ifnames=0 2019-10-08T13:36:07.985505+02:00 kiste 40grub2: debug: parsing: initrd /initrd-4.12.14-lp151.28.13-default 2019-10-08T13:36:07.994885+02:00 kiste 40grub2: debug: parsing: } 2019-10-08T13:36:07.998127+02:00 kiste 40grub2: debug: parsing: menuentry 'openSUSE Leap 15.1 , with Linux 4.12.14-lp151.28.13-default (recovery mode) (on /dev/sda5)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/vmlinuz-4.12.14-lp151.28.13-default--332d07b6-ba9f-4f2b-8c79-e112d194fd7e' { 2019-10-08T13:36:08.015747+02:00 kiste 40grub2: Skipping entry 'openSUSE Leap 15.1 , with Linux 4.12.14-lp151.28.13-default (recovery mode) (on /dev/sda5)': 2019-10-08T13:36:08.018697+02:00 kiste 40grub2: appears to be an automatic reference taken from another grub.cfg 2019-10-08T13:36:08.021665+02:00 kiste 40grub2: debug: parsing: insmod part_msdos 2019-10-08T13:36:08.024731+02:00 kiste 40grub2: debug: parsing: insmod ext2 2019-10-08T13:36:08.027841+02:00 kiste 40grub2: debug: parsing: set root='hd0,msdos2' 2019-10-08T13:36:08.030929+02:00 kiste 40grub2: debug: parsing: if [ x$feature_platform_search_hint = xy ]; then 2019-10-08T13:36:08.034052+02:00 kiste 40grub2: debug: parsing: search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2 --hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2 --hint='hd0,msdos2' 2c080be0-510c-4ca8-a7b4-f7e249922090 2019-10-08T13:36:08.037249+02:00 kiste 40grub2: debug: parsing: else 2019-10-08T13:36:08.040345+02:00 kiste 40grub2: debug: parsing: search --no-floppy --fs-uuid --set=root 2c080be0-510c-4ca8-a7b4-f7e249922090 2019-10-08T13:36:08.043420+02:00 kiste 40grub2: debug: parsing: fi 2019-10-08T13:36:08.046684+02:00 kiste 40grub2: debug: parsing: linux /vmlinuz-4.12.14-lp151.28.13-default root=UUID=12c94c4b-cbe9-46f9-9bc4-4b984a202901 2019-10-08T13:36:08.052996+02:00 kiste 40grub2: debug: parsing: initrd /initrd-4.12.14-lp151.28.13-default 2019-10-08T13:36:08.062416+02:00 kiste 40grub2: debug: parsing: } 2019-10-08T13:36:08.065704+02:00 kiste 40grub2: debug: parsing: menuentry 'openSUSE Leap 15.1 , with Linux 4.12.14-lp151.28.7-default (on /dev/sda5)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/vmlinuz-4.12.14-lp151.28.7-default--332d07b6-ba9f-4f2b-8c79-e112d194fd7e' { 2019-10-08T13:36:08.083078+02:00 kiste 40grub2: Skipping entry 'openSUSE Leap 15.1 , with Linux 4.12.14-lp151.28.7-default (on /dev/sda5)': 2019-10-08T13:36:08.086060+02:00 kiste 40grub2: appears to be an automatic reference taken from another grub.cfg 2019-10-08T13:36:08.089013+02:00 kiste 40grub2: debug: parsing: insmod part_msdos 2019-10-08T13:36:08.092327+02:00 kiste 40grub2: debug: parsing: insmod ext2 2019-10-08T13:36:08.095248+02:00 kiste 40grub2: debug: parsing: set root='hd0,msdos2' 2019-10-08T13:36:08.098423+02:00 kiste 40grub2: debug: parsing: if [ x$feature_platform_search_hint = xy ]; then 2019-10-08T13:36:08.101655+02:00 kiste 40grub2: debug: parsing: search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2 --hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2 --hint='hd0,msdos2' 2c080be0-510c-4ca8-a7b4-f7e249922090 2019-10-08T13:36:08.104814+02:00 kiste 40grub2: debug: parsing: else 2019-10-08T13:36:08.107897+02:00 kiste 40grub2: debug: parsing: search --no-floppy --fs-uuid --set=root 2c080be0-510c-4ca8-a7b4-f7e249922090 2019-10-08T13:36:08.110997+02:00 kiste 40grub2: debug: parsing: fi 2019-10-08T13:36:08.114173+02:00 kiste 40grub2: debug: parsing: linux /vmlinuz-4.12.14-lp151.28.7-default root=UUID=12c94c4b-cbe9-46f9-9bc4-4b984a202901 net.ifnames=0 2019-10-08T13:36:08.120716+02:00 kiste 40grub2: debug: parsing: initrd /initrd-4.12.14-lp151.28.7-default 2019-10-08T13:36:08.130065+02:00 kiste 40grub2: debug: parsing: } 2019-10-08T13:36:08.133273+02:00 kiste 40grub2: debug: parsing: menuentry 'openSUSE Leap 15.1 , with Linux 4.12.14-lp151.28.7-default (recovery mode) (on /dev/sda5)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/vmlinuz-4.12.14-lp151.28.7-default--332d07b6-ba9f-4f2b-8c79-e112d194fd7e' { 2019-10-08T13:36:08.149515+02:00 kiste 40grub2: Skipping entry 'openSUSE Leap 15.1 , with Linux 4.12.14-lp151.28.7-default (recovery mode) (on /dev/sda5)': 2019-10-08T13:36:08.152599+02:00 kiste 40grub2: appears to be an automatic reference taken from another grub.cfg 2019-10-08T13:36:08.155758+02:00 kiste 40grub2: debug: parsing: insmod part_msdos 2019-10-08T13:36:08.158734+02:00 kiste 40grub2: debug: parsing: insmod ext2 2019-10-08T13:36:08.161792+02:00 kiste 40grub2: debug: parsing: set root='hd0,msdos2' 2019-10-08T13:36:08.164913+02:00 kiste 40grub2: debug: parsing: if [ x$feature_platform_search_hint = xy ]; then 2019-10-08T13:36:08.168104+02:00 kiste 40grub2: debug: parsing: search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2 --hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2 --hint='hd0,msdos2' 2c080be0-510c-4ca8-a7b4-f7e249922090 2019-10-08T13:36:08.171302+02:00 kiste 40grub2: debug: parsing: else 2019-10-08T13:36:08.174400+02:00 kiste 40grub2: debug: parsing: search --no-floppy --fs-uuid --set=root 2c080be0-510c-4ca8-a7b4-f7e249922090 2019-10-08T13:36:08.177535+02:00 kiste 40grub2: debug: parsing: fi 2019-10-08T13:36:08.180807+02:00 kiste 40grub2: debug: parsing: linux /vmlinuz-4.12.14-lp151.28.7-default root=UUID=12c94c4b-cbe9-46f9-9bc4-4b984a202901 2019-10-08T13:36:08.187139+02:00 kiste 40grub2: debug: parsing: initrd /initrd-4.12.14-lp151.28.7-default 2019-10-08T13:36:08.196631+02:00 kiste 40grub2: debug: parsing: } 2019-10-08T13:36:08.199910+02:00 kiste 40grub2: debug: parsing: } 2019-10-08T13:36:08.202936+02:00 kiste 40grub2: debug: parsing: 2019-10-08T13:36:08.205948+02:00 kiste 40grub2: debug: parsing: ### END /etc/grub.d/30_os-prober ### 2019-10-08T13:36:08.209011+02:00 kiste 40grub2: debug: parsing: 2019-10-08T13:36:08.212172+02:00 kiste 40grub2: debug: parsing: ### BEGIN /etc/grub.d/40_custom ### 2019-10-08T13:36:08.215267+02:00 kiste 40grub2: debug: parsing: # This file provides an easy way to add custom menu entries. Simply type the 2019-10-08T13:36:08.218470+02:00 kiste 40grub2: debug: parsing: # menu entries you want to add after this comment. Be careful not to change 2019-10-08T13:36:08.221607+02:00 kiste 40grub2: debug: parsing: # the 'exec tail' line above. 2019-10-08T13:36:08.224720+02:00 kiste 40grub2: debug: parsing: ### END /etc/grub.d/40_custom ### 2019-10-08T13:36:08.227816+02:00 kiste 40grub2: debug: parsing: 2019-10-08T13:36:08.230915+02:00 kiste 40grub2: debug: parsing: ### BEGIN /etc/grub.d/41_custom ### 2019-10-08T13:36:08.234148+02:00 kiste 40grub2: debug: parsing: if [ -f ${config_directory}/custom.cfg ]; then 2019-10-08T13:36:08.237270+02:00 kiste 40grub2: debug: parsing: source ${config_directory}/custom.cfg 2019-10-08T13:36:08.240439+02:00 kiste 40grub2: debug: parsing: elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then 2019-10-08T13:36:08.243544+02:00 kiste 40grub2: debug: parsing: source $prefix/custom.cfg; 2019-10-08T13:36:08.246645+02:00 kiste 40grub2: debug: parsing: fi 2019-10-08T13:36:08.249781+02:00 kiste 40grub2: debug: parsing: ### END /etc/grub.d/41_custom ### 2019-10-08T13:36:08.252916+02:00 kiste 40grub2: debug: parsing: 2019-10-08T13:36:08.256146+02:00 kiste 40grub2: debug: parsing: ### BEGIN /etc/grub.d/80_suse_btrfs_snapshot ### 2019-10-08T13:36:08.259262+02:00 kiste 40grub2: debug: parsing: ### END /etc/grub.d/80_suse_btrfs_snapshot ### 2019-10-08T13:36:08.262403+02:00 kiste 40grub2: debug: parsing: 2019-10-08T13:36:08.265545+02:00 kiste 40grub2: debug: parsing: ### BEGIN /etc/grub.d/90_persistent ### 2019-10-08T13:36:08.268693+02:00 kiste 40grub2: debug: parsing: ### END /etc/grub.d/90_persistent ### 2019-10-08T13:36:08.271821+02:00 kiste 40grub2: debug: parsing: 2019-10-08T13:36:08.274912+02:00 kiste 40grub2: debug: parsing: ### BEGIN /etc/grub.d/95_textmode ### 2019-10-08T13:36:08.278167+02:00 kiste 40grub2: debug: parsing: ### END /etc/grub.d/95_textmode ### 2019-10-08T13:36:08.281857+02:00 kiste 50mounted-tests: debug: /usr/lib/linux-boot-probes/mounted/40grub2 succeeded 2019-10-08T13:36:08.301201+02:00 kiste linux-boot-prober: debug: linux detected by /usr/lib/linux-boot-probes/50mounted-tests 2019-10-08T13:36:13.449354+02:00 kiste [RPM][2122]: erase kernel-default-4.12.14-lp151.28.7.1.x86_64: success 2019-10-08T13:36:13.449771+02:00 kiste [RPM][2122]: Transaction ID 5d9c7489 finished: 0 2019-10-08T13:36:13.457380+02:00 kiste purge-kernels[1262]: Removed: 2019-10-08T13:36:13.457844+02:00 kiste purge-kernels[1262]: kernel-default-4.12.14-lp151.28.7.1.x86_64 2019-10-08T13:36:13.459016+02:00 kiste systemd[1]: Started Purge old kernels. 2019-10-08T13:36:13.460293+02:00 kiste systemd[1]: Reached target Multi-User System. 2019-10-08T13:36:13.460872+02:00 kiste systemd[1]: Reached target Graphical Interface. 2019-10-08T13:36:13.461157+02:00 kiste systemd[1]: Starting Update UTMP about System Runlevel Changes... 2019-10-08T13:36:13.471755+02:00 kiste systemd[1]: Started Update UTMP about System Runlevel Changes. 2019-10-08T13:36:13.472314+02:00 kiste systemd[1]: Startup finished in 2.122s (kernel) + 28.756s (initrd) + 2min 14.185s (userspace) = 2min 45.064s. 2019-10-08T13:36:24.785404+02:00 kiste nscd: 1164 Die beobachtete Datei »/etc/resolv.conf« wurde verändert (»mtime«) 2019-10-08T13:36:24.785890+02:00 kiste nscd: 1164 überwache Datei »/etc/resolv.conf« (7) 2019-10-08T13:36:24.786178+02:00 kiste nscd: 1164 überwache das Verzeichnis »/etc« (2) 2019-10-08T13:36:51.919908+02:00 kiste login: pam_unix(login:session): session closed for user root 2019-10-08T13:36:51.926799+02:00 kiste systemd[1]: getty(a)tty1.service: Service has no hold-off time (RestartSec=0), scheduling restart. 2019-10-08T13:36:51.927217+02:00 kiste systemd-logind[1269]: Session 2 logged out. Waiting for processes to exit. 2019-10-08T13:36:51.927676+02:00 kiste systemd[1]: Stopped Getty on tty1. 2019-10-08T13:36:51.928015+02:00 kiste systemd[1]: Started Getty on tty1. 2019-10-08T13:36:51.934646+02:00 kiste systemd-logind[1269]: Removed session 2. 2019-10-08T13:36:51.937258+02:00 kiste systemd[1]: Stopping User Manager for UID 0... 2019-10-08T13:36:52.013998+02:00 kiste systemd[3228]: Stopped target Default. 2019-10-08T13:36:52.014382+02:00 kiste systemd[3228]: Stopped target Basic System. 2019-10-08T13:36:52.014669+02:00 kiste systemd[3228]: Stopped target Sockets. 2019-10-08T13:36:52.014947+02:00 kiste systemd[3228]: Closed D-Bus User Message Bus Socket. 2019-10-08T13:36:52.015633+02:00 kiste systemd[3228]: Stopped target Timers. 2019-10-08T13:36:52.015979+02:00 kiste systemd[3228]: Stopped target Paths. 2019-10-08T13:36:52.016264+02:00 kiste systemd[3228]: Reached target Shutdown. 2019-10-08T13:36:52.016545+02:00 kiste systemd[3228]: Starting Exit the Session... 2019-10-08T13:36:52.036395+02:00 kiste systemd[3228]: Received SIGRTMIN+24 from PID 4327 (kill). 2019-10-08T13:36:52.056181+02:00 kiste systemd: pam_unix(systemd-user:session): session closed for user root 2019-10-08T13:36:52.058598+02:00 kiste systemd[1]: Stopped User Manager for UID 0. 2019-10-08T13:36:52.059877+02:00 kiste systemd[1]: Removed slice User Slice of root. 2019-10-08T13:37:03.718108+02:00 kiste sddm-greeter[1907]: Reading from "/usr/share/xsessions/plasma5.desktop" 2019-10-08T13:37:03.718562+02:00 kiste sddm[1632]: Message received from greeter: Login 2019-10-08T13:37:03.718900+02:00 kiste sddm[1632]: Reading from "/usr/share/xsessions/plasma5.desktop" 2019-10-08T13:37:03.721454+02:00 kiste sddm[1632]: Reading from "/usr/share/xsessions/plasma5.desktop" 2019-10-08T13:37:03.721869+02:00 kiste sddm[1632]: Session "/usr/share/xsessions/plasma5.desktop" selected, command: "/usr/bin/startkde" 2019-10-08T13:37:03.810159+02:00 kiste sddm-helper[4328]: [PAM] Starting... 2019-10-08T13:37:03.810683+02:00 kiste sddm-helper[4328]: [PAM] Authenticating... 2019-10-08T13:37:03.817501+02:00 kiste sddm-helper[4328]: [PAM] Preparing to converse... 2019-10-08T13:37:03.817913+02:00 kiste sddm-helper[4328]: [PAM] Conversation with 1 messages 2019-10-08T13:37:03.837957+02:00 kiste sddm-helper[4328]: [PAM] returning. 2019-10-08T13:37:03.839004+02:00 kiste sddm[1632]: Authenticated successfully 2019-10-08T13:37:03.839411+02:00 kiste sddm-greeter[1907]: Message received from daemon: LoginSucceeded (*) 2019-10-08T13:37:03.893232+02:00 kiste sddm-greeter[1907]: qrc:///QtQuick/VirtualKeyboard/content/components/SelectionControl.qml:80: TypeError: Cannot read property 'cursorRectIntersectsClipRect' of null (*) 2019-10-08T13:37:03.897454+02:00 kiste sddm-greeter[1907]: qrc:///QtQuick/VirtualKeyboard/content/components/SelectionControl.qml:48: TypeError: Cannot read property 'anchorRectIntersectsClipRect' of null 2019-10-08T13:37:03.905498+02:00 kiste systemd[1]: Created slice User Slice of jw. 2019-10-08T13:37:03.911740+02:00 kiste systemd[1]: Starting User Manager for UID 1000... 2019-10-08T13:37:03.925452+02:00 kiste systemd-logind[1269]: New session 3 of user jw. 2019-10-08T13:37:03.925821+02:00 kiste systemd: pam_unix(systemd-user:session): session opened for user jw by (uid=0) 2019-10-08T13:37:03.926200+02:00 kiste systemd[1]: Started Session 3 of user jw. 2019-10-08T13:37:04.084028+02:00 kiste systemd[4329]: Starting D-Bus User Message Bus Socket. 2019-10-08T13:37:04.084435+02:00 kiste systemd[4329]: Reached target Timers. 2019-10-08T13:37:04.084724+02:00 kiste systemd[4329]: Reached target Paths. 2019-10-08T13:37:04.097216+02:00 kiste systemd[4329]: Listening on D-Bus User Message Bus Socket. 2019-10-08T13:37:04.097580+02:00 kiste systemd[4329]: Reached target Sockets. 2019-10-08T13:37:04.097882+02:00 kiste systemd[4329]: Reached target Basic System. 2019-10-08T13:37:04.098152+02:00 kiste systemd[1]: Started User Manager for UID 1000. 2019-10-08T13:37:04.098432+02:00 kiste systemd[4329]: Reached target Default. 2019-10-08T13:37:04.098731+02:00 kiste systemd[4329]: Startup finished in 156ms. 2019-10-08T13:37:04.104399+02:00 kiste sddm-helper: pam_unix(sddm:session): session opened for user jw by (uid=0) 2019-10-08T13:37:04.104846+02:00 kiste sddm-helper[4328]: Starting: "/etc/X11/xdm/Xsession \"/usr/bin/startkde\"" 2019-10-08T13:37:04.128225+02:00 kiste sddm-helper[4338]: Adding cookie to "/home/jw/.Xauthority" 2019-10-08T13:37:04.152673+02:00 kiste sddm-helper[1893]: [PAM] Closing session 2019-10-08T13:37:04.154889+02:00 kiste sddm-helper: pam_unix(sddm-greeter:session): session closed for user sddm 2019-10-08T13:37:04.155579+02:00 kiste sddm-helper[1893]: [PAM] Ended. 2019-10-08T13:37:04.158717+02:00 kiste sddm[1632]: Auth: sddm-helper exited successfully 2019-10-08T13:37:04.159109+02:00 kiste sddm[1632]: Greeter stopped. 2019-10-08T13:37:04.160604+02:00 kiste systemd-logind[1269]: Session 1 logged out. Waiting for processes to exit. 2019-10-08T13:37:04.162505+02:00 kiste systemd-logind[1269]: Removed session 1. 2019-10-08T13:37:04.165246+02:00 kiste systemd[1]: Stopping User Manager for UID 466... 2019-10-08T13:37:04.166522+02:00 kiste systemd[1898]: Stopping D-Bus User Message Bus... 2019-10-08T13:37:04.166880+02:00 kiste systemd[1898]: Stopped target Default. 2019-10-08T13:37:04.172822+02:00 kiste systemd[1898]: Stopped D-Bus User Message Bus. 2019-10-08T13:37:04.173185+02:00 kiste systemd[1898]: Stopped target Basic System. 2019-10-08T13:37:04.173483+02:00 kiste systemd[1898]: Stopped target Sockets. 2019-10-08T13:37:04.173764+02:00 kiste systemd[1898]: Stopped target Paths. 2019-10-08T13:37:04.174451+02:00 kiste systemd[1898]: Stopped target Timers. 2019-10-08T13:37:04.174766+02:00 kiste systemd[1898]: Closed D-Bus User Message Bus Socket. 2019-10-08T13:37:04.175048+02:00 kiste systemd[1898]: Reached target Shutdown. 2019-10-08T13:37:04.175323+02:00 kiste systemd[1898]: Starting Exit the Session... 2019-10-08T13:37:04.178503+02:00 kiste systemd[1898]: Received SIGRTMIN+24 from PID 4340 (kill). 2019-10-08T13:37:04.183600+02:00 kiste sddm[1632]: Session started 2019-10-08T13:37:04.189959+02:00 kiste systemd[1]: Stopped User Manager for UID 466. 2019-10-08T13:37:04.190447+02:00 kiste systemd: pam_unix(systemd-user:session): session closed for user sddm 2019-10-08T13:37:04.191469+02:00 kiste systemd[1]: Removed slice User Slice of sddm. 2019-10-08T13:37:04.259126+02:00 kiste systemd[4329]: Started D-Bus User Message Bus. 2019-10-08T13:37:04.268671+02:00 kiste dbus-daemon[4348]: [session uid=1000 pid=4348] Successfully activated service 'org.freedesktop.systemd1' 2019-10-08T13:37:05.082697+02:00 kiste kapplymousetheme[4400]: kcm_input: Using X11 backend [ at this point the system hangs until I press the power button ] 2019-10-08T13:39:56.045936+02:00 kiste systemd-logind[1269]: Power key pressed. 2019-10-08T13:39:56.046381+02:00 kiste systemd-logind[1269]: Powering Off... 2019-10-08T13:39:56.046688+02:00 kiste systemd-logind[1269]: System is powering down. 2019-10-08T13:39:56.093007+02:00 kiste systemd[1]: Stopping Daemon for power management... 2019-10-08T13:39:56.093585+02:00 kiste avahi-daemon[1253]: Got SIGTERM, quitting. 2019-10-08T13:39:56.093888+02:00 kiste systemd[1]: Stopping Forward Password Requests to Plymouth... 2019-10-08T13:39:56.094143+02:00 kiste sshd[1493]: Received signal 15; terminating. 2019-10-08T13:39:56.094389+02:00 kiste systemd[1]: Stopped target Graphical Interface. 2019-10-08T13:39:56.094641+02:00 kiste avahi-daemon[1253]: Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::ca37:49b7:d23b:8919. 2019-10-08T13:39:56.095409+02:00 kiste systemd[1]: Stopping CUPS Scheduler... 2019-10-08T13:39:56.095672+02:00 kiste avahi-daemon[1253]: Leaving mDNS multicast group on interface eth0.IPv4 with address 10.116.41.67. 2019-10-08T13:39:56.095992+02:00 kiste systemd[1]: Stopped Detect if the system suffers from bsc#1089761. 2019-10-08T13:39:56.096245+02:00 kiste systemd[1]: Stopped Early Kernel Boot Messages. 2019-10-08T13:39:56.096501+02:00 kiste systemd[1]: Stopping X Display Manager... 2019-10-08T13:39:56.096748+02:00 kiste systemd[1]: Stopping Session 3 of user jw. 2019-10-08T13:39:56.096994+02:00 kiste systemd[1]: Stopped target Multi-User System. 2019-10-08T13:39:56.097245+02:00 kiste systemd[1]: Stopping Initializes zram swaping... 2019-10-08T13:39:56.097489+02:00 kiste systemd[1]: Stopping OpenSSH Daemon... (*) 2019-10-08T13:39:56.097749+02:00 kiste sddm[1632]: Authentication error: "Process crashed" (*) 2019-10-08T13:39:56.098069+02:00 kiste sddm[1632]: Auth: sddm-helper crashed (exit code 15) (*) 2019-10-08T13:39:56.098352+02:00 kiste sddm[1632]: Authentication error: "Process crashed" (*) 2019-10-08T13:39:56.098618+02:00 kiste sddm[1632]: Auth: sddm-helper exited with 15 2019-10-08T13:39:56.098895+02:00 kiste sddm[1632]: Socket server stopping... 2019-10-08T13:39:56.099151+02:00 kiste sddm[1632]: Socket server stopped. 2019-10-08T13:39:56.099408+02:00 kiste sddm[1632]: Display server stopping... 2019-10-08T13:39:56.099667+02:00 kiste systemd[1]: Stopping Avahi mDNS/DNS-SD Stack... 2019-10-08T13:39:56.103929+02:00 kiste systemd[1]: Stopping irqbalance daemon... 2019-10-08T13:39:56.104358+02:00 kiste systemd[1]: Stopped target Login Prompts. 2019-10-08T13:39:56.104700+02:00 kiste systemd[1]: Stopping Getty on tty1... 2019-10-08T13:39:56.105057+02:00 kiste systemd[1]: Stopping Machine Check Exception Logging Daemon... 2019-10-08T13:39:56.105556+02:00 kiste systemd[1]: Stopped Apply settings from /etc/sysconfig/keyboard. 2019-10-08T13:39:56.108897+02:00 kiste avahi-daemon[1253]: avahi-daemon 0.7 exiting. -- Josef Wolf jw(a)raven.inka.de -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 12

[opensuse] What on earth was this? I suddenly lost access to at least one hard disk.
by Carlos E. R. 13 Oct '19

13 Oct '19

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I was happily creating some directories and deleting others in mc, when suddenly the system wen bonkers. mc froze. I saw in the log that disk access was lost, so I halted, powered off and on, and booted. The first thing in the log is this: <10.6> 2019-10-11 20:40:01 Telcontar CRON 1584 - - pam_unix(crond:session): session closed for user cer <3.6> 2019-10-11 20:42:00 Telcontar dbus-daemon 4227 - - [session uid=1000 pid=4227] Activating service name='org.freedesktop.thumbnails.Cache1' requested by ':1.10' (uid=1000 pid=4307 comm="Thunar --sm-client-id 25b4ecb72-97b6-45d0-9e54-588") <1.6> 2019-10-11 20:42:00 Telcontar org.freedesktop.thumbnails.Cache1 4227 - - Registered thumbailer evince-thumbnailer -s %s %u %o <1.6> 2019-10-11 20:42:00 Telcontar org.freedesktop.thumbnails.Cache1 4227 - - Registered thumbailer /usr/bin/gdk-pixbuf-thumbnailer -s %s %u %o <1.6> 2019-10-11 20:42:00 Telcontar org.freedesktop.thumbnails.Cache1 4227 - - Registered thumbailer ffmpegthumbnailer -i %i -o %o -s %s -f <1.6> 2019-10-11 20:42:00 Telcontar org.freedesktop.thumbnails.Cache1 4227 - - Registered thumbailer gnome-thumbnail-font --size %s %u %o <1.6> 2019-10-11 20:42:00 Telcontar org.freedesktop.thumbnails.Cache1 4227 - - Registered thumbailer gsf-office-thumbnailer -i %i -o %o -s %s <1.6> 2019-10-11 20:42:00 Telcontar org.freedesktop.thumbnails.Cache1 4227 - - Registered thumbailer /usr/bin/totem-video-thumbnailer -s %s %u %o <1.6> 2019-10-11 20:42:00 Telcontar org.freedesktop.thumbnails.Cache1 4227 - - Registered thumbailer /usr/bin/gdk-pixbuf-thumbnailer -s %s %u %o <3.6> 2019-10-11 20:42:00 Telcontar dbus-daemon 4227 - - [session uid=1000 pid=4227] Successfully activated service 'org.freedesktop.thumbnails.Cache1' <0.3> 2019-10-11 20:45:36 Telcontar kernel - - - [260610.969175] ata10.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen <0.3> 2019-10-11 20:45:36 Telcontar kernel - - - [260610.969178] ata10.00: failed command: FLUSH CACHE EXT <0.3> 2019-10-11 20:45:36 Telcontar kernel - - - [260610.969183] ata10.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0 <0.3> 2019-10-11 20:45:36 Telcontar kernel - - - [260610.969183] res 40/00:82:82:00:00/00:00:00:00:00/50 Emask 0x4 (timeout) <0.3> 2019-10-11 20:45:36 Telcontar kernel - - - [260610.969185] ata10.00: status: { DRDY } <0.6> 2019-10-11 20:45:36 Telcontar kernel - - - [260610.969190] ata10.00: hard resetting link <0.6> 2019-10-11 20:45:37 Telcontar kernel - - - [260611.283231] ata10.01: hard resetting link <0.4> 2019-10-11 20:45:42 Telcontar kernel - - - [260616.801391] ata10.00: link is slow to respond, please be patient (ready=0) <0.3> 2019-10-11 20:45:46 Telcontar kernel - - - [260621.005555] ata10.00: SRST failed (errno=-16) <0.6> 2019-10-11 20:45:46 Telcontar kernel - - - [260621.005560] ata10.00: hard resetting link <0.6> 2019-10-11 20:45:47 Telcontar kernel - - - [260621.319641] ata10.01: hard resetting link <0.4> 2019-10-11 20:45:52 Telcontar kernel - - - [260626.833785] ata10.00: link is slow to respond, please be patient (ready=0) <0.3> 2019-10-11 20:45:56 Telcontar kernel - - - [260631.033951] ata10.00: SRST failed (errno=-16) <0.6> 2019-10-11 20:45:56 Telcontar kernel - - - [260631.033957] ata10.00: hard resetting link <0.6> 2019-10-11 20:45:57 Telcontar kernel - - - [260631.348027] ata10.01: hard resetting link <0.4> 2019-10-11 20:46:02 Telcontar kernel - - - [260636.858178] ata10.00: link is slow to respond, please be patient (ready=0) <0.3> 2019-10-11 20:46:31 Telcontar kernel - - - [260666.091332] ata10.00: SRST failed (errno=-16) <0.4> 2019-10-11 20:46:31 Telcontar kernel - - - [260666.091337] ata10.00: limiting SATA link speed to 1.5 Gbps <0.4> 2019-10-11 20:46:31 Telcontar kernel - - - [260666.091339] ata10.01: limiting SATA link speed to 1.5 Gbps <0.6> 2019-10-11 20:46:31 Telcontar kernel - - - [260666.091343] ata10.00: hard resetting link <0.6> 2019-10-11 20:46:32 Telcontar kernel - - - [260666.405373] ata10.01: hard resetting link <0.3> 2019-10-11 20:46:37 Telcontar kernel - - - [260671.139530] ata10.00: SRST failed (errno=-16) <0.3> 2019-10-11 20:46:37 Telcontar kernel - - - [260671.150081] ata10.00: reset failed, giving up <0.4> 2019-10-11 20:46:37 Telcontar kernel - - - [260671.150086] ata10.00: disabled <0.4> 2019-10-11 20:46:37 Telcontar kernel - - - [260671.150089] ata10.01: disabled <0.6> 2019-10-11 20:46:37 Telcontar kernel - - - [260671.150098] ata10: EH complete <0.6> 2019-10-11 20:46:37 Telcontar kernel - - - [260671.150117] sd 9:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK <0.6> 2019-10-11 20:46:37 Telcontar kernel - - - [260671.150121] sd 9:0:0:0: [sdc] tag#0 CDB: Synchronize Cache(10) 35 00 00 00 00 00 00 00 00 00 <0.3> 2019-10-11 20:46:37 Telcontar kernel - - - [260671.150130] print_req_error: I/O error, dev sdc, sector 2287414464 <0.6> 2019-10-11 20:46:37 Telcontar kernel - - - [260671.150140] sd 9:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK <0.6> 2019-10-11 20:46:37 Telcontar kernel - - - [260671.150143] sd 9:0:0:0: [sdc] tag#0 CDB: Synchronize Cache(10) 35 00 00 00 00 00 00 00 00 00 <0.3> 2019-10-11 20:46:37 Telcontar kernel - - - [260671.150144] print_req_error: I/O error, dev sdc, sector 7062330200 <0.3> 2019-10-11 20:46:37 Telcontar kernel - - - [260671.150148] print_req_error: I/O error, dev sdc, sector 7062330208 <0.1> 2019-10-11 20:46:37 Telcontar kernel - - - [260671.150169] XFS (sdc7): metadata I/O error: block 0x7a1e6cc0 ("xlog_iodone") error 5 numblks 64 <0.5> 2019-10-11 20:46:37 Telcontar kernel - - - [260671.150174] XFS (sdc7): xfs_do_force_shutdown(0x2) called from line 1263 of file ../fs/xfs/xfs_log.c. Return address = 0xffffffffa114de19 <0.6> 2019-10-11 20:46:37 Telcontar kernel - - - [260671.150176] sd 9:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK <0.6> 2019-10-11 20:46:37 Telcontar kernel - - - [260671.150180] sd 9:0:0:0: [sdc] tag#0 CDB: Write(16) 8a 00 00 00 00 00 06 8b 84 50 00 00 00 28 00 00 <0.3> 2019-10-11 20:46:37 Telcontar kernel - - - [260671.150183] print_req_error: I/O error, dev sdc, sector 109806672 <0.1> 2019-10-11 20:46:37 Telcontar kernel - - - [260671.150188] XFS (sdc7): Log I/O Error Detected. Shutting down filesystem <0.1> 2019-10-11 20:46:37 Telcontar kernel - - - [260671.150189] XFS (sdc7): Please umount the filesystem and rectify the problem(s) <0.1> 2019-10-11 20:46:37 Telcontar kernel - - - [260671.150192] XFS (sdc14): metadata I/O error: block 0x2cd1db58 ("xlog_iodone") error 5 numblks 64 <0.5> 2019-10-11 20:46:37 Telcontar kernel - - - [260671.150194] XFS (sdc14): xfs_do_force_shutdown(0x2) called from line 1263 of file ../fs/xfs/xfs_log.c. Return address = 0xffffffffa114de19 <0.1> 2019-10-11 20:46:37 Telcontar kernel - - - [260671.150216] XFS (sdc14): Log I/O Error Detected. Shutting down filesystem .... What was THAT? Telcontar:~ # smartctl --health /dev/sdc smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.12.14-lp151.28.16-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 Telcontar:~ # I just did a short test and it passed. Telcontar:~ # smartctl -x /dev/sdc smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.12.14-lp151.28.16-default] (SUSE RPM) Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Seagate Barracuda 3.5 Device Model: ST4000DM004-2CV104 Serial Number: ZFN0DBVK LU WWN Device Id: 5 000c50 0a46c652b Firmware Version: 0001 User Capacity: 4,000,787,030,016 bytes [4.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 5425 rpm Device is: In smartctl database [for details use: -P show] ATA Version is: ACS-3 T13/2161-D revision 5 SATA Version is: SATA 3.1, 6.0 Gb/s (current: 3.0 Gb/s) Local Time is: Fri Oct 11 21:06:17 2019 CEST SMART support is: Available - device has SMART capability. SMART support is: Enabled AAM feature is: Unavailable APM feature is: Unavailable Rd look-ahead is: Enabled Write cache is: Enabled DSN feature is: Unavailable ATA Security is: Disabled, frozen [SEC2] Wt Cache Reorder: Unavailable === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x82) Offline data collection activity was completed without error. Auto Offline Data Collection: Enabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 0) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 1) minutes. Extended self-test routine recommended polling time: ( 486) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x30a5) SCT Status supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate POSR-- 069 064 006 - 7467918 3 Spin_Up_Time PO---- 097 096 000 - 0 4 Start_Stop_Count -O--CK 100 100 020 - 506 5 Reallocated_Sector_Ct PO--CK 100 100 010 - 0 7 Seek_Error_Rate POSR-- 087 060 045 - 499325756 9 Power_On_Hours -O--CK 093 093 000 - 6672 (44 253 0) 10 Spin_Retry_Count PO--C- 100 100 097 - 0 12 Power_Cycle_Count -O--CK 100 100 020 - 504 183 Runtime_Bad_Block -O--CK 100 100 000 - 0 184 End-to-End_Error -O--CK 100 100 099 - 0 187 Reported_Uncorrect -O--CK 100 100 000 - 0 188 Command_Timeout -O--CK 100 100 000 - 0 0 0 189 High_Fly_Writes -O-RCK 100 100 000 - 0 190 Airflow_Temperature_Cel -O---K 067 061 040 - 33 (Min/Max 32/33) 191 G-Sense_Error_Rate -O--CK 100 100 000 - 0 192 Power-Off_Retract_Count -O--CK 100 100 000 - 167 193 Load_Cycle_Count -O--CK 100 100 000 - 691 194 Temperature_Celsius -O---K 033 040 000 - 33 (0 16 0 0 0) 195 Hardware_ECC_Recovered -O-RC- 069 064 000 - 7467918 197 Current_Pending_Sector -O--C- 100 100 000 - 0 198 Offline_Uncorrectable ----C- 100 100 000 - 0 199 UDMA_CRC_Error_Count -OSRCK 200 200 000 - 0 240 Head_Flying_Hours ------ 100 253 000 - 6643h+31m+22.338s 241 Total_LBAs_Written ------ 100 253 000 - 12846250365 242 Total_LBAs_Read ------ 100 253 000 - 25403895357 ||||||_ K auto-keep |||||__ C event count ||||___ R error rate |||____ S speed/performance ||_____ O updated online |______ P prefailure warning General Purpose Log Directory Version 1 SMART Log Directory Version 1 [multi-sector log support] Address Access R/W Size Description 0x00 GPL,SL R/O 1 Log Directory 0x01 SL R/O 1 Summary SMART error log 0x02 SL R/O 5 Comprehensive SMART error log 0x03 GPL R/O 5 Ext. Comprehensive SMART error log 0x04 GPL,SL R/O 8 Device Statistics log 0x06 SL R/O 1 SMART self-test log 0x07 GPL R/O 1 Extended self-test log 0x08 GPL R/O 2 Power Conditions log 0x09 SL R/W 1 Selective self-test log 0x0c GPL R/O 2048 Pending Defects log 0x10 GPL R/O 1 NCQ Command Error log 0x11 GPL R/O 1 SATA Phy Event Counters log 0x21 GPL R/O 1 Write stream error log 0x22 GPL R/O 1 Read stream error log 0x24 GPL R/O 512 Current Device Internal Status Data log 0x30 GPL,SL R/O 9 IDENTIFY DEVICE data log 0x80-0x9f GPL,SL R/W 16 Host vendor specific log 0xa1 GPL,SL VS 24 Device vendor specific log 0xa2 GPL VS 8160 Device vendor specific log 0xa6 GPL VS 192 Device vendor specific log 0xa8-0xa9 GPL,SL VS 136 Device vendor specific log 0xab GPL VS 1 Device vendor specific log 0xb0 GPL VS 9048 Device vendor specific log 0xbe-0xbf GPL VS 65535 Device vendor specific log 0xc0 GPL,SL VS 1 Device vendor specific log 0xc1 GPL,SL VS 16 Device vendor specific log 0xc3 GPL,SL VS 8 Device vendor specific log 0xc4 GPL,SL VS 24 Device vendor specific log 0xd1 GPL VS 264 Device vendor specific log 0xd3 GPL VS 1920 Device vendor specific log 0xe0 GPL,SL R/W 1 SCT Command/Status 0xe1 GPL,SL R/W 1 SCT Data Transfer SMART Extended Comprehensive Error Log Version: 1 (5 sectors) No Errors Logged SMART Extended Self-test Log Version: 1 (1 sectors) Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 6672 - # 2 Short offline Completed without error 00% 6654 - # 3 Short offline Completed without error 00% 6638 - # 4 Short offline Completed without error 00% 6622 - # 5 Short offline Completed without error 00% 6614 - # 6 Short offline Completed without error 00% 6600 - # 7 Extended offline Completed without error 00% 6598 - # 8 Short offline Completed without error 00% 6581 - # 9 Short offline Completed without error 00% 6574 - #10 Short offline Completed without error 00% 6569 - #11 Short offline Completed without error 00% 6563 - #12 Short offline Completed without error 00% 6546 - #13 Short offline Completed without error 00% 6522 - #14 Short offline Completed without error 00% 6502 - #15 Short offline Completed without error 00% 6487 - #16 Short offline Completed without error 00% 6482 - #17 Short offline Completed without error 00% 6471 - #18 Short offline Completed without error 00% 6465 - #19 Short offline Completed without error 00% 6463 - SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. SCT Status Version: 3 SCT Version (vendor specific): 522 (0x020a) SCT Support Level: 1 Device State: Active (0) Current Temperature: 33 Celsius Power Cycle Min/Max Temperature: 32/33 Celsius Lifetime Min/Max Temperature: 15/39 Celsius Under/Over Temperature Limit Count: 0/0 SCT Temperature History Version: 2 Temperature Sampling Period: 3 minutes Temperature Logging Interval: 59 minutes Min/Max recommended Temperature: 14/55 Celsius Min/Max Temperature Limit: 10/60 Celsius Temperature History Size (Index): 128 (119) Index Estimated Time Temperature Celsius 120 2019-10-06 15:33 33 ************** 121 2019-10-06 16:32 ? - 122 2019-10-06 17:31 26 ******* 123 2019-10-06 18:30 32 ************* ... ..( 2 skipped). .. ************* 126 2019-10-06 21:27 32 ************* 127 2019-10-06 22:26 ? - 0 2019-10-06 23:25 27 ******** 1 2019-10-07 00:24 33 ************** 2 2019-10-07 01:23 ? - 3 2019-10-07 02:22 26 ******* 4 2019-10-07 03:21 32 ************* ... ..( 3 skipped). .. ************* 8 2019-10-07 07:17 32 ************* 9 2019-10-07 08:16 ? - 10 2019-10-07 09:15 26 ******* 11 2019-10-07 10:14 32 ************* 12 2019-10-07 11:13 33 ************** 13 2019-10-07 12:12 33 ************** 14 2019-10-07 13:11 32 ************* 15 2019-10-07 14:10 32 ************* 16 2019-10-07 15:09 34 *************** 17 2019-10-07 16:08 ? - 18 2019-10-07 17:07 25 ****** 19 2019-10-07 18:06 33 ************** 20 2019-10-07 19:05 34 *************** 21 2019-10-07 20:04 33 ************** 22 2019-10-07 21:03 33 ************** 23 2019-10-07 22:02 34 *************** 24 2019-10-07 23:01 ? - 25 2019-10-08 00:00 26 ******* 26 2019-10-08 00:59 34 *************** 27 2019-10-08 01:58 34 *************** 28 2019-10-08 02:57 34 *************** 29 2019-10-08 03:56 33 ************** 30 2019-10-08 04:55 34 *************** ... ..( 5 skipped). .. *************** 36 2019-10-08 10:49 34 *************** 37 2019-10-08 11:48 33 ************** 38 2019-10-08 12:47 34 *************** 39 2019-10-08 13:46 ? - 40 2019-10-08 14:45 26 ******* 41 2019-10-08 15:44 32 ************* ... ..( 2 skipped). .. ************* 44 2019-10-08 18:41 32 ************* 45 2019-10-08 19:40 33 ************** 46 2019-10-08 20:39 32 ************* 47 2019-10-08 21:38 33 ************** 48 2019-10-08 22:37 33 ************** 49 2019-10-08 23:36 32 ************* 50 2019-10-09 00:35 32 ************* 51 2019-10-09 01:34 32 ************* 52 2019-10-09 02:33 33 ************** 53 2019-10-09 03:32 32 ************* 54 2019-10-09 04:31 32 ************* 55 2019-10-09 05:30 32 ************* 56 2019-10-09 06:29 ? - 57 2019-10-09 07:28 26 ******* 58 2019-10-09 08:27 32 ************* 59 2019-10-09 09:26 32 ************* 60 2019-10-09 10:25 33 ************** 61 2019-10-09 11:24 33 ************** 62 2019-10-09 12:23 33 ************** 63 2019-10-09 13:22 32 ************* 64 2019-10-09 14:21 33 ************** 65 2019-10-09 15:20 ? - 66 2019-10-09 16:19 26 ******* 67 2019-10-09 17:18 32 ************* ... ..( 3 skipped). .. ************* 71 2019-10-09 21:14 32 ************* 72 2019-10-09 22:13 33 ************** 73 2019-10-09 23:12 32 ************* ... ..( 2 skipped). .. ************* 76 2019-10-10 02:09 32 ************* 77 2019-10-10 03:08 30 *********** 78 2019-10-10 04:07 32 ************* ... ..( 3 skipped). .. ************* 82 2019-10-10 08:03 32 ************* 83 2019-10-10 09:02 ? - 84 2019-10-10 10:01 26 ******* 85 2019-10-10 11:00 32 ************* ... ..( 2 skipped). .. ************* 88 2019-10-10 13:57 32 ************* 89 2019-10-10 14:56 33 ************** 90 2019-10-10 15:55 33 ************** 91 2019-10-10 16:54 32 ************* 92 2019-10-10 17:53 31 ************ 93 2019-10-10 18:52 33 ************** 94 2019-10-10 19:51 32 ************* ... ..( 9 skipped). .. ************* 104 2019-10-11 05:41 32 ************* 105 2019-10-11 06:40 31 ************ 106 2019-10-11 07:39 32 ************* ... ..( 10 skipped). .. ************* 117 2019-10-11 18:28 32 ************* 118 2019-10-11 19:27 ? - 119 2019-10-11 20:26 32 ************* SCT Error Recovery Control command not supported Device Statistics (GP Log 0x04) Page Offset Size Value Flags Description 0x01 ===== = = === == General Statistics (rev 1) == 0x01 0x008 4 504 --- Lifetime Power-On Resets 0x01 0x010 4 6672 --- Power-on Hours 0x01 0x018 6 12845698977 --- Logical Sectors Written 0x01 0x020 6 112072766 --- Number of Write Commands 0x01 0x028 6 25400659571 --- Logical Sectors Read 0x01 0x030 6 244896730 --- Number of Read Commands 0x01 0x038 6 - --- Date and Time TimeStamp 0x03 ===== = = === == Rotating Media Statistics (rev 1) == 0x03 0x008 4 2337654761 N-- Spindle Motor Power-on Hours 0x03 0x010 4 2337652683 N-- Head Flying Hours 0x03 0x018 4 691 --- Head Load Events 0x03 0x020 4 0 --- Number of Reallocated Logical Sectors 0x03 0x028 4 0 --- Read Recovery Attempts 0x03 0x030 4 0 --- Number of Mechanical Start Failures 0x03 0x038 4 0 --- Number of Realloc. Candidate Logical Sectors 0x03 0x040 4 167 --- Number of High Priority Unload Events 0x04 ===== = = === == General Errors Statistics (rev 1) == 0x04 0x008 4 1 --- Number of Reported Uncorrectable Errors 0x04 0x010 4 0 --- Resets Between Cmd Acceptance and Completion 0x05 ===== = = === == Temperature Statistics (rev 1) == 0x05 0x008 1 33 --- Current Temperature 0x05 0x010 1 32 --- Average Short Term Temperature 0x05 0x018 1 31 --- Average Long Term Temperature 0x05 0x020 1 39 --- Highest Temperature 0x05 0x028 1 0 --- Lowest Temperature 0x05 0x030 1 37 --- Highest Average Short Term Temperature 0x05 0x038 1 23 --- Lowest Average Short Term Temperature 0x05 0x040 1 34 --- Highest Average Long Term Temperature 0x05 0x048 1 24 --- Lowest Average Long Term Temperature 0x05 0x050 4 0 --- Time in Over-Temperature 0x05 0x058 1 55 --- Specified Maximum Operating Temperature 0x05 0x060 4 190 --- Time in Under-Temperature 0x05 0x068 1 13 --- Specified Minimum Operating Temperature 0x06 ===== = = === == Transport Statistics (rev 1) == 0x06 0x008 4 1577 --- Number of Hardware Resets 0x06 0x010 4 61 --- Number of ASR Events 0x06 0x018 4 0 --- Number of Interface CRC Errors |||_ C monitored condition met ||__ D supports DSN |___ N normalized value Pending Defects log (GP Log 0x0c) supported [please try: '-l defects'] SATA Phy Event Counters (GP Log 0x11) ID Size Value Description 0x000a 2 2 Device-to-host register FISes sent due to a COMRESET 0x0001 2 0 Command failed due to ICRC error 0x0003 2 0 R_ERR response for device-to-host data FIS 0x0004 2 0 R_ERR response for host-to-device data FIS 0x0006 2 0 R_ERR response for device-to-host non-data FIS 0x0007 2 0 R_ERR response for host-to-device non-data FIS Telcontar:~ # - -- Cheers Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXaDTHRwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVp4kAnj2yjbEoIPTlxPjv37jV nj0NzBvNAJ4+LNeIiP2t2KoIYWXfgrIAcGWNww== =XHaa -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 5

[opensuse] google gmail changed IMAP to retain all of your email, regardless of IMAP settings.
by L A Walsh 13 Oct '19

13 Oct '19

I noticed some people having probs with gmail back in September, and I noticed a problem with gmail that I couldn't ignore and still haven't solved. Sometime last spring google changed their IMAPS service to no longer follow the IMAP specification. In IMAP, all email is normally routed to a fixed name 'Inbox' or 'INBOX'. They changed their IMAP service to put all email under a label called 'All Mail' that is not displayed, by default. IMAP users who previously turned off SPAM filtering had it turned back on with the IMAP 'INBOX' getting the remainder of the mail. When I checked my account, I found about 440 emails in the Junk/SPAM folder that were only emails from the past 30 days. Email in the Spam folder, is auto-deleted after 30 days. The above default to putting email in 'All Mail' happens even though the IMAP settings are set to have it deleted: ------This is from the control pannel for IMAP and POP access---- Status: IMAP is enabled x Enable IMAP Disable IMAP When I mark a message in IMAP as deleted: Auto-Expunge on - Immediately update the server. (default) x Auto-Expunge off - Wait for the client to update the server. When a message is marked as deleted and expunged from the last visible IMAP folder: Archive the message (default) Move the message to the Trash x Immediately delete the message forever -------------------------------------------------- Turns out I am now using about 1.8GB out of my allotment. I'm still engaging with their 3rd party support people -- google no longer handles customer support for gmail, but routes emails and calls to a 3rd party support organization that knows nothing about google's technical setup. Example of instructions for proceeding further in trying to escalate this: ======= Having addressed that we can now focus on the main issue "why IMAP settings are not being followed". To begin looking into this reported error I will need the following information. 1) Disconnect your account from IMAP and re-add. If the issue persist, please obtain the next pieces of information. 2) Screenshot of the IMAP settings claimed not working as intended 3) Screenshot of your IMAP configuration 4) Expected behavior 5) Actual behavior ======== Copying and pasting the settings wasn't something they could deal with. They responded: ============== Copying and pasting the setting configuration is not necessarily the same. I actually do not understand all of the text sent together as it appears everything is just joined together. Once again the following screenshot will allow us to determine why the messages are not being deleted from Google's side. 1) Log into Gmail.com 2) Go to Settings > Forwarding and POP/IMAP 3) Full Page Screenshot showing computer Time Stamp We will be awaiting your response with this so that we may continue to review your request. -------------- What computer time stamp? They don't have access to the gmail setup pages we are presented with. Anyway, if you thought you were not keeping your email on gmail -- you might want to check. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

7 10

[opensuse] Hundreds of coredumps related to tracker in oS 15.1
by Carlos E. R. 12 Oct '19

12 Oct '19

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I just upgraded to 15.1 (using zypper dup) As soon as I log in, I see in the log: <3.6> 2019-10-12 02:52:28 Telcontar dbus-daemon 5093 - - [session uid=1000 pid=5093] Activating via systemd: service name='org.gnome.zeitgeist.SimpleIndexer' unit='zeitgeist-fts.service' requested by ':1.155' (uid=1000 pid=19516 comm="/usr/bin/zeitgeist-daemon ") <3.6> 2019-10-12 02:52:28 Telcontar dbus-daemon 5093 - - [session uid=1000 pid=5093] Successfully activated service 'org.gnome.zeitgeist.Engine' <10.5> 2019-10-12 02:52:28 Telcontar polkitd 15858 - - Registered Authentication Agent for unix-session:40 (system bus name :1.44 [/usr/lib/polkit-gnome-authentication-agent-1], object path /org/gnome/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) <3.6> 2019-10-12 02:52:29 Telcontar dbus-daemon 5093 - - [session uid=1000 pid=5093] Successfully activated service 'org.gnome.zeitgeist.SimpleIndexer' <1.4> 2019-10-12 02:52:29 Telcontar zeitgeist-datah 19524 - - zeitgeist-datahub.vala:224: Unable to get name "org.gnome.zeitgeist.datahub" on the bus! <3.6> 2019-10-12 02:52:29 Telcontar dbus-daemon 5093 - - [session uid=1000 pid=5093] Successfully activated service 'org.freedesktop.thumbnails.Thumbnailer1' <1.4> 2019-10-12 02:52:31 Telcontar baloo_file 19612 - - Failed to register via dbus. Another instance is running <1.7> 2019-10-12 02:52:31 Telcontar drkonqi 19613 - - found lsb_release <1.7> 2019-10-12 02:52:31 Telcontar drkonqi 19613 - - Using /proc to determine executable path <1.7> 2019-10-12 02:52:31 Telcontar drkonqi 19613 - - Executable is: "/usr/bin/baloo_file" <1.7> 2019-10-12 02:52:31 Telcontar drkonqi 19613 - - Executable exists: true <1.7> 2019-10-12 02:52:31 Telcontar drkonqi 19613 - - Enabling drkonqi crash catching <1.4> 2019-10-12 02:52:31 Telcontar drkonqi 19613 - - QSystemTrayIcon::setVisible: No Icon set <3.6> 2019-10-12 02:52:32 Telcontar systemd 1 - - Started Process Core Dump (PID 19641/UID 0). <3.6> 2019-10-12 02:52:32 Telcontar systemd-coredump 19642 - - Removed old coredump core.single.1000.e88569c50cca448b961ddc5a0d233692.10798.1570835353000000.lz4. <3.6> 2019-10-12 02:52:32 Telcontar systemd 1 - - Started Process Core Dump (PID 19645/UID 0). <1.2> 2019-10-12 02:52:33 Telcontar systemd-coredump 19642 - - Process 19640 (single) of user 1000 dumped core. <1.7> 2019-10-12 02:52:33 Telcontar drkonqi 19613 - - Sending SIGSTOP to process <3.6> 2019-10-12 02:52:33 Telcontar systemd 1 - - Started Process Core Dump (PID 19652/UID 0). <1.2> 2019-10-12 02:52:34 Telcontar systemd-coredump 19646 - - Process 19644 (single) of user 1000 dumped core. <3.6> 2019-10-12 02:52:34 Telcontar systemd 1 - - Started Process Core Dump (PID 19659/UID 0). <1.2> 2019-10-12 02:52:34 Telcontar systemd-coredump 19653 - - Process 19651 (single) of user 1000 dumped core. <3.6> 2019-10-12 02:52:34 Telcontar systemd 1 - - Started Process Core Dump (PID 19666/UID 0). <3.6> 2019-10-12 02:52:34 Telcontar systemd-coredump 19667 - - Removed old coredump core.single.1000.e88569c50cca448b961ddc5a0d233692.10809.1570835354000000.lz4. <1.2> 2019-10-12 02:52:35 Telcontar systemd-coredump 19660 - - Process 19658 (single) of user 1000 dumped core. <3.6> 2019-10-12 02:52:35 Telcontar systemd 1 - - Started Process Core Dump (PID 19676/UID 0). <1.2> 2019-10-12 02:52:35 Telcontar systemd-coredump 19667 - - Process 19665 (single) of user 1000 dumped core. <3.6> 2019-10-12 02:52:35 Telcontar systemd 1 - - Started Process Core Dump (PID 19683/UID 0). <1.2> 2019-10-12 02:52:36 Telcontar systemd-coredump 19677 - - Process 19675 (single) of user 1000 dumped core. <3.6> 2019-10-12 02:52:36 Telcontar systemd 1 - - Started Process Core Dump (PID 19690/UID 0). <1.2> 2019-10-12 02:52:36 Telcontar systemd-coredump 19684 - - Process 19682 (single) of user 1000 dumped core. <3.6> 2019-10-12 02:52:36 Telcontar systemd 1 - - Started Process Core Dump (PID 19697/UID 0). <3.6> 2019-10-12 02:52:36 Telcontar systemd-coredump 19698 - - Removed old coredump core.single.1000.e88569c50cca448b961ddc5a0d233692.10818.1570835355000000.lz4. <1.2> 2019-10-12 02:52:36 Telcontar systemd-coredump 19691 - - Process 19689 (single) of user 1000 dumped core. <3.6> 2019-10-12 02:52:37 Telcontar systemd 1 - - Started Process Core Dump (PID 19704/UID 0). <1.2> 2019-10-12 02:52:37 Telcontar systemd-coredump 19698 - - Process 19696 (single) of user 1000 dumped core. <3.6> 2019-10-12 02:52:37 Telcontar systemd 1 - - Started Process Core Dump (PID 19711/UID 0). <1.2> 2019-10-12 02:52:38 Telcontar systemd-coredump 19705 - - Process 19703 (single) of user 1000 dumped core. <3.6> 2019-10-12 02:52:38 Telcontar systemd 1 - - Started Process Core Dump (PID 19718/UID 0). <1.2> 2019-10-12 02:52:39 Telcontar systemd-coredump 19712 - - Process 19710 (single) of user 1000 dumped core. <3.6> 2019-10-12 02:52:39 Telcontar systemd 1 - - Started Process Core Dump (PID 19725/UID 0). <1.2> 2019-10-12 02:52:39 Telcontar systemd-coredump 19719 - - Process 19717 (single) of user 1000 dumped core. <3.6> 2019-10-12 02:52:40 Telcontar systemd 1 - - Started Process Core Dump (PID 19732/UID 0). <3.6> 2019-10-12 02:52:40 Telcontar systemd-coredump 19733 - - Removed old coredump core.single.1000.e88569c50cca448b961ddc5a0d233692.10825.1570835357000000.lz4. <1.2> 2019-10-12 02:52:40 Telcontar systemd-coredump 19726 - - Process 19724 (single) of user 1000 dumped core. <3.6> 2019-10-12 02:52:40 Telcontar systemd 1 - - Started Process Core Dump (PID 19741/UID 0). <1.2> 2019-10-12 02:52:40 Telcontar systemd-coredump 19733 - - Process 19731 (single) of user 1000 dumped core. <3.6> 2019-10-12 02:52:41 Telcontar systemd 1 - - Started Process Core Dump (PID 19748/UID 0). Telcontar:~ # coredumpctl TIME PID UID GID SIG COREFILE EXE Sat 2019-10-12 00:58:44 CEST 6315 1000 100 31 missing /usr/lib/tracker-extract Sat 2019-10-12 00:58:45 CEST 6319 1000 100 31 missing /usr/lib/tracker-extract Sat 2019-10-12 00:58:45 CEST 6326 1000 100 31 missing /usr/lib/tracker-extract Sat 2019-10-12 00:58:45 CEST 6335 1000 100 31 missing /usr/lib/tracker-extract Sat 2019-10-12 00:58:46 CEST 6342 1000 100 31 missing /usr/lib/tracker-extract Sat 2019-10-12 00:58:46 CEST 6349 1000 100 31 missing /usr/lib/tracker-extract Sat 2019-10-12 00:58:47 CEST 6356 1000 100 31 missing /usr/lib/tracker-extract Sat 2019-10-12 00:58:47 CEST 6363 1000 100 31 missing /usr/lib/tracker-extract Sat 2019-10-12 00:58:48 CEST 6370 1000 100 31 missing /usr/lib/tracker-extract Sat 2019-10-12 00:58:48 CEST 6377 1000 100 31 missing /usr/lib/tracker-extract Sat 2019-10-12 00:58:48 CEST 6384 1000 100 31 missing /usr/lib/tracker-extract Sat 2019-10-12 00:58:49 CEST 6392 1000 100 31 missing /usr/lib/tracker-extract Sat 2019-10-12 00:58:49 CEST 6399 1000 100 31 missing /usr/lib/tracker-extract Sat 2019-10-12 00:58:50 CEST 6406 1000 100 31 missing /usr/lib/tracker-extract Sat 2019-10-12 00:58:50 CEST 6413 1000 100 31 missing /usr/lib/tracker-extract Sat 2019-10-12 00:58:51 CEST 6422 1000 100 31 missing /usr/lib/tracker-extract Sat 2019-10-12 00:58:51 CEST 6429 1000 100 31 missing /usr/lib/tracker-extract Sat 2019-10-12 00:58:51 CEST 6436 1000 100 31 missing /usr/lib/tracker-extract Sat 2019-10-12 00:58:52 CEST 6443 1000 100 31 missing /usr/lib/tracker-extract Sat 2019-10-12 00:58:52 CEST 6452 1000 100 31 missing /usr/lib/tracker-extract Sat 2019-10-12 00:58:53 CEST 6461 1000 100 31 missing /usr/lib/tracker-extract Sat 2019-10-12 00:58:53 CEST 6468 1000 100 31 missing /usr/lib/tracker-extract ...skipping... Sat 2019-10-12 02:52:57 CEST 20031 1000 100 31 present /usr/lib/tracker-extract Sat 2019-10-12 02:52:57 CEST 20038 1000 100 31 present /usr/lib/tracker-extract Sat 2019-10-12 02:52:58 CEST 20045 1000 100 31 present /usr/lib/tracker-extract Sat 2019-10-12 02:52:58 CEST 20052 1000 100 31 present /usr/lib/tracker-extract Sat 2019-10-12 02:52:59 CEST 20059 1000 100 31 present /usr/lib/tracker-extract Sat 2019-10-12 02:52:59 CEST 20066 1000 100 31 present /usr/lib/tracker-extract Sat 2019-10-12 02:53:00 CEST 20073 1000 100 31 present /usr/lib/tracker-extract Sat 2019-10-12 02:53:00 CEST 20080 1000 100 31 present /usr/lib/tracker-extract Sat 2019-10-12 02:53:01 CEST 20089 1000 100 31 present /usr/lib/tracker-extract Sat 2019-10-12 02:53:01 CEST 20096 1000 100 31 present /usr/lib/tracker-extract Sat 2019-10-12 02:53:02 CEST 20103 1000 100 31 present /usr/lib/tracker-extract Sat 2019-10-12 02:53:02 CEST 20110 1000 100 31 present /usr/lib/tracker-extract Sat 2019-10-12 02:53:03 CEST 20117 1000 100 31 present /usr/lib/tracker-extract Sat 2019-10-12 02:53:03 CEST 20124 1000 100 31 present /usr/lib/tracker-extract Sat 2019-10-12 02:53:04 CEST 20131 1000 100 31 present /usr/lib/tracker-extract Sat 2019-10-12 02:53:04 CEST 20138 1000 100 31 present /usr/lib/tracker-extract Sat 2019-10-12 02:53:05 CEST 20145 1000 100 31 present /usr/lib/tracker-extract Sat 2019-10-12 02:53:05 CEST 20152 1000 100 31 present /usr/lib/tracker-extract Sat 2019-10-12 02:53:06 CEST 20161 1000 100 31 present /usr/lib/tracker-extract Sat 2019-10-12 02:53:06 CEST 20168 1000 100 31 present /usr/lib/tracker-extract Sat 2019-10-12 02:53:07 CEST 20175 1000 100 31 present /usr/lib/tracker-extract Sat 2019-10-12 02:53:07 CEST 20182 1000 100 31 present /usr/lib/tracker-extract Sat 2019-10-12 02:53:32 CEST 19481 1000 100 11 present /usr/bin/baloo_file Telcontar:~ # To stop it, I have to: killall tracker-store tracker-extract tracker-miner-apps tracker-miner-fs which works till next login. Telcontar:~ # coredumpctl info 20182 19481 PID: 20182 (single) UID: 1000 (cer) GID: 100 (users) Signal: 31 (SYS) Timestamp: Sat 2019-10-12 02:53:07 CEST (9min ago) Command Line: /usr/lib/tracker-extract Executable: /usr/lib/tracker-extract Control Group: /user.slice/user-1000.slice/session-40.scope Unit: session-40.scope Slice: user-1000.slice Session: 40 Owner UID: 1000 (cer) Boot ID: e88569c50cca448b961ddc5a0d233692 Machine ID: 2ce1d54548517a7307c1c2bc38206d00 Hostname: Telcontar Storage: /var/lib/systemd/coredump/core.single.1000.e88569c50cca448b961ddc5a0d233692.20182.1570841587000000.lz4 Message: Process 20182 (single) of user 1000 dumped core. PID: 19481 (baloo_file) UID: 1000 (cer) GID: 100 (users) Signal: 11 (SEGV) Timestamp: Sat 2019-10-12 02:53:32 CEST (9min ago) Command Line: baloo_file Executable: /usr/bin/baloo_file Control Group: /user.slice/user-1000.slice/session-40.scope Unit: session-40.scope Slice: user-1000.slice Session: 40 Owner UID: 1000 (cer) Boot ID: e88569c50cca448b961ddc5a0d233692 Machine ID: 2ce1d54548517a7307c1c2bc38206d00 Hostname: Telcontar Storage: /var/lib/systemd/coredump/core.baloo_file.1000.e88569c50cca448b961ddc5a0d233692.19481.1570841612000000.lz4 Message: Process 19481 (baloo_file) of user 1000 dumped core. Telcontar:~ # Ideas to stop this and get tracker to work properly without this madness? Bugzilla? - -- Cheers Carlos E. R. (from 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXaEm/Rwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVZy0An06LbygIT0rTVB6iS+Ts bvLC5bT2AJ4kKZDL4tOAqUDUshaTJank80gItw== =za/8 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] distribution upgrade sed problem
by Carlos E. R. 11 Oct '19

11 Oct '19

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, on <https://en.opensuse.org/SDB:System_upgrade> it says: The following command modifies all repos from the old to the new. Modify "15.0" if your current system is not 15.0: # sed -i 's/15.0/15.1/g' /etc/zypp/repos.d/* Well, it does not work for me: Telcontar:/etc/zypp/repos.d # sed -i 's/15.0/15.1/g' /etc/zypp/repos.d/* sed: couldn't edit /etc/zypp/repos.d/ANTIGUOS_REPOS: not a regular file Telcontar:/etc/zypp/repos.d # Yes, certainly I do have directories in that path. How do I change that sed command to work ignoring directories in there? I confess that sed syntax overloads my mind, so I need help. Meanwhile, I'm editing all those files by hand, one by one. - -- Cheers Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXaDKlhwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVO44An0n+FJZ11J3IzjcHzcJM XmVzTIUqAJ9+zSC20b0pBTtEP0EFUTI2Ja91Kw== =jnIq -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 4

[opensuse] Leap 15.0 - touchpad on Thinkpad P50 not working since Kernel 4.12.14-lp150.12.73
by Boris Gaensicke 11 Oct '19

11 Oct '19

Hi, I am running Opensuse Leap 15.0 on a Lenovo Thinkpad P50 with XFCE 4 as window manager. After the last two kernel updates (4.12.14-lp150.12.73 / 76) the touchpad is not working any longer. The touchpad is still recognised (Synaptics TM3149-002), and actived in the XFCE settings, but simply does not work. A mouse plugged into the USB port or docking station works fine. Booting back into 4.12.14-lp150.12.70 the touchpad still works fine. Boris -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

[opensuse] Kudos to opensuse for designing a ballot that uses no js except from opensuse.org
by David C. Rankin 10 Oct '19

10 Oct '19

opensuse webmins, Very good job on the name-change ballot. For the very first time in one of these web based schemes, I didn't have to fight with NoScript to let a lot of nasty sites run javascript on my box just to click a few buttons. Kudos to you! -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Spell check not working right in 15.0 Thunderbird
by Carlos E. R. 08 Oct '19

08 Oct '19

I have an email with quoted material, with all the quoted text underlined in red, while the normal text works. I change the language from English to Spanish and reverse, no change. > I have an email with quoted material, with all the quoted text underlined in red. After I start this post, Thunderbird behaves correctly on the old and new mail. I applied an update today. 68.1.1 (64-bit) -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)

3 3

[opensuse] leap 15.1 nfs server
by Mark Hounschell 08 Oct '19

08 Oct '19

Just upgraded a box from 15.0 to 15.1 and all seems to work except the nfs server. Checked the config via yast and all looks normal. The nfsserver.service starts. # systemctl status nfs-server ● nfs-server.service - NFS server and services Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; enabled; vendor preset: disabled) Drop-In: /usr/lib/systemd/system/nfs-server.service.d └─nfsserver.conf, options.conf /run/systemd/generator/nfs-server.service.d └─order-with-mounts.conf Active: active (exited) since Sat 2019-10-05 09:59:13 EDT; 39s ago Process: 2837 ExecStart=/usr/sbin/rpc.nfsd $NFSD_OPTIONS (code=exited, status=0/SUCCESS) Main PID: 2837 (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 4915) CGroup: /system.slice/nfs-server.service Oct 05 09:59:12 harley systemd[1]: Starting NFS server and services... Oct 05 09:59:13 harley systemd[1]: Started NFS server and services. I made no configuration changes. Neither of the leap-15.0 boxes are now able to mount the exports of the leap-15.1 system. Are there any known issues? Regards Mark -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

6 7

[opensuse] Firefox ESR
by Frans de Boer 08 Oct '19

08 Oct '19

LS, I was unpleasantly surprised today after applying the latest updates to 15.1. I normally share the .mozilla directory between TW and 15.1. Now Firefox under 15.1 start wining and does not let me use the data, add-ons etc in my common .mozilla directory. No, I have to make a whole new profile, which I need to maintain also. Double the effort for the same functionality. Many packages on 15.1 are already (very) old, but at least it is slightly more stable then TW. So that's my production environment. TW is used for other purposes. But now it takes extra the effort for syncing both .mozilla directories. What's next, same with Thunderbird? --- Frans. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 13

[opensuse] tumbleweed update - firewalld blocking qemu-guests
by Simon Becherer 08 Oct '19

08 Oct '19

Hi, updated tumbleweed from: 20190607 -> 20191002 i have a bridge network for qemu. using virt-manager for virtualization. before update my guests where inside my home-network accessible with ssh from all computers. after the update only the host computer could ssh to the guests. no other computer from network will work: ssh: connect to host visume port 22: No route to host ping is working. when i stop firewalld at the host, all computers from network are able to connect to the virtual computers. the bridge has open ssh ports what has changed? i do not see anithing. (i am not expert with firewalld, i use yast firewall) is there somewhere a config file where some standarts have changed? simoN -- www.becherer.de -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 3

[opensuse] gnome scrollbars
by Dave Howorth 08 Oct '19

08 Oct '19

I've finally become annoyed enough with the gnome scrollbars to want to fix them. (the ones that are almost invisible and only become visible when you mouse over them). I've found https://www.linuxuprising.com/2019/09/how-to-disable-gnomes-overlay.html and determined that I don't have the 'overlay-scrolling' setting in dconf-editor, so presumably have an older version of gnome. I don't know how to find out what version of gnome I'm running, or even whether the question makes sense. There are various how-tos online that don't work on my system. I use an LXDE desktop and various programs of all ilks as my mood takes me. YaST shows me various different version numbers for various gnome-* packages, but the latest seems to be 3.26. Is there a concept of a single gnome version and how can I find it? Anyway I tried GTK_OVERLAY_SCROLLING=0 gedit and that worked so I've added export GTK_OVERLAY_SCROLLING=0 gdbus call --session --dest org.freedesktop.DBus --object-path /org/freedesktop/DBus --method org.freedesktop.DBus.UpdateActivationEnvironment '{"GTK_OVERLAY_SCROLLING": "0"}' to ~/.profile and that works. The I decided to make it the default for the whole system so I went to add it to /etc/environment. But that file just contains: # # This file is parsed by pam_env module # # Syntax: simple "KEY=VAL" pairs on seperate lines # which apart from the spelling error, just seems to indicate that it's not a good place to put a shell script fragment. So is the comment correct, or is the file actually interpreted by a shell at some point? And if the comment is correct, what's the correct place to put the gnome setting for its scrollbars to make it global? Cheers, Dave -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

Re: [opensuse] Backup Failed
by Carlos E.R. 07 Oct '19

07 Oct '19

Please remember to post to the mail list, not in private. If I don't see the post or don't know the answer, you are stuck, while other listers may know the answer. > On 05/10/2019 21:10, Carlos E. R. wrote: >> On 05/10/2019 22.05, Paul Groves wrote: >>> My backup failed last night. I have three files which failed with >>> tar error Cannot stat: Bad message >>> >>> I tried opening the files and the cannot open with bad message error >>> I also checked the permissions which shows a load of question marks >>> instead of the rwx flags >>> >>> What does this error mean and how can I fix it? >> >> umount and fsck the partition On 07/10/2019 17.32, Paul Groves wrote: > It is the root partition of a live server. Is there a way I can do this > on this system while it is up? Quick answer is "no". But sometimes you might. If it is the /home partition or other data partition, you could umount it while live. If it is the "/" or root partition, then no; you must reboot, and my preference is to reboot to another partition or to a live system on USB. Note: if the root filesystem is btrfs I can hardly help with a detailed recovery procedure; I mean, if you hit further problems with the fsck itself. I confess my ignorance on btrfs. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)

1 0

[opensuse] I lost several addons with the last Thunderbird update on 15.0
by Carlos E. R. 07 Oct '19

07 Oct '19

I did not see a warning of this. I lost "Check and Send", "Remove duplicate Messages (Alternate)" and "Toggle Word Wrap" The last one I used daily. :-( -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)

4 9

[opensuse] tumbleweed - update wifi will not start
by Simon Becherer 07 Oct '19

07 Oct '19

Hi, updated tumbleweed from: 20190607 -> 20191002 the wireless network adapter "wlp2s0" did not start automatically as before. starting by hand will work. how to find the problem??? situation: managed by wicked, over a bonding device. so if unplug from cable the wireless will jump in. was working before. after update i got: wicked ifstatus all lo up link: #1, state up type: loopback config: compat:suse:/etc/sysconfig/network/ifcfg-lo leases: ipv4 static granted addr: ipv4 127.0.0.1/8 [static] enp3s0 enslaved link: #2, state device-up, mtu 1500, master bond0 type: ethernet, hwaddr xx:xx:xx:xx:xx:xx config: compat:suse:/etc/sysconfig/network/ifcfg-enp3s0 wlp2s0 device-not-running link: #3, state down, mtu 1500 type: wireless config: compat:suse:/etc/sysconfig/network/ifcfg-wlp2s0 bond0 setup-in-progress link: #4, state device-up, mtu 1500 type: bond, mode active-backup, hwaddr xx:xx:xx:xx:xx:xx config: compat:suse:/etc/sysconfig/network/ifcfg-bond0 then start by hand: wicked ifup wlp2s0 wlp2s0 enslaved wicked ifstatus all lo up link: #1, state up type: loopback config: compat:suse:/etc/sysconfig/network/ifcfg-lo leases: ipv4 static granted addr: ipv4 127.0.0.1/8 [static] enp3s0 enslaved link: #2, state device-up, mtu 1500, master bond0 type: ethernet, hwaddr xx:xx:xx:xx:xx:xx config: compat:suse:/etc/sysconfig/network/ifcfg-enp3s0 wlp2s0 enslaved link: #3, state up, mtu 1500, master bond0 type: wireless config: compat:suse:/etc/sysconfig/network/ifcfg-wlp2s0 bond0 up link: #4, state up, mtu 1500 type: bond, mode active-backup, hwaddr xx:xx:xx:xx:xx:xx config: compat:suse:/etc/sysconfig/network/ifcfg-bond0 leases: ipv4 static granted addr: ipv4 192.168.0.23/24 [static] route: ipv4 default via 192.168.0.99 proto boot ============================== some logs with the error: Okt 06 20:51:43 becherer7 systemd[1]: Starting wicked AutoIPv4 supplicant service... Okt 06 20:51:43 becherer7 systemd[1]: Starting wicked DHCPv6 supplicant service... Okt 06 20:51:43 becherer7 systemd[1]: Starting wicked DHCPv4 supplicant service... Okt 06 20:51:43 becherer7 systemd[1]: Started wicked AutoIPv4 supplicant service. Okt 06 20:51:43 becherer7 systemd[1]: Started wicked DHCPv6 supplicant service. Okt 06 20:51:43 becherer7 systemd[1]: Started wicked DHCPv4 supplicant service. Okt 06 20:51:44 becherer7 systemd[1]: Starting wicked network management service daemon... Okt 06 20:51:44 becherer7 systemd[1]: Started wicked network management service daemon. Okt 06 20:51:44 becherer7 systemd[1]: Starting wicked network nanny service... Okt 06 20:51:44 becherer7 systemd[1]: Started wicked network nanny service. Okt 06 20:51:44 becherer7 systemd[1]: Starting wicked managed network interfaces... Okt 06 20:51:44 becherer7 dbus-daemon[1237]: [system] Activating via systemd: service name='fi.epitest.hostap.WPASupplicant' unit='wpa_supplicant.service' requested by ':1.14' (uid=0 pid=1388 comm="/usr/sbin/wickedd --systemd --foreground ") Okt 06 20:52:09 becherer7 wickedd[1388]: ni_wpa_interface_bind(wlp2s0): Operation not permitted Okt 06 20:52:09 becherer7 wickedd[1388]: wpa_supplicant doesn't know interface wlp2s0 Okt 06 20:52:09 becherer7 wickedd-nanny[1392]: device wlp2s0: call to org.opensuse.Network.Wireless.changeDevice() failed: General failure Okt 06 20:52:09 becherer7 wickedd-nanny[1392]: wlp2s0: failed to bring up device, still continuing Okt 06 20:52:14 becherer7 wicked[1394]: lo up Okt 06 20:52:14 becherer7 wicked[1394]: enp3s0 enslaved Okt 06 20:52:14 becherer7 wicked[1394]: wlp2s0 device-not-running Okt 06 20:52:14 becherer7 wicked[1394]: bond0 setup-in-progress Okt 06 20:52:14 becherer7 systemd[1]: Started wicked managed network interfaces. Okt 06 20:53:16 becherer7 wickedd[1388]: unable to translate eap protocol PWD ======================================= and here is my /etc/sysconfig/network/ifcfg-wlp2s0 BOOTPROTO='none' BROADCAST='' ETHTOOL_OPTIONS='' IPADDR='' MTU='' NAME='Wireless 7260' NETWORK='' REMOTE_IPADDR='' STARTMODE='hotplug' WIRELESS_AP='' WIRELESS_AP_SCANMODE='1' WIRELESS_AUTH_MODE='psk' WIRELESS_BITRATE='auto' WIRELESS_CA_CERT='' WIRELESS_CHANNEL='' WIRELESS_CLIENT_CERT='' WIRELESS_CLIENT_KEY='' WIRELESS_CLIENT_KEY_PASSWORD='' WIRELESS_DEFAULT_KEY='0' WIRELESS_EAP_AUTH='' WIRELESS_EAP_MODE='' WIRELESS_ESSID='my-wifiname' WIRELESS_FREQUENCY='' WIRELESS_KEY='' WIRELESS_KEY_0='' WIRELESS_KEY_1='' WIRELESS_KEY_2='' WIRELESS_KEY_3='' WIRELESS_KEY_LENGTH='128' WIRELESS_MODE='Managed' WIRELESS_NICK='' WIRELESS_NWID='' WIRELESS_PEAP_VERSION='' WIRELESS_POWER='no' WIRELESS_WPA_ANONID='' WIRELESS_WPA_IDENTITY='' WIRELESS_WPA_PASSWORD='' WIRELESS_WPA_PSK='my-password' ZONE=home PREFIXLEN='24' IFPLUGD_PRIORITY='1' this file has not changed since the update. whats going on here?? simoN -- www.becherer.de -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 2

[opensuse] Google search security question
by Carlos E. R. 06 Oct '19

06 Oct '19

Hi, This has happened to me more than once, but this time I investigated. I was googling for "home made vaccum pump for grains" (something on a thread on the offtopic mail list). One of the answers was: +++............ Homemade Grain Vac - Inomera inomera.com › svp=homemade-grain-vac Traducir esta página This pump can draw a vacuum like the first, but it can also inflate beach toys and air mattresses, or pump water. The actual shelf life of oatmeal varies with the ... ............++- Points to <https://www.goo[---]gle.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=23&cad=r…> (side note: I'm disabling most urls in this post by inserting But clicking on the *google* search I got redirected to a BAD site that fakes to be google but it is not, says that I have been selected for a price. Impossible to go back, the site manipulates the FF history (so, if you try it, use "open on a new tab"). Attempting again, I get to porno site! It is not the first time this happens to me. :-( It seems the first redirection is <https://lads[---]blue.com/rubpf4qr?key=356544da9066c05a7f4a580d11b93717> It also hits: <https://best[---]dateshere-for23.com/?u=7pfk605&o=e9ym176&t=14961610adster&…> <http://competi[---]tion8673.fastfree[---]redics105.live/4513258688/?u=zqq8h…> <https://best.alie[---]xpress.com/es.htm?af=14952720&dp=aemkt8ltfstr&cn=%257…> <https://commer[---]cego.site/tracking/redirct.php?t=http://s.click.aliexpre…> <http://gamet[---]racker.club/redirct.php?t=http://s.click.aliexpress.com/e/…> I will have to block all those sites. ¿Ideas? This machine is on "named". Can "ublock" block entire sites? [...] Yes, but I don't know where to write them. <https://github.com/gorhill/uBlock/wiki/Dynamic-filtering:-rule-syntax> «For example, * disqus.com * block means "globally block all net requests to disqus.com".» I have to do that, but I don't see how. The addon does not allow me to write anything! The box to write is a search box. Apparently: 127.0.0.1 lads[---]blue.com in /etc/hosts does the trick So that's what I'm doing now. Is that the best method, or can I convince ublock to block entire sites? Second question: Can one report to google that it is giving as replies *bad* sites? -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)

5 8

[opensuse] supertuxcart
by Simon Becherer 06 Oct '19

06 Oct '19

Hi, is someone running supertuxcart on a LOCAL network with firewalls enabled? i opened the 3 ports (server and client): 2759 udp 2758 udp 2757 udp i could play when i type in the server ip-address. but the search for servers will not show the server. only if i disable the firewall AT CLIENT then it will show the server with the search function. i tried also to change the config of supertuxcart to use static client port. but what i have seen with wireshark (without really knowing what i see) there is no 2758 shown, so i guess this setting did not work at the moment) any ideas ? simoN -- www.becherer.de -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Backup Failed
by Paul Groves 05 Oct '19

05 Oct '19

My backup failed last night. I have three files which failed with tar error Cannot stat: Bad message I tried opening the files and the cannot open with bad message error I also checked the permissions which shows a load of question marks instead of the rwx flags What does this error mean and how can I fix it? Paul -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

[opensuse] OT-ish : dir content globbing question
by David T-G 05 Oct '19

05 Oct '19

Hi, all -- I know that this isn't SuSE-specific, but everyone here loves a puzzle :-) I have a collection of directories with varying contents; most but not all have files in them, and many of interest have subdirs in them. Here's a sample set: davidtg@u17383850:/tmp/TEST> du -ka * 16404 2019-0203/file 32804 2019-0203/DIR-100/content 32808 2019-0203/DIR-100 32804 2019-0203/DIR-23W/content 32808 2019-0203/DIR-23W 32804 2019-0203/DIR-A05/content 32808 2019-0203/DIR-A05 114832 2019-0203 16404 2019-0312/file 16408 2019-0312 32804 2019-0416/DIR-209/content 32808 2019-0416/DIR-209 16404 2019-0416/file 16404 2019-0416/other 65620 2019-0416 4 2019-0611 32804 2019-0817/DIR-209/content 32808 2019-0817/DIR-209 16404 2019-0817/file 32804 2019-0817/DIR-941/content 32808 2019-0817/DIR-941 32804 2019-0817/DIR-PXD/content 32808 2019-0817/DIR-PXD 114832 2019-0817 16404 2019-0924/file 16404 2019-0924/other 32812 2019-0924 I want to get a du total for all of the DIR-* subdirs, grouped by parent, without throwing any errors. The simple version obviously doesn't work: davidtg@u17383850:/tmp/TEST> for D in 2* ; do du -skhc $D/DIR-* ; done 33M 2019-0203/DIR-100 33M 2019-0203/DIR-23W 33M 2019-0203/DIR-A05 97M total du: cannot access `2019-0312/DIR-*': No such file or directory 0 total 33M 2019-0416/DIR-209 33M total du: cannot access `2019-0611/DIR-*': No such file or directory 0 total 33M 2019-0817/DIR-209 33M 2019-0817/DIR-941 33M 2019-0817/DIR-PXD 97M total du: cannot access `2019-0924/DIR-*': No such file or directory 0 total The best I've found in ten minutes of thinking is to use case to test a globbing of the list to see if it's still the input, but that seems ... ugly :-) davidtg@u17383850:/tmp/TEST> for D in 2* ; do DIRS=`echo $D/DIR-*` ; case "$DIRS" in *\* ) continue ;; esac ; du -skhc $D/DIR* ; done 33M 2019-0203/DIR-100 33M 2019-0203/DIR-23W 33M 2019-0203/DIR-A05 97M total 33M 2019-0416/DIR-209 33M total 33M 2019-0817/DIR-209 33M 2019-0817/DIR-941 33M 2019-0817/DIR-PXD 97M total What I'd really like is to be able to [ -d $D/DIR-* ] but of course that doesn't work because there can be multiple matches. Got any better ideas? HANN :-D -- David T-G See http://justpickone.org/davidtg/email/ See http://justpickone.org/davidtg/tofu.txt -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 9

[opensuse] video question
by Doug McGarrett 05 Oct '19

05 Oct '19

OpenSUSE Tumbleweed up to date as per a day or two ago. I receive every so often, a video packed in a file from some organization--perhaps Popular Mechanics--which reads "No compatible source was found for this media. Refresh the page to resume playback." It is not possible to play the video. It is not possible to "refresh the page"--I wouldn't even know how, if it were, but no action can be taken in regard to this. The specific file from PopMech is called WATCH NEXT "This Glider Uses Water-Reactive Fuel to Launch" It is a subsidiary of this URL: https://www.popularmechanics.com/science/animals/g29331225/fat-bears-machin… I probably need some kind of driver that I don't have. Can someone tell me what I need to run this video? Thanx! --doug -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

8 22

[opensuse] tumbleweed update libvirtd did not start any more.
by Simon Becherer 05 Oct '19

05 Oct '19

Hi, updated tumbleweed from: 20190607 -> 20191002 libvirt will not start any more. (before was running) ● libvirtd.service - Virtualization daemon Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Sat 2019-10-05 16:46:22 CEST; 3min 20s ago Docs: man:libvirtd(8) https://libvirt.org Process: 9810 ExecStart=/usr/sbin/libvirtd $LIBVIRTD_ARGS (code=exited, status=6) Main PID: 9810 (code=exited, status=6) Oct 05 16:46:22 becherer2 systemd[1]: libvirtd.service: Service RestartSec=100ms expired, scheduling restart. Oct 05 16:46:22 becherer2 systemd[1]: libvirtd.service: Scheduled restart job, restart counter is at 5. Oct 05 16:46:22 becherer2 systemd[1]: Stopped Virtualization daemon. Oct 05 16:46:22 becherer2 systemd[1]: libvirtd.service: Start request repeated too quickly. Oct 05 16:46:22 becherer2 systemd[1]: libvirtd.service: Failed with result 'exit-code'. Oct 05 16:46:22 becherer2 systemd[1]: Failed to start Virtualization daemon. ● libvirtd.socket - Libvirt local socket Loaded: loaded (/usr/lib/systemd/system/libvirtd.socket; disabled; vendor preset: disabled) Active: failed (Result: service-start-limit-hit) since Sat 2019-10-05 16:46:22 CEST; 3min 20s ago Listen: /run/libvirt/libvirt-sock (Stream) Oct 05 16:46:21 becherer2 systemd[1]: Listening on Libvirt local socket. Oct 05 16:46:22 becherer2 systemd[1]: libvirtd.socket: Failed with result 'service-start-limit-hit'. what should this tell me???? simoN -- www.becherer.de -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 3

Re: [opensuse] video question
by Carlos E.R. 05 Oct '19

05 Oct '19

You forgot to post to the list, so others could not comment. On 04/10/2019 20.23, Doug McGarrett wrote: > On 10/04/2019 01:04 PM, Carlos E.R. wrote: >> On 04/10/2019 16.31, Peter McD wrote: >>> Am 04.10.19 um 14:10 schrieb Carlos E. R.: >>>> On 04/10/2019 13.45, Peter McD wrote: >>>>> Am 04.10.19 um 02:52 schrieb Doug McGarrett: >>>>> >>>>>> Thank you, Carlos! I believe that this worked. Your very detailed >>>>>> instructions are just what I needed to add the Packman stuff. > > It looks lke it only partly worked. I can now see a picture when I try > and open "This Glider Uses Water-Reactive Fuel to Launch" from the Pop > Mech site, but I just get a little circle going around and around in the > middle of the picture. Maybe the picture is defective, but I > suspect there's still something missing. The other test video that > someone suggested in this thread is viewable. Well, maybe you need to restart the session or maybe reboot. Try "zypper ps" to see what is pending (as root or sudo). It is also possible that you need something else. Enter yast software manager again, search (in the search box) for "GStreamer" (name only). There should be a lot of them. Well, now, one by one you check that they come from packman (there is a version tab on the right hand panel). Some do not have a version on packman, so don't change them. You'll see a list of package versions and from where; the top line says what's the installed version. If it is not packman and there is one from packman, just tick on the one that says "packman". There should be none to change, as you did the switch yesterday. Maybe there is some not installed package, though; if that's the case, use your judgment to install them. Those will not have a tick on the left (right hand panel, top half). Ignore the -debuginfo or -devel or -doc packages. Possibly ignore the -32bit too. Me, I just did that and found some new ones. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)

1 0

[opensuse] leap 15.0 zypper up - Segmentation Fault??
by David C. Rankin 04 Oct '19

04 Oct '19

All, This is the first time I've seen this: # zypper up Retrieving repository 'cinelerra' metadata ........................................................[done] Building repository 'cinelerra' cache .............................................................[done] Retrieving repository 'mozilla' metadata ..........................................................[done] Building repository 'mozilla' cache ...............................................................[done] Retrieving repository 'update' metadata --------------------------------------------------------------[/]Segmentation fault zypper.log contains, e.g. <snip> 2019-10-04 15:45:06 <5> vlleap15(7938) [zypp] ZYppFactory.cc(sigsegvHandler):55 Error: signal 11 2019-10-04 15:45:06 <5> vlleap15(7938) [zypp] ZYppFactory.cc(sigsegvHandler):55 [hd]: (-3) /usr/lib64/libzypp.so.1712 : zypp::dumpBacktrace(std::ostream&)+0x39 [0x7f6be32eb399] 2019-10-04 15:45:06 <5> vlleap15(7938) [zypp] ZYppFactory.cc(sigsegvHandler):55 [hd]: (-2) /usr/lib64/libzypp.so.1712 : +0x39923b [0x7f6be32a423b] 2019-10-04 15:45:06 <5> vlleap15(7938) [zypp] ZYppFactory.cc(sigsegvHandler):55 [hd]: (-1) /lib64/libc.so.6 : +0x361e0 [0x7f6be1dd11e0] 2019-10-04 15:45:06 <5> vlleap15(7938) [zypp] ZYppFactory.cc(sigsegvHandler):55 vvvvvvvvvv---------------------------------------- 2019-10-04 15:45:06 <5> vlleap15(7938) [zypp] ZYppFactory.cc(sigsegvHandler):55 [bt]: (0) /usr/lib64/libcurl.so.4 : +0x53011 [0x7f6be156e011] 2019-10-04 15:45:06 <5> vlleap15(7938) [zypp] ZYppFactory.cc(sigsegvHandler):55 [bt]: (1) /usr/lib64/libcurl.so.4 : +0x530bf [0x7f6be156e0bf] 2019-10-04 15:45:06 <5> vlleap15(7938) [zypp] ZYppFactory.cc(sigsegvHandler):55 [bt]: (2) /usr/lib64/libcurl.so.4 : +0x538fa [0x7f6be156e8fa] 2019-10-04 15:45:06 <5> vlleap15(7938) [zypp] ZYppFactory.cc(sigsegvHandler):55 [bt]: (3) /usr/lib64/libcurl.so.4 : +0x54b07 [0x7f6be156fb07] 2019-10-04 15:45:06 <5> vlleap15(7938) [zypp] ZYppFactory.cc(sigsegvHandler):55 [bt]: (4) /usr/lib64/libcurl.so.4 : +0x21c39 [0x7f6be153cc39] 2019-10-04 15:45:06 <5> vlleap15(7938) [zypp] ZYppFactory.cc(sigsegvHandler):55 [bt]: (5) /usr/lib64/libcurl.so.4 : +0xf3a8 [0x7f6be152a3a8] 2019-10-04 15:45:06 <5> vlleap15(7938) [zypp] ZYppFactory.cc(sigsegvHandler):55 [bt]: (6) /usr/lib64/libcurl.so.4 : +0x2660f [0x7f6be154160f] 2019-10-04 15:45:06 <5> vlleap15(7938) [zypp] ZYppFactory.cc(sigsegvHandler):55 [bt]: (7) /usr/lib64/libcurl.so.4 : +0x382e3 [0x7f6be15532e3] 2019-10-04 15:45:06 <5> vlleap15(7938) [zypp] ZYppFactory.cc(sigsegvHandler):55 [bt]: (8) /usr/lib64/libcurl.so.4 : curl_multi_perform+0xc3 [0x7f6be1554423] 2019-10-04 15:45:06 <5> vlleap15(7938) [zypp] ZYppFactory.cc(sigsegvHandler):55 [bt]: (9) /usr/lib64/libzypp.so.1712 : zypp::media::multifetchrequest::run(std::vector<zypp::Url, std::allocator<zypp::Url> >&)+0x148 [0x7f6be306b838] 2019-10-04 15:45:06 <5> vlleap15(7938) [zypp] ZYppFactory.cc(sigsegvHandler):55 [bt]: (10) /usr/lib64/libzypp.so.1712 : zypp::media::MediaMultiCurl::multifetch(zypp::filesystem::Pathname const&, _IO_FILE*, std::vector<zypp::Url, std::allocator<zypp::Url> >*, zypp::callback::SendReport<zypp::media::DownloadProgressReport>*, zypp::media::MediaBlockList*, long) const+0x528 [0x7f6be306df38] <snip> ?? -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

[opensuse] Help with crontab
by Gustav Degreef 04 Oct '19

04 Oct '19

Hello, I am trying to use festival TTS. It needs to be run as a server. The instructions are to enter in a console " sudo crontab -e" command then to add @restart /usr/bin/festival --server Tha is straightforward, but then I don't know how to proceed from there. I read the man page for crontab and it says that once the commands are specified, you have to exit the editor that is specified (I guess in my system) and then the crontab file becomes active. I have no idea where to proceed after I past the command into the window. I tried typing exit, q and control q, but nothing happens. The menu of the window says to save the output, but when I try that it gives a blank box to type a name to save it to. What is the correct way to finish the task Any help would be appreciated. Gustav -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

14 57

[opensuse] Search by content does not work for me.
by Carlos E. R. 04 Oct '19

04 Oct '19

Leap 15.0, XFCE. I don't know what "program" does it, the title of the box says "search for files". There is no "about" box. But in the "ps afxu" list I see that "gnome-search-tool" is running. I select to search: Name contains: *odt Look in folder: cer (that's my home) Select more options contains the text: cucaracha Finds nothing. Which is absurd, I have that LO doc opened, the file does exist. If I try search without a content, also finds nothing. Again absurd, I have many *odt files on my home. I can not see in the entire application menu what to use to configure the search, but I have used it in the past, so it must exist. Anyway, this tool says it uses "find(1), locate(1), grep(1)". Grep? Wasn't there a tool in gnome or xfce that created an index of contents that took a lot of resources, similar to baloo in KDE? What's it name? Ah, tracker. If I run "tracker" nothing happens. It seems to be a CLI program. cer@Telcontar:~> tracker status Currently indexed: 107064 files, 5715 folders Remaining space on database partition: 59,0 GB (56,13%) All data miners are idle, indexing complete cer@Telcontar:~> The rpm description says: tracker - Object database, tag/metadata database, search tool and indexer Tracker is a desktop-neutral object database, tag/metadata database, search tool and indexer. There must be a GUI to it! The wikipedia says "Tracker has been adopted by the GNOME desktop environment and is heavily integrated into GNOME Shell and GNOME Files." Ok, how do I use it? I don't see it in Nautilus (aka gnome files). I see a search button, but I do not see how to search for a file pattern with a certain content. [...] Ok, found it, and it does locate the "cucarachas" files. Not easy at all to find it, and each time I need it I have to search first how to do it... Took an hour! -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)

3 4

[opensuse] Cisco ARM
by Roger Oberholtzer 03 Oct '19

03 Oct '19

Does anyone have any experience with Cisco ARM on openSUSE? Especially Tumbleweed? It seems that we may need to run this on any Linux computer that we want to connect to our work network. I see that they support RedHat and CentOS. But often the RedHat stuff will install on openSUSE. At least I am hoping... And maybe they support SUSE, even if I did not see it when I did a quick check. Seems our company is wanting ISO27001 certification. -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 1

[opensuse] Start job for home partition times out after upgrading to 20190923 or newer
by Noah Davis 02 Oct '19

02 Oct '19

I'm using Tumbleweed. When I upgrade from snapshot 20190921 to 20190923 or newer (including 20190926), the start job for my home partition (XFS filesystem) times out when I am booting my laptop. This causes my laptop to go into what I assume is a rescue mode where I can enter my root password and run commands. If I comment out my home partition in /etc/fstab, I can get to SDDM, but I can't log in because I don't have access to my home partition. I have looked at `journalctl -xb`, but I could not find anything else about why this happened. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 1

[opensuse] Tumbleweed and NVidia GEFORCE GT610
by Roger Oberholtzer 02 Oct '19

02 Oct '19

I am trying to do a new Tumbleweed install on a system that has a GT610 graphics card. The install fails early on, complaining that /usr/lib64/dri/swrast_dri.so cannot be found. This file does exist in a current Tumbleweed system. So, I am guessing that there are fewer files on the install media. In this case, it is the network installer. Two questions: * Is there a list of supported graphics cards that can be used with tumbleweed (including the install step)? * Might more files be available in the full installer as compared to the network installer? This is a install of a test system. We were just hoping to use what we had at hand for some equipment testing. We need Tumbleweed because many libraries are compatible with Ubuntu 18.04. Don't ask... -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 4