On Mon, May 6, 2024 at 5:57 AM Guenther Brunthaler wrote:
>
> Package: xscreensaver
> Version: 6.06+dfsg1-3+deb12u1
>
> ### Issue description
>
> Currently (2024-05), on a "stable" installation which is up-to-date,
> xscreensaver displays a message that it is too old and should be
> updated.
On Tue, Apr 23, 2024 at 9:51 AM Jonathan Wiltshire wrote:
> Urgh, I thought this was long since dealt with. Please go ahead urgently.
>
> I presume you've taken steps to avoid it creeping back into future
> releases?
It requires a thorough review of the code (and testing) at every
upstream
On Tue, Apr 23, 2024 at 7:05 PM Jonathan Wiltshire wrote:
>
> Thanks for the upload. Once built I intend to release it through the
> stable-updates mechanism, but the announcement will carry your name. Any
> comments on the following text?
>
> | The XScreenSaver package as released in Debian 12
Package: release.debian.org
Control: affects -1 + src:xscreensaver
User: release.debian@packages.debian.org
Usertags: pu
Tags: bookworm
Severity: normal
Bug #1069617: xscreensaver 6.06 shows upstream upgrade warning from 2024-05-04
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069617)
Hi Andreas, did you find out more about this issue?
Just to clarify a few things:
> pwnam: couldn't get password of "loginname"
This is a normal condition if PAM is used, therefore this message is
only printed in verbose mode, and is likely not important here.
> xscreensaver-auth exited with
Thanks for your report. It would be worthwhile to check if this is a
bug that is already fixed in the newer version of xscreensaver 6.08
that is available in Debian unstable. Can you please try installing
the 6.08 version from Debian unstable? If the binaries don't install
as-is, the package can
I would be happy to maintain this package. It is a Suggests dependency
for the xscreensaver package that I am already maintaining. With the
same upstream and much of the same libraries and tooling I think it
shouldn't be too much extra effort for me.
I have staged commits to
Package: release.debian.org
Control: affects -1 + src:xscreensaver
X-Debbugs-Cc: xscreensa...@packages.debian.org
User: release.debian@packages.debian.org
Usertags: unblock
Severity: normal
Please unblock package xscreensaver 6.06+dfsg1-3
[ Reason ]
A couple of upstream crash regressions
Source: dmg2img
Version: 1.6.7-1
Severity: wishlist
Dear Maintainer,
The current 1.6.7 from upstream lacks support for LZFSE compression,
often used in macOS and iOS disk images.
The offical upstream seems inactive since 2017 but there is a fork
with many fixes and LZFSE added at
On Sun, Feb 19, 2023 at 5:22 PM Simon McVittie wrote:
> It's not clear to me whether this is an xscreensaver issue or a GTK
> issue, so for now I'm marking it to appear in both packages' bug pages.
> If this is a GTK issue, then it's way outside my X11 knowledge, so someone
> with a deeper
On Fri, Feb 10, 2023 at 9:58 PM Tormod Volden wrote:
>
> reassign 1030909 gtk+3.0 3.24.36-3
> affects 1030909 xscreensaver 6.06+dfsg1-2
> thanks
>
> OK, let's see if the gtk package maintainers can comment on this.
I am afraid this is not reaching the attention of
On Fri, Feb 17, 2023 at 5:48 PM Celejar wrote:
> Sorry - I just saw this. I'm currently on 6.06 (Sid package). The
> "Preview" button is currently working, but the screensaver isn't
> activating on its own. I started it with logging enabled, and I see
> regular deactivate events like the following
severity 1030659 normal
thanks
On Sun, Feb 12, 2023 at 4:15 PM Mamoru TASAKA wrote:
>
> So maybe xscreensaver-gl-visual binary does not exist on system
> at the first place??
Well spotted, Mamoru! Thanks a lot for clearing that up. OK, so this
is not a big deal then. I guess sorting out the best
>
> Hi Marco, maybe as a start you can step through xscreensaver-gl-visual
> with gdb. Run from your build tree:
> gdb ./hacks/glx/xscreensaver-gl-visual
> (gdb) break get_gl_visual
> (gdb) run
> # stops at get_gl_visual
> (gdb) next
> and then just press enter repeatedly and it will go "next"
Hi Marco, maybe as a start you can step through xscreensaver-gl-visual
with gdb. Run from your build tree:
gdb ./hacks/glx/xscreensaver-gl-visual
(gdb) break get_gl_visual
(gdb) run
# stops at get_gl_visual
(gdb) next
and then just press enter repeatedly and it will go "next" until end
of the
On Sat, Feb 11, 2023 at 7:50 PM Jamie Zawinski wrote:
>
> Maybe this fixes it?
Yes, many thanks, that seems to fix it.
Tormod
>
> --- a/driver/demo-Gtk.c
> +++ b/driver/demo-Gtk.c
> @@ -1677,6 +1677,7 @@ switch_page_cb (GtkNotebook *notebook, GtkWidget *page,
>state *s = >state;
>
>if
For completeness, here is the backtrace at breakpoint on
XSetInputFocus, on Debian unstable with debug symbols (before
launching gdb, export DEBUGINFOD_URLS="https://debuginfod.debian.net;
).
(gdb) bt full
#0 XSetInputFocus (dpy=0x555fda90, focus=focus@entry=41943047,
This line changes p2->dpms_enabled_p to zero when the Advanced windows
is opened the first time:
CHECKBOX (p2->dpms_enabled_p, dpms_button);
(line 1324 in driver/demo-Gtk.c, in flush_dialog_changes_and_save)
225128 (squirtorus)
xscreensaver-settings: 14:49:38: quit menu
On Sat, Feb 11, 2023 at 2:39 PM Tormod Volden wrote:
>
> On Sat, Feb 11, 2023 at 9:09 AM Klaus Ethgen wrote:
> > With this version, DPMS is not working anymore. The screen always is on
> > and does not go to sleep a
On Sat, Feb 11, 2023 at 9:09 AM Klaus Ethgen wrote:
> With this version, DPMS is not working anymore. The screen always is on
> and does not go to sleep anymore.
Hi, thanks for your report. Which version did you use before?
It looks like I can reproduce this. I enable settings in the GUI and:
reassign 1030909 gtk+3.0 3.24.36-3
affects 1030909 xscreensaver 6.06+dfsg1-2
thanks
OK, let's see if the gtk package maintainers can comment on this.
Here is the code around that XSetInputFocus():
https://salsa.debian.org/gnome-team/gtk3/-/blob/debian/master/gdk/x11/gdkdisplay-x11.c#L1473
And this is the XSetInputFocus call sending the offending request (on
the same system).
(gdb) bt
#0 0x76cfb350 in XSetInputFocus () at /lib/x86_64-linux-gnu/libX11.so.6
#1 0x77eec2c1 in _gdk_wm_protocols_filter
(xev=0x7fffd8e0, event=, data=) at
> FWIW, there is a GDK_SYNCHRONIZE environment variable that makes GDK
> call XSynchronize some places.
This the X error backtrace with GDK_SYNCHRONIZE set. Note this is not
on Debian unstable and I couldn't install libX11 debug symbols.
(gdb) bt
#0 x_error (dpy=0x77e56460,
> > You'll need to run with -sync for backtraces of X errors to make any sense.
> > (Seeing XInternAtom in the stack is always an indication that the backtrace
> > is bogus.)
>
> I have indeed tried -sync and --sync but it is not recognized by
> xscreensaver-settings. How do I enable it?
FWIW,
Wait, this was different:
(gdb) bt full
#0 x_error (dpy=0x77e56460, error=0x7fffd610) at demo-Gtk.c:4253
#1 0x76d03734 in _XError () at /lib/x86_64-linux-gnu/libX11.so.6
#2 0x76d00107 in () at /lib/x86_64-linux-gnu/libX11.so.6
#3 0x76d001a5 in () at
On Fri, Feb 10, 2023 at 10:29 AM Jamie Zawinski wrote:
>
> Ugh. Try adding XSynchronize (s->dpy, True); to xscreensaver_window_realize
> around line 4958, just after s->dpy = gdk_x11_get_default_xdisplay();
>
> It's possible that that won't be early enough to catch it... If not, maybe
> this in
On Fri, Feb 10, 2023 at 10:08 AM Jamie Zawinski wrote:
>
> You'll need to run with -sync for backtraces of X errors to make any sense.
> (Seeing XInternAtom in the stack is always an indication that the backtrace
> is bogus.)
I have indeed tried -sync and --sync but it is not recognized by
On Fri, Feb 10, 2023 at 9:10 AM Marco wrote:
>
> What is the difference in the behaviour of the according to X?
> Is it a fault of mwm or XScreensaver?
I think XScreensaver must wait and ensure the windows is mapped and
viewable before sending the X_SetInputFocus request to it. Whether the
fix
On Fri, Feb 10, 2023 at 8:54 AM Marco wrote:
> > Marco, which window manager are you using?
>
> mwm (motif window manager), on both machines.
I can reproduce the issue after installing mwm. (Normally I use the
Marco window manager :) )
Tormod
On Fri, Feb 10, 2023 at 1:18 AM H. S. Teoh wrote:
> xscreensaver-settings: 16:11:29: xscreensaver-gl-visual did not report a GL
> visual!
> Segmentation fault
> --snip---
>
> Apparently there *is* a segfault, even though it doesn't appear that way
>
>From searching about failing X_SetInputFocus requests, one common
cause is that the window hasn't been mapped by the window manager yet.
I notice that Teoh is using the ratpoison window manager.
Marco, which window manager are you using?
retitle 1030659 xscreensaver-gl-visual did not report a GL visual!
thanks
On Thu, Feb 9, 2023 at 9:01 PM Jamie Zawinski wrote:
>
> Not having a GL visual reported here is definitely a problem in the "should
> never happen" category, so trying to figure out where that's going wrong
> would be
Thanks! So the segfault is just a small bug in the debug printing, it
can be avoided with this patch:
--- driver/demo-Gtk.c.orig2022-12-07 02:12:13.577705209 +0100
+++ driver/demo-Gtk.c2023-02-09 16:59:22.656746738 +0100
@@ -3302,7 +3302,7 @@ fix_preview_visual (state *s)
if
You should now be able to get more details in a gdb backtrace, since
you have all debug symbols and no optimization.
On Thu, Feb 9, 2023 at 12:08 PM Marco wrote:
> I did it on another machine (same segfault), but there is no
> xscreensaver-settings in driver.
>
> The manpage files for it were created.
>
> m@test-moock:~/Downloads/xscreensaver-6.06$ find ./ -name '*xscreensaver-set*'
>
On Thu, Feb 9, 2023 at 10:20 AM Tormod Volden wrote:
> Would it be possible for you to build the upstream sources, without
> optimization, and try it out? You shouldn't need to install any of it,
> just run driver/xscreensaver-settings --debug from the build tree. And
> also
On Thu, Feb 9, 2023 at 10:36 AM Marco wrote:
> From Debian or from the developer itself?
> With which compile options?
I was thinking in the first place the upstream developer tarball at
https://www.jwz.org/xscreensaver/download.html
(or get it from the Debian source package). Compile with -g and
On Mon, Feb 6, 2023 at 11:52 AM Marco wrote:
> Am 06.02.2023 um 11:43:48 Uhr schrieb Tormod Volden:
> > On Mon, Feb 6, 2023 at 11:12 AM Marco wrote:
> > > I've installed xscreensaver-dbgsym.
> > Thanks, the backtrace got a little bit better. Anyway, I wonder if
> &g
Hi, thanks for your report. Thanks also for checking for similar
existing bugs. I believe it is the same issue as in #1030659 but for
now it is better to track the reports separately. I was thinking that
if it was a real issue there must be more reports coming. I am not
able to reproduce this
On Mon, Feb 6, 2023 at 11:12 AM Marco wrote:
> I've installed xscreensaver-dbgsym.
Thanks, the backtrace got a little bit better. Anyway, I wonder if
"xscreensaver-gl-visual did not report a GL visual!" is the real
issue.
Is there something special about your system that would be worthwhile
to
On Mon, Feb 6, 2023 at 10:00 AM Marco wrote:
> Reading symbols from xscreensaver-demo...
> (No debugging symbols found in xscreensaver-demo)
Please install the corresponding debug symbol packages from
http://debug.mirrors.debian.org/debian-debug/pool/main/x/xscreensaver/
Also try "thread apply
On Mon, Feb 6, 2023 at 9:39 AM Marco Moock wrote:
> Starting it via xscreensaver-demo --debug or xscreensaver-settings --debug
> If I don't used --debug, it also crashed without the segfault error message
> Application crashed,
Thanks for your report. Can you please provide a backtrace from the
OK. Maybe you can try 6.06, it is in salsa but is awaiting sponsoring
and uploading. In any case, please attach the verbose log from
xscreensaver -v -v -v -log your.log
I am not able to reproduce the issue.
Tormod
Note that Debian hasn't installed any
/usr/lib/X11/app-defaults/XScreenSaver at least since 2000
(xscreensaver 3.26). The installation (postinst) would also for a long
time remove any stale fiiles from that location. The app defaults file
is shipped in /etc/X11/app-defaults. If Lubuntu has been
>
> I just wanted to warn that version 6.05 is available upstream. I've built it
> on
> Testing without any issue. Thanks for your attention.
>
Hi, I am working on packaging 6.06 now, and should get it in before
the bookworm freeze.
Regards,
Tormod
VA, please provide a tested patch against our VCS
https://salsa.debian.org/debian/xscreensaver
thanks
On Mon, Feb 21, 2022 at 9:03 AM Christian Britz wrote:
> Dear Maintainer,
>
> I have configured xscreensaver to use "Blank Screen Only", enabled power
> management and "Quick Power-off in Blank Only Mode".
> The display IS powered off when I issue "File -> Blank Screen Now" in
> xscreensaver-demo.
On Tue, Mar 15, 2022 at 6:57 PM Julian Gilbey wrote:
> euler:~ $ xscreensaver -no-splash
> xscreensaver-auth: 17:48:30: OOM: /proc/7427/oom_score_adj: Permission denied
> xscreensaver-auth: 17:48:30: To prevent the kernel from randomly unlocking
> xscreensaver-auth: 17:48:30: your screen via
dfu-util 0.11-1 has been uploaded to the DELAYED queue with a delay of
7 days, see attached nmudiff.
Tormod
dfu-util-0.11-1.nmudiff
Description: Binary data
tag 1005956 pending
thanks
On Fri, Feb 18, 2022 at 8:59 AM Helmut Grohne wrote:
>
> I cannot reproduce that failure locally.
Neither can I any longer. Weird. But I was working on this and trying
to use autoreconf and much more to try to work around the autoconf
2.71 issue, so maybe some
Another option would be to keep dh_auto_configure if
--disable-option-checking can be used. Or patching configure to
accept/ignore --runtimedir specifically.
On Fri, Feb 18, 2022 at 8:44 AM Tormod Volden wrote:
>
> Oh, and
> DEB_BUILD_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_BUILD
Oh, and
DEB_BUILD_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE)
DEB_HOST_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE)
on top.
On Fri, Feb 18, 2022 at 8:41 AM Tormod Volden wrote:
>
> Thanks, but your patch is basically reverting commit 15712174. The
&g
Thanks, but your patch is basically reverting commit 15712174. The
reason for calling configure directly is that dh_auto_configure adds
the --runtimedir option which is not supported by this configure.
Please try if adding
--build=$(DEB_BUILD_GNU_TYPE) \
--host=$(DEB_HOST_GNU_TYPE) \
instead will
Package: xtron
Version: 1.1a-14
Please find attached a debdiff which reworks the packaging to use dh
and quilt and recent versions of standards.
Note that the debdiff reverts the previous direct patching of upstream
sources and replaces it with debian/patches/*.
I might proceed to an ITS later.
Package: aa3d
Version: 1.0-8
Please find attached a debdiff which reworks the packaging to use dh
and quilt and recent versions of standards.
I might proceed to an ITS later.
Best regards,
Tormod
aa3d_1.0-9.debdiff
Description: Binary data
Of course, if current maintainers want to continue, feel free to use
or pick from the attached debdiff (only of debian/ folder) for a
0.11-1 package.
Tormod
debian_dfu-util_0.11-1.debdiff
Description: Binary data
Package: dfu-util
Version: 0.9-1
Severity: Important
X-Debbugs-CC: Uwe Hermann , m...@qa.debian.org
I have the intention to take over maintainership, or if interest,
co-maintenance of the dfu-util package.
Bugs against dfu-util hasn't seen maintainer activity since March 2016
(last Debian
Please behave when using the Debian forums.
I was obviously talking about what to do in the Debian package, not
upstream. I think it makes sense for us to not blindly pick whatever
is in the user's PATH. And we will eventually get to reunifying the
packages, it is a bit more work though due to
I agree to "xscreensaver SHOULD search for screensavers only in
/usr/lib/xscreensaver, where other packages are expected to install
them", with the exception to allow users to specify a full path in
their xscreensaver config, in case they want to use something
installed elsewhere. There were
Hi Andreas,
Thanks for the report. The package already depends on wget, which
recommends ca-certificates, so this only affects users that have
decided (against the recommendation) to not install this.
In any case, the expected retrieved file has a known checksum (the
whole downloading dance is
close 990007 5.44+dfsg1-1
merge 920753
thanks
Thank you for the report, this was fixed in 5.44+dfsg1-1.
Tormod
This issue is marked as affecting 5.42+dfsg1-1 in buster (and even
stretch) in our CVE tracker, however the set_cap action was first
added in 5.44+dfsg1-1.
https://security-tracker.debian.org/tracker/CVE-2021-31523
Tormod
This issue is marked as affecting 5.42+dfsg1-1 in buster (and even
stretch) in our CVE tracker, however the openwall report says:
"The issue affects only XScreenSaver version 5.45. Versions 5.44 and
older, as well as 6.00, are not affected."
Tormod
On Mon, Jun 14, 2021 at 9:45 AM Sebastian Ramacher wrote:
>
> xscreensaver already migrated.
Thanks for taking care of the migration!
> > Question:
> > The trivial addition of a missing " || true" in debian/rules* would fix
> > building on kfreebsd/hurd. Could that be considered?
>
> I would
deo output disconnection (Closes: #989508)
-- Tormod Volden Sun, 06 Jun 2021 12:25:19 +0200
Justification of the changes:
The fix for 987149 has been discussed with the security team. The change
is small, just disabling an extra feature of the "sonar" screensaver
hack/mode, and the c
On Sun, Jun 6, 2021 at 12:56 PM Tormod Volden wrote:
>
> I'll take a look at this now. We might want to include this in 5.45+dfsg1-2.
>
I have included the fix from Qubes-OS, pushed to salsa in commit 60304c21.
I did some testing by plugging and unplugging an external monitor
around
On Sun, Jun 6, 2021 at 11:57 AM Salvatore Bonaccorso wrote:
>
> I've prepared an NMU for xscreensaver (versioned as 5.45+dfsg1-1.1) and
> uploaded it to DELAYED/2. Please feel free to tell me if I
> should delay it longer.
>
I saw this now. I would of course prefer to have my 5.45+dfsg1-2
I'll take a look at this now. We might want to include this in 5.45+dfsg1-2.
Tormod
On Sat, Jun 5, 2021 at 8:51 PM Salvatore Bonaccorso wrote:
>
> On oss-security mailinglist an issue with xscreensaver has been
> published which seems to be specific to the 4.45 version (and not
> affecting
wrote:
>
> Hi Tormod,
>
> On Thu, May 06, 2021 at 07:38:34PM +0200, Moritz Mühlenhoff wrote:
> > Am Mon, Apr 19, 2021 at 11:42:54AM +0200 schrieb Moritz Muehlenhoff:
> > > On Sun, Apr 18, 2021 at 07:21:31PM +0200, Tormod Volden wrote:
> > > > Yes, I think d
On Sun, Apr 18, 2021 at 7:04 PM Salvatore Bonaccorso wrote:
> Sure I did as I'm on the team alias as well. Given it looks unlikely
> that mesa will fix it (at the moment?) I though/think we should
> probably do something on xscreensaver's side in Debian as well.
>
> Is the sonar screensaver
Indeed, as Jamie points out, the problem is in Mesa.
Salvatore, why did you file this against xscreensaver? I thought you
had followed the e-mail discussion we had with Tavis?
Tormod
Hi Joachim,
Thanks for the report. I was unaware of the other packages using
/usr/lib/xscreensaver . Is there a way I can have these listed? Yes,
they must either follow the xscreensaver changes (and we can add
Breaks) or use full path in configuration.
Getting this hack upstream sounds like a
OK, so I guess removing the global user enablement will avoid having
xscreensaver running in lightdm. However, I still wonder if this
lingering service that was observed will also be the case if a user
logs out and another (or same) logs in within 15 seconds? Is there
still an underlying issue
On Sun, Jan 10, 2021 at 5:46 PM Michael Biebl wrote:
> If you want to clean up this state, I would propose to use the following
>
> deb-systemd-helper --user purge xscreensaver.service >/dev/null || true
> deb-systemd-helper --user unmask xscreensaver.service >/dev/null || true
>
> Guarded by a
I should add that although we added the
debian/xscreensaver.user.service file in 5.44+dfsg1-2, we are using
"dh_installsystemduser --no-enable" since 5.45+dfsg1-1, so it won't be
enabled for the lightdm user in new installs or upgrades skipping
5.44+dfsg1-2. It will now only be enabled for those
In that case it seems better to only Recommends: gsfonts-x11 . It
seems that xfonts-100dpi will only be useful in few cases, and I don't
see in what case it would be better than gsfonts-x11.
If we use Recommends: gsfonts-x11 | xfonts-100dpi I /think/ the first
will be installed if none are
On Sun, Jan 10, 2021 at 12:44 PM Michael Biebl wrote:
> Negating @system might work.
> Something like ConditionUser=!@system, but untested.
Thanks! I was just about to suggest this myself after searching around for this.
(https://www.freedesktop.org/software/systemd/man/systemd.unit.html)
I
On Tue, Jan 5, 2021 at 6:09 PM Ryan Kavanagh wrote:
>
> Control: reopen -1
> Control: found -1 5.45+dfsg1-1
>
> On Wed, Dec 23, 2020 at 11:06:10AM +, Debian Bug Tracking System wrote:
> >* Do not enable systemd unit by default, since it breaks existing
> > (non-systemd) setups
On Fri, Jan 8, 2021 at 10:00 PM Jamie Zawinski wrote:
>
> > In xscreensaver (or maybe lightdm).
> > Why is xscreensaver started in the lightdm session anyway?
> > Is xscreensaver really usable as a per user service or should it be per
> > session?
> > Why is the lightdm xscreensaver instance
So if we replace the Recommends on xfonts-100dpi to gsfonts-x11
everybody will be happy? Or is just xfonts-base needed?
Regards,
Tormod
tags 977804 pending
thanks
We will use dh_installsystemduser --no-enable.
On Mon, Dec 21, 2020 at 9:03 AM Bjørn Mork wrote:
> Masking the unnecessary systemd unit fixes the issue for me. This
> should probably be the default as long as there is no way to do
> systemd integration without breaking existing configurations.
Hi, thanks for your report. What is the best way
FYI, my first patch above was applied in upstream 5.45 and will appear
in 5.45-1 in unstable soon. Please let us know if it works fine with
your SSSD.
Tormod
Just a few notes on the new upstream release 0.10:
- Closes: #840390, #849873, #952905
- debian/rules: udev rules file renamed to 60-dfu-util.rules
- debian/dfu-util.install: Please consider installing dfuse-pack to
/usr/bin (instead of leaving a zip in examples)
Best regards,
Tormod
On Thu, Oct 29, 2020 at 7:27 AM Helmut Grohne wrote:
> xscreensaver fails to cross build from source, because the upstream
> configure hard codes the build architecture pkg-config as it uses
> AC_PATH_PROGS to detect pkg-config. I'm attaching a patch that switches
> it to AC_PATH_TOOL and makes
Package: sponsorship-requests
Hi,
(Following the advice on http://mentors.debian.net/sponsor/rfs-howto
... No, that's a joke because it is a broken link, from
https://wiki.debian.org/DebianMentorsFaq#How_do_I_get_a_sponsor_for_my_package.3F)
My current sponsor for the xscreensaver package is
>
> This is only the libglade-convert script for converting
> pre-2001 (sic) glade files.
>
> I can adopt or NMU (whatever you prefer) libglade2 with the trivial fix
> of removing this script.
>
> > Regards,
> > Andreas Henriksson
>
> cu
> Adrian
Adrian, are you still willing to NMU this? Are
Upstream pull request that explains and fixes this:
https://github.com/gregkh/usbutils/pull/103
Thanks, this was first reported in bug #920753 and has been fixed in git.
Tormod
> Le 30/09/2020 à 22:06, Jamie Zawinski a écrit :
> > The reason remote.c includes @hostname on the XA_SCREENSAVER_ID is to
> > detect the case when "xscreensaver" and "xscreensaver-demo" are running on
> > different hosts, because if they are different hosts, they are likely
> > different file
>
> I maintain the code at g...@salsa.debian.org:tormod-guest/s3switch.git
> Can you please create the repo at
> g...@salsa.debian.org:xorg-team/app/s3switch.git ?
>
Scratch that, the repo is already there now. But I cannot push to it.
If anyone can pull from mine and push there it would be good.
tag 968529 pending
thanks
Hi Simon,
Thanks for the report. I chose the latter of your suggestions (and
added dh_install).
I maintain the code at g...@salsa.debian.org:tormod-guest/s3switch.git
Can you please create the repo at
g...@salsa.debian.org:xorg-team/app/s3switch.git ?
Best regards,
The launchpad links I posted didn't survive. I have now set up a git
repository for the Debian packaging,
which includes Stephen's 1.4.1 and my 1.5.0:
https://salsa.debian.org/tormod/agar
Upstream has after 4 years recently released a 1.6.0, I might take a look at it.
I was running xscreensaver continuously for a couple of months but
could not reproduce. If nobody else can reproduce and you cannot
provide more information I must at least lower the severity of this
bug report.
Regards,
Tormod
On Thu, Mar 26, 2020 at 10:29 PM Tormod Volden wrote:
>
>
I looked at the above-mentioned "porting guide" and optimistically
started on the C code changes, which appear easy enough. Please see
attached patch which at least compiles. For testing it I tried
gtk-builder-convert but this was not enough, see error messages below.
Maybe someone familiar with
Thanks for the report, this has been discussed in bug #816722 as well.
Tormod
Hi Vincent,
Thanks for your report. Yes, I understand it from the messages that on
your machines getpwuid() returns a username including this "@domain"
part, but the server_xscreensaver_version() which queries the server,
strips away all "@" parts (I don't even know if XGetWindowProperty()
merge 944382 920753
thanks
Thanks for your report.
On Thu, Apr 2, 2020 at 10:21 PM Stephen Lyons wrote:
>
> Package: xscreensaver-data-extra
> Version: 5.42+dfsg1-1
>
> --- Please enter the report below this line. ---
> The problem seems to be a spurious line-feed part way through the
>
Jens, the log indicates the machine has an Intel(R) HD Graphics 530
(Skylake GT2) GPU. Is this the same for the other machines? I have
been trying to reproduce for several days, also running on Intel
drivers, but with a 5500 series GPU and also I am on "testing" so I
have newer Xorg and kernel.
1 - 100 of 452 matches
Mail list logo
