[Bug 2063270] Re: display artifacts in gnome-console

2024-04-24 Thread Egmont Koblinger
I'm having a hard time trying to tell apart lit pixels from dust on your screen. :) Do you mean these dots that blink together with the cursor? ** Attachment added: "PXL_20240424_153154820.MP_marked.jpg" https://bugs.launchpad.net/ubuntu/+source/gnome-console/+bug/2063270/+attachment/5770113/

[Bug 2063270] Re: display artifacts in gnome-console

2024-04-24 Thread Egmont Koblinger
Thanks a lot! Forwarded upstream at https://gitlab.gnome.org/GNOME/vte/-/issues/2778 for the developer most familiar with this area to take a look. ** Bug watch added: gitlab.gnome.org/GNOME/vte/-/issues #2778 https://gitlab.gnome.org/GNOME/vte/-/issues/2778 -- You received this bug notifica

[Bug 2064073] Re: gnome-terminal display lags on keypresses

2024-04-29 Thread Egmont Koblinger
*** This bug is a duplicate of bug 2059847 *** https://bugs.launchpad.net/bugs/2059847 It's a bug in the mutter package; a fix is on the way. See bug #2059847. ** This bug has been marked a duplicate of bug 2059847 Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRi

[Bug 2064695] Re: gnome terminal doesn't respect gnome theme setting

2024-05-03 Thread Egmont Koblinger
Upstream GNOME Terminal 3.52.1 received a change that _looks_ like it _might_ fix this. I don't know, there's no bug entry linked to it, we'd have to try and see if it indeed fixes the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to U

[Bug 2064716] Re: gnome-terminal sometimes very dark after gnome unlock

2024-05-03 Thread Egmont Koblinger
Just wondering, does it help if you disable transparency (in Preferences -> Unnamed profile -> Colors)? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064716 Title: gnome-terminal sometimes very dar

[Bug 2064716] Re: gnome-terminal sometimes very dark after gnome unlock

2024-05-06 Thread Egmont Koblinger
Sorry if I wasn't clear. I didn't mean what if you toggle transparency after the bug manifests. What I meant was: What if you completely disable transparency, use gnome-terminal without enabling that feature. Maybe even restart gnome- terminal, just in case. Does the bug still occur then? If so,

[Bug 2059847] Re: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?"

2024-05-14 Thread Egmont Koblinger
> The only thing that has worked for me is listed below > 1. Reinstall Ubuntu LTS 22.04.4 without any upgrade or just don't connect it > to the internet. To anyone who considers reinstalling the OS due to this issue (because you messed up your system beyond repair, or whatever): Why not go for 24

[Bug 2059847] Re: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?"

2024-05-14 Thread Egmont Koblinger
> @egmont-gmail For users on 22.04, would you suggest upgrading to 24.04 as > well ? > Is this something you would recommend or are there some important pitfalls to > know about beforehand ? @toniopelo I cannot make a generic recommendation. It depends on your circumstances, priorities, short-te

[Bug 2073881] Re: gnome-terminal stopped accepting arguments: # Failed to parse arguments: Too many arguments

2024-10-18 Thread Egmont Koblinger
I guess this patch should work. I tried to remain as close to the existing code as possible, just remove that erroneous parameter which comes from self.args[0]. (No idea how to properly format the patch here, anyway, you get the point and can apply manually.) --- gnome-terminal +++ gnome-terminal

[Bug 2073881] Re: gnome-terminal stopped accepting arguments: # Failed to parse arguments: Too many arguments

2024-10-21 Thread Egmont Koblinger
> generally the [0] argument can also be -- How? Can you please give an example? The upstream GNOME Terminal change that we're affected by is https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/8074. GNOME Terminal used to silently ignore non-option parameters (before the "--" if such a parame

[Bug 2089835] Re: gnome-terminal crashes when detaching window

2024-11-28 Thread Egmont Koblinger
Duplicate of bug 2049923? ** Summary changed: - gnome-terinal crashes when detaching window + gnome-terminal crashes when detaching window -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2089835 Title

[Bug 2073881] Re: gnome-terminal stopped accepting arguments: # Failed to parse arguments: Too many arguments

2025-04-06 Thread Egmont Koblinger
Ubuntu 25.04 removes the gnome-terminal.real wrapper, and thereby (maybe accidentally) fixes this bug. The only affected distro is 24.10 which will EOL in 3-4 months from now, so I guess it won't see a fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is s

[Bug 2097620] Re: anomal blinking of a cursor in terminal

2025-04-05 Thread Egmont Koblinger
So, the rectangle text insertion cursor is where it is supposed to be, but is blinking much faster than it should; do I understand you correctly now? When this happens, how long does it last? If you move the mouse pointer away, does the blinking go back to its regular pace? If you move the mouse p

