Bug#953098: xscreensaver: Crashes with XIO: fatal IO error

Jens, can you please also attach an Xorg log from the crash? If I understand the original report right, the X session continued otherwise as normal, so I guess the X server didn't crash. It could have run out of memory temporarily, or xscreensaver requested something out of reach, like loads of

Bug#954017: xscreensaver: epicycle screensaver braws part of its figure in black on black background

tag 954017 pending thanks Hi James, Thanks for the report. I suppose this was a bug in 5.42 that was fixed in 5.43. It would be nice if you can confirm this by trying our 5.43 packaging from: https://salsa.debian.org/debian/xscreensaver Regards, Tormod On Sun, Mar 15, 2020 at 8:15 PM James

Bug#932837: xscreensaver: No text on lock screen

> Kernel taint flags: TAINT_USER BTW, do you know why your kernel is tainted? > > If you really think its a kernel problem then I can certainly build a newer > > version to test, but I don't currently have the time and there's nothing > > newer > > available from Debian AFAIK, not even in

Bug#932837: xscreensaver: No text on lock screen

On Tue, Jul 23, 2019 at 9:33 PM Jacob Adams wrote: > > No text at all appears in the unlock dialog. > The version number and the text in the buttons simply is not visible. Hi Jacob, Thanks for your bug report. Can you please try to check if it is related to the graphics driver? Can you try a

Bug#782644: Re : Bug#782644: Re : Bug#782644: Re : Bug#782644: xscreensaver always rejects my password

On Sun, Mar 24, 2019 at 4:45 PM nicolas.patrois wrote: > > Le 24/03/2019 14:22:53, Tormod Volden a écrit : > > Is your /etc/shadow readable by the shadow group and your > > /sbin/unix_chkpwd setgid shadow? > > I think so: > > > ll /etc/shadow > -rw-r-

Bug#782644: Re : Bug#782644: Re : Bug#782644: xscreensaver always rejects my password

On Wed, Feb 27, 2019 at 3:36 PM nicolas patrois wrote: > > I have this for example: > Feb 2 17:57:22 nicolas unix_chkpwd[10736]: check pass; user unknown > Feb 2 17:57:31 nicolas unix_chkpwd[10743]: check pass; user unknown > Feb 2 17:57:31 nicolas unix_chkpwd[10743]: password check failed for

Bug#782644: Re : Bug#782644: xscreensaver always rejects my password

On Thu, Feb 14, 2019 at 9:27 AM Nicolas Patrois wrote: > I suspect a problem with PAM because I can read a very quick yellow message > from PAM on top of the screen. > Note that Ctrl-Alt-Fx won’t let me out of X. Is there any information in e.g. /var/log/auth.log ? Regards, Tormod

Bug#782644: xscreensaver always rejects my password

Nicolas, I see that you are using a French locale and so probably have a French keyboard. Is it possible that the keyboard mapping becomes wrong, so it would work if you typed your password as if you had an English keyboard? Best regards, Tormod On Sat, Feb 2, 2019 at 7:09 PM Nicolas Patrois

Bug#920753: xscreensaver-data-extra: trouble with glitchpeg.desktop

tag 920753 pending thanks On Mon, Jan 28, 2019 at 7:33 PM Patrice Duroux wrote: > Could you please consider this: > https://salsa.debian.org/debian/xscreensaver/merge_requests/1 > or I am wrong to solve the trouble with this desktop file? Thanks, I have applied your fix. Best regards, Tormod

Bug#918753: xscreensaver: xdg desktop files miss many items from debian menu file

On Wed, Jan 9, 2019 at 3:09 AM Matthew Gabeler-Lee wrote: > I noticed on an upgrade that I lost (in wmaker) many menu items related to > xscreensaver. On investigation this is because these menu items are only > provided in xscreensaver in the legacy Debian menu system and not in the > modern xdg

Bug#636317: libagar (ITP) libtool troubles

On Sun, Jan 13, 2019 at 5:57 PM Tormod Volden wrote: > Unfortunately, it doesn't build in the PPA yet, because of a libtool > issue. If anyone can take a look at the failed build log and give me a I believe I have fixed this issue (bug in BSDBuild makefile), and the new package is at:

Bug#636317: libagar (ITP) libtool troubles

While looking for a Debian package of agar, I found Stephen's work here: https://launchpad.net/~bregma/+archive/ubuntu/debian/+sourcefiles/agar/1.4.1-1/agar_1.4.1-1.dsc I updated it for upstream 1.5.0 and a few other fixes here:

