I'm not sure how far the Python3 update has gotten, but I've done a bit
of work on the issue updating the 1.91-1 repository on my github:
https://github.com/Erotemic/terminator2
If there is still Python3 work to be done for the next release, I
wouldn't mind putting a bit of my time towards it. I'l
I've re-upgraded to 24.04 and this is still happening. I will look into
the posted workarounds and see if I can gather more information.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064037
Title:
I upgraded to the 550 drives, which did seem to remove the simple-drm
piece from my logs, but the issue still occurs.
What looks like the Relevant part of the logs:
```
Sep 16 21:26:40 toothbrush /usr/libexec/gdm-x-session[2580]: (WW) NVIDIA(0):
Failed to request fliplock.
Sep 16 21:26:40 tooth
This is causing me issues. I installed mlocate in 22.04 (and from what I
understand that is an alias for plocate), but it is taking too long, and
I would rather just install other packages, but the dpkg lock is now in
use, and stopping the install seems to break things, so without
knowledge on how
Public bug reported:
I've got a fresh install of the first 24.04 release, and I'm seeing
strange behavior related to super+arrow keys and the enhanced tiling.
I've disabled tiling popups and tiling groups, but I like the quad
blocks.
The issue is when I'm moving around windows, sometimes the oran
I was able to get a screenshot of the issue. I edited the images to
remove sensitive information I was working with at the time, but the
point is that I was moving around windows (I forget if I was using
super+arrow or dragging to corners), and the issue happened. I'm still
not sure exactly how to
I've confirmed it does happen when just using super+arrow and no mouse
interaction. I still cannot get it to work reliably though.
My monitor setup looks roughly like this:
```
+--+
|2 | +--+
| | |1 |
+--+ | |
+--+ | |
|3 | |
Public bug reported:
I've written an AskUbuntu question about this:
https://askubuntu.com/questions/1511958/screen-lock-keeps-occuring-
on-24-04-even-though-i-believe-ive-disabled-it/1512075#1512075
Originally I thought it was gnome not respecting my setting to prevent
locking the screen after id
I'm also experiencing intermittent crashes of the window manager -
either gnome-shell or gdm3, not 100% sure. What I am sure of is that I'm
getting forcibly logged out.
I just experienced a crash when discussion this issue in matrix chat.
There were a few things going on at the time. I did have st
Also attaching the results of `sudo journalctl --dmesg --priority
warning > journalctl_dmsg_warnings.log` it does seem to have some nvidia
errors and tracebacks. It doesn't mean much to me, but perhaps it has
useful information in it.
** Attachment added: "journalctl_dmsg_warnings.log"
https:/
On the matrix chat Nils mentioned that "im on nvidia 550 atm and on
wayland. i had some X11 crashes in the past and wayland does a much
better job so far"
So, I changed my session type to Wayland by logging out and using the
gear by my username to select wayland. Doing that seems to have an issue
I did have another "random" crash in the middle of a session. I was
moving a window around. So it's not rela.ted to the main reason for this
bug report, but I figure its relevant enough to attach the journalctl
logs
** Attachment added: "wayland_crash_journalctl.log"
https://bugs.launchpad.ne
Is there a resource you could point me to where I can learn what the
security risks of public .crash files are? I'm interested to know what
sensitive information could be contained in them.
Interesting that the whoopsie-id seems to persist across OS installs, or maybe
it's tied to my Ubuntu One
I'm not sure if this is the same exact bug, my problem just seems to
happen randomly not when necessarily when I close something, I'm still
trying to identify a reproducible cause. My problem seems more similar
to https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-
ubuntu-dock/+bug/20
Update: I don't know what changed, (I did do an apt upgrade), but now
the crash is happening for Wayland too whenever the screen powers off.
It's very frustrating.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
I have noticed that it will happen in the wrong place and then go away
from time to time. That bothers me a lot less than when it persists and
obscures something I want to look at. I have no idea how to replicate it
yet.
--
You received this bug notification because you are a member of Ubuntu
Bug
Here is prevboot.txt
Is my whoopsie-id something that should be kept private? I do have files
in /var/crash that have timestamps from yesterday and today, but they do
not seem to appear under https://errors.ubuntu.com/user/ even after
I ran `ubuntu-bug `
** Attachment added: "prevboot.txt"
ht
I made an interesting observation. If I unplug all bug one monitor (I
have been using 3 in tests up until now), the crash does not occur in
X11. I have not tried wayland yet.
I'm going to plug in a second monitor to check if it happens with 2, and
then verify that it still occurs with 3.
--
You
Oh boy, so I've spent the past two days recording observations on this
issue, and I see no clear patterns at all. I've created a zipfile with a
text document called update.txt which contains my actions and
observations.
The basic pattern is: I do stuff, wait for the screen blank, un-blank
and see
I've updated my bios, but the issue seems to persist. It's still
inconsistent. Sometimes it un-blanks without issue, sometimes I get the
gray-screen-of-death, and sometimes it unblanks directly to the login
page without a GSOD.
I'll try any other debugging suggestions, including a OS-reinstall. Th
I've reinstalled a fresh copy of 24.04 with extras enabled and
recommended proprietary software installed, and I recorded a set of
observations on a fresh system. I recorded journal logs and other stats
in a similar format.
I think I may have identified a culprit. The crash appears to only occur
w
It looks like this is also true in 22.04. I'm wondering if there is a
way to build it manually? I want to use OVS to manage the networks I use
with KVM virtual machines, but I've been unable to get it working due to
the lack of builtin network manager support.
I'd like to avoid moving to netplan i
22 matches
Mail list logo
