January 2017 - openSUSE Users - openSUSE Mailing Lists

[opensuse] system-sleep/grub2.sleep fails to find the correct grub target
by Carlos E. R. 31 Jan '17

31 Jan '17

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I see this in the log while trying to hibernate, and a delay: <3.6> 2017-01-30 20:23:20 Telcontar systemd-sleep 10692 - - INFO: running /usr/lib/systemd/system-sleep/grub2.sleep for hibernate <3.6> 2017-01-30 20:23:20 Telcontar systemd-sleep 10692 - - INFO: Running prepare-grub .. <3.6> 2017-01-30 20:23:20 Telcontar systemd 1 - - Stopping Deferred execution scheduler... <3.6> 2017-01-30 20:23:20 Telcontar systemd 1 - - Stopped Deferred execution scheduler. <3.6> 2017-01-30 20:23:20 Telcontar systemd-sleep 10692 - - service: no such service upsd.service <3.6> 2017-01-30 20:23:20 Telcontar systemd-sleep 10692 - - Skipping grub entry #, because its root= parameter (/dev/sda1) <3.6> 2017-01-30 20:23:20 Telcontar systemd-sleep 10692 - - does not match the current root device (/dev/sdb8). <3.6> 2017-01-30 20:23:20 Telcontar systemd-sleep 10692 - - Skipping grub entry #, because its root= parameter (/dev/sda1) <3.6> 2017-01-30 20:23:20 Telcontar systemd-sleep 10692 - - does not match the current root device (/dev/sdb8). <3.6> 2017-01-30 20:23:20 Telcontar systemd-sleep 10692 - - Skipping grub entry #, because its root= parameter (/dev/sda1) <3.6> 2017-01-30 20:23:20 Telcontar systemd-sleep 10692 - - does not match the current root device (/dev/sdb8). <3.6> 2017-01-30 20:23:20 Telcontar systemd-sleep 10692 - - Skipping grub entry #, because it has the noresume option <3.6> 2017-01-30 20:23:20 Telcontar systemd-sleep 10692 - - Skipping grub entry #, because its root= parameter (/dev/sda1) <3.6> 2017-01-30 20:23:20 Telcontar systemd-sleep 10692 - - does not match the current root device (/dev/sdb8). <3.6> 2017-01-30 20:23:20 Telcontar systemd-sleep 10692 - - Skipping grub entry #, because it has the noresume option <3.6> 2017-01-30 20:23:20 Telcontar systemd-sleep 10692 - - Skipping grub entry #, because its root= parameter (/dev/sdb2) <3.6> 2017-01-30 20:23:20 Telcontar systemd-sleep 10692 - - does not match the current root device (/dev/sdb8). <3.6> 2017-01-30 20:23:20 Telcontar systemd-sleep 10692 - - Skipping grub entry #, because its root= parameter (/dev/sdb2) <3.6> 2017-01-30 20:23:20 Telcontar systemd-sleep 10692 - - does not match the current root device (/dev/sdb8). <3.6> 2017-01-30 20:23:20 Telcontar systemd-sleep 10692 - - Skipping grub entry #, because its root= parameter (/dev/sdb2) <3.6> 2017-01-30 20:23:20 Telcontar systemd-sleep 10692 - - does not match the current root device (/dev/sdb8). <3.6> 2017-01-30 20:23:20 Telcontar systemd-sleep 10692 - - Skipping grub entry #, because its root= parameter (/dev/sdb2) <3.6> 2017-01-30 20:23:20 Telcontar systemd-sleep 10692 - - does not match the current root device (/dev/sdb8). <3.6> 2017-01-30 20:23:20 Telcontar systemd-sleep 10692 - - Skipping grub entry #, because its root= parameter (/dev/sdb7) <3.6> 2017-01-30 20:23:20 Telcontar systemd-sleep 10692 - - does not match the current root device (/dev/sdb8). <3.6> 2017-01-30 20:23:20 Telcontar systemd-sleep 10692 - - Skipping grub entry #, because its root= parameter (/dev/sdb7) <3.6> 2017-01-30 20:23:20 Telcontar systemd-sleep 10692 - - does not match the current root device (/dev/sdb8). <3.6> 2017-01-30 20:23:20 Telcontar systemd-sleep 10692 - - Skipping grub entry #, because its root= parameter (/dev/sdb7) <3.6> 2017-01-30 20:23:20 Telcontar systemd-sleep 10692 - - does not match the current root device (/dev/sdb8). <3.6> 2017-01-30 20:23:20 Telcontar systemd-sleep 10692 - - Skipping grub entry #, because its root= parameter (/dev/sdb7) <3.6> 2017-01-30 20:23:20 Telcontar systemd-sleep 10692 - - does not match the current root device (/dev/sdb8). <3.6> 2017-01-30 20:23:20 Telcontar systemd-sleep 10692 - - Skipping grub entry #, because its root= parameter (/dev/sdb7) <3.6> 2017-01-30 20:23:20 Telcontar systemd-sleep 10692 - - does not match the current root device (/dev/sdb8). <3.4> 2017-01-30 20:23:25 Telcontar systemd-sleep 10697 - - /usr/lib/systemd/system-sleep/grub2.sleep failed with error code 2. <3.6> 2017-01-30 20:23:25 Telcontar systemd-sleep 10692 - - Suspending system... <0.6> 2017-01-31 12:04:55 Telcontar kernel - - - [158874.187341] PM: Syncing filesystems ... done. Then, on come back, I see the boot menu of grub waiting for a boot selection. Fortunately it is the default one and boot proceeds after some seconds correctly, and hibernation image is found. It is true that the string "/dev/sdb8" is not found on /boot/grub2/grub.cfg. It is an UUID: linux /vmlinuz-4.4.36-8-default root=UUID=c6a59497-85b9-454c-a5d1-1dcafa6eed3d splash=verbose loglevel=3 console=tty0 vga=0x31a resume=/dev/disk/by-label/Swap_0 splash=verbose showopts cer@Telcontar:~> l /dev/disk/by-uuid/c6a59497-85b9-454c-a5d1-1dcafa6eed3d lrwxrwxrwx 1 root root 10 Jan 27 13:47 /dev/disk/by-uuid/c6a59497-85b9-454c-a5d1-1dcafa6eed3d -> ../../sdb8 cer@Telcontar:~> How come? Bugzilla? Known issue? I might as well remove the system-sleep/grub2.sleep script as useless... - -- Cheers Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAliQddcACgkQtTMYHG2NR9WWhgCePioF3GkkypuX/NMvQVceJx/d QhsAn2nQjwqsX3gv/hANJm/5Z9gv2H2b =8nmt -----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] Multiple 6 and 11 coredumps on tumblerd
by Mikhail Kasimov 31 Jan '17

