Viestit paikassa Launchpad

I haven’t edited the corresponding AppArmor files

26. tammikuuta 2021 klo 18.41
Sijainti: Vianhallintajärjestelmät: Launchpad
Avainsanat: Apparmor

No, I haven’t (and wouldn’t know how).

Vastaa viestiin sen kontekstissa (Launchpad)

Yes, this is still present in 20.04

26. joulukuuta 2020 klo 16.56
Sijainti: Vianhallintajärjestelmät: Launchpad

Yes, this is still present in 20.04 with printer-driver-cups-pdf 3.0.1-6, limited to original reporter’s case of having the symlink point to another filesystem; if I point ~/PDF to, say ~/tmp/PDF (without crossing filesystem borders), the PDF is created without issue, whereas having ~/PDF linked to /media/$USER/$USB_THUMBDRIVE/PDF/ does still cause it to fail:

[…]
Sat Dec 26 16:48:07 2020 [DEBUG] output filename created: /home/jani/PDF/Bug__1092099__342_200_234inconsistent_behavior_for…ry_342_200_-job_8.pdf
Sat Dec 26 16:48:07 2020 [DEBUG] ghostscript commandline built: /usr/bin/gs -q -dCompatibilityLevel=1.2 -dNOPAUSE -dBATCH -dSAFER -sDEVICE=pdfwrite -sOutputFile=”/home/jani/PDF/Bug__1092099__342_200_234inconsistent_behavior_for…ry_342_200_-job_8.pdf” -dAutoRotatePages=/PageByPage -dAutoFilterColorImages=false -dColorImageFilter=/FlateEncode -dPDFSETTINGS=/prepress -c .setpdfwrite -f /var/spool/cups-pdf/SPOOL/cups2pdf-233705
Sat Dec 26 16:48:07 2020 [DEBUG] output file unlinked: /home/jani/PDF/Bug__1092099__342_200_234inconsistent_behavior_for…ry_342_200_-job_8.pdf
Sat Dec 26 16:48:07 2020 [DEBUG] TMPDIR set for GhostScript: /var/tmp
Sat Dec 26 16:48:07 2020 [DEBUG] waiting for child to exit
Sat Dec 26 16:48:07 2020 [DEBUG] entering child process
Sat Dec 26 16:48:07 2020 [DEBUG] GID set for current user
Sat Dec 26 16:48:07 2020 [DEBUG] supplementary groups set for current user
Sat Dec 26 16:48:07 2020 [DEBUG] UID set for current user: jani
Sat Dec 26 16:48:07 2020 [DEBUG] ghostscript has finished: 256
Sat Dec 26 16:48:07 2020 [ERROR] failed to set file mode for PDF file: /home/jani/PDF/Bug__1092099__342_200_234inconsistent_behavior_for…ry_342_200_-job_8.pdf (non fatal)
Sat Dec 26 16:48:07 2020 [DEBUG] ERRNO: 2 (No such file or directory)
Sat Dec 26 16:48:07 2020 [DEBUG] no postprocessing
Sat Dec 26 16:48:07 2020 [DEBUG] spoolfile unlinked: /var/spool/cups-pdf/SPOOL/cups2pdf-233705
Sat Dec 26 16:48:07 2020 [DEBUG] all memory has been freed
Sat Dec 26 16:48:07 2020 [STATUS] PDF creation successfully finished for jani
jani@latimeria:~$ ls -l PDF
lrwxrwxrwx 1 jani jani 27 joulu 26 16:47 PDF -> /media/jani/KINGSTON_1G/PDF
jani@latimeria:~$ ls -l PDF/
yhteensä 0

Vastaa viestiin sen kontekstissa (Launchpad)

Sorry, tried to link this with LP #1723881 but failed, because LP #1334

27. marraskuuta 2020 klo 18.33
Sijainti: Vianhallintajärjestelmät: Launchpad
Avainsanat: Launchpad

Sorry, tried to link this with LP #1723881 but failed, because LP #1334

