VA, please provide a tested patch against our VCS
https://salsa.debian.org/debian/xscreensaver
thanks
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 to
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 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
uploaded
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 frequen
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
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 here
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 ver
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
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 als
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 inter
I think this is solely through the build dependency on libglade2-dev
so this will be solved by xscreensaver getting rid of this dependency
(bug #967892) or by libglade2 getting rid of its python dependency
(bug #895517):
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895517#14
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:
>
> Jen
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.
To
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 mem
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
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 build should abort. In c
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 i
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 wh
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
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" -
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)" =
>> "XScreen
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/XScre
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=76148525&caseType=SERIAL_NO&searchType=statusSearch
>>
>>
>> Matrix:
>>
>> http:
On Tue, Sep 3, 2013 at 4:24 AM, Brandon Simmons wrote:
> Is anyone maintaining this package? What can I do to help?
>
Hi Brandon,
The Debian intel-gpu-tools packaging is maintained at
http://git.debian.org/?p=pkg-xorg/app/intel-gpu-tools.git
If you can provide patches against this tree it would b
> In file included from src/mainwindow.h:52:0,
> from src/bodypropertyeditor.cpp:43:
> src/glwidget.h:198:3: error: 'GLUquadricObj' does not name a type
This identifier is defined in glu.h, and adding #include to
ElmerGUI/Application/src/glwidget.h made it compile. Then it failed
> Package: linux-wlan-ng-source
> Version: 0.2.9+dfsg-4
> Severity: grave
>
> These modules fail to build against Linux 3.1:
>
> make[5]: Entering directory `/usr/src/linux-headers-3.1.0-1-amd64'
> /usr/src/linux-headers-3.1.0-1-common/arch/x86/Makefile:81: stack protector
> enabled but no compile
On Mon, Oct 3, 2011 at 4:13 PM, Tormod Volden wrote:
> also fixed this. I will have to ping him again. I should also push it
> to a branch of my own so that you can see what I have done already.
http://cgit.freedesktop.org/~tormod/radeontool/
--
To UNSUBSCRIBE, email to debian-bugs-r
On Wed, Sep 28, 2011 at 1:52 PM, Jonathan Nieder wrote:
> Didier Raboud wrote:
>
>>> radeontool.c: In function 'fatal':
>>> radeontool.c:42:5: error: format not a string literal and no format
>>> arguments [-Werror=format-security]
>
> Yep, known. The patch below (excluding the hunk patching rade
Yes, it has been on the todo list for some years to get rid of the gdm
build dependency. I guess it is time to do something about it.
(Jose, for your reference, our old conversation on this has subject
"build dep on gdm")
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with
On Sun, Sep 26, 2010 at 6:38 PM, Luca Bruno wrote:
>
> Moreover, the patch for armel should really be sent upstream.
> Would you take care of this (if you are in touch with authors) or should
> I do it?
Hi Luca,
I can not talk for the maintainer, but I will encourage you to submit
the patch on th
severity 534165 normal
thanks
This sounds more like a graphic drivers issue. I can not reproduce it
here. What kind of video card and drivers do you use? Please attach
your Xorg.0.log.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble?
Move the local libssl away the same way we do for libcrypto.
The standard libssl0.9.8 Debian package should work fine.
(Closes: 528029, 537837)
Signed-off-by: Tormod Volden
---
make-googleearth-package |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/make-googleearth
You listed 5 reverted commits above. Did you try to narrow down which
ones you need to revert? Or are they all broken by the
02_temporary_revert_pciaccess.diff?
You can also try to start the server with "sudo strace Xorg" from
another machine, or "sudo gdb Xorg". Sometimes the debugging makes the
Thanks for your report. The problem has also been reported in
https://bugs.launchpad.net/bugs/224065
For now, we'll demote flurry to the -extra package so that it is not
installed by default.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL
On Mon, Mar 3, 2008 at 8:55 PM, Jamie Zawinski <[EMAIL PROTECTED]> wrote:
> I don't understand why you're wasting your time on this. The
> xscreensaver executable is only 200kb.
>
> A good principle is "don't fix what ain't broke".
>
Jamie,
I like to see it as "progress" :) I understand your f
On Mon, Mar 3, 2008 at 3:53 PM, Frans Pop <[EMAIL PROTECTED]> wrote:
> Yes, I understand that, but it is not the point of my report.
For a moment I thought you were the misgruntled kscreensaver
maintainer, that's why I explained everything so carefully :)
> Which is _exactly_ why you should hav
On Mon, Mar 3, 2008 at 3:12 AM, Frans Pop <[EMAIL PROTECTED]> wrote:
>
> After upgrading to this version of xscreensaver I noticed that the KDE
> controlcenter module used to configure the screensaver now lists a
> number of screensavers that no longer work.
>
> Apparently the list of available
On Sun, Mar 2, 2008 at 12:55 PM, Raphael Hertzog <[EMAIL PROTECTED]> wrote:
> > The changelog was wrong! It should be of course:
> > * (From Ubuntu) Split xscreensaver-gl package into:
> > - xscreensaver-gl (standard GL hacks)
> > - xscreensaver-gl-extra (GL hacks not installed by def
Raphael, thanks for the analysis. I will try to fix this ASAP.
Peter, please hold on until a new version is out.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: udev
Version: 0.105-4
Followup-For: Bug #427972
I had the same trouble now that I did an upgrade. My root partition was
originally a large vfat partition that I
cut in two, using gparted IIRC.
This also results in corrupted label names used to identify drives on the
desktop for
inst
Package: linux-wlan-ng-source
Followup-For: Bug #386037
Hmm, I realized the kernel had been compiled with gcc-4.0... So I
installed gcc-4.0 as well, and now it successfully built the modules.
I guess this bug should be something "make sure the kernel compiler
version is installed before buildin
Package: linux-wlan-ng-source
Version: 0.2.4+svn20060808-2
Severity: serious
I just installed the newest weekly cd, and then installed
linux-wlan-ng-source. Using "module-assistant" I am not able to build
the modules.
One thing is that it complains about not finding gcc-4.0 (gcc-4.1 is
instal
45 matches
Mail list logo
