May 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1087277] New: Upgrade from Leap 42.3 to 15.0 Beta gives segmentation fault when trying to start KDE session
by bugzilla_noreply＠novell.com 29 Jan '20

29 Jan '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1087277 Bug ID: 1087277 Summary: Upgrade from Leap 42.3 to 15.0 Beta gives segmentation fault when trying to start KDE session Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: freek(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 765230 --> http://bugzilla.opensuse.org/attachment.cgi?id=765230&action=edit ksmserver.kcrash.txt First I describe the test setup, second the results. I have two spare ext4 partitions on my multi boot system with Leap 42.3, Tumbleweed and a newly installed Leap 15.0 Beta. I copied the home and system partition of 42.3 to the two spare partitions, each with a new label. The spare partitions are newly formatted with ext4 and both got a new unique label. I copied, using "rsync -a .." the root and home partition of the existing 42.3 to these new partitions. On the new system partition I changed in /etc/fstab the labels for / and /home to the new assigned labels. All partitions are mounted by label in /etc/fstab. I booted the latest image of Leap 15.0 Beta from a USB disk and performed an upgrade on the new partition with the copied 42.3 system. The old 42.3 system is still intact. The 42.3 system also has repository Education, KDE:Extra and Packman, so I had to resolve some conflicts and delete unavailable packages. But all in all I ended with an upgraded 42.3 to 15.0 Beta. However the bootloader showed some problems. Error message about /boot/grub2/device.map, which contained twice hd0. After the reboot only the old 42.3 system was bootable, the other three were not, although mentioned in the GRUB menu. I inspected /boot/grub2/ device.map and removed double entries, not only hd0, but also hd3, I used yast->bootloader to generate a new grub. I was able to boot all 4 systems. The upgraded 42.3 to 15.0 system showed a login screen and I entered the password. However after that, two application showed a segmentation fault, kdmserver and akonadictl. I was unable to use drkonqi to make a traceback, but some information about a traceback could be saved (see attachement). Apparently some information on the home partition causes this. The solution I found was to delete /home/<user>/.cache, after which I was able to login. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1082023] New: git send-email fails to authenticate with SMTP server
by bugzilla_noreply＠novell.com 29 Jan '20

29 Jan '20

