The fix is in this commit:
https://github.com/bit-
team/backintime/commit/e1ae23ddc0b4229053e3e9c6c61adcb7f3d8e9b3
Which is the only essential difference in 1.3.2.
https://github.com/bit-team/backintime/compare/1.3.1...v1.3.2
--
You received this bug notification because you are a member of
I think, 22.04 being an LTS release, must have a working backup
software.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970090
Title:
Backintime not launching because of python error
To manage
Public bug reported:
Starting backintime fails with the following output:
Traceback (most recent call last):
File "/usr/share/backintime/common/backintime.py", line 27, in
import config
File "/usr/share/backintime/common/config.py", line 32, in
import tools
File
The fix is released in Debian unstable, not in Ubuntu (not even jammy).
** Changed in: lbzip2 (Ubuntu)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926092
** Summary changed:
- XSane plugin not available in File menu
+ XSane plugin not available in GIMP File menu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1948881
Title:
XSane plugin not available
Public bug reported:
Description of the bug
On the initial startup, GIMP initializes plugins, including xsane.
Initializing xsane takes a long time on my system (perhaps, around 20
seconds), and after that the startup completes. However, there is no
option in File->Create menu to create an image
Public bug reported:
lbzip2 package does not contain any binaries in hirsute. Here is the
list of files in groovy:
/usr/bin/lbunzip2
/usr/bin/lbzcat
/usr/bin/lbzip2
/usr/share/doc/lbzip2/changelog.Debian.gz
/usr/share/doc/lbzip2/copyright
/usr/share/man/man1/lbunzip2.1.gz
*** This bug is a duplicate of bug 1924624 ***
https://bugs.launchpad.net/bugs/1924624
It seems, it started happening with kernel version 5.8.0-49. With
5.8.0-48 I can't reproduce this behavior, at least not as easily.
--
You received this bug notification because you are a member of Ubuntu
/snd/controlC0: lastique 1319 F pulseaudio
/dev/snd/controlC1: lastique 1319 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Mon Apr 19 02:18:39 2021
HibernationDevice:
# Prevents "gave up waiting for suspend/resume device" timeout on boot
R
The updated packages don't work for me on groovy.
$ apt policy ubuntu-keyring ubuntu-dbgsym-keyring
ubuntu-keyring:
Installed: 2020.06.17.3
Candidate: 2020.06.17.3
Version table:
*** 2020.06.17.3 500
500 http://ru.archive.ubuntu.com/ubuntu groovy-updates/main amd64
Packages
Public bug reported:
libnss3 package installs these files:
libnss3:amd64, libnss3:i386: /usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.chk
libnss3:amd64, libnss3:i386: /usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.so
libnss3:amd64, libnss3:i386: /usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.chk
Public bug reported:
After upgrading from Kubuntu 20.04 to 20.10, PipeWire gets installed and
started along with PulseAudio. As a result, upon system startup some
audio output and input devices are not visible in PulseAudio. For
example, a Builtin audio device might not have analog output or
At this point it might be worth updating gcc-10 to 10.2.
I'm particularly interested in gcc-10 upgrade because I might be
affected by a g++ bug that is already fixed in a more recent version of
gcc-10. I cannot upgrade locally because the problem appears in a public
Travis CI instance.
--
You
The workaround is to blacklist hid_logitech_hidpp and hid_logitech_dj
modules by adding /etc/modprobe.d/blacklist-hid_logitech.conf with this
content:
```
blacklist hid_logitech_hidpp
blacklist hid_logitech_dj
```
and running `update-initramfs -u -k all`. After reboot, the buttons
start working
n: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
- USERPID ACCESS COMMAND
- /dev/snd/controlC3: lastique 2015 F pulseaudio
- /dev/snd/controlC0: lastique 2015 F pulseaudio
- /dev/snd/controlC2: lastique 2015 F pulseaudio
- /dev/snd/controlC1
nelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC3: lastique 2015 F pulseaudio
/dev/snd/controlC0: lastique 2015 F pulseaudio
/dev/snd/controlC2: lastique 2015 F pulseaudio
** Attachment added: "Output of `libinput list-devices` when the mouse is wired"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875408/+attachment/5361704/+files/libinput_wired.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Fixed in 5.3.0-24.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849993
Title:
DualShock 4 over Bluetooth does not work
To manage notifications about this bug go to:
This bug duplicates
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849993.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1850443
Title:
Bluetooth: hidp: Fix assumptions on the return value
The bug is still present in 5.3.0-22.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849993
Title:
DualShock 4 over Bluetooth does not work
To manage notifications about this bug go to:
I can confirm that the patch[1] in the upstream bug indeed fixes the
problem for me.
[1]: https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth
/bluetooth-next.git/commit/?id=8bb3537095f107ed55ad51f6241165b397aaafac
--
You received this bug notification because you are a member of Ubuntu
Upon connecting the gamepad, kern.log contains the following lines:
Nov 3 12:03:00 lastique-pc kernel: [ 189.682027] sony 0005:054C:05C4.0009:
unknown main item tag 0x0
Nov 3 12:03:00 lastique-pc kernel: [ 189.682133] sony 0005:054C:05C4.0009:
DualShock 4 calibration report's CRC check
Possible upstream bug:
https://bugzilla.kernel.org/show_bug.cgi?id=204877
The bug contains a link with a fix. Please, backport.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849993
Title:
ortVersion: 2.20.11-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC3: lastique 2092 F pulseaudio
/dev/snd/controlC0: lastique 2092 F pulseaudio
/dev/snd/controlC2: lastique 2092 F pulseaudio
/dev/snd/controlC1: lastiqu
The problem exists in the mainline kernel 5.3.7 and does NOT exist with
5.2.21. I cannot test 5.4-rc4 because Nvidia driver doesn't compile for
this kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sending email to 901...@bugs.debian.org bounces because the bug is
archived and cannot be modified.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1793640
Title:
Pulseaudio fails to detect sound
I have tested on Kubuntu 19.04:
1. After installing timidity-daemon, the timidity user is automatically created
and added to the audio group. After reboot, the primary audio output device is
inaccessible in PulseAudio.
2. After removing timidity user from audio group and rebooting, PulseAudio
A user in that bug already verified that it works. What I'm pointing out
is that the user/group fix is not implemented in the Debian or Ubuntu
package, and as long as that bug is closed it's not likely become
implemented.
--
You received this bug notification because you are a member of Ubuntu
Can the Debian bug be reopened? Otherwise, I'm afraid, we'll never see
it fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1793640
Title:
Pulseaudio fails to detect sound card, while timidity
I tried it multiple times, it didn't work, although it failed on
different files. Debian package succeeded from the first attempt.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1713615
Title:
This workaround:
sudo apt purge ttf-mscorefonts-installer && sudo apt install --reinstall
ttf-mscorefonts-installer
does *not* fix the installation on Disco for me. I'm assuming it may fix
the problem for some if the redirection from https to http does not
happen for some reason.
I'm able to
>From the discussion in bug 210472 and in the Debian bug, it looks more
like a configuration or intergration issue in timidity packages rather
than a genuine upstream bug.
Also, forums and mailing lists are a way to report bugs, too. Even
though not as convenient as bug trackers.
--
You
I've upgraded to upower 0.99.8-2ubuntu0.1 and it seems to have fixed the
problem. Keyboard backlight is working now. Thanks!
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
The keyboard backlight control doesn't work in 4.18.16.
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800164
Title:
Keyboard backlight control doesn't
I tested with the mainline Linux kernel 4.19 and the key combinations
work.
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
: 2.20.10-0ubuntu13
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: lastique 2820 F pulseaudio
/dev/snd/controlC1: lastique 2820 F pulseaudio
CurrentDesktop: KDE
Date: Fri Oct 26 17:40:24 2018
InstallationDate: Installed on 2013-10-11 (1840 days
As described in bug
https://bugs.launchpad.net/ubuntu/+source/timidity/+bug/1799541 starting
timidity system daemon can prevent PulseAudio from gaining access to one
of the sound cards in ALSA.
I think, a better solution would be to change timidity to run as a user-
specific service, instead of
I think I found the source of the problem. Apparently, I had running the
timidity daemon, which grabbed the ALSA PCM device and caused the
"Device or resource busy" error. The "fuser -v /dev/snd/*" command
didn't show this as I ran it as an unprivileged user and the daemon runs
under a different
I can add that I've also tried with the kernel 4.15.0-36.39 from Ubuntu
18.04 and the problem also reproduced. Right now I also suspect
systemd/udev or userspace ALSA components because, although I can play
sounds on the "default" and "sysdefault" devices, I cannot play on "D2X"
or "surround51"
The problem reproduces with generic kernel 4.19.0.
** Tags added: kernel-bug-exists-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1799541/+attachment/5204674/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799541
Title:
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1799541/+attachment/5204677/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799541
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1799541/+attachment/5204679/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799541
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1799541/+attachment/5204678/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1799541/+attachment/5204681/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799541
Title:
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1799541/+attachment/5204680/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799541
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1799541/+attachment/5204682/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799541
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1799541/+attachment/5204675/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799541
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1799541/+attachment/5204676/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1799541/+attachment/5204671/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1799541/+attachment/5204673/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799541
Title:
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1799541/+attachment/5204672/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799541
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1799541/+attachment/5204670/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799541
Title:
ASUS
DMI 0
Direct sample mixing device
dsnoop:CARD=PCH,DEV=0
HDA Intel PCH, ALC892 Analog
Direct sample snooping device
dsnoop:CARD=PCH,DEV=1
HDA Intel PCH, ALC892 Digital
Direct sample snooping device
dsnoop:CARD=PCH,DEV=3
HDA Intel PCH, HDMI 0
Direct sample s
CH,DEV=0
HDA Intel PCH, ALC892 Analog
Direct sample mixing device
dmix:CARD=PCH,DEV=1
HDA Intel PCH, ALC892 Digital
Direct sample mixing device
dmix:CARD=PCH,DEV=3
HDA Intel PCH, HDMI 0
Direct sample mixing device
dsnoop:CARD=PCH,DEV=0
HDA Intel PCH, ALC892 Analog
Direct
> Did this issue start happening after an update/upgrade? Was there a
> prior kernel version where you were not having this particular problem?
As said in the description, it started happening after upgrading from
Kubuntu 18.04 to 18.10. 18.04 has kernel 4.15.
> Would it be possible for you to
4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: lastique 3112 F pulseaudio
/dev/snd/controlC1: lastique 3112 F pulseaudio
CurrentDesktop: KDE
Da
Happens when upgrading from Kubuntu 18.04 to 18.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1713615
Title:
ttf-mscorefonts-installer fails because Redirection from https to http
is
Yay, finally! Thank you Daniel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574746
Title:
Enable support for libsoxr
To manage notifications about this bug go to:
> Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
I don't know when this started to happen. But the same netem rules
worked as expected in Ubuntu 17.10.
I've tested kernel version
ric x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: lastique 2087 F pulseaudio
/dev/snd/controlC1: lastique 2087 F pulseaudio
CurrentDesktop: KDE
Date: Thu Jul 26 19:31:25 2
Public bug reported:
When reporting a bug against SDDM (ubuntu-bug sddm) Apport displayed an
error dialog box with only "text" message. See the screenshot.
The error should be more descriptive.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: apport 2.20.9-0ubuntu7
ProcVersionSignature:
Note that the attached modified pam.d/sddm and pam.d/sddm-autologin
files are the result of my attempts to fix the problem. The problem
exists with the original files.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This error dialog box appeared twice - first, when Apport was collecting
information and second right after I pressed Yes on the first one.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769385
Public bug reported:
On automatic login, SDDM does not unlock gnome-keyring, which suspends
the boot process and asks for a password. The boot process blocks until
the password is entered. Apparently, the boot process stops because
Pidgin is in the autostart list and it requires access to the
For me this problem appeared after I upgraded from 17.10 to 18.04 two of
my machines. Both machines increased their boot times substantially (by
around 30 seconds).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Just for the record, I have found the problem that caused the lockups.
It was the nvidia driver ForceCompositionPipeline parameter in
xorg.conf. Without it the hangs no longer happen, but the warnings are
still present in the log.
--
You received this bug notification because you are a member of
The errors in the kernel log don't appear with kernel version 4.10.17.
However, I still get lockups with that kernel as well.
At this point I think the lockups are probably not related to the
warnings and are possibly caused by a hardware failure. The errors in
the log are still a valid issue,
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744379
Title:
tcp_fastretrans_alert
Is it possible that the lockups are caused by the buggy microcode update
from Intel? Did Canonical revert the microcode update?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744379
Title:
I tried kernel 4.15.0-rc9 and had the same kind of hard lockup. The
system wouldn't react to mouse or keypresses after some idle time. The
log is attached (the kernel was upgraded on Jan 24-th). There are many
errors about soft lockups in the log, although the backtraces are
different from 4.13.
> Did this issue start happening after an update/upgrade?
I did not have hard lockups before upgrading to 4.13.0-25. The lockup
happened once, after several days past the upgrade. I did not look in
the logs until after the lockup, so I can't tell if the
tcp_fastretrans_alert errors were there
4.13.0-25-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC3: lastique 3183 F pulseaudio
/dev/snd/controlC1: lastique 3183 F
I have fixed the problem by installing nvidia driver 390.12.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1742302
Title:
Kernel 4.13.0-25 broke nvidia driver
To manage notifications about this
Public bug reported:
When booting into recovery mode and enabling networking, networking does
not get enabled. DNS lookup doesn't work because systemd-resolved does
not start and /etc/resolv.conf is a broken symlink.
Steps to reproduce:
1. Reboot.
2. In the grub menu, select "Advanced options
COMMAND
/dev/snd/controlC0: lastique 3049 F pulseaudio
/dev/snd/controlC2: lastique 3049 F pulseaudio
/dev/snd/controlC3: lastique 3049 F pulseaudio
/dev/snd/controlC1: lastique 3049 F pulseaudio
CurrentDesktop: KDE
Date: Wed Jan 10 02:00:46 2018
InstallationDate
I've created a MIR ticket for libsoxr:
https://bugs.launchpad.net/ubuntu/+source/libsoxr/+bug/1702558
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574746
Title:
Enable support for libsoxr
To
Public bug reported:
[Availability]
libsoxr is in "universe", it compiles for all target architectures:
https://launchpad.net/ubuntu/+source/libsoxr/0.1.2-2
[Rationale]
I would like libsoxr to be moved to "main" so that it can be used in
PulseAudio as an audio resampler backend (see
I don't see 3.2.5-1 packages in Zesty, only 7:3.2.4-1build2.
** Changed in: ffmpeg (Ubuntu)
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1688735
Title:
Public bug reported:
I have an OpenVPN connection with statically configured DNS server
address and the search domain. When this connection is established,
there is a high chance that the DNS address and the search domain are
not pushed to systemd-resolved for this connection. The problem does
I have reported the bug upstream:
https://bugzilla.gnome.org/show_bug.cgi?id=782469.
** Bug watch added: GNOME Bug Tracker #782469
https://bugzilla.gnome.org/show_bug.cgi?id=782469
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
When vdpau-copy hardware decoder is used, mpv displays an error such as
this:
The linesize 1280 cannot be represented as uint32
The problem is a bug in ffmpeg that was fixed in 3.3.0 but is present in
3.2.4 which is released in Ubuntu 17.04.
I'm attaching the patch that
> And if you had a look at the upstream bug you'd see that the patch
doesn't work.
I can see that someone reported it to not work for one-key combinations
(e.g. Ctrl). I believe, the previous patch that was removed had the same
limitation, and it was "good enough".
We need to see if it works for
Public bug reported:
For split-tunnelling VPN connections (i.e. when the "Use only for
resources on this connection" checkbox is set in the IPv4 -> Routes
menu), the IPv4 -> Search Domains field has no effect.
For example, my VPN connection has the following parameters:
[ipv4]
Since this bug is marked as resolved for xorg-server, I've created a new
one: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1683383.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
Public bug reported:
This is a reopen of bug #36812, which has reappeared in Kubuntu 17.04
Zesty Zapus.
This is a bug about shortcuts mapped to combinations which include each
other.
For example, if we have Ctrl+Shift (for keyboard layout) and Ctrl+Shift+N (to
open a new terminal), then we are
I've changed this to Confirmed because it broke the upgrade from Yakkety
to Zesty for me. The upgrade process stopped after the package updating
step, with this message:
Upgrade complete
The upgrade has completed but there were errors during the upgrade
process.
It didn't offer to remove
I'll add that apparently the upgrading process did not fully complete
either because `apt-get dist-upgrade` still had lots of packages left to
upgrade.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm not sure what that link points to but neither plasma-workspace-dbg
nor plasma-workspace-dbgsym is installable on my system. Neither of
these packages is found at http://packages.ubuntu.com/ in yakkety
(search by package names).
I've attached my /etc/apt/sources.list.
** Changed in:
Public bug reported:
There is no plasma-workspace-dbg package for Kubuntu 16.10 (and 17.04),
which makes it difficult to diagnose problems related to plasmashell.
The package is present for 16.04. Please, add the package for other
releases as well.
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Public bug reported:
I'd like to ask to enable support for libsoxr-based resamplers in the official
Ubuntu packages for pulseaudio. The upstream already supports libsoxr and
automatically detects its availability, so the only change really needed is to
add the build dependency to
Public bug reported:
When starting xfce4-volumed from the command line in non-daemon mode it
fails to bind the "increase volume" multimedia key with the following
error:
** (xfce4-volumed:5338): WARNING **: Binding 'XF86AudioRaiseVolume'
failed!
At the same time it binds the "decrease volume"
I'm having the problem in wily with xfce4-volumed - it doesn't react to
multimedia volume keys.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1347272
Title:
Several XFCE applications appear
Yes, thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1471791
Title:
Thunderbird package is outdated
To manage notifications about this bug go to:
Public bug reported:
Thunderbird version shipped with Ubuntu is 31.7.0, which is much older
than the current version 38.0.1 released by Mozilla. The package version
is the same in 15.04 and 15.10. Please, update the package to a more
recent Thunderbird version.
ProblemType: Bug
DistroRelease:
I have solved the problem. Apparently, the keys were disabled in the
keyboard by a hardware switch, and I didn't notice that. Sorry for the
noise.
** Changed in: linux (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I tried the 4.1.0-040100rc6-generic and it still doesn't work. I'm
attaching the output of evtest.
** Attachment added: The output of evtest.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1455915/+attachment/4410852/+files/event4.txt
** Changed in: linux (Ubuntu)
Status:
** Attachment added: xkbcomp -xkb :0 - output
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1455915/+attachment/4398944/+files/xkbcomp.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: lastique 2083 F pulseaudio
/dev/snd/controlC1: lastique 2083 F pulseaudio
/dev/snd/controlC3: lastique 2083 F pulseaudio
/dev/snd/controlC0: lastique
** Attachment added: setxkbmap -print output
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1455915/+attachment/4398947/+files/xkbmap.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
1 - 100 of 156 matches
Mail list logo
