October 2016 - openSUSE Users - openSUSE Mailing Lists

[opensuse] dv camcorder and firewire IEEE1394
by jdd 31 Oct '16

31 Oct '16

Hello, I have an old camcorder, DV one, that use IEEE1384/Firewire interface. I also have a 6 years old HP computer that have a IEEE1394 that used to work with openSUSE. But I didn't use it for at least 4 years now :-( I can't make it work right now. dvgrab says it do not find the camcorder (connected, on "pause" in reader mode). I know raw1394 do not exists anymore (does it?) and is replaced by firewireXXX module, but even with modeprobing this module (modprobe firewire-ohci), no luck, same message - no /dev/fw* device # lsmod | grep fir firewire_ohci 45056 0 firewire_core 73728 1 firewire_ohci crc_itu_t 16384 1 firewire_core any user here? thanks jdd -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Amarok crash and KDE wierdness
by George from the tribe 31 Oct '16

31 Oct '16

Anyone else getting Amarok to crash whenever you try and open it? Here is what happens: > amarok KCrash: Application 'amarok' crashing... KCrash: Attempting to start /usr/lib64/kde4/libexec/drkonqi from kdeinit KCrash: Connect sock_file=/home/george/.kde4/socket-tribaltrekker/kdeinit4__0 unnamed app(8642): Communication problem with "amarok" , it probably crashed. Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Message did not receive a reply (timeout by message bus)" " It doesn't seem to give much information. I think there is something wrong with my system - KDE has been acting strangely lately. Kwin is crashing very frequently, and for a while on startup my screens would all just blink until I clicked in the middle of the screen. What is the best suggestion of how to reset KDE to a factory default setting? I have heard I can just delete the .config file, but I am hesitant to do that just yet. -- 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

2 4

[opensuse] changing a user passwd via root (13.2: Authentication token manipulation error (?))
by L. A. Walsh 30 Oct '16

30 Oct '16

Having an odd experience here, in that I wanted to create another userid to test something with. Noticed I already had a testid for that purpose, tried to use it but password was invalid. So went to reset it with sudo passwd testuser and expected it to ask for new passwd and to repeat it. Instead I got: passwd: Authentication token manipulation error passwd: password unchanged Anyone know why I might get this and how it should be fixed? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

6 7

[opensuse] is it possible to create rpm from installed package?
by Felix Miata 30 Oct '16

30 Oct '16

I forgot to lock mc before updating TW installation #2 on host hpg33, resulting in 4.8.17 being replaced by 4.8.18. Nothing in between 4.8.15 and 4.8.18 exists in any openSUSE repo that I can find. https://software.opensuse.org/search returns no Midnight Commander package due to https://bugzilla.opensuse.org/show_bug.cgi?id=930505 and/or https://github.com/openSUSE/software-o-o/issues/61 or maybe neither. I have other TW installations that still have 4.8.17, including host hpg33, which unlike 4.8.18 is not broken, so I would like to be able to use it. Is $SUBJECT possible? -- "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

4 15

[opensuse] xfs error won't repair
by John Andersen 30 Oct '16

30 Oct '16

