unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Reza Alizadeh Majd <r.majd@pantherx.org>
Cc: 37725@debbugs.gnu.org
Subject: [bug#37725] [PATCH] gnu: lxqt-config: Add libkscreen as propagated-inputs.
Date: Fri, 18 Oct 2019 11:54:27 +0200	[thread overview]
Message-ID: <87wod24bvw.fsf@gnu.org> (raw)
In-Reply-To: <38aa418c-7f64-452b-b49c-8f1b4d2d914e@www.fastmail.com> (Reza Alizadeh Majd's message of "Wed, 16 Oct 2019 14:48:18 +0330")

Hi Reza,

"Reza Alizadeh Majd" <r.majd@pantherx.org> skribis:

> maybe I could describe better about this patch file.
>
> `libkscreen`  is used by `lxqt-config-monitor` to modify
> the desktop resolution in LXQt desktop. 
>
> the problem is that, during execution of `lxqt-config-monitor` 
> application crashes with "segmentation fault". 
>
> we had a review over `lxqt-config-monitor` source code, 
> but didn't find any unusual usage of `ksceen` library. just 
> a normal link during build process and binaries were made 
> successfully. 
>
> this issue might because of crash inside `libkscreen`, but we
> didn't  review that yet. 
>
> so as a quick workaround we find that adding the `libkscreen`
> as a propagated input could fix this issue.

Thanks for explaining, I understand better now.

I think that it’s not satisfying to apply a workaround that we don’t
understand.  That is, intuitively, I see now reason why propagating
libkscreen would “fix” a segfault.

Could you either (1) provide an ‘operating-system’ config and
instructions to reproduce the problem, or (2) grab a backtrace of the
segfaulted program with GDB?

Let us know if you need guidance.

Thanks,
Ludo’.

  reply	other threads:[~2019-10-18  9:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-13  4:23 [bug#37725] [PATCH] gnu: lxqt-config: Add libkscreen as propagated-inputs Hamzeh Nasajpour
2019-10-13 22:07 ` Ludovic Courtès
2019-10-14  5:50   ` Hamzeh Nasajpour
2019-10-14 20:21     ` Ludovic Courtès
2020-04-02 19:17       ` Hamzeh Nasajpour
2020-04-27 16:39         ` Efraim Flashner
2019-10-16 11:18 ` Reza Alizadeh Majd
2019-10-18  9:54   ` Ludovic Courtès [this message]
2019-10-18 16:44     ` Reza Alizadeh Majd
2020-04-22 15:50       ` Ludovic Courtès
2020-09-16  8:40 ` Hamzeh Nasajpour via web

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wod24bvw.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=37725@debbugs.gnu.org \
    --cc=r.majd@pantherx.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).