http://bugzilla.suse.com/show_bug.cgi?id=1082023 Bug ID: 1082023 Summary: git send-email fails to authenticate with SMTP server Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: ohering(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- With current Tumbleweed git send-email fails to authenticate with the SMTP server. This used to work. since I rarly use git send-email I cant say when it started. The username/password combination works with mutt. Send this email? ([y]es|[n]o|[q]uit|[a]ll): y Net::SMTP>>> Net::SMTP(3.10) Net::SMTP>>> Net::Cmd(3.10) Net::SMTP>>> Exporter(5.72) Net::SMTP>>> IO::Socket::IP(0.38) Net::SMTP>>> IO::Socket(1.38) Net::SMTP>>> IO::Handle(1.36) Net::SMTP=GLOB(0x55b5df986d00)<<< 220 smtp.strato.de ESMTP RZmta (P7 -) Net::SMTP=GLOB(0x55b5df986d00)>>> EHLO sender Net::SMTP=GLOB(0x55b5df986d00)<<< 250-smtp.strato.de greets 2001:a62:816:91ff:a572:884d:f51d:1a86 Net::SMTP=GLOB(0x55b5df986d00)<<< 250-ENHANCEDSTATUSCODES Net::SMTP=GLOB(0x55b5df986d00)<<< 250-PIPELINING Net::SMTP=GLOB(0x55b5df986d00)<<< 250-8BITMIME Net::SMTP=GLOB(0x55b5df986d00)<<< 250-DELIVERBY Net::SMTP=GLOB(0x55b5df986d00)<<< 250-SIZE 104857600 Net::SMTP=GLOB(0x55b5df986d00)<<< 250-AUTH DIGEST-MD5 CRAM-MD5 LOGIN PLAIN Net::SMTP=GLOB(0x55b5df986d00)<<< 250-STARTTLS Net::SMTP=GLOB(0x55b5df986d00)<<< 250-BURL imap Net::SMTP=GLOB(0x55b5df986d00)<<< 250-CHUNKING Net::SMTP=GLOB(0x55b5df986d00)<<< 250 HELP Net::SMTP=GLOB(0x55b5df986d00)>>> STARTTLS Net::SMTP=GLOB(0x55b5df986d00)<<< 220 Ready to start TLS Net::SMTP::_SSL=GLOB(0x55b5df986d00)>>> EHLO sender Net::SMTP::_SSL=GLOB(0x55b5df986d00)<<< 250-smtp.strato.de greets 2001:a62:816:91ff:a572:884d:f51d:1a86 Net::SMTP::_SSL=GLOB(0x55b5df986d00)<<< 250-ENHANCEDSTATUSCODES Net::SMTP::_SSL=GLOB(0x55b5df986d00)<<< 250-PIPELINING Net::SMTP::_SSL=GLOB(0x55b5df986d00)<<< 250-8BITMIME Net::SMTP::_SSL=GLOB(0x55b5df986d00)<<< 250-DELIVERBY Net::SMTP::_SSL=GLOB(0x55b5df986d00)<<< 250-SIZE 104857600 Net::SMTP::_SSL=GLOB(0x55b5df986d00)<<< 250-AUTH DIGEST-MD5 CRAM-MD5 LOGIN PLAIN Net::SMTP::_SSL=GLOB(0x55b5df986d00)<<< 250-BURL imap Net::SMTP::_SSL=GLOB(0x55b5df986d00)<<< 250-CHUNKING Net::SMTP::_SSL=GLOB(0x55b5df986d00)<<< 250 HELP Net::SMTP::_SSL=GLOB(0x55b5df986d00)>>> EHLO sender Net::SMTP::_SSL=GLOB(0x55b5df986d00)<<< 250-smtp.strato.de greets 2001:a62:816:91ff:a572:884d:f51d:1a86 Net::SMTP::_SSL=GLOB(0x55b5df986d00)<<< 250-ENHANCEDSTATUSCODES Net::SMTP::_SSL=GLOB(0x55b5df986d00)<<< 250-PIPELINING Net::SMTP::_SSL=GLOB(0x55b5df986d00)<<< 250-8BITMIME Net::SMTP::_SSL=GLOB(0x55b5df986d00)<<< 250-DELIVERBY Net::SMTP::_SSL=GLOB(0x55b5df986d00)<<< 250-SIZE 104857600 Net::SMTP::_SSL=GLOB(0x55b5df986d00)<<< 250-AUTH DIGEST-MD5 CRAM-MD5 LOGIN PLAIN Net::SMTP::_SSL=GLOB(0x55b5df986d00)<<< 250-BURL imap Net::SMTP::_SSL=GLOB(0x55b5df986d00)<<< 250-CHUNKING Net::SMTP::_SSL=GLOB(0x55b5df986d00)<<< 250 HELP Net::SMTP::_SSL=GLOB(0x55b5df986d00)>>> AUTH DIGEST-MD5 ... -- You are receiving this mail because: You are on the CC list for the bug.

1 25

[Bug 1136307] New: laptop now longer powers fully down on shutdown or even does a reboot
by bugzilla_noreply＠novell.com 28 Jan '20

28 Jan '20

http://bugzilla.suse.com/show_bug.cgi?id=1136307 Bug ID: 1136307 Summary: laptop now longer powers fully down on shutdown or even does a reboot Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: alexvkaam(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- hi HP Notebook - 17-ca0710nd https://support.hp.com/us-en/drivers/selfservice/hp-17-ca0000-laptop-pc/203… under Leap 15.0 the laptop worked mostly fine except for a slow power drain issue (bug 1109374) Updated the laptop to 15.1 and as from that moment the shutdown (KDE) no longer shuts the laptop fully down, the Plymouth shutdown appears and if I press ESC it goes through just fine, screen is powered down so as far as I can tell it shutsdown normal on the linux side and does not hang. BUT the laptop fan keeps running and the caps-lock light blinks (on/off per second). Only way to stop it now is to hold down power for 5sec Tried a reboot and it gives the exact same effect as the powerdown ?! Waited for an hour, just kept in that state. booted up and retried a few times, same effect. shutdown now, same effect booted up a windows on usb, it had no issues with the shutdown checked HP for bios updates and installed the latest one F24 (was on F11) redid all the above steps, same effect. System is fully up to date with 15.1 now sure what info you need Regards, Alex -- You are receiving this mail because: You are on the CC list for the bug.

