February 2017 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 976985] New: tcl plugin for firefox throws error "undefined symbol: Tcl_Init"
by bugzilla_noreply＠novell.com 05 Dec '19

05 Dec '19

http://bugzilla.suse.com/show_bug.cgi?id=976985 Bug ID: 976985 Summary: tcl plugin for firefox throws error "undefined symbol: Tcl_Init" Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: hguo(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This is a freshly installed tumbleweed snapshot 20160417. When starting firefox while tclplug is installed, an error is printed in the firefox output: LoadPlugin: failed to initialize shared library /usr/lib64/browser-plugins/libnptcl3.1.so [/usr/lib64/browser-plugins/libnptcl3.1.so: undefined symbol: Tcl_Init] Hence the plugin is not usable. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 996733] New: unknown error on my Raspbery Pi with openSUSE Tumbleweed
by bugzilla_noreply＠novell.com 29 Nov '19

29 Nov '19

http://bugzilla.suse.com/show_bug.cgi?id=996733 Bug ID: 996733 Summary: unknown error on my Raspbery Pi with openSUSE Tumbleweed Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: petr.m(a)seznam.cz QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 690410 --> http://bugzilla.suse.com/attachment.cgi?id=690410&action=edit unknown error I've got this error on my Raspbery Pi with openSUSE Tumbleweed from http://download.opensuse.org/ports/armv6hl/tumbleweed/ srp 31 18:44:34 dns4 kernel: dwc2 20980000.usb: dwc2_hc_chhltd_intr_dma: Channel 1 - ChHltd set, but reason is unknown srp 31 18:44:34 dns4 kernel: dwc2 20980000.usb: hcint 0x00000002, intsts 0x04600029 -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1014706] New: No warnings on SSDM trying to login on Windows DC after expired password
by bugzilla_noreply＠novell.com 26 Nov '19

26 Nov '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1014706 Bug ID: 1014706 Summary: No warnings on SSDM trying to login on Windows DC after expired password Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: rafael.linux.user(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I'm on an Windows domain in a LAN. I can login without problems but have severe problems login with SSDM cause: 1 - If I type an incorrect password, there is no any message about "Error on user/password" 2 - There is no warning about my DC Windows password is near to expire 3 - When my password is expired (and I need to change it) it's IMPOSSIBLE to login thru SSDM. There is no way to do it. Please, fix this incompatibilities on login in Windows domains. Thank you -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1024446] New: [Build 20170208] openQA test fails in live_installation
by bugzilla_noreply＠novell.com 26 Nov '19

26 Nov '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1024446 Bug ID: 1024446 Summary: [Build 20170208] openQA test fails in live_installation Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: http://openqa.opensuse.org/tests/351409/modules/live_i nstallation/steps/7 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- ## Observation openQA test in scenario opensuse-Tumbleweed-KDE-Live-x86_64-kde-live_installation@64bit fails in [live_installation](http://openqa.opensuse.org/tests/351409/modules/live_ins… ## Reproducible Fails since (at least) Build [20170208](http://openqa.opensuse.org/tests/351220) ## Expected result Last good: [20170207](http://openqa.opensuse.org/tests/350409) (or more recent) ## Further details Always latest result in this scenario: [latest](http://openqa.opensuse.org/tests/latest?machine=64bit&distri=opensu… The dialog asking to confirm what action one would like to perform with the installer is new - and causes this regression -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1023288] New: [Build 20170201] openQA test fails in zdup
by bugzilla_noreply＠novell.com 26 Nov '19

26 Nov '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1023288 Bug ID: 1023288 Summary: [Build 20170201] openQA test fails in zdup Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: http://openqa.opensuse.org/tests/346006/modules/zdup/s teps/112 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- ## Observation openQA test in scenario opensuse-Tumbleweed-NET-x86_64-zdup-Leap-42.1-kde@64bit fails in [zdup](http://openqa.opensuse.org/tests/346006/modules/zdup/steps/112) ## Reproducible Fails since (at least) Build [20170201](http://openqa.opensuse.org/tests/345565) ## Expected result Last good: [20170131](http://openqa.opensuse.org/tests/344377) (or more recent) ## Further details The issue boils down to a packaging policy violation: the shared library package libKF5Kipi30_0_0 contains a .desktop file, which is not acceptable. As the test shows, installation on libKF5Kipi32_0_0 is not possible without a file conflict. a SLPP package is not to contain ANYTHING that does not follow the SOVER of the library packaged (that can be multiple libraries, or even versioned files) -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1007652] New: FTDI adapter does not show up as ttyUSB
by bugzilla_noreply＠novell.com 25 Nov '19

