March 2018 - openSUSE Users - openSUSE Mailing Lists

[opensuse] continous access on/spinning up of floppy drive
by Paul Neuwirth 23 Oct '18

23 Oct '18

This is an OpenPGP/MIME signed message (RFC2440, RFC3156). --=_MIME_CONTENT_BREAK_=_ZVSGRBXMZBOOXUGBRBCHOBMGKKNVGJR_= Content-Type: text/plain; charset="utf-8" Content-Disposition: inline; filename="message.txt" Content-Transfer-Encoding: quoted-printable Hello group, I have on several machines this problem: they are continously trying to=20 access the floppy drives. Two drives already defective, due to the=20 mechanic stress. dmesg shows following continously: [1537682.559487] sd 0:0:3:0: [sdc] Read Capacity(10) failed: Result:=20 hostbyte=3DDID_OK driverbyte=3DDRIVER_SENSE [1537682.559496] sd 0:0:3:0: [sdc] Sense Key : Not Ready [current] [1537682.559498] sd 0:0:3:0: [sdc] Add. Sense: Logical unit not ready,=20 cause not reportable [1537682.656688] sd 0:0:3:0: [sdc] Spinning up disk... [1537683.668046]=20 ............................................................................= ..................not=20 responding... [1537783.093938] sd 0:0:3:0: [sdc] Spinning up disk... [1537784.104049]=20 ............................................................................= ..................not=20 responding... this can't be the wanted behaviour for any removable storage devices? Any Hints? Thank you and have a nice weekend --=_MIME_CONTENT_BREAK_=_ZVSGRBXMZBOOXUGBRBCHOBMGKKNVGJR_= Content-Type: application/pgp-signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Topal (http://freshmeat.net/projects/topal) iQIcBAEBAgAGBQJaLS66AAoJEIiaa+Y8YDPuZSUP/itt7+QHjNCwX6Wi352+lANf whjep7nBWy6Q0bS2PO/ymWDGiodFkO/AvM+MIitdK4cAm1HCBbMZjKsZYLD3e1LR ZnskqO66VG58TU6lVB1jEXWKlp6OKeb6Ar24SR0YxB4F+ZcbSwZI5w62JEBsozhV X4imcBdO+ztJFSW/hFLeV4WrfrplcTufyL6nw+5TtImrVs62uEg20LYjA//OxlHJ NmXM07A48uVBijRUmMsqeyRMevoKjKop2iICZgKyvTnRtRqx0jbzVeqj+aLqnbaq ncdBnBr7Vr9S86TVGHjIDHPN8Ws8dnufk1GwRTQR+Aj4z58g2r88j/u6o7csTFla vINP3ClCp6MRVbVbEqIYOIvG8NDIVTiwQwXk3CeCf+Be71JbDUMjV9GwVl+X9ksC oNBwwFi+mhHQGJOuX/54HGUEn3lJ1ixQzLimuXTgWmdsb1WoWuG+lNO13NhU+ZVn /IKpcqVjkXikQi9hrmZTUutmrFjJ1QusjnPJQDuBLYB0E/lMWjTpUNmRGw71hrDb uccAYc3sQP6zMuUfEgPWewhMmuTwn1LoQdqYrZ0p1+1z/+w5cB3DOB4JILmbKBUH QUYaDhefxPL1oRBtOxoDAdABJLAfgfKdEE0+g0u6HA67Atioe3HP8MWonrKgs3FC pvU9BHc2k0ASHh7HEsRx =uYfb -----END PGP SIGNATURE----- --=_MIME_CONTENT_BREAK_=_ZVSGRBXMZBOOXUGBRBCHOBMGKKNVGJR_=-- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

17 75

[opensuse] 'mailto' + 'postfix' at local machine, host or domain name not found
by Simon Becherer 07 Jun '18