1 17

[Bug 1130395] New: Valgrind fails to build on armv6 and armv7
by bugzilla_noreply＠novell.com 28 Jan '20

28 Jan '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1130395 Bug ID: 1130395 Summary: Valgrind fails to build on armv6 and armv7 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: armv7 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: guillaume.gardet(a)arm.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Build logs: * armv6: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:ARM/valg… * armv7: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:ARM/valg… -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1130536] New: missing crtab option - breaks boot time entry
by bugzilla_noreply＠novell.com 28 Jan '20

28 Jan '20

http://bugzilla.suse.com/show_bug.cgi?id=1130536 Bug ID: 1130536 Summary: missing crtab option - breaks boot time entry Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: jsrain(a)suse.com Reporter: mmeeks(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- For various reasons my /etc/cryptab contained: cr_home-storage /data/home-storage none none cr_ata-Samsung_SSD_860_EVO_M.2_1TB_S415NB0M118918N-part3 /dev/disk/by-id/ata-Samsung_SSD_860_EVO_M.2_1TB_S415NB0M118918N-part3 none none And fstab: fstab:/dev/mapper/cr_home-storage /crypt-home xfs loop,nofail 0 0 /dev/mapper/cr_ata-Samsung_SSD_860_EVO_M.2_1TB_S415NB0M118918N-part3 /newhome xfs nofail 0 2 The first lookback file there /data/home-storage is/was no longer there - I removed it. At boot-time I would get prompted for the password to unlock the /newhome partition - but before that completed - I would be thrown into X - which would fail to auto-log-me-in and crash (since home was not available via a symlink to /newhome ;-) That made for quite some unpleasantness. Would love the prompter to be more robust there, and to cope with a 2nd partition that needs unlocking in the presence of a first that is not there. Thanks ! =) -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1094668] New: Firefox start failure ppc64le in TW
by bugzilla_noreply＠novell.com 27 Jan '20

27 Jan '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1094668 Bug ID: 1094668 Summary: Firefox start failure ppc64le in TW Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: PowerPC URL: https://openqa.opensuse.org/tests/682425/modules/firef ox/steps/4 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Firefox Assignee: bnc-team-mozilla(a)forge.provo.novell.com Reporter: normand(a)linux.vnet.ibm.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Firefox start failure ppc64le in TW the journalctl is reporting; === May 25 06:15:07 susetest kernel: firefox[15803]: unhandled signal 11 at 0000000000000000 nip 00000001260adfb8 lr 00000001260aef8c code 1 May 25 06:15:07 susetest systemd[1]: Started Process Core Dump (PID 15810/UID 0). May 25 06:15:07 susetest kernel: firefox[15809]: unhandled signal 11 at 0000000000000008 nip 00000001260ade18 lr 00000001260aef8c code 1 May 25 06:15:07 susetest systemd[1]: Started Process Core Dump (PID 15812/UID 0). May 25 06:15:07 susetest systemd-coredump[15813]: Process 15809 (firefox) of user 1000 dumped core. May 25 06:15:07 susetest systemd-coredump[15811]: Process 15803 (firefox) of user 1000 dumped core. May 25 06:21:15 susetest systemd[1]: Started Getty on tty5. === [Build 20180524] openQA test fails in firefox ## Observation openQA test in scenario opensuse-Tumbleweed-DVD-ppc64le-system_performance@ppc64le fails in [firefox](https://openqa.opensuse.org/tests/682425/modules/firefox/steps/4) ## Reproducible Fails since (at least) Build [20180524](https://openqa.opensuse.org/tests/682425) (current job) ## Expected result Last good: (unknown) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=ppc64le&flavor=DVD&te… -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1094138] New: VUL-0: CVE-2018-11243: upx: PackLinuxElf64::unpack in p_lx_elf.cpp in UPX 3.95 allows remote attackers to cause a denial of service
by bugzilla_noreply＠novell.com 24 Jan '20

