Bug 709172 – Thers isn't any window, maye because missing „ Important” logs

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 709172 - Thers isn't any window, maye because missing „ Important” logs


Summary:	Thers isn't any window, maye because missing „ Important” logs


Status:	RESOLVED OBSOLETE

Product:	gnome-logs
Classification:	Other
Component:	general
Version:	git master
Hardware:	Other Linux

Importance:	Normal normal
Target Milestone:	---
Assigned To:	gnome-logs maintainer(s)
QA Contact:	gnome-logs maintainer(s)

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2013-10-01 10:42 UTC by Yosef Or Boczko
Modified:	2013-10-24 11:10 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Yosef Or Boczko 2013-10-01 10:42:23 UTC

In ArchLinux, GNOME 3.10 from git, when my
user is in 'systemd-journal' and 'log' groups:
$ groups yosefor
log systemd-journal users

I run 'gnome-logs' and get the following warning, and not see any window:
** (Logs:17855): WARNING **: Error getting message from systemd journal: Cannot assign requested address

The process isn't crash.

Well, in gdb:
$ G_DEBUG=fatal-warnings gdb gnome-logs
(gdb) run
Starting program: /pkg/gnome-logs/gnome-logs/gnome-logs 
warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7ffff7ffa000
warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x7fffee0b9700 (LWP 17859)]

** (Logs:17855): WARNING **: Error getting message from systemd journal: Cannot assign requested address

Program received signal SIGTRAP, Trace/breakpoint trap.
0x00007ffff5f9e359 in g_logv (log_domain=0x0, log_level=G_LOG_LEVEL_WARNING, format=<optimized out>, args=args@entry=0x7fffffffd508) at gmessages.c:989
989			G_BREAKPOINT ();
(gdb) bt

+ Trace 232560

#0 g_logv
at gmessages.c line 989
#1 g_log
at gmessages.c line 1025
#2 insert_journal_items_cmdline
at src/gl-eventview.c line 841
#3 gl_event_view_add_listbox_important
at src/gl-eventview.c line 970
#4 gl_event_view_init
at src/gl-eventview.c line 1340
#5 g_type_create_instance
at gtype.c line 1868
#6 g_object_new_internal
at gobject.c line 1746
#7 g_object_newv
at gobject.c line 1890
#8 _gtk_builder_construct
at gtkbuilder.c line 718
#9 builder_construct
at gtkbuilderparser.c line 197
#10 end_element
at gtkbuilderparser.c line 1102
#11 g_markup_parse_context_parse
at gmarkup.c line 1602
#12 _gtk_builder_parser_parse_buffer
at gtkbuilderparser.c line 1285
#13 _gtk_builder_extend_with_template
at gtkbuilder.c line 1139
#14 gtk_widget_init_template
at gtkwidget.c line 15748
#15 gl_window_init
at src/gl-window.c line 250
#16 g_type_create_instance
at gtype.c line 1868
#17 g_object_new_internal
at gobject.c line 1746
#18 g_object_new_valist
at gobject.c line 2002
#19 g_object_new
at gobject.c line 1559
#20 gl_window_new
at src/gl-window.c line 280
#21 gl_application_activate
at src/gl-application.c line 127
#22 _g_closure_invoke_va
at gclosure.c line 840
#23 g_signal_emit_valist
at gsignal.c line 3238
#24 g_signal_emit
at gsignal.c line 3386
#25 g_application_activate
at gapplication.c line 1414
#26 g_application_real_local_command_line
at gapplication.c line 499
#27 g_application_run
at gapplication.c line 1585
#28 main
at src/gl-main.c line 39


Any idea about this?

Comment 1 David King 2013-10-24 11:10:21 UTC

The journal reading code has completely changed now, but this was probably a duplicate of bug 709290.