I have the same problem on 2 installs out of 3. And no "Removing a
network device that was not added" in /var/log/syslog.
I also found that the problem does not seem to occur on Xorg, only on
Wayland.
And I also found that the work around is to go to a console and then
back using (e.g.) ctrl-alt
Another surprising observation: Wayland seems to work just fine for me,
it's only X11 that has the maximization shrinking bug. 'headerbar' can
be true or false on Wayland with 22.04. I tried it on two different
installs with the same behavior.
Okay then. I guess I'll use Wayland. I liked t
@peterx14 I did a few more experiments. One needs a new gnome
session altogether for the 'headerbar' false change to work. I tried
this a few times to confirm. Just killing all the terminals is not
enough. However, when I login/out or kill gnome-session to restart the
session manager, the p
Hm, perhaps I misremembered the tweak. I do recall that 22.04 did not
work initially. I applied the dconf menu setting and it started to
work. I reset the dconf legacy menu setting just now and it still works
(i.e. no shrinking after maximization). So I'm mystified . . .
--
You received this b
The bug disappeared for some old installs but not all. For those that
still had the bug, the following seemed to fix the problem:
dconf write /org/gnome/terminal/legacy/headerbar '@mb false'
@peterx14 maybe that would help in your case as well?
--
You received this bug notification because you
I can confirm, and this has been irritating me for years.
I suggest using 'terminator' as a work around.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1288655
Title:
Termi
We can close this bug report at this point. But I do appreciate the
follow up!
It turns out that there were two problems. The first was that 18.04 had
misconfigured the cryptoswap so that was not working at all. I reported
this separately before the release of bionic and I believe that this bug
xorg.conf has been replaced by the rules in /usr/share/X11/xorg.conf.d.
You can see if there is some older cruft in there.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1768610
If you want to try that, you can grab a more recent kernel from
http://kernel.ubuntu.com/~kernel-ppa/mainline/ but I doubt that this
will fix your issue. I'd bet on a configuration thing, but not sure
what. You don't, by any chance, have a custom xorg.conf (in /etc/X11
or /usr/share/X11)? I thin
Yes, I would make a new comment to your bug report with the logs under
xorg session. I hope that one of the Ubuntu developers have a clue
about this. I'm curious myself.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session i
P.S. I also note that you are using wayland. No reason to think it will
matter, but just of of curiosity, have you tried the xorg session?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad
I look a quick look at your posted data. It does seem odd that your
system starts out configuring the drm and then uses fb. Do you have
anything custom on your boot line, like some video parameters? E.g.
'cat /proc/cmdline'. More grabbing at straws.
--
You received this bug notification becau
Well, this sounds like a different problem. The problem I reported was
very clearly the result of an incomplete package upgrade/removal
resulting in a failed test for unity compatibility leading to setting
that environment variable for software gl.
You might consider opening an new bug report wit
Emiliano: I'm grabbing at straws, but try checking for other files in
'/etc/X11/Xsession.d/' that might be setting 'export
LIBGL_ALWAYS_SOFTWARE=1' in the environment. E.g. 'grep -H LIBGL
/etc/X11/Xsession.d/*'
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs
I'm not an expert, but you might want to see if you can gain some
insight from the output of 'journalctl -b0'.
E.g. is your system using the framebuffer driver "fbcon: xxx" or "[drm]
..." during boot up?
In the 'journalctl -b0' output I posted above,you can see that it's
using the frame buffer.
Emiliano: the problem file is
'/etc/X11/Xsession.d/50_check_unity_support'. You might want to confirm
that this is gone with the purge.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.ne
I have figured out the problem: the installer removed nux-tools, left
over from unity, but did not purge it. This left a start up script in
/etc/X11/Xsession.d which interfered with gnome. Purged that and the
problem was gone.
So this is a dependency bug in the nux-tools package (or perhaps some
** Summary changed:
- No acceleration after upgrading to 18:04 gnome-session-check-accelerated
incorrectly picks llvmpipe
+ No acceleration after upgrading to 18.04: gnome-session-check-accelerated
incorrectly picks llvmpipe
--
You received this bug notification because you are a member of Ubu
Public bug reported:
After an upgrade from 17.10 to 18.04, I noticed that all gnome windows
animations were gone. After some digging, it seems that gnome-session
incorrectly assumes that my graphics has no acceleration, when in fact
it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated gra
I continue to see this problem on a daily basis, often after a resume
from suspend, I am not running Wayland, and this crashes my
gnome-session half the time, so something there is some confusion/bug
somewhere. This morning's crash resulted in message from xorg-server so
I let apport file a bug ag
I've been studying the swap mess. It seems that the installer made a
swapfile called /swapfile and entered the line in /etc/crypttab as:
cryptswap1 /target/swapfile /dev/urandom swap,offset=1024,cipher=aes-
xts-plain64
which is the wrong, non-existent filename. So that seems to be an issue with
Thanks. Your comments led me to look at swap. There is no swap!
I installed from iso image several weeks ago (I am traveling and had a
bad ecryptfs corruption, not sure how this happened, and needed to
reinstall, and had this on my memory stick for testing).
I selected encrypted and had an prex
I saw that. But the disk is far from full. Don't know what's up with
the /snap loopback devices. The hard drive itself is at 35%. Here's
the df output:
Filesystem Size Used Avail Use% Mounted on
udev 3.8G 0 3.8G 0% /dev
tmpfs 767M 1
I'm still getting failures. This is with a fixed variety and no gnome-
shell extensions other than the default ubuntu extensions.
I don't see but reports similar to this, so I gather that others are not
generally plagued by this problem. Nonetheless, I appreciate any advice
or comment you have o
Thanks. That variety script was from an old version of variety, it
seems. I removed that and checked that the current scripts in
/usr/share/variety/scripts do not have that bug (looked like an
operation on a shell variable that may not exist). I did notice a few
variety crashes, but they do not
Daniel,
I took a few days, but it did again fail with the same issue. I'm
attaching the log, collected shortly after the failure by switch to
console while running the Wayland session, as you requested. Had to
reboot afterwards, to be able to log on to the desktop.
Hope this helps you spot the
** Tags removed: wayland-session
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1755800
Title:
Greeter/lockscreen fails to authenicate in an endless loop
To manage notifications abou
Also a problem with the Wayland session. Not a big surprise. For now,
I've turn off the screen lock.
Not sure what else to do.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1755800
Addendum: I was running the Xorg ("Ubuntu") session when the problems
occurred. I'm trying the Wayland session now, so the autogenerated tag
is not correct, and maybe not relevant.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3
Public bug reported:
After a recent install of the 18.04 (why is a separate story), I notice
that after some number of successful screen locks, I become locked out
of the desktop with an authentication failure. During those
unsuccessful attempts to log in, syslog shows:
Mar 13 22:46:04 magpie /u
I refiled the bug at bugzilla.gnome.org as bug 790040.
The link is: https://bugzilla.gnome.org/show_bug.cgi?id=790040
I'm really surprised that there are not more complaints about this. To
be fair, the dock+external monitor setup has NOT worked perfectly in any
release Ubuntu release, including
Just to make sure, I again repeated the sequence of events outlined
above on the stock 17.10 kernel:
Linux magpie 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux
The behavior is identical to that reported above.
One minor elaboration: when I open the
Public bug reported:
In the default configuration, resuming my T440s on the Lenovo ultradock
results in not detecting the external monitor followed by a suspend.
If I open the lid while on the dock, gnome detects the external monitor
and blanks the laptop display. Then, closing the lid results i
Yes, no problem with GNOME on Xorg. Thanks for the heads up.
I found another problem with Wayland handling the dock + laptop lid that
works correctly with Xorg. Just trying to help. Not sure what package
to file a bug on, do you? Would that be xwayland?
--
You received this bug notification
Yes, GNOME on Wayland. I will try GNOME on X.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1725698
Title:
Size decreases when cycling between full-screen mode using F11
Public bug reported:
Launch an gnome-terminal and cycle between full screen and normal by
pressing F11 twice. The original size of the terminal is not restored.
Doing this multiple times, the window continues to shrink.
This did not occur on 17.04 or earlier. I use this regularly as part of
my
Regarding Comment #6: I can confirm that changing the BIOS setting on
numlock behavior from "independent" to "synchronized" does indeed solve
the problem here.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu
37 matches
Mail list logo
