Bug#1009745: My bad.. Just ignore the report.

[Beardy Face]

Dear Maintainer,

Sorry to have bothered you.
This is what comes of switching between installs & doing reinstalls when tired.

I simply forgot the adwaita-qt package was required for the option to be there 
and was using an install with it absent.

Feel free to close this.

Bug#1009745: just to add.. since I forgot.

[Beardy Face]

Those of us on the autistic spectrum can find excessively bright windows within 
a dark screen somewhat painful too deal with.. even if the Fusion style renders 
the text readable.

Bug#1009745: virtualbox: Command-line option --style Adwaita-Dark broken by update.

[Beardy Face]

Package: virtualbox
Version: 6.1.32-dfsg-1~fto11+2
Severity: normal
Tags: a11y
X-Debbugs-Cc: bea...@mxstuff.org

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
apt-get upgrade (apparently downgrade).
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Nothing unusual, simply upgrading to remaain current.
   * What was the outcome of this action?
Error when starting the application stating the style is unavailable.
The interface consequently bacame unreadable with a dark theme selected.
   * What outcome did you expect instead?
The interface to remain useable, rathewr than white text on a white
 background.. which is obviously not possible to read.


*** End of the template - remove these template lines ***


-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (100, 'bullseye-fasttrack'), (100, 
'bullseye-backports-staging')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-13-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: OpenRC (via /run/openrc), PID 1: init
LSM: AppArmor: enabled

Versions of packages virtualbox depends on:
ii  adduser   3.121
iu  iproute2  5.17.0-1
ii  libc6 2.33-7
iu  libcurl3-gnutls   7.82.0-2
ii  libdevmapper1.02.12:1.02.175-2.1
ii  libgcc-s1 12-20220319-1
iu  libgl11.4.0-1
ii  libgsoap-2.8.104  2.8.104-3
ii  liblzf1   3.6-3
ii  libopus0  1.3.1-0.1
ii  libpng16-16   1.6.37-3
iu  libpython3.9  3.9.12-1
ii  libsdl1.2debian   1.2.15+dfsg2-6
ii  libssl1.1 1.1.1n-1
ii  libstdc++612-20220319-1
iu  libvncserver1 0.9.13+dfsg-3
ii  libvpx6   1.9.0-1
iu  libx11-6  2:1.7.5-1
ii  libxcursor1   1:1.2.0-2
iu  libxml2   2.9.13+dfsg-1
iu  libxt61:1.2.1-1
iu  procps2:3.3.17-7+b1
iu  python3   3.10.4-1
iu  python3.9 3.9.12-1
iu  virtualbox-dkms [virtualbox-modules]  6.1.32-dfsg-1+b3
ii  zlib1g1:1.2.11.dfsg-4

Versions of packages virtualbox recommends:
iu  libqt5core5a5.15.2+dfsg-16
iu  libqt5gui5  5.15.2+dfsg-16
iu  libqt5opengl5   5.15.2+dfsg-16
iu  libqt5widgets5  5.15.2+dfsg-16
ii  libxcb1 1.14-3
iu  libxext62:1.3.4-1
iu  virtualbox-qt   6.1.32-dfsg-1+b3

Versions of packages virtualbox suggests:
pn  vde2
iu  virtualbox-guest-additions-iso  6.1.32-1

-- no debconf information

Bug#991880: gdm3: Please support systemd and elogind via the logind virtual packages

[Beardy Face]

On Wed, 4 Aug 2021 12:15:15 +0100 Mark Hindley  wrote:
> Package: gdm3
> Version: 3.38.2.1-1
> Severity: normal
> Tags: patch
>
> Dear colleagues,
>
> Please consider adjusting the gdm3 dependencies to support libpam-elogind as
> well as libpam-systemd via the logind and default-logind virtual packages.
>
> I think I remember it being said (although I cannot now find the reference,
> apologies if I have misremembered) that gdm3 might require systemd --user and
> therefore note work with elogind. However, as far as I can see, operation
> without systemd --user is supported and the gdm3 changelog only mentions a
> requirement for XDG_RUNTIME_DIR which elogind provides.
>
> To confirm this, I have tested gdm3 with libpam-elogind and can find no
> breakage.
>
> I would appreciate you considering the attached patch for the bookworm cycle.
>
> Many thanks.
>
> Mark



I also have tested this, by making an equivs package.. gdm3 certainly works if 
you either build such a package which says libpam-elogind provides 
libpam-systemd & create a symlink such that pam_systemd.so points to 
pam_elogind.so

Though I suspect that changing the code to accept either would be better, since 
the symlink masks similar problems, such as LightDM disabling the power options 
in it's greeter if no such link exists...

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

[Beardy Face]

