[Desktop-packages] [Bug 2053110] Re: openjdk-8 402 fails to install in focal, jammy, mantic on i386
Hi Vladimir, rmadison says it’s fixed now and it’s available for i386 again, so I undid the workaround addition. I’ve just uploaded 8u412, but I’ve re-enabled tests for Debian. Due to your situation with the i386 packages, you’ll have to regenerate d/control on noble to get the i386 exclusion (I hope I got the syntax, with both architecture and profile specification, right). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to java-atk-wrapper in Ubuntu. https://bugs.launchpad.net/bugs/2053110 Title: openjdk-8 402 fails to install in focal, jammy, mantic on i386 Status in java-atk-wrapper package in Ubuntu: Confirmed Status in openjdk-8 package in Ubuntu: Fix Released Status in openjdk-8 package in Debian: Fix Released Bug description: openjdk-8 402 fails to install in focal, jammy, mantic on i386 due to dependency on java-atk-bridge. This dependency was introduced by dropping condition present in 392: -- ifeq ($(derivative),Ubuntu) ifeq ($(DEB_HOST_ARCH),i386) ifeq (,$(filter $(distrel),precise trusty xenial bionic)) with_bridge = endif endif endif -- Note: java-atk-wrapper is present in noble on i386 This is a regression introduced in 8u402-ga-2: * Restore M-A installability of focal/i386 package (LP#1916327) by adding xenial, bionic, focal, jammy to the list of releases built with the ATK bridge, but not enabling it by default; keep jessie on, stretch and sid and mantic/noble off the list: please report bugs for issues with the bridge, so sthibault can find, debug, fix them See LP: #1916327 The alternative is to publish atk-wrapper for i386 in mantic, jammy and focal. Options: a) rollback the fix in Ubuntu b) publish atk-wrapper To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/java-atk-wrapper/+bug/2053110/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2053110] Re: openjdk-8 402 fails to install in focal, jammy, mantic on i386
(FWIW, last time I looked, it _did_ exist in noble) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to java-atk-wrapper in Ubuntu. https://bugs.launchpad.net/bugs/2053110 Title: openjdk-8 402 fails to install in focal, jammy, mantic on i386 Status in java-atk-wrapper package in Ubuntu: Confirmed Status in openjdk-8 package in Ubuntu: Fix Released Status in openjdk-8 package in Debian: Fix Released Bug description: openjdk-8 402 fails to install in focal, jammy, mantic on i386 due to dependency on java-atk-bridge. This dependency was introduced by dropping condition present in 392: -- ifeq ($(derivative),Ubuntu) ifeq ($(DEB_HOST_ARCH),i386) ifeq (,$(filter $(distrel),precise trusty xenial bionic)) with_bridge = endif endif endif -- Note: java-atk-wrapper is present in noble on i386 This is a regression introduced in 8u402-ga-2: * Restore M-A installability of focal/i386 package (LP#1916327) by adding xenial, bionic, focal, jammy to the list of releases built with the ATK bridge, but not enabling it by default; keep jessie on, stretch and sid and mantic/noble off the list: please report bugs for issues with the bridge, so sthibault can find, debug, fix them See LP: #1916327 The alternative is to publish atk-wrapper for i386 in mantic, jammy and focal. Options: a) rollback the fix in Ubuntu b) publish atk-wrapper To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/java-atk-wrapper/+bug/2053110/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2053110] Re: openjdk-8 402 fails to install in focal, jammy, mantic on i386
oh ffs, it’s missing (again?) in noble, too? I’ll add noble to the workaround for 8u412-ga-1, which I’m working on r/n. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to java-atk-wrapper in Ubuntu. https://bugs.launchpad.net/bugs/2053110 Title: openjdk-8 402 fails to install in focal, jammy, mantic on i386 Status in java-atk-wrapper package in Ubuntu: Confirmed Status in openjdk-8 package in Ubuntu: Fix Released Status in openjdk-8 package in Debian: Fix Released Bug description: openjdk-8 402 fails to install in focal, jammy, mantic on i386 due to dependency on java-atk-bridge. This dependency was introduced by dropping condition present in 392: -- ifeq ($(derivative),Ubuntu) ifeq ($(DEB_HOST_ARCH),i386) ifeq (,$(filter $(distrel),precise trusty xenial bionic)) with_bridge = endif endif endif -- Note: java-atk-wrapper is present in noble on i386 This is a regression introduced in 8u402-ga-2: * Restore M-A installability of focal/i386 package (LP#1916327) by adding xenial, bionic, focal, jammy to the list of releases built with the ATK bridge, but not enabling it by default; keep jessie on, stretch and sid and mantic/noble off the list: please report bugs for issues with the bridge, so sthibault can find, debug, fix them See LP: #1916327 The alternative is to publish atk-wrapper for i386 in mantic, jammy and focal. Options: a) rollback the fix in Ubuntu b) publish atk-wrapper To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/java-atk-wrapper/+bug/2053110/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020814] Re: xmllint does not recognize emdash ( )
Hmm. I normally use libxml2 via xmlstarlet which has a somewhat nicer UX
than xmllint.
My guess is that you didn’t give a DTD, so it could only check that all
present entities are syntactically valid, but not expand them.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libxml2 in Ubuntu.
https://bugs.launchpad.net/bugs/2020814
Title:
xmllint does not recognize emdash ()
Status in libxml2 package in Ubuntu:
Invalid
Bug description:
I'm using Ubuntu 20.04.2 LTS, x85_64, fully patched. I'm using DocBook to
build a PDF. One of the steps I use in my build script is to validate and
format the XML using xmllint from libxml2-utils
2.9.13+dfsg-1ubuntu0.3:
echo "Validating book..."
if ! xmllint --xinclude --noout --postvalid book.xml
then
echo "Validation failed. Exiting."
exit 1
fi
echo "Complete."
echo "Formatting source code..."
for file in *.xml
do
if xmllint --format "${file}" --output "${file}.format"
then
mv "${file}.format" "${file}"
fi
done
echo "Complete."
When I added an emdash () the book failed to format:
Validating book...
Complete.
Formatting source code...
ch02.xml:58: parser error : Entity 'mdash' not defined
injections are remediated using several methods. And two output devices
^
ch02.xml:58: parser error : Entity 'mdash' not defined
methods. And two output devices the printer and plaintext email
^
Complete.
The text is:
... And two output devices the printer and plaintext
email do not require...
It seems like emdash should be recognized.
-
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 22.04.2 LTS
Release:22.04
Codename: jammy
-
$ xmllint --version
xmllint: using libxml version 20913
compiled with: Threads Tree Output Push Reader Patterns Writer SAXv1 FTP
HTTP DTDValid HTML Legacy C14N Catalog XPath XPointer XInclude Iconv ICU
ISO8859X Unicode Regexps Automata Schemas Schematron Modules Debug Zlib Lzma
$ command -v xmllint
/usr/bin/xmllint
$ dpkg -S /usr/bin/xmllint
libxml2-utils: /usr/bin/xmllint
$ apt-cache show libxml2-utils
Package: libxml2-utils
Architecture: amd64
Version: 2.9.13+dfsg-1ubuntu0.3
Multi-Arch: foreign
Priority: optional
Section: text
Source: libxml2
Origin: Ubuntu
Maintainer: Ubuntu Developers
Original-Maintainer: Debian XML/SGML Group
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 202
Depends: libc6 (>= 2.34), libxml2 (>= 2.9.0)
Filename:
pool/main/libx/libxml2/libxml2-utils_2.9.13+dfsg-1ubuntu0.3_amd64.deb
Size: 40192
MD5sum: 3ca7de07562010fcaabf255ea8fea9c4
SHA1: 128a9cfaff49e85f2ab08578f389eecb21f17766
SHA256: c279c07caf909545e2cedb7845b5ac652e0a70f9784e5faf799a1a01441b4649
SHA512:
51600d7206c9a5568fdaeee9adddbc48962fc094cc479f4bd42c0714b3725cd3200937f8c876a897db08fc50d891005d7dbabfb6ae12ad27ad6ed416f8b6a03d
Homepage: http://xmlsoft.org
...
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/2020814/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020814] Re: xmllint does not recognize emdash ( )
Yeah well, those portability problems were back in the 1990s when people
used latin1 or whatever codepages.
** Changed in: libxml2 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libxml2 in Ubuntu.
https://bugs.launchpad.net/bugs/2020814
Title:
xmllint does not recognize emdash ()
Status in libxml2 package in Ubuntu:
Invalid
Bug description:
I'm using Ubuntu 20.04.2 LTS, x85_64, fully patched. I'm using DocBook to
build a PDF. One of the steps I use in my build script is to validate and
format the XML using xmllint from libxml2-utils
2.9.13+dfsg-1ubuntu0.3:
echo "Validating book..."
if ! xmllint --xinclude --noout --postvalid book.xml
then
echo "Validation failed. Exiting."
exit 1
fi
echo "Complete."
echo "Formatting source code..."
for file in *.xml
do
if xmllint --format "${file}" --output "${file}.format"
then
mv "${file}.format" "${file}"
fi
done
echo "Complete."
When I added an emdash () the book failed to format:
Validating book...
Complete.
Formatting source code...
ch02.xml:58: parser error : Entity 'mdash' not defined
injections are remediated using several methods. And two output devices
^
ch02.xml:58: parser error : Entity 'mdash' not defined
methods. And two output devices the printer and plaintext email
^
Complete.
The text is:
... And two output devices the printer and plaintext
email do not require...
It seems like emdash should be recognized.
-
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 22.04.2 LTS
Release:22.04
Codename: jammy
-
$ xmllint --version
xmllint: using libxml version 20913
compiled with: Threads Tree Output Push Reader Patterns Writer SAXv1 FTP
HTTP DTDValid HTML Legacy C14N Catalog XPath XPointer XInclude Iconv ICU
ISO8859X Unicode Regexps Automata Schemas Schematron Modules Debug Zlib Lzma
$ command -v xmllint
/usr/bin/xmllint
$ dpkg -S /usr/bin/xmllint
libxml2-utils: /usr/bin/xmllint
$ apt-cache show libxml2-utils
Package: libxml2-utils
Architecture: amd64
Version: 2.9.13+dfsg-1ubuntu0.3
Multi-Arch: foreign
Priority: optional
Section: text
Source: libxml2
Origin: Ubuntu
Maintainer: Ubuntu Developers
Original-Maintainer: Debian XML/SGML Group
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 202
Depends: libc6 (>= 2.34), libxml2 (>= 2.9.0)
Filename:
pool/main/libx/libxml2/libxml2-utils_2.9.13+dfsg-1ubuntu0.3_amd64.deb
Size: 40192
MD5sum: 3ca7de07562010fcaabf255ea8fea9c4
SHA1: 128a9cfaff49e85f2ab08578f389eecb21f17766
SHA256: c279c07caf909545e2cedb7845b5ac652e0a70f9784e5faf799a1a01441b4649
SHA512:
51600d7206c9a5568fdaeee9adddbc48962fc094cc479f4bd42c0714b3725cd3200937f8c876a897db08fc50d891005d7dbabfb6ae12ad27ad6ed416f8b6a03d
Homepage: http://xmlsoft.org
...
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/2020814/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020814] Re: xmllint does not recognize emdash ( )
I doubt this is a bug: nowhere do you pass the validator a DTD, and
entities are defined in the DTD.
It’s best practice nowadays to not use entities but just write the UTF-8
characters directly.
An em dash surrounded by hair spaces is: “ — ” (for your copy/paste
convenience)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libxml2 in Ubuntu.
https://bugs.launchpad.net/bugs/2020814
Title:
xmllint does not recognize emdash ()
Status in libxml2 package in Ubuntu:
New
Bug description:
I'm using Ubuntu 20.04.2 LTS, x85_64, fully patched. I'm using DocBook to
build a PDF. One of the steps I use in my build script is to validate and
format the XML using xmllint from libxml2-utils
2.9.13+dfsg-1ubuntu0.3:
echo "Validating book..."
if ! xmllint --xinclude --noout --postvalid book.xml
then
echo "Validation failed. Exiting."
exit 1
fi
echo "Complete."
echo "Formatting source code..."
for file in *.xml
do
if xmllint --format "${file}" --output "${file}.format"
then
mv "${file}.format" "${file}"
fi
done
echo "Complete."
When I added an emdash () the book failed to format:
Validating book...
Complete.
Formatting source code...
ch02.xml:58: parser error : Entity 'mdash' not defined
injections are remediated using several methods. And two output devices
^
ch02.xml:58: parser error : Entity 'mdash' not defined
methods. And two output devices the printer and plaintext email
^
Complete.
The text is:
... And two output devices the printer and plaintext
email do not require...
It seems like emdash should be recognized.
-
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 22.04.2 LTS
Release:22.04
Codename: jammy
-
$ xmllint --version
xmllint: using libxml version 20913
compiled with: Threads Tree Output Push Reader Patterns Writer SAXv1 FTP
HTTP DTDValid HTML Legacy C14N Catalog XPath XPointer XInclude Iconv ICU
ISO8859X Unicode Regexps Automata Schemas Schematron Modules Debug Zlib Lzma
$ command -v xmllint
/usr/bin/xmllint
$ dpkg -S /usr/bin/xmllint
libxml2-utils: /usr/bin/xmllint
$ apt-cache show libxml2-utils
Package: libxml2-utils
Architecture: amd64
Version: 2.9.13+dfsg-1ubuntu0.3
Multi-Arch: foreign
Priority: optional
Section: text
Source: libxml2
Origin: Ubuntu
Maintainer: Ubuntu Developers
Original-Maintainer: Debian XML/SGML Group
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 202
Depends: libc6 (>= 2.34), libxml2 (>= 2.9.0)
Filename:
pool/main/libx/libxml2/libxml2-utils_2.9.13+dfsg-1ubuntu0.3_amd64.deb
Size: 40192
MD5sum: 3ca7de07562010fcaabf255ea8fea9c4
SHA1: 128a9cfaff49e85f2ab08578f389eecb21f17766
SHA256: c279c07caf909545e2cedb7845b5ac652e0a70f9784e5faf799a1a01441b4649
SHA512:
51600d7206c9a5568fdaeee9adddbc48962fc094cc479f4bd42c0714b3725cd3200937f8c876a897db08fc50d891005d7dbabfb6ae12ad27ad6ed416f8b6a03d
Homepage: http://xmlsoft.org
...
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/2020814/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1729558] Re: [regression] In Java apps like Netbeans, dark menu bars don't look good for disabled elements
As far as I see, openjdk-8 (8u275-b01-1) contains this patch, so it was backported upstream. ** Changed in: openjdk-8 (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1729558 Title: [regression] In Java apps like Netbeans, dark menu bars don't look good for disabled elements Status in Ubuntu theme: Invalid Status in openjdk-8 package in Ubuntu: Fix Released Status in openjdk-9 package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Invalid Bug description: This fix, #961679, specifically Ambiance/gtk-2.0/gtkrc:346 (http://bazaar.launchpad.net/~ubuntu-art-pkg/ubuntu- themes/trunk/revision/583), makes disabled elements in menus look terrible. Unfortunately I'm not aware of an easy way to get screenshots of open menus, so hopefully these attached phone pictures of Netbeans are enough to illustrate the issue. As you can see it is hard to tell the difference between what is disabled and what isn't, and the disabled items look fuzzy (easier to observe on monitor). I really don't see the issue with lighter menus, but if they must stay dark then the readability / contrast of disabled items needs to be fixed. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1729558/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1589836] Re: package libxml2-utils 2.9.3+dfsg1-1 failed to install/upgrade: krijg geen toegang tot archief: Bestand of map bestaat niet
AUB niet de files verwijderen tijdens apt nog aan’t werken is. Probeer es: $ sudo apt-get update $ sudo apt-get -f install -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/1589836 Title: package libxml2-utils 2.9.3+dfsg1-1 failed to install/upgrade: krijg geen toegang tot archief: Bestand of map bestaat niet Status in libxml2 package in Ubuntu: Invalid Bug description: The package failed to upgrade in the terminal. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libxml2-utils 2.9.3+dfsg1-1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Tue Jun 7 09:40:41 2016 ErrorMessage: krijg geen toegang tot archief: Bestand of map bestaat niet InstallationDate: Installed on 2016-04-23 (44 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: libxml2 Title: package libxml2-utils 2.9.3+dfsg1-1 failed to install/upgrade: krijg geen toegang tot archief: Bestand of map bestaat niet UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/1589836/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1589679] Re: package libxml2 2.9.3+dfsg1-1 failed to install/upgrade: unable to securely remove '/usr/share/doc/libxml2/AUTHORS.dpkg-new': Read-only file system
I suggest to learn to read. Mount your filesystems read-write when you install packages. ** Changed in: libxml2 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/1589679 Title: package libxml2 2.9.3+dfsg1-1 failed to install/upgrade: unable to securely remove '/usr/share/doc/libxml2/AUTHORS.dpkg-new': Read-only file system Status in libxml2 package in Ubuntu: Invalid Bug description: occur when i update ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libxml2 2.9.3+dfsg1-1ubuntu0.1 ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10 Uname: Linux 4.4.0-23-generic i686 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 Date: Mon Jun 6 17:10:44 2016 DuplicateSignature: package:libxml2:2.9.3+dfsg1-1 Unpacking libxml2:i386 (2.9.3+dfsg1-1ubuntu0.1) over (2.9.3+dfsg1-1) ... dpkg: error processing archive /var/cache/apt/archives/libxml2_2.9.3+dfsg1-1ubuntu0.1_i386.deb (--unpack): unable to securely remove '/usr/share/doc/libxml2/AUTHORS.dpkg-new': Read-only file system ErrorMessage: unable to securely remove '/usr/share/doc/libxml2/AUTHORS.dpkg-new': Read-only file system InstallationDate: Installed on 2016-05-26 (10 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: libxml2 Title: package libxml2 2.9.3+dfsg1-1 failed to install/upgrade: unable to securely remove '/usr/share/doc/libxml2/AUTHORS.dpkg-new': Read-only file system UpgradeStatus: Upgraded to xenial on 2016-05-27 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/1589679/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1394929] Re: Please provide 'locales-all' as in Debian
Hi Doko, the package *is* required if you programmatically need to have “all”, or at least a large set of, locales available. Possible use case here is a package dependency (declaratively). In the specific case of FusionForge, I have seen it (both the native tracker and the embedded mediawiki) malfunction if locales-all was not installed, even getting PHP to segfault. Another use case is to ensure something is available to users, especially nōn-root users, in the default location (so there is no need to set LOCPATH. (This can help ssh, sudo, etc.) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to langpack-locales in Ubuntu. https://bugs.launchpad.net/bugs/1394929 Title: Please provide 'locales-all' as in Debian Status in “glibc” package in Ubuntu: Confirmed Status in “langpack-locales” package in Ubuntu: New Bug description: Hi, Debian provides a 'locales-all' package, which is very convenient to ensure all locales are available, and installs very quickly. It's particularly handy when providing i18n'd web applications (e.g. that use php-gettext). As they may be accessed by visitors of all supported languages, rather than documenting how the server administrator should enable a list of 10-15 languages by reconfiguring 'locales', the packager can just add 'locales-all' to the Recommends or Depends. See for instance the FusionForge package in Debian (https://packages.debian.org/jessie/gforge-web-apache2). Cheers! Sylvain To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1394929/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1357227]
Created attachment 8474439 eMail exhibiting the bug OK. This eMail contains a PGP message encrypted to 0xD1D8EFD2 whose public and secret (passphrase is 123123) key I also attached. I just confirmed with a coworker that this does exhibit the bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1357227 Title: broken charset/encoding autodetection for encrypted messages Status in Mozilla Thunderbird Mail and News: New Status in “thunderbird” package in Ubuntu: New Status in “kdepim” package in Debian: Confirmed Bug description: Version: 1:31.0+build1-0ubuntu0.12.04.1 Hi, this is a bug Mozilla™ Thunderbird and KDEPIM share: When I send an Inline PGP encrypted message, whose body is using UTF-8, to another user, the message is ASCII armoured (and thus 7bit). The other user, running Thunderbird or Kontact, (or my own Kontact instance in the “sent-mail” folder), gets the message and interprets the post-decryption body as ISO-8859-1 (or Windows-1252, probably) instead of UTF-8. Manually switching the encoding to Unicode in the menu corrects this… for this one message. (See https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1108980 as well.) The problem here is that the human message encoding (everything within the PGP armour) must be separated from the transport message encoding (the RFC822 message in which the “-BEGIN PGP MESSAGE”…“END PGP MESSAGE-” is transmitted) must be separated from each other, which they aren’t. Please fix this, it harms using those MUAs in an enterprise environment. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1357227/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1357227]
Created attachment 8474435 secret part of test GPG key -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1357227 Title: broken charset/encoding autodetection for encrypted messages Status in Mozilla Thunderbird Mail and News: New Status in “thunderbird” package in Ubuntu: New Status in “kdepim” package in Debian: Confirmed Bug description: Version: 1:31.0+build1-0ubuntu0.12.04.1 Hi, this is a bug Mozilla™ Thunderbird and KDEPIM share: When I send an Inline PGP encrypted message, whose body is using UTF-8, to another user, the message is ASCII armoured (and thus 7bit). The other user, running Thunderbird or Kontact, (or my own Kontact instance in the “sent-mail” folder), gets the message and interprets the post-decryption body as ISO-8859-1 (or Windows-1252, probably) instead of UTF-8. Manually switching the encoding to Unicode in the menu corrects this… for this one message. (See https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1108980 as well.) The problem here is that the human message encoding (everything within the PGP armour) must be separated from the transport message encoding (the RFC822 message in which the “-BEGIN PGP MESSAGE”…“END PGP MESSAGE-” is transmitted) must be separated from each other, which they aren’t. Please fix this, it harms using those MUAs in an enterprise environment. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1357227/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1357227]
Created attachment 8474434 public part of test GPG key -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1357227 Title: broken charset/encoding autodetection for encrypted messages Status in Mozilla Thunderbird Mail and News: New Status in “thunderbird” package in Ubuntu: New Status in “kdepim” package in Debian: Confirmed Bug description: Version: 1:31.0+build1-0ubuntu0.12.04.1 Hi, this is a bug Mozilla™ Thunderbird and KDEPIM share: When I send an Inline PGP encrypted message, whose body is using UTF-8, to another user, the message is ASCII armoured (and thus 7bit). The other user, running Thunderbird or Kontact, (or my own Kontact instance in the “sent-mail” folder), gets the message and interprets the post-decryption body as ISO-8859-1 (or Windows-1252, probably) instead of UTF-8. Manually switching the encoding to Unicode in the menu corrects this… for this one message. (See https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1108980 as well.) The problem here is that the human message encoding (everything within the PGP armour) must be separated from the transport message encoding (the RFC822 message in which the “-BEGIN PGP MESSAGE”…“END PGP MESSAGE-” is transmitted) must be separated from each other, which they aren’t. Please fix this, it harms using those MUAs in an enterprise environment. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1357227/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1108980] Re: thunderbird message preview pane do not honor global character encoding settings
Confirmed in Thunderbird 1:31.0+build1-0ubuntu0.12.04.1
Please fix!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1108980
Title:
thunderbird message preview pane do not honor global character
encoding settings
Status in “thunderbird” package in Ubuntu:
Confirmed
Bug description:
character encoding is set to UTF-8 for incoming and outgoing messages in Edit
Preferences : Display Advanced.
In the review pane, the message is shown with Western ISO-8859-1 as seen in
View Character Encoding. When manually change it to UTF-8 it work, but when
clicking on other message and going back, te Western character encoding is
restored.
Is there other global character encoding hidden in somwhere else?
If not, this is defenitey a bug.
P.S: The auto-detect menu in View Character Encoding changes
nothing. I tried set auto detect to off and Universal and no
change.
Best Regards,
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: thunderbird 17.0.2+build1-0ubuntu0.12.04.1
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic x86_64
NonfreeKernelModules: fglrx
AddonCompatCheckDisabled: False
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: amd64
BuildID: 20130106044124
Card0.Amixer.info:
Card hw:0 'SB'/'HDA ATI SB at 0xfeb0 irq 16'
Mixer name : 'Realtek ALC892'
Components : 'HDA:10ec0892,10438410,00100302'
Controls : 44
Simple ctrls : 21
Card1.Amixer.info:
Card hw:1 'U0x46d0x991'/'USB Device 0x46d:0x991 at usb-:00:13.2-2, high
speed'
Mixer name : 'USB Mixer'
Components : 'USB046d:0991'
Controls : 2
Simple ctrls : 1
Card1.Amixer.values:
Simple mixer control 'Mic',0
Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum
Capture channels: Mono
Limits: Capture 0 - 8
Mono: Capture 6 [75%] [27.00dB] [off]
Card2.Amixer.info:
Card hw:2 'Generic'/'HD-Audio Generic at 0xfea4 irq 89'
Mixer name : 'ATI R6xx HDMI'
Components : 'HDA:1002aa01,00aa0100,00100200'
Controls : 6
Simple ctrls : 1
Card2.Amixer.values:
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
Channel: Unavailable
Date: Tue Jan 29 13:20:58 2013
ForcedLayersAccel: False
IfupdownConfig:
auto lo
iface lo inet loopback
InstallationMedia: Xubuntu 12.04 Precise Pangolin - Beta amd64 (20120228)
IpRoute:
default via 192.168.1.1 dev wlan0 proto static
169.254.0.0/16 dev wlan0 scope link metric 1000
192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.33 metric
2
MarkForUpload: True
Plugins:
Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
IcedTea-Web Plugin (using IcedTea-Web 1.2 (1.2-2ubuntu1.3)) -
/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/amd64/IcedTeaPlugin.so
(icedtea-7-plugin)
PrefSources:
prefs.js
[Profile]/extensions/masterpasswordtimeoutplus@vano/defaults/preferences/masterpasswordplus.js
[Profile]/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/defaults/preferences/lightning.js
[Profile]/extensions/{847b3a00-7ab1-11d4-8f02-006008948af5}/defaults/preferences/enigmail.js
ProcEnviron:
LANGUAGE=en_US:en
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=17.0.2/20130106044124 (In use)
RelatedPackageVersions: icedtea-7-plugin 1.2-2ubuntu1.3
RunningIncompatibleAddons: False
SourcePackage: thunderbird
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/02/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0901
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: M5A99X EVO
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr0901:bd12/02/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A99XEVO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: To be filled by O.E.M.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1108980/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1357227] [NEW] broken charset/encoding autodetection for encrypted messages
Public bug reported: Version: 1:31.0+build1-0ubuntu0.12.04.1 Hi, this is a bug Mozilla™ Thunderbird and KDEPIM share: When I send an Inline PGP encrypted message, whose body is using UTF-8, to another user, the message is ASCII armoured (and thus 7bit). The other user, running Thunderbird or Kontact, (or my own Kontact instance in the “sent-mail” folder), gets the message and interprets the post- decryption body as ISO-8859-1 (or Windows-1252, probably) instead of UTF-8. Manually switching the encoding to Unicode in the menu corrects this… for this one message. (See https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1108980 as well.) The problem here is that the human message encoding (everything within the PGP armour) must be separated from the transport message encoding (the RFC822 message in which the “-BEGIN PGP MESSAGE”…“END PGP MESSAGE-” is transmitted) must be separated from each other, which they aren’t. Please fix this, it harms using those MUAs in an enterprise environment. ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New ** Affects: kdepim (Debian) Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #754265 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754265 ** Also affects: kdepim (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754265 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1357227 Title: broken charset/encoding autodetection for encrypted messages Status in “thunderbird” package in Ubuntu: New Status in “kdepim” package in Debian: Unknown Bug description: Version: 1:31.0+build1-0ubuntu0.12.04.1 Hi, this is a bug Mozilla™ Thunderbird and KDEPIM share: When I send an Inline PGP encrypted message, whose body is using UTF-8, to another user, the message is ASCII armoured (and thus 7bit). The other user, running Thunderbird or Kontact, (or my own Kontact instance in the “sent-mail” folder), gets the message and interprets the post-decryption body as ISO-8859-1 (or Windows-1252, probably) instead of UTF-8. Manually switching the encoding to Unicode in the menu corrects this… for this one message. (See https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1108980 as well.) The problem here is that the human message encoding (everything within the PGP armour) must be separated from the transport message encoding (the RFC822 message in which the “-BEGIN PGP MESSAGE”…“END PGP MESSAGE-” is transmitted) must be separated from each other, which they aren’t. Please fix this, it harms using those MUAs in an enterprise environment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1357227/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1357227] Re: broken charset/encoding autodetection for encrypted messages
** Bug watch added: Mozilla Bugzilla #1054187 https://bugzilla.mozilla.org/show_bug.cgi?id=1054187 ** Also affects: thunderbird via https://bugzilla.mozilla.org/show_bug.cgi?id=1054187 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1357227 Title: broken charset/encoding autodetection for encrypted messages Status in Mozilla Thunderbird Mail and News: Unknown Status in “thunderbird” package in Ubuntu: New Status in “kdepim” package in Debian: Unknown Bug description: Version: 1:31.0+build1-0ubuntu0.12.04.1 Hi, this is a bug Mozilla™ Thunderbird and KDEPIM share: When I send an Inline PGP encrypted message, whose body is using UTF-8, to another user, the message is ASCII armoured (and thus 7bit). The other user, running Thunderbird or Kontact, (or my own Kontact instance in the “sent-mail” folder), gets the message and interprets the post-decryption body as ISO-8859-1 (or Windows-1252, probably) instead of UTF-8. Manually switching the encoding to Unicode in the menu corrects this… for this one message. (See https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1108980 as well.) The problem here is that the human message encoding (everything within the PGP armour) must be separated from the transport message encoding (the RFC822 message in which the “-BEGIN PGP MESSAGE”…“END PGP MESSAGE-” is transmitted) must be separated from each other, which they aren’t. Please fix this, it harms using those MUAs in an enterprise environment. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1357227/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 928293] Re: always adds a “created with the GIMP” comment to files
Thanks, that _seems_ to do the trick. As for why, when storing large binaries in LDAP, every three-octet group is precious (we have user photos in LDAP for perusal by the company’s Jabber server with mod_vcard_ldap and mod_shared_roster_ldap) as there are timeouts. We found that jpegPhoto attributes of about 4K (before base64 encoding) work best, and more than about 8K are unreasonable. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/928293 Title: always adds a “created with the GIMP” comment to files Status in “gimp” package in Ubuntu: Incomplete Bug description: Version: 2.6.6-0ubuntu1~hardy1~andre1 GIMP always adds a comment “Created with the GIMP” to files when saving. This is inacceptable, as it severely raises the file size, especially when trying to use GIMP to make photos smaller to get them to fit into space-constrained database fields or LDAP. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/928293/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 928293] [NEW] always adds a “created with the GIMP” comment to files
Public bug reported: Version: 2.6.6-0ubuntu1~hardy1~andre1 GIMP always adds a comment “Created with the GIMP” to files when saving. This is inacceptable, as it severely raises the file size, especially when trying to use GIMP to make photos smaller to get them to fit into space-constrained database fields or LDAP. ** Affects: gimp (Ubuntu) Importance: Undecided Status: New ** Tags: hardy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/928293 Title: always adds a “created with the GIMP” comment to files Status in “gimp” package in Ubuntu: New Bug description: Version: 2.6.6-0ubuntu1~hardy1~andre1 GIMP always adds a comment “Created with the GIMP” to files when saving. This is inacceptable, as it severely raises the file size, especially when trying to use GIMP to make photos smaller to get them to fit into space-constrained database fields or LDAP. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/928293/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
