Bug#1041732: "N: Missing Signed-By in the sources.list(5) entry for 'http://deb.debian.org/debian'"
Package: apt Version: 2.7.2 Severity: minor X-Debbugs-Cc: debbugs2023...@wulf.eu.org Hello, since updating to apt-2.7.2 I'm getting a notice on "apt update": # apt update Hit:1 http://deb.debian.org/debian sid InRelease Hit:2 http://deb.debian.org/debian experimental InRelease Reading package lists... Done Building dependency tree... Done Reading state information... Done All packages are up to date. N: Missing Signed-By in the sources.list(5) entry for 'http://deb.debian.org/debian' N: Missing Signed-By in the sources.list(5) entry for 'http://deb.debian.org/debian' My /etc/apt/sources.list.d/debian.sources contains: Types: deb deb-src URIs: http://deb.debian.org/debian/ Suites: sid experimental Components: main contrib non-free non-free-firmware The Changelog contains an entry: * update: Add notice about missing Signed-By in deb822 sources" I tried "Signed-By: /etc/apt/trusted.gpg.d/*" but that doesn't work. What is the correct value? Thanks! -- Package-specific info: -- apt-config dump -- APT ""; APT::Architecture "amd64"; APT::Build-Essential ""; APT::Build-Essential:: "build-essential"; APT::Install-Recommends "0"; APT::Install-Suggests "0"; APT::Sandbox ""; APT::Sandbox::User "_apt"; APT::Authentication ""; APT::Authentication::TrustCDROM "true"; APT::NeverAutoRemove ""; APT::NeverAutoRemove:: "^firmware-linux.*"; APT::NeverAutoRemove:: "^linux-firmware$"; APT::NeverAutoRemove:: "^linux-image-[a-z0-9]*$"; APT::NeverAutoRemove:: "^linux-image-[a-z0-9]*-[a-z0-9]*$"; APT::VersionedKernelPackages ""; APT::VersionedKernelPackages:: "linux-.*"; APT::VersionedKernelPackages:: "kfreebsd-.*"; APT::VersionedKernelPackages:: "gnumach-.*"; APT::VersionedKernelPackages:: ".*-modules"; APT::VersionedKernelPackages:: ".*-kernel"; APT::Never-MarkAuto-Sections ""; APT::Never-MarkAuto-Sections:: "metapackages"; APT::Never-MarkAuto-Sections:: "tasks"; APT::Move-Autobit-Sections ""; APT::Move-Autobit-Sections:: "oldlibs"; APT::Update ""; APT::Update::Post-Invoke-Success ""; APT::Update::Post-Invoke-Success:: "/usr/bin/test -e /usr/share/dbus-1/system-services/org.freedesktop.PackageKit.service && /usr/bin/test -S /var/run/dbus/system_bus_socket && /usr/bin/gdbus call --system --dest org.freedesktop.PackageKit --object-path /org/freedesktop/PackageKit --timeout 4 --method org.freedesktop.PackageKit.StateHasChanged cache-update > /dev/null; /bin/echo > /dev/null"; APT::Update::Post-Invoke ""; APT::Update::Post-Invoke:: "[ ! -x /usr/bin/debtags ] || debtags update || true"; APT::Architectures ""; APT::Architectures:: "amd64"; APT::Architectures:: "i386"; APT::Compressor ""; APT::Compressor::. ""; APT::Compressor::.::Name "."; APT::Compressor::.::Extension ""; APT::Compressor::.::Binary ""; APT::Compressor::.::Cost "0"; APT::Compressor::zstd ""; APT::Compressor::zstd::Name "zstd"; APT::Compressor::zstd::Extension ".zst"; APT::Compressor::zstd::Binary "zstd"; APT::Compressor::zstd::Cost "60"; APT::Compressor::zstd::CompressArg ""; APT::Compressor::zstd::CompressArg:: "-19"; APT::Compressor::zstd::UncompressArg ""; APT::Compressor::zstd::UncompressArg:: "-d"; APT::Compressor::lz4 ""; APT::Compressor::lz4::Name "lz4"; APT::Compressor::lz4::Extension ".lz4"; APT::Compressor::lz4::Binary "lz4"; APT::Compressor::lz4::Cost "50"; APT::Compressor::lz4::CompressArg ""; APT::Compressor::lz4::CompressArg:: "-1"; APT::Compressor::lz4::UncompressArg ""; APT::Compressor::lz4::UncompressArg:: "-d"; APT::Compressor::gzip ""; APT::Compressor::gzip::Name "gzip"; APT::Compressor::gzip::Extension ".gz"; APT::Compressor::gzip::Binary "gzip"; APT::Compressor::gzip::Cost "100"; APT::Compressor::gzip::CompressArg ""; APT::Compressor::gzip::CompressArg:: "-6n"; APT::Compressor::gzip::UncompressArg ""; APT::Compressor::gzip::UncompressArg:: "-d"; APT::Compressor::xz ""; APT::Compressor::xz::Name "xz"; APT::Compressor::xz::Extension ".xz"; APT::Compressor::xz::Binary "xz"; APT::Compressor::xz::Cost "200"; APT::Compressor::xz::CompressArg ""; APT::Compressor::xz::CompressArg:: "-6"; APT::Compressor::xz::UncompressArg ""; APT::Compressor::xz::UncompressArg:: "-d"; APT::Compressor::bzip2 ""; APT::Compressor::bzip2::Name "bzip2"; APT::Compressor::bzip2::Extension ".bz2"; APT::Compressor::bzip2::Binary "bzip2"; APT::Compressor::bzip2::Cost "300"; APT::Compressor::bzip2::CompressArg ""; APT::Compressor::bzip2::CompressArg:: "-6"; APT::Compressor::bzip2::UncompressArg ""; APT::Compressor::bzip2::UncompressArg:: "-d"; APT::Compressor::lzma ""; APT::Compressor::lzma::Name "lzma"; APT::Compressor::lzma::Extension ".lzma"; APT::Compressor::lzma::Binary "xz"; APT::Compressor::lzma::Cost "400"; APT::Compressor::lzma::CompressArg ""; APT::Compressor::lzma::CompressArg:: "--format=lzma"; APT::Compressor::lzma::CompressArg:: "-6"; APT::Compressor::lzma::UncompressArg ""; APT::Compressor::lzma::UncompressArg:: "--format=lzma"; APT::Compressor::lzma::UncompressArg:: "-d"; Dir "/"; Dir::State "var/lib/apt"; Dir::State::lists "lists/";
Bug#1035490: libwebkit2gtk-4.0-37: evolution won't display mails after upgrading libwebkit2gtk
Package: libwebkit2gtk-4.0-37 Version: 2.40.1-1~deb11u1 Severity: important X-Debbugs-Cc: debbugs2...@wulf.eu.org Dear maintainer, unattended upgrades ran tonight: 2023-05-04 06:11:47 upgrade gir1.2-webkit2-4.0:amd64 2.38.5-1~deb11u1 2.40.1-1~deb11u1 2023-05-04 06:11:47 upgrade libwebkit2gtk-4.0-37:amd64 2.38.5-1~deb11u1 2.40.1-1~deb11u1 2023-05-04 06:11:49 upgrade gir1.2-javascriptcoregtk-4.0:amd64 2.38.5-1~deb11u1 2.40.1-1~deb11u1 2023-05-04 06:11:49 upgrade libjavascriptcoregtk-4.0-18:amd64 2.38.5-1~deb11u1 2.40.1-1~deb11u1 Afterwards, evolution fails to display mail bodies properly. There's only a tiny browser bar which contains the mail. See attached screenshot. If I scroll through it, I see bits of my mail. Downgrading above packages fixes the problem. -- System Information: Debian Release: 11.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-21-amd64 (SMP w/4 CPU threads) 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: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libwebkit2gtk-4.0-37 depends on: ii bubblewrap 0.4.1-3 ii gstreamer1.0-plugins-base 1.18.4-2 ii gstreamer1.0-plugins-good 1.18.4-2+deb11u1 ii libatk1.0-0 2.36.0-2 ii libatomic1 10.2.1-6 ii libc6 2.31-13+deb11u6 ii libcairo-gobject2 1.16.0-5 ii libcairo2 1.16.0-5 ii libenchant-2-2 2.2.15-1 ii libepoxy0 1.5.5-1 ii libfontconfig1 2.13.1-4.2 ii libfreetype62.10.4+dfsg-1+deb11u1 ii libgcc-s1 10.2.1-6 ii libgcrypt20 1.8.7-6 ii libgdk-pixbuf-2.0-0 2.42.2+dfsg-1+deb11u1 ii libglib2.0-02.66.8-1 ii libgpg-error0 1.38-2 ii libgstreamer-gl1.0-01.18.4-2 ii libgstreamer-plugins-base1.0-0 1.18.4-2 ii libgstreamer1.0-0 1.18.4-2.1 ii libgtk-3-0 3.24.24-4+deb11u3 ii libharfbuzz-icu02.7.4-1 ii libharfbuzz0b 2.7.4-1 ii libhyphen0 2.8.8-7 ii libicu6767.1-7 ii libjavascriptcoregtk-4.0-18 2.40.1-1~deb11u1 ii libjpeg62-turbo 1:2.0.6-4 ii liblcms2-2 2.12~rc1-2 ii libmanette-0.2-00.2.5-1 ii libopenjp2-72.4.0-3 ii libpango-1.0-0 1.46.2-3 ii libpangocairo-1.0-0 1.46.2-3 ii libpng16-16 1.6.37-3 ii libseccomp2 2.5.1-1+deb11u1 ii libsecret-1-0 0.20.4-2 ii libsoup2.4-12.72.0-2 ii libsqlite3-03.34.1-3 ii libstdc++6 10.2.1-6 ii libsystemd0 247.3-7+deb11u2 ii libtasn1-6 4.16.0-2+deb11u1 ii libwayland-client0 1.18.0-2~exp1.1 ii libwayland-egl1 1.18.0-2~exp1.1 ii libwayland-server0 1.18.0-2~exp1.1 ii libwebp60.6.1-2.1 ii libwebpdemux2 0.6.1-2.1 ii libwoff11.0.2-1+b1 ii libwpe-1.0-11.10.0-2 ii libwpebackend-fdo-1.0-1 1.8.0-1 ii libx11-62:1.7.2-1 ii libxcomposite1 1:0.4.5-1 ii libxdamage1 1:1.1.5-2 ii libxml2 2.9.10+dfsg-6.7+deb11u4 ii libxrender1 1:0.9.10-1 ii libxslt1.1 1.1.34-4+deb11u1 ii libxt6 1:1.2.0-1 ii xdg-dbus-proxy 0.1.2-2 ii zlib1g 1:1.2.11.dfsg-2+deb11u2 Versions of packages libwebkit2gtk-4.0-37 recommends: ii gstreamer1.0-gl 1.18.4-2 ii gstreamer1.0-libav1.18.4-3 ii gstreamer1.0-plugins-bad 1.18.4-3 ii libgl1-mesa-dri 20.3.5-1 ii xdg-desktop-portal-gtk1.8.0-1 Versions of packages libwebkit2gtk-4.0-37 suggests: pn gstreamer1.0-alsa -- no debconf information
Bug#1003352: Workaround for #1003352
Same problem here, efivarfs isn't mounted. Also, mdadm must be called
before running cryptsetup, at least on my system (crypted rootfs on
raid).
Solution: Create /target/etc/initramfs-tools/scripts/init-premount/fakeraid
(chmod +x),
then rebuild the initrd: in-target update-initramfs -u -k all
#!/bin/sh -e
PREREQS=""
prereqs() { echo "$PREREQS"; }
case "$1" in
prereqs)
prereqs
exit 0
;;
esac
. /scripts/functions
log_begin_msg "Assembling fake-raid"
mount efivarfs /sys/firmware/efi/efivars -t efivarfs -o
rw,nosuid,nodev,noexec,relatime
mdadm --assemble --scan
log_end_msg "fake-raid set up"
signature.asc
Description: PGP signature
Bug#990428: Add fixed package to stable?
Hello, could the fixed version 2.13 please be added to stable/bullseye? So far it appears to work for me; 2.12 doesn't. Cheers signature.asc Description: PGP signature
Bug#995471: Backport virt-top to bullseye
Package: virt-top Version: 1.0.9-1.1 Hello, virt-top didn't make it into bullseye: https://tracker.debian.org/news/1196264/virt-top-removed-from-testing/ Later, a fixed version was uploaded into unstable (#973188). That one compiles without modifications on bullseye. Could it please be uploaded into bullseye-backports? Cheers Jörn Heissler signature.asc Description: PGP signature
Bug#956189: Upgrade to 2.1.0
Hello, the issue was fixed in release 2.1.0 Cheers signature.asc Description: PGP signature
Bug#939294: network-manager: After upgrade to 1.20.0-1, mac address of wlan0 is randomized
On Tue, Sep 03, 2019 at 00:55:59 +0200, Michael Biebl wrote: > network-manager did always randomize the mac, unless you have a package > explicitly overriding this behaviour. After a reboot it worked again. I had a closer looks at the logs: It appears like NM always changes mac address before scanning: device (wlan0): set-hw-addr: set MAC address to 7E:83:4F:92:E9:72 (scanning) And changing it back when connecting: device (wlan0): set-hw-addr: reset MAC address to <---redacted---> (preserve) I wasn't even aware of the feature, but it makes sense. That happened before the upgrade too. During the upgrade, NM started a scan for some reason and changed the address. Then the NM process was terminated. The new instance of NM assumed wrongly that the current mac address is the real one. Logs looked like: device (wlan0): set-hw-addr: set MAC address to C6:E8:D3:FB:55:4B (scanning) exiting (success) --- NetworkManager (version 1.20.0) is starting... (after a restart) device (wlan0): set-hw-addr: set MAC address to 52:8C:79:7C:65:5E (scanning) device (wlan0): set-hw-addr: reset MAC address to C6:E8:D3:FB:55:4B (preserve) The flaw can be triggered easily: # systemctl restart wpa_supplicant.service; sleep 1.5; systemctl restart NetworkManager.service Restart of wpa_supplicant.service causes a rescan which appears to take about 3 seconds. During rescan, NM is restarted. Afterwards the MAC address is wrong. A workaround without reboot is to stop NM, change the mac adress manually (ip link set dev wlan0 down; ip link set dev wlan0 address zz:yy:xx:ww:vv:uu), then start NM again. So, I believe this is really a bug in NetworkManager which should be fixed. But might well be an upstream bug. signature.asc Description: PGP signature
Bug#939294: network-manager: After upgrade to 1.20.0-1, mac address of wlan0 is randomized
Package: network-manager Version: 1.20.0-1 Severity: important Hello, I upgraded several packages, including network-manager (1.18.0-3 -> 1.20.0-1). During the upgrade, my wifi connection disconnected and wouldn't connect again. Luckily I wasn't doing the upgrade from remote ;-) It appears that the mac address of my wlan0 device is now changed and my wifi router refused the new address because it got a whitelist. There is no mention of this behaviour change in the docs and it's unclear how to disable/control this feature. I suggest that this change is reverted or at least users should be made aware of it. And users should be pointed at relevant documentation. In fact I'm not sure that network-manager is the culprit, but it's a likely candidate. Thanks Jörn Heissler -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) 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 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages network-manager depends on: ii adduser3.118 ii dbus 1.12.16-1 ii init-system-helpers1.57 ii libaudit1 1:2.8.5-2 ii libbluetooth3 5.50-1+b1 ii libc6 2.28-10 ii libcurl3-gnutls7.65.3-1 ii libglib2.0-0 2.60.6-2 ii libgnutls303.6.9-4 ii libjansson42.12-1 ii libmm-glib01.10.4-0.1 ii libndp01.6-1+b1 ii libnewt0.520.52.21-3 ii libnm0 1.20.0-1 ii libpam-systemd 242-5 ii libpolkit-agent-1-00.105-26 ii libpolkit-gobject-1-0 0.105-26 ii libpsl50.20.2-2 ii libreadline8 8.0-3 ii libselinux12.9-2+b2 ii libsystemd0242-5 ii libteamdctl0 1.28-1+b1 ii libudev1 242-5 ii libuuid1 2.34-0.1 ii policykit-10.105-26 ii udev 242-5 ii wpasupplicant 2:2.9-1 Versions of packages network-manager recommends: ii crda 3.18-1 ii dnsmasq-base [dnsmasq-base] 2.80-1+b1 ii iptables 1.8.3-2 ii modemmanager 1.10.4-0.1 ii ppp 2.4.7-2+4.1+b1 Versions of packages network-manager suggests: ii isc-dhcp-client 4.4.1-2 pn libteam-utils -- no debconf information
Bug#932428: , Bug#932767, Bug#932781: gnome-shell crashes involving monitor changes
On Tue, Jul 30, 2019 at 11:19:38 +0100, Simon McVittie wrote: > I've found an upstream commit that might be the solution for all of these > crashes. Please try mutter 3.30.2-8 and gnome-shell 3.30.2-10 when they > become available in unstable. After upgrading you will need to log out > and back in (or reboot) for the new code to be used. > > The actual fix is in mutter, but the updated gnome-shell has a different > crash fix, and while you're restarting GNOME anyway we might as well get > wider testing for the updated gnome-shell too... I now installed gnome-shell==3.30.2-10 and mutter==3.30.2-8. No further crashes yet. Should there be another crash, I'll let you know. Thank you! signature.asc Description: PGP signature
Bug#932428: Also crashes when (dis)connecting external monitor
Hello, gnome-shell crashes when I suspend my laptop or when I connect an external monitor or disconnect it. Jul 22 08:05:13 debian kernel: [88227.622753] traps: gnome-shell[4462] general protection ip:7f09fbd74de1 sp:7fff35fb3b60 error:0 in libwayland-server.so.0.1.0[7f09fbd74000+7000] Jul 22 07:38:41 debian kernel: [86635.326924] gnome-shell[4610]: segfault at 19071e08 ip 7f1f774fee04 sp 7ffe55d54720 error 4 in libwayland-server.so.0.1.0 (deleted)[7f1f774fe000+7000] Jul 21 18:57:05 debian kernel: [40939.580567] traps: gnome-shell[1387] general protection ip:7f8b87482e04 sp:7ffdbbd5a020 error:0 in libwayland-server.so.0.1.0[7f8b87482000+7000] Jul 21 18:57:22 debian kernel: [40956.582960] traps: gnome-shell[4217] general protection ip:7f6e3c9bcdc3 sp:77381828 error:0 in libgbm.so.1.0.0[7f6e3c9bc000+7000] Jul 21 18:57:23 debian kernel: [40957.033029] gnome-shell[4031]: segfault at 7fd0e84e3590 ip 7fd0e84e3590 sp 7ffea58bc328 error 15 Jul 20 23:05:25 debian kernel: [2440020.265881] gnome-shell[1263]: segfault at 1020 ip 7f88ca7b2de1 sp 7ffe664d4d10 error 4 in libwayland-server.so.0.1.0[7f88ca7b2000+7000] It's always gnome-shell that crashes, no other processes crash. It appears to crash in totally random places. This happens since my last upgrade on 2019-07-20 18:58:42; previous (still working) upgrade was on 2019-07-12 18:02:58. List of libraries upgraded on 2019-07-20 that are loaded by the gnome-shell process: libegl-mesa0:amd64 (18.3.6-2, 19.1.2-1) libevdev2:amd64 (1.6.0+dfsg-1, 1.7.0+dfsg-1) libexpat1:amd64 (2.2.6-2, 2.2.7-1) libgbm1:amd64 (18.3.6-2, 19.1.2-1) libgcc1:amd64 (1:9.1.0-8, 1:9.1.0-10) libglapi-mesa:amd64 (18.3.6-2, 19.1.2-1) libglib2.0-0:amd64 (2.58.3-3, 2.60.5-1) libgpg-error0:amd64 (1.36-2, 1.36-7) libgssapi-krb5-2:amd64 (1.17-4, 1.17-5) libgstreamer1.0-0:amd64 (1.14.4-1, 1.16.0-2) libgtk-3-0:amd64 (3.24.5-1, 3.24.10-1) libharfbuzz0b:amd64 (2.4.0-2, 2.5.3-1) libk5crypto3:amd64 (1.17-4, 1.17-5) libkrb5-3:amd64 (1.17-4, 1.17-5) libkrb5support0:amd64 (1.17-4, 1.17-5) libnss-myhostname:amd64 (241-6, 241-7) libseccomp2:amd64 (2.3.3-4, 2.4.1-2) libstdc++6:amd64 (9.1.0-8, 9.1.0-10) libsystemd0:amd64 (241-6, 241-7) libtasn1-6:amd64 (4.13-3, 4.13-4) libtinfo6:amd64 (6.1+20181013-2, 6.1+20190713-1) libudev1:amd64 (241-6, 241-7) libxcursor1:amd64 (1:1.1.15-2, 1:1.2.0-2) Perhaps it's one of those; gnome-shell is at 3.30.2-9 and has last been upgraded on Apr 30. Cheers signature.asc Description: PGP signature
Bug#928284: libxalan2-java: Breaks JOSM with javaws: Provider org.apache.xerces.jaxp.validation.XMLSchemaFactory not found
Source: libxalan2-java Severity: normal Hello, when libxalan2-java is installed, I cannot run JOSM (https://josm.openstreetmap.de/) through javaws anymore. Reproduce: * apt install icedtea-netx libxalan2-java * Click https://josm.openstreetmap.de/download/josm.jnlp in your browser * Alternatively: Download the file and exec: javaws josm.jnlp Versions: * libxalan2-java 2.7.2-2 * openjdk-11-jre 11.0.3+7-4 * icedtea-netx 1.7.2-2 Error details: netx: Launch Error: Could not launch JNLP file. ( (Provider for class javax.xml.validation.SchemaFactory cannot be created (javax.xml.validation.SchemaFactory: Provider org.apache.xerces.jaxp.validation.XMLSchemaFactory not found))) net.sourceforge.jnlp.LaunchException: Fatal: Launch Error: Could not launch JNLP file. The application has not been initialized, for more information execute javaws/browser from the command line and send a bug report. at java.desktop/net.sourceforge.jnlp.Launcher.launchApplication(Launcher.java:582) at java.desktop/net.sourceforge.jnlp.Launcher$TgThread.run(Launcher.java:945) Caused by: java.lang.reflect.InvocationTargetException at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at java.desktop/net.sourceforge.jnlp.Launcher.launchApplication(Launcher.java:576) ... 1 more Caused by: javax.xml.validation.SchemaFactoryConfigurationError: Provider for class javax.xml.validation.SchemaFactory cannot be created at java.xml/javax.xml.validation.SchemaFactoryFinder.findServiceProvider(SchemaFactoryFinder.java:350) at java.xml/javax.xml.validation.SchemaFactoryFinder._newFactory(SchemaFactoryFinder.java:217) at java.xml/javax.xml.validation.SchemaFactoryFinder.newFactory(SchemaFactoryFinder.java:144) at java.xml/javax.xml.validation.SchemaFactory.newInstance(SchemaFactory.java:245) at org.openstreetmap.josm.tools.XmlUtils.newXmlSchemaFactory(XmlUtils.java:55) at org.openstreetmap.josm.data.preferences.PreferencesReader.validateXML(PreferencesReader.java:97) at org.openstreetmap.josm.data.preferences.PreferencesReader.validateXML(PreferencesReader.java:85) at org.openstreetmap.josm.data.Preferences.load(Preferences.java:411) at org.openstreetmap.josm.data.Preferences.init(Preferences.java:522) at org.openstreetmap.josm.gui.MainApplication.mainJOSM(MainApplication.java:782) at org.openstreetmap.josm.gui.MainApplication$3.processArguments(MainApplication.java:277) at org.openstreetmap.josm.gui.MainApplication.main(MainApplication.java:704) ... 6 more Caused by: java.util.ServiceConfigurationError: javax.xml.validation.SchemaFactory: Provider org.apache.xerces.jaxp.validation.XMLSchemaFactory not found at java.base/java.util.ServiceLoader.fail(ServiceLoader.java:588) at java.base/java.util.ServiceLoader$LazyClassPathLookupIterator.nextProviderClass(ServiceLoader.java:1211) at java.base/java.util.ServiceLoader$LazyClassPathLookupIterator.hasNextService(ServiceLoader.java:1220) at java.base/java.util.ServiceLoader$LazyClassPathLookupIterator$1.run(ServiceLoader.java:1267) at java.base/java.util.ServiceLoader$LazyClassPathLookupIterator$1.run(ServiceLoader.java:1266) at java.base/java.security.AccessController.doPrivileged(Native Method) at java.base/java.util.ServiceLoader$LazyClassPathLookupIterator.hasNext(ServiceLoader.java:1269) at java.base/java.util.ServiceLoader$2.hasNext(ServiceLoader.java:1299) at java.base/java.util.ServiceLoader$3.hasNext(ServiceLoader.java:1384) at java.xml/javax.xml.validation.SchemaFactoryFinder$2.run(SchemaFactoryFinder.java:339) at java.xml/javax.xml.validation.SchemaFactoryFinder$2.run(SchemaFactoryFinder.java:335) at java.base/java.security.AccessController.doPrivileged(Native Method) at java.xml/javax.xml.validation.SchemaFactoryFinder.findServiceProvider(SchemaFactoryFinder.java:335) ... 17 more Thanks in advance! -- System Information: Debian Release: 10.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores) 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 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#850669: ansible: Enable python3
Hello! I'd really love to see ansible with python3 in Buster. I've been using py3 on controllers and targets for some time now and I'm quite happy. Problems usually only arise if third party modules haven't been ported to py3 yet. Is there anything I can help with? Thanks, Jörn signature.asc Description: PGP signature
Bug#908120: gnome-terminal: Cursor disappears when changing or moving window
Package: gnome-terminal Version: 3.28.2-1 Severity: normal Hello, when I start a new gnome-terminal window, it got a text cursor just as usual. When I resize or move the terminal window or switch to a different window (terminal or other), the cursor disappears. And it won't come back. I tried different options for the cursor (shape, blinking), but doesn't make any difference. Typing "reset" in the shell doesn't help. Neither does the menu option "Reset". Only workaround so far: When I switch the terminal tab, the cursor comes back. But only until I switch/move/resize windows again. No other software besides gnome-terminal appears to be affected. This started happening after upgrading lots of packages, so I have no idea which one causes the issue. Cheers -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.17.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gnome-terminal depends on: ii dbus-user-session [default-dbus-session-bus] 1.12.10-1 ii dbus-x11 [dbus-session-bus] 1.12.10-1 ii dconf-gsettings-backend [gsettings-backend] 0.30.0-1 ii gnome-terminal-data 3.28.2-1 ii gsettings-desktop-schemas 3.28.0-1 ii libatk1.0-0 2.28.1-1 ii libc6 2.27-6 ii libdconf1 0.30.0-1 ii libglib2.0-0 2.58.0-2 ii libgtk-3-03.24.0-1 ii libpango-1.0-01.42.4-2 ii libuuid1 2.32.1-0.1 ii libvte-2.91-0 0.52.2-1 ii libx11-6 2:1.6.6-1 Versions of packages gnome-terminal recommends: ii gvfs 1.36.2-1 pn nautilus-extension-gnome-terminal ii yelp 3.30.0-1 gnome-terminal suggests no packages. -- no debconf information
Bug#818065: live-config / console-setup issue
On Thu, Mar 16, 2017 at 07:03:04PM +0200, Anton Zinoviev wrote: > ls --full-time /etc/console-setup/cached* /etc/default/console-setup > /etc/default/keyboard This is from a configuration where I hard coded the two files in /etc/default/ and did not set the keyboard parameters elsewhere. Files in /etc/default/ aren't overwritten in the booted system (i.e. looks same in booted system): -rw-r--r-- root/root 4024 2017-03-17 06:50 squashfs-root/etc/console-setup/cached_UTF-8_del.kmap.gz -rw-r--r-- root/root 4147 2017-03-17 06:50 squashfs-root/etc/console-setup/cached_Uni2-Fixed16.psf.gz -rwxr-xr-x root/root 471 2017-03-17 06:50 squashfs-root/etc/console-setup/cached_setup_font.sh -rwxr-xr-x root/root 174 2017-03-17 06:50 squashfs-root/etc/console-setup/cached_setup_keyboard.sh -rwxr-xr-x root/root73 2017-03-17 06:50 squashfs-root/etc/console-setup/cached_setup_terminal.sh -rw-rw-r-- root/root 136 2017-03-14 09:47 squashfs-root/etc/default/console-setup -rw-rw-r-- root/root 172 2017-03-12 17:39 squashfs-root/etc/default/keyboard Same image, but this time I set on kernel command line: locales=de_DE.UTF-8 keyboard-layouts=de keyboard-variants=nodeadkeys The file date is newer, still keyboard layout not set. -rw-rw-r-- 1 root root 136 2017-03-14 09:47:49.0 +0100 console-setup -rw-rw-r-- 1 root root 172 2017-03-17 07:12:20.128082454 +0100 keyboard -rwxr-xr-x 1 root root 471 2017-03-17 06:50:38.0 +0100 /etc/console-setup/cached_setup_font.sh -rwxr-xr-x 1 root root 174 2017-03-17 06:50:38.0 +0100 /etc/console-setup/cached_setup_keyboard.sh -rwxr-xr-x 1 root root 73 2017-03-17 06:50:38.0 +0100 /etc/console-setup/cached_setup_terminal.sh -rw-r--r-- 1 root root 4147 2017-03-17 06:50:38.0 +0100 /etc/console-setup/cached_Uni2-Fixed16.psf.gz -rw-r--r-- 1 root root 4024 2017-03-17 06:50:38.0 +0100 /etc/console-setup/cached_UTF-8_del.kmap.gz I made a new image, without the hard coded keyboard + console-setup files. Contents in squashfs: "keyboard" has XKBLAYOUT="us", so not what I want. -rwxr-xr-x 1 root root 471 2017-03-17 07:11:05.0 +0100 squashfs-root/etc/console-setup/cached_setup_font.sh -rwxr-xr-x 1 root root 174 2017-03-17 07:11:05.0 +0100 squashfs-root/etc/console-setup/cached_setup_keyboard.sh -rwxr-xr-x 1 root root 73 2017-03-17 07:11:05.0 +0100 squashfs-root/etc/console-setup/cached_setup_terminal.sh -rw-r--r-- 1 root root 4147 2017-03-17 07:11:04.0 +0100 squashfs-root/etc/console-setup/cached_Uni2-Fixed16.psf.gz -rw-r--r-- 1 root root 4024 2017-03-17 07:11:04.0 +0100 squashfs-root/etc/console-setup/cached_UTF-8_del.kmap.gz -rw-r--r-- 1 root root 285 2017-03-17 07:11:04.0 +0100 squashfs-root/etc/default/console-setup -rw-r--r-- 1 root root 150 2017-03-17 07:10:59.0 +0100 squashfs-root/etc/default/keyboard After I boot (still same kernel command line parameters): -rwxr-xr-x 1 root root 471 2017-03-17 07:11:05.0 +0100 /etc/console-setup/cached_setup_font.sh -rwxr-xr-x 1 root root 174 2017-03-17 07:11:05.0 +0100 /etc/console-setup/cached_setup_keyboard.sh -rwxr-xr-x 1 root root 73 2017-03-17 07:11:05.0 +0100 /etc/console-setup/cached_setup_terminal.sh -rw-r--r-- 1 root root 4147 2017-03-17 07:11:04.0 +0100 /etc/console-setup/cached_Uni2-Fixed16.psf.gz -rw-r--r-- 1 root root 4024 2017-03-17 07:11:04.0 +0100 /etc/console-setup/cached_UTF-8_del.kmap.gz -rw-r--r-- 1 root root 285 2017-03-17 07:11:04.0 +0100 /etc/default/console-setup -rw-r--r-- 1 root root 160 2017-03-17 07:18:22.112087333 +0100 /etc/default/keyboard Here is an excerpt from /var/log/syslog: Mar 17 07:18:24 localhost systemd[1]: Reached target Local File Systems. Mar 17 07:18:24 localhost systemd[1]: Starting live-config contains the components that configure a live system during the boot process (late userspace) Mar 17 07:18:24 localhost systemd[1]: Starting Create Volatile Files and Directories... Mar 17 07:18:24 localhost systemd[1]: Starting Raise network interfaces... Mar 17 07:18:24 localhost systemd[1]: Starting Set console font and keymap... Mar 17 07:18:24 localhost systemd[1]: Started Create Volatile Files and Directories. Mar 17 07:18:24 localhost systemd[1]: Starting Update UTMP about System Boot/Shutdown... Mar 17 07:18:24 localhost systemd[1]: Starting Network Time Synchronization... Mar 17 07:18:24 localhost systemd[1]: Started Set console font and keymap. Mar 17 07:18:24 localhost systemd[1]: Started Update UTMP about System Boot/Shutdown. Mar 17 07:18:24 localhost systemd[1]: Started Network Time Synchronization. Mar 17 07:18:24 localhost systemd[1]: Reached target System Time Synchronized. Mar 17 07:18:24 localhost live-config[393]: live-config: debconf hostnameDevice "eth0" does not exist. Mar 17 07:18:24 localhost live-config[393]: Device "eth0" does not exist. Mar 17 07:18:24 localhost live-config[393]:
Bug#818065: live-config / console-setup issue
Hello, I had the same issue. Running a live-build image, nothing worked to setup the keyboard layout. I found out that my image contained /etc/console-setup/cached_* files. What really helped was adding a hook in live-build to remove those files, before the image was built. $ cat config/hooks/live/0900-cleanup.hook.chroot #!/bin/sh rm -f -- /etc/console-setup/cached_* Cheers signature.asc Description: PGP signature
