** Attachment added: "19.04_error_log"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1853879/+attachment/5309097/+files/19.04_error_log
** Changed in: cups (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Attachment added: "19.10_Brother_MFC_L2720DW_series.ppd"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1853879/+attachment/5309094/+files/19.10_Brother_MFC_L2720DW_series.ppd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Here are ppd files and error logs for Ubuntu 19.04 (where it works) and
Ubuntu 19.10 (where it doesn't work). Also, attrs.txt. As I didn't have
any 19.04 installation, and had changed the printer configuration
manually in 19.10, I run two live media, 19.04 and 19.10, and tested and
generated the
** Attachment added: "19.04_Brother_MFC_L2720DW_series.ppd"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1853879/+attachment/5309096/+files/19.04_Brother_MFC_L2720DW_series.ppd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: "19.10_error_log"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1853879/+attachment/5309095/+files/19.10_error_log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853879
I can confirm this bug on a different printer; Brother MFC-L2720DW. It
runs over the network, and without any drivers or any special setup. No
matter if I choose long or short edge, it will print as if I selected
short edge. This worked in 19.04, so it seems the issue has been
introduced in 19.10.
I'm running 18.04 right now and don't have the issue, so I guess it has
been resolved. Are you running 17.10 @thuerrschmidt?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1725955
Title:
"Printer
Two more solutions:
* Make the background the same but keep a line between:
https://i.imgur.com/ilhA6Zr.png
* Make the background the same and remove the line:
https://i.imgur.com/qS0ODeq.png
(I based the images of Marco Trevisan's, hope that's OK :-) )
--
You received this bug notification
*** This bug is a duplicate of bug 1748450 ***
https://bugs.launchpad.net/bugs/1748450
I suppose bug #1748450 is private, as I can't access it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The issue is fixed in gparted version 0.30, but not in the latest ubuntu
package which is of version 0.28 in artful. Also, according to
https://bugzilla.gnome.org/show_bug.cgi?id=776437, the package must be
compiled with --enable-xhost-root. It would be great if the maintainer
(Curtis Gedak) could
Now the bug is reported in GNOME's bug reporter:
https://bugzilla.gnome.org/show_bug.cgi?id=789490
** Bug watch added: GNOME Bug Tracker #789490
https://bugzilla.gnome.org/show_bug.cgi?id=789490
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Nothing shows up about it in the syslog except this, which seems to show
up each time the notification comes:
colord[1227]: failed to get session [pid 2331]: No data available
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
- I've recently installed Ubuntu 17.10 (Gnome shell). After a while a saw
+ I've recently installed Ubuntu 17.10 (Gnome shell). After a while I saw
an OSD notification with the message "printer added", and thought that
must be because of the new driverless printers
Public bug reported:
I've recently installed Ubuntu 17.10 (Gnome shell). After a while a saw
an OSD notification with the message "printer added", and thought that
must be because of the new driverless printers feature in the kernel. I
have a brother printer in the network, and I tested it and it
Public bug reported:
When in the wayland session, it takes around 30 seconds from when I
press Ctrl+Alt+T to when the terminal (gnome-terminal) actually opens.
If I press multiple times sequentially, it will take 30 seconds between
each launch. When I launch via activities or any other way, it
I have tested this on another machine with Ubuntu 16.04 now, and I can
reproduce it with these steps there as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1578792
Title:
nautilus/files
A more exact way to reproduce: ("Files" will be referred to as nautilus)
-- Start by having nautilus pinned and closed --
* Open nautilus
* Unpin it (it will still display, as excepted)
* Close nautilus (now it won't display, as excepted)
* Open nautilus via the dash
* Now it will display for
yes
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1578792
Title:
nautilus/files doesn't show up in the launcher when unpinned
To manage notifications about this bug go to:
Public bug reported:
When nautilus is unpinned, it doesn't show up in the launcher. When it's
pinned, you can see the open windows with arrows on the side as usual,
and switch between windows if there are several of them. But when I
unpin it, it will disappear entirely. Sometimes when I open it,
This bug i still present in 15.10 and it's very annoying. Will it be
fixed there?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1511154
Title:
xdg-settings set fails with status 2 because of a
This seems to be fixed here: https://bugs.launchpad.net/ubuntu/+source
/xdg-utils/+bug/1511154. But only for Xenial. Can it be patched to wily
and other affected versions of Ubuntu?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have the exact same problem in Xenial, latest daily.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1536738
Title:
ubiquity crashes on boot: ValueError: invalid literal for int() with
base 10:
Confirmed on Ubuntu 15.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1438935
Title:
? just got the something wrong procedure
To manage notifications about this bug go to:
Bug confirmed on 15.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/349469
Title:
debconf: DbDriver config: /var/cache/debconf/config.dat is locked by
another process: Resource temporarily
I get the same error.
** Changed in: init-system-helpers (Ubuntu)
Status: Invalid = New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to init-system-helpers in Ubuntu.
https://bugs.launchpad.net/bugs/1439988
Title:
package
I get the same error.
** Changed in: init-system-helpers (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/1439988
Title:
package init-system-helpers 1.22ubuntu4
Hello!
I have tried out the proposed package, and it solves the bug! Thank you
Brian!
** Tags removed: verification-needed
** Tags added: verification-done
--
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 1396232 ***
https://bugs.launchpad.net/bugs/1396232
** This bug has been marked a duplicate of bug 1396232
Desktop freezes when Do starts if quiet mode is not enabled
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
The thing is that it wasn't ME that tried to install grub to /dev/sdb2,
it was ubuntu. I haven't done anything. That's the bug, Ubuntu suggested
something that is not possible.
** Changed in: grub-installer (Ubuntu)
Status: Invalid = New
** Changed in: grub-installer (Ubuntu)
Public bug reported:
When i tried to install ubuntu, a message came up that said that it was
unable to install the bootloader.
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: ubiquity 2.20.0
ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
Uname: Linux 3.16.0-23-generic x86_64
Public bug reported:
Directly when i start gnome do, it immediately crashes, and Ubuntu
freezes. Then I must press Ctrl + Alt + F1 and type killall gnome-do so
I can continue use the computer.
I will also add a picture of how it looks like when it crashes, cause
it's very interesting. As I
31 matches
Mail list logo
