[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1121244: marked as done (trixie-pu: package qiv/3.0.1-2+deb13u1)

Your message dated Sat, 10 Jan 2026 11:52:34 +0000
with message-id <E1veXWE-00000004Rgl-3Lfp@coccia.debian.org>
and subject line Released with 13.3
has caused the Debian Bug report #1121244,
regarding trixie-pu: package qiv/3.0.1-2+deb13u1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1121244: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1121244
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
Tags: trixie
X-Debbugs-Cc: qiv@packages.debian.org, bartm@debian.org
Control: affects -1 + src:qiv
User: release.debian.org@packages.debian.org
Usertags: pu

Can qiv 3.0.1-2+deb13u1 be added in trixie-updates?
qiv 3.0.1-2 in trixie always produces a 'segmentation fault'. qiv
3.0.1-2+deb13u1 includes the smallest possible fix. The fix is
cherry-picked from a newer upstream release of qiv.

[ Reason ]
qiv 3.0.1-2 in trixie always produces a 'segmentation fault'.

[ Impact ]
qiv 3.0.1-2 in trixie is unusable most users. Only users who find their
way to the workaround on #1103712 know how to make the package usable.

[ Tests ]
Switching between 3.0.1-2 and 3.0.1-2+deb13u1 makes the problem appear
and go away 100% of the times. Tested on a fresh trixie setup.

[ Risks ]
In my view the risk is low. It is an extremely small code change.

[ Checklist ]
  [x] *all* changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in (old)stable
  [x] the issue is verified as fixed in unstable

[ Changes ]
Added patch debian/patches/putenv-x11.diff is cherry-picked from
upstream. It adds 'putenv("GDK_BACKEND=x11");' to the source code.
Upstream's explantion is "set GDK backend to x11. Otherwise qiv won't
work on wayland.". This matches the reported problem on #1103712.

[ Other info ]
/

diff -ruNw orig/qiv-3.0.1/debian/changelog qiv-3.0.1/debian/changelog
--- orig/qiv-3.0.1/debian/changelog	2025-04-13 16:42:36.000000000 +0200
+++ qiv-3.0.1/debian/changelog	2025-11-23 17:21:30.527618738 +0100
@@ -1,3 +1,9 @@
+qiv (3.0.1-2+deb13u1) trixie; urgency=medium
+
+  * debian/patches/putenv-x11.diff: Fixes: #1103712 for trixie.
+
+ -- Bart Martens <bartm@debian.org>  Sun, 23 Nov 2025 17:20:30 +0100
+
 qiv (3.0.1-2) unstable; urgency=medium
 
   * debian/patches/background.diff: Closes: #1102608.
diff -ruNw orig/qiv-3.0.1/debian/patches/putenv-x11.diff qiv-3.0.1/debian/patches/putenv-x11.diff
--- orig/qiv-3.0.1/debian/patches/putenv-x11.diff	1970-01-01 01:00:00.000000000 +0100
+++ qiv-3.0.1/debian/patches/putenv-x11.diff	2025-11-23 17:20:04.011515594 +0100
@@ -0,0 +1,14 @@
+Index: qiv-3.0.1/main.c
+===================================================================
+--- qiv-3.0.1.orig/main.c
++++ qiv-3.0.1/main.c
+@@ -55,6 +55,9 @@ int main(int argc, char **argv)
+   int dot_clock;
+ */
+ 
++  // set GDK backend to x11. Otherwise qiv won't work on wayland.
++  putenv("GDK_BACKEND=x11");
++
+   /* Randomize seed for 'true' random */
+   gettimeofday(&tv,NULL);
+   srand(tv.tv_usec*1000000+tv.tv_sec);
diff -ruNw orig/qiv-3.0.1/debian/patches/series qiv-3.0.1/debian/patches/series
--- orig/qiv-3.0.1/debian/patches/series	2025-04-13 16:41:48.000000000 +0200
+++ qiv-3.0.1/debian/patches/series	2025-11-23 17:18:57.291436665 +0100
@@ -1,2 +1,3 @@
 prefix.diff
 background.diff
+putenv-x11.diff

--- End Message ---
--- Begin Message --- 
Package: release.debian.org\nVersion: 13.3\n\nThis update has been released as part of Debian 13.3.

--- End Message ---
Reply to: