Bug#962342: libexplain-dev: missing dependency on libacl1-dev

2020-06-06 Thread Lars Stoltenow
Package: libexplain-dev
Version: 1.4.D001-10
Severity: normal

Dear Maintainer,

the libexplain-dev package should possibly have a dependency on libacl1-dev,
as its headers use the sys/acl.h header that is provided by it.

More specifically, compiling a program with (not much more than)
  #include 
fails with
  In file included from /usr/include/libexplain/libexplain.h:38,
   from expl.c:12:
  /usr/include/libexplain/acl_from_text.h:33:10: fatal error: sys/acl.h: No 
such file or directory
   #include 
^~~

By installing libacl1-dev, the error is resolved and the package can be used
as expected.


-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.17.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libexplain-dev depends on:
ii  libexplain51  1.4.D001-10
ii  lsof  4.91+dfsg-1

libexplain-dev recommends no packages.

libexplain-dev suggests no packages.

-- no debconf information



Bug#882270: systemd-logind crashes when closing lid after "systemctl mask sleep.target"

2017-11-20 Thread Lars Stoltenow
Package: systemd
Version: 235-3
Severity: normal

Dear Maintainer,

I want to be able to configure if my laptop should suspend when closing the
lid. Because I do not want to kill the X session for this, changing logind.conf
and restarting logind is not an option. Therefore, I set
HandleLidSwitch=suspend and HandleLidSwitchDocked=suspend and want to manually
disable suspend using "systemctl mask sleep.target suspend.target".

It works insofar that when closing the lid, the laptop doesn't suspend,
but logind crashes multiple times in rapid succession. journalctl:

Nov 20 21:39:26 litterbox systemd-logind[10697]: Lid closed.
Nov 20 21:39:26 litterbox systemd-logind[10697]: Suspending...
Nov 20 21:39:26 litterbox systemd-logind[10697]: Assertion 'signal_name[w]' 
failed at ../src/login/logind-dbus.c:1495, function send_prepare_for(). 
Aborting.
[...unrelated kernel log entries...]
Nov 20 21:39:26 litterbox systemd[1]: systemd-logind.service: Main process 
exited, code=killed, status=6/ABRT
Nov 20 21:39:26 litterbox systemd[1]: systemd-logind.service: Failed with 
result 'signal'.
Nov 20 21:39:26 litterbox systemd[1]: systemd-logind.service: Service has no 
hold-off time, scheduling restart.
Nov 20 21:39:26 litterbox systemd[1]: systemd-logind.service: Scheduled restart 
job, restart counter is at 2.
Nov 20 21:39:26 litterbox systemd[1]: Stopped Login Service.
Nov 20 21:39:26 litterbox systemd[1]: Starting Login Service...
Nov 20 21:39:26 litterbox systemd[1]: Started Login Service.
Nov 20 21:39:26 litterbox systemd-logind[10892]: New seat seat0.
Nov 20 21:39:26 litterbox systemd-logind[10892]: Watching system buttons on 
/dev/input/event6 (Power Button)
Nov 20 21:39:26 litterbox systemd-logind[10892]: Watching system buttons on 
/dev/input/event4 (Power Button)
Nov 20 21:39:26 litterbox systemd-logind[10892]: Watching system buttons on 
/dev/input/event3 (Lid Switch)
Nov 20 21:39:26 litterbox systemd-logind[10892]: Watching system buttons on 
/dev/input/event5 (Sleep Button)
Nov 20 21:39:26 litterbox systemd-logind[10892]: Watching system buttons on 
/dev/input/event1 (Logitech USB Receiver)
Nov 20 21:39:26 litterbox systemd-logind[10892]: Watching system buttons on 
/dev/input/event2 (Logitech USB Receiver)
Nov 20 21:39:26 litterbox systemd-logind[10892]: Watching system buttons on 
/dev/input/event0 (AT Translated Set 2 keyboard)
Nov 20 21:39:26 litterbox systemd-logind[10892]: New session 4 of user penma.
Nov 20 21:39:26 litterbox systemd-logind[10892]: New session 1 of user penma.
Nov 20 21:39:26 litterbox systemd-logind[10892]: Suspending...
Nov 20 21:39:26 litterbox systemd-logind[10892]: Assertion 'signal_name[w]' 
failed at ../src/login/logind-dbus.c:1495, function send_prepare_for(). 
Aborting.
Nov 20 21:39:26 litterbox systemd[1]: systemd-logind.service: Main process 
exited, code=killed, status=6/ABRT
Nov 20 21:39:26 litterbox systemd[1]: systemd-logind.service: Failed with 
result 'signal'.
Nov 20 21:39:26 litterbox systemd[1]: systemd-logind.service: Service has no 
hold-off time, scheduling restart.
[...continues multiple times until...]
Nov 20 21:39:27 litterbox systemd[1]: systemd-logind.service: Scheduled restart 
job, restart counter is at 7.
Nov 20 21:39:27 litterbox systemd[1]: Stopped Login Service.
Nov 20 21:39:27 litterbox systemd[1]: systemd-logind.service: Start request 
repeated too quickly.
Nov 20 21:39:27 litterbox systemd[1]: systemd-logind.service: Failed with 
result 'signal'.
Nov 20 21:39:27 litterbox systemd[1]: Failed to start Login Service.

