March 2016 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 932495] New: telepathy-haze SIGTRAP: tp-glib", log_level=G_LOG_LEVEL_CRITICAL, format=<optimized out>, args=args@entry=0x7ffc4614b998) at gmessages.c:1046
by bugzilla_noreply＠novell.com 26 Jun '20

26 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=932495 Bug ID: 932495 Summary: telepathy-haze SIGTRAP: tp-glib", log_level=G_LOG_LEVEL_CRITICAL, format=<optimized out>, args=args@entry=0x7ffc4614b998) at gmessages.c:1046 Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: mpluskal(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 635636 --> http://bugzilla.opensuse.org/attachment.cgi?id=635636&action=edit backtrace telepathy-haze random SIGTRAP: #0 g_logv (log_domain=0x7f4ee1ef2806 "tp-glib", log_level=G_LOG_LEVEL_CRITICAL, format=<optimized out>, args=args@entry=0x7ffc4614b998) at gmessages.c:1046 #1 0x00007f4ee220ebe2 in g_log (log_domain=log_domain@entry=0x7f4ee1ef2806 "tp-glib", log_level=log_level@entry=G_LOG_LEVEL_CRITICAL, format=format@entry=0x7f4ee225615d "%s: assertion '%s' failed") at gmessages.c:1079 #2 0x00007f4ee220ec09 in g_return_if_fail_warning (log_domain=log_domain@entry=0x7f4ee1ef2806 "tp-glib", pretty_function=pretty_function@entry=0x7f4ee1efe4c0 <__func__.31694> "tp_base_connection_finish_shutdown", expression=<optimized out>) at gmessages.c:1088 #3 0x00007f4ee1df2e7c in tp_base_connection_finish_shutdown (self=<optimized out>) at base-connection.c:2905 #4 0x0000000000413eec in idle_finish_shutdown (data=0x872150) at connection.c:317 #5 0x00007f4ee2207b55 in g_main_dispatch (context=0x796350) at gmain.c:3122 #6 g_main_context_dispatch (context=context@entry=0x796350) at gmain.c:3737 #7 0x00007f4ee2207ec8 in g_main_context_iterate (context=0x796350, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3808 #8 0x00007f4ee220818a in g_main_loop_run (loop=0x836650) at gmain.c:4002 #9 0x00007f4ee1ecb654 in tp_run_connection_manager (prog_name=prog_name@entry=0x422425 "haze", version=version@entry=0x4222f3 "0.8.0", construct_cm=construct_cm@entry=0x410150 <get_cm>, argc=argc@entry=1, argv=argv@entry=0x7ffc4614bcc8) at run.c:284 #10 0x000000000041001b in main (argc=1, argv=0x7ffc4614bcc8) at main.c:267 -- You are receiving this mail because: You are on the CC list for the bug.

2 8

[Bug 931435] New: gdm-session-worker sigabrt
by bugzilla_noreply＠novell.com 26 Jun '20