07 Jun '18

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, ipv4, /etc/hosts 127.0.0.1 localhost 127.0.0.2 becherer1.site becherer1 195.167.0.5 becherer1.site becherer1 /etc/postfix/main.cf myhostname = becherer1.site inet_protocols = ipv4 on my older systems (opensuse 11.4) i can use: programm "mailto" and as address: simon@becherer1 simon@localhost simon(a)becherer1.site simon all will be delivered correct at the local machine. if i use the simon@becherer1 or simon(a)becherer1.site or simon the mail tells me in all cases: send to: simon(a)becherer1.site if i use simon@localhost the mail tells me: send to: simon(a)localhost.site i have the same settings like above in the same files in tumbleweed. (because of newer system, there are much more settings in main.cf) only send to "simon(a)becherer1.site" and "simon" will pass. the simon@becherer1 will generate a "undelivered mail return to sender" host or domain name not found name service error for name = becherer1 type=a: host not found the simon@localhost will generate a "undelivered mail return to sender" "simon@localhost loopbacks to myself." sending a "ping" to becherer1 or becherer1.site will return "from becherer1.site 127.0.0.2" and localhost will return "from localhost 127.0.0.1" on both machnines identical, so normally the names are set correct? i guess some other default for postfix may be changed, but i do not find whats wrong, why did postfix not deliver the mails? regards, simoN - -- www.becherer.de -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iQIcBAEBAgAGBQJat+L4AAoJEOuDxDCJWQG+cmYQAKdAWjrF05rtV4B0Sj6AwmWR HtU4gNauN+RB5hIxaBLE2b+/t1+URGkbNdR7jbS/VVmAazFoaJS3uWt3BerGy9kr AvFbnMEJQWjVehHwlnREkjX3Ed3WSPmRYehhqfgKflzZG1tsopfnx8SEJCpIi7yB hcyLRCH7eBF8CStSZ5gf4M76KPwGxkQ602r9pC+IqR0MtOtRmCUMRIJE8UUPK7Fw nVGgOLN8C33xPsNTEbLcM7qzZAEywj4r2qu+a4Fnvpr9fcS2QahpDJ/Drj1YiqJE OaA9GcCKkwab4lvD1BZp0kJEfniPV4W69g5oUq5rHslayXXbYGeQ9OeRryy2O93f c8nV4HBsqjnXrhewWG1wQO8+lcP0UFlztSYy20BX5zZMxyBcWRMEmKgyiQYoOAVX gws2+gs+XnJR0nTN1WT775K/5S8zGHb5C+D+Q7iO2JX/jblWq6zlNnkejSHVWLFV jqv+0GF0bvQ3VpNgtuu5WJrNF36DIxiinOp8VZWg1oT8Z6WKH8p5Eie555PkFxhg t3PWfY+oHNyZhU8SQP3p8myg1Cux3AEQI8bhm/lswMhT88btkEBGb2DSI/VK9mWW 56k2tc90mf8dHrfGZHOd0cWHSE2hiW84AOGRXqY2TS90oAasWdVJgDKxm85VqJVH x/MF6lAOlAXOTHXmQVGQ =egfF -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 16

[opensuse] zypper addrepo - http:// vs. https://
by Per Jessen 10 Apr '18

10 Apr '18

I'm sure someone has a quick explanation: a) zypper addrepo 'https://download.opensuse.org/repositories/Virtualization:containers/openSU…' This fails: Download (curl) error for 'https://download.opensuse.org/repositories/Virtualization:containers/openSU…': Error code: Bad URL Error message: Protocol http not supported or disabled in libcurl b) zypper addrepo 'https://download.opensuse.org/repositories/Virtualization:/containers/openS…' Works fine. (notice the extra slash between 'Virtualization:' and 'container'. c) zypper addrepo 'http://download.opensuse.org/repositories/Virtualization:containers/openSUS…' d) zypper addrepo 'http://download.opensuse.org/repositories/Virtualization:/containers/openSU…' Both work fine. -- Per Jessen, Zürich (9.1°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

7 13

[opensuse] prime-select: unable to query GPU information
by Daniel Bauer 05 Apr '18

05 Apr '18

Hi, I just upgraded my asus laptop with intel/nvidia graphics from 42.1 to 42.3, all went well so far. But when entering prime-select nvidia I get: ERROR unable to query GPU information The script runs anyway, I guess, because when I reboot at some point the screen with the boot messages begins to flicker heavily (I could not read the last message...). I had to restart and boot to runlevel 3, then entered "prime-sectect intel" and now I can boot normally - but of course only using the intel card. I don't know which information you need to help me: please ask and I'll try to provide it. Thanks for your help! Daniel -- Daniel Bauer photographer Basel Barcelona https://www.patreon.com/danielbauer http://www.daniel-bauer.com -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

