[Bug 1968388] Re: Installation blocks apt due to automatic initialization
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 to stop this indexing gracefully I'm stuck waiting for updatedb to index my entire 20TB data drive before I can use anything else that needs the dpkg lock. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968388 Title: Installation blocks apt due to automatic initialization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plocate/+bug/1968388/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064037] Re: GDM session crashes after returning from a screen-off.
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 when screen lock is disabled. Maybe someone could try to reproduce? ** Attachment added: "debug-2024-05-05.zip" https://bugs.launchpad.net/ubuntu/+bug/2064037/+attachment/5775378/+files/debug-2024-05-05.zip -- 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: GDM session crashes after returning from a screen-off. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2064037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064037] Re: GDM session crashes after returning from a screen-off.
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. The alternative is that I disable screen-blanking (which seems like a waste of power) or I revert to 22.04. -- 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: GDM session crashes after returning from a screen-off. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2064037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064037] Re: GDM session crashes after returning from a screen-off.
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 if it crashes. Sometimes the crash happens and sometimes it does not. It also contains observations that detail what may be a separate issue (enabling / disabling screens had weird behavior, and I think I found a minor but fixable bug in the screenshot tool). I have 2 journalctl logs in there. After a few entries I realized I should start adding timestamps and normalize the observation format, so it goes from prose to a time / action / result / notes format after a point. In a few places I reference screenshots (which demonstrate the screenshot and monitor bug), those are included in the zipfile. Things that should be noted: At this point I've installed a fair bit of external software on the machine. I've included a list of it in apt_list.txt in the zipfile. I also have a development .pyenv in my home directory and my .bashrc will default to a specified virtualenv. So far I'm the only person who has reported this behavior. I'm wondering if its an issue with my hardware? I really like 24.04 so far, but this is a major issue for me. I may try a fresh install to make more observations with less uncontrolled variables. ** Attachment added: "debug-monitor-2024-05-02.zip" https://bugs.launchpad.net/ubuntu/+bug/2064037/+attachment/5774592/+files/debug-monitor-2024-05-02.zip -- 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: GDM session crashes after returning from a screen-off. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2064037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064037] Re: GDM session crashes after returning from a screen-off.
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 received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064037 Title: GDM session crashes after returning from a screen-off. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2064037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064037] Re: GDM session crashes after returning from a screen-off.
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" https://bugs.launchpad.net/ubuntu/+bug/2064037/+attachment/5773672/+files/prevboot.txt -- 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: GDM session crashes after returning from a screen-off. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2064037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063970] Re: Enhanced tiling orange shading that indicates what a window will resize to will persist even after I'm done with the adjustment.
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063970 Title: Enhanced tiling orange shading that indicates what a window will resize to will persist even after I'm done with the adjustment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-tiling-assistant/+bug/2063970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064037] Re: GDM session crashes after returning from a screen-off.
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.net/bugs/2064037 Title: GDM session crashes after returning from a screen-off. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2064037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056506] Re: ubuntu-dock 89 crashes on gnome-shell 45 with signal 6 when right clicking on the dock [clutter_actor_dispose: assertion failed: (priv->parent == NULL)]
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/2056633 but it is marked as a duplicate of this, so I'm posting my debug journalctl.txt info here. ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2056506/+attachment/5772540/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056506 Title: ubuntu-dock 89 crashes on gnome-shell 45 with signal 6 when right clicking on the dock [clutter_actor_dispose: assertion failed: (priv->parent == NULL)] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2056506/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064037] Re: GDM session crashes after returning from a screen-off.
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 account? I see crash reports on here going back to 2021. Recent crash reports on the 24.04 machine are: _usr_bin_gnome-shell.1000.crash - https://errors.ubuntu.com/oops/235257f3-0630-11ef-8b1f-fa163ec8ca8c _usr_bin_nautilus.1000.crash - https://errors.ubuntu.com/oops/1a6e3dfa-0409-11ef-9dc8-fa163ec44ecd _usr_bin_gnome-control-center.1000.crash - https://errors.ubuntu.com/oops/19d7ad54-0599-11ef-8b1c-fa163ec8ca8c _opt_google_chrome_chrome.1000.crash - https://errors.ubuntu.com/oops/13ddfcd0-0587-11ef-9dca-fa163ec44ecd I believe the gnome-shell is the relevant one. -- 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: GDM session crashes after returning from a screen-off. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2064037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064037] Re: GDM session crashes after returning from a screen-off.
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.net/ubuntu/+source/gdm3/+bug/2064037/+attachment/5772177/+files/wayland_crash_journalctl.log -- 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: GDM session crashes after returning from a screen-off. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2064037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064037] Re: GDM session crashes after returning from a screen-off.
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 with "Settings", clicking the setting gear or running `gnome-control- center` resulted in a segfault. I did some googling, and saw that this might be a nvidia driver issue, so I upgraded my drivers from `nvidia- driver-350` to `nvidia-driver-550`. After a reboot the segfault in `gnome-control-center` went away, and the logout crash also seems to be gone as well. I tested it by letting the screen dim, waiting 10 minutes, and then pressing a few keys. Instead of crashing it went right back to my session. Of course it would be nice if crashes didn't occur in the out-of-the-box Ubuntu 24.04 install, but in this case there seems to be a simple solution: Use Wayland and 550 drivers. -- 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: GDM session crashes after returning from a screen-off. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2064037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064037] Re: GDM session crashes after returning from a screen-off.
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://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2064037/+attachment/5772123/+files/journalctl_dmsg_warnings.log -- 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: GDM session crashes after returning from a screen-off. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2064037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064037] Re: GDM session crashes after returning from a screen-off.
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 steam and starcraft 2 open (running through steam's experimental proton). But that was in the background. In the foreground I was just moving a gvim window that had journalctl logs in it that I was going to copy into my chrome browser. I'm attaching the journalctl logs from that crash here as well, as perhaps these issues are related. ** Attachment added: "journalctl-gdm-crash-logs2.log" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2064037/+attachment/5772122/+files/journalctl-gdm-crash-logs2.log -- 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: GDM session crashes after returning from a screen-off. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2064037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064037] [NEW] GDM session crashes after returning from a screen-off.
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 idling, but after discussing the issue on matrix (https://matrix.to/#/!EJhpCQHHqqcNicfiql:xentonix.net/$kPbn- fqDZgoG4s6PyQfki8tcSKJUpGH9QrXZSSV_vKY?via=decred.org=matrix.org=ubuntu.com) I think it is actually just a gdm or gnome-shell crash that happens when the PC idles, the screen turns off, and then I wake it. To summarize the symptom. I have the PC set to disable the screen after being idle for 5 minutes. I also set it such that it should not lock the session when this happens. (I want to turn on the screen and get right back to where I was without password overhead). What I've observed is that when I give the idle PC keyboard input, it wakes to a login screen, and when I login my windows from the previous session are completely gone (although tmux sessions are still alive). I've attached a relevant section of `journalctl --user` from around the time when I last tried to interact with the idle PC. I believe the "wake" event happens at `Apr 28 13:42:43` at which point we start seeing whoopsie messages: ``` Apr 28 13:42:44 toothbrush systemd[1]: Started whoopsie.service - crash report submission. ``` And then what looks like logs indicating that I was logged out and the previous session was ended: ``` Apr 28 13:42:56 toothbrush systemd[1]: run-user-1000-gvfs.mount: Deactivated successfully. Apr 28 13:42:57 toothbrush gdm-password][60731]: pam_unix(gdm-password:session): session closed for user joncrall Apr 28 13:42:57 toothbrush systemd[1]: session-61.scope: Deactivated successfully. Apr 28 13:42:57 toothbrush systemd[1]: session-61.scope: Consumed 12min 9.467s CPU time. Apr 28 13:42:57 toothbrush systemd-logind[1790]: Session 61 logged out. Waiting for processes to exit. Apr 28 13:42:57 toothbrush systemd-logind[1790]: Removed session 61. ``` The time from `13:42:44` to `13:43:07` where I get: ``` Apr 28 13:43:07 toothbrush systemd-logind[1790]: New session 221 of user joncrall. Apr 28 13:43:07 toothbrush systemd[1]: Started session-221.scope - Session 221 of User joncrall. ``` seems about right, because it takes a few seconds to go from de-idling the machine to seeing any sort of display. System Information: No LSB modules are available. Description:Ubuntu 24.04 LTS Release:24.04 # System Details Report --- ## Report details - **Date generated:** 2024-04-28 15:17:36 ## Hardware Information: - **Hardware Model:** ASUS ROG STRIX Z590-E GAMING WIFI - **Memory:** 128.0 GiB - **Processor:** 11th Gen Intel® Core™ i9-11900K × 16 - **Graphics:**NVIDIA GeForce RTX™ 3090 - **Graphics 1:** NVIDIA GeForce RTX™ 3090 - **Disk Capacity:** 45.0 TB ## Software Information: - **Firmware Version:**0232 - **OS Name:** Ubuntu 24.04 LTS - **OS Build:**(null) - **OS Type:** 64-bit - **GNOME Version:** 46 - **Windowing System:**X11 - **Kernel Version:** Linux 6.8.0-31-generic Nvidia versions: NVIDIA-SMI 535.171.04 Driver Version: 535.171.04 CUDA Version: 12.2 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gdm3 46.0-2ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Apr 28 15:04:13 2024 InstallationDate: Installed on 2024-04-25 (3 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2024-04-25T18:50:53.891514 ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble ** Attachment added: "Journalctl logs" https://bugs.launchpad.net/bugs/2064037/+attachment/5772117/+files/journalctl_logs.log -- 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: GDM session crashes after returning from a screen-off. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2064037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com
[Bug 2063970] Re: Enhanced tiling orange shading that indicates what a window will resize to will persist even after I'm done with the adjustment.
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 | | | | | | | +--+ +--+ ``` In one test, I was moving a window in monitor 3, and after pressing super+down the orange box appeared across the bottom of monitor 2, which is kinda weird. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063970 Title: Enhanced tiling orange shading that indicates what a window will resize to will persist even after I'm done with the adjustment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2063970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063970] Re: Enhanced tiling orange shading that indicates what a window will resize to will persist even after I'm done with the adjustment.
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 reproduce, but this at least provides some illustration of what is happening. Also note. I have 3 monitors. Two are in landscape and 1 is in portrait. Nothing of interest was in the other monitors. I'll also note I'm using nvidia graphics. I have an RTX 3090 driving the 3 monitors. ** Attachment added: "Screenshot of issue where orange overlay does not go away" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2063970/+attachment/5771713/+files/gnome-shell-bug-reproduction.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063970 Title: Enhanced tiling orange shading that indicates what a window will resize to will persist even after I'm done with the adjustment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2063970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063970] [NEW] Enhanced tiling orange shading that indicates what a window will resize to will persist even after I'm done with the adjustment.
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 orange shading that indicates what a window will resize to will persist even after I'm done with the adjustment. I'm not sure how to reproduce yet, but it's happened several times. Not sure if I'll be able to take a screenshot or not. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell 46.0-0ubuntu5 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 27 16:06:49 2024 DisplayManager: gdm3 InstallationDate: Installed on 2024-04-25 (2 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) RelatedPackageVersions: mutter-common 46.0-1ubuntu9 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063970 Title: Enhanced tiling orange shading that indicates what a window will resize to will persist even after I'm done with the adjustment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2063970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621156] Re: terminator not working with python3
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'll need to familiarize myself with the launchpad contribution process though. Is there a site (e.g. github / bitbucket / gitlab) where the main development repository is hosted and that I could submit a merge request to? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1621156 Title: terminator not working with python3 To manage notifications about this bug go to: https://bugs.launchpad.net/terminator/+bug/1621156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
