October 2016 - openSUSE Users - openSUSE Mailing Lists

[opensuse] Client failed to connect to the D-BUS daemon
by Istvan Gabor 13 Oct '16

13 Oct '16

Hello: I would like to run deluge on openSUSE 13.1 with KDE3 desktop. When I run deluge, I get a list of errors: ~> deluge (deluge:26545): GConf-WARNING **: Client failed to connect to the D-BUS daemon: Failed to connect to socket /tmp/dbus-zceXBHrC2m: Connection refused (deluge:26545): GConf-WARNING **: Client failed to connect to the D-BUS daemon: Failed to connect to socket /tmp/dbus-zceXBHrC2m: Connection refused (deluge:26545): GConf-WARNING **: Client failed to connect to the D-BUS daemon: Failed to connect to socket /tmp/dbus-zceXBHrC2m: Connection refused (deluge:26545): GConf-WARNING **: Client failed to connect to the D-BUS daemon: Failed to connect to socket /tmp/dbus-zceXBHrC2m: Connection refused (deluge:26545): GConf-WARNING **: Client failed to connect to the D-BUS daemon: Failed to connect to socket /tmp/dbus-zceXBHrC2m: Connection refused (deluge:26545): GConf-WARNING **: Client failed to connect to the D-BUS daemon: Failed to connect to socket /tmp/dbus-zceXBHrC2m: Connection refused Traceback (most recent call last): File "/usr/bin/deluge", line 9, in <module> load_entry_point('deluge==1.3.11', 'gui_scripts', 'deluge')() File "/usr/lib/python2.7/site-packages/deluge/main.py", line 132, in start_ui UI(options, args, options.args) File "/usr/lib/python2.7/site-packages/deluge/ui/ui.py", line 150, in __init__ ui = GtkUI(args) File "/usr/lib/python2.7/site-packages/deluge/ui/gtkui/gtkui.py", line 233, in __init__ common.associate_magnet_links(False) File "/usr/lib/python2.7/site-packages/deluge/ui/gtkui/common.py", line 255, in associate_magnet_links if (gconf_client.get(key) and overwrite) or not gconf_client.get(key): glib.GError: No D-BUS daemon running dbus-daemon is running. ~> ps -e|grep dbus 1494 ? 00:00:05 dbus-daemon I know nothing about dbus but deluge used to work earlier. How could I fix this? Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 3

[opensuse] Sound card setup fails in Leap42.1
by Marc Chamberlin 13 Oct '16

13 Oct '16