6 42

[opensuse] Which distros for ReiserFS?
by Stevens 03 Apr '18

03 Apr '18

On the odd chance that I was ignored for possibly hijacking a thread, I shall start a new one but copy and paste my comments in hope of an answer: (re: Killing ReiserFS) I have been following this thread with some interest because of having been running ReiserFS since before he turned homicidal. I have had zero, count that ZERO, problems in all that time so I read with some dismay the effort to actively kill its usage in this whatever-you-call-it distro. I think that the more relevant question to ask is not "can we keep this file system around, pretty please" but "what distros are allowing its use by not actively trying to kill it"? I have used opensuse since before Mandrake went away, which has been a while and, although I don't really want to change distros, I am not married to suse (or leap, or whatever). I feel that what we have here with opensuse/leap is an example of the classic "swing" cartoon which shows the stages of project development from sales, engineering, installation and what the customer actually wanted. My need is not as complex as some and for that ReiserFS works quite well. So, my question remains, "If not suse/leap, then who"? Hopefully someone will know what distros allow the freedom to use whichever FS one wishes without running afoul of the FS nazis. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

22 99

[opensuse] bumblebeed oops
by Markus Koßmann 31 Mar '18

31 Mar '18

Anyone seen this before: 2018-03-31T06:11:24.251115+02:00 linux-86i0 kernel: [ 9.778199] ------------[ cut here ]------------ 2018-03-31T06:11:24.251116+02:00 linux-86i0 kernel: [ 9.778206] WARNING: CPU: 1 PID: 2105 at ../drivers/pci/pci.c:1596 pci_disable_device+0x90/0xa0() 2018-03-31T06:11:24.251117+02:00 linux-86i0 kernel: [ 9.778208] pci 0000:02:00.0: disabling already-disabled device 2018-03-31T06:11:24.251118+02:00 linux-86i0 kernel: [ 9.778208] Modules linked in: vmnet(O) ppdev parport_pc parport fuse vmw_vsock_vmci_transport vsock vmw_vmci vmmon(O) msr bnep btrfs xor raid6_pq arc4 nls_iso8859_1 nls_cp437 vfat intel_rapl fat x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_hdmi kvm_intel snd_hda_codec_realtek snd_hda_codec_generic kvm irqbypass crct10dif_pclmul snd_hda_intel crc32_pclmul snd_hda_codec snd_hda_core crc32c_intel snd_hwdep ghash_clmulni_intel snd_pcm pn544_mei drbg snd_seq uvcvideo mei_phy iwlmvm videobuf2_vmalloc videobuf2_memops snd_seq_device pn544 mac80211 ansi_cprng videobuf2_v4l2 hci snd_timer videobuf2_core aesni_intel btusb btrtl v4l2_common btbcm iTCO_wdt aes_x86_64 dell_wmi videodev nfc snd iTCO_vendor_support sparse_keymap lrw dell_laptop gf128mul btintel glue_helper rtsx_pci_ms bluetooth iwlwifi dcdbas ablk_helper ipmi_msghandler ie31200_edac cryptd memstick soundcore cfg80211 acpi_als joydev edac_core pcspkr i2c_i801 lpc_ich kfifo_buf mei_me shpchp mei industrialio fjes fan thermal int3403_thermal int3402_thermal int3400_thermal battery dell_rbtn dell_smo8800 ac int340x_thermal_zone acpi_thermal_rel rfkill processor ext4 crc16 jbd2 mbcache sd_mod hid_multitouch usbhid sg dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ahci rtsx_pci_sdmmc libahci mmc_core i915(O) i2c_algo_bit libata rtsx_pci mxm_wmi drm_kms_helper(O) syscopyarea sysfillrect sysimgblt fb_sys_fops xhci_pci serio_raw scsi_mod mfd_core ehci_pci xhci_hcd ehci_hcd usbcore usb_common drm(O) wmi video button dm_mirror dm_region_hash dm_log dm_mod bbswitch(O) efivarfs autofs4 [last unloaded: nvidia] 2018-03-31T06:11:24.251119+02:00 linux-86i0 kernel: [ 9.778263] CPU: 1 PID: 2105 Comm: bumblebeed Tainted: P O 4.4.120-45-default #1 2018-03-31T06:11:24.251120+02:00 linux-86i0 kernel: [ 9.778264] Hardware name: Dell Inc. XPS 15 9530/XPS 15 9530, BIOS A08 01/08/2015 2018-03-31T06:11:24.251121+02:00 linux-86i0 kernel: [ 9.778266] 0000000000000000 ffffffff813438a7 ffff88041d86fd98 ffffffff81a532f5 2018-03-31T06:11:24.251121+02:00 linux-86i0 kernel: [ 9.778269] ffffffff810844e1 ffff88041f123000 ffff88041d86fde8 00007fc07cd8e000 2018-03-31T06:11:24.251122+02:00 linux-86i0 kernel: [ 9.778271] ffff88041d86ff28 0000000000000028 ffffffff8108455c ffffffff81a6dc88 2018-03-31T06:11:24.251123+02:00 linux-86i0 kernel: [ 9.778274] Call Trace: 2018-03-31T06:11:24.251124+02:00 linux-86i0 kernel: [ 9.778284] [<ffffffff8101b0f9>] dump_trace+0x59/0x350 2018-03-31T06:11:24.251125+02:00 linux-86i0 kernel: [ 9.778288] [<ffffffff8101b4ea>] show_stack_log_lvl+0xfa/0x180 2018-03-31T06:11:24.251125+02:00 linux-86i0 kernel: [ 9.778291] [<ffffffff8101c2b1>] show_stack+0x21/0x40 2018-03-31T06:11:24.251126+02:00 linux-86i0 kernel: [ 9.778295] [<ffffffff813438a7>] dump_stack+0x5c/0x85 2018-03-31T06:11:24.251127+02:00 linux-86i0 kernel: [ 9.778301] [<ffffffff810844e1>] warn_slowpath_common+0x81/0xb0 2018-03-31T06:11:24.251128+02:00 linux-86i0 kernel: [ 9.778305] [<ffffffff8108455c>] warn_slowpath_fmt+0x4c/0x50 2018-03-31T06:11:24.251128+02:00 linux-86i0 kernel: [ 9.778309] [<ffffffff8138d960>] pci_disable_device+0x90/0xa0 2018-03-31T06:11:24.251129+02:00 linux-86i0 kernel: [ 9.778314] [<ffffffffa000c1cd>] bbswitch_off+0x8d/0x240 [bbswitch] 2018-03-31T06:11:24.251143+02:00 linux-86i0 kernel: [ 9.778319] [<ffffffffa000c5ae>] bbswitch_proc_write+0xae/0xbc [bbswitch] 2018-03-31T06:11:24.251146+02:00 linux-86i0 kernel: [ 9.778324] [<ffffffff81281bcc>] proc_reg_write+0x3c/0x70 2018-03-31T06:11:24.251147+02:00 linux-86i0 kernel: [ 9.778329] [<ffffffff81215ff6>] __vfs_write+0x26/0x140 2018-03-31T06:11:24.251148+02:00 linux-86i0 kernel: [ 9.778332] [<ffffffff81216d7f>] vfs_write+0xaf/0x1d0 2018-03-31T06:11:24.251149+02:00 linux-86i0 kernel: [ 9.778336] [<ffffffff81217e22>] SyS_write+0x42/0xa0 2018-03-31T06:11:24.251150+02:00 linux-86i0 kernel: [ 9.778342] [<ffffffff81640809>] entry_SYSCALL_64_fastpath+0x22/0xba 2018-03-31T06:11:24.253122+02:00 linux-86i0 systemd[1]: Started Network Manager Script Dispatcher Service. 2018-03-31T06:11:24.253330+02:00 linux-86i0 dbus[1340]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' 2018-03-31T06:11:24.255077+02:00 linux-86i0 kernel: [ 9.781274] DWARF2 unwinder stuck at entry_SYSCALL_64_fastpath+0x22/0xba 2018-03-31T06:11:24.255083+02:00 linux-86i0 kernel: [ 9.781275] 2018-03-31T06:11:24.255083+02:00 linux-86i0 kernel: [ 9.781275] Leftover inexact backtrace: 2018-03-31T06:11:24.255085+02:00 linux-86i0 kernel: [ 9.781275] 2018-03-31T06:11:24.255086+02:00 linux-86i0 kernel: [ 9.781303] ---[ end trace 0beb54cbaeaebc1a ]--- Is bumblebeed doing the wrong thing here by not checking the graphics cards state before trying to disable it on startup ? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] misconfigured keyboard: which is correct <keyboard> for HP Envy laptop?
by ken 30 Mar '18

