Public bug reported:
Since a while I have stange issues with X. As it happens with multiple
applications, I guess it's not application related but some xserver
related issue. The issue itself is about having odd horizonal stripes
sometimes, or sometimed unreadable fonts, etc. Sometimes they
** Attachment added: Rendering problems with google-chrome.
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1052910/+attachment/3323886/+files/Screenshot%20from%202012-09-19%2014%3A49%3A44.png
--
You received this bug notification because you are a member of Desktop
Packages, which is
** Attachment added: Rendering problems with pidgin.
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1052910/+attachment/3323887/+files/Screenshot%20from%202012-09-19%2011%3A50%3A24.png
--
You received this bug notification because you are a member of Desktop
Packages, which is
** Attachment added: Rendering problems with pidgin.
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1052910/+attachment/3323888/+files/Screenshot%20from%202012-09-19%2011%3A50%3A24.png
** Attachment removed: Rendering problems with pidgin.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1052910
Title:
Rendering problems in X with various applications.
Status in “xorg” package in Ubuntu:
New
Bug description:
Since a
Public bug reported:
I'm using Unity-2D (so metacity), up-to-date precise, 32 bit. Since a
while (I can't tell the exact point, since I've just noticed it) I can't
drag tabs in chrome and firefox (to re-order tabs) anymore. I am sure in
one thing: it works in oneiric at least, since I have a
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to metacity in Ubuntu.
https://bugs.launchpad.net/bugs/1011594
Title:
Dragging of tabs does not work with chrome and firefox
Status in “metacity” package in Ubuntu:
New
Bug description:
Public bug reported:
I am not sure if it's a bug, however this works on the text console
without problem since years.
Yes, that is ugly, I know: sometimes I need to test (while developing)
softwares run as a specific unix user. To make this simple I often used
the trick to add a line to
lgb@orion:~$ gnome-session --version
gnome-session 3.2.0
lgb@orion:~$ dpkg -S `which gnome-session`
gnome-session-bin: /usr/bin/gnome-session
lgb@orion:~$ dpkg -s gnome-session-bin
Package: gnome-session-bin
Status: install ok installed
Priority: optional
Section: gnome
Installed-Size: 576
If I try to run gnome-session by hand:
lgb@orion:~$ gnome-session
gnome-session[6343]: GLib-GIO-CRITICAL: Settings schema
'org.gnome.SessionManager' is not installed
gnome-session[6343]: GLib-GIO-CRITICAL: Settings schema
'org.gnome.desktop.session' is not installed
gnome-session[6343]:
Sorry for the huge amount of comments from me, but I think this bug is
simply a show-stopper, since system can't be used at all (well of
course, if someone can run another kind of session than gnome ...). I
try almost every day to upgrade the system and check the situation with
oneiric, but still,
@Sebastien: thanks for your answer!
gnome-session-bin: 3.2.0-0ubuntu2
gconf2: 3.2.0-0ubuntu1
libglib2 is not installed, not even an installable package exists with
that name (according to apt-get install)
Similar package name seems to be libglib2.0-0 , it's installed, and
version is:
I've reinstall the mentioned packages (apt-get --reinstall install ...)
but still no success.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/852485
Title:
[oneiric] cannot
@Anakin: hmm, but does it mean that oneiric will be released as stable
that I can't even log in to the system? It sounds quite painfull
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
I would be surprised, if a specific bug like this is caused by a
hardware failure, especially because I am using that notebook since
months without a single problem (with previous versions of Ubuntu, too).
Also, other DEs, like KDE seems to work nicely, with many resource
hungry tasks (which
I've removed sabayon (dpkg --purge sabayon). I have even done a reboot
then. However the problem remains. I've attached the whole .xsession-
errors file (I've tested with a totally new and clean user). I've
tested memory with memtest for a while at least, as I thought; no
problem has been found.
By the way, by google'ing a bit, I found something which seems to be a
bit similar to my problem at least: http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=633851
Also there was an article mentioning that all your gconf schemas have
been unregistered for some reason and suggesting this:
cd
Just one thing (I don't know if it's a problem or not): on a natty system there
is file:
/usr/share/gconf/schemas/gnome-session.schemas
However on my promlematic oneiric notebook is does not exist. However since
they are different ubuntugnme releases, maybe it's not even a problem.
--
You
Command gsettings get org.gnome.desktop.session session says: No such
schema 'org.gnome.desktop.session'. Setting envvar XDG_DATA_DIRS to
/usr/share does not seem to help. The output of grep (with also the -n
option) is attached.
** Attachment added: grep.output
Wow! Yes. With removing (well, moving away to have a backup) I could log
in.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/852485
Title:
[oneiric] cannot login, failed to load
Still some minor issues left, like missing icons (firefox etc), maybe
that's the problem of bad XDG_DATA_DIRS. I wonder if I made misstake to
always install meta packages for kubuntu, edubuntu, xubuntu, etc too,
since as far as I can recall, that file you suggested to remove is part
of edubuntu
Public bug reported:
I've upgraded to oneiric to test the new not-yet-ready version of
ubuntu. However since then I cannot log in at the lightdm (btw I tried
to use gdm too, the result is the same) screen. A window (without
borders) appear that failed to load session ubuntu. The result is the
** Attachment added: .xsession-erros file
https://bugs.launchpad.net/bugs/852485/+attachment/2416290/+files/.xsession-errors
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
Btw, I also created a new user, and tested with that, to be sure that no
user config files etc can cause problems, but the result was the same.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
Interesting: running X (with another DE/WM) I got this:
lgb@orion:~$ gconftool --dump /
gconfentryfile
entrylist base=/
Failure listing entries in `/': Failed to activate configuration server: The
name org.gnome.GConf was not provided by any .service files
/entrylist
/gconfentryfile
The
Is it possible that it's not the bug of gnome-session (I was reported
as)? Maybe it should be moved to the right package, at least deletion of
/etc/X11/Xsession.d/20desktop-profiles_activateDesktopProfiles helped,
and that file is part of pacakge desktop-profiles and rdepends on
Public bug reported:
I've upgraded oneiric to precise (32 bit). One annoying problem is the
window placement/moving policy now. In oneiric this worked (I am using
Unity-2D, so metacity, composing manager/effects are enabled) very well.
If I open a new window, it will be placed stacked on existing
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to metacity in Ubuntu.
https://bugs.launchpad.net/bugs/971322
Title:
Unity-2D/metacity window placement/move problems in precise
Status in “metacity” package in Ubuntu:
New
Bug
Also it seems workspace switcher does not support wrapping: ie if I am
at the first workspace, using switch to workspace at the left would
cause (in oneiric it works) to the last one and vice versa. This
behaviour _is_ enabled, I've just checked gconf settings, but it does
not work anyway.
--
Public bug reported:
I'm using Unity-2D with metacity (composite effects are on). I also
switched on icons on the desktop (computer, home, mounted filesystems),
but I have custom ones too. If I want to move an icon by dragging it,
ugly garbage is left on the screen where I move that icon. The
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to metacity in Ubuntu.
https://bugs.launchpad.net/bugs/980013
Title:
moving icons on the desktop leaves some garbage
Status in “metacity” package in Ubuntu:
New
Bug description:
I'm
Public bug reported:
Not exactly a show-stopper bug ... I have a terminal window, not
maximazed, but full screen. I'm using Unity-2D+metacity, with composite
support is switched on. The terminal window is semi-transparent. Now, if
I move the mouse to the left side of the screen, I can see
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to metacity in Ubuntu.
https://bugs.launchpad.net/bugs/985449
Title:
unity-2d launcher behind a full screen window
Status in “metacity” package in Ubuntu:
New
Bug description:
Not
I have whitelisted pidgin for systray icon (well not just pidgin but
all). The stange thing: I cannot see pidgin's icon, however during
switching workspaces, pidgin icon _can_be_ seen but only for that moment
while workspace switching sliding effect is played, then it cannot be
seen again
--
Public bug reported:
I've just upgraded my desktop from Ubuntu 12.04 to 12.10 (32 bit).
Everything works fine till the lightdm login screen: after I gave my
password nothing happened, and login screen was not responsive either.
Switching back to text console, I noticed that several things (which
Public bug reported:
This (or these kind ...) of bugs sometimes happens. No exact information
how to trigger, but it seems some kind of rapid change between
workspaces can help to trigger it.
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: xserver-xorg-video-intel 2:2.21.4-0ubuntu1b1
Public bug reported:
Sometimes (but not always) after locking the screen there is the
situation not having any input field where I can type the password to
unlock the session again. The shaded gray area simply does not have the
input field. I can't do anything, I have to switch to text console
Public bug reported:
I work with terminal windows (gnome-terminal) a lot. I have 8 workspaces
and multiple terminals on each of them. Sometimes I need to focus on a
more complicated issue eg with a server I am logged on via ssh on a
terminal, in this case I use full screen mode. Initially it
It happened again now (up-to-date 14.04 LTS now): screen started to fade
out after pressing CTRL-ALT-L, then it stuck in the middle of process, I
can move the mouse, but I can't do anything neither with mouse or
keyboard. What helped: switching to text console (CTRL-ALT-F1) login,
then killing
Public bug reported:
First of all, sorry, I am not sure what kind of package should I specify
with this report.
Upgraded to trusty, and some of the user settings are not used (or only
temporary) anymore:
* I use F12 to open a terminal since ages (I depends most on terminals in my
work).
Same here, 32 bit up-to-date (daily updated) 14.04 32 bit on a Lenovo
L520 notebook. I can't type password at lightdm login screen, and not
even able to move up/down (to select user to log in as) with the
keyboard. Just click on the AT icon (without actually selecting anything
from there eg
Public bug reported:
After each login a dialog box appears to enter the password of my gmail
mailbox. However even if I type the correct password, the dialog box
reappears. It seems it's totally unimportant if I type the correct or
some incorrect password. The only thing which helps is to cancel
Public bug reported:
Somewhat odd situation. If I use CTRL-ALT-L to lock my session, it
normally works as expected. However if there is a fullscreen gnome-
terminal (F11) was on the screen, CTRL-ALT-L does something interesting:
it begins fade the screen but it's left in a middle state, no way to
Btw, the other even more odd workaround: switch to text console, kill
gnome-terminal and switch back to the VT used by X, and you can unlock
then.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-screensaver in Ubuntu.
Public bug reported:
Up-to-date 32 bit 14.04 on Lenovo L520 notebook. After locking the
screen eg with CTRL-ALT-L I want to unlock it, so I give my password. It
works, but sometimes after some seconds of unlocked state (I already
working, ie typing etc) the screen fades out again and I have to
Public bug reported:
I am not sure if it's bug of xserver-xorg or other package. The problem:
after reboot everything seems to be fine, scrolling within windows,
moving windows are smooth and fast. After some time however everything
becomes quite slow, eg output in gnome-terminal which made the
The dialog box saying low graphics mode allows me to exit to console, if
I do that, I can see on console 7 (ALT+F7):
[FAILED] Failed to start Light Display Manager.
See systemctl status lightdm.service for details.
[DEPEND] Dependency failed for Graphical Interface.
Entering the suggested
** Package changed: xorg (Ubuntu) = lightdm (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1434396
Title:
Xserver does not start on boot (low-graphics mode)
Status in
Public bug reported:
After upgrading to (32bit) vivid I hadn't got any problem, but since a
day (daily upgraded) booting results in a dialog saying low graphics
mode and a dialog window about this. Choosing running in default mode
causes to boot splash to be shown forever. if I choose exit to
By the way I am not sure if it's related: on booting backlight of the
LCD (of the notebook) is always set to minimal during the boot at one
moment, barely visible (but surely I can use the keyboard Fn +
corresponding key to increase to a readable level). It was also the
situation with the previous
** Summary changed:
- Xserver does not start, on boot (low-graphics mode)
+ Xserver does not start on boot (low-graphics mode)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1434396
And it seems after I can login the crash report dialog brings me to bug
1340964 then. What is interesting for me: why is there a problem Xorg
does not start, when it does if I try it then.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
I have a problem described in bug 1434396 that is: Xserver does not
start on boot, and the low graphics mode dialog is presented instead,
though if I exit to console and start lightdm service by hand it
works. After logging in, bug report dialog on X crash appears and that
brings me to this
@asala But does using upstart (or systemd, but with gdm instead of
lightdm) fixes it for you? Then it can be said, at least lightdm+systemd
issue ... However reading duplicates, and comments here, at least it
seems, Lenovo Thinkpads are highly affected for some reason, even if not
only ...
--
ThinkPad L520: exactly the same as professordes wrote: systemd + lightdm
does not work, dropping to console login freezes (interestingly it
worked some days ago when I managed to use service lightdm stop/start
to cure the problem at least so systemd could be used with some extra
work though, not
Now it turns out even more bizarre, I can no longer use my notebook with
systemd. After having that low-graphics dialog, only exit to console
helped (eg stopping/starting lightdm service by hand) but now exit to
console cause a freeze that the computer does not react to keyboard
anymore (not even
I have this bug only with systemd, choosing upstart everything is OK,
again please read my comment at bug 1434396
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1340964
Title:
Hmm, reading the duplicates, it seems it's a Lenovo notebook + systemd +
lightdm combined problem, and does not occur too much if all of the
three conditions do not meet? For me, it's true, all of them, and I have
the problem at least ...
--
You received this bug notification because you are a
Today I tried again and now it seems system boots normally, I can log
in, with lightdm+systemd. I guess some of the updates solved the
problem, but it would be useful to hear that it's not only me ...
--
You received this bug notification because you are a member of Desktop
Packages, which is
** Summary changed:
- Xserver does not start on boot (low-graphics mode)
+ Xserver does not start on freezes with systemd + lightdm
** Summary changed:
- Xserver does not start on freezes with systemd + lightdm
+ Xserver does not start or freezes with systemd + lightdm
--
You received this
This bug seems to be still valid, but its behaviour is somewhat
different at least for me. When I first noticed this, X did not start at
all, and it dropped to the screen to allow to choose for low graphics
mode, exit to console, etc. Now, X starts however it freezes in a way
that no keyboard can
It seems though it can be guessed more or less what can cause problems
(ie thinkpad + lightdm + systemd) the exact details are not the same,
and some other conditions can/do count as well. Also the not always
factor sometimes, kinda odd.
However, as bug 1340964 if often referenced for me, and it
Ok, I was too fast ... Tried again: now, X server starts and logic
screen is shown (though with the default background not the one based on
the last user logged in) but keyboard does not usable and no mouse
cursor either. Still, choosing upstart seems to work!
--
You received this bug
For me, it's kinda odd. It seem to work (and worked even some day ago),
then trying again (boot again) and it does not work again then ...
Recently it seems to be quite unpredictable. But it can be a reason that
sometimes I attach external monitor via the VGA D-SUB connector, but
sometimes I
Quite ugly "bug" :( I had the habit "since ages" (ehhh) to work in
terminal windows, and copy URLs etc. It worked nicely with a quick
double click on the URL which does not work anymore after upgrade to
Wily :( I understand that it was not meant to select URLs anyway (and
not a perfect solution
Public bug reported:
It's a bit fuzzy report, I have to admit, and more like a feeling, as I
can't check it out too well, but I haven't experienced that in previous
Ubuntu versions before upgrading to Wily.
I have firefox running with many tabs open. The CPU usage (without too
much active pages,
I'm sorry but now it *seems* for me, that it's not firefox, but maybe
compiz related (hmmm, or both?), please read the newer bug report of
mine: bug 1516308
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
Meanwhile, I've upgraded to 15.10. Now the system _mostly_ works, but
let's say about every 5th boot the system freezes with black screen if
systemd is used. Upstart always work. Interestingly in most cases
systemd works as well, but not always. I cannot find any reason about
this always changing
Public bug reported:
My problem seems to be rather specific. I develop an emulator for a 8
bit computer with SDL2, capable of running on Linux and Windows. I use
cross-compiling with mingw for Windows, and wine to test it. It seems
the problem occurs when I try the windows build, with full screen
** Attachment added: "Screenshot after pressing F11 (fullscreen, OK)"
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1573563/+attachment/4642824/+files/Screenshot%20from%202016-04-22%2014-09-59.png
--
You received this bug notification because you are a member of Desktop
** Attachment added: "Screenshot after pressing F11 again, not OK!"
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1573563/+attachment/4642825/+files/Screenshot%20from%202016-04-22%2014-10-13.png
--
You received this bug notification because you are a member of Desktop
Public bug reported:
I use tons of terminal windows (gnome-terminal) all the time for various
tasks. Thus, it's important for me to be able to go into full screen
mode (F11) - if I need more attention or space and switch back later.
I haven't got any problem with this in previous Ubuntu
I've attached some screen shots, if it's more understandable than my
not-so-perfect English, sorry about that.
Moreover, I had the suspect that it can be a generic window manager
issue more, rather than gnome-terminal specific problem, but starting
the KDE console (konsole) its fullscreen toggle
Public bug reported:
It's 17.04 64 bit Ubuntu, wayland+gnome-shell. I have key F11 configured
to toggle between fullscreen and windowed mode. Just noticed, that every
time I press F11 to get full screen, then F11 to get back windowed mode,
the window becomes one line shorter ... Continuing this I
Please tell me, if you need further information of some kind of co-
operation to resolve this issue. Thanks a lot, in advance.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1688253
I'm really not an xrandr / etc wizard, but what looks strange for me,
that it seems something reports "VGA-1" when all the examples on the Net
(and in xrandr man page) mentions "VGA". Even in Xorg.log:
root@vega:~# fgrep VGA /var/log/Xorg.0.log
[25.034] (II) modeset(0): Output VGA-1 has no
Another interesting finding with grep'ing around in /var/log for VGA-1:
root@vega:/var/log# grep VGA-1 syslog
May 4 14:27:10 vega unity-settings-[1644]: unable to get EDID for
xrandr-VGA-1: unable to get EDID for output
And maybe the even more interesing part in /var/log/gpu-manager.log
Public bug reported:
I've never had a problem like this before. Now, after upgraded to Ubuntu
17.04 it was already strange to see the boot logo in a kind of low and
fuzzy resolution. And it remained for the LightDM login screen, also for
the desktop after logged on. System setting -> Display
With wayland, the problem is even worse, with X11 I could at least use
xrandr to set the correct resolution. This is not an option with wayland
though, so I cannot even use my desktop normally, I guess I should
downgrade ubuntu, since no way to use the machine in a sane way anymore,
and not so
With wayland, the problem is even worse, with X11 I could at least use
xrandr to set the correct resolution. This is not an option with wayland
though, so I cannot even use my desktop normally, I guess I should
downgrade ubuntu, since no way to use the machine in a sane way anymore,
and not so
Ok, I've found a workaround, to specify this kernel parameter in GRUB:
video=VGA-1:1920x1080@60
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1688253
Title:
Wrong resolution, and
Same problem with powerdns, I can't run it with apparmor profile,
because it complains:
operation="sendmsg" info="Failed name lookup - disconnected path"
error=-13 profile="/usr/sbin/pdns_server" name="run/systemd/journal/dev-
log" pid=17236 comm="pdns_server" requested_mask="w" denied_mask="w"
This bug still affects me now, upgraded to the to-be-released 17.10
(artful). I was a die hard text only user of Linux systems for a while,
so I still configure system to "emulate" something like this, ie
ALT+F1...F8 to switch between workspaces. However, ALT-F5 does not
_always_ works. Sometimes
Oh, by the way, it's often happens after locking then unlocking the
screen though! It often fixes the problem too (if it was before). But
not always ...
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
I've just noticed: it seems it only happens if the shell prompt is
colourfull. if it's not, there is no shrinking of the gnome-terminal
window height when cycling between fullscreen and windowed mode ...
Interesting!!
--
You received this bug notification because you are a member of Desktop
Public bug reported:
I have "Alternative switch to next source" option set to "Right Alt
(while pressed)" in "Input source options" within "Region & Language" in
settings. I use US kbd layout, but often I need my national characters,
so I use the "while pressed" solution since years, it's much
*** This bug is a duplicate of bug 1288655 ***
https://bugs.launchpad.net/bugs/1288655
I don't know how to tell, but it seems the bug happens when the prompt
has effect on the title of the window. What I mean here: opening a
gnome-terminal with a colourful PS1 causes this. However if I ssh
*** This bug is a duplicate of bug 1288655 ***
https://bugs.launchpad.net/bugs/1288655
So, as thinking on this, I must say, maybe this is my mis-interpretation
of the problem. Maybe not the colour prompt causes this, but if I use a
newer (or ssh into a newer) ubuntu box versus ssh into an
Still happens time to time, even with fresh 18.10 install. It's a
"miracle" that it's such an old bug, but still hits us :(
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
Public bug reported:
I've upgraded my Ubuntu 18.10 to 19.04. Everything looked okey, however
if I enter gnome shell "overview mode" I cannot leave it anymore, I
can't select any window, type to search etc, and all my windows are in
the foreground, covering the search bar etc, but not possible to
Public bug reported:
When I try to lock the screen, gnome-shell seems to crash, always since
two days or so (I update daily basis). crash file is attached. x86_64
Ubuntu 20.04 LTS
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
ProcVersionSignature:
I'm using 20.04.2 LTS (focal), I can also confirm the problem exists
there with Xorg and gnome-shell (no idea about 20.10 and/or Wayland
though).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
22.04 fresh install, even worse, the window shrunk by 3 lines each time
:-O And now even shrinks by 3 rows ... I use toggle full screen back and
forth, since this is what I really use a lot, not the maximize. But
maximize has the same effect, just checked.
--
You received this bug notification
I've fetched some older versions (again, I am running 22.04.4) of
packages gir1.2-mutter-10 libmutter-10-0 and mutter-common and made them
into hold status. After a very ugly and dangerous move, namely editing
/var/lib/dpkg/status by hand (to comply the dependencies of gnome-shell
which was broken
I have similar problem. I'm currently using Ubuntu 22.04.4 LTS (x86_64).
Since some days (maybe three?) I see very odd behaviour from programs
running in gnome-terminal (or xfce4-terminal if it does not matter, I
guess the problem is not the terminal itself but VTE probably or
similar? - no
Probably not related, but "nvidia-driver-535" was mentioned above in a
post. I'm now using ppa:vanvugt/mutter and it seems to be fine, but apt
also upgraded nvidia driver from 525 to 535 (maybe not related at all
just the new nvidia driver was presented now?). Since then I have hard
lock-ups on my
96 matches
Mail list logo
