Bug 104791 - plymouthd crashed with SIGSEGV in script_obj_deref_direct()
Summary: plymouthd crashed with SIGSEGV in script_obj_deref_direct()
Status: RESOLVED MOVED
Alias: None
Product: plymouth
Classification: Unclassified
Component: script plugin (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Charlie Brej
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-01-25 16:18 UTC by Cristian Aravena
Modified: 2018-08-07 09:28 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments
Ubuntu script (54 bytes, text/plain)
2018-04-03 18:40 UTC, Brian Murray
Details

Description Cristian Aravena 2018-01-25 16:18:01 UTC
Hello,

Open bug in Launchpad.net
https://bugs.launchpad.net/bugs/1745406

"I do not know why this happened"



BackTrace:
#0  script_obj_deref_direct (obj=0x0) at ./script-object.c:133
No locals.
#1  0x00007faef226f6ff in script_obj_as_custom (obj=<optimized out>, user_func=user_func@entry=0x7faef226ef70 <script_obj_execute>, user_data=user_data@entry=0x7ffc11c15b10) at ./script-object.c:242
        reply = <optimized out>
#2  0x00007faef226ecac in script_execute_object_with_parlist (parameter_data=0x55ba4b4f7600, this=0x0, obj=<optimized out>, state=0x55ba4b3dd390) at ./script-execute.c:287
        execute_data = {state = 0x55ba4b3dd390, this = 0x0, parameter_data = 0x55ba4b4f7600}
        execute_data = <optimized out>
#3  script_execute_object (state=0x55ba4b3dd390, function=<optimized out>, this=this@entry=0x0, first_arg=first_arg@entry=0x0) at ./script-execute.c:649
        reply = <optimized out>
        args = {{gp_offset = 32, fp_offset = 21946, overflow_arg_area = 0x7ffc11c15bb0, reg_save_area = 0x7ffc11c15b50}}
        arg = <optimized out>
        parameter_data = 0x55ba4b4f7600
#4  0x00007faef2272be3 in script_lib_plymouth_on_display_normal (state=<optimized out>, data=<optimized out>) at ./script-lib-plymouth.c:289
        ret = <optimized out>
#5  0x00007faef226ba42 in display_normal (plugin=0x55ba4b3dd2a0) at ./plugin.c:473
No locals.
#6  0x00007faef4459101 in create_text_displays_for_terminal (terminal=0x55ba4b3d1c10, manager=0x55ba4b3d1a70) at ply-device-manager.c:658
        display = 0x55ba4b4f3780
        display = <optimized out>
        _old_errno = <optimized out>
        _old_errno = <optimized out>
#7  create_devices_for_terminal_and_renderer_type (manager=0x55ba4b3d1a70, device_path=<optimized out>, terminal=0x55ba4b3d1c10, renderer_type=<optimized out>) at ply-device-manager.c:735
        renderer = <optimized out>
        keyboard = 0x55ba4b446de0
        __func__ = "create_devices_for_terminal_and_renderer_type"
#8  0x00007faef4670e32 in ply_event_loop_handle_timeouts (loop=0x55ba4b3ca3a0) at ply-event-loop.c:1192
        next_node = <optimized out>
        watch = 0x55ba4b3d1990
        node = 0x55ba4b3e75d0
        now = 10.590881546
        node = <optimized out>
        now = <optimized out>
        next_node = <optimized out>
        watch = <optimized out>
#9  ply_event_loop_process_pending_events (loop=loop@entry=0x55ba4b3ca3a0) at ply-event-loop.c:1251
        timeout = <optimized out>
        number_of_received_events = 0
        i = <optimized out>
        events = {{events = 4294967295, data = {ptr = 0xffffffffffffffff, fd = -1, u32 = 4294967295, u64 = 18446744073709551615}} <repeats 64 times>}
        __PRETTY_FUNCTION__ = "ply_event_loop_process_pending_events"
#10 0x00007faef4671480 in ply_event_loop_run (loop=0x55ba4b3ca3a0) at ply-event-loop.c:1310
No locals.
#11 0x000055ba49be1514 in main (argc=4, argv=0x7ffc11c16f58) at main.c:2390
        state = {loop = 0x55ba4b3ca3a0, boot_server = 0x55ba4b3cce70, boot_splash = 0x55ba4b3d6b10, session = 0x55ba4b3ce1a0, boot_buffer = 0x55ba4b3cd170, progress = 0x55ba4b3d17a0, keystroke_triggers = 0x55ba4b3cbdc0, entry_triggers = 0x55ba4b3cbde0, entry_buffer = 0x55ba4b3cbe00, messages = 0x55ba4b3cce50, command_parser = 0x55ba4b3ca260, mode = PLY_MODE_BOOT, local_console_terminal = 0x55ba4b3d1c10, device_manager = 0x55ba4b3d1a70, deactivate_trigger = 0x0, quit_trigger = 0x0, start_time = 5.5555437300000001, splash_delay = nan(0x8000000000000), device_timeout = 5, kernel_command_line = "BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-041500rc9-generic root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet splash vt.handoff=7\n", '\000' <repeats 3949 times>, kernel_command_line_is_set = 1, no_boot_log = 0, showing_details = 0, system_initialized = 1, is_redirected = 0, is_attached = 0, should_be_attached = 1, should_retain_splash = 0, is_inactive = 1, is_shown = 1, should_force_details = 0, override_splash_path = 0x0, system_default_splash_path = 0x0, distribution_default_splash_path = 0x0, default_tty = 0x55ba49bebcff "/dev/tty1", number_of_errors = 0, pending_messages = 0x55ba4b3cce30}
        exit_code = <optimized out>
        should_help = false
        no_boot_log = false
        no_daemon = false
        debug = false
        attach_to_session = true
        daemon_handle = <optimized out>
        mode_string = 0x55ba4b3cac30 "p\254<K\272U"
        kernel_command_line = 0x0
        tty = 0x0
        device_manager_flags = <optimized out>
        __func__ = "main"


Regards,
--
Cristian
Comment 1 Charlie Brej 2018-01-25 16:55:19 UTC
Are you running a custom theme? If so could you supply the .script component of it?
Comment 2 Cristian Aravena 2018-01-25 17:16:05 UTC
Hello,

I'm not using a custom theme.

Regards,
--
Cristian
Comment 3 Brian Murray 2018-04-03 18:40:53 UTC
Created attachment 138557 [details]
Ubuntu script
Comment 4 Brian Murray 2018-04-03 18:41:35 UTC
Ubuntu uses the attached script by default.
Comment 5 GitLab Migration User 2018-08-07 09:28:33 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/plymouth/plymouth/issues/58.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.