[Bug 1847275] Re: stunnel4: "INTERNAL ERROR: Bad magic at ssl.c, line 117" - DoS vulnerability
In addition to my earlier packet capture and stack trace, I can now add a detailed debug log from a different occurrence of this crash. See attachment. I turned the log level on stunnel all the way up to the maximum (debug=7) and left things running until another attack hit my server. This log only covers 30 seconds, but in that time stunnel handled four different incoming connections, the last of which ended in a crash. It's probably worth noting that right before the crash there's a big chunk of repetitive message pairs: "Remove session callback" followed by "Deallocating application specific data for session connect address", repeated in tandem until the crash with "INTERNAL ERROR: Bad magic at ssl.c, line 117". Hope that helps, and please let me know if there's any more information I can provide. ** Attachment added: "Debug log during crash" https://bugs.launchpad.net/ubuntu/+source/stunnel4/+bug/1847275/+attachment/5331741/+files/stunnel.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847275 Title: stunnel4: "INTERNAL ERROR: Bad magic at ssl.c, line 117" - DoS vulnerability To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/stunnel4/+bug/1847275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858141] Re: "Advanced" tab is missing from Print dialog in Qt5 applications
Well, thanks anyway for looking into it. It's disappointing, but I can totally understand why this won't be backported if the patch is that complex and touches that many other packages. I'll just use the workaround until I get the updated Qt stack in 20.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858141 Title: "Advanced" tab is missing from Print dialog in Qt5 applications To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1858141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858141] [NEW] "Advanced" tab is missing from Print dialog in Qt5 applications
Public bug reported: Please backport Qt patch 213391 to qtbase-opensource-src in Bionic: https://codereview.qt-project.org/#/c/213391/ [Impact] On Kubuntu 18.04 (bionic), any applications using Qt5 are unable to fully configure printers from within the "Print..." dialog because the "Advanced" tab is no longer present. Settings shown here will differ by printer, but this includes important settings such as paper type (plain, glossy, photo, etc.), print resolution, and ink usage strategies. Gwenview and Okular are notable affected applications. GTK applications are unaffected and do show the advanced options provided by the printer driver. As a workaround for Qt5 applications, the printer *default* advanced settings can be successfully accessed and changed from within the "Printers" section of Plasma's "System Settings", but this is cumbersome, unintuitive, and is not the intended way of interacting with these settings on a per-print-job basis. [Additional Information] This was identified as a bug in Qt5 upstream: https://bugreports.qt.io/browse/QTBUG-54464 The bug was fixed upstream in Qt 5.11, but Bionic is stable on Qt 5.9. I'd like to request that this patch be backported to Bionic, please. [Regression Potential] OpenSUSE has already backported this patch to their Qt 5.9 stable branch, so there is precedent for this patch being low risk: https://build.opensuse.org/package/view_file/KDE:Qt:5.9/libqt5-qtbase/0010-Reintroduce-the-Advanced-tab-in-the-QPrintProperties.patch?expand=1 Software Versions: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.3 LTS Release:18.04 Codename: bionic $ apt-cache policy libqt5printsupport5 libqt5printsupport5: Installed: 5.9.5+dfsg-0ubuntu2.4 Candidate: 5.9.5+dfsg-0ubuntu2.4 Version table: *** 5.9.5+dfsg-0ubuntu2.4 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 5.9.5+dfsg-0ubuntu2.1 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 5.9.5+dfsg-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ** Affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858141 Title: "Advanced" tab is missing from Print dialog in Qt5 applications To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1858141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847275] Re: stunnel4: "INTERNAL ERROR: Bad magic at ssl.c, line 117" - DoS vulnerability
I too see this problem with stunnel on a public-facing Ubuntu 18.04 server. In addition to the stack trace with debugging symbols that I provided earlier, I now have a packet capture of one of the TLS sessions that caused a crash. I was lucky enough to catch the attacker in the act, and in addition to capturing packets on the wire, I was also logging TLS session premaster keys. I've injected the relevant ephemeral key material (*not* my server private key!) into the capture so that we can all see inside the TLS tunnel. I'm not a TLS expert, but nothing jumped out at me as being obviously malformed or exploitative in the TLS negotiation, though second opinions are very welcome. Looking inside the tunnel, the attacker appears to be trying to begin some sort of WordPress-based vulnerability test. Stunnel crashed before it could connect to the local service I have it in front of, so this HTTP GET request was never delivered downstream. For what it's worth, I'm not running WordPress, so that vulnerability scan would have come up empty anyway. Please let me know if there's any more information I can provide regarding this packet capture or my server configuration. ** Attachment added: "Capture of an attack that caused stunnel to crash" https://bugs.launchpad.net/ubuntu/+source/stunnel4/+bug/1847275/+attachment/5312290/+files/stunnel-crash-20191206145927.pcapng -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847275 Title: stunnel4: "INTERNAL ERROR: Bad magic at ssl.c, line 117" - DoS vulnerability To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/stunnel4/+bug/1847275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847275] Re: stunnel4: "INTERNAL ERROR: Bad magic at ssl.c, line 117" - DoS vulnerability
Stacktrace:
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
set = {__val = {0, 140337533684800, 140725801169072, 94865733453904,
140725801169056, 15442105031219824384, 4, 94865733453904, 0,
15442105031219824384, 4, 1, 94865733453904, 1, 4, 94865708102691}}
pid =
tid =
ret =
#1 0x7fa2e09d5801 in __GI_abort () at abort.c:79
save_stage = 1
act = {__sigaction_handler = {sa_handler = 0x5647a656bd10,
sa_sigaction = 0x5647a656bd10}, sa_mask = {__val = {94865708083362, 1572911363,
206158430224, 140725801169664, 94865708014912, 17179869207, 17179869201,
511101108234, 1318554959873, 94862942666752, 18446744073709530016,
94865733327264, 94865707998636, 94865708111963, 140725801169488,
94865708083362}}, sa_flags = -1529528963, sa_restorer = 0x75}
sigs = {__val = {32, 0 }}
__cnt =
__set =
__cnt =
__set =
#2 0x5647a4d3e3d0 in ?? ()
No symbol table info available.
#3 0x5647a4d395b3 in ?? ()
No symbol table info available.
#4 0x5647a4d39809 in ?? ()
No symbol table info available.
#5 0x5647a4d39e44 in ?? ()
No symbol table info available.
#6 0x7fa2e17ab7c8 in CRYPTO_free_ex_data
(class_index=class_index@entry=2, obj=obj@entry=0x7fa2d0019f90,
ad=ad@entry=0x7fa2d001a0e0) at ../crypto/ex_data.c:354
mx =
i = 2
ip = 0x7fa2e1aff6f0
ptr =
f = 0x5647a656b430
stack = {0x0, 0x5647a656b3a0, 0x5647a656b430, 0xd64d60b5ca214700,
0x7fa2d000bc80, 0x5647a65715f0, 0x7fa2d0019f90, 0x7fa2e17ab2c8
, 0x5, 0x5647a65715f0}
storage = 0x7ffd4763b370
#7 0x7fa2e1b3fe58 in SSL_SESSION_free (ss=0x7fa2d0019f90) at
../ssl/ssl_sess.c:787
i =
ss = 0x7fa2d0019f90
i =
i =
#8 0x7fa2e17af3fc in doall_util_fn (arg=0x7ffd4763b460,
arg@entry=0x7ffd4763b420, func_arg=func_arg@entry=0x7fa2e1b406f0 ,
func=0x0, use_arg=1, lh=0x5647a6551d40) at ../crypto/lhash/lhash.c:196
i = 5
a =
n = 0x7fa2c8012800
i =
a =
n =
#9 OPENSSL_LH_doall_arg (lh=0x5647a6551d40, func=func@entry=0x7fa2e1b406f0
, arg=arg@entry=0x7ffd4763b460) at ../crypto/lhash/lhash.c:211
No locals.
#10 0x7fa2e1b414e7 in lh_SSL_SESSION_doall_TIMEOUT_PARAM
(arg=0x7ffd4763b460, fn=0x7fa2e1b406f0 , lh=) at
../ssl/ssl_sess.c:1104
No locals.
#11 SSL_CTX_flush_sessions (s=0x5647a65715f0, t=) at
../ssl/ssl_sess.c:1119
i =
tp = {ctx = 0x5647a65715f0, time = 1572911664, cache = 0x5647a6551d40}
#12 0x5647a4d4d080 in ?? ()
No symbol table info available.
#13 0x5647a4d4d109 in ?? ()
No symbol table info available.
#14 0x5647a4d38c56 in ?? ()
No symbol table info available.
#15 0x7fa2e09b6b97 in __libc_start_main (main=0x5647a4d38be0, argc=2,
argv=0x7ffd4763b688, init=, fini=,
rtld_fini=, stack_end=0x7ffd4763b678) at ../csu/libc-start.c:310
self =
__self =
result =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {0, -5506946324664727591,
94865707995104, 140725801170560, 0, 0, -2240925574734854183,
-2280530182707525671}, mask_was_saved = 0}}, priv = {pad = {0x0, 0x0,
0x7fa2e1d9e733 <_dl_init+259>, 0x7fa2e1d816b8}, data = {prev = 0x0, cleanup =
0x0, canceltype = -505813197}}}
not_first_call =
#16 0x5647a4d3900a in ?? ()
No symbol table info available.
StacktraceAddressSignature:
/usr/bin/stunnel4:6:/lib/x86_64-linux-gnu/libc-2.27.so+40801:/usr/bin/stunnel4+e3d0:/usr/bin/stunnel4+95b3:/usr/bin/stunnel4+9809:/usr/bin/stunnel4+9e44:/usr/lib/x86_64-linux-gnu/libcrypto.so.1.1+1757c8:/usr/lib/x86_64-linux-gnu/libssl.so.1.1+3ee58:/usr/lib/x86_64-linux-gnu/libcrypto.so.1.1+1793fc:/usr/lib/x86_64-linux-gnu/libssl.so.1.1+404e7:/usr/bin/stunnel4+1d080:/usr/bin/stunnel4+1d109:/usr/bin/stunnel4+8c56:/lib/x86_64-linux-gnu/libc-2.27.so+21b97:/usr/bin/stunnel4+900a
StacktraceSource:
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
[Error: raise.c was not found in source tree]
#1 0x7fa2e09d5801 in __GI_abort () at abort.c:79
[Error: abort.c was not found in source tree]
#2 0x5647a4d3e3d0 in ?? ()
#3 0x5647a4d395b3 in ?? ()
#4 0x5647a4d39809 in ?? ()
#5 0x5647a4d39e44 in ?? ()
#6 0x7fa2e17ab7c8 in CRYPTO_free_ex_data
(class_index=class_index@entry=2, obj=obj@entry=0x7fa2d0019f90,
ad=ad@entry=0x7fa2d001a0e0) at ../crypto/ex_data.c:354
[Error: ex_data.c was not found in source tree]
#7 0x7fa2e1b3fe58 in SSL_SESSION_free (ss=0x7fa2d0019f90) at
../ssl/ssl_sess.c:787
[Error: ssl_sess.c was not found in source tree]
#8 0x7fa2e17af3fc in doall_util_fn (arg=0x7ffd4763b460,
arg@entry=0x7ffd4763b420, func_arg=func_arg@entry=0x7fa2e1b406f0 ,
func=0x0, use_arg=1, lh=0x5647a6551d40) at ../crypto/lhash/lhash.c:196
[Error: lhash.c was not found in source tree]
#9 OPENSSL_LH_doall_arg
[Bug 1847275] Re: stunnel4: "INTERNAL ERROR: Bad magic at ssl.c, line 117" - DoS vulnerability
ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.8 Architecture: amd64 DistroRelease: Ubuntu 18.04 Package: stunnel4 3:5.44-1ubuntu3 PackageArchitecture: amd64 ProcEnviron: LANG=C.UTF-8 TERM=xterm PATH=(custom, no user) SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18 Tags: bionic uec-images Uname: Linux 4.15.0-65-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True modified.conffile..etc.default.stunnel4: [modified] mtime.conffile..etc.default.stunnel4: 2019-11-04T17:53:44.054718 ** Tags added: apport-collected bionic uec-images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847275 Title: stunnel4: "INTERNAL ERROR: Bad magic at ssl.c, line 117" - DoS vulnerability To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/stunnel4/+bug/1847275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847275] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1847275/+attachment/5302860/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847275 Title: stunnel4: "INTERNAL ERROR: Bad magic at ssl.c, line 117" - DoS vulnerability To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/stunnel4/+bug/1847275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847275] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1847275/+attachment/5302859/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847275 Title: stunnel4: "INTERNAL ERROR: Bad magic at ssl.c, line 117" - DoS vulnerability To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/stunnel4/+bug/1847275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667208] Re: Ubuntu's selenium hardcodes a path that is valid for Debian, but not for Ubuntu
Thanks for the symlink, Oliver. My machines just started picking up this update today. Much appreciated! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667208 Title: Ubuntu's selenium hardcodes a path that is valid for Debian, but not for Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1667208/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667208] Re: Ubuntu's selenium hardcodes a path that is valid for Debian, but not for Ubuntu
While I'm happy to see this fix released, I'm not so happy that it broke all of our company's Selenium-based scripts running on Ubuntu 16.04 by making a non-backwards-compatible change in an LTS release. All of our scripts had been written to accommodate the "buggy" behavior that has been present since Xenial's release by specifying the ChromeDriver path at '/usr/lib/chromium-browser/chromedriver'. Now, after applying the latest security updates, these scripts are finding that their ChromeDriver has gone missing. In order to provide backwards-compatibility on the LTS releases, could you please provide (in a packaging update) a symlink at the old '/usr/lib/chromium-browser/chromedriver' location pointing to the new '/usr/bin/chromedriver' location? Thanks for your consideration of this request. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667208 Title: Ubuntu's selenium hardcodes a path that is valid for Debian, but not for Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1667208/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1586570] Re: openvpn chroot does not have a valid resolv.conf
I encountered this same problem on Ubuntu MATE 16.04.2. Every time the OpenVPN connection attempted to automatically restart itself, it was unable to do so. This breaks the connection until a manual restart of the connection through the NetworkManager GUI. This bug is easily reproducible by sending the openvpn process a signal to restart itself: $ sudo killall -SIGUSR1 openvpn Watching syslog and using strace on the process show it is unable to properly restart because of lack of privileges and being jailed in the chroot environment. As others have mentioned here, I tried adding more and more dependencies into the chroot, but after a while it just got ridiculous, unmaintainable, and never actually fixed the problem. *The following workaround does fix the problem for me.* NetworkManager attempts to run openvpn as an unprivileged user and in a chroot. Normally, this is a good security practice, but the implementation unfortunately is half-baked. The openvpn man page calls out several problematic cases in which dropping privileges or chrooting can cause failures on connection restarts, and both the man page and official how-to seem lukewarm at best on the added security benefits. The benefits are even less clear for a client-only configuration as opposed to a server. A reasoned cost/benefit analysis for my own use- case shows the costs of dropping privileges and/or chrooting when running openvpn outweigh the benefits, at least at this point in time (02/2017). While disabling NetworkManager and running openvpn manually or as a standalone service is a valid solution for running openvpn as root, there are other benefits to running NetworkManager on a desktop or laptop system that I don't want to give up. However, getting NetworkManager to play nice is not trivial. As of late Sep. 2016, NetworkManager changed their default behavior with regard to openvpn, forcing it to always run with least privileges: https://github.com/GNOME/network-manager-openvpn/commit/03fc318608b0d60decaced38e0de7a74c2ac5c4c As mentioned in the source code, the only way to override this default is by setting a few environment variables with null values. The cleanest way to do this is to create a drop-in systemd configuration file for NetworkManager: 1. Create the directory to hold the drop-in configuration file: $ cd /etc/systemd/system $ sudo mkdir NetworkManager.service.d $ cd NetworkManager.service.d 2. Create a new conf file: $ sudo nano disable-openvpn-reduced-privileges.conf 3. Add the following content to the file: # Disable NetworkManager's OpenVPN plug-in from performing chroot and dropping privileges by default (null assignment) [Service] Environment="NM_OPENVPN_CHROOT=" Environment="NM_OPENVPN_USER=" Environment="NM_OPENVPN_GROUP=" 4. Save the file and exit nano 5. In order for the changes to take effect, you may either restart the NetworkManager service and quit & restart your openvpn connection, or if it is simpler for you, just restart your computer. You can test if this is working properly several ways: 1. Systemd should show that the drop-in configuration is in use: $ systemctl status NetworkManager NetworkManager.service - Network Manager Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled) Drop-In: /etc/systemd/system/NetworkManager.service.d +-disable-openvpn-reduced-privileges.conf 2. When openvpn is running it should be running as the root user. This can be verified using ps or any other process lister/monitor. 3. Force a running openvpn connection to restart and see if it is successful: $ sudo killall -SIGUSR1 openvpn -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1586570 Title: openvpn chroot does not have a valid resolv.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1586570/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1584457] Re: gsd-backlight-helper spamming the logs since upate to 16.04
I believe this bug has been fixed upstream. Would it be possible to get this patch merged into the Ubuntu package?: https://git.gnome.org/browse/gnome-settings-daemon/commit/?id=76dab07 ** Bug watch added: GNOME Bug Tracker #764896 https://bugzilla.gnome.org/show_bug.cgi?id=764896 ** Also affects: gnome-settings-daemon via https://bugzilla.gnome.org/show_bug.cgi?id=764896 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1584457 Title: gsd-backlight-helper spamming the logs since upate to 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1584457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1047262] Re: race condition on startup between samba and cups
Are there any plans to fix this issue in Precise now that Quantal has a working patch? Thanks. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1047262 Title: race condition on startup between samba and cups To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1047262/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1047262] Re: race condition on startup between samba and cups
Are there any plans to fix this issue in Precise now that Quantal has a working patch? Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1047262 Title: race condition on startup between samba and cups To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1047262/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 812134] Re: Konsole + Terminus font, wrong line alignment (Update to terminus 4.36)
It should be noted that Debian Wheezy, which uses the same 4.35-1 package for xfonts-terminus, does not suffer from this problem. I compared Kubuntu Oneiric and Debian Wheezy side by side, and the same version of Terminus appeared with different font size availabilities in each one. Kubuntu: sizes 9, 11, 12, 14, 15, 17, 18, 21, 24 Debian: sizes 9, 10, 12, 13, 15, 16, 18, 21, 24 I tested each of these font sizes on each distribution, and the only ones that displayed the buggy behavior were the sizes that were available *only* in Kubuntu. All of the Debian sizes display fine. Sizes 11, 14, and 17 display the bug in Kubuntu, but all of the other Kubuntu sizes display fine. If I had to guess what was happening here, it would be that the buggy sizes do not actually exist in this bitmap font. Something is trying to automatically scale up what *should* be sizes 10, 13, and 16 (as they appear in Debian) to sizes +1 from these, and since Terminus is a bitmap font designed *not* to be scaled, this scaling breaks the perfect monospacing. The same wrong font sizes appear no matter the KDE program trying to use the font: Konsole, Kate, KDE System Settings, etc. Interestingly, I tried installing Gedit and GNOME Terminal to test with GTK, and while these programs let you choose any size of Terminus that you want, they had little suggestion marks under the *proper* sizes, i.e. the sizes as listed in Debian. Does this indicate that the problem is more to do with KDE's font rendering for bitmap fonts than with Terminus itself? Debian Wheezy currently runs KDE 4.6.5, while Kubuntu runs KDE 4.7.4, so there is an inequality in the comparison there. I would test with another monospaced bitmap font, but I do not know of any others in the Ubuntu Debian repositories off the top of my head. Suggestions? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/812134 Title: Konsole + Terminus font, wrong line alignment (Update to terminus 4.36) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/konsole/+bug/812134/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 840306] Re: Muon hangs when using etckeeper
This fix has been packaged for precise, but not for oneiric. The oneiric repositories still have qapt and muon 1.2.1, which still leaves a fresh Kubuntu 11.10 installation ready to break upon the first round of updates via Muon Updater. Since this breaks basic package management functionality for the average stable release user who is just doing what the OS is prompting him/her to do, I would like to request a minimum version upgrade from 1.2.1 to 1.2.3 in the oneiric repositories, please. I have tested a fresh Kubuntu 11.10 installation on a spare laptop, and updating muon and qapt to 1.2.3 from Jonathan Thomas' QApt PPA before running the first round of regular updates fixed this bug for me. Without the PPA upgrade to 1.2.3, the first Full Update right after installation will attempt to install/upgrade 356 packages and get hung up at 49% during Committing Changes. Steps to reproduce restoration of expected update behavior: 1. Perform a fresh installation of Kubuntu 11.10 -- my tests were run on the i386 version 2. During installation, do not check the Install updates option 3. After installer completes, reboot, login, and ignore notification from Muon Updater 4. Open Muon Package Manager 5. Verify software version in About Muon Package Manager = 1.2.1 6. Configure Software Sources - Other Software - Add... ppa:echidnaman/qapt 7. Close and re-open Muon Package Manager -- this seems to be necessary to force the Filters list to recognize the newly added PPA even though Check For Updates has been performed (separate bug, maybe?) 8. Under Filter: choose By Origin and select QApt PPA 9. Select all packages in this filtered list that have the status Upgradeable and mark them for upgrade -- for me, this included 10 packages 10. Apply changes 11. Close and re-open Muon Package Manager 12. Verify software version in About Muon Package Manager = 1.2.3 13. Check For Updates, Full Upgrade, Apply Changes These steps resulted in the same 356 packages as before getting installed/upgraded, except the update procedure completed to 100% without any hang ups. I have yet to notice any negative impact from installing version 1.2.3 of muon qapt, only the positive impact of the bugfix. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/840306 Title: Muon hangs when using etckeeper To manage notifications about this bug go to: https://bugs.launchpad.net/qapt/+bug/840306/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 812134] Re: Konsole + Terminus font, wrong line alignment
I'd like to request that this bug be re-opened, please. Harald Sitter marked this bug as invalid because it needed to be reported upstream. However, someone has indeed reported this bug to the KDE folks here: https://bugs.kde.org/show_bug.cgi?id=284365 The discussion in that bug determined that the problem only exists in Kubuntu, not KDE in general, so the problem needs to be fixed here. The proposed solution in that bug is simply to update Terminus from 4.35 to 4.36, which is consistent with the workaround that Vadim Pilipenko posted here. I don't know whether this bug should stay with konsole, or if it needs to be moved to xfonts-terminus, but either way, could someone please reopen this bug so that we can get Terminus updated to the latest version? Thanks. ** Bug watch added: KDE Bug Tracking System #284365 http://bugs.kde.org/show_bug.cgi?id=284365 ** Changed in: konsole (Ubuntu) Status: Invalid = New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/812134 Title: Konsole + Terminus font, wrong line alignment To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/konsole/+bug/812134/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 812134] Re: Konsole + Terminus font, wrong line alignment
** Also affects: xfonts-terminus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/812134 Title: Konsole + Terminus font, wrong line alignment To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/konsole/+bug/812134/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