OK this is weird, I tried to use YaST to set up my sound card and things went backwards on me... I used the Sound configuration tool within YaST, and I tried each of the setup options, Quick, Normal, and Advance to configure the card. While in the Sound configuration everything works fine, I test the sound and hear it from the speakers OK. And the messages log file indeed report that systemd does start the sound card OK. But when I go and save the sound configuration, exiting the sound configuration tool at the same time, when it reaches the stage where it says the tool says it is turning on the sound card, I lose the sound! And systemd is reporting, at the point that the tool is saying it is turning on the sound card, that the "sound.target is not needed any more." and turns off the sound card instead! Output from the messages log shows that indeed the sound got turned on while I was within the sound configuration tool and then off for some reason when I exit and save the sound configuration. What gives? Marc.. Here I am starting up the sound configuration tool within YaST and having it configure the sound card settings for me - 2016-10-11T17:35:56.634304-07:00 bigbang kernel: [ 5727.069747] snd_hda_codec_idt hdaudioC0D2: autoconfig for STAC9221D A2: line_outs=3 (0xd/0xb/0xf/0x0/0x0) type:line 2016-10-11T17:35:56.634330-07:00 bigbang kernel: [ 5727.069755] snd_hda_codec_idt hdaudioC0D2: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) 2016-10-11T17:35:56.634333-07:00 bigbang kernel: [ 5727.069759] snd_hda_codec_idt hdaudioC0D2: hp_outs=1 (0xa/0x0/0x0/0x0/0x0) 2016-10-11T17:35:56.634335-07:00 bigbang kernel: [ 5727.069763] snd_hda_codec_idt hdaudioC0D2: mono: mono_out=0x0 2016-10-11T17:35:56.634337-07:00 bigbang kernel: [ 5727.069766] snd_hda_codec_idt hdaudioC0D2: dig-out=0x10/0x0 2016-10-11T17:35:56.634339-07:00 bigbang kernel: [ 5727.069769] snd_hda_codec_idt hdaudioC0D2: inputs: 2016-10-11T17:35:56.634341-07:00 bigbang kernel: [ 5727.069774] snd_hda_codec_idt hdaudioC0D2: Rear Mic=0xe 2016-10-11T17:35:56.634343-07:00 bigbang kernel: [ 5727.069778] snd_hda_codec_idt hdaudioC0D2: Front Mic=0x15 2016-10-11T17:35:56.634345-07:00 bigbang kernel: [ 5727.069781] snd_hda_codec_idt hdaudioC0D2: Line=0xc 2016-10-11T17:35:56.679442-07:00 bigbang kernel: [ 5727.113637] input: HDA Intel Rear Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input44 2016-10-11T17:35:56.679457-07:00 bigbang kernel: [ 5727.113810] input: HDA Intel Line as /devices/pci0000:00/0000:00:1b.0/sound/card0/input45 2016-10-11T17:35:56.679460-07:00 bigbang kernel: [ 5727.113969] input: HDA Intel Line Out Front as /devices/pci0000:00/0000:00:1b.0/sound/card0/input46 2016-10-11T17:35:56.679463-07:00 bigbang kernel: [ 5727.114114] input: HDA Intel Line Out Surround as /devices/pci0000:00/0000:00:1b.0/sound/card0/input47 2016-10-11T17:35:56.679465-07:00 bigbang kernel: [ 5727.114262] input: HDA Intel Line Out CLFE as /devices/pci0000:00/0000:00:1b.0/sound/card0/input48 2016-10-11T17:35:56.679468-07:00 bigbang kernel: [ 5727.114448] input: HDA Intel Front Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input49 2016-10-11T17:35:56.946038-07:00 bigbang systemd[1]: Starting Sound Card. 2016-10-11T17:35:56.959303-07:00 bigbang systemd[1]: Reached target Sound Card. at this point I am within the sound configuration tool and sound is working fine. When I go to exit the sound configuration tool and save the settings, this is what happens - 2016-10-11T17:37:06.072618-07:00 bigbang systemd-udevd[508]: Network interface NamePolicy= disabled on kernel commandline, ignoring. 2016-10-11T17:37:06.157274-07:00 bigbang systemd[1]: Unit sound.target is not needed anymore. Stopping. 2016-10-11T17:37:06.164995-07:00 bigbang systemd[1]: Stopping Sound Card. 2016-10-11T17:37:06.165905-07:00 bigbang systemd[1]: Stopped target Sound Card. -- "The Truth is out there" - Spooky -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 2

[opensuse] Encrypted root with LUKSdon't work anymore with opensuse-Leap-42.1. Help?
by Josef Wolf 12 Oct '16

12 Oct '16