24 Jan '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1094138 Bug ID: 1094138 Summary: VUL-0: CVE-2018-11243: upx: PackLinuxElf64::unpack in p_lx_elf.cpp in UPX 3.95 allows remote attackers to cause a denial of service Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other URL: https://smash.suse.de/issue/206156/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Maintenance Assignee: meissner(a)suse.com Reporter: vpereira(a)microfocus.com QA Contact: security-team(a)suse.de Found By: Security Response Team Blocker: --- CVE-2018-11243 PackLinuxElf64::unpack in p_lx_elf.cpp in UPX 3.95 allows remote attackers to cause a denial of service (double free), limit the ability of a malware scanner to operate on the entire original data, or possibly have unspecified other impact via a crafted file. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-11243 http://people.canonical.com/~ubuntu-security/cve/2018/CVE-2018-11243.html https://github.com/upx/upx/blob/devel/NEWS https://github.com/upx/upx/issues/206 https://github.com/upx/upx/issues/207 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1135723] New: Installation: Fstab Options window extended below screen bottom on 1280x800 screenS
by bugzilla_noreply＠novell.com 23 Jan '20

23 Jan '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1135723 Bug ID: 1135723 Summary: Installation: Fstab Options window extended below screen bottom on 1280x800 screenS Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: mrmazda(a)earthlink.net QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 805561 --> http://bugzilla.opensuse.org/attachment.cgi?id=805561&action=edit screenshot of Fstab Options window during NET 15.1 installation Original Summary: Installation: Fstab Options window extended below screen bottom on 1280x800 screenS This was on a Sony Vaio VGN CR290 laptop, not my own. Screens were mirrored. Same window opened on first boot centered top to bottom of smaller screen, with expected resolutions: > xrandr Screen 0: minimum 320 x 200, current 3200 x 1200, maximum 8192 x 8192 LVDS-1 connected primary 1280x800+0+0 (normal left inverted right x axis y axis) 0mm x 0mm 1280x800 60.00*+ 59.99 59.97 59.81 59.91 1280x720 60.00 59.99 59.86 59.74 1024x768 60.04 60.00... VGA-1 connected 1920x1200+1280+0 (normal left inverted right x axis y axis) 519mm x 324mm 1920x1200 59.95*+ 1920x1080 60.00 1680x1050 59.95 1400x1050 59.98 1280x1024 60.02 1440x900 59.89 1280x960 60.00 1280x800 59.81... SVIDEO-1 disconnected (normal left inverted right x axis y axis) -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1133741] New: System freeze and kernel panic after starting supertux2 1~2 minutes (radeon)
by bugzilla_noreply＠novell.com 23 Jan '20

23 Jan '20