Bug#914109: xscreensaver-data: looks for image files to display even though it is told not to

Hi, Thanks for your bug report. I can confirm this issue, for instance by running glitchpeg standalone: usage: xscreensaver-getimage-file [--verbose] directory-or-feed-url Prints the name of a randomly-selected image file. The directory is searched recursively. Images smaller

Bug#907674: xscreensaver: Please update to latest version 5.40

On Fri, Aug 31, 2018 at 10:36 AM Eduard Bloch wrote: > > I am reporting this as severity:normal because I would like to report a > minor issue to upstream, but the upstream is known for the > use-my-latest-version-from-yesterday-or-else policy. > > Therefore, please update the version to 5.40.

Bug#907674: preparing an upload of xscreensaver 5.40 (and later)

On Wed, Sep 5, 2018 at 12:35 AM, Antoine Beaupré wrote: > Hi Tormod! > > I've noticed the Debian package of xscreensaver is somewhat lagging > behind the upstream version in "unstable". I also noticed you have done > good work in the git repository to package 5.39. > > I have taken that work and

Bug#878373: xscreensaver-screensaver-webcollage: Fails to get resuls from google, bing, and instagram making collages repetitive.

Dang, you're right. It has only gone almost 9 months sometimes. Nice table. perl?

Bug#878373: xscreensaver-screensaver-webcollage: Fails to get resuls from google, bing, and instagram making collages repetitive.

Haha, what are you smoking? I don't even bother to look it up, I guess there is not even dates in your changelog. It is more like 1-2 per calendar year maximum. The one that went into Debian's previous stable release and you made so much fuzz about, had been the last release for I don't know how

Bug#854691: xscreensaver user unit

On Fri, Oct 27, 2017 at 4:23 AM, Daniel Kahn Gillmor wrote: > On Thu 2017-08-31 12:07:10 +1000, Jeremy Visser wrote: >> I've attached a patch which fixes the issue. Thanks for the patch, and for forwarding it here (don't know where it was sent). > > Jeremy's patch (below) looks reasonable to me.

Bug#878373: xscreensaver-screensaver-webcollage: Fails to get resuls from google, bing, and instagram making collages repetitive.

Hi, With regards to the latest XScreenSaver release, which I hope will fix this issue, I was fast getting it packaged up in git, but it has sitting there for a while because I need to check all the Debian QA stuff, new policies, etc, and get someone to review it, but most importantly real life got

Bug#878379: xscreensaver-screensaver-webcollage: Please provide a means to set safe seach levels for those image search mehods that support it.

Hi, Thanks for the suggestion. It's legitimate wish, but nothing I will look into unless someone sends a patch. I also share upstream opinion on this to a large degree, and people can refrain from installing webcollage if they are afraid of what internet can come up with. Personally I am skeptical

Bug#876087: xscreensaver: source-less and unlicensed code at hacks/images/m6502/dmsc.asm

On Sun, Sep 24, 2017 at 9:02 PM, Daniel Serpell wrote: > Attached is the source to the demo, in 6502 assembly, with a GPL > license. Daniel and Daniel, Thanks a lot for sorting this out. Sometimes someone just has to ask and it is as easy as that. Regards, Tormod

Bug#873108: xscreensaver does not trap errors from intltool-update

On Thu, Aug 24, 2017 at 6:00 PM, Helmut Grohne wrote: > Source: xscreensaver > Version: 5.36-1 > Severity: serious > Justification: policy 4.6 > User: helm...@debian.org > Usertags: rebootstrap > > The debian policy section 4.6 requires that when build commands fail, > the

Bug#873106: xscreensaver FTCBFS: fails to detect a working c compiler

On Thu, Aug 24, 2017 at 5:57 PM, Helmut Grohne wrote: > > xscreensaver fails to cross build from source, because it insists on > using AC_TRY_RUN to verify that the compiler works. That's generally a > bad idea and can simply be discarded. It also uses the build > architecture

Bug#840390: dfu-util: Allow all console users access to the USB device

Hi Uwe, Would it help you to get a full debdiff, or should we try to get a NMU for this? Best regards, Tormod On Tue, Oct 11, 2016 at 9:15 AM, Petter Reinholdtsen wrote: > > debian/patches/udev-console-access.patch: > > Description: Use ACLs to provide device access to

Bug#822049: linux-wlan-ng: Build arch:all+arch:any but is missing build-{arch,indep} targets

