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 746503 - "has_boot_id" is not initialized
"has_boot_id" is not initialized
Status: RESOLVED FIXED
Product: gnome-logs
Classification: Other
Component: general
git master
Other Linux
: Normal normal
: ---
Assigned To: gnome-logs maintainer(s)
gnome-logs maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2015-03-20 04:50 UTC by Jonathan Kang
Modified: 2015-03-26 16:46 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
patch for this bug (795 bytes, patch)
2015-03-20 04:52 UTC, Jonathan Kang 		committed Details | Review

Description Jonathan Kang 2015-03-20 04:50:38 UTC 
In gl-journal.c, inside the function of gl_journal_set_matches, the boolean varaible has_boot_id is not initialized. It cause a unexpected error that even _BOOT_ID is not in @matches, it won't take events from this boot only.
Comment 1 Jonathan Kang 2015-03-20 04:52:45 UTC 
Created attachment 299910 [details] [review]
patch for this bug

The variable has_boot_id should be initialized as FALSE. Here is the patch.
Comment 2 David King 2015-03-26 16:45:30 UTC 
Review of attachment 299910 [details] [review]:

Thanks for the patch! I pushed it to master and gnome-3-16 as 01793aef17c04d78354a99e668d15e318d7152f2 and 262f694e625abbe3441da17fcd4b6e5b839a0d31.