Bug 487297 - The "spectacle" program crashes when the time zone is set incorrectly
Summary: The "spectacle" program crashes when the time zone is set incorrectly
Status: RESOLVED FIXED
Alias: None
Product: Spectacle
Classification: Applications
Component: General (show other bugs)
Version: 24.04.90
Platform: NixOS Linux
: NOR crash
Target Milestone: ---
Assignee: Noah Davis
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-05-20 21:02 UTC by kixoncon33@gmail.com
Modified: 2024-06-30 12:01 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
coredumpctl gdb 123141 | wl-copy (40.86 KB, text/plain)
2024-06-04 23:01 UTC, Chris
Details

Note You need to log in before you can comment on or make changes to this bug.
Description kixoncon33@gmail.com 2024-05-20 21:02:02 UTC
1. setting the wrong time zone through the nixos config and generating it (in my case, not knowing that there was only one time zone “Asia/Almaty” left, I set it to “Asia/Astana”)
2. an attempt to take a screenshot, of a region, of the entire screen, an attempt to save it or copy it to the clipboard, after which it crashes
3. when run via terminal using the command "spectacle -bcr
" the error "Unable to determine system time zone: please check your system configuration. Segmentation fault (core dumped)"

it just doesn't work in the wrong time zone, making it difficult to diagnose using topic chats

os: nixos unstable chanel, KDE plasma 6.0.5
Comment 1 Noah Davis 2024-05-21 05:36:38 UTC
Can you please attach a backtrace of the crash using the coredumpctl command-line program, as detailed in https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl? I'm wondering if the issue comes from spectacle itself or a library we use.
Comment 2 Chris 2024-06-04 03:44:54 UTC
Hi, I have the same issue as the OP, with the exact same system.
The output from `timedatectl` seems okay, though.
I tried to run coredumpctl gdb 70296`, but besides providing information, I get `Failed to invoke gdb: No such file or directory`. So, I'll come back to it later.
Comment 3 kixoncon33@gmail.com 2024-06-04 05:00:21 UTC
(In reply to Noah Davis from comment #1)
> Can you please attach a backtrace of the crash using the coredumpctl
> command-line program, as detailed in
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/
> How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl?
> I'm wondering if the issue comes from spectacle itself or a library we use.

Sorry, I can no longer reproduce this error, my system does not boot with such changes, funny XD
Comment 4 Chris 2024-06-04 23:01:44 UTC
Created attachment 170152 [details]
coredumpctl gdb 123141 | wl-copy

Hi Noah,

I've been told on the nixos chat room that: "Thought without debug symbols it won't show much else beside what coredumpctl already shows".
So I past the output of `coredumpctl gdb 123141`.
Coredump resulting from invoking `spectacle` from command line and then clicking on `save` or `copy` or `configure` to name a few.
Which results in the error message: "Unable to determine system time zone: please check your system configuration. Segmentation fault (core dumped)"
But really my time zone seems perfectly okay.
```
$ timedatectl | grep zone
                Time zone: UTC (UTC, +0000)
```

If I can provide additional information I'm happy to do it,
Cheers,
Chris
Comment 5 Bug Janitor Service 2024-06-19 03:47:10 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Chris 2024-06-30 12:01:57 UTC
I did provide the requested info a fortnight ago.

However `sudo nixos-rebuild boot --upgrade` just now (unstable) and rebooting caused the bug not showing anymore, so I guess the issue can just be closed.