Description of problem: Came back to my laptop after sitting overnight: was greeted with gdm instead of my a password prompt to unlock my desktop. Version-Release number of selected component: gnome-shell-3.28.1-3.fc28 Additional info: reporter: libreport-2.9.5 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: gweather_timezone_get_tzid executable: /usr/bin/gnome-shell journald_cursor: s=d56bd705b9a74a56b1aed2f6235d7e63;i=4022c;b=3aa98d8122a147129e2f1e5ad02294af;m=65d50a0bf;t=56b6fffe048d5;x=78eb8056e2ffbb25 kernel: 4.16.5-300.fc28.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 gweather_timezone_get_tzid at ../libgweather/gweather-timezone.c:383 #1 gweather_location_get_timezone at ../libgweather/gweather-location.c:1005 #2 ffi_call_unix64 at ../src/x86/unix64.S:76 #3 ffi_call at ../src/x86/ffi64.c:525 #4 gjs_invoke_c_function(JSContext*, Function*, JS::HandleObject, JS::HandleValueArray const&, mozilla::Maybe<JS::MutableHandle<JS::Value> >, GIArgument*) at gi/function.cpp:1088 #5 function_call(JSContext*, unsigned int, JS::Value*) at /usr/include/c++/8/new:169 #6 js::CallJSNative(JSContext*, bool (*)(JSContext*, unsigned int, JS::Value*), JS::CallArgs const&) at /usr/src/debug/mozjs52-52.7.3-1.fc28.x86_64/jscntxtinlines.h:239 #7 js::InternalCallOrConstruct(JSContext*, JS::CallArgs const&, js::MaybeConstruct) at /usr/src/debug/mozjs52-52.7.3-1.fc28.x86_64/vm/Interpreter.cpp:447 #8 js::CallFromStack(JSContext*, JS::CallArgs const&) at /usr/src/debug/mozjs52-52.7.3-1.fc28.x86_64/vm/Interpreter.cpp:2922 #9 Interpret(JSContext*, js::RunState&) at /usr/src/debug/mozjs52-52.7.3-1.fc28.x86_64/vm/Interpreter.cpp:2922
Created attachment 1432059 [details] File: backtrace
Created attachment 1432060 [details] File: cgroup
Created attachment 1432061 [details] File: core_backtrace
Created attachment 1432062 [details] File: cpuinfo
Created attachment 1432063 [details] File: dso_list
Created attachment 1432064 [details] File: environ
Created attachment 1432065 [details] File: exploitable
Created attachment 1432066 [details] File: limits
Created attachment 1432067 [details] File: maps
Created attachment 1432068 [details] File: mountinfo
Created attachment 1432069 [details] File: open_fds
Created attachment 1432070 [details] File: proc_pid_status
Created attachment 1432071 [details] File: var_log_messages
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.