[Bug 1609342] Re: Gnome-terminal sets directory to HOME for ctrl-shift-n and custom shell command
Hi, So, this is affecting me on Ubuntu 20.04 - gnome-terminal no longer preserves the current working directory in bash upon opening a new window (or tab) from the context menu. Does anyone know what's going on? The /etc/profile.d/vte-2.91.sh script is being sourced correctly, but I believe that it only has to do with the pwd in the titlebar, which is also working. Switching to fish as proposed on StackOverflow is not an option... Any tips? :-( All the best, Yury -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in 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 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 750700] Re: Unity Compiz plugin captures F10 for menu even when explicitly disabled in gnome-terminal
** Summary changed: - gnome-terminal captures F10 for menu even when explicitely disabled + Unity Compiz plugin captures F10 for menu even when explicitly disabled in gnome-terminal ** Description changed: - Binary package hint: gnome-terminal + There is menu item in Edit / Keyboard Shortcuts which says Enable the + menu shortcut key (F10 by default). The F10 key is captured by gnome- + terminal regardless of the checkbox described above. - There is menu item in Edit/Keyboard Shortcuts which says Enable the menu shortcut key (F10 by default). - The F10 key is captured by gnome-terminal regardless of the checkbox described above. + In this case, F10 does not come through to gnome-terminal and is + captured by the window manager which in turn shows the menu. The + configuration option available via gnome-terminal menu DOES NOT WORK IN + THE DEFAULT Ubuntu CONFIGURATION. It cannot be expected from the + average / target user to hunt for the application capturing F10 and + disabling it. - It might be the case, that F10 does not come through to gnome-terminal - and is captured by the window manager which in turn shows the menu. It - is surely configurable somewhere via gconf-editor, but it does not - change the fact, that the user gets really confused. The configuration - option available via gnome-terminal menu DOES NOT WORK IN THE DEFAULT - Ubuntu CONFIGURATION. It cannot be expected from the average/target - user to hunt for the application capturing F10 and disabling it. There - is a half dozen of entries containing F10 to be found via gconf-editor. + The workaround is to disable F10 binding in Ubuntu Unity Compiz plugin: - ProblemType: Bug - DistroRelease: Ubuntu 11.04 - Package: gnome-terminal 2.32.1-0ubuntu3 - ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38 - Uname: Linux 2.6.38-7-generic x86_64 - Architecture: amd64 - Date: Mon Apr 4 21:37:11 2011 - EcryptfsInUse: Yes - ExecutablePath: /usr/bin/gnome-terminal - InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) - ProcEnviron: - SHELL=/bin/bash - PATH=(custom, user) - LANG=en_GB.utf8 - LANGUAGE=en_GB:en - SourcePackage: gnome-terminal - UpgradeStatus: Upgraded to natty on 2011-04-03 (1 days ago) + CompizConfig Settings Manager / Ubuntu Unity Plugin / + Key to open the first panel menu + + Either this binding should be disabled by default, or somehow cooperate + with programs that require to free it (i.e. gnome-terminal). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/750700 Title: Unity Compiz plugin captures F10 for menu even when explicitly disabled in gnome-terminal -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 750700] Re: Unity Compiz plugin captures F10 for menu even when explicitly disabled in gnome-terminal
Invalid means that it is not a bug in gnome-terminal. It has the status New in Unity. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/750700 Title: Unity Compiz plugin captures F10 for menu even when explicitly disabled in gnome-terminal -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 750700] Re: gnome-terminal captures F10 for menu even when explicitely disabled
I am re-assigning this to Unity since apparently it is the root cause of all these problems. ** Also affects: unity (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-terminal (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/750700 Title: gnome-terminal captures F10 for menu even when explicitely disabled -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 750700] Re: gnome-terminal captures F10 for menu even when explicitely disabled
To be more specific, I think that CompizConfig Settings Manager / Ubuntu Unity Plugin / Key to open the first panel menu should be deactivated by default, because it causes a lot of trouble to quite a bit of unsuspecting people. Otherwise, if F10 is disabled in gnome-terminal it should also disable Unity binding. I don't know if this is feasible though. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/750700 Title: gnome-terminal captures F10 for menu even when explicitely disabled -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 766188] Re: None of the gnome-terminal keyboard shortcut settings let me use F10 for exit in mc
*** This bug is a duplicate of bug 750700 *** https://bugs.launchpad.net/bugs/750700 Then there are two checkboxes upper left. And they should be both unchecked (on my Lucid machine it says ENABLE menu shortcut). File menu opens in the terminal header. So it has clearly nothing to do with mc. Gnome people must have broken it. I will re-assign it to gnome-terminal then. ** Also affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Changed in: mc (Ubuntu) Status: Incomplete = Invalid ** This bug has been marked a duplicate of bug 750700 gnome-terminal captures F10 for menu even when explicitely disabled * You can subscribe to bug 750700 by following this link: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/750700/+subscribe -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/766188 Title: None of the gnome-terminal keyboard shortcut settings let me use F10 for exit in mc -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 750700] Re: gnome-terminal captures F10 for menu even when explicitely disabled
People are already complaining to us about it. For now you can use Esc + 0 to quit mc if F10 is captured by gnome-terminal. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/750700 Title: gnome-terminal captures F10 for menu even when explicitely disabled -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 665065] Re: cannot distinguish between Home and Ctrl+Home
Reassigning to the right people. Bug vte upstream about this. ** Changed in: mc Status: New = Invalid ** Project changed: gnome-terminal = vte ** Bug watch added: GNOME Bug Tracker #600659 https://bugzilla.gnome.org/show_bug.cgi?id=600659 ** Also affects: gnome-terminal via https://bugzilla.gnome.org/show_bug.cgi?id=600659 Importance: Unknown Status: Unknown ** Changed in: gnome-terminal Importance: Unknown = Undecided ** Changed in: gnome-terminal Status: Unknown = New ** Changed in: gnome-terminal Remote watch: GNOME Bug Tracker #600659 = None ** Changed in: vte Importance: Undecided = Unknown ** Changed in: vte Status: New = Unknown ** Changed in: vte Remote watch: None = GNOME Bug Tracker #600659 ** Changed in: gnome-terminal (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in ubuntu. https://bugs.launchpad.net/bugs/665065 Title: cannot distinguish between Home and Ctrl+Home -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 120251] Re: security check failed
After some more experimentation, I'd like to document my findings for anyone considering to use SmartVoip or any other betamax-based providers with Ekiga: 1) My points 3-4) are basically invalid. Points 1-2) still stand. 2) Number format is described correctly. 3) What results in the random inability to connect is the failure to negotiate suitable voice codec. As I could notice, betamax primarily uses PCMU / PCMA codecs for voice and if you have Speex enabled it just somehow enters in an infinite loop trying to negotiate and re-negotiate the codecs over and over again. So what you have to do if you consider primarily using betamax is to disable Speex in Ekiga settings and use the arrows to bring PCMU / PCMA up as the codecs of choice and everything gonna work. Latest Ekiga backports for Hardy are available from my PPA: https://launchpad.net/~zyv/+archive/ppa Happy VOIP'ing! -- security check failed https://bugs.launchpad.net/bugs/120251 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 120251] Re: security check failed
I have backported ekiga from lucid to hardy, but it doesn't seem to work properly. I get the same message as previous posters, security check failed. Only for betamax sip, though. ekiga.net echo test works just fine. The workaround of starting as root doesn't help. I added myself to the voice group. -- security check failed https://bugs.launchpad.net/bugs/120251 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 120251] Re: security check failed
After I finally got it working (somehow), here are some thoughts. It seems that: 1) I shouldn't use proxy sip:sip.smartvoip.com or sip.smartvoip.com --- this results in unconditional inability to connect to any host 2) having the number ending with @smartvoip.com results in security check failure ... this is the reliable reason this stupid message appears! It's not a problem with Ekiga. It's just that given provider will not route to the numbers which are not within its own network. 3) having sip: in the phone number also results in the inability to connect (unreliable?) 4) having just the number +xx... results in inability to connect (unreliable?) The number should be in the format of +xx...@sip.smartvoip.com or 00xx...@sip.smartvoip.com . Both work for me. It seems, that when a connection can not be established the best strategy is to re-register the account and try again. It might be that my testing was unreliable, because the provided has some kind on limits on the number of unsuccessful attempts and few failed attempts make the subsequent correct attempts to fail. Very strange. I had a similar kind of issues with ekiga 2.x, but after the first round of problems all subsequent starts very perfectly fine. Let's see if it gonna work tomorrow. -- security check failed https://bugs.launchpad.net/bugs/120251 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 324728] Re: mc in terminal with zh_TW locale have mess display in Jaunty
Re-assigning this to vte. ** Also affects: vte (Ubuntu) Importance: Undecided Status: New -- mc in terminal with zh_TW locale have mess display in Jaunty https://bugs.launchpad.net/bugs/324728 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to vte in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
