Standard Docker images contain a file /etc/apt/apt.conf.d/docker-gzip-
indexes with
Acquire::GzipIndexes "true"; Acquire::CompressionTypes::Order:: "gz";
in it. So c-n-f is broken there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
*** This bug is a duplicate of bug 1907878 ***
https://bugs.launchpad.net/bugs/1907878
** This bug has been marked a duplicate of bug 1907878
wrong var declaration in if-up.d/resolved (nm-dispatcher[54417]:
/etc/network/if-up.d/resolved: 12: mystatedir: not found)
--
You received this
Also note: there was been a huge refactoring in this file in the commit
05569e53fd3e ("KCM/Component Revamp Browser config"). The commit is
available in the release v5.18.90.
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to plasma-desktop in
Something should be wrong in
kcms/componentchooser/componentchooserbrowser.cpp , probably in
CfgBrowser::configChanged() and/or CfgBrowser::load().
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I think I know how to reproduce it:
In my .config/kdeglobals I have a line
[General]
BrowserApplication[$e]=chromium-browser.desktop
...
After I removed this line, the "Apply"button started to work properly,
and I could select Chrome. The line after saving:
[General]
The file with the string "with the following command:" is
/usr/lib/x86_64-linux-gnu/qt5/plugins/kcm_componentchooser.so from
plasma-desktop.
ii plasma-desktop4:5.18.4.1-0ubuntu1
amd64Tools and widgets for the desktop
** Also affects: plasma-desktop
Chromium has been my default browser for quite long time. Recently,
somewhere during the Focal development phase, Konqueror started to get
launched by default, and I can change but cannot save the settings with
the System Settings application anymore.
** Package changed: chromium-browser (Ubuntu)
Public bug reported:
The default browser cannot be changed in Kubuntu 20.04
Reproduce:
Open "System Settings", select "Default Application"->"Web Browser",
change a radio button state.
Result: "Apply" stays disabled, the changes are not saved.
Expected: the button "Apply" becomes active, like
A fix could be ported, or a package could be upgraded to v0.6.2. See
https://github.com/docker/docker-credential-
helpers/pull/29/commits/79f93e5e69abc2ead458d19f4577b64b7e35c504
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1813003 ***
https://bugs.launchpad.net/bugs/1813003
** This bug has been marked a duplicate of bug 1813003
Invalid free while running docker build
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Here is a simple patch based on plymouth-theme-ubuntu-text.install that
fixes both
dpkg: warning: version '/etc/lsb-release' has bad syntax: version
number does not start with digit
and
rmdir: failed to remove '/lib/plymouth/': No such file or directory
** Patch added:
Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900242
** Bug watch added: Debian Bug tracker #900242
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900242
** Also affects: samba via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900242
Importance: Unknown
The script /usr/share/samba/panic-action contains lines:
echo "If the problem persists, you are encouraged to first install the"
echo "samba-dbg package, which contains the debugging symbols for the Samba"
echo "binaries. Then submit the provided information as a bug report to"
But since the
Public bug reported:
Ubuntu 18.04 Bionic Beaver
Linux 4.15.0-22-generic #24-Ubuntu SMP Wed May 16 12:15:17 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
>From time to time I get emails like the one below. I don't use samba
actively, it's installed as a dependency with default settings.
The emails
ii libsmbclient:amd64
2:4.7.6+dfsg~ubuntu-0ubuntu2amd64shared library for
communication with SMB/CIFS servers
ii libwbclient0:amd64
2:4.7.6+dfsg~ubuntu-0ubuntu2amd64Samba winbind client
Checked out the logs https://launchpadlibrarian.net/371726798
/buildlog_ubuntu-cosmic-amd64.mplayer-skins_3.2build1_BUILDING.txt.gz
and found the problem: pkgstripfiles from the package pkgbinarymangler
is stripping the files. To disable this script, "export
NO_PNG_PKG_MANGLE=1" should be added to
The new package http://de.archive.ubuntu.com/ubuntu/pool/multiverse/m
/mplayer-skins/mplayer-skins_3.2build1_all.deb still doesn't work. The
PNG files are stripped differently from the 3.2 version, but also
differently from the package that I have built locally in a docker image
(ubuntu:bionic)
mplayer-gui can be fixed by reuploading mplayer-skins, see
https://bugs.launchpad.net/ubuntu/+source/mplayer/+bug/1218510
Therefore, no need to delete it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi All!
This problem can be solved in a very easy way: just rebuild and reupload
the package.
Explanation:
The PNG files were probably stripped by some bogus script between the versions
3 (16 Oct 2009) and 3.1 (28 Aug 2013), that were also present at the times of
3.2 (29 May 2014). See
Thanks dino99!
Are any actions from me required?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1706223
Title:
tcsh subshell escaping broken
To manage notifications about this bug go to:
dino99, why should this bug be marked as Invalid? The newer releases
(Artful and Beaver-dev) are still (as of today) have the older version
(3:4.8.19-1) of Midnight Commander without the patch (upstream release
4.8.20 of 25.11.2017). The newer releases just weren't released in July
2017.
PS I
*** This bug is a duplicate of bug 1720519 ***
https://bugs.launchpad.net/bugs/1720519
** This bug has been marked a duplicate of bug 1720519
KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once at
most. Refusing to load.
--
You received this bug notification because you
Here is the fix of the problem:
Use the right type for `len`, avoid segmentation fault
`getline()` requires its second parameter to be `size_t *`. On the amd64
platform the size of `unsigned int` is 4 and the size of `size_t` is 8
bytes. Using a wrong pointer type can lead to a stack variables
Public bug reported:
discover 2.1.2-7.1
libdiscover2 2.1.2-7.1
Ubuntu artful amd64
Running `discover` produces a crash:
Program received signal SIGSEGV, Segmentation fault.
__strlen_sse2 () at ../sysdeps/x86_64/multiarch/../strlen.S:120
120 ../sysdeps/x86_64/multiarch/../strlen.S: No such
After updating one of these packages I don't have this problem anymore.
Unfortunately, I cannot pinpoint the exact package that fixed it.
-at-spi2-core 2.25.91-0ubuntu1 amd64
+at-spi2-core 2.26.0-2 amd64
-bind9-host 1:9.10.3.dfsg.P4-12.5ubuntu1 amd64
+bind9-host 1:9.10.3.dfsg.P4-12.6ubuntu1 amd64
I'm afraid, the problem can be in some related QT or KDE library: I've
tried to downgrade sddm and sddm-theme-breeze to the versions from zesty
(0.13.0-1ubuntu5 and 4:5.9.4-0ubuntu1 correspondently), but the problem
is still there.
KDE version 4:5.10.5-0ubuntu1, QT version 5.9.1+dfsg-5ubuntu2.
The letters on the visual keyboard are invisible too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1717608
Title:
Invisible text (fonts) in SDDM login screen
To manage notifications about this
Interesting though, if you click the place with the mouse, where the
"show password" eye icon should be, the password text is visible (or the
grey "Password" is shown). But if you click it again, the text
disappears.
The eye icon is invisible during the log in, but visible on the lock
screen.
Public bug reported:
Ubuntu: 15.10-17.10
Toggling the "Bluetooth device interface status" tunable tries to
execute commands `/usr/sbin/hciconfig hci0 up` and `/usr/sbin/hciconfig
hci0 down`, and produce messages `sh: 1: /usr/sbin/hciconfig: not
found`.
See bt_tunable::bt_tunable() in
The issue has been fixed in
https://github.com/MidnightCommander/mc/commit/0fec3ef449de6f22281161ba7af8f5dbb948292d
, and is to appear in the next mc release (4.20).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Bug watch added: Midnight Commander Bug Tracker #3852
http://midnight-commander.org/ticket/3852
** Changed in: mc
Importance: Undecided => Unknown
** Changed in: mc
Status: New => Unknown
** Changed in: mc
Remote watch: None => Midnight Commander Bug Tracker #3852
--
You
** Also affects: mc (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- Escaping broken
+ tcsh subshell escaping broken
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1706223
Christos explained that tcsh escaping is tricky, buggy, and "fixing" it
in a proper way can break legacy scripts.
I propose to fix the problem on the Midnight Commander side instead. To
prevent messages like 'Warning: Cannot change to /tmp/a b/c d..' and
failure to cd to such directories when
I'm also trying to contact the upstream commit author Christos Zoulas,
but he seems to be busy.
The website http://tcsh.org/ is down right now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1706223
I'm sorry, actually the Christos have naswered my email, but it got into
the spam folder. Let's see if we can get an upstream solution.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1706223
Title:
Public bug reported:
Release: Ubuntu 17.04 Zesty
tcsh version: 6.20.00-7
I’m trying to fix the integration between mc and the recent version of
tcsh (as a subshell) that got broken in Ubuntu 17.04 Zesty. I have
noticed that the escaping has been changed in the commit
** Changed in: ktorrent (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/1207589
Title:
ktorrent fails to unzip peerguardian filter file
To manage notifications
Kubuntu 17.04 Zesty, ktorrent 4.3.1-5
The file from
"http://list.iblocklist.com/?list=bt_level1=p2p=gz;
is being downloaded, but not ungzipped. Ktorrent says:
```
There are no IP addresses to convert in
_USERNAME_SKIPPED_/.kde/share/apps/ktorrent/level1.txt
```
--
You received this bug
I've installed http://archive.ubuntu.com/ubuntu/pool/restricted/n
/nvidia-graphics-drivers-304/nvidia-304_304.132-0ubuntu2_amd64.deb , and
dmesg doesn't complain about the mtrr functions anymore, but the X
doesn't work: I see the big green Nvidia logo, and then a black screen
instead of sddm, but
tcsh_6.18.01-5ubuntu0.16.10.1_amd64.deb works for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1618803
Title:
tcsh crashed with SIGSEGV in __GI___rewinddir()
To manage notifications about
I also get a crash with `/bin/tcsh -c "ls-F"`:
```
(gdb) bt
#0 0x7f84413711d8 in rewinddir () from /lib/x86_64-linux-gnu/libc.so.6
#1 0x00427985 in ?? ()
*** This bug is a duplicate of bug 1618803 ***
https://bugs.launchpad.net/bugs/1618803
** This bug has been marked a duplicate of bug 1618803
tcsh crashed with SIGSEGV in __GI___rewinddir()
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
PS bash, ksh and mksh don't crash.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1635159
Title:
tcsh crashes with segv when listing directories
To manage notifications about this bug go to:
I can confirm the same problem: linux kernel 4.8.0-26.28 (Yakkety), tcsh
6.18.01-5. Tcsh crashes during auto completion, gdb says:
#0 0x7fae17e031d8 in rewinddir () from /lib/x86_64-linux-gnu/libc.so.6
#1 0x00427985 in ?? ()
#2 0x00429431 in ?? ()
#3 0x0042a8bb in
There is a new bug opened https://bugs.launchpad.net/ubuntu/+source
/nvidia-graphics-drivers-304/+bug/1634802 , that shows the same problem
that Brian observes in the Yakkety release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
> nm /lib/modules/4.8.0-26-generic/updates/dkms/nvidia_304.ko | fgrep mtrr
U mtrr_add
U mtrr_del
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1634802
Title:
Could
See also the last comments in https://bugs.launchpad.net/ubuntu/+source
/nvidia-graphics-drivers-304/+bug/1531151
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1634802
Title:
Could not insert
I can confirm: the driver was working in 16.04, but stopped working in
16.10, with the same messages about mtrr_del/mtrr_add.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1634802
Title:
Could not
48 matches
Mail list logo