http://bugzilla.suse.com/show_bug.cgi?id=1133741 Bug ID: 1133741 Summary: System freeze and kernel panic after starting supertux2 1~2 minutes (radeon) Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: dawei.pang(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Run supertux2 on gnome with wayland, the whole system freeze after 1~2 minutes. Try to connect the machine with serial console, enable kernel crash dump and set boot parameter 'ignore_loglevel crashkernel=256M console=ttyS0,115200 debug drm.debug=1 sysrq_always_enabled panic=10 pause_on_oops=5 loglevel=8', just got panic information as following and refer to attachment for crash dump. #inxi -GxxSM System: Host: linux-7fu1 Kernel: 4.12.14-lp151.24-default x86_64 bits: 64 gcc: 7.4.0 Console: tty 1 dm: gdm Distro: openSUSE Leap 15.1 Machine: Device: desktop System: Dell product: Precision Tower 5810 serial: HTS9SM2 Mobo: Dell model: 0HHV7N v: A00 serial: /HTS9SM2/CNFCW007BB00B0/ UEFI: Dell v: A29 date: 12/13/2018 Chassis: type: 7 serial: HTS9SM2 Graphics: Card: Advanced Micro Devices [AMD/ATI] Cape Verde GL [FirePro W4100] bus-ID: 03:00.0 chip-ID: 1002:682c Display Server: X.org 1.20.3 drivers: ati (unloaded: modesetting,fbdev,vesa,radeon) tty size: 180x32 Advanced Data: N/A for root # loginctl show-session c1 -p Type Type=wayland ===Panic information=== [ 1499.102545] [drm:si_irq_set [radeon]] si_irq_set: sw int dma [ 1520.821321] NMI watchdog: Watchdog detected hard LOCKUP on cpu 5 [ 1520.821322] Modules linked in: fuse af_packet msr xfs nls_iso8859_1 nls_cp437 vfat libcrc32c fat snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi intel_rapl sb_edac x86_pkg_temp_th ermal intel_powerclamp coretemp kvm_intel kvm dell_smbios irqbypass crc32_pclmul mxm_wmi dell_wmi_descriptor wmi_bmof ghash_clmulni_intel iTCO_wdt pcbc mei_wdt iTCO_vendor_support dcdbas snd_hda_intel dell_smm_h wmon snd_hda_codec snd_hda_core aesni_intel snd_hwdep aes_x86_64 snd_pcm crypto_simd glue_helper cryptd i2c_i801 pcspkr lpc_ich snd_timer e1000e snd mei_me ptp soundcore mei pps_core wmi button amdgpu chash gpu_ sched btrfs xor zstd_decompress zstd_compress xxhash sr_mod cdrom raid6_pq hid_generic usbhid radeon i2c_algo_bit drm_kms_helper syscopyarea ehci_pci xhci_pci sysfillrect sysimgblt [ 1520.821337] fb_sys_fops xhci_hcd ehci_hcd ttm crc32c_intel ahci usbcore libahci drm drm_panel_orientation_quirks sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua efivarfs [ 1520.821341] CPU: 5 PID: 72 Comm: kworker/5:1 Tainted: G L 4.12.14-lp151.24-default #1 openSUSE Leap 15.1 [ 1520.821341] Hardware name: Dell Inc. Precision Tower 5810/0HHV7N, BIOS A29 12/13/2018 [ 1520.821342] Workqueue: events_power_efficient radeon_fence_check_lockup [radeon] [ 1520.821342] task: ffff88041ed541c0 task.stack: ffffc90001b8c000 [ 1520.821343] RIP: 0010:native_queued_spin_lock_slowpath+0xe9/0x190 [ 1520.821343] RSP: 0018:ffffc90001b8fdf0 EFLAGS: 00000002 [ 1520.821344] RAX: 0000000000000000 RBX: 0000000000000292 RCX: ffff88042fd64c40 [ 1520.821344] RDX: 0000000000180101 RSI: 0000000000000101 RDI: ffff880419475520 [ 1520.821344] RBP: 0000000000000000 R08: 0000000000180000 R09: 0000000000000000 [ 1520.821345] R10: 0000000000000000 R11: 0000000000001329 R12: ffff880419474f10 [ 1520.821345] R13: 0000000000000003 R14: 0000000000000000 R15: 0000000000000000 [ 1520.821345] FS: 0000000000000000(0000) GS:ffff88042fd40000(0000) knlGS:0000000000000000 [ 1520.821346] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 1520.821346] CR2: 00007f699b51d000 CR3: 000000000200a001 CR4: 00000000001606e0 [ 1520.821347] Call Trace: [ 1520.821347] _raw_spin_lock_irqsave+0x32/0x40 [ 1520.821347] __wake_up_common_lock+0x53/0x90 [ 1520.821348] radeon_fence_check_lockup+0x12d/0x170 [radeon] [ 1520.821348] process_one_work+0x1da/0x400 [ 1520.821348] worker_thread+0x2b/0x3f0 [ 1520.821349] ? process_one_work+0x400/0x400 [ 1520.821349] kthread+0x113/0x130 [ 1520.821349] ? kthread_create_worker_on_cpu+0x50/0x50 [ 1520.821350] ret_from_fork+0x35/0x40 [ 1520.821350] Code: f3 90 8b 37 81 fe 00 01 00 00 74 f4 e9 60 ff ff ff 44 89 c0 c1 e8 10 66 87 47 02 89 c2 c1 e2 10 85 d2 75 61 45 31 c9 eb 02 f3 90 <8b> 17 66 85 d2 75 f7 be 01 00 00 00 eb 0c 89 d0 f0 0f b1 37 39 [ 1520.821360] Kernel panic - not syncing: Hard LOCKUP [ 1520.821361] CPU: 5 PID: 72 Comm: kworker/5:1 Tainted: G L 4.12.14-lp151.24-default #1 openSUSE Leap 15.1 [ 1520.821361] Hardware name: Dell Inc. Precision Tower 5810/0HHV7N, BIOS A29 12/13/2018 [ 1520.821361] Workqueue: events_power_efficient radeon_fence_check_lockup [radeon] [ 1520.821362] Call Trace: [ 1520.821362] <NMI> [ 1520.821362] dump_stack+0x5c/0x86 [ 1520.821363] panic+0xd5/0x233 [ 1520.821363] nmi_panic+0x35/0x40 [ 1520.821363] watchdog_overflow_callback+0xef/0x110 [ 1520.821364] __perf_event_overflow+0x52/0xe0 [ 1520.821364] intel_pmu_handle_irq+0x24c/0x4c0 [ 1520.821364] ? perf_event_nmi_handler+0x2d/0x50 [ 1520.821364] perf_event_nmi_handler+0x2d/0x50 [ 1520.821365] nmi_handle+0x63/0x110 [ 1520.821365] default_do_nmi+0x4e/0x100 [ 1520.821365] do_nmi+0xe5/0x140 [ 1520.821366] end_repeat_nmi+0x16/0x61 [ 1520.821366] RIP: 0010:native_queued_spin_lock_slowpath+0xe9/0x190 [ 1520.821366] RSP: 0018:ffffc90001b8fdf0 EFLAGS: 00000002 [ 1520.821367] RAX: 0000000000000000 RBX: 0000000000000292 RCX: ffff88042fd64c40 [ 1520.821367] RDX: 0000000000180101 RSI: 0000000000000101 RDI: ffff880419475520 [ 1520.821368] RBP: 0000000000000000 R08: 0000000000180000 R09: 0000000000000000 [ 1520.821368] R10: 0000000000000000 R11: 0000000000001329 R12: ffff880419474f10 [ 1520.821368] R13: 0000000000000003 R14: 0000000000000000 R15: 0000000000000000 [ 1520.821369] ? native_queued_spin_lock_slowpath+0xe9/0x190 [ 1520.821369] ? native_queued_spin_lock_slowpath+0xe9/0x190 [ 1520.821369] </NMI> [ 1520.821369] _raw_spin_lock_irqsave+0x32/0x40 [ 1520.821370] __wake_up_common_lock+0x53/0x90 [ 1520.821370] radeon_fence_check_lockup+0x12d/0x170 [radeon] [ 1520.821370] process_one_work+0x1da/0x400 [ 1520.821371] worker_thread+0x2b/0x3f0 [ 1520.821371] ? process_one_work+0x400/0x400 [ 1520.821371] kthread+0x113/0x130 [ 1520.821372] ? kthread_create_worker_on_cpu+0x50/0x50 [ 1520.821372] ret_from_fork+0x35/0x40 ===GDB crash=== crash> bt PID: 72 TASK: ffff88041ed541c0 CPU: 5 COMMAND: "kworker/5:1" #0 [fffffe00000e5a68] machine_kexec at ffffffff8105f08f #1 [fffffe00000e5ab8] __crash_kexec at ffffffff8111e25e #2 [fffffe00000e5b70] panic at ffffffff811bb7d0 #3 [fffffe00000e5bf0] nmi_panic at ffffffff8108a895 #4 [fffffe00000e5bf8] watchdog_overflow_callback at ffffffff8114de5f #5 [fffffe00000e5c08] __perf_event_overflow at ffffffff811a90e2 #6 [fffffe00000e5c38] intel_pmu_handle_irq at ffffffff8100c03c #7 [fffffe00000e5e40] perf_event_nmi_handler at ffffffff8100560d #8 [fffffe00000e5e58] nmi_handle at ffffffff81030213 #9 [fffffe00000e5eb0] default_do_nmi at ffffffff8103068e #10 [fffffe00000e5ed0] do_nmi at ffffffff81030825 #11 [fffffe00000e5ef0] end_repeat_nmi at ffffffff81801ccd [exception RIP: native_queued_spin_lock_slowpath+233] RIP: ffffffff810d4b59 RSP: ffffc90001b8fdf0 RFLAGS: 00000002 RAX: 0000000000000000 RBX: 0000000000000292 RCX: ffff88042fd64c40 RDX: 0000000000180101 RSI: 0000000000000101 RDI: ffff880419475520 RBP: 0000000000000000 R8: 0000000000180000 R9: 0000000000000000 R10: 0000000000000000 R11: 0000000000001329 R12: ffff880419474f10 R13: 0000000000000003 R14: 0000000000000000 R15: 0000000000000000 ORIG_RAX: ffffffffffffffff CS: 0010 SS: 0018 --- <NMI exception stack> --- #12 [ffffc90001b8fdf0] native_queued_spin_lock_slowpath at ffffffff810d4b59 #13 [ffffc90001b8fdf0] _raw_spin_lock_irqsave at ffffffff817da862 #14 [ffffc90001b8fe00] __wake_up_common_lock at ffffffff810ca293 #15 [ffffc90001b8fe60] radeon_fence_check_lockup at ffffffffa03860ed [radeon] #16 [ffffc90001b8fe98] process_one_work at ffffffff810a39ba #17 [ffffc90001b8fed8] worker_thread at ffffffff810a3c0b #18 [ffffc90001b8ff10] kthread at ffffffff810aa3d3 #19 [ffffc90001b8ff50] ret_from_fork at ffffffff81800235 -- You are receiving this mail because: You are on the CC list for the bug.