31 Jan '17

Hello! After 42.1 -> 42.2 via 'zypper dup', I have multiple coredumps (6 and 11) on /usr/lib64/tumbler-1/tumblerd. Can some give a hint how to insvestigate and fix these annoying problems? [1] https://bugzilla.opensuse.org/show_bug.cgi?id=1012138 (SEGV 11) [2] https://bugzilla.opensuse.org/show_bug.cgi?id=1022066 (SEGABRT 6) Thanks fot advice! -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] cfdisk - strange bad behavior in openSUSE 13.2
by Istvan Gabor 31 Jan '17

31 Jan '17

Hello: This occurs in openSUSE 13.2. Whenever I run cfdisk (version: cfdisk from util-linux 2.25.1) after exiting the program the given device is "rescanned" and my desktop is populated with "A new medium has been detected" windows (Trinity desktop), as many as the partition numbers on the disk. dmesg also indicates that the device was "rescanned". For example: # cfdisk /dev/sdd I exit cfdisk without modifying anything 11 "new devices window appears on the desktop dmesg shows: [ 940.463099] sdd: sdd1 sdd2 sdd3 sdd4 < sdd5 sdd6 sdd7 sdd8 sdd9 sdd10 sdd11 sdd12 > If I login from a remote computer through ssh and run and exit cfdisk, the windows appear on the current user's desktop. This is an unwanted behavior. I've been using cfdisk for several years but never seen something similar. How can I stop this? Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 2

Re: [opensuse] HP printer Leap 42.2 solved
by michael norman 30 Jan '17

30 Jan '17

On 30/01/17 11:44, michael norman wrote: > I have two pcs both attached to a BT router. pc1 is my main box and > dual boots 42.2 and Linux Mint 18.1. That one is a Shuttle, about 5 > years old but still fully functional. pc2 is an older tower probably > about 12 years old but again functional. I use it as a back up machine > and because its the most convenient place to put the printer. HP > Deskjest 2300 > > On 30/01/17 11:20, Per Jessen wrote: >> michael norman wrote: >> >>> My HP D2300 usb printer has worked for many years. It is attached to >>> one of my two pcs and shared between the two. This worked fine up to >>> 13.2 but I cannot get 42.2 to share the printer. >> >> Share out or share in? >> >>> Sharing fails in Yast whereas it worked up to 13.2, >> >> On my Leap422 test clients, I have to go into Yast->Printers and enable >> the network listening. After that it works - the client then runs a >> cups-browsed daemon. >> >>> Is there a known fix for this ? >> >> I think we'll need some more info about your setup - where is the >> printer attached etc. >> >> >> > I went into Yast Printers and just enabled sharing to all computers on the local network. works now. M -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Leap42x - playing mpeg video ?
by Per Jessen 30 Jan '17