25 Nov '19

http://bugzilla.suse.com/show_bug.cgi?id=1007652 Bug ID: 1007652 Summary: FTDI adapter does not show up as ttyUSB Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: mbrugger(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When plugging in the FTDI adpater, it get's registered as ttyUSB but shortly afterwards it gets deregistered and reregistered as input device: udevadm monitor monitor will print the received events for: UDEV - the event which udev sends out after rule processing KERNEL - the kernel uevent KERNEL[4096.004758] add /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2 (usb) KERNEL[4096.007131] add /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0 (usb) KERNEL[4096.007175] add /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/ttyUSB0 (usb-serial) KERNEL[4096.007883] add /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/ttyUSB0/tty/ttyUSB0 (tty) UDEV [4096.526145] add /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2 (usb) UDEV [4096.531416] add /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0 (usb) UDEV [4096.532623] add /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/ttyUSB0 (usb-serial) UDEV [4096.538064] add /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/ttyUSB0/tty/ttyUSB0 (tty) KERNEL[4096.668041] remove /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/ttyUSB0/tty/ttyUSB0 (tty) KERNEL[4096.668075] remove /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/ttyUSB0 (usb-serial) UDEV [4096.670253] remove /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/ttyUSB0/tty/ttyUSB0 (tty) UDEV [4096.671010] remove /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/ttyUSB0 (usb-serial) KERNEL[4100.679481] add /devices/virtual/input/input38 (input) KERNEL[4100.679612] add /devices/virtual/input/input38/event20 (input) UDEV [4100.681392] add /devices/virtual/input/input38 (input) UDEV [4100.714831] add /devices/virtual/input/input38/event20 (input) lsusb Bus 001 Device 018: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC dmesg [ 4330.254760] usb 1-1.2: new full-speed USB device number 19 using ehci-pci [ 4330.371475] usb 1-1.2: New USB device found, idVendor=0403, idProduct=6001 [ 4330.371480] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 4330.371484] usb 1-1.2: Product: FT232R USB UART [ 4330.371486] usb 1-1.2: Manufacturer: FTDI [ 4330.371488] usb 1-1.2: SerialNumber: A50285BI [ 4330.374746] ftdi_sio 1-1.2:1.0: FTDI USB Serial Device converter detected [ 4330.374826] usb 1-1.2: Detected FT232RL [ 4330.375406] usb 1-1.2: FTDI USB Serial Device converter now attached to ttyUSB0 [ 4331.045927] usb 1-1.2: usbfs: interface 0 claimed by ftdi_sio while 'brltty' sets config #1 [ 4331.046819] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0 [ 4331.046845] ftdi_sio 1-1.2:1.0: device disconnected -- You are receiving this mail because: You are on the CC list for the bug.

1 33

[Bug 996203] New: Failed at step NAMESPACE spawning /usr/sbin/start_apache2: Operation not permitted
by bugzilla_noreply＠novell.com 22 Nov '19

22 Nov '19

