November 2019 - openSUSE Support - openSUSE Mailing Lists

[opensuse-support] Re: [opensuse-factory] Qemu 4.1. and TW
by Simon Lees 12 Nov '19

12 Nov '19

Hi, This really is a support question please use the support list instead opensuse-support(a)opensuse.org On 11/12/19 11:28 PM, Frans de Boer wrote: > I can't get Qemu 4.1.0 to make a network connection using Win 10 as a > client under TW. > Qemu 3.1.1.1 works fine under TW. The 4.1 under under 15.1 works also. > All with the same image. > > This my command line: > > qemu-system-x86_64 -snapshot -name telewerken -cpu phenom -smp > cores=2,threads=1,sockets=1 -enable-kvm -machine type=q35,accel=kvm -m > 3072 -soundhw hda -net > nic,model=virtio-net-pci,macaddr=52:54:63:1f:a0:00 -net > tap,ifname=tap0,script=/etc/qemu/qemu-ifup,downscript=/etc/qemu/qemu-ifdown > -vga std -display gtk -rtc clock=host,base=localtime -boot order=c -usb > -device usb-tablet -drive > file=./telewerken.raw,format=raw,index=0,media=disk,if=virtio,cache=writeback > > configuring qemu network with bridge for tap0 > qemu-ifdown: Removing tap0 from Bridge br0 > + sudo /sbin/tunctl -d tap0 > > Works already several years under TW,, 15.1 and pevious versions. It > stopped working since the end of the summer when switching to kernel > 5.1+(?) > > Suggestions? > > --- Frans. > -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B

1 0

[opensuse-support] Tumbleweed problem with UDisks2
by Patrick Shanahan 11 Nov '19

11 Nov '19

systemctl status udisks2.service reports: ● udisks2.service - Disk Manager Loaded: loaded (/usr/lib/systemd/system/udisks2.service; disabled; vendor preset: disabled) Active: activating (start) since Sun 2019-11-10 14:25:32 EST; 41s ago Docs: man:udisks(8) Main PID: 7447 (udisksd) Tasks: 6 (limit: 4915) Memory: 6.8M CGroup: /system.slice/udisks2.service ├─7447 /usr/lib/udisks2/udisksd ├─7464 /bin/sh -f /usr/sbin/xfs_info /data └─7471 xfs_spaceman -p xfs_info -c info /data Nov 10 14:25:32 crash systemd[1]: Starting Disk Manager... Nov 10 14:25:32 crash udisksd[7447]: udisks daemon version 2.8.3 starting Nov 10 14:25:32 crash udisksd[7447]: Error initializing polkit authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: Unit polkit.service is masked. (g-io-error-quark, 36) Nov 10 14:25:32 crash udisksd[7447]: Can't load configuration file /etc/udisks2/udisks2.conf polkit has never been a problem and udisks2.conf has always been "missing". attempting systemctl reload udisks2.service provides: http://wahoo.no-ip.org/~paka/udisks2.fail.txt mentioned disk sda has and continues to report good in smartctl. udisks2 failure causes great delay generating initial plasma5 desktop and some apps such as gwenview. I do not know where to go to correct or trouble-shoot udisks2 failure. tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

2 6

[opensuse-support] Is $HOME/bin added by default to $PATH?
by Robert Munteanu 11 Nov '19

11 Nov '19

Hi, I am having trouble understanding whether $HOME/bin should automatically be added to $PATH or if I should add it myself in $HOME/.bashrc. I recall this was working out of the box at some point but now it does not. I looked in /etc/skel and /etc/profile.d but did not find any indication that it should be set. Is $HOME/bin added by default to $PATH? Thanks, Robert -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

9 17

[opensuse-support] How to fix btrfs Csum failure of root partition?
by CnZhx 11 Nov '19

11 Nov '19

