[Bug 1609342] Re: Gnome-terminal sets directory to HOME for ctrl-shift-n and custom shell command
For setting: vte-2.91.sh is intended to do that... the ".sh" extension was missing, sorry. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1609342 Title: Gnome-terminal sets directory to HOME for ctrl-shift-n and custom shell command To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1609342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1609342] Re: Gnome-terminal sets directory to HOME for ctrl-shift-n and custom shell command
gnome-terminal 3.36, which is included in Ubuntu 20.04, added a config option Preferences -> -> Command -> Preserve working directory. Older versions preserved the directory only when launching a shell, not when launching a custom command. This behavior was frowned upon by some folks, understandably. The change is at https://gitlab.gnome.org/GNOME/gnome- terminal/-/commit/79b2291 , the two bugtracker entries are linked from the commit message. Now, in order for this to work, two more things have to happen: Whichever application (presumably your shell) is running in the source window has to set the desired value, and whichever application is starting up in the new window has to respect it (not intentionally override it). For setting: vte-2.91 is intended to do that, see its __vte_osc7() method. Now there's a chance that some fragment in your shell profile overrides it. To debug I recommend to manually issue the given escape sequence and then not give back control to the shell, not to give it a chance to override from PS1 or PROMPT_COMMAND or so: printf "\e]7;file:/etc\e\\" ; sleep 1000 A newly opened tab should be in /etc now. If this fixes the problem then try it without the sleep. If that still fixes then your shell just doesn't emit it. If removing the sleep breaks it again then there's something in your prompt overriding the value. To debug the other side: Set up a custom command of "sleep 2000", open a new window, from another terminal locate the pid of this sleep, and check its working directory at /proc//cwd. If this is set correctly, yet it doesn't work your shell or custom command, then it's that command intentionally switching to some other directory. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1609342 Title: Gnome-terminal sets directory to HOME for ctrl-shift-n and custom shell command To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1609342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876768] Re: Terminal mouse went berserk after lost ssh connection
The same applies not just for the mouse mode, but a whole lot of other terminal modes (e.g. keypad modes, alternate charset, alternate scroll mode, bracketed paste mode, colors, attributes and many many more...). The problem cannot be fixed in the terminal: The terminal, by design, only sees a single continuous stream of instructions to execute. It has no idea where they come from, e.g. remote or local, ssh or not. It cannot figure out when is the time to override those instructions. A reasonable place to fix this would be the shell prompt (or a hardwired behavior of the shell, to reset these modes whenever it prints the prompt). You can customize your PS1 to include the escape sequence that switches off mouse mode, and whatever else you wish. (Don't forget to wrap these in \[ \] as per the PROMPTING section in bash's manual.) I agree that either upstream bash, or downstream distributions by configuring PS1 accordingly, should do their best to minimalize the risk of such situations, i.e. reset as many of the terminal modes as reasonable. I myself used to do it in my personal PS1 until I got bored of maintaining it and stopped caring, the problems are so rare that I just execute "reset" or close the terminal and open a new one :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876768 Title: Terminal mouse went berserk after lost ssh connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1876768/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876113] Re: Gnome terminal omits cmake bootstrap command from bash history
Yes the space could be relevant, search for "ignorespace" in bash's manual. Also, it's the shell (bash) handling the history, not the terminal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876113 Title: Gnome terminal omits cmake bootstrap command from bash history To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1876113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859123] Re: No global menus (panel-appmenu / dbus) in Firefox 72.0.1
I was severely annoyed by the new behavior of the Alt key (FF 75, Ubuntu 20.04, Unity 7). If I move the window using Alt + mouse drag (which I frequently do), the menu opens up. Subsequent letters I type aren't sent to the webpage, but navigate the menu. Another lone Alt keypress doesn't close it either (well, pressing it closes, but then releasing the key opens the menu bar again), so I have to reach out to Esc to close it. This behavior was unacceptable for me. I first found the workaround of enabling View -> Toolbars -> Menu bar. This way the menu bar is always visible, and the super annoying behavior of Alt is gone. Alas, there's a price to pay in terms of wasted screen real estate. After a bit more searching I found an even better workaround. Instead of the previous one, go to about:config and set ui.key.menuAccessKey to -1. Then the browser needs to be restarted. A lone Alt key (or Alt + moving the window) no longer opens up the menu bar. However, Alt+F, Alt+E etc., as well as F10 still open it up, so all the functionality, in their familiar layout is still conveniently available. It's not as good as Unity integration used to be, but almost as good; to me it's an acceptable minor inconvenience. I hope I could help some people with this comment. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859123 Title: No global menus (panel-appmenu / dbus) in Firefox 72.0.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1859123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872377] Re: No menus in Unity after upgrading to 20.04
See also bug #1859123. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872377 Title: No menus in Unity after upgrading to 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1872377/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871807] Re: Installed fonts are not available for selection
gnome-terminal lists the fonts that are monospace according to pango_font_family_is_monospace(). The font as well as Pango should be examined why this one isn't believed to be a monospace one. That being said, you can still set this font using dconf-editor, by setting /org/gnome/terminal/legacy/profiles:/:/font. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871807 Title: Installed fonts are not available for selection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1871807/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872053] Re: Local mail is never checked
I'd take one step back and ask the question: Why would anyone one a graphical system need to run a terminal emulator in order to get notified about new mail? What if someone uses all kinds of other applications (web browser, document editor, photo viewer, music player...), just not a terminal, why wouldn't they be notified? The right approach is not to fix whatever happens inside the terminal emulator, the right approach is to have a graphical indicator on the desktop. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872053 Title: Local mail is never checked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1872053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872053] Re: Local mail is never checked
It is really, really not the terminal emulator's job to set basic environment variables. It should either be done by the environment in which gnome-terminal is started (e.g. systemd --user), so that the terminal just transparently passes this on; or should be done by the shell initialization files, as in your workaround. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872053 Title: Local mail is never checked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1872053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869769] Re: gnome-terminal regularly becomes corrupted
https://weechat.org/files/doc/devel/weechat_user.en.html#option_weechat.look.eat_newline_glitch: "[eat_newline_glitch] is disabled by default because it can cause serious display bugs" Try the behavior in xterm, too. If it's buggy there too then it clearly has nothing to do with gnome-terminal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869769 Title: gnome-terminal regularly becomes corrupted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1869769/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867746] Re: URL highlighting broken with VTE 0.60
> How did you get terminator to print the following? With Eoan + VTE 0.60, I just execute "terminator" from another terminal emulator. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867746 Title: URL highlighting broken with VTE 0.60 To manage notifications about this bug go to: https://bugs.launchpad.net/terminator/+bug/1867746/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868116] Re: QEMU monitor no longer works
Thanks for this investigation so far! We've opened an upstream VTE issue at https://gitlab.gnome.org/GNOME/vte/issues/222 . We'd appreciate if QEMU developers joined us there. Apparently QEMU uses the "commit" signal in a way that it was not meant to be used, and thus it's unclear what the best solution would be. ** Bug watch added: gitlab.gnome.org/GNOME/vte/issues #222 https://gitlab.gnome.org/GNOME/vte/issues/222 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868116 Title: QEMU monitor no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1868116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1691678] Re: Scrollbars escape the bottom and right side of the Terminal window by 1px
> but dropping the change creates a regression on the Ubuntu session/theme So the situation is: Unpatched gnome-terminal looks perfect on the default GTK theme and on many others, except Ubuntu's. Conclusion: Let's patch gnome-terminal! Wow. I'm wondering: Has anyone considered fixing the Ubuntu theme(s) instead? Oh, sure, in comment 16: "there's a workaround hacked into Yaru" Why is that a workaround, and not a fix? Any why Yaru only and not Ambiance or any other affected Ubuntu theme? Move forward please in this direction, fix (or workaround, whatever) the affected themes so that then you can drop the broken gnome-terminal patch. Or, again: If you believe that your themes as well as your gnome- terminal patch are correct, and other themes are buggy, please provide evidence. If that's not the case, adding a workaround to (and thus breaking) gnome-terminal instead of fixing the broken themes was clearly the wrong thing to do, and should be properly fixed ASAP. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1691678 Title: Scrollbars escape the bottom and right side of the Terminal window by 1px To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1691678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1691678] Re: Scrollbars escape the bottom and right side of the Terminal window by 1px
> It appears we would need a new upstream bug to track this because the old one didn't go anywhere. This is not true. The old one did go somewhere: It examined the behavior and clearly concluded that upstream gnome-terminal is NOT buggy here, it never was. It's one of the Ubuntu patches that introduces the bug. This conclusion was also stated in this thread here. Could you please clarify how you expect upstream gnome-terminal to fix this situation? Meanwhile, this bug is almost 3 years old, and I haven't seen any worthwile comment from any Ubuntu developer trying to track down which of its patches, and which part within that is the culprit. Or if you believe that upstream gnome-terminal is indeed buggy, this bug just doesn't happen to trigger anywhere else, except with your perfect innocent patches, then this claim should be justified with technical arguments, something I haven't seen in this thread yet. And I can't help to notice that this is not the only issue where Ubuntu introduces a regression to the overall gnome-terminal user experience, and then really doesn't care about fixing it. Bug 1770507 is another prominent example, you guys broke something during the feature freeze period(!) of the previous LTS, and still til this day haven't cared about fixing. I'm sad and disappointed to see that the software I've been co- developing for years, putting my passion, heart, and lots and lots of time into, is broken in multiple ways by perhaps the most popular Linux distribution, and its developers just don't care. I don't even know what to think about you pointing fingers at us. Instead, maybe could you Ubuntu devs finally please, pretty please get yourself together and fix at the very least these two bugs that YOU introduced, in time for the just-around-the-corner LTS release? If simply by dropping the patches that introduces the bugs, along with then dropping whatever features those patches add, so it be. Thanks! I firmly believe that Ubuntu should revise its bug prioritizing policy, and handle with much-much higher priority if one of its changes introduces a regression from mainstream. It should be something like: if a regression is found, and not fixed within a week, the patch is automatically dropped. Think about it... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1691678 Title: Scrollbars escape the bottom and right side of the Terminal window by 1px To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1691678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865326] Re: extra spaces on right and bottom border of gnome terminal's scrollbar
*** This bug is a duplicate of bug 1691678 *** https://bugs.launchpad.net/bugs/1691678 ** This bug has been marked a duplicate of bug 1691678 Scrollbars escape the bottom and right side of the Terminal window by 1px -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865326 Title: extra spaces on right and bottom border of gnome terminal's scrollbar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1865326/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864364] Re: Possible Regession: PCRE2 fails to match regex
Upstream fix: https://vcs.pcre.org/pcre2?view=revision=1228 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864364 Title: Possible Regession: PCRE2 fails to match regex To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcre2/+bug/1864364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864364] Re: Possible Regession: PCRE2 fails to match regex
Upstream report: https://bugs.exim.org/show_bug.cgi?id=2531 ** Bug watch added: bugs.exim.org/ #2531 http://bugs.exim.org/show_bug.cgi?id=2531 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864364 Title: Possible Regession: PCRE2 fails to match regex To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcre2/+bug/1864364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856438] Re: auto suggest previously used commands
This should be a feature request against the command line shell, not the terminal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856438 Title: auto suggest previously used commands To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1856438/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850621] Re: zoom sets wrong window size in fullscreen mode
*** This bug is a duplicate of bug 1849285 *** https://bugs.launchpad.net/bugs/1849285 This is fixed in official gnome-terminal 3.34.1, which is on its way to appear as an eoan update. So let me mark this as duplicate. ** This bug has been marked a duplicate of bug 1849285 [SRU] 3.34.2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850621 Title: zoom sets wrong window size in fullscreen mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1850621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849090] Re: Autocompletion does not work correctly with special signs
Autocompletion is done by the shell and its configs, not by the terminal. ** Also affects: bash-completion (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849090 Title: Autocompletion does not work correctly with special signs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1849090/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847850] Re: Update vte2.91 to 0.58.2
Filed bug #1848156, thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847850 Title: Update vte2.91 to 0.58.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte2.91/+bug/1847850/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847850] Re: Update vte2.91 to 0.58.2
Filed #1848156, thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847850 Title: Update vte2.91 to 0.58.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte2.91/+bug/1847850/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848156] [NEW] Update gnome-terminal to 3.34.1
Public bug reported: Please update to gnome-terminal 3.34.1 (or .2) for eoan. Or, at least, cherry-pick this trivial fix: https://gitlab.gnome.org/GNOME/gnome- terminal/commit/2cbc9e6b9be7f4d6b2d92b40e37ec687d36ce98d A change in GTK triggered a bug in Terminal causing a pretty bad user experience. A fullscreened terminal under Wayland doesn't retain its fullscreen status at certain operations, such as opening/closing a second tab, or zooming. Opening a second tab actually further grows the window as the tab bar appears, so that the bottom 1 or 2 text rows become invisible (out of screen). This issue was fixed in 3.34.1, along with two other minor issues and many translation updates. 3.34.2 brings another translation update only. Ubuntu usually aims to ship GNOME x.y.1. I assume there was no particular reason for not updating GNOME Terminal to .1 in this cycle, other than probably lack of time. I sincerely hope that the aforementioned UX regression convinces you to release a last minute fix for 19.10, or an update shortly afterwards. Thanks a lot! ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-terminal 3.34.0-1ubuntu2 [modified: usr/bin/gnome-terminal usr/libexec/gnome-terminal-server usr/share/applications/org.gnome.Terminal.desktop usr/share/glib-2.0/schemas/org.gnome.Terminal.gschema.xml usr/share/icons/hicolor/scalable/apps/org.gnome.Terminal.svg usr/share/metainfo/org.gnome.Terminal.appdata.xml] ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Tue Oct 15 10:42:06 2019 InstallationDate: Installed on 2016-11-09 (1069 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to eoan on 2019-09-08 (36 days ago) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848156 Title: Update gnome-terminal to 3.34.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1848156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847850] Re: Update vte2.91 to 0.58.2
Just wondering, Jeremy, in the opening report you said > This update is required to update gnome-terminal to 3.34.2 but there's no gnome-terminal update in progress, is there? gnome-terminal 3.34.1 fixes a problem with fullscreen terminals not staying fullscreen at certain operations like font size change. 3.34.2 is nothing (just a translation update). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847850 Title: Update vte2.91 to 0.58.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte2.91/+bug/1847850/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847850] Re: Update vte2.91 to 0.58.2
0.58.1 and 0.58.2 each fix a crash. So indeed it would be great if you could make an exception and update these packages, thanks! ** Summary changed: - Update vte2.91 to 2.58.2 + Update vte2.91 to 0.58.2 ** Description changed: I'm filing a bug since we are now in Final Freeze for Ubuntu 19.10 - vte 2.58.2 is a new release in the stable 2.58 series aligned with GNOME + vte 0.58.2 is a new release in the stable 0.58 series aligned with GNOME 3.34. There is a standing microrelease exception for GNOME. https://wiki.ubuntu.com/StableReleaseUpdates#GNOME https://gitlab.gnome.org/GNOME/vte/compare/0.58.0...0.58.2 This update is required to update gnome-terminal to 3.34.2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847850 Title: Update vte2.91 to 0.58.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte2.91/+bug/1847850/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846255] Re: No cursor in gnome-terminal 3.34.0-1ubuntu2 (eoan)
> Cursor color: checked, same colors Well, if cursor color is the same as the default color then it is requested to be invisible. What you need for the cursor color is something very different from the defaults (e.g. the two colors swapped). Nitpicking: You shouldn't need to restart gnome-terminal, it should pick up the preference changes immediately. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846255 Title: No cursor in gnome-terminal 3.34.0-1ubuntu2 (eoan) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1846255/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846255] Re: No cursor in gnome-terminal 3.34.0-1ubuntu2 (eoan)
Could you please execute this command? Do you see a cursor while it is running? echo -ne '\e[?25h\e]112\e\\'; sleep 1000 If not, then while the previous command is still running: Please open gnome-terminal's preferences, click on your profile in the left-side bar. Disable cursor blinking, and try all three available cursor shapes. Does any of them appear? Still while that command is running: Go to the Colors tab of this preference, is Cursor color enabled here? (Is it perhaps set to the same color as your background?) Does changing that setting make any difference? What if you set a custom cursor background color? Can you recall when was the last time the cursor showed up correctly for you? (Like, about 1 day ago, about 1 week ago...?) Was that on disco, or eoan beta? Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846255 Title: No cursor in gnome-terminal 3.34.0-1ubuntu2 (eoan) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1846255/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845737] Re: Missing dependency on lenses
I forgot to explicitly say: The required packages, which should be listed in the Depends field, are: - unity-lens-applications - unity-lens-files -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845737 Title: Missing dependency on lenses To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-tweak-tool/+bug/1845737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845737] [NEW] Missing dependency on lenses
Public bug reported: For some (unknown) reason, my unity-lens-* packages got uninstalled. Trying to start unity-tweak-tool from a terminal under a Unity 7 session gives this error in the terminal: Error: schema com.canonical.Unity.ApplicationsLens not installed and this in a popup window: Schemas missing [<- this is the window title] The following schema is missing com.canonical.Unity.ApplicationsLens In order to work properly, Unity Tweak Tool recommends you install the necessary packages And if I install the requested "applications" lens and restart unity- tweak-tool, the same error is presented for the "files" lens instead. Either the package should depend on these two lens packages, and the wording "recommends" in the error message should be changed to "requires" (just in case someone manages to break those packages); or according to the wording of "recommends" these packages should be optional dependencies and their lack should not result in startup failure. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: unity-tweak-tool 0.0.7+-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0 Uname: Linux 5.3.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Sat Sep 28 00:11:10 2019 InstallationDate: Installed on 2016-11-09 (1051 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: unity-tweak-tool UpgradeStatus: Upgraded to eoan on 2019-09-08 (18 days ago) ** Affects: unity-tweak-tool (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845737 Title: Missing dependency on lenses To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-tweak-tool/+bug/1845737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 562130] Re: Selecting an RTL language should install RTL capable terminal emulator
GNOME Terminal 3.34 (as well as all other terminals using VTE 0.58) support RTL. These versions appear in Ubuntu 19.10 Eoan Ermine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/562130 Title: Selecting an RTL language should install RTL capable terminal emulator To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/562130/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843880] [NEW] GtkSpinButton's context menu changes the width of '+'
Public bug reported: GtkSpinButton consists of a (typically numeric) input field, followed by a '-' and finally a '+' sign. The width of the '+' sign shrinks a little bit when you open the right-click context menu of the input field. It shouldn't, it should have a constant width. Happens with Ubuntu's old default Ambiance and Radiance themes. Does not happen with Ubuntu's new default Yaru, or with GTK's default Adwaita. Example: Open gnome-terminal, right click on its terminal canvas, choose Preferences. You're taken to the profile's Text tab which contains four such widgets. Right-click on one of these input fields, e.g. on "80" for the initial number of columns. In addition to the context menu appearing, the '+' button becomes narrower, and thus the label on its right (e.g. "columns") shifts to the left. For some of the spinbuttons (the ones that stretch the window) the entire window also shrinks. Dismiss the context menu and it goes back to its previous width. (This is similar to former bug 1740709.) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: light-themes 19.04-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Fri Sep 13 11:48:51 2019 InstallationDate: Installed on 2016-11-09 (1037 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: Upgraded to eoan on 2019-09-08 (4 days ago) ** Affects: ubuntu-themes (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan visual-quality ** Tags added: visual-quality -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843880 Title: GtkSpinButton's context menu changes the width of '+' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1843880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843872] Re: libexec migration incomplete
> What the script does, since you ask, Sorry for the loose phrasing. I was aware of the global picture, just wasn't sure (and was lazy to investigate) when exactly a bug would be triggered, i.e. when that code would be reached, which you answered: > It is broken if you pass --app-id Thanks for the libexec migration by the way, it's one less thing for me to worry about (Ubuntu doing something differently than mainstream, and if I forget to pass --libexec= then I end up with a server here and a server there and who knows if the right one is started up, it's a source of all kinds of confusions... you must know the feeling. Anyway, it's probably just me, most users don't care about this change :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843872 Title: libexec migration incomplete To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1843872/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843872] [NEW] libexec migration incomplete
Public bug reported: Debian/Ubuntu package of gnome-terminal 3.34.0 moved the server binary from /usr/lib/gnome-terminal to /usr/libexec. The Ubuntu package ships a wrapper script as /usr/bin/gnome-terminal. This one still looks for the server at its old location in spawn_terminal_server(). It's unclear to me what this wrapper script exactly does, and how/why it still manages to successfully start up gnome-terminal (probably in a different way than it intends to). ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843872 Title: libexec migration incomplete To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1843872/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843197] Re: Time reported for having downloaded the packages is way off
** Also affects: apt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843197 Title: Time reported for having downloaded the packages is way off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1843197/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843197] [NEW] Time reported for having downloaded the packages is way off
Public bug reported: It took about 30 minutes for me to download the packages for a distro upgrade, yet it reports it took 6 seconds. I'm upgrading from Disco to Eoan test version, using the command sudo do-release-upgrade -d Excerpt from the output: 7 packages are going to be removed. 81 new packages are going to be installed. 1940 packages are going to be upgraded. You have to download a total of 1,964 M. This download will take about 4 hours with a 1Mbit DSL connection and about 3 days 4 hours with a 56k modem. [...] Fetching Get:1 http://hu.archive.ubuntu.com/ubuntu eoan/main amd64 locales all 2.30-0ubuntu1 [3,870 kB] Get:2 http://hu.archive.ubuntu.com/ubuntu eoan/main amd64 libc6-dbg amd64 2.30-0ubuntu1 [5,736 kB] [...] Get:2020 http://hu.archive.ubuntu.com/ubuntu eoan/universe amd64 xawtv-plugins amd64 3.106-1 [51.6 kB] Get:2021 http://hu.archive.ubuntu.com/ubuntu eoan/main amd64 xbrlapi amd64 5.6-11ubuntu2 [63.0 kB] Fetched 1,964 MB in 6s (1,094 kB/s) The last line is faulty. The actual time was maybe about 30 minutes, not 6 seconds :-D Note that the two other values shown in the last line, namely the overall size and the average download speed seem to be correct, and dividing these two indeed gives about 30 minutes. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: ubuntu-release-upgrader-core 1:19.04.16.6 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity:Unity7:ubuntu Date: Sun Sep 8 22:48:32 2019 InstallationDate: Installed on 2016-11-09 (1032 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to disco on 2019-09-08 (0 days ago) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco dist-upgrade third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843197 Title: Time reported for having downloaded the packages is way off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1843197/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 310053] Re: Devanagari text rendered incorrectly in VTE apps
VTE (libvte-2.91-0) version 0.56 mostly addresses this issue, spacing marks are now combined as desired with the preceding base letter. (Dotted circles still might be displayed around line wraps, as well as under the rectangle cursor. For the latter problem, a workaround is to choose a different cursor shape.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/310053 Title: Devanagari text rendered incorrectly in VTE apps To manage notifications about this bug go to: https://bugs.launchpad.net/vte/+bug/310053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1566437] Re: Scrolling randomly stops working
> I found a hacky workaround - add this to your $PS1: The workaround of resetting relevant settings from the prompt has already been mentioned – although without showing a concrete example. > Given how randomly it happens, I believe there is a real bug in Terminator I'm about 99.999% sure that this is _not_ a bug in Terminator (VTE). It is believed to properly execute the relevant escape sequences it receives. (Can you reproduce the issue with xterm, urxvt, konsole...? I bet you can.) > but if you want to force the broken state, just open 'mc' and run 'pkill mc' from another terminal, your scrolling will be broken. Yup, in this case mc asks the terminal to switch to a special mode, and due to getting killed, it does not ask the terminal to leave that mode. Nothing new here, exactly what has already been concluded in this thread. > run e.g 'mc > trace.txt'. Then type 'exit', hit return, and mc will quit. You will get all the escape sequences from mc in trace.txt to inspect. Can you really reproduce the issue this way? Because you don't kill mc now, but exit it cleanly. > to report it as a terminator bug Unless you have firm evidence that this is a terminator (or VTE) bug, please don't spam its bugtracker with something that's most likely an issue elsewhere. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1566437 Title: Scrolling randomly stops working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1566437/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835224] Re: gnome-terminal drops pam_group config
> Starting a gnome-terminal from this terminal Even executing "gnome-terminal" from an xterm goes through dbus/systemd. "gnome-terminal" is just a controlling client that asks systemd to start up a server which then displays the window and does all the rest. Don't ask why the architecture is like this, I don't know. But gnome- terminal definitely doesn't do anything with groups, nor asks dbus/systemd/whatever to tamper with the groups. The issue is probably in systemd, starting up gnome-terminal (and presumably any other app that it starts up) with the wrong groups. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835224 Title: gnome-terminal drops pam_group config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1835224/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835224] Re: gnome-terminal drops pam_group config
gnome-terminal itself doesn't do any authentication / PAM stuff. It's probably an issue with `systemd --user` which launches gnome-terminal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835224 Title: gnome-terminal drops pam_group config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1835224/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263822] Re: RTL (right to left) support in terminal (BiDi)
GNOME Terminal 3.33.3 (VTE 0.57.3) implements BiDi support, according to the proposal at https://terminal-wg.pages.freedesktop.org/bidi/ . In alignment with Diego's comments and my responses to them, it implements multiple modes. Shuffling the characters according to the BiDi algorithm is enabled by default, this is required for simple utilities such as "echo", "cat" and friends. An escape sequence can turn off BiDi in the terminal, to be used if BiDi is performed by the application running inside. As mentioned, this won't magically make fullscreen apps (e.g. "mc") BiDi-aware, it's impossible without adding this feature to all those applications. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/263822 Title: RTL (right to left) support in terminal (BiDi) To manage notifications about this bug go to: https://bugs.launchpad.net/vte/+bug/263822/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1691678] Re: Scrollbars escape the bottom and right side of the Terminal window by 1px
I confirm the previous suspicion: This is _not_ an upstream bug. Upstream gnome-terminal draws the scrollbar perfectly. This bug is introduced by one of the Ubuntu patches. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1691678 Title: Scrollbars escape the bottom and right side of the Terminal window by 1px To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1691678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829375] Re: Drop libvte9 suggestion
I've fired up Geany, and clicked on Terminal in the bottom left corner. The presented terminal is libvte-2.91-0, as confirmed by `echo $VERSION` reporting its version number. Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896101 ** Bug watch added: Debian Bug tracker #896101 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896101 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829375 Title: Drop libvte9 suggestion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geany/+bug/1829375/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728241] Re: stjerm project is abandoned(unmaintained) upstream -- please remove from archives
Thanks guys for having addressed this removal! I just came here to report the same request. > What bugs, specifically, do you believe justify this package's removal from the archive? Pretty much the entire set of bugs that have been fixed in VTE in the last 8 years :-) including potential data leakage by writing the scrollback data unencrytped to disk. > it has no obsolete library dependencies It uses an ancient version of VTE which I just asked to get removed in bug 1829377. There are about a dozen VTE-based emulators shipped by Ubuntu, IMO it's already too much. I see no point in carrying one that couldn't catch up with API changes for 8 years. I'm just commenting to confirm that you made the right choice by removing stjerm, thanks again! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728241 Title: stjerm project is abandoned(unmaintained) upstream -- please remove from archives To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/stjerm/+bug/1728241/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829377] [NEW] Remove this package
Public bug reported:
Please remove the ancient GTK2-based vte aka. libvte9{,-common} from
Eoan.
Upstream version has been unmaintained for about 8 years, development
continued in the GTK3 branch (vte2.91 aka. libvte-2.91-0).
Geany is the only package referring to it, and it also does incorrectly
since it already uses GTK3, see bug 1829375.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: libvte9 1:0.28.2-6
ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
Uname: Linux 5.0.0-15-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Thu May 16 13:41:04 2019
InstallationDate: Installed on 2016-11-09 (917 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
SourcePackage: vte
UpgradeStatus: Upgraded to disco on 2019-04-10 (35 days ago)
** Affects: vte (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug disco
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829377
Title:
Remove this package
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vte/+bug/1829377/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829375] [NEW] Drop libvte9 suggestion
Public bug reported: Geany recommends to install libvte9. Since Bionic, Geany has been compiled against GTK3. libvte9 uses GTK2. Hence I'm pretty sure geany cannot make any use of it. Please remove this outdated suggestion, or replace by the GTK3 based libvte-2.91-0 if geany can use this latter one (which I'm not sure about). Thanks! ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: geany 1.34.1-1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu May 16 13:34:23 2019 InstallationDate: Installed on 2016-11-09 (917 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: geany UpgradeStatus: Upgraded to disco on 2019-04-10 (35 days ago) ** Affects: geany (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829375 Title: Drop libvte9 suggestion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geany/+bug/1829375/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829373] [NEW] Outdated description says GTK2
Public bug reported: The package's (and some of the subpackages') description says: "It is using only the GTK2 toolkit and therefore you need only the GTK2 runtime libraries to run Geany." Since Bionic it's been compiled against GTK3, and accordingly, depends on libgtk-3-0. Please update the description, thanks! ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: geany 1.34.1-1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu May 16 13:29:59 2019 InstallationDate: Installed on 2016-11-09 (917 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: geany UpgradeStatus: Upgraded to disco on 2019-04-10 (35 days ago) ** Affects: geany (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829373 Title: Outdated description says GTK2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geany/+bug/1829373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1740709] Re: GtkSpinButton's '+' changes width if insensitive
Can't reproduce on disco. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1740709 Title: GtkSpinButton's '+' changes width if insensitive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1740709/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824438] Re: libvte: syntax error in /etc/profile.d/vte-2.91.sh
What problem did you experience at the first place? What's your goal when you execute the mentioned command? vte-2.91.sh was written for bash and zsh. You execute it with sh (dash). Due to -n, the commands are not executed and thus it skips the bash/zsh check and continues. Then it fails on a bash/zsh specific syntax. This script is not meant to be executed manually, especially not with -n. As such, I see no problem whatsoever. > I believe that this problem leads to the creation of a file called 'config-err' in my /tmp folder. I find it pretty unlikely. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824438 Title: libvte: syntax error in /etc/profile.d/vte-2.91.sh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte2.91/+bug/1824438/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818991] Re: Drop pcre2-version-update.patch
The patch itself is misleadingly still present inside tilix_1.8.9-1build1.debian.tar.xz. It's not mentioned in 'series' though, which I believe means it's not applied? This might have confused OP and me as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818991 Title: Drop pcre2-version-update.patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tilix/+bug/1818991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)
Please do not forget to remove the pcre patch from Tilix, see https://bugs.launchpad.net/ubuntu/+source/tilix/+bug/1818991 - thanks! ** Also affects: tilix (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817438] Re: Error displaying icon for preference menu in title bar
Most likely a duplicate of bug 1770507. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817438 Title: Error displaying icon for preference menu in title bar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1817438/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1816171] Re: Show menubar by default in new terminals has no effect
Thanks for the report! I can confirm this; forwarded to: https://gitlab.gnome.org/GNOME/gnome-terminal/issues/81 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816171 Title: Show menubar by default in new terminals has no effect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1816171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797744] Re: Mouse scrolling no longer moves between tabs in gnome-terminal 3.30
** Summary changed: - Mouse scrolling no longer moves between tabs in gnome-terminal 2.30 + Mouse scrolling no longer moves between tabs in gnome-terminal 3.30 ** Description changed: - In gnome-terminal 2.28 and earlier, scrolling with the mouse cursor over + In gnome-terminal 3.28 and earlier, scrolling with the mouse cursor over the tab bar switched between tabs. This seems to be broken in cosmic's - 2.30. + 3.30. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797744 Title: Mouse scrolling no longer moves between tabs in gnome-terminal 3.30 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1797744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807773] [NEW] Crash in set_blink_settings()
Public bug reported: vte 0.54.0 to 0.54.2 suffers from a potential crash if the user closes a terminal tab/window in gnome-terminal (or any other vte-based app) and then modifies the cursor blinking settings. Mainstream release 0.54.3 fixes this issue. See https://gitlab.gnome.org/GNOME/vte/issues/77 and https://bugzilla.redhat.com/show_bug.cgi?id=1657512 for details. Could you please release a fix for Cosmic? (And while at it, consider addressing bug 1804457 too?) Thanks! ** Affects: vte2.91 (Ubuntu) Importance: Undecided Status: New ** Tags: cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1807773 Title: Crash in set_blink_settings() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte2.91/+bug/1807773/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790100] Re: unable to write ~ and ^ chars in the terminal
Please understand: It's not that we (vte and gnome-terminal developers) don't want to hear about it. We've heard about it and we are pretty certain that this is a bug somewhere elsewhere. Vte's and gnome- terminal's source code has absolutely no sign of treating ^ or any other similar simple character specially. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790100 Title: unable to write ~ and ^ chars in the terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte2.91/+bug/1790100/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798481] Re: org.gnome.desktop.interface.cursor-blink-timeout not honored
Thanks for the investigation! In the mean time I've tried xfce, icewm and windowmaker – /org/gnome/desktop/interface/cursor-blink* weren't used by VTE in any of them, some hardcoded defaults were used. I guess some dconf or gsettings daemon needs to be running to have the required binding in place (not sure). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798481 Title: org.gnome.desktop.interface.cursor-blink-timeout not honored To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte2.91/+bug/1798481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798481] Re: org.gnome.desktop.interface.cursor-blink-timeout not honored
> cursor-blink-time: 1200 > cursor-blink-timeout: 1 > time=463 timeout=10 Oops, time should also match and it doesn't. Can you confirm that blinking is pretty fast for you, that is, the duration of an entire cycle (on + off phases) is a bit less than half a second (463 ms, rather than 1.2 seconds)? As seen at https://gitlab.gnome.org/GNOME/vte/blob/0.54.1/src/widget.cc#L285, VTE refers to the widget settings' "gtk-cursor-blink" and friends properties, which are somehow mapped to gsetting's /org/gnome/desktop/interface/cursor-blink and friends – or well, in your case, mapped probably somewhere else. It'd take help from a GTK+ expert or investigating GTK+'s source to check this mapping, to figure out where it takes these values from if not from gsettings's /org/gnome/desktop/interface/, and how that can be configured. What desktop system do you have? Maybe if let's say you use Mate then these values might come from /org/mate/... or so, I'm wondering. Could you do a "dconf dump /" and look for 463 in its output, to have a clue where this number comes from, assuming that it comes from dconf at all. And see if changing that value takes effect in VTE. > Do gedit and pidgin have some relationship with vte? They all use GTK+ and perhaps even some higher level GNOME libraries. Other than, not much. Gedit also has a VTE plugin but that's most likely irrelevant, and Pidgin doesn't have such. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798481 Title: org.gnome.desktop.interface.cursor-blink-timeout not honored To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1798481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798481] Re: org.gnome.desktop.interface.cursor-blink-timeout not honored
VTE does have code in place to support these variables and they work for me. No need for reboot, not even to restart gnome-terminal, it should pick up the change immediately. It stops blinking the cursor when the focus is lost, and restarts blinking it when the terminal is focused again. Are you sure this is not what confused you? What are the exact values of your cursor-blink related values in dconf? Could you please download VTE tarball (or git), and try the test app with debug options, like: tar xf vte-0.54.1.tar.xz cd vte-0.54.1 ./configure --enable-debug make VTE_DEBUG=misc ./src/app/vte-2.91 Does it print a line beginning with "Cursor blinking settings"? How does it look like? If you modify the dconf settings, does such a line appear again? Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798481 Title: org.gnome.desktop.interface.cursor-blink-timeout not honored To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1798481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796422] Re: Crash at encoding change
Thanks guys! :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796422 Title: Crash at encoding change To manage notifications about this bug go to: https://bugs.launchpad.net/vte/+bug/1796422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743373] Re: Combobox arrow and color are inverted
I can confirm the issue is fixed in Cosmic beta. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743373 Title: Combobox arrow and color are inverted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1743373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796422] [NEW] Crash at encoding change
Public bug reported: Using vte 0.54.0: Open gnome-terminal, and use its Terminal -> Set Character Encoding menu to switch to another encoding. Switch back, then again to something different. gnome-terminal crashes. Mainstream vte 0.54.1 fixes this issue. Could you please sync the upgraded package from Debian (or at least cherry-pick this fix from upstream git)? Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910208 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libvte-2.91-0 0.54.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Sat Oct 6 00:47:27 2018 InstallationDate: Installed on 2016-11-09 (694 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: vte2.91 UpgradeStatus: Upgraded to cosmic on 2018-09-25 (9 days ago) ** Affects: vte2.91 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796422 Title: Crash at encoding change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte2.91/+bug/1796422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795745] [NEW] Combobox opens at wrong vertical position
Public bug reported: When a combobox is opened, the list of entries is expected to be positioned so that the currently selected one is exactly where that value was shown before the list was opened. See the two screenshots demonstrating the problem. Note that even though the mouse pointer isn't visible, I did not move the mouse between making these two screenshots. It was at the top part of the closed combobox. So when I clicked to open it, it automatically focused the previous entry. Clicking once again would choose that entry, modifying my settings. Expected: if I click again without moving the mouse, my settings shouldn't change. It seems that the height of the additional top/bottom paddings with the rounded corners isn't properly taken into account. (The screenshots were taken in gnome-terminal's preferences window, but this is irrelevant.) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: yaru-theme-gtk 18.10.5 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Tue Oct 2 23:24:58 2018 InstallationDate: Installed on 2016-11-09 (691 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: yaru-theme UpgradeStatus: Upgraded to cosmic on 2018-09-25 (6 days ago) ** Affects: yaru-theme (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795745 Title: Combobox opens at wrong vertical position To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1795745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795745] Re: Combobox opens at wrong vertical position
** Attachment added: "Before opening - good so far" https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1795745/+attachment/5196123/+files/yaru-combobox-1.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795745 Title: Combobox opens at wrong vertical position To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1795745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795745] Re: Combobox opens at wrong vertical position
** Attachment added: "After opening - list is mispositioned" https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1795745/+attachment/5196124/+files/yaru-combobox-2.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795745 Title: Combobox opens at wrong vertical position To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1795745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790317] Re: Crash with vte-0.54
Debian report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909744. ** Bug watch added: Debian Bug tracker #909744 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909744 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790317 Title: Crash with vte-0.54 To manage notifications about this bug go to: https://bugs.launchpad.net/sakura/+bug/1790317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791373] Re: [FFe] Update gnome-terminal to 3.30.0 and vte to 0.54
Hi guys, - Due to a change in vte-0.54 around the child-exited signal, unfortunately lxterminal (LP: #1794440) and sakura (LP: #1790317) now crash when a tab is closed by clicking on the X button. Luckily, a fix is available for both of them. Could you please make sure to apply those fixes? - I know that normally you update to the .1 minor release, I'd just like to point out that vte-0.54.1 fixes a segfault around encoding switches, so please indeed make sure not to miss this update. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791373 Title: [FFe] Update gnome-terminal to 3.30.0 and vte to 0.54 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1791373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790317] Re: Crash with vte-0.54
** Also affects: sakura (Ubuntu) Importance: Undecided Status: New ** Tags added: cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790317 Title: Crash with vte-0.54 To manage notifications about this bug go to: https://bugs.launchpad.net/sakura/+bug/1790317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1794440] [NEW] Crash with vte-0.54 when closing a tab with the X button
Public bug reported: Open a new tab, and close any tab by clicking on the X button. As of vte-0.54, lxterminal crashes. Upstream bug and fix: https://github.com/lxde/lxterminal/issues/61 Mainstream release 0.3.2 fixes the bug, this is already packaged in Debian unstable. Please backport the fix, or sync 0.3.2 from Debian; thanks! ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: lxterminal 0.3.1-2ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Wed Sep 26 09:35:44 2018 InstallationDate: Installed on 2016-11-09 (685 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: lxterminal UpgradeStatus: Upgraded to cosmic on 2018-09-25 (0 days ago) ** Affects: lxterminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794440 Title: Crash with vte-0.54 when closing a tab with the X button To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxterminal/+bug/1794440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791967] Re: Shortcut for "Hide and Show Menubar" does not work
Thanks for the report! I've forwarded it upstream: https://gitlab.gnome.org/GNOME/gnome-terminal/issues/33. (Note that this shortcut is disabled by default, not assigned to F10.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791967 Title: Shortcut for "Hide and Show Menubar" does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1791967/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791337] Re: Terminal should prompt for confirmation before pasting text containing newlines
> I don't think having to hit Enter when you paste several lines [...] would be a great annoyance You have the shell as use case in your mind. Other use cases include e.g. pasting to a text editor. Having to hit Enter there would be quite an annoyance. > but if it was for someone, there would always be the setting to disable it. And that's the problematic part. I'd like to have it disabled when running the text editor, but have some confirmation when pasting to the shell. > Does that address the case where I actually do want to paste a sequence of commands and run them? Yes. You just hit Enter. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791337 Title: Terminal should prompt for confirmation before pasting text containing newlines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1791337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791337] Re: Terminal should prompt for confirmation before pasting text containing newlines
I'm not affiliated with Ubuntu, so I probably shouldn't be the one warning you, but your style is unacceptable, no matter how serious issue you report. gnome-terminal could warn you before pasting a newline. It could offer to disable that warning, in which case most users would do so, falling back to the problem you reported. Or it could not offer such possibility, making intentional multi-line pastes annoying as hell. I believe the proper solution is to enable bracketed paste mode in your shell (which requires a newer Ubuntu, shipping bash-4.4). Please reassign (or report a new bug) against Ubuntu's bash or readline package to enable this feature by default. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791337 Title: Terminal should prompt for confirmation before pasting text containing newlines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1791337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1666264] Re: FFe: Update gnome-terminal to 3.24 and vte to 0.48
Fix: "I have to admit I don't know what this regex *flag* is for..." -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1666264 Title: FFe: Update gnome-terminal to 3.24 and vte to 0.48 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1666264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1666264] Re: FFe: Update gnome-terminal to 3.24 and vte to 0.48
> So the cause is that the MULTILINE flag is just that not set during compilation? Compilation of the regex when running tilix, not compilation of the source code. I have to admit I don't know what this regex is for, and whether required in unpatched vte or not. If tilix is warning-free with unpatched vte then probably Ubuntu should just simply remove this line that emits the warning. (Well, Ubuntu should really move pcre2 to main and drop this entire patch, but that's a different story.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1666264 Title: FFe: Update gnome-terminal to 3.24 and vte to 0.48 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1666264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720213] Re: Word moving with left-arrow-ctrl broken in wayland
It's indeed an opinion, but my one matches Merlijn's (Merlijn, I'd appreciate if you opened a bug according to Daniel's suggestion (does it really belong to mutter, rather than some more core wayland component?)). In most software, Ctrl+Arrow walk the cursor faster than the modifier- less Arrow key. I might press and hold the arrow key, and then realize it's going to take a bit too long and want make it faster. It's an obvious an intuitive reaction to press Ctrl as well, or the other way around, to release Ctrl but leave the Arrow pressed when I'm about to reach my destination and want to slow down. This is pretty similar to how typically holding the Shift speeds up walking in many games - you won't find a game where you have to stop walking for a sec do to this. The new behavior is not just counterintuitive, but if one gets used to it then also still slower than the old one. Even when someone is fully used to this new behavior, having to release the Arrow and press it again later is a loss of time, partially because of the speed of our fingers, and partially beucase the repetition delay between the first and second emitted keystroke has to elapse again. This is the kind of usability issue that can easily frequently increase the user's frustration level, by a tiny little bit every time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720213 Title: Word moving with left-arrow-ctrl broken in wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1720213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1666264] Re: FFe: Update gnome-terminal to 3.24 and vte to 0.48
> As you can see both arguments itself are true. The first two arguments you printed are bitmasks, it doesn't make sense to directly interpret them as boolean. > But why is a "bitwise and" used in g_warn_if_fail()? Because that's what it wants to do: warn if the MULTILINE flag isn't set, regardless of the other flags. > So what I did and propose is to replace the "bitwise and" with a "logical or". This is semantically absolutely incorrect. The second argument is a nonzero constant, logically OR-ing would always give logical TRUE, hence the "warn if fail" not executed. You could just as well remove the entire line, that'd be okay. --- Let's take one step back. Comment #17 says "This is still breaking tilix functionality and polluting the logs" but the tilix bug linked from #19 only talks about the warnings. Maybe I'm missing something, but is Tilix's actual behavior broken? If so, how exactly, and where's the tracking Ubuntu bug of that? Or are we only talking about annoying but harmless warnings? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1666264 Title: FFe: Update gnome-terminal to 3.24 and vte to 0.48 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1666264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720213] Re: Word moving with left-arrow-ctrl broken in wayland
> Only a few applications don't adhere to this, even on Wayland. That's probably due to the others still using the X11 compatibility layer Xwayland. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720213 Title: Word moving with left-arrow-ctrl broken in wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1720213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734817] Re: keyboard: alt-F doesn't open File menu
gnome-terminal is a long complicated story (see the link from comment 5 if you care), BUT one of the 3 or so reasons we removed the global menu mnemonics was that even if we enabled them, Alt+F didn't work. I can no longer recall for sure, but I think Alt+F stopped working for us when we ported to GMenu (the first link here from comment 3). 18.04, Unity 7, gedit: Alt+F does not work for me, Alt+E etc. do work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734817 Title: keyboard: alt-F doesn't open File menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1734817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785444] Re: Can't enable menubar mnemonics for gnome-terminal in 18.04 under Unity
gnome-terminal switched to using the GMenu architecture in https://gitlab.gnome.org/GNOME/gnome-terminal/commit/0820b3853, which is supposed to be superior to the old one with Unity's menuproxy. It suffers from new bugs and limitations though. This change, as far as I recall, already affected how the mnemonics work in the global menu (I think they broke to some extent which we attempted to fix). Plus, mnemonics weren't working at many other places of gnome- terminal where they should've (e.g. Find or Preferences dialogs) which we aimed to fix too. Re-enabling them for the menubar in Unity, using the new architecture, still resulted in Alt+F not working (the others working though), and had other downsides too. See also https://bugzilla.gnome.org/show_bug.cgi?id=792312 comment 11 onwards for a bug which we tried to work around. In the end, if my memories are correct, we decided not support them for Unity, it was a compromise we had to make because we couldn't get everything right. Some rationale to back up this decision were: - it's no longer Ubuntu's default desktop, so not high priority; - enabling Alt+F etc. conflicts with their use inside the terminals, which most people want; - you can still easily focus the menu using Alt+F10. My memories are pretty vague and the story was quite complex. See https://gitlab.gnome.org/GNOME/gnome-terminal/commit/f1c46cb52 and its linked bug for the long discussions. > Is there a way to compile terminal differently to get the with- mnemonic version instead of the without-mnemonic version, if it's not possible for on-the-fly switching to be enabled? Both versions are always compiled in, and selected based on the mentioned dconf setting, IIRC overridden to the non-mnemonic one when Unity is detected (I'm not sure again). ** Bug watch added: GNOME Bug Tracker #792312 https://bugzilla.gnome.org/show_bug.cgi?id=792312 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785444 Title: Can't enable menubar mnemonics for gnome-terminal in 18.04 under Unity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1785444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780501] Re: Traceback calling Vte.Terminal.feed_child()
Hey guys, Hope I'm not speaking up too late. It's indeed a bit nasty situation we're in, and I am also a little bit responsible for this. When updating the PCRE fixes for 0.52 I focused on the actual work, and ignored (just ported blindly in "autopilot" mode) the annotation changes. I should've stopped and asked "what the heck is this?". Sorry for that! In the mean time vte itself is also somewhat responsible for the mess by silently fixing its python bindings in backwards incompatible ways. (Mainstream 0.52 fixed feed_child() not to take a third parameter, it was broken before and required an explicit length. The same happened to feed_child_binary() in 0.46 which may have been the reason for someone to (accidentally or intentionally) sneak in the revert of this to the PCRE patch.) So a "faulty" vte update has already been released for bionic, breaking 4 packages we're aware of (ubuntu-release-upgrader, terminator, guake, cubic). Maybe there's one or two more at most, but I don't think so. On the other hand, this change "fixes" vte to be like mainstream, which is a huge advantage for anyone wishing to manually install vte-based software. I assume you don't intend to carry these changes forever. Brian Murray from comment 10: > I agree that having downstream API differences is bad and that it shouldn't be fixed for cosmic I can only parse this sentence assuming a typo: "*should* be fixed for cosmic", am I right, or what am I missing? ubuntu-release-upgrader has already been fixed to cope with either signatures if I understand correctly, and the other three will also need to be fixed eventually. At this point, if it was dozens of packages that broke, I'd agree with reverting the vte change. If vte received a broken change, I'd agree with reverting it. However, vte actually received a fix, which happened to break 4 apps that were strictly speaking broken (to adjust to broken vte), and they'll need to get fixed anyway. In this situation I find it much clearer to escape forward rather than retreat, and just fix those 4 broken packages. For all of them it's a trivial change, you don't even need to handle two different APIs with a try-expect, you can just go for the final correct version (two parameters) straight away. I understand that the overhead right now is somewhat bigger for releasing 4 updates rather than 1. However, it results in a much clearer situation that gets rid of the differences from mainstream, more easily supportable for the forthcoming almost 5 years and is much better for any user who hack around on their system (i.e. install vte-based apps from various sources). I do believe that – cleanliness and better overall quality of bionic with this approach over the other put aside – it's even cheaper to fix those 4 packages now, than to maintain and support this crazy oddness for the rest of bionic's lifetime. Could you guys please seriously consider fixing this situation in the direction where all packages look like they should, rather than none of them? Thanks a lot! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780501 Title: Traceback calling Vte.Terminal.feed_child() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1780501/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775329] Re: Feature request: Add a handler for CVE URLs
Haha, indeed. Thanks! It's been inactive for 9 years, though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775329 Title: Feature request: Add a handler for CVE URLs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1775329/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775329] Re: Feature request: Add a handler for CVE URLs
> The other option would be to do it "properly" the way upstream want I can't recall/find such a request in upstream gnome-terminal's tracker, I don't think we (gnome-terminal upstream developers) have any plans on adding this feature. IMHO downstream distro-specific patches are fine here. > Also do we know if Debian are interested Jeremy is maintaining both the Debian and Ubuntu patches, that why I thought he might want to do it this way. Anyway, I leave this up to you guys to figure out. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775329 Title: Feature request: Add a handler for CVE URLs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1775329/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775329] Re: Feature request: Add a handler for CVE URLs
I wanted to say "Jeremy is maintaining both the Debian and Ubuntu *packages* ..." -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775329 Title: Feature request: Add a handler for CVE URLs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1775329/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775329] Re: Feature request: Add a handler for CVE URLs
I agree it's a nice idea. One nitpick: All the source code goes right next to handling LP regexes, so I'd place and number the patch itself in the "series" file right next to it, too. This patch would be useful for Debian too, but they don't have 60_add_lp_handler.patch which this patch builds on. Perhaps their order should be swapped, so that CVE comes first, and this is the one that converts the body of action_copy_match_cb() into an "if" branch. Then LP comes on top of this for Ubuntu only. Indeed Debian and Ubuntu would use different URLs for CVEs. Maybe you could make the patch itself the same, using a macro passed to configure/make, or define that in another one-liner patch. Not sure if that simplifies anything in your build systems, just a simple idea up for you to consider. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775329 Title: Feature request: Add a handler for CVE URLs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1775329/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1500272] Re: "Tap to click" disabled on Wily upgrade
I can't recall this being an issue on subsequent upgrades to newer releases. Feel free to close. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1500272 Title: "Tap to click" disabled on Wily upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1500272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778824] Re: Terminal starts maximized when using custom font
I can reproduce this in a GNOME session, but not in Unity. Sounds like a bug with the window manager (gnome-shell or mutter). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778824 Title: Terminal starts maximized when using custom font To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1778824/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775111] Re: gnome-terminal Find ignores "Match case"
Fixed upstream in https://gitlab.gnome.org/GNOME/gnome- terminal/commit/6ec754bf. Will be included in gnome-terminal 3.28.3, whenever (if at all) released (there's no schedule for that). Up for Ubuntu to cherry-pick the fix... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775111 Title: gnome-terminal Find ignores "Match case" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1775111/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775111] Re: gnome-terminal Find ignores "Match case"
Confirmed. Thanks for the report, forwarded upstream: https://gitlab.gnome.org/GNOME/gnome-terminal/issues/4. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775111 Title: gnome-terminal Find ignores "Match case" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1775111/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1774167] Re: [SRU] 3.28.2 / 0.52.2
Yes please :) For both components, there are only very few and tiny changes. vte 0.52.2 (ftp://ftp.gnome.org/pub/GNOME/sources/vte/0.52/vte-0.52.2.changes) fixes a crash which I've also filed with further details as LP bug 1772506, hence releasing a fix is highly desirable. > here are fixes related to the list of encodings; if that's bad then you might not be able to use this functionality. gnome-terminal 3.28.2 (ftp://ftp.gnome.org/pub/GNOME/sources/gnome- terminal/3.28/gnome-terminal-3.28.2.changes) now translates the encoding names which were accidentally shown in the Preferences dialog in English. It simply adds a _(...) function call to the displayed string and does not affect the underlying behavior. That being said, of course it's appreciated if you double check the functionality. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1774167 Title: [SRU] 3.28.2 / 0.52.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1774167/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1772557] Re: FREETYPE_PROPERTIES environment variable is not respected
Confirmed. This is related to how gnome-terminal starts up, via dbus / systemd --user. Even if you type "gnome-terminal" in let's say an xterm, it just notifies systemd to fire up the server. During this step, environment variables get lost. As a workaround, you could manually start up the server, followed by the client (with a tiny pause in between, if doing from a script), as described at https://wiki.gnome.org/Apps/Terminal/Debugging (without the gdb part). Here's my wrapper script I often use while debugging: #!/bin/bash /usr/lib/gnome-terminal/gnome-terminal-server --app-id a.b$$ & sleep 0.2 /usr/bin/gnome-terminal --app-id a.b$$ "$@" Plenty of other env variables that somehow affect the behavior (e.g. GTK_THEME) aren't forwarded either. So it's probably not feasible to start whitelisting and somehow proxying them to the server one by one. I guess other apps that use dbus/systemd to start up are also affected. xfce4-terminal follows a more standard pattern. I'm not sure what the right solution would be, it looks to me that this overall design has this limitation, or at least I'm not aware of the proper approach (maybe configure systemd??). Alas I'm not aware with the rationale and details of this design. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1772557 Title: FREETYPE_PROPERTIES environment variable is not respected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1772557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1772506] [NEW] Crash related to hyperlinks
Public bug reported: A crash was discovered recently in VTE, triggered by the combination of explicit hyperlinks (a new feature of vte-0.50) and a non-aligned window size (e.g. Tilix, or maximized GNOME Terminal) due to a missing trivial boundary check. Since GNOME Terminal handles all of its terminals in a single process, a crash causes all its terminals to disappear, making the consequences even worse. Mainstream bugreport with technical details and steps to reproduce: https://bugzilla.gnome.org/show_bug.cgi?id=795826 Fix (for vte-0.52.x): https://git.gnome.org/browse/vte/commit/?h=vte-0-52=5966e8bfb Bionic ships 0.52.1. Mainstream 0.52.2 has been released with this code change only (apart from the version as reported by VTE itself), so instead of patching you could probably just simply bump the version number. Older Ubuntu release are unaffected, since they didn't yet have support for explicit hyperlinks. Jeremy & others, could you please release a fixed package as an update for Bionic LTS? Thanks a lot! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libvte-2.91-0 0.52.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Mon May 21 22:06:38 2018 InstallationDate: Installed on 2016-11-09 (557 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: vte2.91 UpgradeStatus: Upgraded to bionic on 2018-03-14 (67 days ago) ** Affects: vte2.91 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1772506 Title: Crash related to hyperlinks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte2.91/+bug/1772506/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747171] Re: "New Tab" disappeared from the GNOME Terminal menu
Well, since it's in "proposed", which I guess means waiting for feedback, and is not an urgent update at all, my feedback was maybe you should hold it off and release along with that other fix to save an update for users :-) Anyway, filed that as bug 1771290, rest is up to you. Thanks a lot! :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747171 Title: "New Tab" disappeared from the GNOME Terminal menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1747171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771290] [NEW] Untranslated list of encodings in preferences
Public bug reported: The list of encodings in Preferences → Compatibility is in English. The list in the Terminal → Set Character Encoding menu is properly translated, though. Upstream bugreport: https://bugzilla.gnome.org/show_bug.cgi?id=795358 Upstream trivial fix: https://git.gnome.org/browse/gnome- terminal/commit/?h=gnome-3-28=1828cb6d5 Could you please backport this tiny fix to Bionic LTS? (We're planning to release gnome-terminal 3.28.2 containing this plus at least one other tiny fix in about a week.) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-terminal 3.28.1-1ubuntu1 [modified: usr/bin/gnome-terminal usr/lib/gnome-terminal/gnome-terminal-server usr/share/applications/org.gnome.Terminal.desktop usr/share/glib-2.0/schemas/org.gnome.Terminal.gschema.xml usr/share/metainfo/org.gnome.Terminal.appdata.xml] ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Tue May 15 09:46:24 2018 InstallationDate: Installed on 2016-11-09 (551 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to bionic on 2018-03-14 (61 days ago) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771290 Title: Untranslated list of encodings in preferences To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1771290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747171] Re: "New Tab" disappeared from the GNOME Terminal menu
Jeremy, Łukasz, If you're about to release an update for Bionic, could you please backport the trivial https://git.gnome.org/browse/gnome-terminal/commit/?h=gnome-3-28=1828cb6d5 as well? At one place the strings are accidentally left untranslated on the UI, even though at some other place these same strings appear properly translated (that is, the translations are already present accoding to translators' work, just remain unused at one place). Technically it's absolutely independent from the current "New Tab" issue; however, I think we should optimize for releasing as few updates as possible, hence I'm trying to sneak it in here. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747171 Title: "New Tab" disappeared from the GNOME Terminal menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1747171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747171] Re: "New Tab" disappeared from the GNOME Terminal menu
The new menu items are there in mainstream gnome-terminal's source (behind a configure flag; so they aren't added by Ubuntu). Hence they are translated (or not) according to the mainstream GNOME translators' work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747171 Title: "New Tab" disappeared from the GNOME Terminal menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1747171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770494] Re: Does not display VT-100 control codes correctly/consistently
What's the version of GNOME Terminal on CentOS that you're referring to, where you don't face these issues? GNOME Terminal (more precisely, the underlying VTE widget) was improved a lot during the last 4 years, tons of emulation (and other) bugs were fixed. The most relevant one is probably https://bugzilla.gnome.org/show_bug.cgi?id=732586. I can't reproduce the issues on Ubuntu 18.04 (gnome-terminal 3.28, vte 0.52). I personally recommend to you to upgrade to 18.04 soon (14.04 will EOL in a year anyway). It's pretty unlikely that these emulation fixes will be backported to 14.04. (My guess is that GNOME Terminal in Ubuntu 16.04 is most likely already fixed.) (Disclaimer: I'm a GNOME Terminal / VTE guy, but not an Ubuntu developer, so it's not Ubuntu's recommendation to you to upgrade.) > in Ubuntu Gnome terminal it is rendered as a cursor that is the color of a 50% blend between the background and foreground color, making it the best appearing terminal I've used Thanks; not everyone shares your opinion though, see https://bugzilla.gnome.org/show_bug.cgi?id=778122 :) ** Bug watch added: GNOME Bug Tracker #732586 https://bugzilla.gnome.org/show_bug.cgi?id=732586 ** Bug watch added: GNOME Bug Tracker #778122 https://bugzilla.gnome.org/show_bug.cgi?id=778122 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770494 Title: Does not display VT-100 control codes correctly/consistently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1770494/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1718238] Re: Giant terminal icon is blocking out the Terminal window buttons
Continued in bug 1770507. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1718238 Title: Giant terminal icon is blocking out the Terminal window buttons To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1718238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764558] Re: Window buttons icon effect isn't applied to mutter decorations
Done: bug 1770507. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764558 Title: Window buttons icon effect isn't applied to mutter decorations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1764558/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770507] [NEW] Oversized appmenu icon not rescaled
Public bug reported: The patch from bug 1764558 (https://gitlab.gnome.org/GNOME/mutter/merge_requests/62) is broken, and should be reverted (or fixed). The breakage it introduces is noticeably more severe than the tiny shadow it fixes. The broken patch resurrects bug 1718238, which was fixed not long before Bionic's release (but then subsequently broken). Details about the bug re-occurring start at comment 17 of that bug. Screenshot in comment 26. Quick recap: - Launch Ubuntu's default desktop (on X11). - Go to GNOME Tweaks -> Top bar -> disable Application Menu. - Make sure the gnome-icon-theme package isn't installed. - Start gnome-terminal -> note that it looks as in the aforementioned screenshot. For some (unknown) reason the removal of the supposedly irrelevant gnome-icon-theme package makes GTK+ place an icon of 48x48 size as _NET_WM_ICON, rather than a 16x16 one as when this package is installed. Mainstream mutter scales this image from 48x48 to 16x16 and then displays it, as desired. The faulty patch removes the code that scales the image, so the 48x48 version shows up where there's only room for 16x16. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mutter 3.28.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu May 10 23:25:19 2018 InstallationDate: Installed on 2016-11-09 (546 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: mutter UpgradeStatus: Upgraded to bionic on 2018-03-14 (56 days ago) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic regression-release -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770507 Title: Oversized appmenu icon not rescaled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1770507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1718238] Re: Giant terminal icon is blocking out the Terminal window buttons
@guido Nope, that one is irrelevant (that icon title is something completely different, it's a legacy concept: the title of the window whenever it's iconified; plus the change is in gnome-terminal's current development series which won't appear in Bionic). Anyway, I managed to locate the bug, see my previous comment. Now it's Ubuntu's turn to apply the fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1718238 Title: Giant terminal icon is blocking out the Terminal window buttons To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1718238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764558] Re: Window buttons icon effect isn't applied to mutter decorations
This patch is broken, and is responsible for re-introducing bug 1718238 (comment 17 onwards). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764558 Title: Window buttons icon effect isn't applied to mutter decorations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1764558/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
