la 30. tammik. 2021 klo 17.42 Santiago Garcia Mantinan
(ma...@debian.org) kirjoitti:
> BTW: one thing I do on this kind of hotplug setup is allow hotplug on
> bridge-utils, which means setting it to yes on /etc/default/bridge-utils
> This allows me to plug in and out ethernet devices without
la 30. tammik. 2021 klo 14.46 Santiago Garcia Mantinan
(ma...@debian.org) kirjoitti:
>
> > On a host with a mixture of USB WiFi dongles and Ethernet cards, I have to
> > specify the MAC address using both bridge_hw and ifup's generic hwaddress
> > to ensure that the host fetches the correct IP
I HAVE set bridge_hw to a static device. That's what I described.
Martin-Éric
la 30. tammik. 2021 klo 14.13 Santiago Garcia Mantinan
(ma...@debian.org) kirjoitti:
>
> Hi again!
>
> > What I DO notice is that because the bridge is stupid enough to use the
> > MAC address of a removable device to
If anyone asks me, declaring removable devices in allow-hotplug would
make more sense, since we'll typically wanna run perform ifup actions
upon connecting the device to the computer. In the case of WiFi
dongles used as AP, we'll typically wanna load the configuration file
defined via the "hostapd
Package: bridge-utils
Version: 1.6-5+b1
Followup-For: Bug #981076
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Having further googled this and made a few tests, the key difference seems to
be whether the removable devices are declared in the auto or in the
allow-hotplug lines of
Package: bridge-utils
Version: 1.6-5+b1
Followup-For: Bug #979963
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I wouldn't know whether it's because of the kernel driver or because of
bridge-utils.
What I DO notice is that because the bridge is stupid enough to use the MAC
address of a
Actually, make that:
Document the minimum and maximum values of all options, and tell which
value is the strongest for each.
-- Martin-Éric
Package: bridge-utils
Version: 1.6-5+b1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Reading the manual page, it remains unclear which bridge_portprio value would
give a port a higher priority. It only says that the default value is 128.
Would a valur of 1 have a higher
Package: bridge-utils
Followup-For: Bug #981076
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
This mess is the result of the kernel maintainers changing their mind on how
the bridge module should work. This isn't bridge-utils' fault. bridge-utils
merely tries to adapt to those changes and
Package: gpm
Version: 1.20.7-8
Followup-For: Bug #980726
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Setting up gpm (1.20.7-8) ...
Created symlink /etc/systemd/system/multi-user.target.wants/gpm.service ->
/lib/systemd/system/gpm.service.
Failed to reload daemon: Connection reset by peer
In that case, a massive bin-NMU of GNOME packages might be in order.
Thanks!
Martin-Éric
ma 25. tammik. 2021 klo 19.06 Michael Biebl (bi...@debian.org) kirjoitti:
>
> Am 25.01.21 um 18:05 schrieb Michael Biebl:
> > Am 25.01.21 um 17:55 schrieb Martin-Éric Racine:
> > > Pac
Package: libcanberra-gtk3-module
Version: 0.30-7
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
libcanberra-gtk3-module and libcanberra-gtk3-0 both depend on this transitional
package.
Package: libgdk-pixbuf2.0-0
Version: 2.40.2-2
Depends: libgdk-pixbuf-2.0-0 (>= 2.40.0),
Package: libclutter-gst-3.0-0
Version: 3.0.27-2
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: libgdk-pixbuf2.0-0
Version: 2.40.2-2
Depends: libgdk-pixbuf-2.0-0 (>= 2.40.0), libgdk-pixbuf-xlib-2.0-0 (>= 2.40.2-2)
Description-en: GDK Pixbuf library (transitional
Package: libclutter-gtk-1.0-0
Version: 1.8.4-4
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: libgdk-pixbuf2.0-0
Version: 2.40.2-2
Depends: libgdk-pixbuf-2.0-0 (>= 2.40.0), libgdk-pixbuf-xlib-2.0-0 (>= 2.40.2-2)
Description-en: GDK Pixbuf library (transitional
Package: libcolord-gtk1
Version: 0.1.26-2
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: libgdk-pixbuf2.0-0
Version: 2.40.2-2
Depends: libgdk-pixbuf-2.0-0 (>= 2.40.0), libgdk-pixbuf-xlib-2.0-0 (>= 2.40.2-2)
Description-en: GDK Pixbuf library (transitional package)
Package: libdbusmenu-gtk3-4
Version: 18.10.20180917~bzr492+repack1-2
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: libgdk-pixbuf2.0-0
Version: 2.40.2-2
Depends: libgdk-pixbuf-2.0-0 (>= 2.40.0), libgdk-pixbuf-xlib-2.0-0 (>= 2.40.2-2)
Description-en: GDK Pixbuf
Package: libdmapsharing-3.0-2
Version: 2.9.41-3
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: libgdk-pixbuf2.0-0
Version: 2.40.2-2
Depends: libgdk-pixbuf-2.0-0 (>= 2.40.0), libgdk-pixbuf-xlib-2.0-0 (>= 2.40.2-2)
Description-en: GDK Pixbuf library (transitional
Package: libgnomekbd8
Version: 3.26.1-1
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: libgdk-pixbuf2.0-0
Version: 2.40.2-2
Depends: libgdk-pixbuf-2.0-0 (>= 2.40.0), libgdk-pixbuf-xlib-2.0-0 (>= 2.40.2-2)
Description-en: GDK Pixbuf library (transitional package)
Package: libgtksourceview-3.0-1
Version: 3.24.11-2
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: libgdk-pixbuf2.0-0
Version: 2.40.2-2
Depends: libgdk-pixbuf-2.0-0 (>= 2.40.0), libgdk-pixbuf-xlib-2.0-0 (>= 2.40.2-2)
Description-en: GDK Pixbuf library (transitional
Package: libgtksourceview-4-0
Version: 4.8.0-1
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: libgdk-pixbuf2.0-0
Version: 2.40.2-2
Depends: libgdk-pixbuf-2.0-0 (>= 2.40.0), libgdk-pixbuf-xlib-2.0-0 (>= 2.40.2-2)
Description-en: GDK Pixbuf library (transitional
Package: libgweather-3-16
Version: 3.36.1-1
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: libgdk-pixbuf2.0-0
Version: 2.40.2-2
Depends: libgdk-pixbuf-2.0-0 (>= 2.40.0), libgdk-pixbuf-xlib-2.0-0 (>= 2.40.2-2)
Description-en: GDK Pixbuf library (transitional package)
Package: librsvg2-common
Version: 2.40.16-1+b1
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
librsvg2-common and librsvg2-2 depend on a transitional package.
Package: libgdk-pixbuf2.0-0
Version: 2.40.2-2
Depends: libgdk-pixbuf-2.0-0 (>= 2.40.0), libgdk-pixbuf-xlib-2.0-0
Package: lightdm-gtk-greeter
Version: 2.0.8-2
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: libgdk-pixbuf2.0-0
Version: 2.40.2-2
Depends: libgdk-pixbuf-2.0-0 (>= 2.40.0), libgdk-pixbuf-xlib-2.0-0 (>= 2.40.2-2)
Description-en: GDK Pixbuf library (transitional
Package: network-manager-gnome
Version: 1.18.0-1
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: libgdk-pixbuf2.0-0
Version: 2.40.2-2
Depends: libgdk-pixbuf-2.0-0 (>= 2.40.0), libgdk-pixbuf-xlib-2.0-0 (>= 2.40.2-2)
Description-en: GDK Pixbuf library (transitional
Package: notification-daemon
Version: 3.20.0-4
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: libgdk-pixbuf2.0-0
Version: 2.40.2-2
Depends: libgdk-pixbuf-2.0-0 (>= 2.40.0), libgdk-pixbuf-xlib-2.0-0 (>= 2.40.2-2)
Description-en: GDK Pixbuf library (transitional
Package: policykit-1-gnome
Version: 0.105-7
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: libgdk-pixbuf2.0-0
Version: 2.40.2-2
Depends: libgdk-pixbuf-2.0-0 (>= 2.40.0), libgdk-pixbuf-xlib-2.0-0 (>= 2.40.2-2)
Description-en: GDK Pixbuf library (transitional package)
Package: zenity
Version: 3.32.0-6
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: libgdk-pixbuf2.0-0
Source: gdk-pixbuf-xlib
Version: 2.40.2-2
Installed-Size: 22
Maintainer: Debian GNOME Maintainers
Architecture: i386
Depends: libgdk-pixbuf-2.0-0 (>= 2.40.0),
Package: ibus-clutter
Version: 0.0+git20090728.a936bacf-5.1+b2
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: libegl1-mesa
Source: mesa
Version: 20.3.3-1
Installed-Size: 68
Maintainer: Debian X Strike Force
Architecture: i386
Depends: libegl1
Description-en:
Package: python3.9
Version: 3.9.1-3
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: mime-support
Depends: mailcap, media-types
Description-en: transitional package
This is a transitional package. It will be possible to remove it
safely once its dependency chain has
Package: bridge-utils
Version: 1.6-2
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On a host with a mixture of USB WiFi dongles and Ethernet cards, I have to
specify the MAC address using both bridge_hw and ifup's generic hwaddress to
ensure that the host fetches the
If anyone asks me, the correct behavior for any interface that uses
the manual method should be to never create the IPv6 fe80 local link,
and instead assume that it will be manually created via other means,
the same way it already is for Ethernet devices. Whether the interface
is listed on the
Package: ifupdown
Version: 0.8.35
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
My router has several USB dongles configured via /etc/network/interfaces as AP
each using an "hostapd /etc/hostapd/dongle1.conf" statement and method manual.
All interfaces are bridged
Package: ifupdown
Version: 0.8.35
Followup-For: Bug #621000
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
It would indeed be a good idea to get around documenting this.
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmAJqkYACgkQrh+Cd8S0
to 21. tammik. 2021 klo 16.46 Santiago Garcia Mantinan
(ma...@debian.org) kirjoitti:
>
> > > iface br0 inet dhcp
> > > bridge_ports all
> > > bridge_hw enp6s0
> >
> > This would obviously change the syntax of bridge_hw but it would
> > accomplish what we need with a syntax that
to 21. tammik. 2021 klo 16.00 Santiago Garcia Mantinan
(ma...@debian.org) kirjoitti:
> > I suggest a new option called bridge_via to specify the routing interface:
>
> I've been thinking a bit on this as I didn't like the bridge_via naming as
> this is just to specify the interface that we take
Actually, on a laptop, I get:
enp9s0 (PCI Ethernet)
wlp12s0 (PCI WiFi)
USB WiFi devices on my other hosts follow a different format:
wlxaabbccddeeff (wlx+mac address)
Thus the regex for wireless seems to be wl* to catch all variants.
Cheers!
Martin-Éric
Package: bridge-utils
Followup-For: Bug #966319
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Thanks for fixing this. Adding en* to the regex should indeed help.
Just to verify:
Is wl* already in the regex?
On this host, I have en* for Ethernet cards and wlx(mac address) for wireless
PCI
Package: calendar
Version: 12.1.7
Severity: normal
Upon upgrading to Bullseye, /etc/calendar/default is reported as oldconfig.
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 5.10.0-1-686-pae (SMP w/1 CPU thread)
Locale:
Package: bridge-utils
Version: 1.6-2
Followup-For: Bug #932114
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
That doesn't reflect what's happening here. The host in question has no
firewalling whatsoever. This is the result of merely launching a bridge.
Whatever commands bridge-utils issue
Package: bridge-utils
Version: 1.6-2
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
My router bridges 2 Ethernet cards and a couple of USB dongles configured as
WiFi hostspots with hostapd.
Whenever I need to perform maintenance at the console, I have to remove the USB
Package: devscripts
Version: 2.20.5
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
While reviewing my packages before the Bullseye freeze, I noticed that PTS
claims one package's upstream releases cannot be scanned.
(Problems while searching for a new upstream version. uscan
The specific command I used is this:
dpkg-query --show --showformat='${Conffiles}\n' | grep obsolete
Martin-Éric
la 2. tammik. 2021 klo 12.06 Charles Plessy (ple...@debian.org) kirjoitti:
>
> Le Sat, Jan 02, 2021 at 10:00:51AM +0200, Martin-Éric Racine a écrit :
> >
> > The issue can
Hey Charles,
The issue can be reproduced both on my Testing host and in an Unstable
chroot that regularly gets updated.
Martin-Éric
la 2. tammik. 2021 klo 5.17 Charles Plessy (ple...@debian.org) kirjoitti:
>
> Le Fri, Jan 01, 2021 at 07:24:28PM +0200, Martin-Éric Racine a écrit :
> &
Hey Charles,
No, there isn't. The issue is repeatable both on my Testing host and
in an Unstable chroot.
Martin-Éric
la 2. tammik. 2021 klo 5.13 Charles Plessy (ple...@debian.org) kirjoitti:
>
> Le Fri, Jan 01, 2021 at 07:26:28PM +0200, Martin-Éric Racine a écrit :
> >
> > Th
Package: mailcap
Version: 3.68
Followup-For: Bug #974729
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
This part of the bug report still applies to 3.68:
mailcap: /etc/mailcap.order
- -- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (800, 'unstable')
Package: piuparts
Version: 1.1.1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
/etc/piuparts/scripts/pre_remove_40_find_obsolete_conffiles is reported as
oldconfig belonging to package piuparts.
Please see...
Package: media-types
Version: 1.0.1
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
/etc/mime.types is reported as oldconfig belonging to package media-types.
Please see...
https://manpages.debian.org/unstable/dpkg/dpkg-maintscript-helper.1.en.html
... for details on how
Package: lintian-brush
Version: 0.89
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Traceback (most recent call last):
File "/usr/bin/deb-scrub-obsolete", line 33, in
sys.exit(load_entry_point('lintian-brush==0.89', 'console_scripts',
'deb-scrub-obsolete')())
File
Package: lintian-brush
Version: 0.89
Followup-For: Bug #917381
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I second this request.
Merely making the changes and running 'dch -i -n' would be enough to produce a
debdiff against the previous release and attached it to a bug report for the
Package: gthumb
Version: 3:3.8.3-0.1
Followup-For: Bug #974608
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Fixed upstream 1 hour ago:
https://gitlab.gnome.org/GNOME/gthumb/-/commit/3bdb4f94ba37b410ac07c25b5c83e587b55482fd
See also:
https://gitlab.gnome.org/GNOME/gthumb/-/issues/137
su 27. jouluk. 2020 klo 23.27 Chris Hofstaedtler (z...@debian.org) kirjoitti:
> * Martin-Éric Racine [201227 22:06]:
> > Right, so in that case, there is no bug in upgrade-system.
> > In your case, the solution indeed is to add --no-guess-python to ORPHANOPTS.
>
> > su 27
--libdevel
> python-cffi-backend
> rbthomas@monk:~$ deborphan --guess-all --no-guess-python --libdevel
> rbthomas@monk:~$
>
> Hope this helps!
> Rick
>
> On Sat, Dec 26, 2020, at 3:03 PM, Martin-Éric Racine wrote:
> > la 26. jouluk. 2020 klo 21.
la 26. jouluk. 2020 klo 21.30 Rick Thomas (rbtho...@rcthomas.org) kirjoitti:
>
> Package: upgrade-system
> Version: 1.7.3.1
> Severity: normal
>
> --- Please enter the report below this line. ---
>
> The package "deluge" is manually (i.e. not "auto") installed on my
> system. I use it daily. But
to 10. jouluk. 2020 klo 21.43 Martin-Éric Racine
(martin-eric.rac...@iki.fi) kirjoitti:
>
> to 10. jouluk. 2020 klo 21.21 Simon McVittie (s...@debian.org) kirjoitti:
> > Debian's rustc has a patch to reduce the i386 baseline from upstream's
> > pentium4 to pentiumpro
> > ht
to 10. jouluk. 2020 klo 21.21 Simon McVittie (s...@debian.org) kirjoitti:
> On Thu, 10 Dec 2020 at 20:02:42 +0200, Martin-Éric Racine wrote:
> > Core was generated by `/usr/bin/gnome-shell'.
> > Program terminated with signal SIGILL, Illegal instruction.
> > #0 0xb5500d08
to 10. jouluk. 2020 klo 19.47 Simon McVittie (s...@debian.org) kirjoitti:
>
> On Thu, 10 Dec 2020 at 18:29:39 +0200, Martin-Éric Racine wrote:
> > Btw, when it comes to libmozjs, is there any attachment you'd need?
> > gdb backtrace, etc.?
>
> A backtrace is always u
Package: gnome-session-bin
Version: 3.38.0-3
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
$ sudo LC_ALL=C coredumpctl debug 865 --output
/tmp/coredump_gnome-session-failed
Failed to check if any systemd-coredump@.service units are running: Failed to
activate service
ti 8. jouluk. 2020 klo 17.35 Martin-Éric Racine
(martin-eric.rac...@iki.fi) kirjoitti:
>
> ma 9. marrask. 2020 klo 20.05 Martin-Éric Racine
> (martin-eric.rac...@iki.fi) kirjoitti:
> >
> > su 8. marrask. 2020 klo 14.40 Simon McVittie (s...@debian.org) kirjoitti:
> >
Reading symbols from /usr/bin/fwupdmgr...
Reading symbols from
/usr/lib/debug/.build-id/94/55f3483d573ccb3fe3629c46880ba8b46a9b02.debug...
[New LWP 1191]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
Core was generated by
$ sudo coredumpctl debug 1191 --output /tmp/coredump_fwupd
PID: 1191 (fwupdmgr)
UID: 62803 (62803)
GID: 62803 (62803)
Signal: 4 (ILL)
Timestamp: Thu 2020-12-10 16:25:33 EET (15min ago)
Command Line: /usr/bin/fwupdmgr refresh --no-metadata-check
Package: fwupd
Version: 1.5.1-5
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
$ sudo invoke-rc.d fwupd restart
Job for fwupd.service failed because a fatal signal was delivered causing the
control process to dump core.
See "systemctl status fwupd.service" and "journalctl
ti 8. jouluk. 2020 klo 19.54 Thorsten Glaser (t...@mirbsd.de) kirjoitti:
>
> Martin-Éric Racine dixit:
>
> >Since systemd 247, there is a very loud dmesg about this:
>
> Yes, but as things are much too complicated, this will not
> be changed before the freeze any more.
&g
Package: systemd-cron
Version: 1.5.15-1
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
[ 43.789346] systemd[1]: /lib/systemd/system/cron-failure@.service:11:
Special user nobody configured, this is not safe!
[ 43.824795] systemd[1]:
Package: smartmontools
Version: 7.1-1
Followup-For: Bug #969048
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Could the upstream fix that was mentioned in the previous comment please be
merged ASAP? Thanks!
- -- System Information:
Debian Release: bullseye/sid
APT prefers testing-debug
Package: plymouth
Version: 0.9.4-3
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
As reported via dmesg:
systemd[1]: /lib/systemd/system/plymouth-start.service:16: Unit configured to
use KillMode=none. This is unsafe, as it disables systemd's process lifecycle
management
Package: gpm
Version: 1.20.7-6
Followup-For: Bug #777291
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Please note that since systemd 247, dmesg displays the following loud warning:
systemd-sysv-generator[177]: SysV service '/etc/init.d/gpm' lacks a native
systemd unit file. Automatically
Package: rng-tools-debian
Version: 2.3
Followup-For: Bug #776597
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Since systemd 247, there is a very loud dmesg about this:
systemd-sysv-generator[177]: SysV service '/etc/init.d/rng-tools-debian' lacks
a native systemd unit file. Automatically
Package: cpufrequtils
Version: 008-2
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Since systemd 247, dmesg displays the following:
systemd-sysv-generator[177]: SysV service '/etc/init.d/loadcpufreq' lacks a
native systemd unit file. Automatically generating a unit file
Package: cpufrequtils
Version: 008-2
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Since systemd 247, dmesg displays this:
systemd-sysv-generator[177]: SysV service '/etc/init.d/cpufrequtils' lacks a
native systemd unit file. Automatically generating a unit file for
ma 9. marrask. 2020 klo 20.05 Martin-Éric Racine
(martin-eric.rac...@iki.fi) kirjoitti:
>
> su 8. marrask. 2020 klo 14.40 Simon McVittie (s...@debian.org) kirjoitti:
> > Because your syslog also included similar crashes in librsvg, which is
> > unrelated to mozjs except that both
Package: librsvg2-2
Version: 2.40.16-1+b1
Severity: important
Tags: upstream
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On this host (Geode LX800 i.e. an i686 minus PAE), the SVG library flat out
crashes:
[ 204.840919] traps: gnome-session-f[939] trap invalid opcode ip:b4e7f86a
Package: librsvg2-2
Version: 2.50.2+dfsg-1
Followup-For: Bug #891561
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On this host (Geode LX800 i.e. an i686 minus PAE), the SVG library flat out
crashes:
[ 204.840919] traps: gnome-session-f[939] trap invalid opcode ip:b4e7f86a
sp:bfcc1460
ma 9. marrask. 2020 klo 20.05 Martin-Éric Racine
(martin-eric.rac...@iki.fi) kirjoitti:
>
> su 8. marrask. 2020 klo 14.40 Simon McVittie (s...@debian.org) kirjoitti:
> > Because your syslog also included similar crashes in librsvg, which is
> > unrelated to mozjs except that both
Package: dh-runit
Followup-For: Bug #968114
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
This bug is not really fixed. The fix was only pushed to experimental.
Meanwhile, packages in unstable still face this issue. Given how close we are
to the freeze, it would be a good idea to push
Package: firefox-esr
Version: 78.4.1esr-1~deb10u1
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
When connecting to a Zoom session, Zoom doesn't transmit the microphone sound,
even though the microphone icon in Firefox flashes to indicate that someone
indeed is speaking.
su 8. marrask. 2020 klo 14.40 Simon McVittie (s...@debian.org) kirjoitti:
> Because your syslog also included similar crashes in librsvg, which is
> unrelated to mozjs except that both involve Rust code, I wonder whether
> it might be the rust compiler rather than mozjs' JIT that is emitting
>
pe 30. lokak. 2020 klo 13.50 Simon McVittie (s...@debian.org) kirjoitti:
> On Fri, 30 Oct 2020 at 10:35:21 +0200, Martin-Éric Racine wrote:
> > [ 165.903916] traps: gnome-shell[869] trap invalid opcode ip:b5518f8a
> > sp:b17d6d80 error:0 in libmozjs-78.so.78.3.0[b4b98000+98
Package: libmozjs-78-0
Version: 78.3.0-2
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
[ 165.903916] traps: gnome-shell[869] trap invalid opcode ip:b5518f8a
sp:b17d6d80 error:0 in libmozjs-78.so.78.3.0[b4b98000+98c000]
[ 186.163963] traps: gnome-shell[931] trap invalid
[uCode/AMD] #0 no ucode updates available
The processor microcode seems to be up-to-date.
to 29. lokak. 2020 klo 20.30 Thomas Liske (tho...@fiasko-nw.net) kirjoitti:
>
> Hi,
>
> could you please provide the output of `needrestart -vw`?
>
>
> TIA & Regards,
> Thomas
>
>
Package: needrestart
Version: 3.5-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Scanning processes...
Use of
Package: lxdm
Version: 0.5.3-3
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The default config that ships with LXDM uses the Clearlooks GTK2 theme. This is
not installed by default on a GTK3 system. LXDM must therefore Depends on
gtk2-engines which provides the
Package: lxdm
Version: 0.5.3-3
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The default config that ships with LXDM fails to produce a visible greeter.
After playing with the defaults, I noticed that the problem is caused by the
default background image. If I change it
Package: systemd-cron
Version: 1.5.14-2
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Since a recent upgrade, systemd complains loudly via dmesg:
[ 45.787544] systemd[1]: /lib/systemd/system/cron-failure@.service:11:
Special user nobody configured, this is not safe!
[
Package: bridge-utils
Version: 1.6-2
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On hosts using Predictable Network Interface Names (e.g.enp4s0) "bridge_ports
all" in /etc/network/interfaces fails at making the bridge find any interface.
None of the interfaces shown in
Package: bridge-utils
Version: 1.6-2
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On hosts that get their IP via DHCP, bridge-utils picks a random MAC address
among the interfaces on the host to identify the DHCP request. This produces
non-predictable results, especially if
Geode is NOT obsolete. The base kernel for i386 in fact is configured
for Geode (686 non-PAE).
Martin-Éric
Package: python3-yaml
Version: 5.3.1-1
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Setting up python3-yaml (5.3.1-1) ...
/usr/lib/python3.8/subprocess.py:838: RuntimeWarning: line buffering
(buffering=1) isn't supported in binary mode, the default buffer size will be
xplanation in the log and otherwise the behaviour is as it
> should be.
>
> Cheers,
> Balint
>
> Bálint Réczey ezt írta (időpont: 2020. febr.
> 2., V, 16:21):
> >
> > Hi Martin-Éric,
> >
> > Martin-Éric Racine ezt írta (időpont:
> > 2020. febr. 2.
su 2. helmik. 2020 klo 17.03 Bálint Réczey (bal...@balintreczey.hu) kirjoitti:
>
> Hi Martin-Éric Racine,
>
> Martin-Éric Racine ezt írta (időpont:
> 2020. febr. 2., V, 15:54):
> >
> > su 2. helmik. 2020 klo 16.50 Bálint Réczey (bal...@balintreczey.hu)
> > ki
su 2. helmik. 2020 klo 16.50 Bálint Réczey (bal...@balintreczey.hu) kirjoitti:
> Martin-Éric Racine ezt írta (időpont:
> 2020. febr. 2., V, 15:33):
> >
> > Package: unattended-upgrades
> > Version: 1.17
> > Severity: important
> >
> > -BEGI
Package: unattended-upgrades
Version: 1.17
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Since a few days, MOTD includes the following stanza:
1 updates could not be installed automatically. For more details,
see /var/log/unattended-upgrades/unattended-upgrades.log
The
la 11. toukok. 2019 klo 22.00 Neil R. Ormos (ormos-deb1...@ormos.org) kirjoitti:
>
> Brian Potkin wrote:
> > Neil Ormos wrote:
>
> >> I have no idea why the new print queue including the
> >> pdftops-renderer=pdftocairo option was not established, as
> >> expected, during the original
et used
> > with
> > the From: line if the name inherited from /etc/passwd is in UTF-8.
> >
> > cat file | mail -s "some subject" u...@domain.ltd
> >
> > q-funk:x:1000:1000:Martin-Éric Racine,,,:/home/q-funk:/bin/bash
>
> Hello Martin-Éric,
>
ke 13. marrask. 2019 klo 23.16 Michael Biebl (bi...@debian.org) kirjoitti:
>
> Ok, at this point I guess it's best to involve upstream.
> Would you mind filing an upstream bug report at
> https://github.com/systemd/system/issues
> mentionting that a daemon-reload triggers an assert in
>
ke 13. marrask. 2019 klo 21.03 Michael Biebl (bi...@debian.org) kirjoitti:
>
> Btw, this reminds me of
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883877#103
>
> Is this the same host where this is happening (again)?
> Is this a Virtualbox guest?
Same host. This has never been a
ke 13. marrask. 2019 klo 20.52 Michael Biebl (bi...@debian.org) kirjoitti:
>
> Thanks a lot for the information so far.
>
> Am 13.11.19 um 16:53 schrieb Martin-Éric Racine:
>
> > Setting up udev (243-5) ...
>
> Could you add a "set -x" to
> /var/lib/dpkg
ke 13. marrask. 2019 klo 17.37 Michael Biebl (bi...@debian.org) kirjoitti:
>
> Am 13.11.19 um 16:06 schrieb Martin-Éric Racine:
>
> >> Can you provide a dmesg dump and the output of journalctl -alb.
> >
> > Attached.
> >
> >> Please mark the time w
ke 13. marrask. 2019 klo 17.06 Martin-Éric Racine
(martin-eric.rac...@iki.fi) kirjoitti:
>
> ke 13. marrask. 2019 klo 16.44 Michael Biebl (bi...@debian.org) kirjoitti:
> >
> > Control: tags -1 moreinfo unreproducible
> > Am 13.11.19 um 10:34 schrieb Martin-Éric Racine
Package: systemd
Version: 243-5
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
systemd upgrade broke dbus, which in turn prevents normal operation of APT and
upgrade of packages that depend upon dbus messages.
**
$ sudo dpkg --configure --pending
Setting up
Package: alsa-utils
Version: 1.1.9-1
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Setting up alsa-utils (1.1.9-1) ...
Installing new version of config file /etc/init.d/alsa-utils ...
Broadcast message from systemd-journald@geode (Wed 2019-11-13 10:31:39 EET):
systemd[1]:
501 - 600 of 1973 matches
Mail list logo