On Sat, 14 Oct 2017 17:37:26 -0700 Jamie Zawinski  wrote:
> Well,
>
> 5.36 was released on 11 Oct 2016, which, as of the date of this bug report, 
> was 1 year and 3 days old.
>
> 5.37, which contains webcollage updates, was released on 5 July 2017.
>
> The latency with which distros package it up for you is entirely out of my 
> hands.
>
Then perhaps for MAJOR Distros on Distrowatch, possibly the top 5 or so.. (the 
top TWO would catch Debian) you might consider packaging xscreensaver up for 
yourself in the latest incarnation, so that users of THOSE can install the 
latest version without having to bother you or compile it themselves.  Just a 
thought.  When I can afford a new hard drive for the newer hardware I have on 
hand ( which has a faulty one, which I can't swap the PATA one from the box I 
reported this from to a SATA one (incompatible interfaces and wrong form 
factor)) compiling from source will be less of an issue.

I'm not averse to going "Off the reservation" and installing .debs from sources 
outside the "official" repos if suitable packages are available, and I have 
done so, adding an entire repo,  in order to get Debian running a graphical 
environment without systemd, which bogs this old box down (I'm guessing by too 
much parallelism for it) but I guess doing so would remove your excuse to bitch 
about Debian. A distro who's philosophy you clearly dislike.

Alternately and for less effort, switch your licence to something Debian don't 
like and force them to either drop or fork the project. The 
https://en.wikipedia.org/wiki/WTFPL 
v2 licence winds them up and is 
"unacceptable" *to them* even though the Free Software Foundation found it 
compatible.  Then you can ignore Debian users like me completely.

Sadly Distrowatch is incapable of allowing a search for distros based on the 
version of xscreensaver, but I suspect FEW are on the latest version... 
Seriously you need to chill out and let the DEBIAN maintainers WHO I ADDRESSED 
in the first instance handle this rather than getting wound up!

I see the latest version in OUR maintainer's git, so I'm guessing it won't be 
all that long finding its way to testing.. which is where I am.

Your blood pressure will lower if you quit watching the Debian BTS.

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

[Beardy Face]

On Fri, 13 Oct 2017 04:18:29 -0700 Jamie Zawinski  wrote:
> Here's an idea, try running a version of xscreensaver that is not over a year 
> old.
>
> Yes, you have made the mistake of using Debian. I realize that they go out of 
> their way to make that difficult for you. My sympathies.

>
I might also add that on my other box, running Gentoo, which most consider 
pretty cutting-edge and up to date (being a rolling distro) EVEN THERE I had to 
UNMASK a version marked unstable to fix this.. and it's not like I'm running 
Jessie.. the version in Buster is LESS than a year old.. and NO NEWER version 
in SID for me to even attempt back-porting.

Your beef Mr. JWZ is with Debian STABLE which is NOT what I'm running!

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

[Beardy Face]

On Fri, 13 Oct 2017 04:19:14 -0700 Jamie Zawinski  wrote:
> Absolutely not. That is completely antithetical to the purpose of the 
> webcollage screen saver.
>
>
Fair enough, I expect Debian's maintainer will mark this won't fix in due 
course, out of respect for your

position.  I fear there's already sufficient tension between yourself and 
Debian in general.  It was only a suggestion

to maybe make the default output fall in line with the default of the major 
search providers, who have this enabled

by default with turning it off optional.

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

[Beardy Face]

On Fri, 13 Oct 2017 04:18:29 -0700 Jamie Zawinski  wrote:
> Here's an idea, try running a version of xscreensaver that is not over a year 
> old.
>
> Yes, you have made the mistake of using Debian. I realize that they go out of 
> their way to make that difficult for you. My sympathies.

>


Not to appear antagonistic in any way, but what distro would you suggest for a 
Pentuim 2 with limited RAM?

I fear I'm pretty limited in choices if I wish the thing to run at all.  Using 
Debian it's surprisingly functional, with the exception of web browsing.

Your own site advises, and I quote:

If you are using Debian, you should be able to find a more recent version of

XScreenSaver in their so-called "unstable" 
packages. Scroll down, 
find the .deb

package for your architecture, and install that.

Which is exactly what I have done.

I honestly don't fancy compiling from source, I compiled a kernel once on that 
box.

It took a week to complete.

This is doubtless out-of-turn, but have you considered the possibility of 
making .debs available on your site?

I have some sympathy with your position as a developer, I'm sure it's 
frustrating having things you've fixed reported,

Which is why I've used the Debian BTS rather than reporting a bug on your own 
site.

I'm hopeful that having a bug might encourage the version in Sid to get bumped.

Bug#841479: xfce4-power-manager: Interface wider than screen when battery model is a long string.

[Beardy]

Package: xfce4-power-manager
Versions: 1.4.1-1 and 1.4.4-4
Severity: normal
Tags: upstream

Dear Maintainer,

* What led up to the situation?

Attempted to use the package on a General Dynamics / Itronics GD8200
notebook with
an original OEM battery installed.

* What exactly did you do (or not do) that was effective (or ineffective)?

I tried resizing fonts, changing theme, and internet searches for solutions.