30 Mar '18

Initially This keyboard was functioning fine on a brand-now installation of Leap 24.3 on an HP Envy laptop (17t-n100 CTO). Trying to solve a completely different problem, I went into YaST2 and ran a hardware scan. After doing that, my keyboard was misconfigured and now has numerous problems. E.g., I now have no CapsLock key, neither of my Ctrl keys works, and the leftside Ctrl key now functions like a Super-L key. And there are many more such problems, none of which I ever had in centos or in suse before running that yast hardware scan. Looking around in logs and configs, I found the keyboard specified in /etc/sysconfig/keyboard to be "pc104". I can't say for certain whether that is correct or incorrect, except that "pc104" was mentioned in the log file "/var/log/YaST2/y2log" several times on or about the date/time I ran the hardware scan. So it is highly suspect. Here's that final line from the "keyboard" file: YAST_KEYBOARD="english-us,pc104" In the backups of this machine's previous CentOS (7.x) system there was no /etc/sysconfig/keyboard, but there was /etc/X11/xorg.conf.d/00-keyboard.conf file (programmatically generated) containing this: Section "InputClass" Identifier "system-keyboard" MatchIsKeyboard "on" Option "XkbLayout" "us" Option "XkbModel" "pc105+inet" EndSection If I was a wild-ass cowboy of a sysadmin I'd just replace the "pc104" value in the Leap /etc/sysconfig/keyboard file with the "pc105+inet" value from the CentOS config file and reboot. Yahoo! But that might hork things immensely and leave me with a system with a keyboard even more crippled than what I have now. Does anyone have a more cautious and/or informed solution or suggestion? tnx -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 15

