October 2016 - openSUSE Users - openSUSE Mailing Lists

[opensuse] Fwd: Btrfs root partition forced readonly
by Thomas Bauffe 30 Oct '16

30 Oct '16

Hello! I seem to have run into a little trouble with btrfs filesystem on my Tumbleweed installation. The system no longer boots to the graphical environment. The issue seems to be that the root filesystem (sdb3) which uses btrfs filesystem is mounted readonly during boot. The filesystem is on a WD hard drive. I did an extended check on the drive using WD's Data Lifeguard Diagnostic tool which passed the drive as healthy. I found the following errors in the logs: ================================ # journalctl -xb BTRFS: error (device sdb3): unable to find ref byte nr 12967161856 parent 557531136 root 5 owner 2659226 offset 0 .. BTRFS: error (device sdb3) in __btrfs_free_extent:6951: errno=-2 No such entry BTRFS info (device sdb3): forced readonly BTRFS: error (device sdb3) in btrfs_run_delayed_refs:2690: errno=-2 No such entry ================================ Could this be an issue with the root filesystem? I dug into this a bit and the btrfs wiki seems to recommend against using a fsck tool (https://btrfs.wiki.kernel.org/index.php/FAQ#When_will_Btrfs_have_a_fsck_lik…) Can anything be done to repair this partition or should I format and reinstall? Thank you so much for your help in advance and have a pleasant day! Thomas -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

Re: [opensuse] Collision between openSUSE 13.2 KDE sessions if dolphin from another user run under first user's KDE session.
by Alec Destry 30 Oct '16

30 Oct '16

open up dolphin under user john in joe's KDE desktop session means: with the understanding that enable-linger has been set for user john using loginctl, while logged in as joe, from joe's KDE desktop, run Kdesu, enter john's password and then have Kdesu run dolphin. open up a full KDE GUI desktop session (on vt8) under user john means: while logged in as joe, from joe's KDE desktop, use the Start / Leave / Switch user option of the KDE menu to login as user john and start up a parallel full KDE GUI desktop session (on vt8) for user john while keeping joe's full KDE GUI desktop session (on vt7) running. open up dolphin under user root in joe's KDE desktop session means: while logged in as joe, from joe's KDE desktop, use the Start / Applications/ System/ File Manager/ File manager (superuser mode) option to start up dolphin under user root (this option is installed in the KDE menu by the openSUSE 13.2 install program). open up a full KDE GUI desktop session (on vt8) under user root means: while logged in as joe, from joe's KDE desktop, use the Start / Leave / Switch user option of the KDE menu to login as user root and start up a parallel full KDE GUI desktop session (on vt8) for user root while keeping joe's full KDE GUI desktop session (on vt7) running. No I am not using SDDM. I am using the regular KDE desktop with the plasma shell and all of the rest of the standard software. ----- Original Message ----- From: "John Andersen" <jsamyth(a)gmail.com> To: "Alec Destry" <xode(a)lanset.com> Sent: Saturday, October 29, 2016 10:46 AM Subject: Re: [opensuse] Collision between openSUSE 13.2 KDE sessions if dolphin from another user run under first user's KDE session. > On 10/29/2016 10:35 AM, Alec Destry wrote: >> then open up dolphin under user john in joe's KDE desktop session, > > Precisely, step by step, what exactly does that mean. > > Did you use the Start / Leave / Switch user option of the KDE menu > or did you do some sudo voodo? > > What? > > > And are you using SDDM? > > -- > After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 6

[opensuse] grub2 booting partition discrepancy
by George from the tribe 30 Oct '16

30 Oct '16