Vastaa viestiin sen kontekstissa (Launchpad)

Currently experiencing this

15. elokuuta 2020 klo 18.32
Sijainti: Vianhallintajärjestelmät: Launchpad
Avainsanat: Ubuntu

Currently experiencing this. `lsof /var/lib/dpkg/lock` shows only ”focal” as holding the lock. The same ”focal” process is also eating up all of the CPU. No dpkg or apt processes are listed by `ps` either.

Vastaa viestiin sen kontekstissa (Launchpad)

Hardware-accelerated video decoding (VA-API) broken in Firefox 79 (Wayland)

31. heinäkuuta 2020 klo 17.12
Sijainti: Vianhallintajärjestelmät: Launchpad
Avainsanat: Firefox, Twitch, Wayland, YouTube

After updating Firefox from 78 to 79, hardware-accelerated video decoding no longer works properly in Wayland: streaming video gets cut off with an error message from the service.

== Steps to reproduce ==
1. Follow the steps in [1] to enable VA-API.
2. Open a Youtube/Twitch video (for instance https://www.twitch.tv/rifftrax), press play

== What I expect to happen ==
For the video be played without issues (as it did with Firefox 78).

== What happens ==
After playing for a while (anything from just a few seconds to a couple of minutes), the video stops and is replaced by a service-specific error message, such as error #3000 (in case of Twitch) or (Youtube). Even when playing, the video also flickers green. After reloading the tab, the video again plays for a few seconds before the error message reappears.

== Other info ==
A fix is apparently already in the works upstream [2].

* [1] https://mastransky.wordpress.com/2020/06/03/firefox-on-fedora-finally-gets-va-api-on-wayland/
* [2] https://bugzilla.mozilla.org/show_bug.cgi?id=1645671

Vastaa viestiin sen kontekstissa (Launchpad)

3.36.4-1ubuntu1~20.04.1 from -proposed fixed the issue

28. heinäkuuta 2020 klo 16.42
Sijainti: Vianhallintajärjestelmät: Launchpad
Avainsanat: Gnome

I can confirm that 3.36.4-1ubuntu1~20.04.1 from -proposed fixed the issue (in Boxes) for me, i.e. the dialog text is now wrapped and hence entirely legible.

Vastaa viestiin sen kontekstissa (Launchpad)

A fix has recently been committed upstream

4. heinäkuuta 2020 klo 18.22
Sijainti: Vianhallintajärjestelmät: Launchpad
Avainsanat: Debian, Ubuntu

A fix has recently been committed upstream: https://salsa.debian.org/debian/ddclient/-/commit/82d99d1dfb0fb002a15e081fdc7ccf8f96215dc6

Vastaa viestiin sen kontekstissa (Launchpad)

I did some manual dconf settings cleanup, and could no longer reproduce the issue

15. toukokuuta 2020 klo 13.10
Sijainti: Vianhallintajärjestelmät: Launchpad

After doing manual dconf cleanup, I’ve been unable to reproduce the issue. That’s since posting the previous comment, so a few days now. So I think I’ll hold off on reporting this upstream for the time being, but I’ll go ahead and do that if the problem still manifests itself.

Thanks again, Daniel.

Vastaa viestiin sen kontekstissa (Launchpad)

I removed all but the Ubuntu extensions, rebooted and then reproduced the issue

12. toukokuuta 2020 klo 16.27
Sijainti: Vianhallintajärjestelmät: Launchpad
Avainsanat: Gnome, Synaptic, Ubuntu

I removed all but Desktop Icons, Ubuntu AppIndicators and Ubuntu Dock, rebooted and then reproduced the issue. Luckily I’ve found one way to reproduce this, albeit somewhat convoluted and still a bit unreliable, involving Synaptic and window tiling. And as it doesn’t seem to trigger the issue when using another account, I’m now working through settings differences between the two in hopes of finding something crucial.

While doing so, I did discover that dconf-editor is similarly affected:

    touko 12 16:09:32 saegusa gnome-shell[8208]: WL: compositor bug: The compositor tried to use an object from one client in a 'wl_pointer.enter' for a different client.
    touko 12 16:09:32 saegusa gnome-shell[8208]: WL: error in client communication (pid 12364)
    touko 12 16:09:32 saegusa dconf-editor[12364]: Error reading events from display: Katkennut putki
    touko 12 16:09:32 saegusa boinc[2098]: No protocol specified
    touko 12 16:09:32 saegusa boinc[2098]: No protocol specified
    touko 12 16:09:33 saegusa boinc[2098]: No protocol specified
    touko 12 16:09:33 saegusa boinc[2098]: No protocol specified
    touko 12 16:09:34 saegusa gnome-shell[8208]: WL: compositor bug: The compositor tried to use an object from one client in a 'wl_pointer.enter' for a different client.
    touko 12 16:09:34 saegusa boinc[2098]: No protocol specified
    touko 12 16:09:34 saegusa boinc[2098]: No protocol specified
    touko 12 16:09:34 saegusa gnome-shell[8208]: WL: error in client communication (pid 12796)
    touko 12 16:09:34 saegusa gnome-terminal-[12796]: Error reading events from display: Katkennut putki
    touko 12 16:09:34 saegusa systemd[3569]: gnome-terminal-server.service: Main process exited, code=exited, status=1/FAILURE
    touko 12 16:09:34 saegusa systemd[3569]: gnome-terminal-server.service: Failed with result 'exit-code'.
    touko 12 16:09:34 saegusa systemd[3569]: vte-spawn-da1941e8-60e5-48e5-868b-7348dd1158c7.scope: Succeeded.
    touko 12 16:09:34 saegusa gnome-shell[8208]: Error adding children to desktop: this.layout.get_child_at(...) is null
    touko 12 16:09:34 saegusa gnome-shell[8208]: Error adding children to desktop: this.layout.get_child_at(...) is null
    touko 12 16:09:34 saegusa gnome-shell[8208]: Error adding children to desktop: this.layout.get_child_at(...) is null
    touko 12 16:09:34 saegusa gnome-shell[8208]: Error adding children to desktop: this.layout.get_child_at(...) is null

Looks like dconf-editor did not exit with FAILURE, but the dconf-editor window did disappear just as Gnome terminal’s did.

Vastaa viestiin sen kontekstissa (Launchpad)

Happened again: The compositor tried to use an object from one client in a ’wl_pointer.enter’ for a different client

11. toukokuuta 2020 klo 18.05
Sijainti: Vianhallintajärjestelmät: Launchpad

Happened again:

May 11 17:05:50 saegusa gnome-shell[3619]: WL: compositor bug: The compositor tried to use an object from one client in a ’wl_pointer.enter’ for a different client.
May 11 17:05:50 saegusa gnome-shell[3619]: WL: error in client communication (pid 5170)
May 11 17:05:50 saegusa gnome-terminal-[5170]: Error reading events from display: Katkennut putki
May 11 17:05:50 saegusa systemd[3544]: gnome-terminal-server.service: Main process exited, code=exited, status=1/FAILURE
May 11 17:05:50 saegusa systemd[3544]: gnome-terminal-server.service: Failed with result ’exit-code’.
May 11 17:05:50 saegusa systemd[3544]: vte-spawn-b269c64d-5376-49ec-83fc-9f4806ac4b30.scope: Succeeded.
May 11 17:05:50 saegusa systemd[3544]: vte-spawn-3294a176-7b32-4995-a11b-fe0fea8b07bc.scope: Succeeded.
May 11 17:05:50 saegusa systemd[3544]: vte-spawn-0b59afd0-1aed-4081-a7d1-801e7c405399.scope: Succeeded.
May 11 17:05:51 saegusa systemd[3544]: Started Application launched by gnome-shell.

But there’s still nothing in /var/crash, nor on the Error Tracker (aside from the aforementioned, unrelated crash from last week).

Vastaa viestiin sen kontekstissa (Launchpad)

Vanhempia »