26 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=931435 Bug ID: 931435 Summary: gdm-session-worker sigabrt Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: os.gnome.maintainers(a)gmail.com Reporter: mpluskal(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 634690 --> http://bugzilla.opensuse.org/attachment.cgi?id=634690&action=edit backtrace After reboot with recent factory, gdm is terminated, after that it is restarted and works fine. backtrace: Core was generated by `gdm-session-worker [pam/gdm-launch-environment]'. Program terminated with signal SIGABRT, Aborted. #0 0x00007fae7aa623c7 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55 55 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory. (gdb) bt #0 0x00007fae7aa623c7 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55 #1 0x00007fae7aa6379a in __GI_abort () at abort.c:78 #2 0x00007fae7b8e61b5 in g_assertion_message (domain=domain@entry=0x7fae7b66069a "AccountsService", file=file@entry=0x7fae7b661200 "act-user-manager.c", line=line@entry=2564, func=func@entry=0x7fae7b663978 <__FUNCTION__.27349> "load_users", message=message@entry=0x13f5630 "assertion failed: (manager->priv->accounts_proxy != NULL)") at gtestutils.c:2356 #3 0x00007fae7b8e624a in g_assertion_message_expr (domain=domain@entry=0x7fae7b66069a "AccountsService", file=file@entry=0x7fae7b661200 "act-user-manager.c", line=line@entry=2564, func=func@entry=0x7fae7b663978 <__FUNCTION__.27349> "load_users", expr=expr@entry=0x7fae7b662390 "manager->priv->accounts_proxy != NULL") at gtestutils.c:2371 #4 0x00007fae7b64bc66 in load_users (manager=0x13dc100) at act-user-manager.c:2564 #5 load_idle (manager=0x13dc100) at act-user-manager.c:2615 #6 0x00007fae7b8c1b55 in g_main_dispatch (context=0x13d81f0) at gmain.c:3122 #7 g_main_context_dispatch (context=context@entry=0x13d81f0) at gmain.c:3737 #8 0x00007fae7b8c1ec8 in g_main_context_iterate (context=0x13d81f0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3808 #9 0x00007fae7b8c218a in g_main_loop_run (loop=0x13f2c10) at gmain.c:4002 #10 0x0000000000408b34 in main (argc=1, argv=0x7fff4d13b0f8) at session-worker-main.c:132 -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 934043] New: gdm segfault: gdm-session-worker-job.c: Permission denied
by bugzilla_noreply＠novell.com 26 Jun '20

26 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=934043 Bug ID: 934043 Summary: gdm segfault: gdm-session-worker-job.c: Permission denied Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: mpluskal(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 637131 --> http://bugzilla.opensuse.org/attachment.cgi?id=637131&action=edit backtrace It seems that gdm have recently died several times with following: Program terminated with signal SIGSEGV, Segmentation fault. #0 0x0000000000420b31 in gdm_session_worker_job_spawn (name=0x2606c00 "`�^\002", session_worker_job=0x26198d0) at gdm-session-worker-job.c:295 295 gdm-session-worker-job.c: Permission denied. (gdb) bt #0 0x0000000000420b31 in gdm_session_worker_job_spawn (name=0x2606c00 "`�^\002", session_worker_job=0x26198d0) at gdm-session-worker-job.c:295 #1 gdm_session_worker_job_start (session_worker_job=0x26198d0, name=name@entry=0x26194a0 "gdm-session-worker [pam/gdm-launch-environment]") at gdm-session-worker-job.c:324 #2 0x000000000041d502 in start_conversation (service_name=0x440c28 "gdm-launch-environment", self=0x26036a0) at gdm-session.c:1851 #3 gdm_session_start_conversation (self=0x26036a0, service_name=service_name@entry=0x440c28 "gdm-launch-environment") at gdm-session.c:1924 #4 0x0000000000414fed in gdm_launch_environment_start (launch_environment=0x24ad1c0) at gdm-launch-environment.c:509 #5 0x000000000041267c in gdm_display_start_greeter_session (self=self@entry=0x1ccb820) at gdm-display.c:1509 #6 0x000000000041779a in set_up_greeter_session (display=0x1ccb820, manager=0x1ccb220) at gdm-manager.c:1779 #7 on_display_status_changed (display=0x1ccb820, arg1=<optimized out>, manager=0x1ccb220) at gdm-manager.c:1834 #8 0x00007f709a15a018 in g_closure_invoke (closure=0x261a6b0, return_value=0x0, n_param_values=2, param_values=0x7ffc15e42c50, invocation_hint=0x7ffc15e42bf0) at gclosure.c:768 #9 0x00007f709a16b22d in signal_emit_unlocked_R (node=node@entry=0x1cbbdf0, detail=detail@entry=240, instance=instance@entry=0x1ccb820, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7ffc15e42c50) at gsignal.c:3549 #10 0x00007f709a172da8 in g_signal_emit_valist (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>, var_args=var_args@entry=0x7ffc15e42de8) at gsignal.c:3305 #11 0x00007f709a173062 in g_signal_emit (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>) at gsignal.c:3361 #12 0x00007f709a15e3a5 in g_object_dispatch_properties_changed (object=0x1ccb820, n_pspecs=16, pspecs=0x0) at gobject.c:1056 #13 0x00007f709a160793 in g_object_notify_by_spec_internal (pspec=<optimized out>, object=0x1ccb820) at gobject.c:1150 #14 g_object_notify (object=0x1ccb820, property_name=property_name@entry=0x43f7ae "status") at gobject.c:1197 #15 0x000000000041030b in _gdm_display_set_status (self=self@entry=0x1ccb820, status=status@entry=1) at gdm-display.c:527 #16 0x00000000004106a0 in gdm_display_real_prepare (self=0x1ccb820) at gdm-display.c:538 #17 0x00000000004137e1 in gdm_local_display_prepare (display=0x1ccb820) at gdm-local-display.c:143 #18 0x0000000000411df1 in gdm_display_prepare (self=self@entry=0x1ccb820) at gdm-display.c:601 #19 0x0000000000411f3f in gdm_display_manage (self=self@entry=0x1ccb820) at gdm-display.c:618 #20 0x000000000040f2ca in create_display (factory=factory@entry=0x1cd6af0, seat_id=0x2614dd0 "seat0", session_type=0x25bfa40 "wayland", initial=1) at gdm-local-display-factory.c:427 #21 0x000000000040f4e5 in on_display_status_changed (display=0x1ccb420, arg1=<optimized out>, factory=0x1cd6af0) at gdm-local-display-factory.c:320 #22 0x00007f709a15a018 in g_closure_invoke (closure=0x2600300, return_value=0x0, n_param_values=2, param_values=0x7ffc15e43230, invocation_hint=0x7ffc15e431d0) at gclosure.c:768 #23 0x00007f709a16b22d in signal_emit_unlocked_R (node=node@entry=0x1cbbdf0, detail=detail@entry=240, instance=instance@entry=0x1ccb420, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7ffc15e43230) at gsignal.c:3549 #24 0x00007f709a172da8 in g_signal_emit_valist (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>, var_args=var_args@entry=0x7ffc15e433c8) at gsignal.c:3305 #25 0x00007f709a173062 in g_signal_emit (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>) at gsignal.c:3361 #26 0x00007f709a15e3a5 in g_object_dispatch_properties_changed (object=0x1ccb420, n_pspecs=16, pspecs=0x0) at gobject.c:1056 #27 0x00007f709a160793 in g_object_notify_by_spec_internal (pspec=<optimized out>, object=0x1ccb420) at gobject.c:1150 #28 g_object_notify (object=0x1ccb420, property_name=property_name@entry=0x43f7ae "status") at gobject.c:1197 #29 0x000000000041030b in _gdm_display_set_status (self=self@entry=0x1ccb420, status=status@entry=3) at gdm-display.c:527 #30 0x0000000000411fe8 in gdm_display_finish (self=0x1ccb420) at gdm-display.c:645 #31 0x0000000000412034 in finish_idle (self=<optimized out>) at gdm-display.c:509 #32 0x00007f7099e85b55 in g_main_dispatch (context=0x1ccc950) at gmain.c:3122 #33 g_main_context_dispatch (context=context@entry=0x1ccc950) at gmain.c:3737 #34 0x00007f7099e85ec8 in g_main_context_iterate (context=0x1ccc950, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3808 #35 0x00007f7099e8618a in g_main_loop_run (loop=0x1cd9190) at gmain.c:4002 #36 0x000000000040ca16 in main (argc=1, argv=0x7ffc15e437f8) at main.c:426 -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 932039] New: gdm segfaults when trying to connect remotely
by bugzilla_noreply＠novell.com 26 Jun '20

26 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=932039 Bug ID: 932039 Summary: gdm segfaults when trying to connect remotely Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: mpluskal(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 635207 --> http://bugzilla.opensuse.org/attachment.cgi?id=635207&action=edit backtrace When trying to connect to machine with Xephyr from different, host, gdm segfaults: (gdb) bt #0 g_logv (log_domain=0x7f17ce29a5e4 "GLib-GObject", log_level=G_LOG_LEVEL_ERROR, format=<optimized out>, args=args@entry=0x7ffd603b9218) at gmessages.c:1046 #1 0x00007f17cdfa4be2 in g_log (log_domain=log_domain@entry=0x7f17ce29a5e4 "GLib-GObject", log_level=log_level@entry=G_LOG_LEVEL_ERROR, format=format@entry=0x7f17ce2a1390 "cannot create instance of abstract (non-instantiatable) type '%s'") at gmessages.c:1079 #2 0x00007f17ce291fce in g_type_create_instance (type=39325328) at gtype.c:1812 #3 0x00007f17ce276cb8 in g_object_constructor (type=<optimized out>, n_construct_properties=13, construct_params=0x25bbeb0) at gobject.c:2059 #4 0x0000000000410a08 in gdm_display_constructor (type=39325328, n_construct_properties=13, construct_properties=0x25bbeb0) at gdm-display.c:1110 #5 0x00007f17ce276fe6 in g_object_new_with_custom_constructor (n_params=6, params=0x7ffd603b9720, class=0x2580ac0) at gobject.c:1692 #6 g_object_new_internal (class=class@entry=0x2580ac0, params=params@entry=0x7ffd603b9720, n_params=6) at gobject.c:1772 #7 0x00007f17ce278f24 in g_object_new_valist (object_type=object_type@entry=39325328, first_property_name=first_property_name@entry=0x43fb3c "remote-hostname", var_args=var_args@entry=0x7ffd603b9878) at gobject.c:2033 #8 0x00007f17ce279304 in g_object_new (object_type=39325328, first_property_name=first_property_name@entry=0x43fb3c "remote-hostname") at gobject.c:1617 #9 0x0000000000426d5b in gdm_xdmcp_display_new (hostname=hostname@entry=0x25bb360 "fd79:5506:3d7a:1:862b:2bff:fea0:17c9", number=number@entry=1, address=address@entry=0x258d6b0, session_number=2052774968) at gdm-xdmcp-display.c:276 #10 0x0000000000424f5d in gdm_xdmcp_display_create (displaynum=1, address=0x258d6b0, hostname=0x25bb360 "fd79:5506:3d7a:1:862b:2bff:fea0:17c9", factory=0x256a0f0) at gdm-xdmcp-display-factory.c:2149 #11 gdm_xdmcp_handle_request (len=<optimized out>, address=0x258d6b0, factory=0x256a0f0) at gdm-xdmcp-display-factory.c:2390 #12 decode_packet (source=<optimized out>, cond=<optimized out>, factory=0x256a0f0) at gdm-xdmcp-display-factory.c:2995 #13 0x00007f17cdf9db55 in g_main_dispatch (context=0x2555e30) at gmain.c:3122 #14 g_main_context_dispatch (context=context@entry=0x2555e30) at gmain.c:3737 #15 0x00007f17cdf9dec8 in g_main_context_iterate (context=0x2555e30, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3808 #16 0x00007f17cdf9e18a in g_main_loop_run (loop=0x25628d0) at gmain.c:4002 #17 0x000000000040ca16 in main (argc=1, argv=0x7ffd603b9ea8) at main.c:426 -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 936206] New: accounts-daemon segfault when inccorrect passwd provided
by bugzilla_noreply＠novell.com 25 Jun '20

25 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=936206 Bug ID: 936206 Summary: accounts-daemon segfault when inccorrect passwd provided Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: mpluskal(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 639342 --> http://bugzilla.opensuse.org/attachment.cgi?id=639342&action=edit backtrace I have noticed segfault when logging in on current factory (over ssh, when entering wrong passwd): #0 magazine_chain_pop_head (magazine_chunks=0x1f547c0) at gslice.c:539 #1 thread_memory_magazine1_alloc (tmem=<optimized out>, ix=1) at gslice.c:842 #2 g_slice_alloc (mem_size=mem_size@entry=24) at gslice.c:998 #3 0x00007fded1db6b76 in g_list_prepend (list=0x7fdec4001500, data=data@entry=0x1fd6a00) at glist.c:311 #4 0x000000000040f3f8 in wtmp_helper_entry_generator (users=0x1f726a0, state=0x7fff4e948258) at wtmp-helper.c:165 #5 0x0000000000408f6b in load_entries (daemon=daemon@entry=0x1f688c0, users=users@entry=0x1f726a0, entry_generator=0x40f300 <wtmp_helper_entry_generator>) at daemon.c:247 #6 0x000000000040913f in reload_users (daemon=daemon@entry=0x1f688c0) at daemon.c:317 #7 0x00000000004092d9 in reload_users_timeout (daemon=0x1f688c0, daemon@entry=<error reading variable: value has been optimized out>) at daemon.c:358 #8 0x00007fded1dbb583 in g_timeout_dispatch (source=0x1fb4600, callback=<optimized out>, user_data=<optimized out>) at gmain.c:4545 #9 0x00007fded1dbab55 in g_main_dispatch (context=0x1f5c8d0) at gmain.c:3122 #10 g_main_context_dispatch (context=context@entry=0x1f5c8d0) at gmain.c:3737 #11 0x00007fded1dbaec8 in g_main_context_iterate (context=0x1f5c8d0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3808 #12 0x00007fded1dbb18a in g_main_loop_run (loop=0x1f64640) at gmain.c:4002 #13 0x0000000000408020 in main (argc=1, argv=0x7fff4e948558) at main.c:219 -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 931523] New: gnome-shell: center_pointer (backend=0xcab0b0) at backends/meta-backend.c:106 segfault
by bugzilla_noreply＠novell.com 25 Jun '20

25 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=931523 Bug ID: 931523 Summary: gnome-shell: center_pointer (backend=0xcab0b0) at backends/meta-backend.c:106 segfault Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: mpluskal(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 634746 --> http://bugzilla.opensuse.org/attachment.cgi?id=634746&action=edit backtrace Same conditions as boo#931513 (gdb) bt #0 center_pointer (backend=0xcab0b0) at backends/meta-backend.c:106 #1 0x00007fd71a341a31 in meta_backend_x11_post_init (backend=0xcab0b0) at backends/x11/meta-backend-x11.c:449 #2 0x00007fd71a3664e5 in meta_init () at core/main.c:358 #3 0x0000000000401f8e in main (argc=1, argv=0x7ffdb849f158) at main.c:429 -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 904210] New: package link not shown in web UI
by bugzilla_noreply＠novell.com 24 Jun '20

24 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=904210 Bug ID: 904210 Summary: package link not shown in web UI Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: BuildService Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: nico.kruber(a)gmail.com QA Contact: adrian(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:33.0) Gecko/20100101 Firefox/33.0 Build Identifier: if repo B is based on repo A which contains package C, then linking to B:C (without C being directly available in B) produces no UI elements to show (un)expanded sources in the web UI, neither is the link shown as such ("links to ...") example: https://build.opensuse.org/package/show/KDE:Extra/PackageKit https://build.opensuse.org/package/show/KDE:Extra/PackageKit?expand=0 https://build.opensuse.org/package/show/KDE:Extra/PackageKit?expand=1 Reproducible: Always Steps to Reproduce: 1. create link to a package in openSUSE:13.2:Update which is only available in openSUSE:13.2 2. browse to that link Actual Results: the link exists but is not shown as such Expected Results: same UI as if the package was linked to openSUSE:13.2 directly -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 953287] New: gdb internal-error: value_contents_bits_eq: Assertion `offset2 + length <= TYPE_LENGTH (val2->enclosing_type) * TARGET_CHAR_BIT' failed.
by bugzilla_noreply＠novell.com 12 Jun '20

12 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=953287 Bug ID: 953287 Summary: gdb internal-error: value_contents_bits_eq: Assertion `offset2 + length <= TYPE_LENGTH (val2->enclosing_type) * TARGET_CHAR_BIT' failed. Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: rguenther(a)suse.com Reporter: mpluskal(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 654335 --> http://bugzilla.opensuse.org/attachment.cgi?id=654335&action=edit core file When opening coredump for pinger (part of squid). following occurs: #17 0x000056267a78966c in IcmpPinger::Recv (this=0x56267a99b620 <control>) at IcmpPinger.cc:166 _dbo = warning: can't find linker symbol for virtual table for `std::basic_ostream<char, std::char_traits<char> >' value warning: found `construction vtable for std::__cxx11::basic_ostringstream<char, std::char_traits<char>, std::allocator<char> >-in-Debug::OutStream' instead @0x56267b3f16c0: warning: can't find linker symbol for virtual table for `std::basic_ostream<char, std::char_traits<char> >' value warning: found `construction vtable for std::__cxx11::basic_ostringstream<char, std::char_traits<char>, std::allocator<char> >-in-Debug::OutStream' instead {<std::basic_ios<char, std::char_traits<char> >> = {<std::ios_base> = {_vptr.ios_base = 0x56267a994978 <construction vtable for std::__cxx11::basic_ostringstream<char, std::char_traits<char>, std::allocator<char> >-in-Debug::OutStream+64>, static boolalpha = std::_S_boolalpha, static dec = std::_S_dec, static fixed = std::_S_fixed, static hex = std::_S_hex, static internal = std::_S_internal, static left = std::_S_left, static oct = std::_S_oct, static right = std::_S_right, static scientific = std::_S_scientific, static showbase = std::_S_showbase, static showpoint = std::_S_showpoint, static showpos = std::_S_showpos, static skipws = std::_S_skipws, static unitbuf = std::_S_unitbuf, static uppercase = std::_S_uppercase, static adjustfield = std::_S_adjustfield, static basefield = std::_S_basefield, static floatfield = std::_S_floatfield, static badbit = std::_S_badbit, static eofbit = std::_S_eofbit, static failbit = std::_S_failbit, static goodbit = std::_S_goodbit, static app = std::_S_app, static ate = std::_S_ate, static binary = std::_S_bin, static in = std::_S_in, static out = std::_S_out, static trunc = std::_S_trunc, static beg = std::_S_beg, static cur = std::_S_cur, static end = std::_S_end, _M_precision = 2, _M_width = 0, _M_flags = 4102, _M_exception = std::_S_goodbit, _M_streambuf_state = std::_S_goodbit, _M_callbacks = 0x0, _M_word_zero = {_M_pword = 0x0, _M_iword = 0}, _M_local_word = {../../gdb/value.c:823: internal-error: value_contents_bits_eq: Assertion `offset2 + length <= TYPE_LENGTH (val2->enclosing_type) * TARGET_CHAR_BIT' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 920134] New: windows:mingw:win{32,64}/mingw{32,64}-binutils: windmc memory bug
by bugzilla_noreply＠novell.com 11 Jun '20

11 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=920134 Bug ID: 920134 Summary: windows:mingw:win{32,64}/mingw{32,64}-binutils: windmc memory bug Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: All OS: Windows Status: NEW Severity: Major Priority: P5 - None Component: 3rd party software Assignee: fstrba(a)suse.com Reporter: gitne(a)gmx.de QA Contact: opensuse-communityscreening(a)forge.provo.novell.com CC: fridrich.strba(a)bluewin.ch, gitne(a)gmx.de, hib(a)hiberis.nl, mkbosmans(a)gmail.com, tlillqvist(a)suse.com Found By: Community User Blocker: No Created attachment 624972 --> http://bugzilla.opensuse.org/attachment.cgi?id=624972&action=edit Sample source message file for windmc without a trailing line feed (U+000A) character If the input file does not end with a line feed character (U+000A) the windmc tool eats up all the memory and then terminates with an out of memory error. To reproduce, try the atteched sample.mc file. Append a line feed character at the end of the file and windmc works (mostly) as intended. Warning: Be careful when reproducing on 64 bit systems with lots of RAM and/or swap space. This operation may cause the system to seemingly block for an extended amount of time. It is probably best to use the mingw32 version of windmc or to specifically limit the available amount of memory to the process to a reasounable amount. -- You are receiving this mail because: You are on the CC list for the bug.

2 12

[Bug 948280] New: windows:mingw:win{32,64}/mingw{32,64}-filesystem: Add hardening options?
by bugzilla_noreply＠novell.com 06 Jun '20

06 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=948280 Bug ID: 948280 Summary: windows:mingw:win{32,64}/mingw{32,64}-filesystem: Add hardening options? Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: fstrba(a)suse.com Reporter: gerald(a)wireshark.org QA Contact: opensuse-communityscreening(a)forge.provo.novell.com CC: fridrich.strba(a)bluewin.ch, hib(a)hiberis.nl, idonmez(a)suse.com, mkbosmans(a)gmail.com, tlillqvist(a)suse.com Found By: --- Blocker: --- It doesn't appear that any of the mingw:win32 or mingw:win64 packages are built with hardening options enabled, e.g. --dynamicbase, --nxcompat, and --highentropyva. Would it be possible to do so? -- You are receiving this mail because: You are on the CC list for the bug.

2 1