tags 822049 pending thanks Hi Santiago, On Fri, Jul 29, 2016 at 2:19 AM, Santiago Vila wrote: > > I also recommend switching to dh, but in the meantime, the attached > patch should work. Thanks! I have actually prepared a new release of linux-wlan-ng which fixes this among other things, but it

Bug#823049: patch works for me

tags 823049 pending thanks On Sat, Jun 11, 2016 at 5:10 AM, Adam Borowski wrote: >> Can you (or anyone on Hurd) please verify that this patch fixes the >> issue, and that the package now builds successfully? > > Just tried it: the package builds and appears to work. Thanks a lot, Adam! Tormod

Bug#822621: xscreensaver-data-extra and xscreensaver-gl-extra should Enhance cinnamon-screensaver

On Mon, May 30, 2016 at 11:08 PM, Christoph Anton Mitterer wrote: > On Tue, 2016-04-26 at 17:56 +0200, Tormod Volden wrote: >> > Well it's the same case as with gnome-screensaver, I thought. >> > Both can use the screensaver modules provided by xscreensaver >> I should

Bug#826509: xscreensaver: Please hide xscreensaver-properties.desktop in GNOME

On Sun, Jun 5, 2016 at 9:49 PM, Laurent Bigonville wrote: > I would be nice if xscreensaver-properties.desktop was not displayed by > default in GNOME (and probably others). It seems there are many GNOME users who still want to use xscreensaver. They expect to find the preference panel if they

Bug#825581: Hmm...

On Sat, May 28, 2016 at 2:34 AM, Peter S wrote: > If another app can capture keyboard input while the screen is locked, > it can watch the user type in the unlock password. Only use software you can trust :) I think this would be a limitation of X11, and not much

Bug#825581: xscreensaver: xscreensaver doesn't prevent Mumble push-to-talk

> Xscreensaver doesn't prevent Mumble from reading its push-to-talk key, > allowing someone to do whatever Mumble's keyboard shortcuts allow, > like talk to people in the current Mumble room while the screen is > locked. > > (I bound left control, if it matters) Hi, What is Mumble, anyway?

Bug#774539: xscreensaver-data-extra: Too many icons showing in GNOME Shell Applications Menu

On Mon, May 23, 2016 at 6:37 PM, Laurent Bigonville wrote: > On Tue, 21 Jul 2015 16:40:25 +0200 Tormod Volden > wrote: >> >> > When running GNOME Shell and xscreensaver modules such as >> > xscreensaver-data- >> > extra and others are added to xscreensave

Bug#823049: xscreensaver: FTBFS on hurd-i386: error: 'PTHREAD_STACK_MIN' undeclared

On Mon, May 2, 2016 at 9:21 PM, Tormod Volden <debian.tor...@gmail.com> wrote: > The "offending" code is: > > # if defined _POSIX_SOURCE || defined _POSIX_C_SOURCE || defined > _XOPEN_SOURCE > /* PTHREAD_STACK_MIN needs the above test. */ > assert(stacksize

Bug#823584: [PATCH] Correct top-level directory name in repackaged tarballs

On Fri, May 6, 2016 at 7:39 PM, Jakub Wilk wrote: > * Tormod Volden, 2016-05-06, 11:21: >> >> >> -packagename-upstream-version.orig >> as the >> >> +packagename-upstream-version+dfsg >> as the > > > NACK. That would be misleading if the ta

Bug#823584: [PATCH] Correct top-level directory name in repackaged tarballs

Package: developers-reference Version: 3.4.17 I believe the top-level directory name in a repackaged source tarball should be name-ver+dfsg and not name-ver.orig Best regards, Tormod From 61ef785ed96a227d43b1b0696fdfbccb3d5db5ea Mon Sep 17 00:00:00 2001 From: Tormod Volden <debian.

Bug#823049: xscreensaver: FTBFS on hurd-i386: error: 'PTHREAD_STACK_MIN' undeclared

The "offending" code is: # if defined _POSIX_SOURCE || defined _POSIX_C_SOURCE || defined _XOPEN_SOURCE /* PTHREAD_STACK_MIN needs the above test. */ assert(stacksize >= PTHREAD_STACK_MIN); # endif PTHREAD_VERIFY(pthread_attr_setstacksize(, stacksize)); Maybe we should simply skip the above

Bug#583520: don't assume an Internet connection to make package usable

