** Tags added: eoan
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1839580
Title:
LucidSound LS31 only outputs mono sound
Status in pulseaudio package in Ubuntu:
In
Upstream merge request.
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/merge_requests/143
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1839580
Title:
Public bug reported:
LucidSound LS31 only outputs mono sound.
The usb vendor:prod = 2f12:0109.
The fix is incoming.
** Affects: pulseaudio (Ubuntu)
Importance: Undecided
Assignee: Dave Chiluk (chiluk)
Status: In Progress
** Changed in: pulseaudio (Ubuntu)
Status: New
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]
** Changed in: bluez (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
[Expired for linux-firmware (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: linux-firmware (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in
[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]
** Changed in: pulseaudio (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
please install headers first:
sudo apt install linux-headers-5.0.0-24
sudo apt install linux-headers-5.0.0-24-generic
Then install the dkms.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
@Hui Wang
Last time, I installed the file by double click it, as I see it's a .deb
file. The installation process went with no issue at all.
Now this time, I am trying to install the file via terminal. But it
never finish the building, as shown my terminal like this...
(Reading database ...
Public bug reported:
Additional software needed, but when i click it and open ubuntu software
center there is nothing in there i can install. and when i try to print
some document it is always canceled somehow.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: cups 2.2.7-1ubuntu2.6
I enabled bionic-proposed and installed ibus, ibus-gtk, ibus-gtk3
versions 1.5.17-3ubuntu5.
I ran the test in a bionic VM which had VMware Horizon Agent for Linux
installed, version 7.9.0-13916467.
Running firefox with no environment variables caused long input delays
and small lockups with the
Here is a quick reproducer.
sudo apt update
sudo apt install slapd ldap-utils -y
Reconfigure the slapd package. When asked about a domain, use
"example.com". Choose a password, and accept defaults for everything
else:
sudo dpkg-reconfigure slapd
Create a file called add-rwm.ldif with these
Private bug reported:
After updating the mesa, the management of my graphic environment is no
longer as fluid.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: libegl-mesa0 19.1.4-1ubuntu1
Uname: Linux 5.2.7-050207-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
BootLog:
I can verify that here as well
uname -a
Linux localhost 5.0.0-23-generic #24~18.04.1-Ubuntu SMP Mon Jul 29 16:12:28 UTC
2019 x86_64 x86_64 x86_64 GNU/Linux
chris@localhost:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.3 LTS
Release:
Public bug reported:
Support for .whl/.egg files (used in Python packaging) was added to
lesspipe in version 487-0.1 of less[1], but the lesspipe(1) manual page
was apparently not updated at the time, and does not currenly list
.whl/.egg as supported file types.
This looks like a Debian bug,
Still in 18.04 LTS
> uname -a
Linux Meerkat 5.0.0-23-generic #24~18.04.1-Ubuntu SMP Mon Jul 29 16:12:28 UTC
2019 x86_64 x86_64 x86_64 GNU/Linux
> lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.3 LTS
Release:18.04
Codename: bionic
Here's the syslog, starting at the point where I have a connection to a
local wifi, and then I have a failed switch to the other local wifi. (I
am sending this after capturing the log, and restarting the network-
manager service.)
Aug 8 10:01:22 serval NetworkManager[14891]: [1565283682.3253]
** Changed in: procps (Ubuntu)
Status: In Progress => Fix Committed
** Summary changed:
- pgrep: Use POSIX _SC_ARG_MAX for maximum pgrep -f command line length
+ pgrep: allows long command lines to be searched e.g. java process with long
classpath
--
You received this bug notification
** Also affects: gtk+3.0 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1726129
Title:
nautilus crashed with SIGSEGV
** Changed in: procps (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: procps (Ubuntu Disco)
Importance: Undecided => Low
** Changed in: procps (Ubuntu Xenial)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Touch
** Description changed:
[Impact]
The pgrep -f and pkill -f commands are unable to find processes strings in
processes which are beyond the 4096th character. This often happens with Java
command lines with long classpaths on the command line.
[Test Case]
A quick test to reproduce this
It's your job as a user to make sure the outcome is what you want. Don't
blindly use -y.
Yes, install can remove conflicting packages, this is by design.
** Changed in: apt (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch
The attachment "debdiff for xenial systemd branch" seems to be a
debdiff. The ubuntu-sponsors team has been subscribed to the bug report
so that they can review and hopefully sponsor the debdiff. If the
attachment isn't a patch, please remove the "patch" flag from the
attachment, remove the
Public bug reported:
I performed this command (didn't know which package provided what I
needed)
apt install -y lib64readline-dev libreadline-dev
This REMOVED these packages:
dkms oem-ethernet-realtek-r8152-lp1806322-4.15-dkms-dkms ubuntu-desktop
x11-session-utils xorg
To my way of thinking,
Hello, everyone.
Here's a debdiff patch with a backport of upstream patch to xenial
branch of systemd.
I've successfully built a modified source and deployed it to some xenial
machines — it works as intended, failed service restart correctly, just
as intended by Restart=always policy.
Before:
Public bug reported:
Hardware: Dell Latitude E6430 with GF108GLM [NVS 5200m]
Lubuntu 19.04
LBS Release: Description:Ubuntu 19.04
software-properties-qt:
Installed: 0.97.11
Candidate: 0.97.11
Version table:
*** 0.97.11 500
500 http://us.archive.ubuntu.com/ubuntu disco/universe
Possible solution would be changing the "Cdrom with" part to something
that can be used in most languages without a translation.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
In my case I'm trying to get softdog to load for SBD instead of the
watchdog daemon.
I can see the point of marking it as opinion, but as Olivier points out,
you have to eliminate the blacklist entry from all of the blacklists
spammed into /lib/modprobe.d, systemd-modules-load does not
I see that the version strings are hardcoded in
data/templates/Ubuntu.info.in, for example for Ubuntu 19.10:
_Description: Ubuntu 19.10 'Eoan Ermine'
_Description: Cdrom with Ubuntu 19.10 'Eoan Ermine'
Not sure if my suggested solution from #2 could be applied on the .in
file, but it would be
Issue still exists in 18.04.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1535840
Title:
systemd ignoring /etc/modules due to blacklist
Status in systemd package in
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: alsa-driver (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
Using 0.96.24.32.11 (which includes the changes from here) the control
is available and the indicator correctly responds to the status changes,
marked as verified
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You
Using 0.96.24.32.11 (which includes the changes from here) the status
information is correctly displayed, marking as verified
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification because
The PPD you have now is completely different, it is not auto-generated
based on a get-printer-attributes IPP request but it is a generic PPD
which is part of the cups-filters package.
How did you set up your printer under Disco? How did you set it up under
Eoan? Does your printer actually print
** Attachment added: "E ipp output"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1837098/+attachment/5281623/+files/e_ipp.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
** Attachment added: "E PPD"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1837098/+attachment/5281616/+files/C43x.ppd
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
Using Ubuntu 18.04.3 LTS with 4.15.0-55-generic #60-Ubuntu SMP Tue Jul 2
18:22:20 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
Output:
libva info: VA-API version 1.1.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/nouveau_drv_video.so
libva info:
kodi_crashlog-20190808_093922.log
** Attachment added: "kodi_crashlog"
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836979/+attachment/5281622/+files/kodi_crashlog-20190808_093922.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Could you also attach the ipptool output of Eoan, to see whether this is
different?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1837098
Title:
Can't print in monochrome,
Could you post the PPD file of Eoan then, so tat I can compare?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1837098
Title:
Can't print in monochrome, only in colour
** Changed in: nut (Ubuntu)
Status: Triaged => Incomplete
** Changed in: modemmanager (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to modemmanager in Ubuntu.
Hm, I forgot to re-add the bug reference after a few iterating over
another change, sorry. But this is a good SRU candidate.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
According to your post, I have modified /lib/udev/rules.d/69-lvm-metad.rules
the line 96, but no.
# the ACTION!="remove", ENV{violently _pv_gone}=="1",
RUN+="/usr/bin/systemd-run /sbin/ LVM pvscan --cache $major:$minor", GOTO="
violently _end"
The ACTION!="remove", RUN+="/sbin/ LVM pvscan
I wasnt able to get a backtrace because there was "no stack".
This is what shows in gdb:
Program received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
50 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb)
Continuing.
Please reopen if you still have this issue!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to json-c in Ubuntu.
https://bugs.launchpad.net/bugs/1695611
Title:
libjson-c3-0.12.1-1.1 has building bug
Status in json-c package
I hope it is ok now
** Changed in: json-c (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to json-c in Ubuntu.
https://bugs.launchpad.net/bugs/1695611
Title:
libjson-c3-0.12.1-1.1
I tested E and that seems to work as expected.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1837098
Title:
Can't print in monochrome, only in colour
Status in cups
** Attachment added: "error_log"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1839446/+attachment/5281584/+files/error_log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
Sorry, wrong bug, ignore that comment.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1839446
Title:
When trying to print a test page CUPS crashes
Status in cups package in
I've tested this on E, and I can now print in B and Colour again.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1839446
Title:
When trying to print a test page CUPS crashes
Could you follow the instructions of the section "CUPS error_log" on
https://wiki.ubuntu.com/DebuggingPrintingProblems to get an error_log in
debug mode from the CUPS crash?
Also some form of backtrace of the crashing CUPS daemon would be great
(apport record? cupsd run in a way that one can
Public bug reported:
I'm trying to get my printer working correctly and when I try and print
test pages it seems like cups crashes and restarts in the background.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: cups 2.2.10-4ubuntu2
ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15
** Merge proposal linked:
https://code.launchpad.net/~fourdollars/ubuntu/+source/systemd/+git/systemd/+merge/370808
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Merge proposal linked:
https://code.launchpad.net/~fourdollars/ubuntu/+source/systemd/+git/systemd/+merge/370808
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Attachment added: "Disco PPD"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1837098/+attachment/5281554/+files/Samsung_C43x_Series_printer_.ppd
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
Hello Matthew, or anyone else affected,
Accepted ibus into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/ibus/1.5.17-3ubuntu5
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Excellent. If the issue is reproducible and affects multiple users, this
seems like a +1 on the SRU.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1838358
Title:
Ibus
This bug was fixed in the package cups - 2.2.11-0ubuntu1
---
cups (2.2.11-0ubuntu1) eoan; urgency=medium
* New upstream release
* Removed 10 patches taken from upstream.
* Refreshed 13 patches with quilt.
* Removed patch to set "LogDebugHistory 9" as it causes high
This bug was fixed in the package cups - 2.2.11-0ubuntu1
---
cups (2.2.11-0ubuntu1) eoan; urgency=medium
* New upstream release
* Removed 10 patches taken from upstream.
* Refreshed 13 patches with quilt.
* Removed patch to set "LogDebugHistory 9" as it causes high
According to the alsa-info.txt in the #73, the fix in the dkms of #72
doesn't apply to your machine.
Did you install the dkms of #72 successfully?
please run 'dkms status' to check if oem-audio-hda-daily-dkm is
installed or not.
--
You received this bug notification because you are a member of
59 matches
Mail list logo
