Bug#1006622: Acknowledgement (network-manager: Upgrade from 1.34.0-2 to any higher version breaks IPv6 config on mobile broadband)

[Bjørn Bürger]

Current Workaround, if you are affected by this (on debian unstable):

Use version 1.34.0-2 from
https://snapshot.debian.org/archive/debian/20220121T093818Z

Bug#1006622: Acknowledgement (network-manager: Upgrade from 1.34.0-2 to any higher version breaks IPv6 config on mobile broadband)

[Bjørn Bürger]

Upstream Bugreport:

https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/944

Bug#1004447: Acknowledgement (modemmanager: Sierra Wireless EM7455 stops working after upgrade to 1.18.4-1 (stays in FCC lock))

[Bjørn Bürger]

Argh! Nevermind, just figured it out.

It's actually documented in the original NEWS file, but it's
not very obvious to the user, why suddenly the modem disappears.

This is the solution:

ln -sft /etc/ModemManager/fcc-unlock.d 
/usr/share/ModemManager/fcc-unlock.available.d/*


and it's also documented quite nicely on the modemmanager.org
website. Maybe debian should add a prominent Warning, because
this will break modemmanager heavily for a lot of non-technical
people:

- cite from NEWS.gz ---

ModemManager 1.18.4
---

 * A new FCC unlock operation management via external scripts is 
introduced,
   which will avoid to automatically unlock FCC locked devices unless 
the user
   has configured the operation manually, or unless an official 
vendor-provided

   FCC unlock tool is found in the system.

   Please refer to the following URL for full details:
   https://modemmanager.org/docs/modemmanager/fcc-unlock/

   The following changes should be taken into account by distribution 
packagers:
   ** A set of FCC unlock scripts named as the specific vendor 'vid' 
will be

  installed in ${datadir}/ModemManager/fcc-unlock.available.d.
   ** A set of symlinks is created named as the specific device 
'vid:pid', and

  pointing to the per-vendor 'vid' files, in the same location inside
  ${datadir}.
   ** A new ${sysconfdir}/ModemManager/fcc-unlock.d directory is 
created, where
  users will manually install additional symlinks to the scripts 
shipped in

  ${datadir}.
   ** A new ${libdir}/ModemManager/fcc-unlock.d directory is created, where
  vendors will install their own official FCC unlock tools.
   ** Both fcc-unlock.d directories should be empty on a new install, 
and their

  contents (if any) should not be removed on ModemManager upgrades.

---

Have a nice weekend.
Bjørn

Bug#948691: firefox: breaks .config/mimeapps.list if started by thunderbird, breaking xdg-settings for whole system

[Bjørn Bürger]

Package: firefox
Version: 72.0.1-1
Severity: important

Hi,

if (and only if) firefox is spawned by clicking a link,
something in the detection code for "default browser"
setting is going crazy.

Steps to reproduce:

1) make firefox default webbrowser on a clean system
   and check current setting:

   $ xdg-settings get default-web-browser
   firefox.desktop

   $ cat .config/mimeapps.list

   [Default Applications]
   text/html=firefox.desktop
   x-scheme-handler/http=firefox.desktop
   x-scheme-handler/https=firefox.desktop
   x-scheme-handler/about=firefox.desktop
   x-scheme-handler/unknown=firefox.desktop

   This is fine.

2) start firefox, select preferences.
   It will tell you that ff is default

3) stop firefox

4) start thunderbird, click on any http(s) link
   wait for firefox to come up and check
   preferences again.

   Now, it will tell you, that it is NOT the default
   browser.

   However, it still is:

   $ xdg-settings get default-web-browser
   firefox.desktop

   $ cat .config/mimeapps.list

   [Default Applications]
   text/html=firefox.desktop
   x-scheme-handler/http=firefox.desktop
   x-scheme-handler/https=firefox.desktop
   x-scheme-handler/about=firefox.desktop
   x-scheme-handler/unknown=firefox.desktop


5) In firefox preferences, hit the "make default browser" button.
   Now, everything gets crazy:

   $ xdg-settings get default-web-browser
   thunderbird.desktop

   $ cat .config/mimeapps.list
   [Default Applications]
   text/html=thunderbird.desktop
   x-scheme-handler/http=thunderbird.desktop
   x-scheme-handler/https=thunderbird.desktop
   x-scheme-handler/about=firefox.desktop
   x-scheme-handler/unknown=firefox.desktop
   x-scheme-handler/ftp=thunderbird.desktop
   x-scheme-handler/chrome=thunderbird.desktop
   application/x-extension-htm=thunderbird.desktop
   application/x-extension-html=thunderbird.desktop
   application/x-extension-shtml=thunderbird.desktop
   application/xhtml+xml=thunderbird.desktop
   application/x-extension-xhtml=thunderbird.desktop
   application/x-extension-xht=thunderbird.desktop

   [Added Associations]
   x-scheme-handler/http=thunderbird.desktop;
   x-scheme-handler/https=thunderbird.desktop;
   x-scheme-handler/ftp=thunderbird.desktop;
   x-scheme-handler/chrome=thunderbird.desktop;
   text/html=thunderbird.desktop;
   application/x-extension-htm=thunderbird.desktop;
   application/x-extension-html=thunderbird.desktop;
   application/x-extension-shtml=thunderbird.desktop;
   application/xhtml+xml=thunderbird.desktop;
   application/x-extension-xhtml=thunderbird.desktop;
   application/x-extension-xht=thunderbird.desktop;

6) Now, links in any application using xdg-open
   won't work anymore. Thunderbird just crashes
   or ignores the load requests.

Please note:

* This Bug also affects firefox.esr
* If started from any other applikation, firefox behaves
  just normal. So far, only Thnuderbird triggers this
  behaviour.

-- Package-specific info:


-- Addons package information
-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages firefox depends on:
ii  debianutils   4.9.1
ii  fontconfig2.13.1-2+b1
ii  libatk1.0-0   2.34.1-1
ii  libc6 2.29-8
ii  libcairo-gobject2 1.16.0-4
ii  libcairo2 1.16.0-4
ii  libdbus-1-3   1.12.16-2
ii  libdbus-glib-1-2  0.110-5
ii  libevent-2.1-72.1.11-stable-1
ii  libffi6   3.2.1-9
ii  libfontconfig12.13.1-2+b1
ii  libfreetype6  2.10.1-2
ii  libgcc1   1:9.2.1-22
ii  libgdk-pixbuf2.0-02.40.0+dfsg-2
ii  libglib2.0-0  2.62.4-1
ii  libgtk-3-03.24.13-1
ii  libnspr4  2:4.24-1
ii  libnss3   2:3.49-1
ii  libpango-1.0-01.42.4-8
ii  libsqlite3-0  3.30.1+fossil191229-1
ii  libstartup-notification0  0.12-6
ii  libstdc++69.2.1-22
ii  libx11-6  2:1.6.8-1
ii  libx11-xcb1   2:1.6.8-1
ii  libxcb-shm0   1.13.1-3
ii  libxcb1   1.13.1-3
ii  libxcomposite11:0.4.4-2
ii  libxdamage1   1:1.1.5-1
ii  libxext6  2:1.3.3-1+b2
ii  libxfixes31:5.0.3-1
ii  libxrender1   1:0.9.10-1
ii  libxt61:1.1.5-1+b3
ii  procps2:3.3.15-2+b1
ii  zlib1g1:1.2.11.dfsg-1+b1

Versions of packages firefox recommends:
ii  libavcodec57  7:3.4.3-1
ii  libavcodec58  7:4.2.1-2+b1

Versions of packages firefox suggests:
ii  

Bug#883393: ITP: jool -- Open Source SIIT and NAT64 Translator for Linux

[Bjørn Bürger]

On 12/03/2017 02:38 PM, Bjoern Buerger wrote:
> Upstream is currently discussing
> a license change for that matter, so it might take some time 
> before we can actually start uploading packages.

Just a short Update:

* The license issue seems to be solved.

* Starting with 3.5.6, all future versions
  will be licensed under the GPLv2 license.

* Details:
  https://github.com/NICMx/Jool/issues/258

Bjørn

Bug#867542: [Enigmail] 'invalid language tag' since 30c1fe69 [was: Re: Bug#867542: enigmail: can't decrypt messages in thunderbird]

[Bjørn Bürger]

Hi,

I stumbled over the same bug and could verify the described behaviour:

* Setting locale to C.UTF-8 leads to an empty message window after
decrypting.

* Setting locale to e.g. de_DE.utf8 fixes the problem.

* Patrick's patch fixes the issue for me with C.UTF-8 as well.

On Wed, 12 Jul 2017 08:44:22 +0200 Patrick Brunschwig
 wrote:
> > The line you're getting an error on was definitely changed between 1.9.7
> > and 1.9.8 (it was changed in 30c1fe69a7c62007f925d760efc832884aed4412,
> > which overhauls the time calculations).

For me, these Versions are broken:

 2:1.9.8.1-1 990
 2:1.9.8.1-1~deb9u1 500

This version is ok:

 2:1.9.7-2 500

-- bbu