Thanks for taking the time to report this bug and helping to make Ubuntu
better. Your bug report is more likely to get attention if it is made in
English, since this is the language understood by the majority of Ubuntu
developers. Additionally, please only mark a bug as "security" if it
shows
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
Public bug reported:
when the screen of my laptop goes blank, it will log me out. this
happens when I lock my laptop or put it to sleep. This only happens on
wayland.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
Public bug reported:
Hello there,
I have Ubuntu 23.04 installed on a Dell XPS 13 9300 with an LG 32" 4K
Ergo Monitor attached as an external display. When I set the "primary
display" at 1080p@60Hz for the LG 32" only with the "secondary display"
of the Dell XPS 13" disabled" and "suspend power"
** Description changed:
I am running a fresh install of ubuntu 22.04 with kde-plasma-desktop.
every 1-2 minutes, there will be a random blue/pink frame(i'm not sure
of the color because it only appears for a short time). I don't get this
problem in fullscreen games running with dxvk and
Public bug reported:
I am running a fresh install of ubuntu 22.04 with kde-plasma-desktop.
every 1-2 minutes, there will be a random blue/pink frame(i'm not sure
of the color because it only appears for a short time). I don't get this
problem in fullscreen games running with dxvk and the random
Public bug reported:
when I watch a video in fullscreen, my laptop can draw as many as 25w.
For comparaison, on windows 11, a similar video will take only 8w from
the battery. obviously, the cpu temps and fan speed are much higher on
ubuntu tan on windows. Also, this might be unrelated, but when
PPS: I have Ubuntu 22.04 (the same version) on my Acer Aspire 3 A315-21G-63YM
[very old notebook of about 5-6 years old]; I tried several times to connect
this notebook to the same monitor with the same scheme - it works perfectly (I
did not try screenshots, because the picture there is
pe you will be able to fix this bug :)
Best wishes,
Alex,
Prague, Czech Republic, EU
PS: When typing this message I found another bug compared to MS Windows.
When making screenshots (Alt/Shift + Print Screen) - it makes perfect picture
even when you actually have the second monitor white all the ti
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
Thank you for using Ubuntu and taking the time to report a bug. Your
report should contain, at a minimum, the following information so we can
better find the source of the bug and work to resolve it.
Submitting the bug about the proper source package is essential. For
help see
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately we can't fix it, because your description
didn't include enough information. You may find it helpful to read 'How
to report bugs effectively'
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html.
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
** Changed in: amd
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1947820
Title:
[SRU] Backport xorg-server 1.20.13 to focal
To manage notifications
** Changed in: amd
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1952083
Title:
Add support for Beige Goby
To manage notifications about this bug go to:
** Tags added: oem-priority originate-from-1947372 somerville
** Tags added: originate-from-1948411
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1952083
Title:
Add support for Beige Goby
To
** Also affects: oem-priority
Importance: Undecided
Status: New
** Changed in: oem-priority
Importance: Undecided => Critical
** Changed in: oem-priority
Assignee: (unassigned) => Yuan-Chen Cheng (ycheng-twn)
--
You received this bug notification because you are a member of
The reverts are in the latest firmware tree:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/amdgpu?id=d7b50e61669dc137924337d03d09b8986eb752a3
Does the latest firmware in the firmware git tree help?
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/log/amdgpu
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
** Changed in: oem-priority
Assignee: Andy Chi (andch) => jeremyszu (os369510)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1918855
Title:
Xorg xserver got signal 6 to abort
To manage
I have my minipc server Gigabite Brix 4105 and the monitor is not connected to
it. Installed Ubuntu Desktop 12.04.2.
I control it from my PC using VNC and no visual artifacts.
This is done through 20-intel.conf
Section "Device"
Identifier "intelgpu0"
Driver "intel"
Option
# suggestion:
On nvidia settings UI, there's no message saying it's building initrd after
user select on-demand mode. So, the nvidia settings looks like just hangs up
when it's building initrd.
If user have multiple kernel before selecting on-demand, user might be
confused and treat it as
# verified pass on focal:
## package version as expected.
ubuntu@dell-bto-focal-fossa-nvstaging-202005-27873:~$ apt list
ubuntu-drivers-common nvidia-prime
Listing... Done
nvidia-prime/focal-proposed,focal-proposed,now 0.8.16~0.20.04.1 all
[installed,automatic]
have update to 5.8.18-050818-generic, used the i2c-hid_standalone module.
this seems to work ok, will let you know if still issues with behaviour.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-libinput in Ubuntu.
i'm on focal with 5.4.0-66-generic, it seems touch is in kernel now, but not
work very good.
have installed the gnome-tweaks and enabled mouse emulation "finger".
sometimes two clicks for right mouse action work, sometimes not.
very few times the 3 finger middle mouse action work, even.
haven't
** Also affects: nvidia-drivers-ubuntu
Importance: Undecided
Status: New
** Also affects: oem-priority
Importance: Undecided
Status: New
** Changed in: oem-priority
Assignee: (unassigned) => Alex Tu (alextu)
** Changed in: oem-priority
Importance: Undeci
Thank you for using Ubuntu and taking the time to report a bug. Your
report should contain, at a minimum, the following information so we can
better find the source of the bug and work to resolve it.
Submitting the bug about the proper source package is essential. For
help see
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
thanks @Mike Boruta (maridius)!
wondered why it worked after re-install of nvidia driver, so thats the
explanation now ;)
what about any issues with the touchpad?
not sure if something else produces my issues, but during longer usage there
random stutterings, the mouse is not moved for some
... but:
have to modprobe -r and modprobe i2c_hid again, to get the touchpad working.
any ideas?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1887190
Title:
MSFT
have managed to compile the i2c_hid.ko module in ubuntu 20.04, too,
works! thanks!
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1887190
Title:
MSFT Touchpad not working
** Changed in: oem-priority
Importance: High => Critical
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1890772
Title:
No signal on 4K 60Hz DisplayPort monitor by default, until "max
** Also affects: hwe-next
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1890772
Title:
No signal on 4K 60Hz DisplayPort monitor by default,
reply to #39,
yes it's a trade off that we don't either want user get darkscreen when
then randomly plug display port for case like #38 or user get lower bpc on
their working display port.
So far, there seems no solid way to make sure both requirement.
--
You received this bug
according to #40 and conversation on mattermost with Kai-Heng.
HWE is planning to add quirk for the faulty dongles so that the dark screen
during boot time[1] can be fixed.
[1] https://gitlab.freedesktop.org/drm/intel/-/issues/1890
--
You received this bug notification because you are a
I afraid we can not just trust (EDID_version >= 1.4 &&
EDID_supports_10bit). Because this issue caused by any problematic
component in the middle of pipeline. To ensure the compatibility, better
to just defautly set bpc=8.
Think of one scenario, a speaker get his Ubuntu machine onto stage, plug
** Bug watch added: gitlab.freedesktop.org/xorg/xserver/-/issues #1066
https://gitlab.freedesktop.org/xorg/xserver/-/issues/1066
** Also affects: xorg-server via
https://gitlab.freedesktop.org/xorg/xserver/-/issues/1066
Importance: Unknown
Status: Unknown
--
You received this
** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #1108
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1108
** Also affects: xorg-server via
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1108
Importance: Unknown
Status: Unknown
Thanks for understanding.
There's an upstream bug discussing this similar issue, we can follow their
effort there.
https://gitlab.freedesktop.org/drm/intel/-/issues/1890
** Bug watch added: gitlab.freedesktop.org/drm/intel/-/issues #1890
https://gitlab.freedesktop.org/drm/intel/-/issues/1890
I think different from #32.
To adding a GUI configure bpc is a long-term plan.
Before that,the default behavior should be designed to get the best user
experience.
As we all know, there're lot of hardware components on the pipline of display
path(e.g. socket, converter, dongle, cable, monitor)
** Tags added: originate-from-1887915
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1890772
Title:
No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc"
is lowered to 8
** Tags added: oem-priority originate-from-1886778 somerville
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1890772
Title:
No signal on 4K 60Hz DisplayPort monitor by default, until
I think i got it right this time.
I managed to apply the proposed libx11 patch, installed the right libx11 deb
and it worked so far.
If anyone willing to test the fix i pushed it to
https://github.com/avafinger/libx11_1.6.4
Mind that if ubuntu team release a new version of the libx11 you might
I applied the patch attached (libX11) but the crash still occurs with less
frequency.
Maybe i missed some additional patch required to fix this.
For the record:
I am running LUbuntu in this PC box (upgraded from 16.04 to 18.04) and i
have another one with Ubuntu 18.04 + LXDE installed from
Ouch, I missed this commit:
https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/34/diffs?commit_id=8b45f9589b3eb1ff46d16c774b017794e553db8e
I Will try again.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libx11 in Ubuntu.
I would like to add some info that may help to narrow the problem.
I have had this crash in PCManFM since i upgraded ubuntu from 16.04 to 18.04
but the same bug manifest in Geany and Chromium as well. The bug could hit
PCManFM within a few clicks opening directories and then clicking on a file
Public bug reported:
Freezes randomly without any traceable pattern. Windows become unresponsive
while the cursor works.
To unfreeze I have to press the OFF button of my HP ProBook and then click on
"Cancel" in the shutdown dialogue. That unfreezes the windows. May happen
several times per
for me the two workaround doesn't work
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1845801
Title:
[nvidia] Automatic login fails and then all subsequent logins fail.
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
Public bug reported:
When in both Firefox and Opera hardware acceleration is on and browser
is running it will trigger freeze with X.OrgX driver on.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux
** Attachment added: "2020-04-15_01-41.png"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1872788/+attachment/5354040/+files/2020-04-15_01-41.png
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
Public bug reported:
compare to bionic, bionic will show complete icon when I press super key
and type prefix of application.
But in Focal, the icon is incomplete as attache screenshot.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu
I had the same issue and I had to reinstall 19.04, but anyway I want to
use the latest Ubuntu, so I afraid to install it again.
Question: How can I check compatibility before updating?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
btw, as record. After reboot of this issue. I also updated BIOS by fwupd
to make sure every thing is updated to date for following debugging.
$ fwupdmgr get-updates
No upgrades for XPS 13 9380 System Firmware, current is 0.1.7.0: 0.1.7.0=same,
0.1.6.0=older, 0.1.5.0=older, 0.1.4.0=older,
** Attachment added: "snap.list"
https://bugs.launchpad.net/oem-priority/+bug/1844934/+attachment/5290476/+files/snap.list
--
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/1844934
Title:
from the apt history log, it looks not something fishy as well.
BTW, the only package I installed these 2 days is multipass snap package.
I use it to run a bionc VM to test TLP behavior.
** Attachment added: "history.log"
** Changed in: oem-priority
Assignee: (unassigned) => Alex Tu (alextu)
** Changed in: oem-priority
Importance: Undecided => High
** Changed in: oem-priority
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribe
the video when issue happens
** Attachment added: "t_video6068977879478174032.mp4"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1844934/+attachment/5290451/+files/t_video6068977879478174032.mp4
--
You received this bug notification because you are a member of Ubuntu-X,
which is
from journalctl , it keep print error message
** Tags added: ubuntu-certified
** Tags added: ce-qa-concern
--
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/1844934
Title:
screen jitter after
Public bug reported:
It's 1st time happens on my xps13 9380 with bionic + oem kernel 4.15.0-1056-oem.
I have updated to 1056 from 1050 for several days, this issue not happens for
these days and not experienced it on 1050 as well. So, looks it's just randomly
happens or I can not find a static
Public bug reported:
It's 1st time happens on my xps13 9380 with bionic + oem kernel 4.15.0-1056-oem.
I have updated to 1056 from 1050 for several days, this issue not happens for
these days and not experienced it on 1050 as well. So, looks it's just randomly
happens or I can not find a static
Public bug reported:
It's 1st time happens on my xps13 9380 with bionic + oem kernel 4.15.0-1056-oem.
I have updated to 1056 from 1050 for several days, this issue not happens for
these days and not experienced it on 1050 as well. So, looks it's just randomly
happens or I can not find a static
kodi_crashlog-20190808_093922.log
** Attachment added: "kodi_crashlog"
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836979/+attachment/5281622/+files/kodi_crashlog-20190808_093922.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Using Ubuntu 18.04.3 LTS with 4.15.0-55-generic #60-Ubuntu SMP Tue Jul 2
18:22:20 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
Output:
libva info: VA-API version 1.1.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/nouveau_drv_video.so
libva info:
Comfirmed.
** Attachment added: "kodi core dump and crash logs"
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836979/+attachment/5281493/+files/kodi-crash.tar.xz
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
Public bug reported:
Inevitably the mouse cursor will become fixated on screen at the
position it was when the screen was unlocked. When I switch TTY and come
back the lock screen will change and I'll be able to move the fixed
mouse cursor to a new location. Only fix is to restart the computer
The original 8 hour test without external monitor.
I removed all wired connection before testing.
Kai-Heng Feng 於 2019年7月24日 週三 下午4:00 寫道：
> Please test latest mainline kernel:
> https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3-rc1/
>
> --
> You received this bug notification because you are
collect some public bugs which look similar to this one:
- https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1821059
- https://uwot.eu/blog/xorg-present-flip-failed/
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in
not see much fishy message in kerne.log, the only message around the time of
issue happened is:
"
Jul 24 01:25:24 u-XPS-13-9380 kernel: [ 2201.963876] [drm] Reducing the
compressed framebuffer size. This may lead to less power savings than a
non-reduced-size. Try to increase stolen memory size
** Attachment added: "syslog.no-screen-after-4k-overnight.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1837683/+attachment/5278844/+files/syslog.no-screen-after-4k-overnight.tar.gz
--
You received this bug notification because you are a member of Ubuntu-X,
which is
1. When the problem is happening, does the kernel log show any problems?
(run: dmesg)
When the problem is happening, the screen is black, so no easy to type
command. I can try ssh before reproducing, but might not soon, I need to
handover this machine to another guy today.
Before that, can you
Public bug reported:
environment:
- XPS-13-938
- connect 5G ac wifi
- disabled suspend in power setting
- disabled blank screen in power setting
steps:
- play 4k video by chrome on youtube[1] overnight
symptom:
- after about 8 hours, the screen is black and keyboard and mouse can not
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
I like the helpful info you supply to your articles. I’ll bookmark your blog
and take a look at once more here frequently. I am somewhat sure I will be told
plenty of new stuff right right here! Good luck for the following!
https://www.writecdr.com/ipenz-ka02-new-zealand-skilled-migration/
I like the helpful info you supply to your articles. I’ll bookmark your blog
and take a look at once more here frequently. I am somewhat sure I will be told
plenty of new stuff right right here! Good luck for the following!
https://www.writecdr.com/ipenz-ka02-new-zealand-skilled-migration/
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
I tried older kernel, older nvidia-driver and switching to lightdm.
Nothing helped.
--
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/1825626
Title:
nvLock: client timed out, taking the lock
To
I have the exact same error.
Laptop: MSI GL62M 7REX
GPU: Nvidia GeForce 1050 Ti
Started after i upgraded to 19.04
--
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/1825626
Title:
nvLock: client
I reviewed vulkan-loader version 1.1.101.0-2_amd64 as checked into
disco. This shouldn't be considered a full security audit but rather a
quick check of maintainability.
- No CVE history in our database
- vulkan-loader provides support for loading the main vulkan library,
handling layer and
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
With kernel 4.18 and 410.104 drivers, it seems to work properly for me.
Ubuntu 18.04.2 LTS on a Dell Inspiron Gaming 7000 with nvidia GeForce
GTX 1050 Ti, Gnome.
I am here because a couple patches ago, I lost ability to resume from
sleep. Opening the lid, it would just hang in black screen,
Public bug reported:
Hi,
Recently, I installed Ubuntu 18.04 on my Dell G7 7588. From day one, the
system has random freezes/crashes (usually a few a day)
The way the crashes manifest is that 2 out of my 3 monitors go black and
in some cases sound and inputs get stuck. In some rare cases, I can
*-display
description: VGA compatible controller
produit: Skylake GT2 [HD Graphics 520]
fabriquant: Intel Corporation
identifiant matériel: 2
information bus: pci@:00:02.0
version: 07
bits: 64 bits
Thanks Diego for the information, I also got the feeling that the bug is
linked to logind waiting for something from the network or usb (not
sure).
I also wanted to add that this bug cause another annoyance : while I
plug a USB storage key in, the system is blocked for a while : I can
move the
I got the issue, today while using sudo (to use bindfs), just after I
typed my password, whole gnome got blocked (the mouse cursor moving but
without changing shape and being unable to type, neither have any action
on any window or program), but I could log in a new tty console. Note
also that
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
@grzesiekC, on my side, I quite frequently do the same (connecting /
reconnecting), I will try to pay attention, to see if it's correlated.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
@grzesiekc thanks for the comment, on my side I have no such specific
content.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1785964
Title:
Unable to unlock the desktop session:
I have the same bug here, and it's been quite a long time. It comes from
time to time. After a while logins happens, but sometimes it's after a
really long time !
I'm not sure but it seems uptime is generally high on my side.
$ uptime
15:10:50 up 8 days, 19:07, 2 users, load average: 1,47,
** Attachment added: "tignasse-syslog1"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785964/+attachment/5205389/+files/tignasse-syslog1
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
** Attachment added: "tignasse-syslog2"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785964/+attachment/5205390/+files/tignasse-syslog2
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
Public bug reported:
my normal monitor's resolution is 1920x1080, but when ubuntu is
loading, it makes resolution 1024x768 and I can't make it better
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xserver-xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
1 - 100 of 1090 matches
Mail list logo