Hello, I am using the scheme outlined below to install opensuse with encrypted root partition. The detailed description how I do this, is described below in this post. This scheme worked great since about 2008 (don't remember which opensuse release it was in 2008) up to opensuse-13.1, with minor tweaks at every new opensuse release. Unfortunately, with opensuse-Leap-42.1 it don't work anymore. When booting the new encrypted root, it won't ask for the passphrase. It just hangs. It looks as if the contents of initrd don't know how to ask for the passphrase. Any ideas how to track down the problem? Here is the procedure how I do it: Install base system with a partitioning scheme like this: /dev/sda1 1g ext2 /boot (unencrypted) /dev/sda2 20g ext4 / (unencrypted) /dev/sda3 20g swap swap (encrypted) /dev/sda4 20g none (encrypted root will go here later) (device names are just examples here) When the base system is installed, I do the following: # create new encrypted filesystem # cryptsetup -v --key-size 256 luksFormat /dev/sda4 cryptsetup luksOpen /dev/sda4 cr_sda4 mkfs.ext4 -O dir_index /dev/mapper/cr_sda4 # mount old (unencrypted) and new (crypted) root filesystems # SRCMNT=/tmp/root-src-$$ DSTMNT=/tmp/root-dst-$$ mkdir -p $SRCMNT $DSTMNT mount -obind / $SRCMNT mount /dev/mapper/cr_sda4 $DSTMNT # copy contents from unencrypted root to encrypted root # rsync -ax $SRCMNT/ $DSTMNT sync cp /boot/initrd /boot/initrd.backup # Fix up /etc/fstab on new root (remove old root and add new root to fstab) # perl -ani.bak -e "s#^\S+#/dev/mapper/cr_sda4# if \$F[1] eq '/'; \ print unless \$F[0] eq '/dev/mapper/cr_sda4'" \ $DSTMNT/etc/fstab # set grub2 defaults on new root (no splash, no resume, quiet boot) # perl -pi.bak -e "s#splash=\S+##; s#resume=\S+#noresume#; s#quiet##;" \ $DSTMNT/etc/default/grub # make sure grub2-mkconfig can search for operating systems within encrypted root # mount -obind /dev $DSTMNT/dev mount -obind /sys $DSTMNT/sys mount -obind /proc $DSTMNT/proc mount -obind /boot $DSTMNT/boot # Create /boot/grub2/grub.cfg # cp /boot/grub2/grub.cfg /boot/grub2/grub.cfg.backup chroot $DSTMNT /usr/sbin/grub2-mkconfig --output=/boot/grub2/grub.cfg # add crypt modules to initrd # mkinitrd -d /dev/mapper/cr_sda4 -f "dm luks" # Clean up and reboot # sync umount $DSTMNT/proc umount $DSTMNT/boot umount $DSTMNT/dev umount $DSTMNT/sys/fs/fuse/connections # FIXME: what the heck? umount $DSTMNT/sys umount $DSTMNT && rmdir $DSTMNT umount $SRCMNT && rmdir $SRCMNT cryptsetup luksClose cr_sda4 sync reboot -- 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

3 7

[opensuse] System slowdowns
by Marc Chamberlin 12 Oct '16

12 Oct '16

Hi - I am running an OpenSuSE Leap 42.2 system on an x64 system with a dual core processor. While using it I am experiencing periods of up to several minutes where I can hear the processor's cooling fan speed up and the system's responsiveness slows way down to where it is unusable. During these episodes I have had KSysguard running and top executing in a shell to see if I can figure out what is causing these episodes. The KSysguard graphical display will show that both processors are running at or near 100% yet the process table and top both show that the running processes are taking only a few percent (typically less than 4 or 5% for the worst process) and the total percentage of CPU time being used for all processes is nowhere near the 100% shown by the cpu usage graph. So how do I track down what application, process, or system service is chewing up my processors. I am experiencing these slowdowns approx 5 to 10 times per hour which is quite frustrating. I kinda suspect it is Firefox but I cannot say that definitively.. Suggestions? Marc.. -- "The Truth is out there" - Spooky -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

6 18

Re: [opensuse] System slowdowns
by Marc Chamberlin 12 Oct '16

12 Oct '16

On 10/5/2016 12:37 AM, John Andersen wrote: > On 10/04/2016 11:21 PM, Marc Chamberlin wrote: >> On 10/4/2016 6:04 PM, John Andersen wrote: >>> On 10/04/2016 05:29 PM, Marc Chamberlin wrote: >>>>> The mouse problems seem worth investigating. Maybe dig in the junk drawer for a totally >>>>> different kind of mouse (serial, bluetooth, usb-wired) and see if that changes anything. >>>>> >>>> Thanks John for your suggestion. I tried a different mouse and no joy... Marc.... >>>> >>> Remind me again what kernel you are using, and what version of Vbox? >>> I tend to purge my list mail fairly aggressivly. >> Hi John - I am running Leap 42.1 (x86_64) I am not running VBox, (which I think what you are >> referring to is VirtualBox?) Interesting that you should ask though because I am playing around with >> Docker. However, I don't think my system slowdowns has anything to do with Docker as these slowdown >> issues preceded my installation of Docker. And these slowdowns occur regardless of whether Docker is >> running or not. (The only reason I am fooling around with Docker, FYI, is so I can get the latest >> version of the Apache James email server up and running, something that OpenSuSE does not directly >> support.) >> >> Marc.... >> >> > > So that was originally kernel 4.1. Are you still on that or have you upgraded? > > It might be worth trying to boot with > iomem=relaxed > > added to the kernel command line. > > It might not do anything but slowness has been detected in several distros > as soon as kernel updates were applied due to tighter memory security. > > > > Thanks John for the thought, I tried adding the iomem=relaxed option to the kernel options using the Yast Boot Loader tool, rebooted, and still no joy... In my fooling around with this issue, I have come across something that definitely triggers high CPU usage, and could be a clue. Although I cannot definitively say this is the smoking gun because I see high system CPU usage going on regardless of whether I do this or not - There is something very wrong going on when I use Dolphin to move stuff to the trash "Recycle Bin" (or sometimes it appears when I use Dolphin to simply move files from one location to another, i.e. drag and drop) and/or when I tell Dolphin to empty the trash. Doing so kicks off the 100% CPU usage and I hear the processor cooling fans kick into high speed. These tasks can take hours or even days to complete (if ever, some are still going on for over a week now. When I reboot the system, these tasks are not initially restarted, but if I do something like open the Recycle Bin to see if the files are still in it (after I told Dolphin to empty the trash) then these processes again kick off and the CPU usage goes up to 100%. The two (or more) spawned processes of interest are file.so and trash.so. However, unlike my original report and observations, these processes do report very high CPU usage also in the Process Table tab of KSystemGuard, top, atop, and htop so I am not 100% certain that this is related to the issue I reported - about something hidden is causing high CPU usage. Of interest also is doing file moves or deletes from the command line, i.e. using the mv, rm, and rmdir commands does not cause this high CPU usage to occur and those commands complete in a reasonable amount of time. Marc... -- "The Truth is out there" - Spooky -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 20

[opensuse] Question about Grub2
by Marc Chamberlin 12 Oct '16

12 Oct '16

Hello - am going to start a new thread for this question. In my recent set of machinations with setting up a new disk for my system, to replace one that may be failing, I encountered a problem for which I couldn't find an easy answer. It appears that when I tell the YaST boot loader setup tool to configure and create a new MBR it does so on the same disk which has the partition that contains the OS files. My system now has 4 drives installed and the BIOS only allows me to select just 3 drives (it's choice as to which 3 drives I get to choose from) to specify the order in which to search the drives for a boot loader. And my new drive now contains the partition which contains my Leap42.1 system. Because I was adding a new 4rth drive, the BIOS is not presenting the new drive to me as one of the options to use for setting up the search order, for a boot loader. I finally managed to get the BIOS to present it by disconnecting one of the other drives but that is an unacceptable solution in the long run. BTW the way I managed to boot up the Leap42.1 system was to boot up an older SuSE system located on one of the other drives and use Yast there to discover all the available OS's, create a boot menu for them, and then use the MBR/Grub menu it wrote out to select the Leap42.1 system. That works, but it took a lot of head scratching to figure out that was what I needed to do. So my question is this - is there some way to tell the YaST boot setup tool that I want to specify which drive that I want it to create an MBR on? Marc... -- "The Truth is out there" - Spooky -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 8

