Yes! The artifacts reappear when I hit Shift-Alt-F12. Good catch!
--
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/1944951
Title:
delayed display update / konsole artifacts
"Fixed" by completely clearing ~/.config/ .
--
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/1944951
Title:
delayed display update / konsole artifacts
Status in xorg package
Update: This isn't a konsole-only issue. I'm seeing this in LibreOffice
Writer as well.
--
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/1944951
Title:
delayed display update
Additional notes:
- Nice reproducer: rsync --progress (the progress output is constantly littered
with artifacts)
- Artifacts vanish (temporarily) when I press e.g. the ALT key.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
I went back to konsole 20.04.0 (built from upstream sources) and still
see these artifacts. Consequently, something else in the xorg/KDE
software stack must be responsible; I'm not sure how to proceed with
debugging, though.
--
You received this bug notification because you are a member of
Public bug reported:
Since one of the recent Impish updates, konsole shows artifacts and
reacts slowly. In fact, it looks like screen updates are pipelined on
pixel-group granularity somehow, and the pipeline isn't drained
completely: When more text goes to the terminal (e.g., I type
something),
Public bug reported:
binutils-common 2.37-1ubuntu1 contains several zero-byte manpages (those
showing up with 20 bytes when packed with gzip):
$ dpkg-query -L binutils-common | grep /usr/share/man/man1/ | xargs ls -Sl
-rw-r--r-- 1 root root 6707 Jul 19 08:20 /usr/share/man/man1/ld.gold.1.gz
Regarding comment #6: Unfortunately the libva fix doesn't fix the obs-
studio issue for me. I reported a separate bug. -->
https://bugs.launchpad.net/ubuntu/+source/obs-studio/+bug/1873400
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Changed in: libva (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libva in Ubuntu.
https://bugs.launchpad.net/bugs/1872875
Title:
[Focal] Intel libva va_openDriver()
OBS Studio error message w/o the workaround, to help others find the
aforementioned temporary solution: "Starting the output failed. Please
check the log for details."
info: [FFMPEG VAAPI encoder: 'streaming_h264'] settings:
device: /dev/dri/renderD128
rate_control: CBR
This also affects OBS Studio (focal package obs-studio), which fails to
record using VAAPI hardware encoding due to this bug.
Workaround: Start obs with the LIBVA_DRIVER_NAME environment variable
set to the driver matching your Intel hardware, e.g. the following for
my Intel Skylake CPU.
Related (and fixed in Debian?): https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=956281
** Bug watch added: Debian Bug tracker #956281
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956281
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
The patch in comment #9 solves the issue for me.
--
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/1872551
Title:
software-properties-qt: nvidia driver version
aptdaemon has been installed from the start.
--
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/1872551
Title:
software-properties-qt: nvidia driver version
software-properties-gtk works as expected.
--
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/1872551
Title:
kubuntu-driver-manager: nvidia driver version switch
In my KDE bug report (https://bugs.kde.org/show_bug.cgi?id=419745) I
filed against systemsettings/kcm_networkmanagement; I'm actually not
sure whether network-manager was the right package to file against, are
you?
--
You received this bug notification because you are a member of Ubuntu
Touch
KDE bug report: https://bugs.kde.org/show_bug.cgi?id=419745
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1871710
Title:
WiFi hotspot with WPA/WPA2 Personal
Public bug reported:
When I create a shared WiFi ("hotspot") in the "Connections - System
Settings Module" with enabled WPA/WPA2 security, I cannot get Windows 10
clients to connect. Android 10 connects to this shared WiFi without
problems. Using the "Hotspot" button behind the system-tray
Public bug reported:
Running "ubuntu-bug xserver-xorg-video-intel" as a normal user pops up a
bogus dialog after a few seconds:
[i] text
[Yes] [No] [Cancel]
There seems to be a descriptive message missing in place of the "text"
placeholder.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Seems to have been fixed by a recent update; boots into SDDM now as
expected, using nvidia-drivers-390.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1752053
Title:
Additional side effect: Bionic sometimes fails to come back from S3 and
stays frozen with a black screen.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1752053
Title:
For me this is still broken with -proposed packages although this bug
has "Fix Released" status: When I have xserver-xorg-video-nvidia-390
390.48-0ubuntu1 installed, the system boots into a back screen.
Without, LightDM comes up as expected.
lspci excerpt (on a ThinkPad T460p):
00:02.0 VGA
** Also affects: fonts-hack (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fonts-dejavu in Ubuntu.
https://bugs.launchpad.net/bugs/299158
Title:
DejaVu, Liberation
Correction: "Hack Bold" renders correctly, "Hack Regular" doesn't.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fonts-dejavu in Ubuntu.
https://bugs.launchpad.net/bugs/299158
Title:
DejaVu, Liberation Mono, Noto Mono,
My test case: echo -e 'a\u0308a'
Correct rendering: äa
(That's what I see with: Courier, Cousine, DejaVu Sans Mono, FreeMono, Hack,
Monospace)
Incorrect rendering: aä
(That's what I see with: Andale Mono, Bitstream Vera Sans Mono, Courier 10
Pitch, Courier New, Liberation Mono, Mitra Mono,
This is still broken in Ubuntu 18.04 bionic. It's notoriously annoying
with text or filenames coming from OSX, which keeps diacritics separate
from the character they're combined with, also for characters that have
a distinct unicode code point for the combined variant.
** Also affects:
This is BTW almost exactly the same what 'hugepages' does --
*increasing* memlock limits to 262144 kB.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1662244
Title:
Please reopen. This just bit me on 17.10, using some manually
configured soft and hard memlock limits in /etc/security/limits.conf:
* softmemlock 262144
* hardmemlock 262144
As these limits *increase* max locked memory from 64 to 262144 kB, it
Note that on my machine (clean 16.10 install, upgraded to 17.04 and
later 17.10), DNS resolution already partially broke in 17.04 (involving
the switch to systemd-resolve). With Ubuntu 17.04, DNS resolution was
broken after suspending, moving to a different WiFi, and resuming the
machine. This
Public bug reported:
Since upgrading to 17.10, hostname resolution (via, e.g., Firefox or the
"host" command-line tool) does not work reliably anymore. Once hostname
resolution fails (Firefox 57: "Hmm. We're having trouble finding that
site."), manually resolving the host via "systemd-resolve"
Update: After reinstalling pulseaudio, alsa-base, pulseaudio-module-
bluetooth and plasma-pa (for KDE's volume control applet), the problem
reappeared. Commenting out "load-module module-switch-on-connect" in
/etc/pulse/default.pa (see comment #4) seems to fix the issue
permanently; the module
I'm seeing this as well on a machine with a clean 17.04 installation
that was upgraded to 17.10, using KDE (sound: Intel HDA). Steps in
comment #2 fixed this problem, at least temporarily.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
*** This bug is a duplicate of bug 1311173 ***
https://bugs.launchpad.net/bugs/1311173
** This bug has been marked a duplicate of bug 1311173
VoIP call flow analyses cause wireshark crashes
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
The newly added workaround (xfce4-mixer (or Xfce Audio Mixer in panel):
Choose Playback:...(PulseAudio Mixer) instead of (Alsa mixer) as sound
card in properties) fixes the symptoms for me.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Is the correct password mentioned in /etc/NetworkManager/system-
connections/eduroam (or whichever SSID is affected in your case) in a
password=MYPASSWORD line? In my case I didn't have such a line, and
replacing password-flags=1 with password=MYPASSWORD fixed automatic
connecting for me.
--
You
I have the same issue, but using Xfce4. Another workaround is to
manually edit /etc/NetworkManager/system-connections/eduroam (or
whichever SSID is affected in your case) and to replace password-
flags=1 with password=MYPASSWORD, this allows automatic connection
for me.
--
You received this bug
36 matches
Mail list logo