I have a /home partition using luks on xfs I've got two little files that barfed up errors while running a backup. Any attempt to access these files results in an error: > poulsbo:/home # l ./jsa/.cache/google-chrome/Default/old_Cache_000/f_0259ff > ls: cannot access ./jsa/.cache/google-chrome/Default/old_Cache_000/f_0259ff: Structure needs cleaning If I list the entire directory I get this: > poulsbo:/home # l ./jsa/.cache/google-chrome/Default/old_Cache_000/ > ls: cannot access ./jsa/.cache/google-chrome/Default/old_Cache_000/f_0259ff: Structure needs cleaning > total 70772 > drwx------ 2 jsa users 94208 May 31 12:38 ./ > drwx------ 5 jsa users 59 Jun 2 14:37 ../ > -rw------- 1 jsa users 10231808 May 31 12:31 data_4 ...snip > -rw------- 1 jsa users 32938 Feb 14 2016 f_020630 > -????????? ? ? ? ? ? f_0259ff > -rw------- 1 jsa users 33622 Mar 17 2016 f_025fef Over on the XFS site Faq them mumble something about question marks in the directory listing suggest you might need inode64, but its only a 500gig drive and this seems unwise at this poing. These also dumped the following into my log: > Oct 27 17:37:20 poulsbo.homeip.net kernel: XFS (dm-1): xfs_iread: validation failed for inode 537556822 failed > Oct 27 17:37:20 poulsbo.homeip.net kernel: ffff8800a928fc00: 49 4e 81 80 03 02 00 00 00 00 03 e8 00 00 00 64 IN.............d > Oct 27 17:37:20 poulsbo.homeip.net kernel: ffff8800a928fc10: 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 ................ > Oct 27 17:37:20 poulsbo.homeip.net kernel: ffff8800a928fc20: 56 e9 94 78 12 00 ec 9f 56 e9 94 78 12 10 2e c5 V..x....V..x.... > Oct 27 17:37:20 poulsbo.homeip.net kernel: ffff8800a928fc30: 56 e9 94 78 12 10 2e c5 00 00 00 00 00 02 72 5d V..x..........r] > Oct 27 17:37:20 poulsbo.homeip.net kernel: XFS (dm-1): Internal error xfs_iread at line 392 of file ../fs/xfs/xfs_inode_buf.c. Caller xfs_iget+0x298/0x7f0 [xfs] > Oct 27 17:37:21 poulsbo.homeip.net kernel: CPU: 1 PID: 16839 Comm: ls Not tainted 3.16.7-45-desktop #1 > Oct 27 17:37:21 poulsbo.homeip.net kernel: Hardware name: Dell Inc. MP061 /0YD479, BIOS A08 04/02/2007 > Oct 27 17:37:21 poulsbo.homeip.net kernel: 0000000000000001 ffffffff8161e1f6 ffff8800a203f000 ffffffffa07e506b > Oct 27 17:37:21 poulsbo.homeip.net kernel: 00000188ba9be7c0 ffffffffa07eadb8 ffff88001f091400 ffff8800a203f000 > Oct 27 17:37:21 poulsbo.homeip.net kernel: 0000000000000075 0000000000000000 ffffffffa0832eba ffffffffa07eadb8 > Oct 27 17:37:21 poulsbo.homeip.net kernel: Call Trace: > Oct 27 17:37:21 poulsbo.homeip.net kernel: [<ffffffff810051ee>] dump_trace+0x8e/0x350 > Oct 27 17:37:21 poulsbo.homeip.net kernel: [<ffffffff81005556>] show_stack_log_lvl+0xa6/0x190 > Oct 27 17:37:21 poulsbo.homeip.net kernel: [<ffffffff81006aa1>] show_stack+0x21/0x50 > Oct 27 17:37:21 poulsbo.homeip.net kernel: [<ffffffff8161e1f6>] dump_stack+0x49/0x6a > Oct 27 17:37:21 poulsbo.homeip.net kernel: [<ffffffffa07e506b>] xfs_corruption_error+0x5b/0x80 [xfs] > Oct 27 17:37:21 poulsbo.homeip.net kernel: [<ffffffffa0832eba>] xfs_iread+0xea/0x400 [xfs] > Oct 27 17:37:21 poulsbo.homeip.net kernel: [<ffffffffa07eadb8>] xfs_iget+0x298/0x7f0 [xfs] > Oct 27 17:37:21 poulsbo.homeip.net kernel: [<ffffffffa082cf2e>] xfs_lookup+0xee/0x110 [xfs] > Oct 27 17:37:21 poulsbo.homeip.net kernel: [<ffffffffa07f0306>] xfs_vn_lookup+0x56/0xa0 [xfs] > Oct 27 17:37:21 poulsbo.homeip.net kernel: [<ffffffff811c1a59>] lookup_real+0x19/0x50 > Oct 27 17:37:21 poulsbo.homeip.net kernel: [<ffffffff811c234f>] __lookup_hash+0x2f/0x40 > Oct 27 17:37:21 poulsbo.homeip.net kernel: [<ffffffff8161b550>] lookup_slow+0x3e/0xa3 > Oct 27 17:37:21 poulsbo.homeip.net kernel: [<ffffffff811c52a5>] path_lookupat+0x725/0x790 > Oct 27 17:37:21 poulsbo.homeip.net kernel: [<ffffffff811c5336>] filename_lookup+0x26/0xc0 > Oct 27 17:37:21 poulsbo.homeip.net kernel: [<ffffffff811c8b54>] user_path_at_empty+0x54/0x90 > Oct 27 17:37:21 poulsbo.homeip.net kernel: [<ffffffff811bd2d6>] vfs_fstatat+0x46/0x90 > Oct 27 17:37:21 poulsbo.homeip.net kernel: [<ffffffff811bd7ad>] SYSC_newlstat+0x1d/0x40 > Oct 27 17:37:21 poulsbo.homeip.net kernel: [<ffffffff81624f0d>] system_call_fastpath+0x1a/0x1f > Oct 27 17:37:21 poulsbo.homeip.net kernel: [<00007fecc5b6dd35>] 0x7fecc5b6dd34 > Oct 27 17:37:21 poulsbo.homeip.net kernel: XFS (dm-1): Corruption detected. Unmount and run xfs_repair So I did as directed, unmounted it and ran xfs_repair on the /dev/mapper/cr_yaddayadda device that represents the encrypted partition /dev/sda4. (it is said to be pointless and dangerous to run xfs_repair on the actual underlying device. Is this true? Its still xfs underneath is it not? ). After multiple such runs, no error is found by xfs_repair, and the problem is not repaired. smartctl shows no errors and no sectors having been re-mapped. The drive appears physically fine. So how do I proceed from here? I have two such little files that barf in the log each time I even try to peek at them. -- 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

7 28

[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