ervlink" != '/etc/runit/runsvdir/current' ]; then
# transition to enable runsvchdir, started in 2.1.2-28, to be
removed in future:
Should do the trick.
--
Jamie Heilman http://audible.transient.net/~jamie/
ntry is:
SV:123456:respawn:/etc/runit/2
I tried the same fix on a old guest I had running systemd and it
worked there too, FWIW.
--
Jamie Heilman http://audible.transient.net/~jamie/
th the
same NIC in it.
and installed Debian 12 it will happen.
This should go to your kernel team I believe as this is an issue with
the kernel driver
module for this NIC.
Any response should be done via email only on this bug please.
Please reply back and confirm that you got this email
Package: linux-image-6.5.0-1-amd64
Version: 6.5.3-1
The r8152 driver is unable to bring up a RTL8156BG device. It's able to
enumerate and present some info, but actually passing packets fails.
I will note that the RTL8156BG firmware is not in the the firmware-realtek
package, unlike its sister
Package: linux-image-6.1.0-11-amd64-unsigned
Version: 6.1.38-4
The cdc_ncm driver is able to enumerate an RTL8156BG device, and glean some
capabilities, but it is unable to fully bring up and utilize it, for unknown
errors. (The systemd log doesn't contain any details, just a generic failed
0 blks, lazy-count=1
realtime =none extsz=4096 blocks=0, rtextents=0
Do we know if the breakage related to bigtime feature?
--
Jamie Heilman http://audible.transient.net/~jamie/
this bug open because pspresent has been
unmaintained for over a decade.
On Sat, 19 Apr 2008 at 00:49, Jamie Wilkinson wrote:
> This one time, at band camp, Brice Goglin wrote:
> >I'm just running pspresent without any parameter except
> >the name of my file (which was cre
Package: src:linux
Version: 6.1.38-2
Severity: important
X-Debbugs-Cc: jamie.bainbri...@gmail.com
Dear Maintainer,
GPD MicroPC and GPD Pocket 3 fail kernel modesetting of the Intel GPU on
Debian v6.1-based kernels. The system performs a hardware lockup and
must be forcibly powered off.
Booting
On 8/7/23 11:46, Carsten Schoenert wrote:
Hello Jamie,
I can't reproduce this issue.
Thank you for the support and sorry to waste your time.
I think the problem is that I didn't have a Primary password set. I set
a primary password, then re-imported my secret key and now it seems to work
Package: thunderbird
Version: 1:115.1.0-1
Severity: normal
Dear Maintainer,
After upgrading to 115.1.0, when sending a message with "Digitally sign"
selected I consistently receive an error that "Sending of the message
failed." (When
just encrypting it works fine.)
The error console reports:
Package: linux-image-6.1.0-9-amd64
Version: 6.1.27-1
Currently, Debian tries to use the cdc_ncm driver with the RTL8156BG, which
fails without useful error. (ifup says the interface doesn't exist, neither
systemd nor dmesg log anything notable, ip addr reports a mac address.)
I think it's
On Tue, 23 May 2023, Paul Gevers wrote:
> > Bug fixes and translations will not be available in bookworm (I am upstream
> > ufw
> > and I cut 0.36.2 specifically for bookworm users).
>
> Please elaborate. It's Full Freeze time. A new upstream needs a lot of
> defending to be considered a
Package: release.debian.org
This has additional information:
https://alioth-lists.debian.net/pipermail/piuparts-devel/2023-May/009566.html
On May 18, 2023 10:33:36 PM Jamie Strandboge wrote:
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags
N' for newer systems
+
+ -- Jamie Strandboge Thu, 18 May 2023 08:45:30 -0500
+
ufw (0.36.1) RELEASED; urgency=medium
* snap packaging updates:
diff -Nru ufw-0.36.1/debian/changelog ufw-0.36.2/debian/changelog
--- ufw-0.36.1/debian/changelog 2022-10-15 05:54:27.0 -0500
+++ ufw-0.36.2
Package: wnpp
Severity: wishlist
* Package name: authentication-milter
Version : 3.20230214
Upstream Contact: Marc Bradshaw
* URL : https://github.com/fastmail/authentication_milter
* License : GPL
Programming Lang: Perl
Description : A Perl
Hi,
Thank you for your report.
By default, ufw adds rules for icmp echo-request to the host *before*
'user rules' in /etc/ufw/before.rules and /etc/ufw/before6.rules. This
is why the 'ufw route deny' rules aren't affecting the ping request
behavior. This is expected behavior.
However, modifying
On Tue, 02 May 2023, Marek Küthe wrote:
> Hello,
>
> thank you for the answer.
>
> I must admit that I was a bit hasty in reporting this error. This error
> occurred when I tried to automate my ufw firewall rules with ansible.
> In doing so, I had unfortunately run several scripts which
On Mon, 01 May 2023, Jamie Strandboge wrote:
> Thank you for the report. If you update hex_decode() in
> /usr/lib/python3/dist-packages/ufw/util.py to use this:
>
> return binascii.unhexlify('%2s' % h).decode("utf-8")
>
> instead of:
>
> return b
On Tue, 02 May 2023, Jamie Strandboge wrote:
> Don't worry about the above, I have a better mitigation to avoid tracing
> back:
> https://git.launchpad.net/ufw/commit/?id=a14ab9777cde6308724164f5c42d368d2a823b3a
Sorry, this is the correct commit:
https://git.launchpad.net/ufw/c
Thanks for this! I plan to add this in the next ufw release and then
push that to Debian with the next upload.
--
Email: ja...@strandboge.com
IRC: jdstrand
Thanks for this! It will be in the next upload.
--
Email: ja...@strandboge.com
IRC: jdstrand
Thank you for the report. If you update hex_decode() in
/usr/lib/python3/dist-packages/ufw/util.py to use this:
return binascii.unhexlify('%2s' % h).decode("utf-8")
instead of:
return binascii.unhexlify(h).decode("utf-8")
Does it resolve the issue for you?
--
Email:
.
Jamie
After testing this further, it appears to already be resolved.
The regular stable kernel (5.10) live or a new install doesn't work,
but the latest bullseye-backport kernel (6.1) works fine without this
iwlwifi.conf
This bug is okay to close.
Many thanks for the quick response and sincere
uldn't
find Ubuntu's history of this package to find why it was included there
in the first place. It's been there for a very long time, at least since
kmod 9 from over 10 years ago.
Given that Ubuntu has shipped this file for so long, the risk of any
regression in Debian seems extremely low.
Thankyou for this part of your reply:
> That's expected: no firmware is deployed at first, the kernel complains,
> d-i notices, and deploys stuff if relevant firmware packages are found,
> and reload the relevant modules. This reloading is what breaks the
> kernel. See upstream bug report:
>
>
With respect, you didn't read the first entry in the bug. There is a
syslog attached, and my syslog is not adding new information.
The mt7912e driver panics on rmmod and the firmware is never loaded. The
first part of the bug describes this. I attempted this workaround in order
to get the
No go for it, thanks.
On Fri, 3 Mar 2023 at 07:27, Adrian Bunk wrote:
> Control: tags 1028454 + patch
> Control: tags 1028454 + pending
>
> Dear maintainer,
>
> I've prepared an NMU for nsscache (versioned as 0.42-2.1) and uploaded
> it to DELAYED/7. Please feel free to tell me if I should
I think I've figured out why we see these errors.
I restarted an Expert mode installation with the latest nightly DI
https://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/
dated
2023-03-07 04:13 size 758M
I ran through the installation to "load installer components from
I am installing on an Asus PN51-E1 which includes the Mediatek MT7921e
wifi device.
I came across this bug while trying to install from
https://cdimage.debian.org/cdimage/bookworm_di_alpha2/ netinst iso on
a USB stick.
I see the same error, but what I was trying to debug when I arrived at
this
but Xfce isn't using it?
Sounds that way! Which is surprising, from reading the code, but not actually a
problem, I guess.
--
Jamie Zawinski • jwz.org • dnalounge.com
If blanking is being inhibited by dbus, the verbose log will look like this:
xscreensaver-systemd: 16:54:30: inhibited by "firefox-esr" (:1.48) with
"video-playing" cookie "0C765C49"
xscreensaver-systemd: 16:54:30: inhibited by "firefox-esr" since Mon Feb 20
16:54:30 2023
xscreensaver-systemd:
a6977ab51c75dfd7/src/xfce-screensaver.c#L233
Is xscreensaver-systemd not running for you?
--
Jamie Zawinski • jwz.org • dnalounge.com
or increase.
Anyway, the bottom line is this: one must call XSync before calling
XSetErrorHandler.
If the GTK devs refuse to add that one line change, well, good luck to you all.
--
Jamie Zawinski • jwz.org • dnalounge.com
oing the effect of GDK_SYNCHRONIZE=1 on the connection used by
> GTK/GDK/xscreensaver. I think this is why GDK_SYNCHRONIZE had no
> effect for you.
This makes sense, thanks. In that case, moving the call to XSynchronize to just
after the call to XtDisplayInitialize should fix that oddit
how it was designed, and that is how it was tested. Trying to install
bits and pieces of it and hoping that it still holds together DEMONSTRABLY does
not work.
--
Jamie Zawinski • jwz.org • dnalounge.com
> Marco and Teoh, out of curiosity, why do you not have xscreensaver-gl
> installed on your systems?
Because you went out of your way to make it trivially easy for someone to drive
their car off the lot with no seat belts or alternator.
--
Jamie Zawinski • jwz.org • dnalounge.com
for everybody,
while solving no problems whatsoever.
Put all of XScreenSaver into one package already, for fuck's sake!
--
Jamie Zawinski • jwz.org • dnalounge.com
Maybe this fixes it?
--- 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 (s->debug_p) fprintf (stderr, "%s: tab changed\n", blurb());
+ populate_prefs_page (s);
pref_changed_cb (GTK_WIDGET
, 0);
A second or two after startup, this will cause an X error. Backtrace will show
a stack that does not include update_subproc_timer or
XSetWindowBackgroundPixmap.
Add XSynchronize (s->dpy, True); before that line. Now the backtrace is as
expected.
--
Jamie Zawinski • jwz.org • dnalounge.com
I meant to say:
1: every call to *XSetErrorHandler* has XSync before it, or
2: every *non-blocking* X11 call inside gdk_x11_display_error_trap_push has
XSync before it.
See also https://github.com/mirror/libX11/blob/master/src/ErrHndlr.c#L38
--
Jamie Zawinski • jwz.org • dnalounge.com
interesting to try
out a few more GTK3 apps and see if the same crash happens there. But it is
obviously timing related, so that might not turn up any examples.
--
Jamie Zawinski • jwz.org • dnalounge.com
On Feb 10, 2023, at 1:50 AM, Tormod Volden wrote:
>
> Wait, this was different:
What is the X error if you let that continue?
--
Jamie Zawinski • jwz.org • dnalounge.com
ose are actually
being called before the X error happens. If so, try putting the XSynchronize
call there. If not... the X error is happening so early that it must be a GTK
or GDK bug?
--
Jamie Zawinski • jwz.org • dnalounge.com
ronize (gdk_x11_get_default_xdisplay(), True);
Wayland isn't involved here, is it? xscreensaver-settings should have printed
warnings if so.
--
Jamie Zawinski • jwz.org • dnalounge.com
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.)
xscreensaver-settings doesn't do anything with focus, though, so this is still
confusing.
--
Jamie Zawinski • jwz.org
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 helpful.
--
Jamie Zawinski • jwz.org • dnalounge.com
Things change. Intentionally. It's better now. Adjust and move on with your
life.
On Jan 6, 2023, at 1:50 AM, Bastian Germann wrote:
>
> But there is a version available at
> https://sourceforge.net/projects/ocr-a-font/ that might be free.
> You can certainly replace it.
This one seems better than that one: https://tsukurimashou.osdn.jp/ocr.php.en
Annoyingly, the name
quantities of data, for example counters being refreshed every few ms
within a month we have seen redis memory usage bloom to 15gb for a dataset
that when exported or saved is only a few hundred mb, the fragmentation is
quite large and is not being cleaned up.
Jamie
You are making this all needlessly complicated. Each distro should have exactly
one xscreensaver package which contains exactly one app-defaults file, with
whatever patches are necessary to that. Which should be "just about none", as
configure should have figured out the correct settings for
No. There should be exactly one XScreenSaver package. So, so many problems have
stemmed from this incomplete, broken installations as a result of this
ridiculous extras-data-extras-gl-extras-extras nonsense. I am decades weary of
hearing about them.
Yes, it is critical that the version of /usr/lib/X11/app-defaults/XScreenSaver
actually correspond to the version of XScreenSaver that is installed. I would
have thought this to be obvious.
If the file does not exist at all, things *should* work ok, but having an old
version there is
Correction, Gallant is in fact BSD licensed:
http://ftp.netbsd.org/pub/NetBSD/NetBSD-current/src/sys/dev/wsfont/gallant12x22.h
False.
Luxi Mono is from Red Hat, I'm sure you've heard of them.
OCRA is an ANSI Standard, and is public domain.
Gallant is a reproduction of the Sun font created by Joshua M. Clulow and
released, as far as I am aware, into the public domain.
What does polkitd do, and why does xscreensaver-systemd fail without it?
I gather it has something to do with "org.freedesktop.PolicyKit1" but I can't
tell what that's for either, and xscreensaver-systemd does not explicitly use
it.
On 2022-12-24 23:22, Richard Hansen wrote:
Control: tags -1 patch
On Sun, 06 Nov 2022 17:58:06 + Jamie Lentin
wrote:
Does the package need updating?
Can you try merge request #7 [1] to see if it works for you? You can
find pre-built .deb files in the CI artifacts [2] for that merge
Package: network-manager-gnome
Version: 1.30.0-2
Severity: normal
Dear Maintainer,
When using nm-applet to connect to a new network, I am properly prompted
for a password, but, after entering the password (either the right one
or the wrong one), nm-applet crashes with the following error:
On 2022-11-11 17:06, Josh Triplett wrote:
I have an external ThinkPad USB keyboard:
$ lsusb | grep -i keyboard
Bus 003 Device 022: ID 17ef:6047 Lenovo ThinkPad Compact Keyboard with
TrackPoint
The Linux kernel exposes a fn_lock attribute in sysfs for this
keyboard:
$ cat
Package: yubico-piv-tool
Version: 2.2.0-1.1
Severity: normal
X-Debbugs-Cc: j...@lentin.co.uk
Dear Maintainer,
I tried following the instructions to set up a Yubikey 5C Nano, firmware 5.4.3,
with PIV:
https://developers.yubico.com/PIV/Guides/SSH_with_PIV_and_PKCS11.html
$ ykman piv reset
Congrats, you are well on your way to understanding that Linux is a trash fire
all the way down!
On Sep 26, 2022, at 11:07 AM, Stefan Monnier wrote:
>
> Oh, it's worse: I installed `picom` which made the opacity slider work,
> but that affects the whole window, whereas I only want the
Less snarkily: none of these things can or will be fixed. Adapting xdaliclock
to more modern toolkits in order to have fully scalable antialiasing and a real
GUI for preferences has some other side effects.
If you want to party like it's 1991, run the code from 1991. It still exists.
Please make sure you grab xscreensaver-6.05.1.tar.gz if you already grabbed the
other one; there was a last minute fix.
T-SCREEN-SAVER extension is under active development. In our universe, that
code almost certainly hasn't been touched since the 90s.
XScreenSaver does not and will not use that server extension.
Install XScreenSaver 6.04 and then "man xscreensaver-systemd".
--
Jamie Zawinski • jwz.org • dnalounge.com
ucking time with
this bullshit.
To Sergio: before you submit a bug report in anything, UPGRADE. Not to the
version that some slacking upstream asshat has made easily available to you,
but to the ACTUAL LATEST VERSION.
https://www.jwz.org/blog/2016/04/i-would-like-debian-to-stop-shipping-
olicyAgent" not
in use
[ kill server ]
xscreensaver-systemd: 02:07:26: X connection closed
Exit 1
--
Jamie Zawinski • jwz.org • dnalounge.com
I don't see how this is possible. When the user logs out, the X server exits.
The display connection that both xscreensaver and xscreensaver-systemd have
open will close with SIGPIPE.
Send logs.
--
Jamie Zawinski • jwz.org • dnalounge.com
ur screen will not auto-lock when you
close the laptop lid.
> Yes, I know the proper fix is to tell firefox to give me an option to not
> inhibit the screensaver
That's not actually the fix, it's just that they are inhibiting it in the
stupidest possible way. Maybe "be less stupid&q
installs *the entire program* as I have designed and tested it.
This requires only a one line change to your dependency list. Your continued
refusal to do this keeps causing problems for everybody, including me.
--
Jamie Zawinski https://www.jwz.org/ https://www.dnalounge.com/
There is no debate about this. It is insecure and irresponsible for
xscreensaver-auth to *not* be setuid root.
Install it setuid root, as it was designed to be, and as "make install" does by
default.
https://www.jwz.org/xscreensaver/faq.html#typeahead
• I used to be able to start typing my password before the unlock
dialog had appeared, but now I have to wait for the prompt.
This is an inevitable consequence of the new security model introduced in
XScreenSaver 6.00. The old
> Why did you switch to it? Or am I misunderstanding that you did?
For the new security model. No other way to increase the privilege separation.
--
Jamie Zawinski https://www.jwz.org/ https://www.dnalounge.com/
.
It is unreasonable to expect an X11 client to hack auto-repeat by itself. This
is a server-side configuration issue.
Also this is far from the only problem with XInput2's keyboard event handling.
See the comments in xscreensaver/driver/xinput.c for a laundry list of its
bugs.
--
Jamie Zawinski
ve no reason to believe that XInput2 has not always behaved that way. You
are noticing it now because XScreenSaver only began using XInput2 as of 6.x.
Stating the problem/annoyance more concisely:
XInput2 does not send auto-repeat press/release events in the same manner as
XNextEvent.
--
Jamie Zawinsk
https://www.jwz.org/xscreensaver/faq.html#typeahead
This is an inevitable consequence of the new security model introduced in
XScreenSaver 6.00. The old behavior will not be returning, so get used to
clicking the mouse or tapping "Shift" before you start typing your password.
Just typing
the whole
line.
--
Jamie Zawinski https://www.jwz.org/ https://www.dnalounge.com/
Well, I'm confused about how it got from "blanking" to "unblanking" without
printing why active_at changed. Please try logging with -vvv -log to make sure
it's printing everything.
--
Jamie Zawinski https://www.jwz.org/ https://www.dnalounge.com/
object has no attribute 'path'
which makes salt on stretch pretty much unusable.
--
Jamie Heilman http://audible.transient.net/~jamie/
I don't understand why you are having trouble logging with 6.02. Did you launch
it as xscreensaver -v -log log.txt?
Investigating this in 5.x will not be helpful, because the flow of control is
completely different with 6.x's new security model.
t;about ten minutes apart" means without you saying actual
timestamps, but that log file shows the screen powering on due to user activity:
> xscreensaver: 18:48:06: user is active (keyboard activity)
> ...
> xscreensaver: 19:25:42: user is active (mouse motion)
--
Jamie Zawinski https://www.jwz.org/ https://www.dnalounge.com/
ts man
> page, I gather xscreensaver-systemd doesn't do anything useful for
> that particular machine.
xscreensaver-systemd is also the mechanism by which most movie players and web
browsers tell XScreenSaver to not blank the screen while a video is playing.
--
Jamie Zawinski https://w
n is installed, then *all* of XScreenSaver
must be installed, or else you get the "zoom" problem and related.
That is how it was designed, and that is how it was tested. Trying to install
bits and pieces of it and hoping it still holds together demonstrably does not
work.
--
Jamie Zawinski https://www.jwz.org/ https://www.dnalounge.com/
ner.
> I think it makes sense for us to not blindly pick whatever is in the user's
> PATH.
You are absolutely 100% wrong. Do not make this change. Many things will
malfunction. Do not make the mistake of forking my program even more than you
already have. That does not go well for any o
nstead of FIVE -- one that installs *all* of XScreenSaver instead of
only bits and pieces and expecting that to still work.
I cannot comprehend why you continue to refuse to implement this trivial
fucking fix.
--
Jamie Zawinski https://www.jwz.org/ https://www.dnalounge.com/
Thanks for the report and patch. Your fix will be in the next upload of
ufw.
--
Email: ja...@strandboge.com
IRC: jdstrand
Thank you for reporting a bug and sorry for only seeing it now.
You mentioned: "From time to time, it hangs on startup so, if you are a
normal user, it is no easy to find the problem." What is hanging on
startup, the ufw oneshot service? This should not be happening. Can you
provide more info on
Thanks for the report and sorry that I only just now saw it.
ufw uses the iptables compat packages and does not use nftables. This
line:
Starting firewall: ufw...
iptables-restore v1.8.7 (nf_tables):
simply means that the 'iptables-restore' command is using the nf_tables
backend. This bug looks
Thanks for the merge!
On Thu, 24 Jun 2021 at 07:09, Sergio Durigan Junior
wrote:
> On Monday, June 21 2021, I wrote:
>
> > Dear maintainer,
> >
> > We're working towards getting OpenLDAP 2.5.5 (already in experimental)
> > ready to start the transition process, and I noticed that nsscache's
> >
this out is if you include all of the output
of -log.
Also, you're running 5.45 instead of 6.00 and if you can't reproduce it in 6.00
there's no point in investigating any further. So try that.
--
Jamie Zawinski https://www.jwz.org/ https://www.dnalounge.com/
As I said, it's already fixed in 6.00. The fix is just to configure without
setcap and use setuid instead, which works properly with Mesa.
I assume that having 6.00 distributed by Debian prior to 2035 would be asking
too much, but we dare to dream.
Already fixed in XScreenSaver 6.00.
The bug is in Mesa: it has a panoply of env vars that do what LD_PRELOAD does,
except Mesa only checks geteuid instead of checking getauxval AT_SECURE, as the
kernel does. So anything that uses both Mesa and setcap is vulnerable.
Ironically, using setuid
It is possible to use sway and Firefox with the flickering but it is
really difficult.
I noticed that sway 1.6 is released now[1].
If a 1.6 release is possible, even in experimental, it would be hugely
appreciated!
jamie
1. https://github.com/swaywm/sway/releases/tag/1.6
--
May First
My Thinkpad T460s was also affected (failing to resume from a suspend if
TPM2 is enabled), however upgrading from 1.49 --> N1CET82W (1.50 )
10/15/2020 seems to have solved the issue. There are references to TPM
sleep/wake issues in the ChangeLog, but only in previous versions:
On Tue, 29 Dec 2020, Jamie Strandboge wrote:
> On Tue, 29 Dec 2020, Energo Koder wrote:
> > Anywhere on enp0s25LIMIT Anywhere
> > Anywhere on wlx08beac034eef LIMIT Anywhere
>
> I suspect it is these two lines that are
Package: ftp.debian.org
Severity: normal
Dear colleagues,
`chaksem' is no longer available from the location mentioned in it's copyright
file. The source only exists now in Debian (archives, salsa) AFAIK.
I personally have no use for a LaTeX slide deck class, and there are many like
it in
.0 3748 664 pts/0S+ 21:56 0:00 grep saver
Note that pid 11997 does not have -nosplash on its command line.
--
Jamie Zawinski https://www.jwz.org/ https://www.dnalounge.com/
nd user B.
If things have gone wrong in a weird way, the "xscreensaver-systemd" process of
user A might linger, but it won't be able to communicate with user B's
xscreensaver.
--
Jamie Zawinski https://www.jwz.org/ https://www.dnalounge.com/
dministrator installed xscreensaver on a multi-user
system, the expectation would be for it to run in all graphical login sessions.
--
Jamie Zawinski https://www.jwz.org/ https://www.dnalounge.com/
> 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 interfering with the xscreensaver
> instance of the logged in user?
>
1 - 100 of 1390 matches
Mail list logo