http://bugzilla.opensuse.org/show_bug.cgi?id=996203 Bug ID: 996203 Summary: Failed at step NAMESPACE spawning /usr/sbin/start_apache2: Operation not permitted Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Apache Assignee: bnc-team-apache(a)forge.provo.novell.com Reporter: per(a)computer.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- System: mysogo, 13.2, xen guest. When issuing an apache reload: # systemctl reload apache2 Job for apache2.service failed. See "systemctl status apache2.service" and "journalctl -xn" for details. # systemctl status apache2 apache2.service - The Apache Webserver Loaded: loaded (/usr/lib/systemd/system/apache2.service; enabled) Active: active (running) (Result: exit-code) since Sun 2016-08-07 12:02:18 CEST; 3 weeks 1 days ago Process: 5711 ExecReload=/usr/sbin/start_apache2 -D SYSTEMD -DFOREGROUND -k graceful (code=exited, status=226/NAMESPACE) Main PID: 854 (httpd2-prefork) Status: "Total requests: 0; Current requests/sec: 0; Current traffic: 0 B/sec" CGroup: /system.slice/apache2.service ├─ 854 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL -D SYSTEMD -DFOREGROUND -k start ├─ 1468 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL -D SYSTEMD -DFOREGROUND -k start ├─ 1472 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL -D SYSTEMD -DFOREGROUND -k start ├─ 1474 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL -D SYSTEMD -DFOREGROUND -k start ├─ 1487 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL -D SYSTEMD -DFOREGROUND -k start ├─ 3398 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL -D SYSTEMD -DFOREGROUND -k start ├─ 3400 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL -D SYSTEMD -DFOREGROUND -k start ├─10336 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL -D SYSTEMD -DFOREGROUND -k start ├─32256 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL -D SYSTEMD -DFOREGROUND -k start ├─32280 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL -D SYSTEMD -DFOREGROUND -k start └─32478 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL -D SYSTEMD -DFOREGROUND -k start Aug 30 11:12:31 mysogo systemd[1]: Reloading The Apache Webserver. Aug 30 11:12:31 mysogo systemd[5711]: Failed at step NAMESPACE spawning /usr/sbin/start_apache2: Operation not permitted Aug 30 11:12:31 mysogo systemd[1]: apache2.service: control process exited, code=exited status=226 Aug 30 11:12:31 mysogo systemd[1]: Reload failed for The Apache Webserver. Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable. A similar issue is mentioned here: https://help.directadmin.com/item.php?id=614 but on my system, both /tmp and /var/tmp are directories, not symlinks. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1015997] New: linkchecker-gui does not start
by bugzilla_noreply＠novell.com 15 Nov '19

15 Nov '19

http://bugzilla.suse.com/show_bug.cgi?id=1015997 Bug ID: 1015997 Summary: linkchecker-gui does not start Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Network Assignee: pth(a)suse.com Reporter: lpechacek(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After fixing bug #1015996... Symptom: lpechacek@fm:~> linkchecker-gui Traceback (most recent call last): File "/usr/bin/linkchecker-gui", line 30, in <module> from PyQt4.QtGui import QApplication ImportError: No module named PyQt4.QtGui Fix: lpechacek@fm:~> sudo zypper in python-qt4 -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 902401] New: plymouth segfault
by bugzilla_noreply＠novell.com 15 Nov '19

15 Nov '19