[Bug 2106366] Re: Progress indicator barely visible in light theme

2025-04-07 Thread Egmont Koblinger
** Attachment added: "Screenshot" https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2106366/+attachment/5869953/+files/Screenshot%20From%202025-04-07%2010-01-04.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https:

[Bug 2106366] [NEW] Progress indicator barely visible in light theme

2025-04-07 Thread Egmont Koblinger
Public bug reported: VTE 0.80 + GNOME Terminal 3.56 (about to debut in Ubuntu 25.04) add a new feature: showing progress in the tab bar. Open multiple tabs (since unfortunately the title bar doesn't show the progress), and in one of them execute a command such as printf "\e]9;4;1;33\e\\" Th

[Bug 2107459] Re: gnome-terminal starts in fullscreen after setting more than 36 rows in profile preferences

2025-04-17 Thread Egmont Koblinger
It's not specific to gnome-terminal. Mutter has a feature that if the initial size of a window is quite large then it maximizes that window. (I faced this problem with Firefox a while ago. Firefox remembers the last window size and opens the new window at that size. I prefer to have my Firefox at

[Bug 2108846] Re: gnome-terminal crashes when detaching tab via mouse

2025-04-23 Thread Egmont Koblinger
How do you _exactly_ detach a tab? Do you drag-n-drop it outside of the window? This action is disabled in upstream GNOME Terminal (exactly because we know GTK can segfault here) and I can't seem to find an Ubuntu patch that would re-enable it. Or do you right-click and choose Detach? If so, isn'

[Bug 2097620] Re: anomal blinking of a cursor in terminal

2025-02-16 Thread Egmont Koblinger
"a cursor starts to blink rapidly when the cursor is [...]" -- so is this another cursor, not _the_ normal cursor? Is it another one of the same shape elsewhere (where?), or a different shape? By "cursor", it seems to me that you mean the mouse pointer, and not the terminal's text insertion rectan

[Bug 2097620] Re: anomal blinking of a cursor in terminal

2025-03-23 Thread Egmont Koblinger
Really strange... > I open a terminal (the vanilla one that pops up when I press ctrl+super+T) Could you please check which terminal app it is? The bug was labeled to belong to gnome-terminal, but that's not the default anymore. Look for "hamburger menu" -> About or something similar. -- You re

[Bug 2112005] Re: Merge gnome-terminal from Debian Unstable for questing

2025-05-29 Thread Egmont Koblinger
Mainstream gnome-terminal 3.56.0 -> 3.56.1 is practically a no-op release. If anything, updating gnome-terminal to 3.56.2 and correspondingly vte to 0.80.2 would make sense, these both do contain actual fixes. -- You received this bug notification because you are a member of Ubuntu Bugs, which i

[Bug 2112278] Re: gnome-terminal error typing after nslookup

2025-06-01 Thread Egmont Koblinger
Okay, I could test it (and reproduce) on 24.04. Yesterday I could only try it on 25.04 and it's fixed there. The bug happens in every terminal, the terminal doesn't matter. nslookup leaves the terminal line settings at a nondefault state, and bash doesn't restore the original ones. Not sure which

[Bug 2112278] Re: gnome-terminal error typing after nslookup

2025-06-01 Thread Egmont Koblinger
Can you please specify *exact* steps to reproduce the problem? E.g. how do you exactly quit nslookup? Does the bug occur in other terminals as well? I'm almost certain it does. I suspect that nslookup doesn't restore the terminal line's settings on an unclean exit, nor does the bash shell. -- Yo

[Bug 2116987] Re: terminator fails to launch after upgrading to plucky 25.04

2025-07-17 Thread Egmont Koblinger
> /usr/local/bin/terminator:4: This is not part of the official Ubuntu Terminator package either. At this point it's absolutely certain that you have tampered with the installation, or created alternate / manual installations of this software, and this is causing problems to you. It works for me

[Bug 2116987] Re: terminator fails to launch after upgrading to plucky 25.04

2025-07-17 Thread Egmont Koblinger
Terminator works fine for me on 25.04. You are launching ./terminator or /home/heather/.local/bin/./terminator which is not part of the terminator package. I guess it's something that you created for yourself perhaps?? None of the files shipped by the terminator package contain the string "pkg_re

[Bug 2116987] Re: terminator fails to launch after upgrading to plucky 25.04

2025-07-17 Thread Egmont Koblinger
By definition, /usr/local is to be left empty (apart from some subdirectories) by distributions, it's a place for stuff that you install for yourself. I've downloaded and examined Ubuntu's Terminator package just to be sure, and it does _not_ ship files under /usr/local. You might have set up a d

<    3   4   5   6   7   8