after which the whole X session goes down because

[  1689.396] (EE)
Fatal server error:
[  1689.396] (EE) systemd-logind disappeared (stopped/restarted?)
[  1689.396] (EE)
[  1689.396] (EE)
Please consult the The X.Org Foundation support at http://wiki.x.org for help.

The crashes are reproducible when the events above are masked, and they
also reliably disappear after unmasking said events.

I feel that logind should not crash in this situation, even if there happens to
be a better way to prevent suspend from happening. (For what I'm trying to
achieve right now, "systemd-inhibit --what=handle-lid-switch cat" is good
enough and doesn't crash logind)

I run X via startx with no desktop environment (only dwm).


-- Package-specific info:

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages systemd depends on:
ii  adduser 3.113+nmu3
ii  libacl1 2.2.52-2
ii  libapparmor12.10-2+b2
ii  libaudit1   1:2.4.5-1
ii  libblkid1   2.29-1
ii  libc6   2.24-7
ii  libcap2 1:2.24-12
ii  libcryptsetup4  2:1.7.0-2
ii  libgcrypt20 1.7.5-3
ii  libgpg-error0   1.21-1
ii  libidn111.33-1
ii  

Bug#639163: avahi-daemon is polluting my system log

2015-11-06 Thread Lars Stoltenow
Unfortunately the issue is not fixed. At 0.6.32~rc+dfsg-1, avahi-daemon
still fills syslog with messages.



Bug#783254: imlib2: cannot rescale+render images 32767 width

2015-04-24 Thread Lars Stoltenow
Source: imlib2
Severity: normal

Dear Maintainer,

rendering an imlib image to a X11 window while simultaneously scaling it, causes
a crash when the image width is  32768 (or 32767 or so).

The bug originally appeared when using feh to view a wide PNG image in
fullscreen (causing it to be downsampled while rendering).

The (apparent) cause of the crash is the __imlib_CalcXPoints calculating
offsets (into image data I think) incorrectly. For not-so-wide images, all
offsets are positive, which makes sense. For wider images, all but the first
offsets are negative, which subsequently causes out-of-bounds memory accesses
and a crash.

I guess this is because the calculations happen with int = 32 bit (even on
amd64). Several intermediate calculations shift left by 16 - sign bit flips
for  32768 - calculated offset becomes negative. (The resulting value is
right shifted by 16 later again, but then of course it is still negative).

A first quick fix that doesn't appear to completely fall apart is attached.
It appears to fix the problem, however I am not sure if there are other parts
that should also use 64 bit numbers.

-- System Information:
Debian Release: 8.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
--- a/src/lib/scale.c	2013-12-22 05:20:31.0 +0100
+++ b/src/lib/scale.c	2015-04-24 20:29:59.623533552 +0200
@@ -112,7 +112,7 @@
if (dw  (b1 + b2))
  {
 val = (b1  16);
-inc = ((sw - b1 - b2)  16) / (dw - b1 - b2);
+inc = ((long long)(sw - b1 - b2)  16) / (dw - b1 - b2);
 for (i = 0; i  (dw - b1 - b2); i++)
   {
  p[j++] = (val  16);


Bug#783254: imlib2: cannot rescale+render images 32767 width

2015-04-24 Thread Lars Stoltenow
On Fri, Apr 24, 2015 at 08:36:26PM +0200, Lars Stoltenow wrote:
 The bug originally appeared when using feh to view a wide PNG image in
 fullscreen (causing it to be downsampled while rendering).

Forgot to provide a quick way of testing:

convert -size 32770x100 xc:white test.png
feh --fullscreen test.png


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#755172: acpi-support: combination of suspend and screen locking broken with xtrlock

2014-07-18 Thread Lars Stoltenow
Package: acpi-support
Version: 0.142-1
Severity: normal

When using xtrlock for screen locking, the screenblank script does not work
properly: The screen is locked, however, suspend is not initiated. After
entering password and unlocking the screen, the system is immediately
suspended.

This is probably because the /usr/share/acpi-support/screenblank script
does not invoke xtrlock in background. Because xtrlock (unlike the other
screensaver commands) blocks and does not return until the password is entered,
the /etc/acpi/sleep_suspend.sh only executes pm-suspend after the screen has
been unlocked again.

Proposed fix: Something like

su $XUSER -s /bin/sh -c /usr/bin/xtrlock 

in the screenblank script.


-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages acpi-support depends on:
ii  acpi-support-base  0.142-1
ii  acpid  1:2.0.22-3
ii  lsb-base   4.1+Debian13
ii  pm-utils   1.4.1-15
ii  x11-xserver-utils  7.7+3

Versions of packages acpi-support recommends:
ii  acpi-fakekey  0.141-2
ii  rfkill0.5-1

Versions of packages acpi-support suggests:
ii  radeontool1.6.3-1
ii  vbetool   1.1-3
ii  xinput1.6.1-1
ii  xscreensaver  5.26-1
ii  xtrlock   2.6

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#641580: dizzy: should fail when no display can be used

2011-09-20 Thread Lars Stoltenow
Hello,

the lack of error handling is indeed a bug in dizzy, and it will be fixed.

However, the issue of the display being borked is not caused by dizzy. This
also happens with other apps. Tested with supertux. Because the X server
can't be used, SDL tries to use the framebuffer driver instead, but that
fails at some stage (no OpenGL, or maybe something else). That's why the
display turns black.





-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#572485: xscreensaver: should not hardcode screenhacks list

2010-03-04 Thread Lars Stoltenow
Package: xscreensaver
Version: 5.10-7
Severity: wishlist


The configuration dialog only shows screenhacks that are either hardcoded
inside the xscreensaver binary, or manually entered into ~/.xscreensaver.
This means there is no easy way to make packages that provide additional
screenhacks.

Currently there's the rss-glx package which has to use an awful hack
to make the screensavers work: rss_glx-install, a script that has to be
run by *every* user on the system manually. Not user friendly at all!

The package should instead do what is suggested by one way of interpreting
/usr/share/xscreensaver/config/README:

 This directory contains XML files that describe each of the screenhacks;
 the per-hack user interface is constructed based on the things in these
 files.  The files are loaded at run-time by xscreensaver-demo (also
 known as the Control Center screensaver properties capplet.)

It shouldn't just read the xml files at runtime, but also the contents
of the directory, so that additional screenhack packages can just dump
their xml file into /usr/share/xscreensaver/config and just work.

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages xscreensaver depends on:
ii  libatk1.0-0  1.28.0-1The ATK accessibility toolkit
ii  libc62.10.2-6Embedded GNU C Library: Shared lib
ii  libcairo21.8.10-2The Cairo 2D vector graphics libra
ii  libfontconfig1   2.8.0-2 generic font configuration library
ii  libfreetype6 2.3.11-1FreeType 2 font engine, shared lib
ii  libglade2-0  1:2.6.4-1   library to load .glade files at ru
ii  libglib2.0-0 2.22.4-1The GLib library of C routines
ii  libgtk2.0-0  2.18.7-1The GTK+ graphical user interface 
ii  libice6  2:1.0.6-1   X11 Inter-Client Exchange library
ii  libpam0g 1.1.1-2 Pluggable Authentication Modules l
ii  libpango1.0-01.26.2-1Layout and rendering of internatio
ii  libsm6   2:1.1.1-1   X11 Session Management library
ii  libx11-6 2:1.3.3-1   X11 client-side library
ii  libxext6 2:1.1.1-2   X11 miscellaneous extension librar
ii  libxinerama1 2:1.1-2 X11 Xinerama extension library
ii  libxml2  2.7.6.dfsg-2+b1 GNOME XML library
ii  libxmu6  2:1.0.5-1   X11 miscellaneous utility library
ii  libxpm4  1:3.5.8-1   X11 pixmap library
ii  libxrandr2   2:1.3.0-3   X11 RandR extension library
ii  libxrender1  1:0.9.5-1   X Rendering Extension client libra
ii  libxt6   1:1.0.7-1   X11 toolkit intrinsics library
ii  libxxf86vm1  1:1.1.0-2   X11 XFree86 video mode extension l
ii  xscreensaver-data5.10-7  data files to be shared among scre

Versions of packages xscreensaver recommends:
ii  libjpeg-progs  8-2.1 Programs for manipulating JPEG fil
ii  perl [perl5]   5.10.1-11 Larry Wall's Practical Extraction 
ii  wamerican [wordlist]   6-3   American English dictionary words 
ii  xli1.17.0+20061110-3 command line tool for viewing imag

Versions of packages xscreensaver suggests:
ii  elinks [www-browser]0.12~pre5-2  advanced text-mode WWW browser
pn  fortune none   (no description available)
ii  iceweasel [www-browser] 3.5.8-1  Web browser based on Firefox
ii  lynx-cur [www-browser]  2.8.8dev.2-1 Text-mode WWW Browser with NLS sup
pn  qcam | streamer none   (no description available)
ii  w3m [www-browser]   0.5.2-4  WWW browsable pager with excellent
pn  xdaliclock  none   (no description available)
pn  xfishtank   none   (no description available)
ii  xscreensaver-gl 5.10-7   GL(Mesa) screen hacks for xscreens

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#563852: thinkpad_acpi: LED restriction does not add safety, please enable CONFIG_THINKPAD_ACPI_UNSAFE_LEDS

2010-01-05 Thread Lars Stoltenow
Package: linux-2.6
Severity: normal


The kernel guys decided it would be a good idea to cripple thinkpad_acpi by
not allowing the state of some hardware LEDs to be set, like the dock and
battery. They say that allowing these LEDs to be set can make users perform
actions dangerous to the hardware because firmware information might get lost.

I think that this change does not add safety at all, because the unaware
user which they reference in the docs doesn't play around with the LEDs anyway.
The LED devices are root writable only anyway, so evil guy wanting to destroy
other people's laptop could just load a fixed kernel module to control the
LEDs. The option is just a PITA for people that want to control the LEDs for
their own purposes, because they have to rebuild kernel modules. (No it's not
even a module load option like with the fan control switch, even though doing
funny things with the fan can cause much more damage to the hardware than
doing things to the LED.)

So there is no advantage in restricting access to the LEDs and therefore I'd
be thankful if future versions of the Debian kernel were built with
CONFIG_THINKPAD_ACPI_UNSAFE_LEDS enabled.

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#558417: tar: is slow on large files because it doesn't lseek

2009-11-28 Thread Lars Stoltenow
Package: tar
Version: 1.22-1
Severity: normal

When running tar tf or tar xf on a large tarball containing few large files,
which is stored on a slow disk, GNU tar becomes incredibly slow.

The reason is: GNU tar doesn't lseek() to the offset where the next file would
start, but rather read()s through the file contents and throws them away.

Busybox tar and libarchive's tar don't show this behavior and call lseek()
instead, which greatly speeds tar up (either while listing files, or when
only extracting parts of the archive).

This happens on all recent versions of GNU tar on all systems.


-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.29-2-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages tar depends on:
ii  libc6 2.9-12 GNU C Library: Shared libraries

tar recommends no packages.

Versions of packages tar suggests:
ii  bzip2 1.0.5-1high-quality block-sorting file co
pn  ncompress none (no description available)

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#543913: tar tf uses read() instead of lseek(), making it slow

2009-08-27 Thread Lars Stoltenow
Package: tar
Version: 1.20-1
Severity: normal

When running tar tf on a large tarball containing few large files, tar
becomes incredibly slow. The reason for this is that tar issues many
read()s to skip the file content, but as it doesn't need the content, it
throws it away. GNU tar could just use lseek() like libarchive and busybox
do.

Also a problem is extracting only one file from said tarball, where the
other files do not need to be read for just that one to be extracted.

The problem exists on all versions of GNU tar and was confirmed to exist
on at least all versions starting from etchthe one shipped with Etch.

-- System Information:
Debian Release: 5.0.2
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26-2-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages tar depends on:
ii  libc6 2.9-12 GNU C Library: Shared libraries

tar recommends no packages.

Versions of packages tar suggests:
ii  bzip2 1.0.5-2high-quality block-sorting file co
pn  ncompress none (no description available)

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#523072: /usr/bin/urxvt: can't select line by tripleclick in a word with umlauts

2009-04-08 Thread Lars Stoltenow
Package: rxvt-unicode
Version: 9.05-1+lenny1
Severity: normal
File: /usr/bin/urxvt

Triple clicking into the terminal normally selects the whole line. When
the pointer is over a word with umlauts (possibly applies to all non-ASCII
chars), one can click like mad, only the umlaut word is selected. The line
never gets selected (except when hovering an ASCII-only word).

-- System Information:
Debian Release: 5.0
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages rxvt-unicode depends on:
ii  base-passwd3.5.19Debian base system master password
ii  libafterimage0 2.2.8-2   imaging library designed for After
ii  libc6  2.7-18GNU C Library: Shared libraries
ii  libcairo2  1.6.4-7   The Cairo 2D vector graphics libra
ii  libfontconfig1 2.6.0-3   generic font configuration library
ii  libfreetype6   2.3.7-2   FreeType 2 font engine, shared lib
ii  libgcc11:4.3.2-1.1   GCC support library
ii  libglib2.0-0   2.16.6-1  The GLib library of C routines
ii  libgtk2.0-02.12.11-4 The GTK+ graphical user interface 
ii  libice62:1.0.4-1 X11 Inter-Client Exchange library
ii  libjpeg62  6b-14 The Independent JPEG Group's JPEG 
ii  libperl5.105.10.0-19 Shared Perl library
ii  libpng12-0 1.2.27-2  PNG library - runtime
ii  librsvg2-2 2.22.2-2lenny1SAX-based renderer library for SVG
ii  libsm6 2:1.0.3-2 X11 Session Management library
ii  libtiff4   3.8.2-11  Tag Image File Format (TIFF) libra
ii  libx11-6   2:1.1.5-2 X11 client-side library
ii  libxext6   2:1.0.4-1 X11 miscellaneous extension librar
ii  libxft22.1.12-3  FreeType-based font drawing librar
ii  libxrender11:0.9.4-2 X Rendering Extension client libra
ii  ncurses-base   5.7+20081213-1basic terminal type definitions
ii  zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime

rxvt-unicode recommends no packages.

Versions of packages rxvt-unicode suggests:
pn  ttf-bitstream-veranone (no description available)

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org