You say "with no video driver PPAs". As an experiment, you could try, as
I did, with NO PPAs (e.g. by doing a clean reinstall from ISO). Perhaps
it's due to a PPA that is not obviously related. Also, could the fact
that you are on 20.04.3 be a problem? If so, but you require the LTS,
you could use
ppa-purge failed (didn't want to replace running kernel and it couldn't find
aptitude), leaving the system unstable. Did a clean reinstall of 21.04 from ISO
to get a usable system (obviously without PPAs), restored home dir from nightly
backup. Back in business ...
mpv can now do mp4 files
I tried running vainfo on my laptop (also running 21.04) and got the
same error.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944088
Title:
mpv aborts on mp4 files
To manage notifications about
vainfo produced no standard output, but gave (in standard error) a very
similar error message to the one I reported when attempting mpv on an
mp4 file:
wl_drm@7: error 0: authenticate failed
VA error: wayland: Wayland roundtrip error: Protocol error (errno 71)
libva info: VA-API version 1.10.0
Public bug reported:
Since upgrading to 21.04 with wayland, mpv has been issuing warnings
(suggesting X session) but performing without any problem, including
with mp4 files. Until recently. Now the result is:
wl_drm@22: error 0: authenticate failed
VA error: wayland: Wayland roundtrip error:
I am seeing the same problem in 13.10 on 2 different systems, one 32-bit
and one 64-bit.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1176509
Title:
After update to 13.04 Brasero CD write hangs at
I wonder if all those encountering this bug have ext3 or older. My
desktop system with the bug has ext3 and my (newer) laptop which does
not is using ext4. Does ext4 have ACLs enabled by default?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Molly, You do understand that the directory to be created under /media should
be named molly in your case (i.e., sudo mkdir /media/molly), right? Not
USERNAME literally.
Also, I noticed on my laptop, which does not have this bug, the directory
(/media/david in my case) did not exist initially,
I just tried the workaround suggested by Sebastian Heutling (on
2012-10-06) and others, of creating a directory whose name is my
username in /media, and this worked for me too. Now mounts of removable
media show up under that subdirectory instead of directly under /media.
Is this the new normal
I am having this same problem with a USB drive (vfat) which I have been
using for some time as a backup disk. No problem until Ubuntu 12.10.
Temporarily mounting it via /etc/fstab until a fix is found for this
bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I think that has fixed it (installed 3 packages). It now seems to be
tracking the actual on/off state of the printer. 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/936155
Title:
Epson
Public bug reported:
This problem first appeared in oneiric (the printer was detected in many Ubuntu
releases before). A proposed kernel was suggested under bug 872711, #
3.0.0-13, which fixed the problem. However, I then took further kernel updates
and detection of my printer is broken again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/936155
Title:
Epson Stylus Photo R300 not detected even with 3.0.0-16
To manage notifications about this bug go to:
I have submitted bug 936155.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/872711
Title:
Kernel does not report some USB printers correctly, making them not
being detected by CUPS
To manage
$ sudo /usr/lib/cups/backend/usb
DEBUG: list_devices
DEBUG: usb_find_busses=5
DEBUG: usb_find_devices=7
direct usb://EPSON/Stylus%20Photo%20R300?serial=L15P10501281054100interface=1
EPSON Stylus Photo R300 EPSON Stylus Photo R300
MFG:EPSON;CMD:ESCPL2,BDC,D4;MDL:Stylus Photo
Make sure your print queue is enabled:
cupsenable EPSON-Stylus-Photo-R300
That was it. Before giving that command, Properties in the Printers GUI (for
EPSON-Stylus-Photo-R300) hand shown a Printer State: of off or unplugged,
just like when I had first upgraded to oneiric and before taking the
I turned off the printer, but even with it off, the Properties still
show idle. Sounds like there may be a problem in both directions. I
close the dialog, go back to the gear - Printers, select my printer,
and then choose Properties from the context menu. Tried many times, but
it keeps saying Idle
I installed cups 1.5.2-4~ppa1 and cups-filters 1.0.1-1~ppa1 (plus 4
additional packages that came along with them). However, I still see
Printer State: Idle, even with the printer off.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
lpinfo -l -v lists my printer if and only if it is turned on. But the
Printer State: in Properties continues to say Idle whether it is on or
off. If I physically disconnect the USB cable, the Printer State:
setting under Properties STILL says Idle.
--
You received this bug notification because
I currently have kernel 3.0.0-16 (32 bit) and my printer (Epson Stylus
Photo R300) is not being detected. Note from some of my previous
comments in this bug, e.g. 2011-10-22, that there have been some earlier
kernel versions, originally a proposed 3.0.0-13 for which my printer
was detected. So I'm
Just installed kernel 3.0.0-15 and my printer is once again being
detected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/872711
Title:
Kernel does not report some USB printers correctly, making
This just stopped working for me. I seem to be back where I started
(claims my printer is unplugged or turned off). I thought the problem
might be that I had upgraded to kernel 3.0.0.14 so I tried booting up
with 3.0.0.13, but it still doesn't work. This is an Epson Stylus Photo
R300. Everything
I looked back to my previous comment here and it was on 2011-10-22 that
I reported my success with 3.0.0-13. However, the kernel files in /boot
now for 3.0.0-13 are dated 2011-11-02! Does this mean I clobbered the
good kernel by updating to a later 3.0.0-13 that lacks the fix? Are
kernel updates
You might want to check the apparmor comment in:
https://wiki.ubuntu.com/DebuggingPrintingProblems
and possibly try: sudo aa-complain cupsd, as suggested there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I don't know whether it is the proposed kernel but 3.0.0-13 has fixed
the problem for me. My Epson Stylus Photo R300 is now detected. This a
32-bit oneiric system.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
The printer was handled without problem in many previous Ubuntu releases.
I don't really believe the fault is in CUPS, but it shows up as CUPS not being
able to find the printer.
I did various tests recommended in
https://wiki.ubuntu.com/DebuggingPrintingProblems:
#2:
$
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/876992
Title:
Epson Stylus Photo R300 not detected in 11.10
To manage notifications about this bug go to:
27 matches
Mail list logo