* What was the outcome of this action?

The interface cannot be resized to fit on-screen, the screen having a
resolution
set at 1024x768.  I located an archived Debian bug #763713 which I believe
to be
related, the report also contains a proposed patch, which would fix the
issue if
the code is still applicable after the changes made upstream to half fix
this.

However, upstream adopted a different approach which only deals with the
case
where the battery is not recognised creating a long string of characters to
be
rendered on the devices tab, not where the manufacturer's name or model
details 
result in a long string, which is the case for GD/Itronix notebook
batteries.

* Additional information

In the original bug report at:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763713

Message #42 links to additional information requested by upstream at the
time:
https://bugzilla.xfce.org/show_bug.cgi?id=11217#c1

As it is relevant to reproducing the issue, I provide it below:

* Begin paste from terminal *

beardy@GD8200-DB-BL:~$ upower --enumerate
/org/freedesktop/UPower/devices/line_power_AC0
/org/freedesktop/UPower/devices/battery_BAT1
/org/freedesktop/UPower/devices/DisplayDevice
beardy@GD8200-DB-BL:~$ upower -i
/org/freedesktop/UPower/devices/battery_BAT1
  native-path:  BAT1
  vendor:   SMP 
  model:GD8200 Primary Battery  018762
LiIon   SMP 
  serial:   018762  LiIon
SMP 
  power supply: yes
  updated:  Thu 20 Oct 2016 11:31:54 BST (56 seconds ago)
  has history:  yes
  has statistics:   yes
  battery
present: yes
rechargeable:yes
state:   fully-charged  
warning-level:   none
energy:  58.7088 Wh
energy-empty:0 Wh
energy-full: 58.7088 Wh
energy-full-design:  56.4516 Wh
energy-rate: 0.0108 W
voltage: 4.967 V
percentage:  100%
capacity:100%
icon-name:  'battery-full-charged-symbolic'
  History (rate):
1476959514  0.011   fully-charged

* End paste *

In this case the culprit is the long line provided as model, rather than 64
characters generated by an unrecognised battery, however, the basic issue is
identical.  The interface either needs to accommodate or truncate the
information
rather than increasing the window dimensions beyond what fits on a
reasonable
screen.

Upstream believe the issue to be fixed in this version. However, the basic
issue 
that the interface can't accommodate long strings without extending off
screen
is still present the versions cited at the beginning of this report.

-- System Information:
Distributor ID: BunsenLabs
Description:BunsenLabs GNU/Linux 8.5 (Hydrogen)
Release:8.5
Codename:   bunsen-hydrogen
Architecture: x86_64

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

Versions of packages xfce4-power-manager depends on:
ii  libc6 2.19-18+deb8u6
ii  libcairo2 1.14.0-2.1+deb8u1
ii  libdbus-1-3   1.8.20-0+deb8u1
ii  libdbus-glib-1-2  0.102-1
ii  libgdk-pixbuf2.0-02.31.1-2+deb8u5
ii  libglib2.0-0  2.42.1-1+b1
ii  libgtk2.0-0   2.24.25-3+deb8u1
ii  libnotify40.7.6-2
ii  libpango-1.0-01.36.8-3
ii  libpangocairo-1.0-0   1.36.8-3
ii  libupower-glib3   0.99.1-3.2
ii  libx11-6  2:1.6.2-3
ii  libxext6  2:1.3.3-1
ii  libxfce4ui-1-04.10.0-6
ii  libxfce4util6 4.10.1-2
ii  libxfconf-0-2 4.10.0-3
ii  libxrandr22:1.4.2-1+b1
ii  upower0.99.1-3.2
ii  xfce4-power-manager-data  1.4.4-4~bpo8+1

Versions of packages xfce4-power-manager recommends:
ii  libpam-systemd   215-17+deb8u5
pn  xfce4-power-manager-plugins  

xfce4-power-manager suggests no packages.

-- no debconf information


---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

Bug#581342: incorrect and reversed behavior in /etc/init.d/udhcpd restart

[beardy]

Package: udhcpd
Version: 1:1.15.3-1
Severity: important

In the startup script, /etc/init.d/udhcpd, the restart option has the 
stopping and
starting of udhcpd reversed. That is, when '/etc/init.d/udhcpd restart' is run, 
udhcpd
first gets started, then stopped, when it should first stop it, and then start 
it.

To fix, change the following in /etc/init.d/udhcpd:
  restart|force-reload)
$0 start
sleep 1
$0 stop

To the following:
  restart|force-reload)
$0 stop
sleep 1
$0 start


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

Kernel: Linux 2.6.32-5-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 udhcpd depends on:
ii  busybox   1:1.15.3-1 Tiny utilities for small and embed

udhcpd recommends no packages.

udhcpd suggests no packages.

-- Configuration Files:
/etc/default/udhcpd changed [not included]
/etc/udhcpd.conf changed [not included]

-- no debconf information


Regards
//beardy (Tobias)



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