http://bugzilla.opensuse.org/show_bug.cgi?id=902401 Bug ID: 902401 Summary: plymouth segfault Classification: openSUSE Product: openSUSE Factory Version: NO 13.2 BUGS!! Hardware: i686 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: idonmez(a)suse.com Reporter: mpluskal(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- # systemd-coredumpctl gdb 169 TIME PID UID GID SIG EXE Čt 2014-10-23 14:42:07 CEST 169 0 0 11 /usr/sbin/plymouthd GNU gdb (GDB; openSUSE Factory) 7.8 Copyright (C) 2014 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i586-suse-linux". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://bugs.opensuse.org/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... warning: /etc/gdbinit.d/gdb-heap.py: Adresář nebo soubor neexistuje Reading symbols from /usr/sbin/plymouthd...Reading symbols from /usr/lib/debug/usr/sbin/plymouthd.debug...done. done. [New LWP 169] b[Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/libthread_db.so.1". Core was generated by `@usr/sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid --attach-to-sessio'. Program terminated with signal SIGSEGV, Segmentation fault. #0 ply_event_loop_stop_watching_signal (loop=0x7665642f, signal_number=signal_number@entry=28) at ply-event-loop.c:869 t869 ply-event-loop.c: Adresář nebo soubor neexistuje. (gdb) bt #0 ply_event_loop_stop_watching_signal (loop=0x7665642f, signal_number=signal_number@entry=28) at ply-event-loop.c:869 #1 0xb76febe7 in ply_terminal_close (terminal=0x99f4008) at ply-terminal.c:707 #2 0xb7717159 in ply_hashtable_foreach (hashtable=0x99f3dc8, func=0xb76feb10 <ply_terminal_close>, user_data=user_data@entry=0x99f3e18) at ply-hashtable.c:272 #3 0xb76fb0fc in ply_close_all_terminals (manager=0x99f3e18) at ply-device-manager.c:954 #4 0x0805396c in quit_splash (state=state@entry=0xbff95794) at main.c:1083 #5 0x08053a4f in dump_details_and_quit_splash (state=state@entry=0xbff95794) at main.c:1114 #6 0x08053ccf in on_quit (state=0xbff95794, retain_splash=false, quit_trigger=0x99f6ac0) at main.c:1349 #7 0x0804ee27 in ply_boot_connection_on_request (connection=0x9a028e0) at ply-boot-server.c:534 #8 0xb7713fc6 in ply_event_loop_handle_met_status_for_source (status=PLY_EVENT_LOOP_FD_STATUS_HAS_DATA, source=0x99f1af0, loop=0x99ef0b0) at ply-event-loop.c:1060 #9 ply_event_loop_process_pending_events (loop=loop@entry=0x99ef0b0) at ply-event-loop.c:1327 #10 0xb7714508 in ply_event_loop_run (loop=0x99ef0b0) at ply-event-loop.c:1359 #11 0x0804c424 in main (argc=4, argv=0xbff95ab4) at main.c:2357 (gdb) bt full #0 ply_event_loop_stop_watching_signal (loop=0x7665642f, signal_number=signal_number@entry=28) at ply-event-loop.c:869 node = 0x19 #1 0xb76febe7 in ply_terminal_close (terminal=0x99f4008) at ply-terminal.c:707 __func__ = "ply_terminal_close" #2 0xb7717159 in ply_hashtable_foreach (hashtable=0x99f3dc8, func=0xb76feb10 <ply_terminal_close>, user_data=user_data@entry=0x99f3e18) at ply-hashtable.c:272 i = 5 #3 0xb76fb0fc in ply_close_all_terminals (manager=0x99f3e18) at ply-device-manager.c:954 No locals. #4 0x0805396c in quit_splash (state=state@entry=0xbff95794) at main.c:1083 __func__ = "quit_splash" #5 0x08053a4f in dump_details_and_quit_splash (state=state@entry=0xbff95794) at main.c:1114 No locals. #6 0x08053ccf in on_quit (state=0xbff95794, retain_splash=false, quit_trigger=0x99f6ac0) at main.c:1349 __func__ = "on_quit" #7 0x0804ee27 in ply_boot_connection_on_request (connection=0x9a028e0) at ply-boot-server.c:534 retain_splash = false quit_trigger = 0x99f6ac0 server = 0x99f1688 command = 0x99f69f8 "Q" argument = 0x99f6b40 "" __PRETTY_FUNCTION__ = "ply_boot_connection_on_request" __func__ = "ply_boot_connection_on_request" #8 0xb7713fc6 in ply_event_loop_handle_met_status_for_source (status=PLY_EVENT_LOOP_FD_STATUS_HAS_DATA, source=0x99f1af0, loop=0x99ef0b0) at ply-event-loop.c:1060 next_node = 0x0 destination = 0x9a02a50 node = <optimized out> #9 ply_event_loop_process_pending_events (loop=loop@entry=0x99ef0b0) at ply-event-loop.c:1327 source = 0x99f1af0 is_disconnected = <optimized out> number_of_received_events = 1 i = 0 events = {{events = 1, data = {ptr = 0x99f1af0, fd = 161422064, u32 = 161422064, u64 = 161422064}}, {events = 4294967295, data = {ptr = 0xffffffff, fd = -1, u32 = 4294967295, u64 = 18446744073709551615}} <repeats 63 times>} __PRETTY_FUNCTION__ = "ply_event_loop_process_pending_events" #10 0xb7714508 in ply_event_loop_run (loop=0x99ef0b0) at ply-event-loop.c:1359 No locals. #11 0x0804c424 in main (argc=4, argv=0xbff95ab4) at main.c:2357 state = {loop = 0x99ef0b0, boot_server = 0x99f1688, boot_splash = 0x0, session = 0x99f27e0, boot_buffer = 0x99f17c8, progress = 0x99f3d60, keystroke_triggers = 0x99ef5e0, entry_triggers = 0x99ef5f0, entry_buffer = 0x99f0660, messages = 0x99f1678, command_parser = 0x99ef008, mode = PLY_MODE_BOOT, local_console_terminal = 0x99f40d8, device_manager = 0x99f3e18, deactivate_trigger = 0x0, quit_trigger = 0x99f6ac0, start_time = 2.9794491600000002, splash_delay = nan(0x8000000000000), kernel_command_line = "BOOT_IMAGE=/boot/vmlinuz-3.17.1-0.g5c4d099-default root=UUID=04f6a8f9-ec8e-4fd8-9d03-9159c16a0a32 resume=/dev/disk/by-id/ata-ST3200827A_5ND4PPCL-part1 splash=silent quiet showopts Y2DEBUG=1\n", '\000' <repeats 321 times>, kernel_command_line_is_set = 1, no_boot_log = 0, showing_details = 1, system_initialized = 1, is_redirected = 0, is_attached = 0, should_be_attached = 1, should_retain_splash = 0, is_inactive = 1, is_shown = 0, should_force_details = 0, override_splash_path = 0x0, system_default_splash_path = 0x99f3e80 "/usr/share/plymouth/themes/openSUSE/openSUSE.plymouth", distribution_default_splash_path = 0x99f3f80 "/usr/share/plymouth/themes/openSUSE/openSUSE.plymouth", default_tty = 0x805641f "/dev/tty7", number_of_errors = 0} exit_code = <optimized out> should_help = false no_boot_log = false no_daemon = false debug = false attach_to_session = true daemon_handle = 0x99ef5a0 mode_string = 0x99ef5a0 " " kernel_command_line = 0x0 tty = 0x0 device_manager_flags = <optimized out> sa = {__sigaction_handler = {sa_handler = 0x80529e0 <dosigaction>, sa_sigaction = 0x80529e0 <dosigaction>}, sa_mask = {__val = {0 <repeats 32 times>}}, sa_flags = -2147483648, sa_restorer = 0x0} __func__ = "main" -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 975879] New: plymouthd crashes in ply_event_loop_stop_watching_fd
by bugzilla_noreply＠novell.com 15 Nov '19