I am preparing to shift around the partitions on one of my drives, so I am shifting the bootable systems to another drive. I have Leap 42.1 installed on one raid drive, and I created a new raid drive, bigger, copied everything from my old 42.1 to my new 42.1, went through the whole procedure to reinstall grub, ran it and it works great. The 2nd part of this project is I have an older 13.2 installation on an older raid partition. I tried to do the same thing with this one. I created a new raid, and then copied the files over from 13.2. Since this one is not the default boot, I then went back into 42.1, and re-ran mkinitrd, grub2mkconfig, and grub2-install. It looked like it picked up the new 13.2 just fine, but there is a little problem. My old 13.2 installation was on raid drive member /dev/md2. My new 13.2 installation (the copy), is on raid drive member /dev/md7. When I run grub2-mkconfig, this is the portion that comes out from the os-prober for the new 13.2 installation on /dev/md7: Found openSUSE 13.2 (x86_64) on /dev/md7 menuentry 'openSUSE 13.2 (x86_64) (on /dev/md7)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-ef4069f8-f912-40b9-b3ca-c5aec35e310f' { insmod part_gpt gpt insmod diskfilter mdraid1x insmod ext2 set root='mduuid/c8ce1dcb76fc24b52d4f7bc1094b46a1' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint='mduuid/c8ce1dcb76fc24b52d4f7bc1094b46a1' ef4069f8-f912-40b9-b3ca-c5aec35e310f else search --no-floppy --fs-uuid --set=root ef4069f8-f912-40b9-b3ca-c5aec35e310f fi linuxefi /boot/vmlinuz-3.16.7-29-desktop root=UUID=c200ac13-438e-47bc-9715-b012893e0270 resume=/dev/disk/by-uuid/6e662ec0-e324-4b6b-81f2-5ecfcdc56d14 splash=silent quiet showopts initrdefi /boot/initrd-3.16.7-29-desktop } I don't fully get the assignment of roots here - in 2 places it has--set=root: --set=root --hint='mduuid/c8ce1dcb76fc24b52d4f7bc1094b46a1' ef4069f8-f912-40b9-b3ca-c5aec35e310f --set=root ef4069f8-f912-40b9-b3ca-c5aec35e310f Both ofthose are looking at UUID=ef4069f8-f912-40b9-b3ca-c5aec35e310f, which is the UUID of /dev/md7. However, the next line down, it has in there root=UUID=c200ac13-438e-47bc-9715-b012893e0270 which is the UUID for /dev/md2, the old 13.2 system that I am trying to get rid of. So when I boot up and get to the grub menu, and select to boot into 13.2 on /dev/md7, it actually boots into 13.2 on /dev/md2, even though grub has in the menu that it is going to boot into /dev/md7. Anyone know how I can get it to boot into 13.2 on /dev/md7, so I can get rid of /dev/md2? -- George Box: 42.1 | KDE Plasma 5 | AMD Phenom IIX4 | 64 | 32GB Laptop #1: 42.1 | Plasma 5.4.7, Qt 5.7.0 | Core i7-4710HQ | 64 | 16GB Laptop #2: 42.1 | KDE Plasma 5 | Core i5 | 64 | 8GB -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 5

[opensuse] Error message in 13.1
by James Knott 30 Oct '16

30 Oct '16

Tonight, I started getting an error message on my system: "A security trust relationship is not present Singature verification for Repository KDE Extra failed" In Software Management, I was given an option to trust KDE Extra. However, I just disabled it for now. Is there a problem with this repository? tnx jk -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

[opensuse] 13.2 update: scanner no longer available to user
by Roger Price 29 Oct '16

29 Oct '16

The box has an Epson 4990 Photo scanner and for some years a lady has used the xsane graphic interface to scan administrative documents. In march I installed 13.2 and this has continued to run well. Last week I did a complete update with Yast, and now the administrative lady reports that when she runs xsane she gets the messages "Scanning for devices", "no devices available". The command lsusb still reports Bus 001 Device 009: ID 04b8:012a Seiko Epson Corp. GT-X800 [Perfection 4990 PHOTO] I can ssh into this box and successfully operate the scanner using xsane as root. So root still has access to the scanner, but not the user. Any suggestion for fixing this would be much appreciated. Roger -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 4

[opensuse] New keys?
by John Andersen 29 Oct '16

29 Oct '16

