Persists on a freshly reinstalled system.
Output from ping -i6 [host] follows. Note the spike in ping time and
high packet loss.
64 bytes from [host]: icmp_seq=3833 ttl=64 time=0.223 ms
64 bytes from [host]: icmp_seq=3834 ttl=64 time=0.212 ms
64 bytes from [host]: icmp_seq=3835 ttl=64
Persists on a freshly reinstalled system.
Output from ping -i6 [host] follows. Note the spike in ping time and
high packet loss.
64 bytes from [host]: icmp_seq=3833 ttl=64 time=0.223 ms
64 bytes from [host]: icmp_seq=3834 ttl=64 time=0.212 ms
64 bytes from [host]: icmp_seq=3835 ttl=64
Public bug reported:
bluetooth network in my ubuntu is not working.actually the on button in the
setting does not turn bluetooth button in to ON, it remains OFF even if i click
on it.i already installed bluez and blueman .
i am using this version of ubuntu
Description:Ubuntu 18.04.1 LTS
@ Spas Spasov (spaszspasov)
Your kernel is out of date. Please upgrade the kernel, or contact the
host administrators to apply at least
https://wiki.openvz.org/Download/kernel/rhel6/042stab134.7
** Changed in: systemd (Ubuntu)
Status: Confirmed => Incomplete
** Description changed:
+ So
Sorry for the noise, it seems this is not related to rsyslog after all.
In our install process we are moving /var/log to another partition
(mounted in /data/) and then symlink it to /var/log. Permissions are set
up properly and work while the system is running. When the system is
rebooted though
I followed previous hint , but issue still occurs.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1778984
Title:
Parse error of /etc/apparmor.d/tunables/home.d/ubuntu
Public bug reported:
USB DAC stops playing sound after a second.
I had problem with kernel 4.15.
So, I tried upgrading to 4.19 but still issue persists.
I think, we might need to add it to sound/usb/quirks.c
I see following in dmesg
[ 5937.978117] usb 1-1.4.2: USB disconnect, device number 16
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apparmor (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
@ David (dasoto)
Please report bad permissions to whoever is distributing the "NVIDIA Jetson TX2
users" installation you are using. Maybe there are some upgrade hooks that
could be shipped by packages install in that installation to fix / mitigate
this issue.
--
You received this bug
** Changed in: initramfs-tools (Debian)
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1811447
Title:
update-initramfs
This issue accelerating/cascading to the extent that that the lxc arch
linux guest is now entirely dead
https://bugs.archlinux.org/task/61428
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
I agree with your point so won't be opening a bug to change the
defaults. But it should be easy to enable somewhere in the GUI sound
settings at least for specific applications. Video conferencing like
appear.in is only really usable with headphones because of this.
Adjusting text config files is
This issue is fixed in Debian since July 2018 - initramfs-tools version
0.132, please accept this simple, 3 lines patch from Debian into Ubuntu
18.04 :
https://salsa.debian.org/kernel-team/initramfs-
tools/commit/312393b0cf1231125eeff3d1a2b6b778a935c21d
Look at bug #1781746 for more info.
**
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: initramfs-tools (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
This bug doesn't exist in Debian, it's only Ubuntu related workaround for
Ubuntu 14.04 (Trusty), see LP bug #1258202
logrotate (3.8.6-1ubuntu2) trusty; urgency=low
* debian/logrotate.conf: use group 'syslog' by default when rotating logs,
otherwise logrotate will refuse to rotate logs in
Thanks for opening the ticket and attaching the patch.
I've generated a new version for bionic and cosmic, both can be found here:
https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+packages?field.name_filter=zeromq3
Would anyone mind testing it before we release it?
Thanks
Excellent Brian! Thank you for your work!
--
Cristian Aravena Romero (caravena)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1787729
Title:
apport-autoreport.service
** Also affects: apport (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Changed in: apport (Ubuntu Cosmic)
Status: New => Triaged
** Changed in: apport (Ubuntu Cosmic)
Importance: Undecided => High
--
You received this bug notification because you are a member of
(unsubscribing sponsors, it's not ready to be uploaded)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1793876
Title:
software-properties-qt/kde does not show
I have pushed a version of initramfs-tools to my ppa that seems to fix
the problem. Can IBM test it?
add-apt-repository ppa:cascardo/kdump2
It's a version for bionic. Only initramfs-tools should come from this
source. kdump-tools and makedumpfile should be from bionic-updates or
bionic.
After
** Summary changed:
- [FAILED] Failed to start Process error reports when automatic reporting is
enabled.
+ apport-autoreport.service fails if whoopsie isn't running
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in
*** This bug is a duplicate of bug 1676547 ***
https://bugs.launchpad.net/bugs/1676547
This issue is still alive and well in 2019. I encountered it while
upgrading from 18.04 to 18.10.
Advice from comment six resolved it, but it wasted several hours of my
time. Please apply a fix or at least
Thanks for opening the ticket and attaching the patch.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zeromq3 in Ubuntu.
https://bugs.launchpad.net/bugs/1811531
Title:
remote execution vulnerability
Status in zeromq3
** Description changed:
I have noticed that Kubuntu 18.04 (Bionic Beaver) does not login to
public Wifi hotspots without wifi security, that require login through a
web page. I don't know if this is reproducible on arbitrary public
networks, or only on the few I tried.
The solution
** Changed in: apport (Ubuntu)
Assignee: (unassigned) => Brian Murray (brian-murray)
** Changed in: apport (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
** Changed in: zeromq3 (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zeromq3 in Ubuntu.
https://bugs.launchpad.net/bugs/1811531
Title:
remote execution vulnerability
Status
** Description changed:
Test Case
-
1) install apport-noui
2) sudo service apport stop
3) modify /usr/share/apport/whoopsie-upload-all to exit(1) thereby recreating
the situation where whoopsie isn't running. I did this by copying lines 159,160
to 161,162 and unindenting them.
** Description changed:
Impact
--
If automatic crash reporting is enabled and apport-autoreport.service starts
before whoopsie on boot then crash reports that happened during shutdown or
start up will not be automatically uploaded to the error tracker.
Test Case
-
1)
** Changed in: apport (Ubuntu Cosmic)
Status: Triaged => In Progress
** Changed in: apport (Ubuntu Cosmic)
Assignee: (unassigned) => Brian Murray (brian-murray)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
>From what I understand, LXD is moving toward SNAP LXD as a default, so
not being able to run SNAP in an LXD container configured for "nesting":
re -
lxc config set security.nesting true
Is basically going to prevent LXD from being used for Nested Containers.
--
You received this bug
** Also affects: apparmor
Importance: Undecided
Status: New
** Changed in: apparmor
Status: New => Confirmed
** Changed in: apparmor
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Okay, I am confused now.
I have another system for with usb DAC works just fine.
Distributor ID: Ubuntu
Description:Ubuntu 18.10
Release:18.10
Codename: cosmic
Linux 4.18.0-13-generic x86_64
And dmesg show me same issue:
[ 3649.034233] usb 3-1: new full-speed USB device
Public bug reported:
login:
password:
Just do nothing. About two seconds later ...
login:
password:
login:
password:
login:
password:
After this being displayed three times:
"Too many failure" or so and login is restarting.
You cant login at all. Only solution: clear the password for the
I just updated to apport 2.20.10-0ubuntu19
** Attachment added: "$ dpkg -l | grep apport"
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1787729/+attachment/5229748/+files/dpkg_-l_+_grep_apport.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Changed in: rhythmbox (Ubuntu)
Status: New => Invalid
--
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/1763940
Title:
Pressing Print Screen in keyboard makes
** Changed in: rhythmbox (Ubuntu)
Status: New => Invalid
--
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/1768364
Title:
Combo boxes close immediately after opening
** Description changed:
+ Test Case
+ -
+ 1) install apport-noui
+ 2) sudo service apport stop
+ 3) modify /usr/share/apport/whoopsie-upload-all to exit(1) thereby recreating
the situation where whoopsie isn't running. I did this by copying lines 159,160
to 161,162 and unindenting them.
Setting the password again you'll have a login, but you cant type in
your password. After typing your login name followed by RETURN password
is immediately left. Looks like the entered RETURN is kept and all
subsequent calls see RETURN and just quit.
--
You received this bug notification because
** Description changed:
+ Impact
+ --
+ If automatic crash reporting is enabled and apport-autoreport.service starts
before whoopsie on boot then crash reports that happened during shutdown or
start up will not be automatically uploaded to the error tracker.
+
Test Case
-
1)
Thank you for your bug report, that's not a network-manager issue
though, there is no need to create that file since the package already
provides a binary with that configuration 'network-manager-config-
connectivity-ubuntu' which is installed by default on Ubuntu. The issue
could be that Kubuntu
I rebooted the notebook, and reviewed the service: 'systemctl status
apport-autoreport.service':
● apport-autoreport.service - Process error reports when automatic reporting is
enabled
Loaded: loaded (/lib/systemd/system/apport-autoreport.service; static;
vendor preset: enabled)
Active:
The lines have been added to:
/lib/systemd/system/apport-autoreport.service
---
[Unit]
[...]
Wants=whoopsie.service
After=whoopsie.service
** Attachment added: "$ cat /lib/systemd/system/apport-autoreport.service"
A fix for this bug was uploaded on the 10th but didn't seem to migrate
out of -proposed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-files in Ubuntu.
https://bugs.launchpad.net/bugs/1808508
Title:
Valgrind doesn't
the gnome-shell error is a bit weird, maybe there is an issue on this
component
** Also affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Yes in that case it sounds like an potential enhancement request that
Firefox or other apps using PulseAudio could implement.
** Changed in: pulseaudio (Ubuntu)
Status: Incomplete => Opinion
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Yes in that case it sounds like a potential enhancement request that
Firefox or other apps using PulseAudio could implement.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
** Description changed:
libzeitgeist-1.0-1 is superseded by libzeitgeist-2.0-0 which is built by
zeitgeist with a slightly different API.
All rpdends must transition to it:
- nautilus, unity-china-video-scope, unity-lens-applications, unity-lens-video,
unity-scope-video-remote
+
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
** Tags removed: artful zesty
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1724307
Title:
[Dell XPS 13 9360]
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Note: This only occurs if the file is in a search location that was
manually added.
For example:
- Open the Settings app
- Select Search in the left hand sidebar
- Ensure Files is On
- Press the gear at the lower right of the dialog to open Search
Locations
- Select the Other tab
- Add a
Public bug reported:
On Ubuntu 18.04 using the `vanilla-gnome-desktop` session (i.e. Gnome
Shell), tracker does not return any files if there is a hyphen (-) in
the search string.
To recreate:
- Create a file named `foo-bar`.
- Press to open Overview.
- Type foo. Observe that the `foo-bar`
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: update-manager (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
** Description changed:
+ https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/8
+
+ ---
+
Steps:
1. Start Rhythmbox and play music
2. Press Print Screen in keyboard
3. Music stops and cannot be played again in Rhythmbox
4. If the music does not stop from the first time try
It appears that you do have Bluetooth hardware (Ralink corp. RT3290),
but it is turned off:
2: hp-bluetooth: Bluetooth
Soft blocked: yes
Hard blocked: no
Maybe it's staying off because the kernel driver isn't up to scratch yet
in 18.04, or missing firmware. To test this theory
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Maybe it works in that other system because 18.10 contains some bug fix
that is missing from your first system (that is 18.04).
I think more likely though it's just that your first system physically
isn't maintaining a clean USB connection. If that's a software problem
then this is a kernel bug
Public bug reported:
We need to package mutter 3.31 and add a Breaks: mutter < 3.31 to
gsettings-desktop-schemas.
Running gsettings-desktop-schemas 3.31 with mutter 3.30 will result in
gdm/gnome-shell being unable to start.
Also, ukwm is a fork of mutter so the Kylin devs need to backport the
Public bug reported:
I have qttols5-dev-tools installed, which provides a qthelpgenerator
implementation. But when I try to run qhelpgenerator (or
qcollectiongenerator) through their usual /usr/bin shims, it errors out:
janke@ubuntu:~/local/repos/octave-addons-chrono/doc$ dpkg -S
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Also affects: upower (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Public bug reported:
When I press the screen backlight up/down buttons, gnome-shell pops up
the backlight control window saying that the backlight is being
adjusted, but the actual screen brightness does not change.
The problem is that gnome is adjusting
Please remove all acpi* kernel parameters and see if it helps.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1812161
Title:
Screen backlight control does not work in
Rocko,
You seem to have some newer kernels installed. Does booting those have
the same problem?
Also, maybe you can try downgrading to cosmic's upower version:
https://launchpad.net/ubuntu/+source/upower/0.99.8-2ubuntu0.1
to see if it was a regression in upower.
** Changed in: linux (Ubuntu)
Ah, yes, Kai-Heng Feng probably makes a better point in comment #2.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1812161
Title:
Screen backlight control does not work in
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
I'm experiencing the same problem with Ubuntu 16.04.5 on OpenVZ (with
kernel: 2.6.32-042stab127.2).
The workaround that I found is to edit `/usr/lib/tmpfiles.d/sshd.conf`
in the following way:
d /run/sshd 0755 root root
Here is the question on askubuntu.com, where my case decribed in more
*** This bug is a duplicate of bug 1545811 ***
https://bugs.launchpad.net/bugs/1545811
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1545811, so is being marked as such.
This is definitely not an invalid bug report. It is not a support request nor
spam.
Steve wrote: "util-linux will be migratable to the disco release pocket".
This simply is not true.
This bug is for util-linux_2.33.1-0.1ubuntu1 and this package cannot be
installed (not migratable to release
On my system there are more missing or broken options (not only the
duplex problem) in the qt print dialog.
On my bionic system i found the following other problems:
- the printers are always on color mode, instead of gray-scale.
- the option to select the input tray is missing.
- the borders
1) I confirm that the gray-scale printing option is completely ignored
and that the printer prints always in color (this is definitively a
bug).
2) I confirm that an option to select the printer tray is missing
(though I think this may be a limitation in the qt version shipped with
bionic).
3) I
** Changed in: util-linux (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1811812
Title:
Util-linux_2.33.1-0.1ubuntu1 will not
92 matches
Mail list logo