Dear all, Recently I got a lot of kernel panics with my openSUSE Tumbleweed laptop. Today, it brings me a rescue screen after reboot from a panic. It says the btrfs system of my root partition has failure of Csum. I put in root password and run 'btrfs rescue --init-chunk-tree' but failed. Any ideas to bring the system up without reinstallation? Regards, Haoxian

5 4

[opensuse-support] plasmashell heavy cpu usage
by Patrick Shanahan 10 Nov '19

10 Nov '19

the last several issues of Tw, currently 20190930, display heavy cpu usage of plasmashell System: Host: crash Kernel: 5.3.1-1-default x86_64 bits: 64 compiler: gcc v: 9.2.1 Desktop: KDE Plasma 5.16.5 tk: Qt 5.13.1 wm: kwin_x11 dm: SDDM Distro: openSUSE Tumbleweed 20190930 Machine: Type: Desktop Mobo: Intel model: DX58SO2 v: AAG10925-205 serial: <root required> BIOS: Intel v: SOX5820J.86A.0920.2013.0729.0042 date: 07/29/2013 CPU: 6-Core: Intel Core i7 970 type: MT MCP arch: Nehalem speed: 1824 MHz min/max: 1596/3193 MHz Graphics: Device-1: NVIDIA GF106 [GeForce GTS 450] vendor: PNY driver: nvidia v: 390.129 bus ID: 03:00.0 chip ID: 10de:0dc4 Display: x11 server: X.Org 1.20.5 driver: nvidia unloaded: fbdev,modesetting,nouveau,vesa alternate: nv compositor: kwin_x11 resolution: 1920x1080~60Hz, 1920x1080~60Hz OpenGL: renderer: llvmpipe (LLVM 8.0 128 bits) v: 3.3 Mesa 19.1.7 compat-v: 3.1 direct render: Yes runlevel: 35 target: multi-user.target Compilers: gcc: 9.2.1 alt: 8/9 clang: 8.0.1 Shell: bash v: 5.0.11 running in: xterm inxi: 3.0.32 USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND paka 19251 90.9 1.0 2311648 389256 ? Sl Oct02 633:01 /usr/bin/plasmashell note that 90.9% cpu is heavy for plasmashell but not for system with effectively 12 cores. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

1 1

[opensuse-support] battery: ACPI: Deprecated procfs I/F for battery is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
by Marco Calistri 03 Nov '19

03 Nov '19

Hello, I suppose that there is no way to set "CONFIG_ACPI_PROCFS_POWER=" parameter unless recompiling the default kernel. In my system such parameter is set as YES: grep ACPI_PROCFS_POWER /boot/config-`uname -r` CONFIG_ACPI_PROCFS_POWER=y At least I've not found nothing relating a way to set this "on the fly", if I'm wrong please correct me and indicate a procedure. It seems that this topic is a sort of an old kernel request which is not yet been defined/resolved along several years so it is affecting a lot of user. What I have noticed in the last days is that my BAT statistics are now completely inaccurate. Thanks and regards, -- Marco Calistri Build: openSUSE Tumbleweed 20191030 Kernel: 5.3.7-1-default - Cinnamon 3.8.9 -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

3 5

[opensuse-support] /usr/lib/at-spi2/at-spi2-registryd - Extremely high CPU consuming!
by Marco Calistri 03 Nov '19

03 Nov '19

Hello, Recently I noticed an extremely high CPU load with consequent abnormal CPU heating and then I discovered that the cause was /usr/lib/at-spi2/at-spi2-registryd attempting to execute an infinite series of tasks which were failing one after the other. Attempting to uninstall the at-spi2-core was not possible due the fact of hundreds of packages dependencies belong on this single package (reason not understandable by me). To workaround the issue I done: 1 - sudo chmod ugo-x /usr/lib/at-spi2/at-spi2-registryd 2 - sudo rm /usr/share/dbus-1/accessibility-services/org.a11y.atspi.Registry.service Thanks for your attention. Regards, -- Marco Calistri Build: openSUSE Tumbleweed 20191024 Kernel: 5.3.7-1-default - Cinnamon 3.8.9 -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

7 18