Github messages for voidlinux
 help / color / mirror / Atom feed
From: kruceter <kruceter@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] lxappearance-obconf: fix segfault with lxappearance
Date: Tue, 10 Jan 2023 00:23:01 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41553@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 418 bytes --]

There is a new pull request by kruceter against master on the void-packages repository

https://github.com/kruceter/void-packages lxappearance-obconf
https://github.com/void-linux/void-packages/pull/41553

lxappearance-obconf: fix segfault with lxappearance
#### Testing the changes
- I tested the changes in this PR: **YES**

A patch file from https://github.com/void-linux/void-packages/pull/41553.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-lxappearance-obconf-41553.patch --]
[-- Type: text/x-diff, Size: 1859 bytes --]

From ee73b850713a087bb0716f08506ae3c642764db7 Mon Sep 17 00:00:00 2001
From: Krul Ceter <kruceter@proton.me>
Date: Tue, 10 Jan 2023 02:01:36 +0300
Subject: [PATCH] lxappearance-obconf: fix segfault with lxappearance

---
 .../patches/gtk3-cairo-segfault.patch         | 24 +++++++++++++++++++
 srcpkgs/lxappearance-obconf/template          |  2 +-
 2 files changed, 25 insertions(+), 1 deletion(-)
 create mode 100644 srcpkgs/lxappearance-obconf/patches/gtk3-cairo-segfault.patch

diff --git a/srcpkgs/lxappearance-obconf/patches/gtk3-cairo-segfault.patch b/srcpkgs/lxappearance-obconf/patches/gtk3-cairo-segfault.patch
new file mode 100644
index 000000000000..7ff8a28b803d
--- /dev/null
+++ b/srcpkgs/lxappearance-obconf/patches/gtk3-cairo-segfault.patch
@@ -0,0 +1,24 @@
+https://github.com/lxde/lxappearance-obconf/pull/1
+
+From b31c69d41c80e92762ffe17addeb238d9df2c62b Mon Sep 17 00:00:00 2001
+From: bill-auger <mr.j.spam.me@gmail.com>
+Date: Thu, 29 Oct 2020 21:15:54 -0400
+Subject: [PATCH] fix GTK3/cairo segfault (closes sf#933)
+
+---
+ src/preview.c | 2 ++
+ 1 file changed, 2 insertions(+)
+
+diff --git a/src/preview.c b/src/preview.c
+index ada6eb3..a2fc63d 100644
+--- a/src/preview.c
++++ b/src/preview.c
+@@ -30,6 +30,8 @@
+ #include <obrender/theme.h>
+ 
+ #if GTK_CHECK_VERSION(3, 0, 0)
++#include <cairo/cairo.h>
++#include <cairo/cairo-xlib.h>
+ #include <gdk/gdkx.h>
+ #endif
+ 
diff --git a/srcpkgs/lxappearance-obconf/template b/srcpkgs/lxappearance-obconf/template
index 063e6d0380a5..d95d3bc795e6 100644
--- a/srcpkgs/lxappearance-obconf/template
+++ b/srcpkgs/lxappearance-obconf/template
@@ -1,7 +1,7 @@
 # Template file for 'lxappearance-obconf'
 pkgname=lxappearance-obconf
 version=0.2.3
-revision=3
+revision=4
 build_style=gnu-configure
 configure_args="--disable-static --enable-gtk3"
 hostmakedepends="pkg-config intltool"

             reply	other threads:[~2023-01-09 23:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-09 23:23 kruceter [this message]
2023-01-10  4:53 ` [PR PATCH] [Merged]: " sgn

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

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

  git send-email \
    --in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41553@inbox.vuxu.org \
    --to=kruceter@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).