October 2016 - openSUSE Users - openSUSE Mailing Lists

[opensuse] Why is DISPLAYMANAGER_SHUTDOWN="root" ignored?
by Josef Wolf 01 Nov '16

01 Nov '16

Hello, I have DISPLAYMANAGER_SHUTDOWN="root" set in /etc/sysconfig/displaymanager But this setting seems to be ignored. Non-privileged users can still shutdown by choosing "shutdown" from their KDE menu. Why is this? BTW: this is opensuse Leap 42.1 -- 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 8

[opensuse] Debugging wifi
by Koenraad Lelong 31 Oct '16

31 Oct '16

Hi, I got a new accesspoint. Unfortunately, my OS 13.2 laptop can't connect to it. With older accesspoints I don't have problems. Is there any way to debug this ? I'm using Network-manager. Other computers can connect without problems. lspci on my laptop gives this : 45:00.0 Network controller: Broadcom Corporation BCM4313 802.11bgn Wireless Network Adapter (rev 01) Please ask if other info is needed. TIA, Koenraad. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 4

Re: [opensuse] dv camcorder and firewire IEEE1394
by Dave Plater 31 Oct '16

31 Oct '16

On 31/10/2016 13:56, Dave Plater wrote: > > > On 31/10/2016 10:16, jdd wrote: >> 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 >> > I maintain ffado (libffado2) which uses libraw1394-11 and supplies > firewire support for jack for the use of audio equipment so libraw > definitely still exists. I see that dvgrab, kinfocenter5 and > kdebase4-workspace-addons depend on it so firewire should work with > dvgrab. There's a libraw-tools package as well you can maybe find > something there. > Regards > Dave P > Sorry libraw-tools is not related, leap doesn't have libraw1394-tools. You can get it via 1 click install. Dave P -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 3

[opensuse] crashes in KDE file indexing daemon
by Mikhail Ramendik 31 Oct '16

31 Oct '16

Hello, When I download files in Chrome, I get a crash message about the KDE file indexing daemon. I try to go the bug reporting route, but it fails to install debug symbols. Is this some known issue I can fix? If not, then how do I install the debug symbols so I can let the bug be files? -- Yours, Mikhail Ramendik Unless explicitly stated, all opinions in my mail are my own and do not reflect the views of any organization -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

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

31 Oct '16

On Sat, 29 Oct 2016, John Andersen wrote: > On 10/29/2016 01:00 PM, Roger Price wrote: >> 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". > > Did you apply today's update Roger? This sounds like the same thing that has > been found in the DVD Gone / Sound Gone threads. > > There was a hozing of permissions in 13.2 which some indicate is due to the > fact that 13.2 dummys up permissions to physical things for anyone sitting at > the console. The work around is to manually add those groups to the user's > "Additional Groups" settings in yast Users and Groups (details tab), or wait > till they get the kernel fixed. I have applied all available 13.2 patches including openSUSE-2016-1241 Security update for the Linux Kernel but that does not fix the problem. Given the post by Marcus Meissner https://lists.opensuse.org/opensuse/2016-10/msg00737.html > Two days ago the 13.2 kernel update broke ACLs that give out these > rights, it will be back with a fix update soonish > No need for group member ship btw, all systemd / udev /acl magic these > days. I will wait for the upcoming update magic, and manage the lady´s administrative problem by non-IT means. Roger

1 0

[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