A fresh error appeared in Yast package manager today. It appears not in my keylist anywhere... It appears to be unsigned by anyone. An error occurred during repository initialization. [download.opensuse.org-Extra|http://download.opensuse.org/repositories/KDE:/…] Valid metadata not found at specified URL History: - Signature verification failed for repomd.xml Remind me how do I import the current set op opensuse keys? -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse][42.2] What is an LXQt session?
by Felix Miata 29 Oct '16

29 Oct '16

I'm a KDE user totally unsatisfied with Plasma 5, so am trying to explore alternatives with KDE3 unavailable in 42.2. When I select an LXQt session in the greeter in a fresh 42.2 minimal X installation, with patterns-openSUSE-lxqt installed by zypper after the initial installation, a popup opens wanting to know what default window manager I want to use. Then a file picker opens to /usr/bin/. What exactly should one be looking for to answer this prompt? How or why does an LXQt session not qualify as or include some window manager by default? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 3

[opensuse] Collision between openSUSE 13.2 KDE sessions if dolphin from another user run under first user's KDE session.
by Alec Destry 29 Oct '16

29 Oct '16

For example, if I have the computer booted into a full KDE GUI desktop session (on vt7) under user joe, then open up dolphin under user john in joe's KDE desktop session, and then open up a full KDE GUI desktop session (on vt8) under user john, the two KDE GUI desktop sessions will collide. Specifically, john's desktop screen and keyboard input will show up on vt7 and will hide joe's desktop screen and keyboard input. However, some of john's windows (e.g. the logout confirmation screen) will still show up on vt8 and will only accept input on vt8. This collision will occur even if I close out the file manager window for john in joe's KDE desktop session before opening up a full KDE GUI desktop session under user john. If I already have a full KDE GUI desktop session under user john open before I open up a file manager window under john in joe's KDE desktop session, the collision will occur if I close out john's KDE desktop session and then open another KDE desktop session under john. This collision also occurs with user root. If I open up a file manager window under root using the command as setup by the openSUSE 13.2 install program and then open up a full KDE desktop session under root, the same collision between joe and root will occur. The only way to prevent the collision is to log joe out and then log joe back in again after having closed out the file manager window under john (or root) and before opening up any full KDE GUI desktop sessions under any other users. I also tried out openSUSE 13.1 and it has the same problem. I tried having the computer use the video card built in to the motherboard instead of the PCiE video card that I had been using, with the result being that parallel sessions will not even start up. Therefore I am wondering if the problem could be with the video card. Has anyone else experienced this problem with either openSUSE 13.1 or openSUSE 13.2? For anyone not having this problem, could you please give me details on what motherboard and video card you are running openSUSE 13.1 or openSUSE 13.2 on? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] DVD gone, Sound gone
by Koenraad Lelong 29 Oct '16

29 Oct '16

Hi, Today I tried to watch a DVD on my OS 13.2 laptop. When putting the disk in the drive I got a message in the tray that DVD-rom was installed. Trying to play it with Kaffeine, I could not. Last weekend, that same disk was announced with it's name and I had no problems playing the disk. Further investigation revealed my sound was gone too. KMix says I have a Dummy-output. Using Yast I had to reconfigure the sound-card. There, playing the test sound works, but I can't have sound from a "real" source. When I right-click on KMix and click sound-settings I get a screen indicating the sound-cards are there, but only the Dummy-output is active, the rest is greyed out. I tried removing .kde4/share/config/kmixctrlrc and kmixrc, but that does nothing. I tried logging in as root, and there everything works. I added a test-user, and there I have the same problems : no dvd, no sound. I tried to open a data-dvd but that fails also. There I get a valid name, and a choice of applications to open the dvd. But selecting file-manager gives an error message. Journalctl -f says this when inserting a data-dvd, as regular user : systemd-udevd[3372]: Failed to apply ACL on /dev/sr0: Invalid argument inserting a video-dvd as regular user gives this : okt 26 21:44:15 lt19 kernel: sr 1:0:0:0: [sr0] okt 26 21:44:15 lt19 kernel: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE okt 26 21:44:15 lt19 kernel: sr 1:0:0:0: [sr0] okt 26 21:44:15 lt19 kernel: Sense Key : Illegal Request [current] okt 26 21:44:15 lt19 kernel: sr 1:0:0:0: [sr0] okt 26 21:44:15 lt19 kernel: Add. Sense: Read of scrambled sector without authentication okt 26 21:44:15 lt19 kernel: sr 1:0:0:0: [sr0] CDB: okt 26 21:44:15 lt19 kernel: Read(10): 28 00 00 00 04 00 00 00 02 00 okt 26 21:44:15 lt19 kernel: end_request: I/O error, dev sr0, sector 4096 okt 26 21:44:15 lt19 kernel: Buffer I/O error on device sr0, logical block 512 okt 26 21:44:15 lt19 systemd-udevd[3401]: Failed to apply ACL on /dev/sr0: Invalid argument okt 26 21:44:15 lt19 kernel: sr 1:0:0:0: [sr0] okt 26 21:44:15 lt19 kernel: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE okt 26 21:44:15 lt19 kernel: sr 1:0:0:0: [sr0] okt 26 21:44:15 lt19 kernel: Sense Key : Illegal Request [current] okt 26 21:44:15 lt19 kernel: sr 1:0:0:0: [sr0] okt 26 21:44:15 lt19 kernel: Add. Sense: Read of scrambled sector without authentication okt 26 21:44:15 lt19 kernel: sr 1:0:0:0: [sr0] CDB: okt 26 21:44:15 lt19 kernel: Read(10): 28 00 00 00 04 00 00 00 02 00 okt 26 21:44:15 lt19 kernel: end_request: I/O error, dev sr0, sector 4096 okt 26 21:44:15 lt19..be kernel: Buffer I/O error on device sr0, logical block 512 As root : a data-dvd shows nothing. A video-DVD gives this : Oct 26 21:48:39 lt19 kernel: sr 1:0:0:0: [sr0] Oct 26 21:48:39 lt19 kernel: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Oct 26 21:48:39 lt19 kernel: sr 1:0:0:0: [sr0] Oct 26 21:48:39 lt19 kernel: Sense Key : Illegal Request [current] Oct 26 21:48:39 lt19 kernel: sr 1:0:0:0: [sr0] Oct 26 21:48:39 lt19 kernel: Add. Sense: Read of scrambled sector without authentication Oct 26 21:48:39 lt19 kernel: sr 1:0:0:0: [sr0] CDB: Oct 26 21:48:39 lt19 kernel: Read(10): 28 00 00 00 04 00 00 00 02 00 Oct 26 21:48:39 lt19 kernel: end_request: I/O error, dev sr0, sector 4096 Oct 26 21:48:39 lt19 kernel: Buffer I/O error on device sr0, logical block 512 Oct 26 21:48:39 lt19 kernel: sr 1:0:0:0: [sr0] Oct 26 21:48:39 lt19 kernel: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Oct 26 21:48:39 lt19 kernel: sr 1:0:0:0: [sr0] Oct 26 21:48:39 lt19 kernel: Sense Key : Illegal Request [current] Oct 26 21:48:39 lt19 kernel: sr 1:0:0:0: [sr0] Oct 26 21:48:39 lt19 kernel: Add. Sense: Read of scrambled sector without authentication Oct 26 21:48:39 lt19 kernel: sr 1:0:0:0: [sr0] CDB: Oct 26 21:48:39 lt19 kernel: Read(10): 28 00 00 00 04 00 00 00 02 00 Oct 26 21:48:39 lt19 kernel: end_request: I/O error, dev sr0, sector 4096 Oct 26 21:48:39 lt19 kernel: Buffer I/O error on device sr0, logical block 512 As far as I can see, the difference is that ACL that does not work. Any suggestions where to look to debug this ? TIA, Koenraad. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

10 30

[opensuse] Leap 42.1 / Lenovo S21 / Touchpad & Wireless
by Adam Tauno Williams 28 Oct '16

28 Oct '16

I have a Lenovo S21 running Leap 42.1. The touch-pad - under kernel 4.1.34 - does not work. But it has never worked. The wireless - a BCM43142 - does work however. When subscribed to Kernel:stable the lenovo installed a 4.8.4 kernel - where the touch pad works but the BCM43142 wireless does not. Does anyone know the trick required to get the BCM43142 to work under a later kernel? I assume this is a firmware load issue. [or if it is possible to make the touchpad on such a device work with a 4.1.x kernel]. LSPCI - 00:00.0 Host bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register (rev 0e) 00:02.0 VGA compatible controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display (rev 0e) 00:14.0 USB controller: Intel Corporation Atom Processor Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI (rev 0e) 00:17.0 SD Host controller: Intel Corporation Atom Processor E3800 Series eMMC 4.5 Controller (rev 0e) 00:1a.0 Encryption controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine (rev 0e) 00:1b.0 Audio device: Intel Corporation Atom Processor Z36xxx/Z37xxx Series High Definition Audio Controller (rev 0e) 00:1c.0 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 1 (rev 0e) 00:1c.1 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 2 (rev 0e) 00:1f.0 ISA bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Power Control Unit (rev 0e) 00:1f.3 SMBus: Intel Corporation Atom Processor E3800 Series SMBus Controller (rev 0e) 01:00.0 Network controller: Broadcom Corporation BCM43142 802.11b/g/n (rev 01) 02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5229 PCI Express Card Reader (rev 01) -- Adam Tauno Williams <mailto:awilliam@whitemice.org> GPG D95ED383 openSUSE, a LINUX desktop for humans who need to get work done. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0