It appears we do not yet have a full log from this machine. Next time
the problem happens, please run:
journalctl -b0 > journal.txt
and then attach the resulting text file here.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You
Please try these, in any order:
1. Replacing the batteries in your wireless mouse.
2. A wired mouse.
3. sudo apt remove xserver-xorg-input-synaptics
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
** Changed in: xorg-server (Ubuntu)
Status: New => Incomplete
** Package
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell
When the problem is happening please run these commands:
journalctl -b0 > journal.txt
xinput list-props N > props.txt
where N is the ID of your touchpad according to 'libinput'.
Please then attach the two resulting text files to this bug.
** Changed in: libinput (Ubuntu)
Status:
If the same fundamental issue persists in Wayland sessions then it
sounds like a hardware limitation or a kernel problem. To help identify
which, the Mutter developers might have some suggestions so please
report the issue here:
https://gitlab.gnome.org/GNOME/mutter/issues
** Changed in:
Note there are two related upstream bugs:
https://gitlab.gnome.org/GNOME/mutter/-/issues/1108
https://gitlab.gnome.org/GNOME/mutter/-/issues/1165
But those are only on resume from suspend and not related to fractional
scaling.
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1108
Public bug reported:
This isn't new, this idiocy has annoyed me ever since I've been using
Ubuntu; however, after upgrading to 20.04 I'm disappointed to see that
it still hasn't been fixed.
I use a laptop and I have an external monitor that I keep connected most
of the time.
So, I have it set
Public bug reported:
Package `libweston-8-dev`: file `libweston-8-protocols.pc` is missing a
declaration of variable `includedir`, which makes pkg-config to fail
when looking for this package. This can be fixed by adding at line 2 the
following:
```
includedir=${prefix}/include
```
ProblemType:
Public bug reported:
Sometimes programs open a "popup" or a "secondary", "child" window, I
don't know what the word is.
For example, in Chrome, if I right-click on an image in a web page and
choose "Save As", this will open a new file browser window that allows
me to browse for a directory to
Public bug reported:
The display is completely frozen, and no signal is output to the
monitors. There is also no signal when switching to a console (Ctr-
Alt-F1). I have normal access via SSH.
It happens about once in 14 days. Only happens when turning the display
off or on (about once in 15
Public bug reported:
On Ubuntu 16.04 I was used to the keyboard shortcut ctrl+Super+D to
reveal the Desktop by minimizing all windows (it was not exactly the
same as minimizing all windows but whatever).
That shortcut was changed at almost every major release, which was
already irritating
The attachment "vt_handoff.patch" seems to be a patch. If it isn't,
please remove the "patch" flag from the attachment, remove the "patch"
tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the
team.
[This is an automated message performed by a Launchpad user owned by
** Package changed: ubuntu => xorg (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1887271
Title:
Square rectangles instead of system fonts after upgrade
To manage notifications about
You have been subscribed to a public bug:
After upgrading my room mate's Fujitsu Esprimo Desktop PC to 20.04
Focal Fossa (from Bionic 18.04):
Any system font line is being displayed distorted / erroneous / in sort
of placeholder blocks or SQUARE RECTANGLES, as if the fonts set wouldn't
be
Hi Guys,
Help me to test this, this works for me,
please find this line "set vt_handoff=vt.handoff=7" in /boot/grub/grub.cfg,
and change it to "set vt_handoff=vt.handoff=1", then reboot let's see how it
goes, thanks.
--
You received this bug notification because you are a member of Ubuntu-X,
if the result in #101 is positive for everyone,
then I think it's because of this missed patch since from cosmic
** Patch added: "vt_handoff.patch"
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1845801/+attachment/5391915/+files/vt_handoff.patch
--
You received this bug
Hi Guys,
Help me to test this, this works for me,
please find this line "set vt_handoff=vt.handoff=7" in /boot/grub/grub.cfg,
and change it to "set vt_handoff=vt.handoff=1", then reboot let's see how it
go, thanks.
--
You received this bug notification because you are a member of Ubuntu-X,
@Bob Lawrence (pilotbob42)
So i'm back with a better workaround.
First I enabled the intel driver like I specified in my first point.(this
removes the tearing)
Then I used your workaround, but this was causing the other inputs to error at
startup so I on some forum that adding a command at
New problems in an old thread
After using @Matthias Fulz's method (bumblebee without bbswitch + pm
with powertop+tlp) its quite simple to run any software requiring
nvidia. with his patch.
The problem is in preventing any other software from using nvidia when
not run with optirun/primusrun. For
** Changed in: ubuntu-mate
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libxcb in Ubuntu.
https://bugs.launchpad.net/bugs/1878434
Title:
xshape - not able to select area on screen
To manage notifications
** Tags added: focal
** Also affects: libdrm (Ubuntu)
Importance: Undecided
Status: New
** Also affects: xserver-xorg-video-amdgpu (Ubuntu)
Importance: Undecided
Status: New
** Also affects: mate-control-center (Ubuntu)
Importance: Undecided
Status: New
--
You
Did a tryout with an older driver of nvidia, ie 435.21, same result!
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.launchpad.net/bugs/1868519
Title:
[nvidia] Xorg crashed with SIGSEGV in
> Note: Please watch your language. They're serious about that here
I know, I wish they were half as serious about handling bugs.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1887247
Title:
Here are the logs, caused from the try to open a grafic in gimp
** Attachment added: "Xorg log from the crash"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1868519/+attachment/5391906/+files/Xorg.1.log.old
--
You received this bug notification because you are a
** Attachment added: "syslog from the crash"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1868519/+attachment/5391907/+files/syslog
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
In case someone is looking into this one: This is still an issue.
Dell Precision 5520
Intel® Core™ i7-7820HQ CPU @ 2.90GHz × 8
Quadro M1200/PCIe/SSE2 / Quadro M1200/PCIe/SSE2
Ubuntu 20.04 LTS
NVIDIA Driver Version: 440.100
I have so far seen that happening on two of my machines, when using gimp
26 matches
Mail list logo