15 Nov '19

http://bugzilla.opensuse.org/show_bug.cgi?id=975879 Bug ID: 975879 Summary: plymouthd crashes in ply_event_loop_stop_watching_fd Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: daniel.lichtenberger(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- In my openSUSE Tumbleweed installation, plymouthd always coredumps during startup. Backtrace: #0 ply_event_loop_get_destination_from_fd_watch (loop=0x7974742f7665642f, watch=0x21) at ply-event-loop.c:449 #1 0x00007f0d1675920b in ply_event_loop_stop_watching_fd (loop=0x7974742f7665642f, watch=0x21) at ply-event-loop.c:750 #2 0x00007f0d165458f7 in ply_terminal_close () from /usr/lib64/libply-splash-core.so.4 #3 0x00007f0d1675cc53 in ply_hashtable_foreach (hashtable=0x180f8e0, func=0x7f0d16545870 <ply_terminal_close>, user_data=0x180ff20) at ply-hashtable.c:268 #4 0x000000000040c050 in quit_splash (state=state@entry=0x7ffd0872a000) at main.c:1064 #5 0x000000000040c8af in on_boot_splash_idle (state=0x7ffd0872a000) at main.c:1196 #6 0x00007f0d16759d2a in ply_event_loop_handle_timeouts (loop=0x180a150) at ply-event-loop.c:1192 #7 ply_event_loop_process_pending_events (loop=loop@entry=0x180a150) at ply-event-loop.c:1251 #8 0x00007f0d1675a340 in ply_event_loop_run (loop=0x180a150) at ply-event-loop.c:1310 #9 0x0000000000405454 in main (argc=<optimized out>, argv=<optimized out>) at main.c:2233 plymouth package version: 0.9.2-2.1 I also reported this at https://bugs.freedesktop.org/show_bug.cgi?id=94952, but later noticed that the stacktrace points to OpenSUSE patches (ply_close_all_terminals in quit_splash). -- You are receiving this mail because: You are on the CC list for the bug.

1 5