I am currently running version 1.8.4-0ubuntu0.17.10.1 of both packages
and have not seen this problem for a while. I have rebooted several
times since installing the packages.
Off-topic, but since yesterday (can't remember it happening earlier) I
have started seeing mouse button freezes after
does the update still work?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1724259
Title:
gnome-shell frozen and using 100% CPU after docking and display
configuration
I must admit that I have not seen this freeze for a while (unless I just
missed it among all the swap-to-death freezes I have had recently), but
I installed the packages. I did not enable proposed, I just manually
installed libinput-bin and libinput10, versions 1.8.4. I probably can't
give any
Hello Michael, or anyone else affected,
Accepted libinput into artful-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/libinput/1.8.4-0ubuntu0.17.10.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package.
libinput 1.9.2 synced to bionic, artful will get 1.8.4 via bug #1733573
** Also affects: gnome-shell (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: libinput (Ubuntu Artful)
Importance: Undecided
Status: New
** Changed in: libinput (Ubuntu)
Status:
** Changed in: libinput
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1724259
Title:
gnome-shell frozen and using 100% CPU after
** Changed in: libinput (Ubuntu)
Importance: Undecided => High
** Changed in: libinput (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
** Changed in: libinput
Status: Unknown => In Progress
** Changed in: libinput
Importance: Unknown => High
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1724259
** Also affects: libinput (Ubuntu)
Importance: Undecided
Status: New
** Also affects: libinput via
https://bugs.freedesktop.org/show_bug.cgi?id=103298
Importance: Unknown
Status: Unknown
** Changed in: libinput (Ubuntu)
Status: New => Confirmed
--
You received
Or a third hypothesis: systemd-logind triggers a suspend on lid close if
there is no external monitor plugged in. Perhaps it looks for a while
too long like there is no monitor, so that systemd-logind suspends the
system and the GNOME Shell wayland output object disappears, causing the
xwayland
Not succeeded in reproducing this again after rebuilding GNOME Shell
with ASAN_OPTIONS=detect_leaks=0 CFLAGS="-fsanitize=address
-fsanitize=return -fsanitize=bounds -fsanitize=object-size". I do now
manage to trigger debian bug 823216 quite reliably now, with the
difference that I can log on
Thinking of it I might be confusing cause and effect here: the
unexpected suspend might be caused somehow by the xwayland and gnome-
shell crash.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
>From the other bug (this is getting a bit tiring):
I was able to trigger the crash pretty easily with the old library still
in use by opening and closing the lid a few times in quick succession
and then trying to type an update to this bug. After restarting I was
not immediately able to trigger
I have rebuilt libinput10 with the patch in that freedesktop.org bug
report and will see if that helps things before trying to submit
anything to launchpad.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
You will need to update your system (other than apport) still.
And yes I believe (based on observations today) Launchpad will accept
it. The block is only on the user end.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell
I installed debug symbols for libinput and had a look at the core file,
and it looks very much like this:
https://bugs.freedesktop.org/show_bug.cgi?id=103298
I am missing the top frame in that stack trace, but I am guessing that
is just chance based on when I took the trace. The description of
That won't fix the outdated packages (one of them was curl...) though,
will it? And does disabled mean that Launchpad will refuse to accept
the upload even if my system tries to send it?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
Apport uploads for 17.10 got disabled last night. Standard policy after
release :/
You can however get around it (please) by downgrading your apport to the
previous release. Then use 'ubuntu-bug' to push us the crash. Then
mention the new bug number here.
I'm sure there must be a proper way to
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
I checked and it was the main thread which was using CPU. Uploading a
crash report (Apport would not submit it due to a couple of outdated
packages). Note that this is on a different system with a fresh Ubuntu
17.10 install (not upgraded; but the report should tell you all that).
** Attachment
Thank you. I assume then that my failure to get a crash report was due
to the GNOME Shell process and not to the underlying mechanism. I will
just check the GNOME Shell/Mutter/whatever source next time beforehand.
--
You received this bug notification because you are a member of Ubuntu
Desktop
Maybe try "kill -TRAP" or kill "-5" on gnome-shell.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1724259
Title:
gnome-shell frozen and using 100% CPU after docking and
Yes, certainly "kill -SEGV ..." will work. But that may confuse other
readers into thinking an actual SEGV happened. Other less dramatic
signals like ABRT, URS1, USR2 may work but it depends on the program and
whether the authors are handling those internally (which means a core
may not get
I will do that next time I see this. A question: is there a signal I
can send to the process (SEGV?) to trigger an Apport bug report in
/var/crash? And would that make things easier for you?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Thanks. It's not obvious to me still which is the busy thread. Can you
find out by running 'top' and then pressing 'H' to show threads?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
Here is a gdb stacktrace. I tried sending signal 3 to the process in
the hope that it would trigger an apport bug report, but it did not.
** Attachment added: "gdb.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724259/+attachment/4991557/+files/gdb.txt
--
You received
Yes, you can get a stack trace without debug packages. It's just going
to be much less detailed, and risks not showing enough information. But
we would welcome a stack trace (or multiple traces to ensure you're
looking in the right spot), even without debug info.
** Summary changed:
- System
27 matches
Mail list logo