[opensuse] symbol "grub_tmp_measure" after update
by Peter Suetterlin 30 Mar '18

30 Mar '18

Hi list, I have a computer that I upgraded 42.2->42.3 a month ago (without issues). It was powered off since then. Today I rebooted it (again, without issues). I ran a 'zypper up', and rebooted - and now it throws me at grub-rescue with the mentioned error symbol "grub_tmp_measure" not found. grub has been updated during this run. Some quick googling revealed TW was having similar issues about a year ago, still haven't found the main reason then - maybe someone remembers faster than I read? Does it have some kernel relation? That's the only real difference from a standard 42.3, I run a 4.11 kernel (still coming from the 42.2 install, I needed it due to some HW) Especially some quick recovery hints welcome :o -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 7

[opensuse] scanner problems
by jdd＠dodin.org 30 Mar '18

30 Mar '18

Hello, I have strange scanner problems... I have three of them. an HP scanner/printer (usb), a brother scanner/printer (wifi) and an epson 4490 photo. The three of them are pretty old and worked flawlessly since some month ago when I changed my computer. I reused the same disk, so didn't think I will have problem, but didn't used the scanner since. I need them now. but... xsane sees the two printers, but not the epson one iscan (the epson software) sees the epson scanner (so the drivers are ok), but I had to install the 32 bits version, the 64 bits issue many warnings and do not launch My main usual program, VueScan (proprietary) do not see any scanner, when it used to see at least the epson (photo) any idea of what I can do to have the all three seen in the same software? thanks jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 8

[opensuse] LibreOffice 6
by James Knott 29 Mar '18

29 Mar '18

I see LibreOffice 6 is available from https://download.opensuse.org/repositories/LibreOffice:/6.0/openSUSE_Leap_4… Will it be available in the usual Yast update? Or do I have to add the repository? tnx jk -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

6 12