Bug#1059146: pandoc produces html5 that gives lintian errors
On Wed, 20 Dec 2023 14:35:09 +0100 Andreas =?UTF-8?B?UsO2bm5xdWlzdA==?= wrote: > Package: pandoc > Version: 3.0.1+ds-3 > Severity: normal > > Dear Maintainer, > > Pandoc produces html5 that gives lintian errors - for example: > > E: allegro5-doc: privacy-breach-uses-embedded-file You may use the > node-html5shiv package (virtual package). > (//cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7.3/html5shiv-printshiv.min.js) > [usr/share/doc/allegro5-doc/refman/acodec.html] > > This is due to the html5 template in pandoc contains the following code block: > > > > This is reported to pandoc upstream, but they find the problem not > worth "introducing additional complexities to deal with this", because > it only affects older IE browsers. > > See https://github.com/jgm/pandoc/issues/6809 . > And now the mentioned code block has been deleted from the template in the upstream package. Could you please remove it from the Debian package too to make lintian not give errors? https://github.com/jgm/pandoc/commit/907b1192d1f5a5f1b8c5156693e0ba4c63f02c2f /Andreas
Bug#1052503: RFS: scite/5.3.8-1 -- Lightweight GTK-based programming editor
On Sat, 23 Sep 2023 14:28:28 +0200, Andreas Rönnquist wrote: >Package: sponsorship-requests >Severity: normal > >Dear mentors, > >I am looking for a sponsor for my package "scite": >(I am a DD, but currently without my gpg key, and in the progress to get >signatures for a new key, so I am forced to seek sponsors for my >uploads). > I still need a sponsor for this (Just posting so you don't get fooled by the previous message in the thread). thanks in advance -- Andreas Rönnquist mailingli...@gusnan.se gus...@debian.org
Bug#1035106: RFS: cdreaper/3.0.0-1 [ITP 1035103] -- Graphical audio CD ripper and encoder
On Sat, 29 Apr 2023 20:10:02 +0100, Peter Blackman wrote: >Package: sponsorship-requests >Severity: wishlist > >Dear mentors, > >I am looking for a sponsor for my package "cdreaper": > >cdreaper is the Gtk3 fork of asunder >https://tracker.debian.org/pkg/asunder > >I would like to set up a packaging VCS on Salsa under the debian group, >but don't have the privilege to create an empty repository there myself. > > * Package name : cdreaper > Version : 3.0.0-1 > Upstream contact : Salamandar > * URL : https://gitlab.gnome.org/Salamandar/Reaper > * License : GPL-2, CC0-1.0 > * Vcs : pending > Section : sound > Please notice that there might be a rename of the project (See #4 on the upstream bugtracker [1]). On another note - I would gladly co-maintain this (whatever the name turns out to be in the end :). 1: https://gitlab.gnome.org/Salamandar/Reaper/-/issues/7#note_1733028 -- Andreas Rönnquist mailingli...@gusnan.se andr...@ronnquist.net
Bug#1011417: Bug#857540: scite: Scroll bar not moving when scrolling
On Thu, 26 Oct 2017 17:09:36 +0200 Andreas Ronnquist wrote: 8< > > The problem is still there - but I am now under the impression that it > is a libgtk3 problem, and not a SciTE problem. > > See > https://bugzilla.gnome.org/show_bug.cgi?id=765410 > The SciTE part of this bug has been fixed in scite 5.2.3-1 (or worked-around, to be honest) - So I clone it and reassign one of the clones to scite and close it there. I believe there's other programs that are affected (like Geany, as mentioned in the upstream bug), so I keep this clone open here. -- Andreas Rönnquist gus...@debian.org
Bug#1005965: scite: leaks X pixmaps upon window switch
Thanks for your report - I have forwarded this upstream. The new thing in 5.2.0 is that it has added a multithreaded layout to improve performance, where I believe some memory leaks have sneaked their way in. best /Andreas Rönnquist gus...@debian.org
Bug#981011: O: gftp -- X/GTK+ and console FTP client (metapackage)
Hi! I have noticed that you marked my bug orphaning gftp as owned by you (which annotation then was removed). As you can see I am still kind of maintaining gftp, even though I have marked it as orphaned. What would you say about co-maintaining the package? I would be fine with that. I noticed now recently that FTPS was compiled in, and quickly (and wrongly) enabled it in the build, uploading to unstable. This shouldn't be done, so I undid the change quickly - there are license problems with the openssl license and the GPL. [1] This however, will be solved by changing the license of gftp to the MIT license, which won't cause the same problems. Upstream is already in progress with the change. [2] After this is done we can enable the FTPS support again. The remaining bigger problem with the package is that it is still using GTK2. This is tracked at [3] and in Debian at [4]. As you probably are aware, programs that only support GTK2 will get removed from Debian sooner or later. -- Andreas Rönnquist gus...@debian.org 1: https://people.gnome.org/~markmc/openssl-and-the-gpl.html 2: https://github.com/masneyb/gftp/pull/133 3: https://github.com/masneyb/gftp/issues/91 4: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967390
Bug#544985: gftp: Is crashing when level changing directory on running transfer
fixed 544985 2.8.0~beta-1 thanks On Fri, 04 Sep 2009 11:50:31 +0200 Frank Lanitz wrote: > Package: gftp > Version: 2.0.19-1 > Severity: normal > > > gftp-gtk is crashing when trying to go up one directory (..) in case > of an transfer is proceed. I can reproduce this on having a ssh2 > session running and transfering data via it. > > Thanks for your report - this seems to have been fixed in 2.8.0~beta-1, I cannot reproduce it with this version- Please reply back if you still see this problem. best /Andreas gus...@debian.org
Bug#997023: sakura: Incorrect usage of PRIMARY and CLIPBOARD selections
Thanks for your report (and patch) - As you might have seen, the patch is now included in the git repo upstream - If a new upstream version takes a longer time, I'll prepare an updated Debian package including the patch. best regards, and thank you! /Andreas Rönnquist gus...@debian.org
Bug#997023: sakura: Incorrect usage of PRIMARY and CLIPBOARD selections
On Fri, 29 Oct 2021 21:03:36 +0200 Fabio Cobianchi wrote: >Package: sakura >Version: 3.8.4-1 >Followup-For: Bug #997023 >X-Debbugs-Cc: c...@mailbox.org > >Dear Maintainer, > >maybe I have found the problem; >I have downloaded version 3.8.4-1 from 'testing' and, with the patch >attached in this e-mail, the bug, for me, is resolved. > --- 8< --- Thank you very much for the patch! It fixes the problem for me too. I have forwarded it to upstream with this information: https://code.launchpad.net/~gusnan/sakura/+git/sakura/+merge/411052 You could comment there if you have more information you wish to add. Thank you very much! /Andreas gus...@debian.org
Bug#995463: geeqie: doesn't save preferences
On Fri, 01 Oct 2021 16:44:30 +0200 Emilian Nowak wrote: >Dear Maintainer, >Each time I uncheck option >Edit -> Preferences -> Image -> Convenience -> "Auto rotate proofs >using Exif information" >after restart of geeqie it is still checked. >Seems like this preferece is not saved. >There is no error about that in console, neither in UI. > > Thanks for your report - as you can see I have forwarded the bug to upstream, and they claim it is intended for the print mechanism, which is redundant when using the standard GTK method for printing. So, if I interpret upstream correctly, they will probably remove the option. I guess it is only this specific option that doesn't stick, and not any others? Please report back if other options doesn't stick for you (I can reproduce it for this one). /Andreas gus...@debian.org
Bug#831016: qscintilla text cursor wrong position
On Wed, 13 Jul 2016 19:58:33 +0200 VA wrote: > Package: python-pyqt5.qsci > Version: 2.9.2+dfsg-3 > > The text cursor in qscintilla widgets seems to offset on the right > compared to the position it should be, and the offset seems to move. > Here's a little screencast to show the problem: > https://lut.im/35DY1KfuWK/iBqSApFpNCFf1t3O.gif > The text cursor should be right after the character typed, but it's > much more to the right. Situation is even worse when editing text in > the middle of a line. > > The issue appears when using "eric", and can also be demonstrated > with a basic PyQt program: > > Can anybody reproduce this on an up to date unstable? Or even on a SciTE in Bullseye (Debian 11)? I haven't seen this for some time (I _think_ lastly on Jessie, maaaybe on Stretch). I think has solved itself, by changes in either GTK or SciTE, but I haven't seen it in a long time. Please report back, in both cases, either if you still see the problem, or if you can report that you haven't seen it in some time. If no one has seen it in some time I am inclined to close this bug. best, and thank you for you reports /Andreas Rönnquist gus...@debian.org
Bug#980368: geeqie: Lossless JPEG rotation does not work
On Mon, 18 Jan 2021 09:42:14 +0100 =?utf-8?Q?=C5=81ukasz_Stelmach?= wrote: > Package: geeqie > Version: 1:1.4+git20190121-2 > Severity: normal > > Dear Maintainer, > > I want to losslessly rotate a JPEG file. The file is displayed > properly. > > I choose Edit -> Orientation -> Losslessly rotate JPEG image > clockwise. > > An error dialog appears saying > > External command failed > > Can't find matching file type. Unable to start external command. > > The image orientation does not change as expected. > Can you reproduce it with an up to date geeqie? There's already 1.6 in stable now. Please try that version, and report back. It works fine for me in both stable and unstable. If the problem is still there, can you provide the image that gives the problems? Preferably a link to a place where you have uploaded it. /Andreas Rönnquist gus...@debian.org
Bug#989684: Geeqie crashed on startup with "X Window System error"
On Thu, 26 Aug 2021 08:05:44 +0200 Jörg Sommer wrote: >Andreas Ronnquist schrieb am Mi 25. Aug, 14:16 (+0200): >> Is this only affecting geeqie, or are you seeing it on other programs >> that use the clutter library? >> >> You can find these by a command like >> >> sudo apt-cache rdepends libclutter-1.0 > >I can't tell. I don't use any of these programs. > Could you please try to install one of them, and report if you see the same behavoiur when running them? You can copy the apt output when installing, and then remove/purge the programs and dependencies that was installed. It would greatly help to determine if it is a libclutter problem, which I greatly suspect it is, or specific to geeqie. /Andreas
Bug#989684: Geeqie crashed on startup with "X Window System error"
Is this only affecting geeqie, or are you seeing it on other programs that use the clutter library? You can find these by a command like sudo apt-cache rdepends libclutter-1.0 - examples are gnome-2048 or empathy. It would be interesting, because if you see the same problem on other programs it's a clutter-specific problem, and I can reassign this bug to the clutter library. (I am assuming it is a libclutter problem). -- Andreas Rönnquist gus...@debian.org
Bug#922615: nvidia-driver: Windows not visible on third screen after stable upgrade
I have just upgraded to Bullseye (and nvidia-driver 460.91.03-1) - and this problem is gone. Feel free to close this bug. (I leave this to you, if you want to track this further, otherwise I am fine with you closing it). Thanks for packaging and maintaining the Nvidia drivers! -- Andreas Rönnquist gus...@debian.org
Bug#990826: lollypop: Segmentation fault - cannot start lollypop
On Thu, 8 Jul 2021 20:20:35 + Amr Ibrahim wrote: > On Thu, 2021-07-08 at 21:45 +0200, Andreas Ronnquist wrote: > > Thanks for your report - Could you please try to reproduce when > > running lollypop from a terminal using "lollypop -d"? It should give > > more useful debugging information. > > > Thanks for your reply. The debug log is attached. > Thanks - I am sorry to say that I cannot reproduce the segfault with the file you provided - Could you please try to debug it using gdb? - This might give more useful information. In short, install the debug package of lollypop (I am suspecting that the problem is in some other package though) - run lollypop in gdb as gdb lollypop and when it crashes you'll get back to gdb, and there get a backtrace with the command - bt full this would give a better backtrace, and probably reveal if the problem is in lollypop or in some library. For more details, you can see https://wiki.debian.org/HowToGetABacktrace best /Andreas
Bug#990826: lollypop: Segmentation fault - cannot start lollypop
On Thu, 08 Jul 2021 18:33:25 +0200 Amr Ibrahim wrote: > Package: lollypop > Version: 1.4.14-1 > Severity: important > X-Debbugs-Cc: amribrahim1...@hotmail.com > > Dear Maintainer, > > I cannot start lollypop due to a segmentation fault. This is on GNOME > Shell Wayland. > > To reproduce in a terminal: > - 8< - Thanks for your report - Could you please try to reproduce when running lollypop from a terminal using "lollypop -d"? It should give more useful debugging information. /Andreas Rönnquist gus...@debian.org
Bug#986964: geeqie: View in new window, new window black until zoom in/out
On Wed, 14 Apr 2021 09:47:07 -0700 Dean Hamstead wrote: >Package: geeqie >Version: 1:1.6-8 >Severity: normal > >Dear Maintainer, > >When an image is opened in a new window, the new window content are >black. Zooming in or out the image appears. > >Not certain how to debug. > Thanks for your report. Are you on wayland? (You can find out by running echo $XDG_SESSION_TYPE in a terminal). Also, I see something similar if I run without "GPU acceleration via Clutter library" - see preferences under "Image", "Use GPU acceleration via Clutter library" - is that checked for you? If I select to run without clutter, I see something similar to what you see. (I will forward this to upstream, but this could possibly be at least a temporary workaround). /Andreas Rönnquist gus...@debian.org
Bug#986862: lollypop: Filename args doesn't work when Lollypop is already running
On Tue, 13 Apr 2021 00:38:47 +0200 Pelle wrote: > Dear Maintainer, > > Running `lollypop foo.mp3` will open up Lollypop and play foo.mp3, > unless Lollypop is already running, in which case Lollypop will > switch to a random track. I expected the command `lollypop foo.mp3` > to play foo.mp3, even when Lollypop is already open. > Thanks for your report - I can reproduce the problem to some extent. What if you run the command and include the full path to the file? Does this change things? What settings to you have for playback? Anything exotic, like "Continuous playback", "Automatic playback (random)" or "Automatic playback (similar)"? /Andreas gus...@debian.org
Bug#984942: Update lollypop to 1.4.17
On Mon, 12 Apr 2021 17:37:05 +0200 Amr Ibrahim wrote: >I had the impression that the Release team does not mind a >bug-only-fix release update, as Lollypop is a leaf package, and the >1.4.14+ versions has only small bug fixes by looking at their git >commits. > > Please do not top post, and trim the message you are replying to. From https://release.debian.org/bullseye/freeze-policy.html : >Soft Freeze > >Starting 2021-02-12, only small, targeted fixes are appropriate for >bullseye. We want maintainers to focus on small, targeted fixes. This >is mainly at the maintainers discretion, there will be no hard rule >that will be enforced. And further down on the same page: >Targeted fixes >A targeted fix is one with only the minimum necessary changes to >resolve a bug. The freeze process is designed to make as few changes >as possible to the forthcoming release. Uploading unrelated changes is >likely to result in a request for you to revert them if you want an >unblock. > >In most cases, it's not appropriate to upload a new upstream release >at this point. New upstream release usually contain unrelated changes, >which might be inappropriate or make review much more difficult. >Uploading a new upstream release is only appropriate when the >resulting debdiff doesn't contain changes that wouldn't be in the >debdiff of a targeted change. When in doubt, ask for pre-approval >before uploading a new upstream release. To me it seems like a targeted fix is one that fixes a specific bug in unstable, and I don't think that "Please update to a newer upstream version" is a really valid candidate as a bug intended for such a fix. And since we have no other bugs than that, I don't see what a targeted fix should do. If there are actual problems with the package, PLEASE report bugs for them, with a valid severity level. If you think otherwise, feel free to contact the release team with a new package fixing bugs and a debdiff and try to convince them. At this point, I'd say that you are out of luck. (And that is even at the time when the bug was reported). And yes, I know I might have been able to squeeze in some later releases of Lollypop into bullseye, but I didn't have the resources to do packaging of Lollypop at that time. /Andreas Rönnquist gus...@debian.org
Bug#986314: RFS: gsimplecal/2.1-2 [QA] -- lightweight GUI calendar application
On Fri, 02 Apr 2021 17:58:45 -0300, Hugo Torres de Lima wrote: >Package: sponsorship-requests >Severity: normal > >Dear mentors, > >I am looking for a sponsor for my package "gsimplecal": > > * Package name: gsimplecal > Version : 2.1-2 > Upstream Author : https://github.com/dmedvinsky/gsimplecal/issues > * URL : https://dmedvinsky.github.io/gsimplecal > * License : BSD-3-Clause > * Vcs : > http://anonscm.debian.org/cgit/collab-maint/gsimplecal.git Section > : misc > >It builds those binary packages: > > gsimplecal - lightweight GUI calendar application > >To access further information about this package, please visit the >following URL: > > https://mentors.debian.net/package/gsimplecal/ > -- 8< -- There seems to be changes in salsa, which has updated the Vcs-*-fields, while yours are still pointing to alioth. https://salsa.debian.org/jmsrdebian/gsimplecal/-/blob/debian/master/debian/changelog Also, there seems to be an upstream 2.2 available from February, which could be nice to package. -- Andreas Rönnquist mailingli...@gusnan.se gus...@debian.org
Bug#985404: qa.debian.org: Packages overview VCS field doesn't consider a debian/experimental branch
On Wed, 17 Mar 2021 16:47:02 +0100 Mattia Rizzolo wrote: >On Wed, Mar 17, 2021 at 03:59:43PM +0100, Andreas Rönnquist wrote: >> The VCS field on developer Packages overview doesn't seem to >> consider a debian/experimental branch. > >How would DDPO (actually, vcswatch is the component you are interested >in) go about knowing that. > >> The Package overview shows Git - 4.4.5-2 (with the version in red as >> if there's a problem with it) as if that is the latest in Git. > >The problem is in your packages. >The branch vcswatch is using the one pointed by HEAD. If that doesn't >contain the version it is expecting, that's marked as an error. > >In your case, you should be specifying the branch in Vcs-Git, using the >-b flag, as documented in Policy. > >> I can see other packages that have experimental packaging in the >> debian/master branch not showing this as a problem, > >Yes, that's correct, because HEAD points to the branch containing the >most up-to-date packaging. > >> or even those where >> the experimental branch is called simply experimental (and not >> debian/experimental) also not showing the version as problematic. > >This sounds weird, do you have an example? > Ah, thanks. I was looking at python-cartopy but didn't notice that there gbp.conf is also updated with proper branch info for each branch. I guess that is why that package don't report a problem, and mine does. Sorry for the noise, and thanks for the education! best /Andreas gus...@debian.org
Bug#965339: geeqie: Geeqie is painfully slow since GTK3
On Wed, 18 Nov 2020 21:22:49 +0100 Adrien CLERC wrote: > Le 15/11/2020 à 16:14, Andreas Ronnquist a écrit : > > Hey guys - > > > > I have packaged a new git snapshot, downloadable from here: > > > > https://www.gusnan.se/debian/geeqie-common_1.5.1+git20201112-fae4de3c-1_all.deb > > https://www.gusnan.se/debian/geeqie_1.5.1+git20201112-fae4de3c-1_amd64.deb > > > > (You'll need to install both debs). > > > > Could you please try it out, and see if it affects your problems? > > > > There have been some progress which I think should be affecting the > > problems you have reported. > > OK, this package does not solve the issue. I tried in a directory > with 31 files of about 4.5MB each, so quite small. Without "Show > marks", it is fast as it should be. With "Show marks" (toggling with > 'M'), it is slow. > > However, I've spotted something. If I repeatedly go forward and > backward on a set of 2 images, it is gradually slower over time. As > if an internal structure was never cleaned and growing ever and ever. > And to be noticeable, it could come from an exponentially growing > structure. > > I hope this can help… > Are you using Clutter? Could you check the Preferences - Image tab, if the "Use GPU acceleration via Clutter library (Requires restart)" checkbox (close to the top) is checked? I noticed somewhere that some slowdown might simply be related to using the Clutter library. If so, please try to de-check the checkbox and see if that improves performance. (Geeqie should work equally well disregarding if Clutter is used or not). /Andreas gus...@debian.org
Bug#984942: Update lollypop to 1.4.17
On Wed, 10 Mar 2021 17:53:35 + Amr Ibrahim wrote: > Please update lollypop to 1.4.17. It's a bug-fix release. > > https://gitlab.gnome.org/World/lollypop/-/releases Bullseye is frozen for the next Debian release, and because of this: "only small targeted fixes are appropriate for bullseye. We want maintainers to focus on small, targeted fixes." https://lists.debian.org/debian-devel-announce/2021/02/msg2.html New upstream releases are most definitely not being considered because of this. If there are bugs in the package, those could be fixed with "targeted fixes", but since no bugs are reported on the package... /Andreas Rönnquist gus...@debian.org
Bug#916756: geeqie: fullscreen spanning multiuple monitors does not work
On Tue, 18 Dec 2018 10:51:10 +0100 Jiri Bohac wrote: > > Dear Maintainer, > > geeqie support for fullscreen spanning all monitors is broken since > jessie. > > I reported the bug upstream and provided a patch. > https://github.com/BestImageViewer/geeqie/issues/650 > > Trouble is the patch only works if geeqie is compiled with GTK3, so > for Debian, either a GTK2 backport of the patch would be needed or > geeqie would have to be switched to GTK3 (bug 904976). > > We use geeqie for stereoscopic projections with two projectors and > without working multi-monitor fullscreen, geeqie is unusable. > Hi! Is this still a problem for you with the version from unstable? (1:1.6-8) It looks like a patch was included in geeqie upstream, and it should be included in unstable now. best regards /Andreas Rönnquist gus...@debian.org
Bug#983628: unblock: geeqie/1:1.6-7
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package geeqie
This new version fixes a recently discovered regression, in remote
handling in geeqie. It closes #983546 - a regression in the way you
could show an image in an already running geeqie, instead of starting a
new instance of the program. (Without the fix and running remote
geeqie instance it always starts new instances of the program).
Leaf package, small fix, not many alternatives to this particular usage
according to the bug reporter.
(The patch also removes a trailing whitespace in d/changelog, which
itself isn't mentioned in the changelog.)
unblock geeqie/1:1.6-7
-- Andreas Rönnquist
gus...@debian.org
diff -Nru geeqie-1.6/debian/changelog geeqie-1.6/debian/changelog
--- geeqie-1.6/debian/changelog 2021-01-16 15:05:21.0 +0100
+++ geeqie-1.6/debian/changelog 2021-02-27 13:36:57.0 +0100
@@ -1,3 +1,10 @@
+geeqie (1:1.6-7) unstable; urgency=medium
+
+ * Add patch fixing regression --remote option failing
+(Closes: #983546)
+
+ -- Andreas Rönnquist Sat, 27 Feb 2021 13:36:57 +0100
+
geeqie (1:1.6-6) unstable; urgency=medium
* Add patch to fix which image rotatation-keys affect
@@ -13,7 +20,7 @@
geeqie (1:1.6-4) unstable; urgency=medium
- * Add patch to fix segfault on X with clutter
+ * Add patch to fix segfault on X with clutter
(Closes: #979463, #979561, #971403)
-- Andreas Rönnquist Sat, 09 Jan 2021 13:47:51 +0100
diff -Nru geeqie-1.6/debian/patches/0006-Fix-860-871-remote-and-slideshow-on-startup.patch geeqie-1.6/debian/patches/0006-Fix-860-871-remote-and-slideshow-on-startup.patch
--- geeqie-1.6/debian/patches/0006-Fix-860-871-remote-and-slideshow-on-startup.patch 1970-01-01 01:00:00.0 +0100
+++ geeqie-1.6/debian/patches/0006-Fix-860-871-remote-and-slideshow-on-startup.patch 2021-02-27 13:30:35.0 +0100
@@ -0,0 +1,32 @@
+From: Colin Clark
+Date: Sat, 27 Feb 2021 09:12:40 +
+Subject: Fix #860, #871: --remote and --slideshow on startup
+
+https://github.com/BestImageViewer/geeqie/issues/860
+https://github.com/BestImageViewer/geeqie/issues/871
+
+Remote slideshow delay is ignored
+
+--remote --File=IMAGE fails: not displaying image, not using running
+instance, not forking
+---
+ src/main.c | 6 --
+ 1 file changed, 6 deletions(-)
+
+diff --git a/src/main.c b/src/main.c
+index 1356f9a..54c10ea 100644
+--- a/src/main.c
b/src/main.c
+@@ -453,12 +453,6 @@ static void parse_command_line(gint argc, gchar *argv[])
+ }
+ remote_list = g_list_prepend(remote_list, "--new-window");
+ }
+- else if (!remote_server_exists(app_lock))
+- {
+- /* Geeqie started for first time but with --remote option
+- */
+- remote_do = FALSE;
+- }
+ g_free(app_lock);
+ }
+
diff -Nru geeqie-1.6/debian/patches/series geeqie-1.6/debian/patches/series
--- geeqie-1.6/debian/patches/series 2021-01-16 15:04:01.0 +0100
+++ geeqie-1.6/debian/patches/series 2021-02-27 13:30:35.0 +0100
@@ -3,3 +3,4 @@
0003-Fix-832-Geeqie-remembers-desktop.patch
0004-Fix-829-segfault-with-clutter-gtk.patch
0005-Fix-822-The-image-rotation-keys-and-affect-the-wrong.patch
+0006-Fix-860-871-remote-and-slideshow-on-startup.patch
Bug#981011: O: gftp -- X/GTK+ and console FTP client (metapackage)
Package: wnpp Severity: normal I intend to orphan the gftp package. The package description is: gFTP is a multithreaded FTP client, available in two versions: * version for X, written using GLib and GTK+ * version for the console, using only GLib -- Andreas Rönnquist gus...@debian.org
Bug#980942: RFA: lollypop -- modern music player
Package: wnpp Severity: normal I request an adopter for the lollypop package. The package description is: A Music player for GNOME featuring intuitive browsing of your music -- Andreas Rönnquist gus...@debian.org
Bug#979701: geeqie: menu bar limited to left panel
On Sun, 10 Jan 2021 11:19:15 +0100 Lionel Elie Mamane wrote: >Package: geeqie >Version: 1:1.6-5 >Severity: important > >In geeqie 1.6, the menu bar is limited in width to the left panel, and >thus is truncated when the left panel is narrower than the menu bar >needs to be. In geeqie 1.5, the menu bar was always full width, which >suits layouts with a narrow left panel much better. > >See the circled red areas in the attached screenshots. > Please see the settings: Edit -> Preferences and there under the general tab you have a checkbox for "Expand menu and toolbar (NOTE! Geeqie must be restarted for change to take effect". Please change that checkbox, restart geeqie, and report back here if that solved your problem or not. /Andreas Rönnquist gus...@debian.org
Bug#979463: crash when run for remote DISPLAY
On Wed, 6 Jan 2021 23:13:21 +0100 Eduard Bloch wrote: > Package: geeqie > Version: 1:1.6-3 > Severity: important > > Just what the description says. You start geeqie and the only > parameter is a picture file (regular JPG). > > Result: application crashes (SIGSEGV). gdb (with symbols loaded) does > not reveal much: > Thanks for your report. In this case I believe the fact that you are running remote isn't a factor of the crash - the backtrace is identical to what some people report in a upstream report with activity recently. https://github.com/BestImageViewer/geeqie/issues/829 I have set this bug as forwarded to that upstream one. It looks like it is a deal of reverting one commit, I'll see what upstream does, and either get a new potential upstream or cherry-pick a patch when one comes. /Andreas Rönnquist gus...@debian.org
Bug#978474: xfwm4: Some native system applications do not follow the theme of windows.
On Sun, 27 Dec 2020 18:04:01 -0300, Wellington Almeida wrote: >When changing the theme of windows in the system's appearance managers >I noticed that some applications have not been modified. > > Which programs doesn't change, and what theme are you changing to? I am guessing you are setting a GTK3-only theme, and the programs that doesn't change are GTK2 ones. /Andreas Rönnquist gus...@debian.org
Bug#977189: geeqie: No image is rendered, only white rectangle visible
On Sat, 12 Dec 2020 10:14:53 +0100 Roberto Lumbreras wrote: > Package: geeqie > Version: 1:1.6-2 > Severity: important > > Geeqie just renders all images as white boxes. > It seems this is a common and old problem with Wayland, leaving geeqie > unusable. > I'm running stock Debian Gnome, which apparently means Wayland. > Upgrading to qeeqie/unstable didn't help. > > Regards, > Roberto > Please try to go to Edit->Preferences-> Image Tab, and change the checkbox "Use GPU acceleration via Clutter library", and then restart geeqie. This should make the images visible again. regards /Andreas Rönnquist gus...@debian.org
Bug#977139: geeqie: fails immediatly after start
On Fri, 11 Dec 2020 19:34:09 +0300 Ilya Ovchinnikov wrote: > On 11.12.2020 19:17, Andreas Ronnquist wrote: > > On Fri, 11 Dec 2020 17:50:07 +0300 > > Ilya Ovchinnikov wrote: > > > >> Package: geeqie > >> Version: 1:1.6-2 > >> Severity: grave > >> Justification: renders package unusable > >> > >> Dear Maintainer, > >> > >> Since last upgrade geeqie fails to start: > >> > >> % geeqie > >> > >> (geeqie:987585): Gtk-CRITICAL **: 17:45:52.857: > >> gtk_box_gadget_distribute: assertion 'size >= 0' failed in > >> GtkScrollbar > >> As in the upstream bug report - for a work-around please try to change the preferences in Edit/Preferences/Windows and de-select "Remember window positions". /Andreas gus...@debian.org
Bug#977139: geeqie: fails immediatly after start
On Fri, 11 Dec 2020 19:34:09 +0300 Ilya Ovchinnikov wrote: >On 11.12.2020 19:17, Andreas Ronnquist wrote: >> On Fri, 11 Dec 2020 17:50:07 +0300 >> Ilya Ovchinnikov wrote: >> >>> Package: geeqie >>> Version: 1:1.6-2 >>> Severity: grave >>> Justification: renders package unusable 8< > >> I am guessing you are running X? (You can quickly find out by the >> command >> >> echo $XDG_SESSION_TYPE >> in the terminal.) > >x11 > >[Detaching after vfork from child process 990936] >[Thread 0x7fffceffd700 (LWP 990929) exited] >^C >Thread 1 "geeqie" received signal SIGINT, Interrupt. >0x7617a39f in poll () from /lib/x86_64-linux-gnu/libc.so.6 >(gdb) bt >#0 0x7617a39f in poll () at /lib/x86_64-linux-gnu/libc.so.6 >#1 0x77230e1e in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 >#2 0x7723117b in g_main_loop_run () at >/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x77a407a5 in >gtk_main () at /lib/x86_64-linux-gnu/libgtk-3.so.0 #4 >0x555c9916 in () #5 0x760add0a in __libc_start_main >() at /lib/x86_64-linux-gnu/libc.so.6 #6 0x555ca54a in () >(gdb) Are you really sure that it is crashing? I have discovered that I can reproduce your problem - I see the geeqie window flashing and disappearing, and then press Ctrl+C in gdb to get the same backtrace. What is happening is that geeqie is simply moved to another workspace (probably the last workspace it was present on), and doesn't crash at all. (I thought that it crashed, just like you). When you see this behaviour, please check so geeqie isn't running on any workspace (which I suspect it still does). It sure fooled me! :) /Andreas gus...@debian.org
Bug#977139: geeqie: fails immediatly after start
On Fri, 11 Dec 2020 17:50:07 +0300 Ilya Ovchinnikov wrote: >Package: geeqie >Version: 1:1.6-2 >Severity: grave >Justification: renders package unusable > >Dear Maintainer, > >Since last upgrade geeqie fails to start: > >% geeqie > >(geeqie:987585): Gtk-CRITICAL **: 17:45:52.857: >gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkScrollbar > Thanks for the report - Is that all that gets printed, and you get a prompt immediately after? Or does it give a segfault or similar? What video-card are you using? I am guessing you are running X? (You can quickly find out by the command echo $XDG_SESSION_TYPE in the terminal.) /Andreas
Bug#976189: Catfish not starting anymore after installation of Python 3.9
I have posted a merge request at https://salsa.debian.org/python-team/packages/catfish/-/merge_requests/2 which fixes this. Please review and merge. /Andreas Rönnquist gus...@debian.org andr...@ronnquist.net
Bug#921740: Split up bug into two different
clone 921740 -1 retitle 921740 geeqie: Pointless scan of all files under a given path thanks Splitting the bug into two, since there are two different problems - Scanning all files under root file system (which already is fixed in upstream git), and the other problem, all files under a given path are scanned, which most likely will take longer to fix. -- Andreas Rönnquist gus...@debian.org
Bug#921740: Pointless scans of the root filesystem at startup
On Fri, 27 Nov 2020 23:28:25 + Steve McIntyre wrote: >On Thu, Nov 19, 2020 at 01:24:47AM +0100, Andreas Ronnquist wrote: >>On Wed, 18 Nov 2020 23:59:39 + >>Steve McIntyre wrote: >> >>>Hi Andreas! >>> >>>Thanks for looking into this for me! >>> >>>On Sun, Nov 15, 2020 at 04:23:12PM +0100, Andreas Ronnquist wrote: >>>> >>>>I have packaged a new git snapshot, downloadable from here: >>>> >>>>https://www.gusnan.se/debian/geeqie-common_1.5.1+git20201112-fae4de3c-1_all.deb >>>>https://www.gusnan.se/debian/geeqie_1.5.1+git20201112-fae4de3c-1_amd64.deb >>>> >>>>Which have fixes which I believe affects this - see the upstream >>>>commit at >>>> >>>>https://github.com/BestImageViewer/geeqie/commit/0ff5c85b082fa2b1dc578807fac8dbfd9b93421c >>>> >>>>Please try out the packages of the git snapshot linked above, and >>>>report back if it fixes the problem or not. >>> >>>I *think* it might have done, but I can't say for certain. >>> >>>The system I first saw the problem on is running Buster and so I >>>can't run your binaries there. Could you point me at a source tree >>>so I can try a rebuild on Buster please? >> >>Great - try the repo here: >> >>https://salsa.debian.org/gusnan/geeqie/ >> >>(You'll know what to do with it). > >Argh: > >tack:~/debian/geeqie$ strace -f -o strace geeqie ~/*jpg > >(geeqie:6782): Gdk-ERROR **: 23:27:04.560: The program 'geeqie' >received an X Window System error. This probably reflects a bug in the >program. The error was 'GLXBadContext'. > (Details: serial 183 error_code 158 request_code 152 (GLX) > minor_code 6) (Note to programmers: normally, X errors are reported > asynchronously; that is, you will receive the error a while after > causing it. To debug your program, run it with the GDK_SYNCHRONIZE > environment variable to change this behavior. You can then get a > meaningful backtrace from your debugger if you break on the > gdk_x_error() function.) >Trace/breakpoint trap > >No idea what's up there... :-( > >-- >Steve McIntyre, Cambridge, UK. Please try starting geeqie with --disable-clutter - this should make it possible to start, at least. I appreciate all your tests. /Andreas
Bug#921740: Pointless scans of the root filesystem at startup
On Wed, 18 Nov 2020 23:59:39 + Steve McIntyre wrote: >Hi Andreas! > >Thanks for looking into this for me! > >On Sun, Nov 15, 2020 at 04:23:12PM +0100, Andreas Ronnquist wrote: >> >>I have packaged a new git snapshot, downloadable from here: >> >>https://www.gusnan.se/debian/geeqie-common_1.5.1+git20201112-fae4de3c-1_all.deb >>https://www.gusnan.se/debian/geeqie_1.5.1+git20201112-fae4de3c-1_amd64.deb >> >>Which have fixes which I believe affects this - see the upstream >>commit at >> >>https://github.com/BestImageViewer/geeqie/commit/0ff5c85b082fa2b1dc578807fac8dbfd9b93421c >> >>Please try out the packages of the git snapshot linked above, and >>report back if it fixes the problem or not. > >I *think* it might have done, but I can't say for certain. > >The system I first saw the problem on is running Buster and so I can't >run your binaries there. Could you point me at a source tree so I can >try a rebuild on Buster please? > Great - try the repo here: https://salsa.debian.org/gusnan/geeqie/ (You'll know what to do with it). Many thanks for testing it! /Andreas Rönnquist gus...@debian.org andr...@ronnquist.net
Bug#921740: Pointless scans of the root filesystem at startup
Hi! I have packaged a new git snapshot, downloadable from here: https://www.gusnan.se/debian/geeqie-common_1.5.1+git20201112-fae4de3c-1_all.deb https://www.gusnan.se/debian/geeqie_1.5.1+git20201112-fae4de3c-1_amd64.deb Which have fixes which I believe affects this - see the upstream commit at https://github.com/BestImageViewer/geeqie/commit/0ff5c85b082fa2b1dc578807fac8dbfd9b93421c Please try out the packages of the git snapshot linked above, and report back if it fixes the problem or not. (I haven't packaged the git snapshot in Debian yet, because it looks like a new upstream release is imminent). thanks in advance /Andreas Rönnquist gus...@debian.org andr...@ronnquist.net
Bug#965339: geeqie: Geeqie is painfully slow since GTK3
Hey guys - I have packaged a new git snapshot, downloadable from here: https://www.gusnan.se/debian/geeqie-common_1.5.1+git20201112-fae4de3c-1_all.deb https://www.gusnan.se/debian/geeqie_1.5.1+git20201112-fae4de3c-1_amd64.deb (You'll need to install both debs). Could you please try it out, and see if it affects your problems? There have been some progress which I think should be affecting the problems you have reported. (I don't package this in Debian yet, since it looks like a new upstream version isn't far away - I will of course upload that to Debian when it comes). Thanks in advance. /Andreas Rönnquist gus...@debian.org andr...@ronnquist.net
Bug#965339: Is upstream notified?
On Sun, 15 Nov 2020 09:44:19 +0200 Henri Salo wrote: >What is the upstream issue ID? > >-- >Henri Salo For example #761, #768, #814 Some of which have been fixed upstream, but not in the Debian package. There is talk about a new upstream release, so I am holding packaging a new git snapshot a while, waiting for upstream. https://github.com/BestImageViewer/geeqie/issues/761 https://github.com/BestImageViewer/geeqie/issues/768 https://github.com/BestImageViewer/geeqie/issues/814
Bug#965339: Geeqie is painfully slow since GTK3
On Sun, 1 Nov 2020 12:50:52 +0100 Adrien CLERC wrote: >Hi, > >Since report, I've upgrade my system from: > >- CPU : Core2 Quad Q9550 > >- GPU : Radeon HD6450 > >to a more modern : > >- CPU/GPU : AMD Ryzen PRO 4750G > >This is not a high end system, but it should be powerful enough. I >experienced exactly the same issue. When switching image, the UI is >unresponsive for ~1 second. Now, I can use clutter, but it does not >change. > >On geeqie-1.5.1-10 switching images are really fast, about 100ms. Now, >it's still subsecond, but more around 900ms. > >I'll be glad to help on this, > >Adrien > Do you have the option "Show marks" enabled? (It's in the "Select" menu, default keyboard shortcut 'M'). If I enable this, geeqie indeed gets very slow. Please try pressing 'M', and disable marks, and report back if this affects the performance. /Andreas Rönnquist gus...@debian.org
Bug#793800: filezilla: Links open two tabs containing same link
On Mon, 27 Jul 2015 18:20:15 +0200 Andreas =?UTF-8?B?UsO2bm5xdWlzdA==?= wrote: > Package: filezilla > Version: 3.9.0.5-1 > Severity: minor > > Dear Maintainer, > > Clicking on links in the program (This includes both the webpage link > in the about dialog, and also the links in the welcome dialog) opens > the links twice in the webbrowser. I am using Iceweasel and open > external links in a new tab, but the filezilla links opens two new > tabs both containing the same address. > > The problem is present on both Jessie and Sid. I cannot reproduce this any longer, neither on unstable nor stable. Feel free to close it. /Andreas gus...@debian.org andr...@ronnquist.net
Bug#971403: geeqie: fails to start with X error
On Wed, 30 Sep 2020 00:33:23 +0200 Lionel Elie Mamane wrote: >Package: geeqie >Version: 1:1.5.1+git20200808-2a27c9ab-1 >Severity: grave >Justification: renders package unusable > >Seems to be since upgrade from 1:1.5.1-9 to >1:1.5.1+git20200808-2a27c9ab-1 > >$ geeqie > >(geeqie:26619): Gdk-ERROR **: 00:31:08.776: The program 'geeqie' >received an X Window System error. This probably reflects a bug in the >program. The error was 'GLXBadContext'. > (Details: serial 185 error_code 161 request_code 152 (GLX) > minor_code 6) (Note to programmers: normally, X errors are reported > asynchronously; that is, you will receive the error a while after > causing it. To debug your program, run it with the GDK_SYNCHRONIZE > environment variable to change this behavior. You can then get a > meaningful backtrace from your debugger if you break on the > gdk_x_error() function.) >Trace/breakpoint trap > Could you please try to start it with geeqie --disable-clutter - and report back if it works with this. If it does, go to Edit -> Preferences - Image - And there change the checkbox "Use GPU acceleration via Clutter library (Requires restart)" Please report back if this fixes the problem. /Andreas Rönnquist gus...@debian.org
Bug#970638: jag: cannot upgrade from 3.6-1 to 3.8-1
Package: jag Version: 0.3.6-1 Severity: serious Justification: Policy 7.6.1 Dear Maintainer, Trying to upgrade jag from 3.6-1 to 3.8-1 fails, because the upgrade tries to overwrite files of jag-data. See the following apt upgrade output: Do you want to continue? [Y/n] Reading changelogs... Done (Reading database ... 248298 files and directories currently installed.) Preparing to unpack .../archives/jag_0.3.8-1_amd64.deb ... Unpacking jag (0.3.8-1) over (0.3.6-1) ... dpkg: error processing archive /var/cache/apt/archives/jag_0.3.8-1_amd64.deb (--unpack): trying to overwrite '/usr/share/games/jag/data/bonus/clock.png', which is also in package jag-data 0.3.6-1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/jag_0.3.8-1_amd64.deb Have you moved clock.png without setting Breaks+Replaces properly as mentioned in policy 7.6.1? https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-in-other-packages -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.6.0-2-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=sv_SE.utf8, LC_CTYPE=sv_SE.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages jag depends on: ii jag-data 0.3.6-1 ii libc62.31-3 ii libgcc-s110.2.0-9 ii libqt5core5a 5.14.2+dfsg-6 ii libqt5gui5 5.14.2+dfsg-6 ii libqt5opengl55.14.2+dfsg-6 ii libqt5widgets5 5.14.2+dfsg-6 ii libqt5x11extras5 5.14.2-2 ii libsdl2-2.0-02.0.12+dfsg1-2 ii libsdl2-mixer-2.0-0 2.0.4+dfsg1-2+b1 ii libstdc++6 10.2.0-9 ii libx11-6 2:1.6.12-1 ii libxrandr2 2:1.5.1-1 jag recommends no packages. jag suggests no packages. -- no debconf information
Bug#846284: O: gftp -- X/GTK+ and console FTP client (metapackage)
On Wed, 26 Aug 2020 18:45:33 +0200 Andreas Ronnquist wrote: > retitle 846284 ITA: gftp -- X/GTK+ and console FTP client > (metapackage) thanks > > I'll adopt this - there's a GTK3 conversion available upstream, which > I'll package, at > > https://github.com/masneyb/gftp > > -- Andreas Rönnquist > gus...@debian.org Also, I should mention - Co-maintainers are very welcome. If you are not a DD or DM yet, no problems, I can sponsor your uploads. /Andreas Rönnquist gus...@debian.org
Bug#846284: O: gftp -- X/GTK+ and console FTP client (metapackage)
retitle 846284 ITA: gftp -- X/GTK+ and console FTP client (metapackage) thanks I'll adopt this - there's a GTK3 conversion available upstream, which I'll package, at https://github.com/masneyb/gftp -- Andreas Rönnquist gus...@debian.org
Bug#967247: allegro5: depends on deprecated GTK 2
Fixed in upstream git repository. I'll patch the Debian package if a new upstream release takes long, otherwise I'll package the new upstream with the fix included. -- Andreas Rönnquist gus...@debian.org
Bug#966509: Bug#966096: geeqie: immediate segfault
I am about to upload a git snapshot of geeqie to Debian unstable, in which I will close 966509, since it adds a --disable-clutter option, which should make it possible to run with or without clutter. In this bug (966096) I track the g_strsplit segfault. -- Andreas Rönnquist gus...@debian.org
Bug#966096: geeqie: immediate segfault
On Wed, 5 Aug 2020 19:41:14 -0400 James Van Zandt wrote: >Thanks! Though none of the discussion I saw there mentioned the >g_strsplit: assertion failed message. I'll hope for the best. > Ah, of course, if the fixes doesn't fix that specific problem, I'll split it out to a bug of it's own. /Andreas
Bug#966096: geeqie: immediate segfault
On Wed, 22 Jul 2020 20:02:43 -0400 James Van Zandt wrote: > Package: geeqie > Version: 1:1.5.1-11 > Severity: important > X-Debbugs-Cc: jim.vanza...@gmail.com > > /tmp/bug > I assume this is the bug: https://github.com/BestImageViewer/geeqie/issues/559 I will probably package a git snapshot (again) if upstream don't make a new release soon, and then you will have the option --disable-clutter which should make it possible to run again. /Andreas
Bug#966509: geeqie: can not start due to clutter-gtk init failure
On Wed, 29 Jul 2020 20:09:55 +0300 Eugene Berdnikov wrote: > Dear Maintainers, > > > % geeqie > > (geeqie:28868): Clutter-CRITICAL **: 19:45:09.437: Unable to > initialize Clutter: Unable to initialize the Clutter backend: no > available drivers found. Can't initialize clutter-gtk. > > > Problem was found after upgrade from 1.5.1-11: > > 2020-07-29 17:13:18 upgrade geeqie:amd64 1:1.5.1-11 > 1:1.5.1+git20200723-2 2020-07-29 17:13:19 upgrade geeqie-common:all > 1:1.5.1-11 1:1.5.1+git20200723-2 > > In ~/.config/geeqie/geeqierc.xml clutter is turned OFF: > image.use_clutter_renderer = "false" > As you can see in the upstream bug report [1], this is due to geeqie tries to start GTK with clutter no matter what, and if that fails it causes a hard crash that it has a hard time recovering from. As you can see there will be an command line option in future releases to start without clutter, and by this work around the problem. /Andreas gus...@debian.org 1: https://github.com/BestImageViewer/geeqie/issues/559
Bug#966096: geeqie: immediate segfault
On Fri, 24 Jul 2020 10:21:03 -0400 James Van Zandt wrote: >Alas, no. Same symptom. > >FWIW, I'm attaching the tail end of an strace log, and a (long) list >of the shared libraries used, per ldd. I note that in the latter >list, there are no nvidia libraries - but the strace log shows it was >looking for (and apparently not finding) libGLX_nvidia.so.0. apt-find >indicates that library can be found in these packages: > > >$ apt-file search libGLX_nvidia.so.0 >libglx-nvidia-legacy-390xx0: >/usr/lib/x86_64-linux-gnu/nvidia/legacy-390xx/libGLX_nvidia.so.0 >libglx-nvidia-tesla-418-0: >/usr/lib/x86_64-linux-gnu/nvidia/tesla-418/libGLX_nvidia.so.0 >libglx-nvidia-tesla-440-0: >/usr/lib/x86_64-linux-gnu/nvidia/tesla-440/libGLX_nvidia.so.0 >libglx-nvidia-tesla-450-0: >/usr/lib/x86_64-linux-gnu/nvidia/tesla-450/libGLX_nvidia.so.0 >libglx-nvidia0: >/usr/lib/x86_64-linux-gnu/nvidia/current/libGLX_nvidia.so.0 > > >I don't suppose the tesla packages are relevant, and apt-get isn't >able to find the other two. The first is supposed to be in non-free. >My /etc/apt/sources.list already includes > >deb http://ftp.us.debian.org/debian/ unstable main contrib non-free > >Should I have something else configured to access that package? > What if you edit your config (in ~/.config/geeqie/geeqierc.xml), and change the line image.use_clutter_renderer = "true" (which I assume it is set to), to image.use_clutter_renderer = "false" ? /Andreas
Bug#966096: geeqie: immediate segfault
On Thu, 23 Jul 2020 08:08:26 -0400 James Van Zandt wrote: >Thanks, I'll do that when I get a chance. > >In the meantime (since I assume the package is working for you), could >you compare our shared library versions? If we're out of sync, maybe >there's an unrecognized incompatibility. I have uploaded a new git snapshot to unstable (1:1.5.1+git20200723-2), please test that one too if it changes anything. /Andreas
Bug#966096: geeqie: immediate segfault
On Wed, 22 Jul 2020 20:02:43 -0400 James Van Zandt wrote: > Package: geeqie > Version: 1:1.5.1-11 > Severity: important > X-Debbugs-Cc: jim.vanza...@gmail.com > > /tmp/bug > I cannot do anything with the information you give. Could you please try installing the debug package - Add something like deb http://deb.debian.org/debian-debug/ unstable-debug main to your /etc/apt/sources.list and install the package geeqie-dbgsym, and then start geeqie throug gdb? I can give you more exact instructions if needed. /Andreas Rönnquist gus...@debian.org
Bug#964441: #964441 geeqie: No image is rendered, only white rectangle visible under GNOME Wayland
On Sun, 19 Jul 2020 13:24:49 +0200 Andreas Ronnquist wrote: >On Sun, 19 Jul 2020 13:56:51 +0300 >he...@nerv.fi wrote: > >>Hello, >> >>Responding to: >> >>> Thanks guys - have I understood correctly that upstream current Git >>> fixes it properly? I have tested some with latest upstream git, and >>> to me it seems it does, but I would like confirmation that it fixes >>> it for you too - I am a bit hesitant in packaging a Git snapshot, >>> but if that is what it takes to fix the bug, then so be it. Upstream >>> unfortunately makes new releases very rarely. >> >>Could you make a .deb of this and I can test? >> >>-- >>Henri Salo > >Sure thing - I will try to get one done before tomorrow. It took longer than expected, sorry about that, but here's some debs: https://www.gusnan.se/debian/geeqie-common_1.5.1+git20200708-1_all.deb https://www.gusnan.se/debian/geeqie_1.5.1+git20200708-1_amd64.deb Please install the geeqie-common before the geeqie one, and please report back with your results. If you run in to problems with the download, let me know. Thanks in advance /Andreas Rönnquist gun...@debian.org
Bug#964441: #964441 geeqie: No image is rendered, only white rectangle visible under GNOME Wayland
On Sun, 19 Jul 2020 13:56:51 +0300 he...@nerv.fi wrote: >Hello, > >Responding to: > >> Thanks guys - have I understood correctly that upstream current Git >> fixes it properly? I have tested some with latest upstream git, and >> to me it seems it does, but I would like confirmation that it fixes >> it for you too - I am a bit hesitant in packaging a Git snapshot, >> but if that is what it takes to fix the bug, then so be it. Upstream >> unfortunately makes new releases very rarely. > >Could you make a .deb of this and I can test? > >-- >Henri Salo Sure thing - I will try to get one done before tomorrow.
Bug#965119: lintian: send-patch isn't silenced by "Applied-Upstream"
Package: lintian Version: 2.84.0 Severity: normal Dear Maintainer, I get I: lollypop source: send-patch debian/patches/add_desktop_keywords_entry.patch and try to fix it by adding Applied-Upstream: https://gitlab.gnome.org/World/lollypop/-/commit/4c1435ee0c4a7f2ccaa05bce60a3e64cb912 to the patch, but lintian still complains. Patch attached, for completeness. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.6.0-2-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=sv_SE.utf8, LC_CTYPE=sv_SE.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lintian depends on: ii binutils 2.34.90.20200706-1 ii bzip2 1.0.8-3 ii diffstat 1.63-1 ii dpkg 1.20.5 ii dpkg-dev 1.20.5 ii file 1:5.38-5 ii gettext 0.19.8.1-10 ii gpg 2.2.20-1 ii intltool-debian 0.35.0+20060710.5 ii libapt-pkg-perl 0.1.36+b3 ii libarchive-zip-perl 1.68-1 ii libcapture-tiny-perl 0.48-1 ii libclass-xsaccessor-perl 1.19-3+b5 ii libclone-perl 0.45-1 ii libconfig-tiny-perl 2.24-1 ii libcpanel-json-xs-perl4.19-1 ii libdata-validate-domain-perl 0.10-1 ii libdevel-size-perl0.83-1+b1 ii libdpkg-perl 1.20.5 ii libemail-address-xs-perl 1.04-1+b2 ii libfile-basedir-perl 0.08-1 ii libfile-find-rule-perl0.34-1 ii libfont-ttf-perl 1.06-1 ii libhtml-parser-perl 3.72-5 ii libio-async-loop-epoll-perl 0.21-1 ii libio-async-perl 0.77-3 ii libjson-maybexs-perl 1.004002-1 ii liblist-compare-perl 0.53-1 ii liblist-moreutils-perl0.416-1+b5 ii liblist-utilsby-perl 0.11-1 ii libmoo-perl 2.004000-1 ii libmoox-aliases-perl 0.001006-1 ii libnamespace-clean-perl 0.27-1 ii libpath-tiny-perl 0.114-1 ii libsereal-decoder-perl4.017+ds-1 ii libsereal-encoder-perl4.017+ds-1 ii libtext-levenshteinxs-perl0.03-4+b7 ii libtext-xslate-perl 3.5.8-1 ii libtime-duration-perl 1.21-1 ii libtime-moment-perl 0.44-1+b2 ii libtimedate-perl 2.3300-1 ii libtry-tiny-perl 0.30-1 ii libtype-tiny-perl 1.010002-1 ii libunicode-utf8-perl 0.62-1+b1 ii liburi-perl 1.76-2 ii libxml-libxml-perl2.0134+dfsg-2 ii libxml-writer-perl0.625-1 ii libyaml-libyaml-perl 0.82+repack-1 ii man-db2.9.3-2 ii patchutils0.3.4-3 ii perl [libdigest-sha-perl] 5.30.3-4 ii t1utils 1.41-4 ii xz-utils 5.2.4-1+b1 Versions of packages lintian recommends: ii libperlio-gzip-perl 0.19-1+b6 Versions of packages lintian suggests: pn binutils-multiarch pn libtext-template-perl -- no debconf information -- Andreas Rönnquist gus...@debian.org Author: Andreas Rönnquist Applied-Upstream: https://gitlab.gnome.org/World/lollypop/-/commit/4c1435ee0c4a7f2ccaa05bce60a3e64cb912 Description: Add Keywords to desktop file Silence Lintian warning desktop-entry-lacks-keywords-entry --- a/data/org.gnome.Lollypop.desktop.in +++ b/data/org.gnome.Lollypop.desktop.in @@ -8,6 +8,8 @@ Terminal=false Type=Application Categories=GNOME;GTK;AudioVideo;Player;Audio; +# Translators: Search term to easier find the app. Do NOT translate or localize the semicolons - also, must end with semicolon. +Keywords=Music;Player; StartupNotify=true X-PulseAudio-Properties=media.role=music MimeType=application/ogg;application/x-ogg;application/x-ogm-audio;audio/aac;audio/mp4;audio/mpeg;audio/mpegurl;audio/ogg;audio/vnd.rn-realaudio;audio/vorbis;audio/x-flac;audio/x-mp3;audio/x-mpeg;audio/x-mpegurl;audio/x-ms-wma;audio/x-musepack;audio/x-oggflac;audio/x-pn-realaudio;audio/x-scpls;audio/x-speex;audio/x-vorbis;audio/x-vorbis+ogg;audio/x-wav;x-content/audio-player;audio/x-aac;audio/m4a;audio/x-m4a;audio/mp3;audio/ac3;audio/flac;application/xspf+xml;audio/x-opus+ogg;
Bug#964441: geeqie: No image is rendered, only white rectangle visible
On Wed, 08 Jul 2020 09:22:47 +0800 Paul Wise wrote: > Control: forwarded -1 > https://github.com/BestImageViewer/geeqie/issues/539 Control: retitle > -1 geeqie: No image is rendered, only white rectangle visible under > GNOME Wayland Control: tags -1 + patch Control: usertags -1 + wayland > > On Tue, 07 Jul 2020 12:19:13 +0200 Florian wrote: > > > No image is shown, instead only a white rectangle is visible. > > I'm getting this too. > > > I am on gnome/wayland. > > I've tested GNOME Xorg and it does not have this issue, retitling. > > > Might be this one: > https://github.com/BestImageViewer/geeqie/issues/539 > > Marking as forwarded. > > It seems there is a patch that makes it work for GPU acceleration mode > but unfortunately not for software rendering mode. > Thanks guys - have I understood correctly that upstream current Git fixes it properly? I have tested some with latest upstream git, and to me it seems it does, but I would like confirmation that it fixes it for you too - I am a bit hesitant in packaging a Git snapshot, but if that is what it takes to fix the bug, then so be it. Upstream unfortunately makes new releases very rarely. /Andreas Rönnquist gus...@debian.org
Bug#960600: buster-pu: package asunder/2.9.3-3+deb10u1
On Tue, 07 Jul 2020 18:49:38 +0100, Adam D. Barratt wrote: >Control: tags -1 + confirmed > >On Thu, 2020-05-14 at 14:25 +0200, Andreas Ronnquist wrote: >> The cddb service freedb,org has been closed down, and I would like to >> update asunder so that it uses gnudb.org by default instead. I >> mention it in a NEWS item too, so that others get a warning and >> chance to change their setting too. > >diff -Nru asunder-2.9.3/debian/NEWS.Debian >asunder-2.9.3/debian/NEWS.Debian --- asunder-2.9.3/debian/NEWS.Debian > 2019-01-23 21:58:01.0 +0100 +++ > asunder-2.9.3/debian/NEWS.Debian2020-05-14 14:12:58.0 > +0200 >@@ -1,3 +1,12 @@ >+asunder (2.9.3-3+deb10u1) unstable; urgency=medium > >That should be buster, in line with the changelog. > >With that fixed, please go ahead. > Done! Package has just been accepted into proposed-updates. Thank you! best -- Andreas Rönnquist mailingli...@gusnan.se andr...@ronnquist.net
Bug#904976: marked as done (Build with GTK3)
On Sun, 21 Jun 2020 10:26:54 +0100 Klaus Ethgen wrote: >Hi, > >Am Sa den 20. Jun 2020 um 23:36 schrieb Debian Bug Tracking System: >> From: Vincent Bernat >[...] >> GTK3 support in Geeqie package is disabled because of #762718. >> However, we are almost 4 years later. It's likely the situation has >> been improved and Geeqie should be able to be compiled with GTK3. >> >> I did a quick test by removing the --disable-gtk3 flag in >> debian/rules and adding libgtk-3-dev as a dependency instead of >> libgtk2.0-dev. I don't see any issue. >> >> Please, compile with GTK3. Otherwise, on HiDPI displays, icons are >> tiny. > >Note that GTK3 has generally problems with mouse support and evdev X >driver. There are also some troubles with flickering Displays in some >configurations. > >It doesn't look like the GTK3 people would care about the troubles, >users have. I don't see that this would change in future. But the fact >that GTK2 is not really improved anymore and many people insist in >features, that are only available in GTK3 build (like map support or >HD displays), it might be the best to build it with GTK3. > >However, at least for the first bug above, that is the most sever one, >there is a workaround and I think, that should be mentioned in the >Debian README (or even use it in a wrapper starting Geeqie). A `export >GDK_CORE_DEVICE_EVENTS=1` does factually disable the special handling, >GTK3 is doing with input devices and give back a working mouse support. > Thanks Klaus! I have updated the Debian readme, see https://salsa.debian.org/debian/geeqie/-/blob/6d2981da5cc18ff008c1fab161d1b5ab188ac2c3/debian/README.Debian - removing the mentioning of gqview (the information seems a bit outdated), and adding info about GDK_CORE_DEVICE_EVENTS instead. It will be published in the Debian repos when I do a new release. And again, thank you for all your work on Geeqie. best /Andreas Rönnquist gus...@debian.org
Bug#960600: buster-pu: package asunder/2.9.3-3+deb10u1
On Thu, 14 May 2020 14:25:03 +0200, Andreas Ronnquist wrote: The corresponding change has come in an upstream release too now, and I have uploaded that (and removed my Debian patch) in unstable. See the upstream changelog at the bottom of https://littlesvr.ca/bugs/show_bug.cgi?id=2 -- Andreas Rönnquist mailingli...@gusnan.se gus...@debian.org
Bug#933734: CRTL+ARROWS switch but does not really now
On Sun, 17 May 2020 23:15:01 +0200 Vincent Lefevre wrote: >On 2020-05-12 13:55:25 +0200, Andreas Ronnquist wrote: >> The default setting is Ctrl+Right/Ctrl+Left to switch tabs, > >I've just installed sakura to try it, and this is what I've noticed. >Ctrl+Right/Ctrl+Left works, but not Alt+Right/Alt+Left. > >The sakura(1) man page says about the default: > > Alt + Left cursor -> Previous tab > Alt + Right cursor -> Next tab > >So, either the default is buggy, or the man page is incorrect. > Thanks - I have submitted a Merge proposal upstream simply changing the man page, and will apply that patch to the Debian packaging and release a new Debian version as soon as it is accepted upstream. best /Andreas Rönnquist gus...@debian.org
Bug#960600: buster-pu: package asunder/2.9.3-3+deb10u1
Package: release.debian.org Severity: normal Tags: buster User: release.debian@packages.debian.org Usertags: pu The cddb service freedb,org has been closed down, and I would like to update asunder so that it uses gnudb.org by default instead. I mention it in a NEWS item too, so that others get a warning and chance to change their setting too. The single-line change is applied in unstable in 2.9.5-2, commit at [1]. The change isn't released in any upstream version, but it is applied to their VCS (svn, so I cannot link a commit) and will come in their next release. For the bug on unstable, see #950815 [2]. It is discussed upstream in [3], where migration to MusicBrainz was considered. Debdiff attached. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.5.0-2-amd64 (SMP w/1 CPU core) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE, TAINT_SOFTLOCKUP Locale: LANG=sv_SE.utf8, LC_CTYPE=sv_SE.utf8 (charmap=UTF-8), LANGUAGE=sv_SE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash 1: https://salsa.debian.org/debian/asunder/-/commit/ea6f907538b0b1c88d3479683fb12bfa006263d1 2: https://bugs.debian.org/950815 3: https://littlesvr.ca/bugs/show_bug.cgi?id=6 -- Andreas Rönnquist mailingli...@gusnan.se andr...@ronnquist.net asunder.debdiff Description: Binary data
Bug#933734: CRTL+ARROWS switch but does not really now
On Tue, 12 May 2020 01:30:00 -0400 PICCORO McKAY Lenz wrote: >tryit new version, this time let me redefine keys and works, but by >default does not work! gtk2 works perfectly (debian wheeze with older >version custon build) > The default setting is Ctrl+Right/Ctrl+Left to switch tabs, which works just fine for me - I just tried by removing $(HOME)/.config/sakura/sakura.conf and by starting sakura again generating a new config, and the default values works just fine for me. What doesn't work for you? /Andreas
Bug#933734: CRTL+ARROWS switch but does not really now
On Tue, 6 Aug 2019 08:30:10 -0400 PICCORO McKAY Lenz wrote: > i created manually the file.. now the config as you pointed was put.. > > BUT graphically seems change to the next terminal.. but the internal > screeen still show the current terminal > > it's clear that the sakura release are totally broken but why? > libvte? gtk3 ? > I cannot reproduce your problem, it works just find over here. I have uploaded a new version of sakura (3.7.1-1), could you please try this version and check if you can reproduce the problem in this version? /Andreas gus...@debian.org
Bug#887100: geeqie: Orientation controls do nothing
fixed 887100 1:1.5.1-2 thanks No reply for more than half a year, I assume that the upload fixed the problem. best -- Andreas Rönnquist gus...@debian.org
Bug#919315: geeqie: Orientation keys ('[' and ']') don't work in latest geeqie release
fixed 919315 1:1.5.1-2 thanks No reply for more than half a year, I assume that the upload fixed the problem. best -- Andreas Rönnquist gus...@debian.org
Bug#952689: libcddb2: freedb service is closing down
Package: libcddb2 Version: 1.3.2-6+b1 Severity: important Dear Maintainer, According to a notice on https://freedb.org, that service is closing down. I assume that libcddb is using that server, and only that - please inform me if I am mistaken. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.4.0-4-amd64 (SMP w/1 CPU core) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=sv_SE.utf8, LC_CTYPE=sv_SE.utf8 (charmap=UTF-8), LANGUAGE=sv_SE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libcddb2 depends on: ii libc6 2.29-10 libcddb2 recommends no packages. libcddb2 suggests no packages. -- no debconf information -- Andreas Rönnquist gus...@debian.org
Bug#950815: asunder: freedb will be shut down March 31th 2020
forwarded 950815 https://littlesvr.ca/bugs/show_bug.cgi?id=6 thanks On Thu, 6 Feb 2020 22:03:24 +0100 Andreas Ronnquist wrote: > Package: asunder > Version: 2.9.5-1 > Severity: normal > > Dear Maintainer, > > Asunder uses freedb by default to look up CD information using the > internet. This service will be shut down the 31th of March 2020, which > will affect everybody using the default setting in the asunder > package. > > (See the "urgent notice" on top of http://www.freedb.org). > > One solution could be to use the MusicBrainz to FreeDB gateway as > described at > > https://mb.videolan.org/doc/FreeDB_Gateway > I have provided musicbrainz support to the upstream bug system, if you are curious about it, there's a tar.gz there to try out. /Andreas gus...@debian.org
Bug#950815: asunder: freedb will be shut down March 31th 2020
Package: asunder Version: 2.9.5-1 Severity: normal Dear Maintainer, Asunder uses freedb by default to look up CD information using the internet. This service will be shut down the 31th of March 2020, which will affect everybody using the default setting in the asunder package. (See the "urgent notice" on top of http://www.freedb.org). One solution could be to use the MusicBrainz to FreeDB gateway as described at https://mb.videolan.org/doc/FreeDB_Gateway -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/1 CPU core) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=sv_SE.utf8, LC_CTYPE=sv_SE.utf8 (charmap=UTF-8), LANGUAGE=sv_SE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages asunder depends on: ii cdparanoia 3.10.2+debian-13+b1 ii dpkg1.19.7 ii libatk1.0-0 2.34.1-1 ii libc6 2.29-10 ii libcddb21.3.2-6+b1 ii libgdk-pixbuf2.0-0 2.40.0+dfsg-2 ii libglib2.0-02.62.4-2 ii libgtk2.0-0 2.24.32-4 ii vorbis-tools1.4.0-11 Versions of packages asunder recommends: pn flac pn wavpack Versions of packages asunder suggests: pn lame -- debconf-show failed
Bug#949166: lintian: Faulty source-is-missing lexilla.so in SciTE
On Fri, 17 Jan 2020 12:10:07 -0800 Felix Lechner wrote: >Hi Andreas, > >On Fri, Jan 17, 2020 at 9:27 AM Andreas Ronnquist >wrote: >> >> The problematic source package available at >> https://www.scintilla.org/scite430.tgz if you would like to look at >> it. > >I cannot find a ./debian folder in this tarball. It looks more like an >upstream (orig) tarball rather than a source package (.dsc). Where can >I find your packaging, please? Thanks - sorry, yeah I mean upstream tarball. My packaging you can find on salsa: (just pushed) https://salsa.debian.org/debian/scite/ > >> Trying to override I get another lintian error: >> >> E: scite: malformed-override Override of source-is-missing for >> package type source (expecting binary) at line 6 > >Is the override included in your source package? If not, please attach >it. See the salsa link above. If I use an override like this: > scite source: source-is-missing scintilla/bin/lexilla.so I get two Lintian errors: E: scite source: source-is-missing scintilla/bin/lexilla.so E: scite: malformed-override Override of source-is-missing for package type source (expecting binary) at line 6 - but if I instead use it without the "source" field like this: > scite: source-is-missing scintilla/bin/lexilla.so I also get two lintian items (different ones, of course): E: scite source: source-is-missing scintilla/bin/lexilla.so I: scite: unused-override source-is-missing scintilla/bin/lexilla.so Is it as simple as the only way to solve this is repackaging upstream removing the unused .so? As I said earlier, the source for lexilla.so _is_ there in the upstream source. best, and thanks for all the help /Andreas
Bug#949166: lintian: Faulty source-is-missing lexilla.so in SciTE
Package: lintian Version: 2.45.0 Severity: normal Dear Maintainer, I am not sure if this is the correct way trying to solve this - but anyway: Packaging the new upstream version of SciTE, upstream has split the source so that the lexilla library can be built as a shared object separately (and that shared object is available and distributed in the source package in scintilla/bin/lexilla.so, and source available in scintilla/lexilla/src - simply buildable using a simple make in the src folder). To me it looks like upstream has included the so by mistake and I will contact them to make them remove it in later releases. The problematic source package available at https://www.scintilla.org/scite430.tgz if you would like to look at it. Building the source (which doesn't use the shared object, but build the scintilla component with the same files as the so and link statically) - lintian gives an error for E: scite source: source-is-missing scintilla/bin/lexilla.so even though it isn't used in the build, and I have a hard time overriding this. The source for this IS available in the source in scintilla/lexilla/src - and is simply buildable using make. Trying to override I get another lintian error: E: scite: malformed-override Override of source-is-missing for package type source (expecting binary) at line 6 I am posting this bug, since I am not sure what is the proper way to handle this - If you think the proper way is to simply repackage the source, feel free to close this bug and I'll do so, but at the same time I feel this is a false positive, since the source for the shared object _is_ there. Thoughts and ideas would be appreciated. best regards, and thank for all your work on Lintian. /Andreas -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/1 CPU core) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=sv_SE.utf8, LC_CTYPE=sv_SE.utf8 (charmap=UTF-8), LANGUAGE=sv_SE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lintian depends on: ii binutils 2.33.50.20200115-2 ii bzip21.0.8-2 ii diffstat 1.63-1 ii dpkg 1.19.7 ii dpkg-dev 1.19.7 ii file 1:5.38-4 ii gettext 0.19.8.1-10 ii gpg 2.2.19-1 ii intltool-debian 0.35.0+20060710.5 ii libapt-pkg-perl 0.1.36+b2 ii libarchive-zip-perl 1.67-1 ii libberkeleydb-perl 0.62-1+b1 ii libcapture-tiny-perl 0.48-1 ii libcgi-pm-perl 4.44-1 ii libclass-accessor-perl 0.51-1 ii libclass-xsaccessor-perl 1.19-3+b3 ii libclone-perl0.43-2 ii libdpkg-perl 1.19.7 ii libemail-valid-perl 1.202-1 ii libfile-basedir-perl 0.08-1 ii libfile-find-rule-perl 0.34-1 ii libfont-ttf-perl 1.06-1 ii libio-async-loop-epoll-perl 0.20-1 ii libio-async-perl 0.75-1 ii libipc-run-perl 20180523.0-2 ii liblist-compare-perl 0.53-1 ii liblist-moreutils-perl 0.416-1+b5 ii libmldbm-perl2.05-2 ii libmoo-perl 2.003006-1 ii libmoox-aliases-perl 0.001006-1 ii libnamespace-clean-perl 0.27-1 ii libpath-tiny-perl0.108-1 ii libtext-levenshtein-perl 0.13-1 ii libtimedate-perl 2.3100-1 ii libtry-tiny-perl 0.30-1 ii libtype-tiny-perl1.008001-2 ii liburi-perl 1.76-1 ii libxml-libxml-perl 2.0134+dfsg-1+b1 ii libyaml-libyaml-perl 0.80+repack-2+b1 ii man-db 2.9.0-2 ii patchutils 0.3.4-2+b1 ii perl [libdigest-sha-perl]5.30.0-9 ii t1utils 1.41-3 ii xz-utils 5.2.4-1+b1 Versions of packages lintian recommends: ii libperlio-gzip-perl 0.19-1+b6 Versions of packages lintian suggests: pn binutils-multiarch ii libhtml-parser-perl3.72-3+b4 pn libtext-template-perl -- no debconf information -- Andreas Rönnquist gus...@debian.org
Bug#947719: [Python-apps-team] Bug#947719: Is gstreamer1.0-libav really a hard dependency of lollypop?
On Sun, 29 Dec 2019 13:28:42 +, Amr Ibrahim wrote: >Package: lollypop >Version: 1.2.19-1 > >I see that gstreamer1.0-libav is set as a hard dependency of lollypop >in Debian. However, upstream does not list gstreamer1.0-libav as a >dependency [1]. If lollypop runs without gstreamer1.0-libav, then it >should not be a run-time dependency. If the idea is to support more >music formats in lollypop, then gstreamer1.0-libav should be a >suggested package (or a recommended package if it provides very >popular music formats). > >[1] https://gitlab.gnome.org/World/lollypop#depends-on Thanks for your report - I'll update the package with a suggests on gstreamer1.0-libav instead of a dependency. -- Andreas Rönnquist mailingli...@gusnan.se gus...@debian.org
Bug#919315: geeqie: Orientation keys ('[' and ']') don't work in latest geeqie release
I have uploaded geeqie 1:1.5.1-2 to unstable where I have cherry-picked a patch that was applied upstream recently - Could you please try that version out and reply back confirming that it fixes the problem (or not)? The patch: http://geeqie.org/cgi-bin/gitweb.cgi?p=geeqie.git;a=commit;h=fdb45ac5f99283775d655fa36b23b4be7905951e thanks for your patience -- Andreas Rönnquist gus...@debian.org
Bug#887100: geeqie: Orientation controls do nothing
I have uploaded geeqie 1:1.5.1-2 to unstable where I have cherry-picked a patch that was applied upstream recently - Could you please try that version out and reply back confirming that it fixes the problem (or not)? The patch: http://geeqie.org/cgi-bin/gitweb.cgi?p=geeqie.git;a=commit;h=fdb45ac5f99283775d655fa36b23b4be7905951e thanks for your patience -- Andreas Rönnquist gus...@debian.org
Bug#944293: www.debian.org: New homepage hovering causes horisontal scrollbar to appear
Package: www.debian.org Severity: minor Dear Maintainer, Thanks for all your work on the new homepage! I have noticed on https://debian-newhomepage.larjona.net/ that hovering either the "Project News" or "The operating system" fields, seems to changes the size of the elements, and causes the horisontal scrollbar to appear (and disappear when leaving the element), which is a bit ugly. I can reproduce this on both Chromium (76.0.3809.100) and Firefox-esr (68.2.0esr) (both on Debian stable). However, it seems to vary a bit depending on zoom level (on both browsers). The field "The Community" seems to be unaffceted by the problem. I am running on 2560x1440 screens, with the windows about 1500x1400 pixels in size. best -- Andreas Rönnquist gus...@debian.org
Bug#943676: ITP: opensurge -- Fun 2d retro platformer
Package: wnpp Severity: wishlist * Package name: opensurge Version : 0.5.0-1 Upstream Author : Alexandre Martins * URL : https://opensurge2d.org/ * License : GPL3+ Programming Lang: C Description : Fun 2d retro platformer Open Surge is a fun 2D retro platformer inspired by old-school Sonic games. It is also a game creation system that lets you unleash your creativity! Play, create games & share! I intend to maintain Open Surge in the Debian games team. -- Andreas Rönnquist gus...@debian.org
Bug#942313: RFS: codelite [QA] -- Powerful and lightweight IDE
On Mon, 14 Oct 2019 14:10:12 +0100, da...@codelite.co.uk wrote: >Package: sponsorship-requests >Severity: normal > >Dear mentors, > >I am looking for a sponsor for an update of the orphaned package >"codelite" > > * Package name: codelite >Version : 13.0+dfsg-1 >Upstream Author : eranif > * URL : https://codelite.org > * License : GPL2+ >Section : devel > > >It builds these binary packages: > > codelite -- Powerful and lightweight IDE > codelite-plugins -- Powerful and lightweight IDE - plugins > >To access further information about this package, please visit the >following URL: > > https://mentors.debian.net/package/codelite > > >Alternatively, one can download the package with dget using this >command: > >dget -x >https://mentors.debian.net/debian/pool/main/c/codelite/codelite_13.0+dfsg-1.dsc > >There is also a git repo: > https://github.com/dghart/debian-salsa-codelite-clone >which is a clone of > https://salsa.debian.org/debian/codelite >to which afaict I can't upload. > >Codelite depends on the wxWidgets toolkit. wxWidgets wraps GTK+, and >is soon to switch to using GTK+3; see #934096 . One of codelite's >dependencies, wxsqlite3, now has a Build-Conflicts for the GTK+2 >wxWidgets and also Breaks codelite; see #940540 . Because of this, >codelite will imminently be removed from testing. > >The current upload depends on the GTK+3 wxWidgets and so fixes these >bugs. It also updates to the latest upstream version, codelite 13.0. > >This is a request for a review and upload of the update. The amended >package builds and works, and has no significant lintian issues. > >Changes since the last upload: > >codelite (13.0+dfsg-1) unstable; urgency=medium > > * QA upload. > > * New upstream release: >- Add new and missing plugins to codelite-plugins. >- Refresh patches. >- Patch out two nonfree-licenced svgs. > > * debian/control: >- Build against the GTK+3 version of wxWidgets (Closes: #934096, > #940540). >- Bump standards to 4.4.1 and remove debian/compat. > > >Regards, > >David Hart > Trying to build your .dsc using cowbuilder, I get the following: -- LIBSSH_LIB is set to /usr/lib/x86_64-linux-gnu/libssh.so -- Some or all of the gtk libraries were not found. (missing: GTK2_GTK_LIBRARY GTK2_GTK_INCLUDE_DIR GTK2_GDK_INCLUDE_DIR GTK2_GDKCONFIG_INCLUDE_DIR GTK2_GDK_LIBRARY) CMake Error at CMakeLists.txt:252 (message): Could not locate GTK. Looks like the CMakeLists looks for GTK2, even though you're building against GTK+3 version of wxWidgets. Full build log attached. -- Andreas Rönnquist mailingli...@gusnan.se andr...@ronnquist.net codelight_full_build_log.txt.gz Description: application/gzip
Bug#941390: lix: New upstream release available
Package: lix Version: 0.9.24-1+b2 Severity: wishlist Dear Maintainer, There's a 0.9.29 release available - please package it in Debian. Thanks for your work on the Lix package! -- Andreas Rönnquist gus...@debian.org -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/1 CPU core) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=sv_SE.utf8, LC_CTYPE=sv_SE.utf8 (charmap=UTF-8), LANGUAGE=sv_SE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lix depends on: ii liballegro-acodec5.2 2:5.2.5.0-3 ii liballegro-audio5.2 2:5.2.5.0-3 ii liballegro-image5.2 2:5.2.5.0-3 ii liballegro-ttf5.22:5.2.5.0-3 ii liballegro5.22:5.2.5.0-3 ii libc62.29-2 ii libgcc1 1:9.2.1-8 ii libphobos2-ldc-shared87 1:1.17.0-2 ii lix-data 0.9.24-1+b2 lix recommends no packages. lix suggests no packages. -- no debconf information
Bug#939783: Re; Add patch to remove dependencies in meson.build
Hi! Upstream has re-added the meson depends - see the discussion in my upstream merge request: https://gitlab.gnome.org/World/lollypop/merge_requests/1358 and the actual commit: https://gitlab.gnome.org/World/lollypop/commit/5aa8056f4d26eeaa52d5d0b8635b2c42c4347a48 If you don't have any objections, I'll do the same in the Debian package. If you have any good argument for why they should remove the dependencies, please mention this in the pull request linked above. Thanks -- Andreas Rönnquist gus...@debian.org
Bug#939750: Split up report into two
severity 939750 grave severity 939783 normal notforwarded 939750 retitle 939783 meson.build dependencies unnecessary thanks Splitting up this into two reports - One for the Debian dependencies [939750], and one for the meson build stuff [939783]. I'll fix the Debian dependencies bug in an upload soon. Thanks -- Andreas Rönnquist gus...@debian.org
Bug#939750: package unusable (missing/wrong dependencies)
On Sun, 08 Sep 2019 14:26:31 +0200 Roderich Schupp > > There are a several more wrong more dependencies and > build-dependencies: > - all the lib*-dev packages are *not* required > (meson.build is wrong, there's nothing to compile here) > - instead several gir1.2-* packages are required > (the contain the *.typelib files required for using gobject > introspection with the correspnding libraries) > - libglib2.0-dev-bin is required for the build > (it provides glib-compile-resources required to compile resource > files) > - python-sqlite is totally wrong: it contains a Python binding to the > obsolete SQLite2 library (and is python2 only); lollypop uses > > import sqlite3 > > which is a Python binding for the SQLite3 library provided > by package libpython3-stdlib which is already covered > as a dependency of package python3 > > Roderich, as you can see on https://gitlab.gnome.org/World/lollypop/merge_requests/1358 there is some discussion on if the meson.build should be changed. I will of course follow what upstream does, but if you would like to post comments for your point of view, that would be the place to do it. I will of course apply your changes in Debian package dependencies to the package. best regards and thanks for your help /Andreas Rönnquist gus...@debian.org
Bug#939750: package unusable (missing/wrong dependencies)
On Sun, 08 Sep 2019 14:26:31 +0200 Roderich Schupp wrote: > There are a several more wrong more dependencies and > build-dependencies: > - all the lib*-dev packages are *not* required > (meson.build is wrong, there's nothing to compile here) > - instead several gir1.2-* packages are required > (the contain the *.typelib files required for using gobject > introspection with the correspnding libraries) > - libglib2.0-dev-bin is required for the build > (it provides glib-compile-resources required to compile resource > files) > - python-sqlite is totally wrong: it contains a Python binding to the > obsolete SQLite2 library (and is python2 only); lollypop uses > > import sqlite3 > > which is a Python binding for the SQLite3 library provided > by package libpython3-stdlib which is already covered > as a dependency of package python3 > > > Patch (for meson.build and debian/control) attached. Thanks - I have forwarded the changes to meson.build upstream [1], and I will apply the dependencies changes to the Debian package. 1: https://gitlab.gnome.org/World/lollypop/merge_requests/1358 Thanks! /Andreas Rönnquist gus...@debian.org
Bug#925769: lix: ftbfs with GCC-9
This one can be closed now, right? See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931825 (which really looks like the same bug to me - and it has been closed). best -- Andreas Rönnquist gus...@debian.org
Bug#935527: scantool: FTBFS due to undefined reference to symbol 'ceilf@@GLIBC_2.4'
Package: scantool Version: 2.0-1 Severity: important Dear Maintainer, scantool fails to build on several architectures, a simple link -lm should fix this problem. (Attached fix works on i386, and should work on the other ports too). Index: scantool-2.0/makefile === --- scantool-2.0.orig/makefile +++ scantool-2.0/makefile @@ -1,5 +1,5 @@ CC = gcc -AL_LIBS = $(shell allegro-config --libs) +AL_LIBS = $(shell allegro-config --libs) -lm CFLAGS ?= -O2 -g -Wall ifdef DEBUGMODE Thanks in advance. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/1 CPU core) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=sv_SE.utf8, LC_CTYPE=sv_SE.utf8 (charmap=UTF-8), LANGUAGE=sv_SE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages scantool depends on: ii liballegro4.4 2:4.4.3.1-1 ii libc6 2.28-10 scantool recommends no packages. scantool suggests no packages. -- Andreas Rönnquist gus...@debian.org
Bug#847937: Tagging bug pending
tags 847937 + pending thanks I have uploaded the package, so it is in the Debian NEW queue waiting for being accepted into the archive. -- Andreas Rönnquist gus...@debian.org
Bug#929949: New upstream version 0.8 available, compatible with python3
On Tue, 18 Jun 2019 20:10:48 +0200 Alexander Zangerl wrote: > On Tue, 18 Jun 2019 13:35:02 +0200, Sebastien Bacher writes: > >Any news about that update? > > yes. so far i can't make duplicity 0.8.0 work with python 2.7 which > is still the default version in debian and hence important in my > opinion. (by "does not work" i mean: the built-in test suite fails > quite a lot, and after patching that part basic functionality is > still very very broken.) > > no promises as to when i will find time and mental strength to wade > through this (upstream-induced) mess. > Is this really a target worth pursuing? To me it looks like the Debian Python team is working to drop Python 2 from Debian during the Bullseye development cycle. Thank you very much for all your work with duplicity packaging. /Andreas Rönnquist gus...@debian.org mailingli...@gusnan.se
Bug#933734: ALT+LEFT or ALT+RIGHT arrow does not work anymore
severity 933734 minor thanks What does your ~/.config/sakura/sakura.conf look like? I have switch_tab_accelerator=8 and prev_tab_key=Left next_tab_key=Right in it, with the results that I can switch between the tabs using Alt+Left and Alt+Right. What are the values of those settings in your sakura config file? /Andreas gus...@debian.org
Bug#931825: Dub executable does not run
severity 931825 grave thanks On Thu, 11 Jul 2019 00:12:56 +0300 Jussi Pakkanen wrote: > Package: dub > Version: 1.12.1-1 > > Installing dub on Debian unstable (tested on x86 and x64) and then > running "dub" errors out immediately with the following error message: > > dub: symbol lookup error: dub: undefined symbol: _Dstd5stdio_ name of mangled symbol>. > > I run into similar problems when simply running dub: dub: symbol lookup error: dub: undefined symbol: _D4core8internal4hash9bytesHashFNaNbNiPxvmmZm Also, the build system of the package lix is affected, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925769 (That one is reported as it affect gcc-9 only, but I run into it on a standard unstable machine).
Bug#929127: geeqie: build with ffmpegthumbnailer
tags 929127 + pending thanks Thanks for your report - I have committed a fix in the packaging git repository, so it will be included in the next release of geeqie in Debian after the Debian freeze. best -- Andreas Rönnquist gus...@debian.org
Bug#924147: geeqie-common: Please add Multi-Arch: foreign
tags 924147 + pending thanks Thanks for your report - I have committed a fix for this in the packaging git repository, so it will be fixed in the next upload after the Debian freeze. best -- Andreas Rönnquist gus...@debian.org
Bug#929401: debian-security-support: Updated Swedish translation
Package: debian-security-support Severity: wishlist Tags: l10n Dear Maintainer, Please find attached a Swedish translation of the debian-security-support package. -- System Information: Debian Release: 10.0 APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/1 CPU core) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=sv_SE.utf8, LC_CTYPE=sv_SE.utf8 (charmap=UTF-8), LANGUAGE=sv_SE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages debian-security-support depends on: ii adduser3.118 ii debconf [debconf-2.0] 1.5.72 ii gettext-base 0.19.8.1-9 debian-security-support recommends no packages. debian-security-support suggests no packages. -- Andreas Rönnquist gus...@debian.org # Swedish translations for debian-security-support package # Svenska översättningar för paket debian-security-support. # Copyright (C) 2019 Christoph Biedl # This file is distributed under the same license as the debian-security-support package. # Andreas Rönnquist , 2019. # msgid "" msgstr "" "Project-Id-Version: \n" "Report-Msgid-Bugs-To: debian-security-supp...@packages.debian.org\n" "POT-Creation-Date: 2016-06-07 12:13+0200\n" "PO-Revision-Date: 2019-05-22 15:31+0200\n" "Last-Translator: Andreas Rönnquist \n" "Language-Team: Swedish\n" "Language: sv\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=2; plural=(n != 1);\n" "X-Generator: Poedit 1.8.11\n" #: ../check-support-status.in:24 #, sh-format msgid "" "Unknown DEBIAN_VERSION $DEBIAN_VERSION. Valid values from $DEB_LOWEST_VER_ID " "and $DEB_NEXT_VER_ID" msgstr "" "Okänd DEBIAN_VERSION $DEBIAN_VERSION. Giltiga värden frÃ¥n $DEB_LOWEST_VER_ID " "och $DEB_NEXT_VER_ID" #: ../check-support-status.in:63 msgid "Failed to parse the command line parameters" msgstr "Misslyckades att tolka kommandoradsparametrarna" #: ../check-support-status.in:72 #, sh-format msgid "$name version $VERSION" msgstr "$name version $VERSION" #: ../check-support-status.in:101 msgid "E: Internal error" msgstr "E: Internt fel" #: ../check-support-status.in:117 msgid "E: Need a --type if --list is given" msgstr "E: Behöver --type om --list är given" #: ../check-support-status.in:130 #, sh-format msgid "E: Unknown --type '$TYPE'" msgstr "E: Okänd --type '$TYPE'" #: ../check-support-status.in:152 msgid "E: Cannot detect dpkg version, assuming wheezy or newer" msgstr "E: Kan inte detektera dpkg-version, antar wheezy eller nyare" #: ../check-support-status.in:282 msgid "Future end of support for one or more packages" msgstr "Framtida slut pÃ¥ support för ett eller flera paket" #: ../check-support-status.in:285 msgid "" "Unfortunately, it will be necessary to end security support for some " "packages before the end of the regular security maintenance life cycle." msgstr "" "Tyvärr kommer det att bli nödvändigt att avsluta säkerhetsstödet för vissa " "paket innan slutet pÃ¥ livscykeln för regelbundet säkerhetsunderhÃ¥ll." #: ../check-support-status.in:288 ../check-support-status.in:298 #: ../check-support-status.in:308 msgid "The following packages found on this system are affected by this:" msgstr "De följande paketen pÃ¥ detta system pÃ¥verkas av detta:" #: ../check-support-status.in:292 msgid "Ended security support for one or more packages" msgstr "Avslutat säkerhetsstöd för ett eller flera paket" #: ../check-support-status.in:295 msgid "" "Unfortunately, it has been necessary to end security support for some " "packages before the end of the regular security maintenance life cycle." msgstr "" "Tyvärr har det blivit nödvändigt att avsluta säkerhetsstödet för vissa paket " "innan slutet pÃ¥ livscykeln för regelbundet säkerhetsunderhÃ¥ll." #: ../check-support-status.in:302 msgid "Limited security support for one or more packages" msgstr "Begränsad säkerhetsstöd för ett eller flera paket" #: ../check-support-status.in:305 msgid "" "Unfortunately, it has been necessary to limit security support for some " "packages." msgstr "" "Tyvärr har det blivit nödvändigt att begränsa säkerhetsstödet för vissa " "paket." #: ../check-support-status.in:320 #, sh-format msgid "* Source:$SRC_NAME, will end on $ALERT_WHEN" msgstr "* Source:$SRC_NAME, kommer att avslutas $ALERT_WHEN" #: ../check-support-status.in:323 #, sh-format msgid "* Source:$SRC_NAME, ended on $ALERT_WHEN at version $ALERT_VERSION" msgstr "* Source:$SRC_NAME, avslutades $ALERT_WHEN med version $ALERT_VERSION" #: ../check-support-status.in:326 #, sh-format msgid "* Source:$SRC_NAME" msgstr "* Source:$SRC_NAME" #: ../check-support-status.in:330 #, sh-format msgid " Details: $ALERT_WHY" msgstr " Detaljer: $ALERT_WHY" #: ../check-support-status.in:333 msgid " Affected binary package:"
Bug#925410: Translations of redirect page
On Sun, 24 Mar 2019 16:01:27 +0100, gus...@debian.org wrote: >Unfortunately this seems like it isn't enough - I have translated the >string for Swedish, but still the message is presented in English. (See >the link above to see for yourself). > >Converted to a bug-report, to easier track. > >As said, I don't see this as a pressing matter, and I fully understand >if it is lower on priority-lists. > >thanks for all your work! I have made a Merge request for a fix for this in Salsa: https://salsa.debian.org/webmaster-team/webwml/merge_requests/90 I would appreciate tests of the fix before I (or you) apply it to the webwml repo. (It doesn't include any translations or updated pot/po-files, this will be needed to test). regards -- Andreas Rönnquist mailingli...@gusnan.se andr...@ronnquist.net
Bug#924120: Say "netinst multi-arch CD images"
On Sat, 9 Mar 2019 19:09:41 +0100, Holger Wansing wrote: >Hi, > >積丹尼 Dan Jacobson wrote: >> Package: www.debian.org >> >> On https://www.debian.org/devel/debian-installer/ >> After "Current daily snapshots" say >> "netinst multi-arch CD images" >> Not just >> "multi-arch CD images". >> > >The "multi-arch CD images" is - as first - the definition of a group >of images, or say a category. >Currently, there is only the netinst image in that category, but maybe >there are more multi-arch images to come in the future? > >If that happens, the label would then be no longer correct now. > > >Holger > Ah, I rushed the fix - should I change it back? -- Andreas Rönnquist mailingli...@gusnan.se andr...@ronnquist.net
Bug#923018: geeqie: Segfault on create new archive filters
On Mon, 25 Feb 2019 18:35:57 +0100 "jEsuSdA 8)" wrote: > El 23/2/19 a las 21:09, Andreas Ronnquist escribió: > > > > That doesn't tell me much - please install debug symbols for geeqie > > - see > > > > https://wiki.debian.org/AutomaticDebugPackages > > > > and add the testing-debug repo - after this install the > > geeqie-dbgsym package and please do a backtrace in gdb (the command > > bt full in gdb) after the segmentation fault. > > > > thanks > > /Andreas > > gus...@debian.org > > > > Hi again! > > This is the output: > > - 8< - Thanks! I might have found the cause - there's a check in the code for the word "Filter", which I can see is "Filtro" in your Spanish version - In my system (which I run in Swedish), the string is also "Filter" just like in English, so I don't run into the problem. Could you please try to run geeqie in English like so: LC_ALL=C geeqie and report back if you run into the problem or not. Regards /Andreas gus...@debian.org
Bug#923018: geeqie: Segfault on create new archive filters
On Sat, 23 Feb 2019 20:34:41 +0100 "jEsuSdA 8)" wrote: >El 23/2/19 a las 19:05, Andreas Ronnquist escribió: >> On Sat, 23 Feb 2019 01:36:27 +0100 jEsuSdA >> wrote: >>> Dear Maintainer, >>> >>> Geeqie crashes when trying to editing archive preferences. >>> >>> Once you try to ADD new archive filter, geeqie crashes. >>> >> - 8< - > >For help, type "help". >Type "apropos word" to search for commands related to "word"... >Reading symbols from geeqie...(no debugging symbols found)...done. >(gdb) start >Function "main" not defined. >Make breakpoint pending on future shared library load? (y or [n]) n >Starting program: /usr/bin/geeqie >[Thread debugging using libthread_db enabled] >Using host libthread_db library >"/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7160e700 >(LWP 11622)] [New Thread 0x70e0d700 (LWP 11623)] >[Detaching after fork from child process 11624] >[Detaching after fork from child process 11626] >[Detaching after fork from child process 11628] >[Detaching after fork from child process 11630] >[New Thread 0x7fffe9671700 (LWP 11632)] >[New Thread 0x7fffe8e70700 (LWP 11633)] >[Detaching after fork from child process 11634] >[Detaching after fork from child process 11636] >[Detaching after fork from child process 11638] >[Detaching after fork from child process 11640] >[Thread 0x7fffe8e70700 (LWP 11633) exited] > >Thread 1 "geeqie" received signal SIGSEGV, Segmentation fault. >0x5565a432 in ?? () > That doesn't tell me much - please install debug symbols for geeqie - see https://wiki.debian.org/AutomaticDebugPackages and add the testing-debug repo - after this install the geeqie-dbgsym package and please do a backtrace in gdb (the command bt full in gdb) after the segmentation fault. thanks /Andreas gus...@debian.org
Bug#923018: geeqie: Segfault on create new archive filters
On Sat, 23 Feb 2019 01:36:27 +0100 jEsuSdA wrote: > Dear Maintainer, > > Geeqie crashes when trying to editing archive preferences. > > Once you try to ADD new archive filter, geeqie crashes. > In addition to what I wrote above - Could you please try upgrading your packages to what is present in testing? I can see see from the version dependency information in the bug report that some of your packages are not even up to date with versioning in testing. This might very well affect package behaviour - and I cannot support some arbitrary mix of stable with testing (Which your APT policy seem to suggest). /Andreas gus...@debian.org
Bug#923018: geeqie: Segfault on create new archive filters
Control: tags moreinfo On Sat, 23 Feb 2019 01:36:27 +0100 jEsuSdA wrote: > Package: geeqie > Version: 1:1.4+git20190121-1 > Severity: important > > Dear Maintainer, > > Geeqie crashes when trying to editing archive preferences. > > Once you try to ADD new archive filter, geeqie crashes. > > Here, the configuration settings where the bug exists: > https://i.imgur.com/nXGXQBR.png > I cannot reproduce this - Does the program crash immediately as you press the "Añadir" button? A backtrace from the crash with debug symbols activated for geeqie would be really helpful. /Andreas Rönnquist gus...@debian.org