[opensuse] samba provision fails
by Egon Alter 11 Oct '16

11 Oct '16

Hi, I try to setup a samba dc server on OS42.1. It should use ldap as a backend. Unfortunately, "net sam provision" fails, because it cannot add the required windows groups "domusers, ...". I found that this is due to the rfc2307bis ldap schema which suse uses as default (and cannot be changed). I can get into details, but just want to know if someone has/had the same problem in the past. Egon -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] fingerprint reader in leap 42.1?
by Mathias Homann 10 Oct '16

10 Oct '16

Hi, am I blind or is there no support for fingerprint readers for authentication in Leap 42.1? Cheers Mathias -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 5

Re: [opensuse] fingerprint reader in leap 42.1?
by stakanov＠freenet.de 10 Oct '16

10 Oct '16

> -----Ursprüngliche Nachricht----- > Von: jdd > Gesendet: Mo. 10.10.2016 16:59 > An: opensuse(a)opensuse.org > Betreff: Re: [opensuse] fingerprint reader in leap 42.1? > > Le 10/10/2016 à 16:47, Mathias Homann a écrit : >> Am 10/10/2016 um 04:37 PM schrieb jdd: >>> Le 10/10/2016 à 15:25, Mathias Homann a écrit : >>>> am I blind or is there no support for fingerprint readers for >>>> authentication in Leap 42.1? >>>> >>> I think there is, but very minimal. I have one pn one laptop but don't >>> know how to use it (it's simply not seen as far as I can see) >> >> I'd call that "no support", not just minimal... Weird part is, according >> to the sdb articles I've found there used to be support, in yast even. >> >> >> Cheers >> MH >> >> > may be I simply misunderstood something, and the fingerprint reader I > have if special, even difficult to use in windows (and unusable in > windows 10) https://software.opensuse.org/package/libfprint is the package for Leap. I suppose this below will work also for leap: https://forums.opensuse.org/showthread.php/506187-Fingerprint-Reader-and-op… AFAIK the fingerprint support in yast was not maintained in leap etc because of lack of resources. --- Die Bundesliga hat begonnen! Alle Tore, alle Ergebnisse, alle News: Pocket Liga jetzt im https://app.adjust.com/dpynzd oder https://app.adjust.com/dpynzd herunterladen - kostenlos! -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Starting XFCE : mysterious assistance from TWM
by ellanios82 10 Oct '16

10 Oct '16

Hello List, - when starting XFCE in the morning : usually takes 10 to 15 minutes, and leaves a ton of stuff about core.xfsettingsd in /var/lib/systemd/coredump ................ - Mysteriously, happened to momentarily start TWM BEFORE starting XFCE : this resulted in almost instantaneous install of XFCE and without any dump in /var/lib/systemd/coredump ........ regards -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0