FS#65898 - [lxappearance-obconf-gtk3] Segmentation fault when executing lxappearance

Attached to Project: Community Packages
Opened by Giovanni Santini (ItachiSan) - Thursday, 19 March 2020, 16:22 GMT
Last edited by Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:07 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Balló György (City-busz)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Whenever executing the application, via terminal or desktop file, the application has a segmentation fault and core dump.

Additional info:
* package version: 0.6.3-2
* config and/or log files: not sure if I should report any
* link to upstream bug report, if any: not that I am aware

Steps to reproduce:
1. Have an LXDE environment
2. Install the required package: `lxappearance-gtk3`
3. Run `lxappearance`
This task depends upon

Closed by  Buggy McBugFace (bugbot)
Saturday, 25 November 2023, 20:07 GMT
Reason for closing:  Moved
Additional comments about closing:  https://gitlab.archlinux.org/archlinux/p ackaging/packages/lxappearance-obconf-gt k3/issues/1
Comment by Balló György (City-busz) - Thursday, 19 March 2020, 19:25 GMT
Please report this problem to upstream with a proper trace:
https://sourceforge.net/p/lxde/bugs/search/?q=labels:lxappearance
Comment by Giovanni Santini (ItachiSan) - Friday, 20 March 2020, 18:02 GMT
Suggestion on the trace generation?
Is the `coredumpctl` stack trace enough?
Comment by Balló György (City-busz) - Friday, 20 March 2020, 18:12 GMT
Maybe, but if you see something like this: '?? ()', then you have to rebuild something with debugging info.

You can see more details here:
https://wiki.archlinux.org/index.php/Debug_-_Getting_Traces
Comment by Giovanni Santini (ItachiSan) - Thursday, 26 March 2020, 18:06 GMT
Done: https://sourceforge.net/p/lxde/bugs/933/

In case they ask me the stack trace, I will oblige :)
Comment by bill-auger (bill-auger) - Sunday, 01 November 2020, 00:22 GMT
  • Field changed: Percent Complete (100% → 0%)
why is this ticket closed? - the bug is still present - a bug report should not be considered as resolved, unless the bug is fixed, or the package is removed from the repos
Comment by bill-auger (bill-auger) - Sunday, 01 November 2020, 01:02 GMT
thanks - there are two patches on the upstream mailing list - i expect that both of these patches will be upstream in the next release, or the root cause may be fixed by then; but that may take some time - it may be a good idea to apply them in arch now

'gtk3-theme-preview-segfault.patch' allow the program to function properly

'gtk3-theme-preview-hide.patch' applies the sed command in the arch PKGBUILD to the upstream sources directly - this would allow the 'lxappearance-obconf-gtk3' PKGBUILD to be merged with 'lxappearance-obconf' as a split package

https://sourceforge.net/p/lxde/mailman/lxde-list/thread/20201030001824.6817b566%40parabola/#msg37140205
Comment by bill-auger (bill-auger) - Sunday, 01 November 2020, 01:09 GMT
sry, i should have been more explicit - i forgot this bug report was against 'lxappearance-gtk3'

the bug is in 'lxappearance-obconf-gtk3' - 'lxappearance-gtk3' works properly if 'lxappearance-obconf-gtk3' is not installed - the patches are against the lxappearance-obconf v0.2.3 source code
Comment by Toolybird (Toolybird) - Monday, 01 May 2023, 06:37 GMT
Is this still an issue with latest pkgs?
Comment by bill-auger (bill-auger) - Monday, 01 May 2023, 08:28 GMT
yes, it is simple to reproduce

# pacman -Sy lxde-gtk3
$ lxappearance

-> program segfaults on launch

# pacman -R lxappearance-obconf-gtk3
$ lxappearance

-> program runs normally - "window borders" tab is unavailable

the bug exists upstream; but the patches are not yet accepted into a release - distros should apply at least the patch 'gtk3-theme-preview-segfault.patch'
Comment by Buggy McBugFace (bugbot) - Tuesday, 08 August 2023, 19:11 GMT
This is an automated comment as this bug is open for more then 2 years. Please reply if you still experience this bug otherwise this issue will be closed after 1 month.

Loading...