30 Jan '17

The video player defaults to "Dragon Player", which doesn't appear to be able to play an MPEG file. On my 10.3 machine, I would use kaffeine, but I suspect I must have installed something extra there too. Ah, kaffeine still works - installed, ran it, it asked if I wanted to install extra libraries/drivers - et voila!, I can play mpeg video. Looks like kaffeine ought to be the default instead of Dragon Player (which doesn't even alert me to the fact that it can't play). -- Per Jessen, Zürich (-4.7°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

8 14

[opensuse] twm
by Richmond 29 Jan '17

29 Jan '17

I see in the change log in yast that twm was split from the original. It says: "Split twm from xorg-x11. Initial version: 1.0.5." It was last updated in 2015. Is it still being maintained? Is there an official website? It looks like it is a SUSE version. I think there is, and possibly always has been, a bug in it... -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

[opensuse] konsole always run as root
by Hans de Faber 28 Jan '17

28 Jan '17

Since some time I can no longer run konsole as a non root user! If a start konsole it asks always for the root password. user hans (non root): dolphin ==> cd /usr/bin and start konsole , konsole asks for rootpassword. copy konsole to /home/hans/bin and start it from there konsole doesnot ask for the rootpasssword. Question: 1. Is it correct that /usr/bin/konsole always asks for the rootpassword ? 2. How is this done that konsole in /usr/bin asks for pwd and a copy in a different dir not ? Thanks, Hans -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

6 8

Re: [opensuse] Tape Drive Error Log Utility
by Paul Groves 28 Jan '17

28 Jan '17

On 25/01/17 07:09, Andrei Borzenkov wrote: > On Fri, Jan 20, 2017 at 9:28 PM, Paul Groves <paul.groves.787(a)gmail.com> wrote: >> On 20/01/17 18:17, Andrei Borzenkov wrote: >>> 20.01.2017 20:45, Paul Groves пишет: >>>> Hi, >>>> >>>> Does anyone have the linux utility for resetting the error codes on tape >>>> drives? (I cannot recall the name) >>>> >>>> I have a drive with 'Error 5' on the LED display which means a hardware >>>> error. It was due to a stuck tape which has since been removed but the >>>> drive is still in an error state. >>> Normally power cycle clears such errors. >>> >>>> I have been on the phone to quantum but they will not support my drive >>>> or not send me a copy of the utility. (Wish I had bought a HP with >>>> lifetime warranty now). >>>> >>>> Thanks >>>> >>>> Paul >>>> >>>> >> Hi Andrei, >> >> I tried that already, no luck I'm afraid. >> >> The manual says that, in the case of any hardware errors the drive has a >> mechanism to prevent users from inserting a tape cartridge until the code is >> cleared using the utility. >> > Then please tell exact manufacturer and model of your drive. Quantum > ships drives from IBM, HP and Quantum and manual for *Quantum* LTO7 > says "The error code [5] may clear when you cycle power to the tape > drive or place it in maintenance mode." And you can place it in > maintenance mode from the panel, without using any external software. it is a 2011 Quantum LTO4 Half Height (Model No:TC-L42BN) LTO4 Quantum refer to it as an 'Original' http://www.quantum.com/serviceandsupport/softwareanddocumentationdownloads/… I was unaware they had a maintenance mode. (If my model does, maybe only the new drives). How does it say to place it in said mode? I have tried power cycling the drive, holding the button in for 2, 10, 20, 30 seconds. I also tried holding the button in while powering on the drive but no luck. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Most stable openSUSE version for 64bit computer
by Terry Eck 28 Jan '17

28 Jan '17

I have a DELL XPS 64bit computer and I've tried Tumbleweed and Leap 4.2. Between the two which is the most stable. Is the another openSUSE version more stable for 64bit computers? The reason I ask is because I've had problem with both Tumbleweed and Leap. Until now I've had great luck using openSUSE software on my old 32bit computer. Thanks, Terry -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

24 82

[opensuse] Tor browser install fails on Leap 42.1
by Dave Howorth 27 Jan '17

27 Jan '17

I'm trying to install the Tor browser on Leap 42.1 I went to https://software.opensuse.org/package/torbrowser-launcher and that suggests https://software.opensuse.org/ymp/devel:languages:python/openSUSE_Leap_42.1… as the best place to get the software. I installed that and when I click on the menu entry for Tor Browser, I get a small dialog titled Tor Browser that says it is installing the browser and then says (GRR! why is it yet another dialog that won't let you copy text!) SIGNATURE VERIFICATION FAILED! It says the same thing if I download again, so I suspect the problem is not a dodgy download. There are no hints as to where to look for more diagnostics. Anybody know how to get it working? Cheers, Dave -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

8 24