tags 583520 wontfix thanks [d*mn touchpad / email web client, trying again] >>> Perhaps also mention somewhere that if the user does not have a net >>> connection during package install, he can instead just download URL A on >>> a machine that does, and then copy it into file B. > > TV> That

Bug#583520: don't assume an Internet connection to make package usable

tags 583520 wontfix thanks >>> Perhaps also mention somewhere that if the user does not have a net >>> connection during package install, he can instead just download URL A on >>> a machine that does, and then copy it into file B. > > TV> That sounds good, I guess we could add this to a README

Bug#822621: xscreensaver-data-extra and xscreensaver-gl-extra should Enhance cinnamon-screensaver

>>> Wouldn't it be better to have cinnamon-screensaver Suggest these >>> packages? I guess cinnamon-screensaver Recommends xscreensaver-data >>> and xscreensaver-gl already. >> Well they recommend it already... so no need for a Suggests. > > Note that I was talking about two other packages here. I

Bug#822621: xscreensaver-data-extra and xscreensaver-gl-extra should Enhance cinnamon-screensaver

> Well it's the same case as with gnome-screensaver, I thought. > Both can use the screensaver modules provided by xscreensaver I should probably remove the Enhance for gnome-screensaver. >> Wouldn't it be better to have cinnamon-screensaver Suggest these >> packages? I guess

Bug#822621: xscreensaver-data-extra and xscreensaver-gl-extra should Enhance cinnamon-screensaver

> The packages xscreensaver-data-extra and xscreensaver-gl-extra should Enhance > the package cinnamon-screensaver, just as they already enhance > gnome-screensaver. Hi Chris, I can add these, but I am unsure about the usefulness of Enhance here. Wouldn't it be better to have

Bug#820945: pu: package xscreensaver/5.30-1+deb8u2

On Thu, Apr 14, 2016 at 11:52 AM, Jonathan Wiltshire wrote: > Personally I would like to see it go through jessie-updates, and then we can > put this embarrassment behind us quicker - especially as the fix is so > trivial. But that's up to SRMs. That would be fine for me as

Bug#816722: zoom-player: interraction with xscreensaver

On Thu, Apr 14, 2016 at 1:38 AM, Jamie Zawinski wrote: > I'm not going to change anything here. Xscreensaver is working as designed. > The problem being experienced is because the system it is running on is > misconfigured. > > Specifically, xscreensaver is only halfway installed;

Bug#816722: zoom-player: interraction with xscreensaver

On Sat, Apr 9, 2016 at 5:41 AM, Jamie Zawinski wrote: > I still think the root of the problem here is that the "zoom" xscreensaver > hack is marked as enabled in the .ad file, but it is not actually installed. > So the .ad file is wrong. Correcting it would fix this. I suppose it

Bug#820945: pu: package xscreensaver/5.30-1+deb8u2

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: pu Bug #819703: Disable Easter egg about "outdated" version There is an outcry from users because the xscreensaver preference dialog / demo / splash screen since a few days displays a message

Bug#816722: zoom-player: interraction with xscreensaver

On Fri, Apr 8, 2016 at 7:01 PM, Jamie Zawinski <j...@jwz.org> wrote: > On Fri Apr 08 2016 02:12:12, Tormod Volden wrote: > >> But let me be clear, I am only talking about the part "let's start the >> hack with name X". For running helpers etc it would be ni

Bug#816722: zoom-player: interraction with xscreensaver

On Fri, Apr 8, 2016 at 12:35 AM, Jamie Zawinski wrote: > If you modify xscreensaver to not obey $PATH, you are making it do this > weird, confusing, undiscoverable thing. > > If you merely launch it with a different $PATH, then it's easy to know what's > going on. Especially since

Bug#816722: zoom-player: interraction with xscreensaver

On Fri, Apr 8, 2016 at 12:39 AM, Jamie Zawinski wrote: > > Hey guess what, this is a problem that only exhibits itself because you took > the code that I had tested and distributed, ripped half of it out, and > expected the other half to continue working properly. > > I am shocked

Bug#820378: Ensure users report bugs in BTS and not to upstream directly

On Fri, Apr 8, 2016 at 6:02 AM, Paul Wise wrote: > On Thu, 7 Apr 2016 21:22:22 +0200 Tormod Volden wrote: >> According to upstream, a lot of Debian stable users send bug reports >> about the xscreensaver package directly to him. > > I note that upstream is or was subscribed

Bug#816722: zoom-player: interraction with xscreensaver