1 17

[Bug 1117230] New: Leap 15 Privoxy is not able to resolve addresses with plasma and/or falkon, even email
by bugzilla_noreply＠novell.com 21 Jan '20

21 Jan '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1117230 Bug ID: 1117230 Summary: Leap 15 Privoxy is not able to resolve addresses with plasma and/or falkon, even email Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: stakanov(a)freenet.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I tried already the workaround of Bug 1041606 however with no effect. Privoxy itself starts up. ● privoxy.service - Privoxy Web Proxy With Advanced Filtering Capabilities Loaded: loaded (/usr/lib/systemd/system/privoxy.service; enabled; vendor preset: disabled) Active: active (running) since Sun 2018-11-25 11:04:41 CET; 33min ago Process: 2694 ExecStart=/usr/sbin/privoxy --chroot --pidfile /run/privoxy.pid --user privoxy /etc/config (code=exited, sta> Process: 2693 ExecStartPre=/usr/bin/cp -upf /lib64/libresolv.so.2 /lib64/libnss_dns.so.2 /var/lib/privoxy/lib64/ (code=exi> Process: 2692 ExecStartPre=/usr/bin/cp -upf /etc/resolv.conf /etc/host.conf /etc/hosts /etc/localtime /var/lib/privoxy/etc> Main PID: 2695 (privoxy) Tasks: 1 (limit: 4915) CGroup: /system.slice/privoxy.service └─2695 /usr/sbin/privoxy --chroot --pidfile /run/privoxy.pid --user privoxy /etc/config nov 25 11:04:40 roadrunner.suse systemd[1]: Starting Privoxy Web Proxy With Advanced Filtering Capabilities... nov 25 11:04:41 roadrunner.suse systemd[1]: Started Privoxy Web Proxy With Advanced Filtering Capabilities. The system runs on wlan1 but when trying to do the following setup for systemewide kde plasma: 127.0.0.1:8118 (which is the default setting for localhost and privoxy) no proxy for localhost or when setting e.g. falcon to manually use http 127.0.0.1:8118 The command sudo tcpdump -n -i lo port 8118 [sudo] password di root: tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on lo, link-type EN10MB (Ethernet), capture size 262144 bytes Does not capture traffic. The browser however loads, the page is loaded correctly. When trying to open the status page the answer is: Privoxy is not being used So obviously the settings are not honored. sudo netstat -tulpn [sudo] password di root: Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 127.0.0.1:8118 0.0.0.0:* LISTEN 2695/privoxy tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 1502/cupsd tcp 0 0 127.0.0.1:5432 0.0.0.0:* LISTEN 1871/postgres tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 2116/master tcp6 0 0 ::1:631 :::* LISTEN 1502/cupsd tcp6 0 0 ::1:5432 :::* LISTEN 1871/postgres tcp6 0 0 ::1:25 :::* LISTEN 2116/master udp 0 0 0.0.0.0:68 0.0.0.0:* 2545/dhclient udp 0 0 127.0.0.1:323 0.0.0.0:* 1518/chronyd udp6 0 0 ::1:323 :::* 1518/chronyd As you see it starts and does listen. But is not used? Funnily enough, yesterday I had as a side effect the impossibility to resolve IMAP mail when setting the Plasma System settings to privoxy? This resolved after setting no proxy in the plasma system settings. -- You are receiving this mail because: You are on the CC list for the bug.

1 3