[Bug 1288655] Re: Terminal height shrinks - repeatedly restored shorter than the previous height

2022-09-21 Thread Péter Prőhle
This bug disappeared in my case, just when I switched to 2204 Jammy. I made a fresh install from scratch, not a dist-upgrade only. Is there anybody who still has this bug in Jammy, if his/her system is a fresh install from scratch? -- You received this bug notification because you are a member

[Bug 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen

2022-01-20 Thread Péter Prőhle
tags: added: impish ** Tags added: impish -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started

[Bug 1916890] Re: each maximisation + un-maximisation cycle of a gnome-termial windows will shrink the terminal by 1 row and by 1 column

2022-01-20 Thread Péter Prőhle
*** This bug is a duplicate of bug 1288655 *** https://bugs.launchpad.net/bugs/1288655 Duplicate status is still correct. ** Tags added: impish -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.

[Bug 1925732] Re: gnome-terminal ignores the --geometry location requests

2022-01-20 Thread Péter Prőhle
This bug is still there, I am interested in discussing it, but nobody assigned this bug to anybody. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1925732 Title: gnome-terminal

[Bug 1925732] Re: gnome-terminal ignores the --geometry location requests

2022-01-20 Thread Péter Prőhle
tags:added: impish ** Tags added: impish -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1925732 Title: gnome-terminal ignores the --geometry location requests To manage

[Bug 1928317] Re: window focus is lost after blank screen

2022-01-20 Thread Péter Prőhle
This bug is still there, I am interested in discussing it, but nobody assigned this bug to anybody. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1928317 Title: window focus is

[Bug 1936238] Re: Lock screen does not properly give focus after unlocking on Wayland

2022-01-20 Thread Péter Prőhle
*** This bug is a duplicate of bug 1928317 *** https://bugs.launchpad.net/bugs/1928317 ** Tags added: impish -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1936238 Title: Lock

[Bug 1928317] Re: window focus is lost after blank screen

2022-01-20 Thread Péter Prőhle
tags:added: impish ** Tags added: impish -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1928317 Title: window focus is lost after blank screen To manage notifications about this

[Bug 1288655] Re: Terminal height shrinks - repeatedly restored shorter than the previous height

2021-10-19 Thread Péter Prőhle
The bug is still present in 21.10 . This bug in 21.04 went away this August 2021 approx. But upgrading from 21.04 to 21.10 brought back the bug. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.

[Bug 1925732] Re: gnome-terminal ignores the --geometry location requests

2021-05-27 Thread Péter Prőhle
** Description changed: + The more gnome-specific and detailed bug description: + + the gnome-terminal either ignores or misinterprets the + + --geometry=+0+0 , --geometry=+0-0 , --geometry=-0+0 and --geometry=-0-0 + + requests, while mate-terminal executes the correct positioning in the +

[Bug 1925732] Re: gnome-terminal ignores the --geometry location requests

2021-05-27 Thread Péter Prőhle
** Summary changed: - [wayland] gnome window manager ignores the --geometry location request of the gnome-terminal + gnome-terminal ignores the --geometry location requests -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in

[Bug 1925732] Re: [wayland] gnome window manager ignores the --geometry location request of the gnome-terminal

2021-05-27 Thread Péter Prőhle
I have just made a couple of tests, and the result is: 1: mate-terminal interprets correctly the --geometry over the both of Wayland and Xorg ** hence it was rigth when I derived "theoretically" from the behaviour of the Gnome Shell, that also over Wayland the client programs can position their

[Bug 1925732] Re: [wayland] gnome window manager ignores the --geometry location request of the gnome-terminal

2021-05-27 Thread Péter Prőhle
** Changed in: gnome-terminal (Ubuntu) Status: Opinion => Confirmed ** Changed in: mutter (Ubuntu) Status: Opinion => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu.

[Bug 1288655] Re: Terminal height shrinks - repeatedly restored shorter than the previous height

2021-05-27 Thread Péter Prőhle
The error works on 21.04 Wayland as well. This bug looks very stable, depending only on the gnome terminal itself, regardless of which version of it is used. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.

[Bug 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen

2021-05-27 Thread Péter Prőhle
The problem is still there. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary

[Bug 1916890] Re: each maximisation + un-maximisation cycle of a gnome-termial windows will shrink the terminal by 1 row and by 1 column

2021-05-27 Thread Péter Prőhle
*** This bug is a duplicate of bug 1288655 *** https://bugs.launchpad.net/bugs/1288655 Duplicate status looks correct. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.

[Bug 1928317] Re: window focus is lost after blank screen

2021-05-27 Thread Péter Prőhle
OK, if a bug must be filed to a source package, and nobody who knows this much better than me did it in the last two weeks, then I will now signal my first guess: the windows manager, perhapes it handles the erroneous behaviour of blanking, I do not know. Sorry, if I made a wrong guess. ** Also

[Bug 1925732] Re: [wayland] gnome window manager ignores the --geometry location request of the gnome-terminal

2021-05-13 Thread Péter Prőhle
OK, if you think that Wayland is responsible for the but, then: 1: this but must be upstreamed to the developers of the Wayland protocol 2: and this bug is also a bug of the "21.04 release as a whole", since it is a bug that it makes this buggy Wayland as default. I understand that this bug

[Bug 1925732] Re: [wayland] gnome window manager ignores the --geometry location request of the gnome-terminal

2021-05-13 Thread Péter Prőhle
"Although dragging could be done by relative movements. Setting an absolute position does appear to be impossible in Wayland." If it was really impossibble, then how the Gnome shell or any window manager can position *itself*? We see, that the diverse components of the diverse window managers

[Bug 1288655] Re: Terminal height shrinks - repeatedly restored shorter than the previous height

2021-05-11 Thread Péter Prőhle
The bug is still there in Ubuntu 21.04, and is very disturbing when I need frequent maximalisation and reset to normal 80 columns, especially when I give classes at the university. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to

[Bug 1925732] Re: [wayland] gnome window manager ignores the --geometry location request of the gnome-terminal

2021-05-10 Thread Péter Prőhle
The definition of "confirmed" is that "Verified by someone other than the reporter.", hence in case of "gnome-terminal" it was wrong to remove the "confirmed" tag, since someone other than me reported as well that the "gnome-terminal" is affected, and hence it is totally right, that the

[Bug 1925732] Re: [wayland] gnome window manager ignores the --geometry location request of the gnome-terminal

2021-05-10 Thread Péter Prőhle
The bug is clearly stated, reproducible and confirmed by others as well. Hence it can not be ONLY "invalid + opinion + opinion" at 3 packages, and no package is mentioned with "new" or "confirmed". It is acceptable, if someone's opinion is that "mutter is not new but opinion only". But it is

[Bug 1925732] Re: [wayland] gnome window manager ignores the --geometry location request of the gnome-terminal

2021-05-08 Thread Péter Prőhle
A very personal comment: the main reason why I use linux exclusively since 1994 is that I can work in character terminal using the unix command line programming environment for my everyday goals (teaching and researching math and computational math). This is the reason why I am so sensitive for

[Bug 1925732] Re: [wayland] gnome window manager ignores the --geometry location request of the gnome-terminal

2021-05-08 Thread Péter Prőhle
Sorry to oppose the opinion of those who probaly know the system much better than me, but it is simply NOT TRUE that neither Ubuntu nor especially Mutter is responsible for the huge step backward, the missing positioning of windows on the screen what was always possible since the 80's. AND it is

[Bug 1925732] Re: new in 21.04: gnome window manager ignores the --geometry location request of the gnome-terminal

2021-05-04 Thread Péter Prőhle
If the "GNOME shell" is able to ask Wayland to position the diverse elements of the destop, then the cooperation of the "GNOME shell" and "gnome-terminal" should be able to do the same. Wayland can be asked to position the top bar to the top of the screen, to position the side bar to the left of

[Bug 1925732] Re: new in 21.04: gnome window manager ignores the --geometry location request of the gnome-terminal

2021-05-04 Thread Péter Prőhle
** Also affects: gnome-shell Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1925732 Title: new in 21.04: gnome window manager ignores

[Bug 1925732] Re: new in 21.04: gnome window manager ignores the --geometry location request of the gnome-terminal

2021-05-04 Thread Péter Prőhle
"* Find a gnome-shell extension that will remember window positions for you;" Thanks, perhaps this is the best direction for me to proceed. Hence I suggest to close this bug report as "successful". -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is

[Bug 1925732] Re: new in 21.04: gnome window manager ignores the --geometry location request of the gnome-terminal

2021-05-03 Thread Péter Prőhle
I do not find how to add "Wayland" to the "affects" list, help please. Thanks. "wayland-protocols (wayland-protocols) (Choose another project) wayland- protocols doesn't use Launchpad to track its bugs. If you know this bug has been reported in another bug tracker, you can link to it; Launchpad

[Bug 1925732] Re: new in 21.04: gnome window manager ignores the --geometry location request of the gnome-terminal

2021-05-03 Thread Péter Prőhle
"... this is expected because windows only have control over their size, and NEVER THEIR POSITION, in Wayland" This is really a tragedy. One significant benefit for me of the linux world over the micro and soft world, that I can POSITION the windows of a project from my shell script starting

[Bug 1925823] [NEW] gnome-terminal losts or ignore the newline character coming from mouse paste

2021-04-23 Thread Péter Prőhle
Public bug reported: If there is a complete bash command with terminating newline in the cut and paste buffer, and it is pasted into a gnome-terminal, then the command is *not* executed, the newline is ignored by the terminal. But in return this bug, the pasted command is showed in reverse

[Bug 1925732] [NEW] new in 21.04: gnome window manager ignores the --geometry location request of the gnome-terminal

2021-04-22 Thread Péter Prőhle
Public bug reported: The example "gnome-terminal --geometry=80x24+200+200" from the man page of gnome-terminal, does not work: while the 80x24 part of the geometry request is executed, the location +200+200 is overridden by the automatic positioning of new windows by the "Gnome Shell".

[Bug 1288655] Re: Terminal height shrinks - repeatedly restored shorter than the previous height

2021-03-02 Thread Péter Prőhle
The bug is still there in Ubuntu 20.10, see the riport in https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1916890 each maximisation + un-maximisation cycle of a gnome-termial windows will shrink the terminal by 1 row and by 1 column two such a sycles (maximize, unmaximize, maximize,

[Bug 1916890] [NEW] each maximisation + un-maximisation cycle of a gnome-termial windows will shrink the terminal by 1 row and by 1 column

2021-02-25 Thread Péter Prőhle
Public bug reported: each maximisation + un-maximisation cycle of a gnome-termial windows will shrink the terminal by 1 row and by 1 column two such a sycles (maximize, unmaximize, maximize, unmaximize) shrinks from 80x42 to 78x40: prohlep@pc56:~$ resize COLUMNS=80; LINES=42; export COLUMNS

[Bug 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen

2021-02-25 Thread Péter Prőhle
Someone wrote, not to me: "Then log out and in again to verify the bug still occurs without extensions.". However my ubuntu 20.10 is in default release state, I added *no* extension to it (I disbled a few kbd shortcuts, added two kbd shortcuts, so it is basically in release state). And I have

[Bug 1738500] Re: Ctrl+Shift+E not working in Bionic

2018-09-01 Thread Péter Prőhle
Who knows, which of the bionic packages provides this Emoji Choice, since that package is the presumable cause of this CONCEPTUAL BUG. If you searh for "gnome disable emoji choice" in google, then you will see, that many other packages is affected in the same way: TRADITIONAL KEYBOARD SHORTCUTS

[Bug 1738500] Re: Ctrl+Shift+E not working in Bionic

2018-09-01 Thread Péter Prőhle
I just found a temporary work around: 1: start "ibus-setup" as a normal user in a terminal 2: chose "Emoji" tab 3: click the button "..." at "Keyboard Shortcuts Emoji Choice" 4: push "delete" among the "add/apply/delete" buttons This is a very windows-ish solution, i.e. it can not be a part

[Bug 1738500] Re: Ctrl+Shift+E not working in Bionic

2018-09-01 Thread Péter Prőhle
Minor TYPO correction: accidentally I wrote "Ctrl-Alt-e shortcut", but naturally "Ctrl-Shift-e shortcut" is in question, at least in my "bionic / gimp" case (fresh install, no unreliable history). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is

[Bug 1738500] Re: Ctrl+Shift+E not working in Bionic

2018-09-01 Thread Péter Prőhle
I have exactly the same problem: the important Ctrl-Alt-e shortcut is diverted to bring up a very childish "Emoji Choice" window, while in GIMP this Ctrl-Alt-e is frequently needed, since if we want to slightly alter a just scanned *.PNG file and save it back, than this is the OFFICIAL SHORTCUT

[Bug 1738500] Re: Ctrl+Shift+E not working in Bionic

2018-09-01 Thread Péter Prőhle
** Also affects: gimp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1738500 Title: Ctrl+Shift+E not working in Bionic To manage

[Bug 1755106] Re: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load

2018-04-03 Thread Péter Prőhle
Today I got similar result: $ /usr/lib/gnome-settings-daemon/gsd-media-keys (gsd-media-keys:2834): GLib-GIO-WARNING **: 23:34:21.130: Dropping signal AcceleratorActivated of type (uuu) since the type from the expected interface is (ua{sv}) (gsd-media-keys:2834): GLib-GIO-WARNING **:

[Bug 1755106] Re: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load

2018-03-31 Thread Péter Prőhle
OK, I forget to tell, that I use Unity! and my custom settings are: $ dconf dump /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ [custom1] binding='BackSpace' command='gnome-session-quit --power-off' name='gnome-session-quit --power-off' [custom0] binding='g'

[Bug 1755106] Re: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load

2018-03-31 Thread Péter Prőhle
Today the problem occurred again, so I could test /usr/lib/gnome- settings-daemon/gsd-media-keys. Do I understand correctly that in a terminal running bash inside, I simply give this /usr/lib/gnome- settings-daemon/gsd-media-keys fully qualified path as a command? The result is that it does not

[Bug 1755106] Re: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load

2018-03-28 Thread Péter Prőhle
In the last 9 days, the problem became less common, but today it has started again. The situation remained the same,as I described at earlier reports. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.

[Bug 1758373] [NEW] bison -Wconversion warning

2018-03-23 Thread Péter Prőhle
Public bug reported: I wish to use the -Wconversion at gcc (the warnings are instructive for me, and they already taught me a lot), but then: $ bash bison_conversion_bug.sh y.tab.c: In function ‘yyparse’: y.tab.c:1023:12: warning: conversion to ‘yytype_int16 {aka short int}’ from ‘int’ may

[Bug 1758373] Re: bison -Wconversion warning

2018-03-23 Thread Péter Prőhle
HELP! I adjusted at the beginning of the bug report, that this is NOT a gnome-settings-daemon bug, BUT a bison bug, ... there was a possibility TO CHANGE THE PACKAGE WHAT IS AFFECTED, I do not know why it changed back to gnome-settings-daemon? Please, somebody who has enough right for this,

[Bug 1755106] Re: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load

2018-03-20 Thread Péter Prőhle
I wish to provide better diagnostic information, but I do not know what to submit in this particular situation. I am also ready to install some sort of Watchdog daemon, which can better detect what is going on in this kind of situation. I can imagine a say a small shell script or something alike

[Bug 1750846] Re: several g-s-d services are timing out when booting a live session

2018-03-17 Thread Péter Prőhle
Is it possible, that my issue https://bugs.launchpad.net/bugs/1755106 has some connection with this issue, see the journalctl | grep -i key | grep -i failed > journalctl_key_failed.txt attachment there: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-

[Bug 1755106] Re: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load

2018-03-17 Thread Péter Prőhle
[continuing the previous comment] The the output of "ps acuwx | fgrep gsd" is still empty. Should I see any process containing the substring "gsd"? Is it possible, that my issue has some connection with the followin issue: https://bugs.launchpad.net/bugs/1750846 -- You received this bug

[Bug 1755106] Re: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load

2018-03-17 Thread Péter Prőhle
Today I had again a possibility to check the issue. Tell me please, that what kind of information, what command outputs should I attach, when I face myself to the issue in question? Output of "dmesg | grep -i gsd" is empty. Outout of "journalctl | grep -i gsd" has no new items in the last 4

[Bug 1756387] [NEW] Whish: a Unity like desktop bar in Gnome, or the default desktop manager of Ubuntu

2018-03-16 Thread Péter Prőhle
Public bug reported: I wish a Unity like desktop bar in Gnome, or the default desktop manager of Ubuntu. More precisely: a desktop bar which is capable to steal, to take away the menu bars of the application windows, and show the menu bar of that application window which is in focus currently.

[Bug 1755106] Re: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load

2018-03-16 Thread Péter Prőhle
No I had a possibility to check the situation for the question: Do you have an active "gsd-media-keys" process when getting the issue? I have the /usr/lib/gnome-settings-daemon/gsd-media-keys ELV binary, but I do NOT see in the linting of "ps auxw", and even the output of "ps acuwx | fgrep gsd"

[Bug 1755106] Re: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load

2018-03-13 Thread Péter Prőhle
"Do other keybinding work?" --- YES they do work, only the "custom shortcuts" are affected, but ALL of them (I have only 2 custom shortcuts). "Does journalctl contains any error about gsd-media-keys?" journalctl | grep gsd-media-keysgives the following result (I upgraded to 18.04 one days

Re: [Bug 1226962] Re: Hotkeys not functional in non-latin keyboard layout in 13.10

2013-12-08 Thread Péter Prőhle
Ctrl-Alt-T doesn't open Terminal in russian layout. However, with m17n workaround works OK. Is there a latin letter T in the russian layout? I mean a real latin letter T, and not only a correspondig cyrillic letter. This is the REAL question. While it is not comfortable, but it is according

Re: [Bug 1226962] Re: Hotkeys not functional in non-latin keyboard layout in 13.10

2013-12-08 Thread Péter Prőhle
There is a letter T in the Greek layout. Also, terminal in Greek translates to τερματικό, both words start with a letter T. So, there is no excuse for the Ctrl-Alt-T Unity shortcut not working in Greek layout. Greek T is NOT identical to Latin T, they are DISTINCT letters, which only

Re: [Bug 1226962] Re: Hotkeys not functional in non-latin keyboard layout in 13.10

2013-12-08 Thread Péter Prőhle
What matters is that the *physical* keyboard shortcuts like Ctrl-Alt-T or Ctrl-C, Ctrl-V should just work no matter what the current layout is. That is, what you say, that the four layers, i.e. the plain, the Alt, the Ctrl and the Ctrl-Alt layers shuld be INDEPENDENT-ly configurable, and so

[Bug 1226962]

2013-12-06 Thread Péter Prőhle
Dear Norbert! IMHO below. In present time many problems come from GNOME fast destruction and simpility/stupidity behavior. GNOME reduces its functionality very fast, and this changes are not tested for all regressions and bugs, this changes are not discussed with gnome-users. So many

[Bug 1113364] [NEW] keyboard layout fails to be different for individual windows

2013-02-02 Thread Péter Prőhle
Public bug reported: My case is a close variant of the following two bugs closely related to each other: https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/885730 https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/622965 My usual setting in system settings