On Thu, Apr 7, 2016 at 10:54 PM, Jamie Zawinski wrote: > Having xscreensaver override and ignore the $PATH that the user passed in is > a terrible idea. Since we are in control of where we install the hacks (/usr/lib/xscreensaver), it is not that bad. But it would prevent the user

Bug#816722: zoom-player: interraction with xscreensaver

On Sat, Mar 5, 2016 at 5:22 PM, Alexandre Detiste wrote: > Le samedi 5 mars 2016, 16:29:41 Stephen Kitt a écrit : >> >> Or perhaps xscreensaver-demo should only look in /usr/lib/xscreensaver... >> (For the xscreensaver maintainers: the context here is that the

Bug#819724: Please find a second maintainer

On Thu, Apr 7, 2016 at 9:25 AM, Goswin von Brederlow wrote: > The BTS is not just for the maintainer. It also documents things for > users. Like what bugs are already known. > > When I see a package with lots of patches in the BTS my willingness to > patch something myself goes

Bug#819703: xscreensaver: please disable "This version of XScreenSaver is very old! Please upgrade!" message

On Wed, Apr 6, 2016 at 1:01 AM, Peter Nowee wrote: > Here is a patch I was working on to add links to the Debian BTS in the > several places where bug reporting is encouraged (man pages, dialog > boxes). Perhaps it can be of use. Note that I did not have a chance to > test

Bug#820378: Ensure users report bugs in BTS and not to upstream directly

ee <pe...@peternowee.com> Date: Wed, Apr 6, 2016 at 1:01 AM On Tue, Apr 05, 2016 at 08:31:46PM +0200, Tormod Volden wrote: > Debian users should always report bugs to Debian and not directly > upstream. So the author being spammed by Debian users on old versions > should in

Bug#820105: xscreensaver: please consider removal from sid

severity 820105 wishlist thanks I don't know if the reason for suggesting "grave" severity here was to make it an RC bug, but otherwise grave means: "makes the package in question unusable or mostly so, or causes data loss, or introduces a security hole allowing access to the accounts of users

Bug#820105: xscreensaver: please consider removal from sid

On Tue, Apr 5, 2016 at 3:48 PM, Steven Chamberlain wrote: > The upstream maintainer of xscreensaver has explicitly asked Debian > to stop shipping it, which is a shame of course: > https://www.jwz.org/blog/2016/04/i-would-like-debian-to-stop-shipping-xscreensaver/ Hi Steven, The above post was a

Bug#819703: Please fix stable version 5.30-1

On Thu, Apr 7, 2016 at 5:43 AM, Jamil Said Jr. wrote: > I read your email and my understanding is that only the unstable version > 5.34 and beyond will be fixed? What about the stable version 5.30? Can you > also fix that? Hi Jamil, Thanks for your interest in the Debian development process! Any

Bug#819724: Please find a second maintainer

severity wishlist On Fri, Apr 1, 2016 at 3:29 PM, Goswin von Brederlow wrote: > Package: xscreensaver > Severity: important > > The xscreensaver package has 120 bugs going back over 9 years that are > just rotting in the BTS without attention. Some of them are tagged > security, some tagged

Bug#819595: xscreensaver: please make the build reproducible

tags 802914 pending thanks On Thu, Mar 31, 2016 at 1:01 AM, Sascha Steinbiss wrote: > > I have attached a patch to use a fixed, sorted order for these files. > This makes the build reproducible for me in my local test environment. Thanks for the patch, I have applied it. Tormod

Bug#819703: xscreensaver: please disable "This version of XScreenSaver is very old! Please upgrade!" message

Thanks to Michael (and others?) for providing patches, generally the most valuable contribution in a bug report. Jamie, you could have deleted all e-mail reports from Debian users in the time it took you to write this Easter egg :) (Just responding to the productive participants first, since

Bug#814377: Please update to stm32flash 0.5

@@ +stm32flash (0.5-1) unstable; urgency=medium + + * New upstream release + * Drop debian/patches/i2c-linuxonly.patch (applied upstream) + * Standards-Version bumped to 3.9.6 (no changes needed) + + -- Tormod Volden <debian.tor...@gmail.com> Wed, 10 Feb 2016 21:05:42 +0100 + stm32flash (0.4-2) un

Bug#814277: Please update to dfu-util 0.9

) unstable; urgency=medium + + * New upstream release + * Updated upstream location in control/copyright/watch + + -- Tormod Volden <debian.tor...@gmail.com> Tue, 09 Feb 2016 21:20:40 +0100 + dfu-util (0.8-1) unstable; urgency=medium * New upstream release (Closes: #696866). diff -Nurp df

Bug#810228: linux-wlan-ng: Firmware download location disappeared

On Thu, Jan 7, 2016 at 3:03 PM, Alexander E. Patrakov wrote: > I have tried to install the prism2-usb-firmware-installer package. > > It tried to download a firmware file from this location: > >

Bug#802914: xscreensaver: upstream 5.34 fixes crash

On Sun, Oct 25, 2015 at 12:03 PM, Tormod Volden wrote: > On Sun, Oct 25, 2015 at 7:41 AM, Salvatore Bonaccorso wrote: >> On Sat, Oct 24, 2015 at 11:59:38PM -0400, Michael Gilbert wrote: >>> A new upstream version is out that fixes a crash while swapping >>> m

Bug#802914: xscreensaver: upstream 5.34 fixes crash

On Sun, Oct 25, 2015 at 7:41 AM, Salvatore Bonaccorso wrote: > On Sat, Oct 24, 2015 at 11:59:38PM -0400, Michael Gilbert wrote: >> A new upstream version is out that fixes a crash while swapping >> monitors, which has security implications. Thanks for the report, guys. I will

Bug#802914: xscreensaver: upstream 5.34 fixes crash

On Sun, Oct 25, 2015 at 7:41 AM, Salvatore Bonaccorso wrote: > On Sat, Oct 24, 2015 at 11:59:38PM -0400, Michael Gilbert wrote: >> A new upstream version is out that fixes a crash while swapping >> monitors, which has security implications. Here is also a debdiff for stable (jessie-security)

Bug#696656: xscreensaver: Turkish translation for the package

For reference, this link explains the translation work flow: https://lists.debian.org/debian-i18n/2010/09/msg00054.html (taken from https://launchpad.net/bugs/1424413) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact

Bug#304406: xscreensaver: New Login button without gdmflexiserver

xscreensaver ships a xscreensaver-wrapper.sh that detects gdm, lightdm and kdm. So we just need the desktop environments to use this wrapper instead of calling xscreensaver-daemon directly, then we can remove the gdmflexiserver default for newLoginCommand. However I don't know what the status is

Bug#681860: xscreensaver-data should recommends vs. depends on libwww-perl

Just to summarize this for later: - Upstream doesn't use url by default, so it will run fine without libperl-www - Debian, in its branding patches, sets url (for planet.debian.org) as default so some tools will complain if libperl-www is not installed. If we modify our branding patches to use

Bug#661174: xscreensaver: should recommend libgnomeui-0

tags 661174 pending thanks xscreensaver-demo starts with a warning about libgnome.so: $ xscreensaver-demo (xscreensaver-demo:23331): libglade-WARNING **: Could not load support for `gnome': libgnome.so: cannot open shared object file: No such file or directory This can be solved

Bug#696656: xscreensaver: Turkish translation for the package

Hi Oguz, Thanks for this contribution. Unfortunately the report has fallen through the cracks. This is a dark hole for localization issues. Would you please consider updating the translation for xscreensaver 5.33 and submit it upstream? Best regards, Tormod PS. The end of your file contains

Bug#778470: xscreensaver: Add support for lighdm new login feature.

Good question. Well, I see 2 ways: 1st. Analyze environment Pro. easy fast tells us about current running dm Cons. As there is no direct info, it's some kind of hack (and dm authors could break this in the future) 2nd. Analyze system settings as

Bug#774539: xscreensaver-data-extra: Too many icons showing in GNOME Shell Applications Menu

tags 774539 pending thanks When running GNOME Shell and xscreensaver modules such as xscreensaver-data- extra and others are added to xscreensaver, the GNOME Application Menu list gets cluttered up with useless icons for each of the many Display Modes that are installed. I think this will be

Bug#678279: with newer X, keyboard input does not reset xscreensaver idle timer

Since I upgraded a bunch of things (X, gtk, ...) xscreensaver sometimes locks my screen when I don't touch the mouse for a few minutes, even if I use the keyboard constantly. That's rather annoying, since at that moment I'm typically in the middle of typing a rather long text. Thanks for

Bug#778470: xscreensaver: Add support for lighdm new login feature.

Please add support for new login feature lightdm (dm-tool) provide. Patch os attached. Hi, thanks for the report and patch. But if both dm-tool and gdmflexiserver are installed on the machine, how do you know which one should be called? Is there a way to know we are in a session started by

Bug#778470: xscreensaver: Add support for lighdm new login feature.

Please add support for new login feature lightdm (dm-tool) provide. Patch os attached. Hi, thanks for the report and patch. But if both dm-tool and gdmflexiserver are installed on the machine, how do you know which one should be called? Is there a way to know we are in a session started by

Bug#767019: xscreensaver: postinst overwrites /etc/X11/app-defaults/XScreenSaver without asking

tags 767019 pending thanks On Mon, Jan 26, 2015 at 7:45 PM, Alex Goebel wrote: On Sat, Dec 20, 2014 at 9:02 AM, Michael Gilbert wrote: if [ -L /etc/X11/app-defaults/XScreenSaver ]; then if [ $(readlink /etc/X11/app-defaults/XScreenSaver) = XScreenSaver-nogl -o \

Bug#766880: xscreensaver screensaver don't appear in mate-screensaver

tags 766880 pending thanks Mailing thread continued here: https://lists.debian.org/debian-desktop/2015/07/msg4.html -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#180775: xscreensaver-gl: Starwars does not show accentuated letters

tags 180775 pending thanks Accuentuated letters are not shown in the starwars hack. Ex : /usr/lib/xscreensaver/starwars -program echo làlélèlô gives only vertical lines for the ls. This makes fortune-fr jokes much harder to read : ) Thanks for your bug report. It seems the -program option

Bug#678279: with newer X, keyboard input does not reset xscreensaver idle timer

severity 678279 normal thanks Since I upgraded a bunch of things (X, gtk, ...) xscreensaver sometimes locks my screen when I don't touch the mouse for a few minutes, even if I use the keyboard constantly. That's rather annoying, since at that moment I'm typically in the middle of typing a

Bug#788314: zyne: Zyne is not starting due to import error (No module named zyne.Resources.variables)

I think sudo touch /usr/lib/python2.7/dist-packages/zyne/__init__.py worked around this for me. (Can't get sound though.) Regards, Tormod -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#766880: xscreensaver screensaver don't appear in mate-screensaver

Posted for broader discussion here: https://lists.debian.org/debian-desktop/2015/06/msg0.html -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#766880: xscreensaver screensaver don't appear in mate-screensaver

On Sat, Jun 20, 2015 at 4:59 PM, Jonas Smedegaard wrote: I would guess that GNOME uses gnome-screensaver instead and therefore has no use (other than indirectly) for xscreensaver. But I don't know, Actually GNOME was the original reason for shipping the desktop files. The xscreensaver daemon

Bug#766880: xscreensaver screensaver don't appear in mate-screensaver

On Sun, May 24, 2015 at 12:48 PM, Jonas Smedegaard wrote: Please, instead of whitelisting known relevant environments, blacklist known irrelevant ones. I.e. replace thise line: OnlyShowIn=XFCE; with (most likely, as a start) this: NotShowIn=KDE;GNOME; Jonas, Your suggestion makes

Bug#767019: xscreensaver: postinst overwrites /etc/X11/app-defaults/XScreenSaver without asking

On Sat, Dec 20, 2014 at 9:02 AM, Michael Gilbert wrote: if [ -L /etc/X11/app-defaults/XScreenSaver ]; then if [ $(readlink /etc/X11/app-defaults/XScreenSaver) = XScreenSaver-nogl -o \ $(readlink /etc/X11/app-defaults/XScreenSaver) = XScreenSaver-gl]; then

Bug#770181: xscreensaver: Fails to properly lock and shut off screen in multiple scenarios

On Wed, Nov 19, 2014 at 9:29 PM, Jamie Zawinski wrote: On Nov 19, 2014, at 5:31 AM, John Goerzen wrote: 3) When moving the mouse or pressing a key to wake up the screen and unlock it, frequently the previous content of the screen will show up for a few seconds before it is blanked and the

Bug#767031: xscreensaver-gl: winduprobot often (or even always?) segfaults

Hello, I noticed a number of log messages like the following on the boxes I use: [ 8368.413929] winduprobot[8149]: segfault at c01465130 ip 0041136a sp 7fffa56dbf08 error 4 in winduprobot[40+9c000] After finding out that winduprobot is a newly added hack shipped in

Bug#766880: Processed: Re: Bug#766880: xscreensaver screensaver don't appear in mate-screensaver

--- screensavers-desktop.stub.old 2014-10-26 15:23:44.826806788 +0100 +++ screensavers-desktop.stub 2014-10-26 15:24:39.322497990 +0100 @@ -2,4 +2,4 @@ Terminal=false Type=Application Categories=Screensaver; -OnlyShowIn=GNOME; +OnlyShowIn=GNOME;MATE; This change results in all xscreensaver

Bug#767019: xscreensaver: postinst overwrites /etc/X11/app-defaults/XScreenSaver without asking

On Mon, Oct 27, 2014 at 6:42 PM, Bjørn Mork wrote: Package: xscreensaver Version: 5.30-1+b1 Severity: serious Justification: Policy 10.7.3 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This part of xscreensaver.postinst overwrites any locally modified /etc/X11/app-defaults/XScreenSaver

Bug#757448: Trademark status

tags 757448 +moreinfo severity 757448 important thanks On Wed, Aug 13, 2014 at 7:03 PM, Wouter Verhelst wrote: On Sat, Aug 09, 2014 at 10:46:28AM +0900, mejiko wrote: Pong: http://tsdr.uspto.gov/#caseNumber=76148525caseType=SERIAL_NOsearchType=statusSearch Matrix:

Bug#763972: Please update to stm32flash 0.4

On Mon, Oct 6, 2014 at 8:36 AM, Andrew Shadura wrote: Hello, On Sat, 4 Oct 2014 13:49:16 +0200 Tormod Volden debian.tor...@gmail.com wrote: We have released stm32flash and would appreciate to see it in before the freeze. I am filing this bug because I am not sure the watch file works

Bug#763972: Please update to stm32flash 0.4

Oh, and if you spin a -2 version, can you please also update the package description with the features I2C support and GPIO signalling? Tormod -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#763972: Please update to stm32flash 0.4

Package: stm32flash Severity: wishlist Dear maintainer, We have released stm32flash and would appreciate to see it in before the freeze. I am filing this bug because I am not sure the watch file works with the code.google repository. Note that we have dropped the protocol.pdf so it should now

Bug#696866: 0.7 and git build fine

retitle 696866 Update to dfu-util 0.8 thanks I have released upstream dfu-util 0.8 and would love to see it in Debian soon. BTW, there is a new dfuse-pack.py utility in the tarball, but it is not installed by make install. Maybe you can put it in /usr/bin or somewhere else like docs/examples.

Bug#745659:

Xavier, what is your window manager? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#640069: ITP: stm32flash -- Flash program for the ST STM32 ARM Cortex-M3 using the ST bootloader

I have released stm32flash 0.3 today. Link to tarball at https://code.google.com/p/stm32flash/ I hope to see it in Debian soon! Thanks for your cooperation. Cheers, Tormod -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact

Bug#738621: wishlist: Display current active screensaver in the password dialog window

On Tue, Feb 11, 2014 at 12:09 PM, Adrian Immanuel Kiess wrote: It would be very nice, if the password display window could list the currently active screensaver of xscreensaver. Another idea would be an option in the preferences to display it maybe under the FPS text or nearby the FPS text.

Bug#640069: ITP: stm32flash -- Flash program for the ST STM32 ARM Cortex-M3 using the ST bootloader

I have become the official stm32flash maintainer, so upstream is alive again. There is now also a man page thanks to Antonio Borneo. I plan to make a 0.3 release in a few weeks. We will maybe move away from code.google.com because soon they won't support downloads any longer. Cheers, Tormod --

Bug#593303: acpi-support: suspend in half the time - background xscreensaver

reopen 593303 thanks xscreensaver-command sleeping three times for a second each. Here's a patch to execute those sleeps in the background and half the time to get the system suspended using the hot keys. It could be executed in another half the time, but I haven't tracked that down.

Bug#726002: xserver-xorg-video-mga: Dualheading using 1.6.2 segfaults

On Thu, Oct 17, 2013 at 5:34 AM, Robert Jacobs wrote: The right solution is for someone to modernize the 1.9.100 branch from six years ago, and give the MGA driver EXA support. But IIRC Brice Goglin had a number of problems that showed up in that branch. (e.g. debian 457502, 452223, 488762,

Bug#726002: xserver-xorg-video-mga: Dualheading using 1.6.2 segfaults

On Thu, Oct 17, 2013 at 9:43 AM, Robert Jacobs wrote: I'm happy to count as a Tested-by, and as far as I can tell the patch 02_tentatively_unbreak_dual_head.diff looks sane to me. I'm unfortunately not very familiar with the Xorg low-level internals to do any kind of comparison to any other

<    1   2   3   4   5   >