[Bug 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen
tags: added: impish ** Tags added: impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1888098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925732] Re: gnome-terminal ignores the --geometry location requests
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925732 Title: gnome-terminal ignores the --geometry location requests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1925732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925732] Re: gnome-terminal ignores the --geometry location requests
tags:added: impish ** Tags added: impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925732 Title: gnome-terminal ignores the --geometry location requests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1925732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916890] Re: each maximisation + un-maximisation cycle of a gnome-termial windows will shrink the terminal by 1 row and by 1 column
*** 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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916890 Title: each maximisation + un-maximisation cycle of a gnome-termial windows will shrink the terminal by 1 row and by 1 column To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1916890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925823] Re: Ubuntu version of BASH losts or misinterprets the newline character coming from mouse paste
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925823 Title: Ubuntu version of BASH losts or misinterprets the newline character coming from mouse paste To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1925823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925823] Re: Ubuntu version of BASH losts or misinterprets the newline character coming from mouse paste
tags:added: impish ** Tags added: impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925823 Title: Ubuntu version of BASH losts or misinterprets the newline character coming from mouse paste To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1925823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928317] Re: window focus is lost after blank screen
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928317 Title: window focus is lost after blank screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1928317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936238] Re: Lock screen does not properly give focus after unlocking on Wayland
*** 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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936238 Title: Lock screen does not properly give focus after unlocking on Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1936238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928317] Re: window focus is lost after blank screen
tags:added: impish ** Tags added: impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928317 Title: window focus is lost after blank screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1928317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1288655] Re: Terminal height shrinks - repeatedly restored shorter than the previous height
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1288655 Title: Terminal height shrinks - repeatedly restored shorter than the previous height To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1288655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925732] Re: gnome-terminal ignores the --geometry location requests
** 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 + same environment (display manager and window manager). + + In case of Wayland, the gnome-terminal ignores the requests listed + above, while mate-terminal is correctly positioned, in contrary to the + urban legend, that under Wayland such a positioning is imposibble. + + In case of Xorg, the gnome-terminal positions itself into the corners of + the rectangle containing the physical screens, even if that corner is + not inside any of the physical screens. + + I.e.: in case of Xorg the gnome-terminal is ready to position itself + into a not visible corner of the virtual space contaning the physical + screens instead of do the same as the mate-terminal can do: to position + itself into a corner of the visible physical screen. + + === The bug of gnome-terminal is that it is not able to position intself + into visible corners, while the mate-terminal can do it, ... and in + general the usual graphical programs can do it since the 80's. + + *** The original bug description: + 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". "--geometry=GEOMETRY Set the window size as COLSxROWS+X+Y. For example, 80x24 or 80x24+200+200." The "+X+Y" part is ignored since I upgraded from 20.10 to 21.04 yesterday, just 4 hours after the official release. ** Tags removed: wayland wayland-session ** Tags added: geometry 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/1925732 Title: gnome-terminal ignores the --geometry location requests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1925732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925732] Re: gnome-terminal ignores the --geometry location requests
** 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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925732 Title: gnome-terminal ignores the --geometry location requests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1925732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925732] Re: [wayland] gnome window manager ignores the --geometry location request of the gnome-terminal
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 windows! Now we see, that even the mate-terminal is capable to position it's window on the base of my --geometry requests 2: gnome-terminal misinterprets the --geometry over Xorg but does something (see below) 3: gnome-terminal ignores the --geometry over Wayland ** hence the gnome-terminal is the package which has serious difficulties to interpret the --geometry requests, ... in detail: If the bottom of "left screen" is higher than the bottom of the "right screen" and the top of the "left screen" is also higher than the top of the "right screen", and the left bar is hidden, then IN XORG: gnome-terminal --geometry=+0+0 is not at the left edge gnome-terminal --geometry=+0-0 is neither at the left edge, but even worse: the bottom of the terminal, --- where we work usually, --- is below the left screen gnome-terminal --geometry=-0+0 is also at a wrong location: the top of it is over the top of the right screen gnome-terminal --geometry=-0-0 this is the only case, where it is at the right position: in the lower right corner, bravo! BUG / 1: in case of Xorg, the gnome-terminal takes the smallest rectangle containing the two screens, subtractes the hidden left bar asif it was shown there, and regardles whether there is a proper physical screen at the corner in question, it puts the window there, even if the user can not see it. BUG / 2: in case of Wayland, the gnome-terminal ignores the --geometry=-0+0 alike requests, while mate-terminal demonstrates, that all of these kind of requests can be correctly satisfied, even in spite of the urban legend, that it is imposibble over Wayland. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925732 Title: [wayland] gnome window manager ignores the --geometry location request of the gnome-terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1925732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925732] Re: [wayland] gnome window manager ignores the --geometry location request of the gnome-terminal
** 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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925732 Title: [wayland] gnome window manager ignores the --geometry location request of the gnome-terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1925732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1288655] Re: Terminal height shrinks - repeatedly restored shorter than the previous height
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1288655 Title: Terminal height shrinks - repeatedly restored shorter than the previous height To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1288655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen
The problem is still there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1888098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916890] Re: each maximisation + un-maximisation cycle of a gnome-termial windows will shrink the terminal by 1 row and by 1 column
*** 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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916890 Title: each maximisation + un-maximisation cycle of a gnome-termial windows will shrink the terminal by 1 row and by 1 column To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1916890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928317] Re: window focus is lost after blank screen
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 affects: gnome-shell (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/1928317 Title: window focus is lost after blank screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1928317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925823] Re: losts or misinterprets the newline character coming from mouse paste
The bug is NOT the error of the original GNU package, but of the way how it is integrated into the Ubuntu 21.04, because if I download the GNU package itself, compile and try, then it works fine. In detail what I did: mkdir -p ~/bash cd ~/bash rm -fr bash-* sudo apt-get -y install byacc wget https://ftp.gnu.org/gnu/bash/bash-5.1.tar.gz tar xvzf bash-*.tar.gz rm bash-*.tar.gz cd bash-* time ( ./configure ; make ) env -i PATH="$PWD:$PATH" ./bash --noprofile --norc and here if I do the same cut and paste tests, and drop a command with a terminating line feed character, then this bash binary will simply execute it ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925823 Title: Ubuntu version of BASH losts or misinterprets the newline character coming from mouse paste To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1925823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925823] Re: losts or misinterprets the newline character coming from mouse paste
In addition to the correct behaviour of the GNU bash, I will not get that disturbing fancy behaviour of the Ubuntu 21.04 version, that instead of executing the command the dropped command is shown in reverse video. Hence the bug in question is clearly an Ubuntu re-packaging issue. ** Summary changed: - losts or misinterprets the newline character coming from mouse paste + Ubuntu version of BASH losts or misinterprets the newline character coming from mouse paste -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925823 Title: Ubuntu version of BASH losts or misinterprets the newline character coming from mouse paste To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1925823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925823] Re: losts or misinterprets the newline character coming from mouse paste
If I remain inside Ubuntu 21.04, but compile the previous version of bash, then the error disappears, ... this suggest that the erorr is not the consequence of the version of Ubuntu, but the "bash, version 5.1.4(1)-release" itself, or perhaps an Ubuntu specific configuration of the environment. In detail: mkdir ~/bash cd ~/bash wget https://ftp.gnu.org/gnu/bash/bash-5.0.tar.gz tar xvzf bash-5.0.tar.gz cd bash-5.0 sudo apt-get install byacc ./configure make env -i PATH="$PWD:$PATH" ./bash --noprofile --norc and here if I drop something containing a line feed character, the bash will correctly execute the currently edited commandline -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925823 Title: losts or misinterprets the newline character coming from mouse paste To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1925823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928317] Re: window focus is lost after blank screen
My problem is that I don't know which package is responsible for blanking: namely to record the windows in input focus, then blank, then wait for a waking event, then switch the monitors on, and restore the input focus to the window what was in focus just before blanking. That is the reason why I didn't want to mark a package on the base of my missing knowledge above. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928317 Title: window focus is lost after blank screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1928317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925732] Re: [wayland] gnome window manager ignores the --geometry location request of the gnome-terminal
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 reporting system is package oriented, ... ok, then the base package of "21.04 release as a whole" which defines what packages belong to the release and what are the default settings HAS this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925732 Title: [wayland] gnome window manager ignores the --geometry location request of the gnome-terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1925732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925732] Re: [wayland] gnome window manager ignores the --geometry location request of the gnome-terminal
"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 does not float around in an uncontrolled way, but *somehow* they are able to tell to Wayland where to position that components. The gnome-terminal should be able to do the same, either directly ask Wayland, or indirectly ask the window manager, in return of the --geometry argument. Hence it is confirmed, that the problem in question is 1: either a severe bug of the windows manager itself 2: or a severe bug of the applications receiving the --geometry arguments. I am extremly upset of keeping this bug report on the level of "opinion". There are so uncomfortable problems around the terminal windowing since 21.04, https://bugs.launchpad.net/ubuntu/+bug/1925823 https://bugs.launchpad.net/ubuntu/+bug/1928317 https://bugs.launchpad.net/ubuntu/+bug/1916890 https://bugs.launchpad.net/ubuntu/+bug/1888098 https://bugs.launchpad.net/ubuntu/+bug/1288655 or the too thick capture bar of a terminal wastes the vertical space that I seriousely consieder to change to other distro. My work depends heavily on the comfort of character terminals I became used to in the late 80's, and since 21.04 the level of comfort reached a treshold of pain. And now, I can not achieve that this serious bug is taken seriously. This bug crosses the basics of the windowing standars hold already for decades. Perhaps one of the iconic feature of a windowing system is that an application can position the other windows. This was possibble already in the mid 80's! I simply do not understand what is going here around the Wayland, while on the other hand it seems to be a very promising progress in the technology of the windowing system. But why it is a so big issue to position a window by an other application? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925732 Title: [wayland] gnome window manager ignores the --geometry location request of the gnome-terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1925732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928317] Re: window focus is lost after blank screen
"Remember, this bug report is a duplicate of bug #1925732. Comment here only if you think the duplicate status is wrong." That is right, totally wrong. Read before acting the descriptions of the two bugs, instead of wasting my time. #1928317 : The essence of this bug is that the window in focus is either not remembered or remembered but the focus is not restored after returning from "screen blank" state. #1925732 : The essence of the other bug is that the windows manager fails to execute the window positioning requests. Of course --- at a high enough abstract level --- all the bugs are duplicates of each other. ** This bug is no longer a duplicate of bug 1925732 [wayland] gnome window manager ignores the --geometry location request of the 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/1928317 Title: window focus is lost after blank screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1928317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928317] Re: window focus is lost after blank screen
*** This bug is a duplicate of bug 1925732 *** https://bugs.launchpad.net/bugs/1925732 ** Summary changed: - windows focus is lost after blank screen + window focus is lost after blank screen -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928317 Title: window focus is lost after blank screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1928317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928317] [NEW] windows focus is lost after blank screen
Public bug reported: New in 21.04 hirsute default installation, the problem was not there in 20.10 . Environment: the default Wayland (source of other trubles as well, the most disturbing out of them is https://bugs.launchpad.net/ubuntu/+bug/1925732) and the Gnome shell Problem steps: (1) there are few windows on my screen and the focus is in one of them, I edit there something, (2) after 5 minutes of user inactivity the screen blanks, (3) I wish to resume the editing in the same window, hence I hit either a ctrl or shift key, or slightly move the mouse, (4) the view comes back, but none of the windows have the input focus! ** Affects: 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/1928317 Title: windows focus is lost after blank screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1928317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925823] Re: losts or misinterprets the newline character coming from mouse paste
Sorry that I edited the original bug report, but I think it was better to make it more informative, and not to grab these improvements of the bug description among the comments. Read please, re-read please the new version of the bug report. ** Description changed: + Quiete a few experients shows, that bash misinterprets the newline- + character coming from mouse paste, while in the same terminals the emacs + or vim or alpine and many other character oriented programs interprest + correctly. + + The problem is specific to the situation when we are at a bash prompt of + a new version of bash we got in Ubuntu 21.04. As soon as I invoke an ssh + session, the interpretation of the newline-caharcter becomes correct, + since the remote older bash interprets correctly. + + >>> Newline bug of first kind: + 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 - coloring, + >>> Newline bug of second kind: - what is very disturbing when a command is not executed, but decorated in - a funny way instead. + If I prepare a bash command say - This is new in 21.04, the dropping commands into a gnome-terminal worked - fine in 20.10, ... + cp target-directory - ... and in the last 27 years of my linux usage. + and I collect into the paste buffer "source-file newline-character" + + and I drop it IN BETWEEN the prepared "cp" and "target-directory" + + then the result is wrong: + + instead of interpreting the newline-character as "push enter" + + the command is broken into the followint 2 lines: + + cp source-file + + target-directory + + and I get an error message about missing target specification. + + cp: missing destination file operand after 'source-file' + Try 'cp --help' for more information. + bash: target-directory: Is a directory + + I found better to make this original bug descripton more informative. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925823 Title: losts or misinterprets the newline character coming from mouse paste To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1925823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925823] Re: losts or misinterprets the newline character coming from mouse paste
** Summary changed: - losts or ignore the newline character coming from mouse paste + losts or misinterprets the newline character coming from mouse paste -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925823 Title: losts or misinterprets the newline character coming from mouse paste To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1925823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1288655] Re: Terminal height shrinks - repeatedly restored shorter than the previous height
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1288655 Title: Terminal height shrinks - repeatedly restored shorter than the previous height To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1288655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890725] Re: wacom tablet disturbs unity background, color scheme and keyboard shortcuts
Nobody except for me is uging Wacom tablet over Ubuntu Unity? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890725 Title: wacom tablet disturbs unity background, color scheme and keyboard shortcuts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-unity-meta/+bug/1890725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925732] Re: [wayland] gnome window manager ignores the --geometry location request of the gnome-terminal
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 "gnome-terminal" is non the list named "Affects" with the status of "Confirmed". No one told, that "gnome-terminal" is mainly responsible for the bug, but the title of the list is *not* "The responsible packages", *but* "Affects". And it is "Confirmed" that "gnome-terminal" is "Affected". Henc I ask someone else, especially who removed it, to put back the "Confirmed" status. Since the "opinion" or "invalid" vould be missleading, and simply the opposite of the real truth. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925732 Title: [wayland] gnome window manager ignores the --geometry location request of the gnome-terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1925732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925732] Re: [wayland] gnome window manager ignores the --geometry location request of the gnome-terminal
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 not acceptable, if the same person does not mark any other package or the Ubuntu as a whole as "new" or "confirmed", --- since if all the packages mentioned already becomes either "invalid" or "opinion", then the bug report is rejected in fact, what would be a wrong decision since the bug is there confiredly. In fact, if wayland protocol is not advanced enough to provide the original standard facility to handle the positioning of windows, then ALL the packages that wish to use this original standard instead of the new facilities, all of them have the bug, because it is a buggy behaviour to rely on something what is not offerd by the underlying wayland. Therefore the releases 21.04 as a whole has this bug: makes something defuault what brakes the all the packages which wish to position the main window of it's own applications. A disturbing exampe: $ wmctrl -d Cannot get current desktop properties. (_NET_CURRENT_DESKTOP or _WIN_WORKSPACE property) $ wmctrl -l $ wmctrl -d does not "List all desktops managed by the window manager." wmctrl -l does not "List the windows being managed by the window manager." While the same "wmctrl" packages works fine with Xorg. However the "wmctrl" can not be added to the affected packages, since the bugs.launchpad does not accept "wmctrl" as an existing package! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925732 Title: [wayland] gnome window manager ignores the --geometry location request of the gnome-terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1925732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925732] Re: [wayland] gnome window manager ignores the --geometry location request of the gnome-terminal
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 the missing positioning of my terminals, since I frequently invoke and kill terminals, depending on the actual needs, I have never abandoned windows waiting for nothing. Sorry for this very personal comment, but I wanted to explain why I wish not to consider "invalid" ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925732 Title: [wayland] gnome window manager ignores the --geometry location request of the gnome-terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1925732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925732] Re: [wayland] gnome window manager ignores the --geometry location request of the gnome-terminal
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 neither true, that USING Wayland becomes impossible to handle the positioning. Wayland side: now I am in Mutter over Wayland w/o Xorg, and the top bar on the screen is NOT appearing randomly depending on the situation, but it is always aligned on the top of the actual screen, and it never extends to the other screen. HENCE the location of top, the location of top-left corner and the location of the top-right corner CAN BE handled, --- and I need exactly that: gnome-terminal --geometry=+0+0 == I wish a terminal into the top-left corner gnome-terminal --geometry=-0+0 == I wish a terminal into the top-right corner Ubuntu side: it is not Wayland but Ubuntu who made DEFAULT this Wayland w/o Xorg any warnings at the login screen, and even the fact that "the current login will fall into Wayladn w/o Xorg OR there will be Xorg services" IS HIDDEN, NOT SHOWN rigth where the account name and the password is due. HENCE Ubuntu as a strategic decider IS involved in the case. Mutter side: it is not true that Mutter is not capable to handle the positioning w/o Xorg, there are PLENTY evidences and indications, that Muter DOES EXACLTY KNOW where the edges of my two physical screens are. HENCE in spite of the backward downgrading of the Wayland protocol, Mutter is NOT behindered in knowing the rectangles of my two physical creens. Therefore Mutter IS also responsible, that the positioning of a gnome- terminal dos not work any longer if the default of Ubuntu is Wayland w/o Xorg. Sorry, I understand, that I could invoke the Xorg services which are now considered obsolote by Ubuntu, ... ... but I use computers since 1972, I was an active adult in parallel with the development of computer systems. HENCE my experience, that better not to deviate from the defaults, otherwise I will have more trubles, than to stand out somehow the defaults. That is why so interesting for me, that the traditional standard positionings of windows should work even over raw Wayland w/o Xorg services. This is the derivation, why I think that it is proven that the categorisation of "invalid" is wrong. Since I am the first reporter, therefore I can not switch this "invalid" back to the previous "confirmed", henc my only possibility now to change it back to "new", SORRY for that, but the "invalid" is not true, and it would behinder the handling of the problem if I leve it "invalid". I changed only at "mutter", since the gnome-terminal looks forwarding the positioning requests. Hence I have choosed "opinion" for the terminal, since there is no better choice for the situation, that the proper use of the gnome- terminals are behindered, actually that was the reason why we descovered the problem around Wayland and the default decison of Ubuntu, but the gnome-terminal looks not responsible for it's insufficient behaviour in the daily use. ** Changed in: mutter (Ubuntu) Status: Invalid => New ** Changed in: gnome-terminal (Ubuntu) Status: Invalid => Opinion -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925732 Title: [wayland] gnome window manager ignores the --geometry location request of the gnome-terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1925732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925732] Re: new in 21.04: gnome window manager ignores the --geometry location request of the gnome-terminal
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 the scereen, ... then "GNOME shell" and "gnome-terminal" should be able to request at Wayland the top-right or top-left positioning according to the original request of gnome-terminal --geometry=-0+0" or "gnome-terminal --geometry=+0+0" respectively. To position someting into one of the 4 corners is so common request, that there shuld be a solution for that, --- hence this bug report is anyways a real problem of the cooperation of "gnome-terminal" and "GNOME shell" with "Wayland". Yet another issue: "I think it's more of a security feature than a bug, ..." --- If Wayland doesn't support the positioning request due to security concerns, then even the size requests shuold be forbidden and make that features obsolote as weel, since a request for maximal possibble size implies the dangerous request of positioning, namely into the upper left corner, what positioning request is considered a security threat. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925732 Title: new in 21.04: gnome window manager ignores the --geometry location request of the gnome-terminal To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1925732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925732] Re: new in 21.04: gnome window manager ignores the --geometry location request of the gnome-terminal
** Also affects: gnome-shell 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/1925732 Title: new in 21.04: gnome window manager ignores the --geometry location request of the gnome-terminal To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1925732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925732] Re: new in 21.04: gnome window manager ignores the --geometry location request of the gnome-terminal
"* 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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925732 Title: new in 21.04: gnome window manager ignores the --geometry location request of the gnome-terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1925732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925732] Re: new in 21.04: gnome window manager ignores the --geometry location request of the gnome-terminal
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 will keep track of its status for you." -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925732 Title: new in 21.04: gnome window manager ignores the --geometry location request of the gnome-terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1925732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925732] Re: new in 21.04: gnome window manager ignores the --geometry location request of the gnome-terminal
"... 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 that project or during the project. This is a design bug of Wayland, what needs to be fixed, regardless of the outcome of the test with "Xorg" (I will do after the funeral today). If there was no other protocol, if the Wayland was the only protocol, even in that case this is a very serious design bug. Hence I suggest to add "Wayland" to the "affects" list. Do I have to leave the Wayland world, and switch back to Xorg? But it was told, that Wayland is more advanced, that is the new direction. Is the new direction in 2021 that I can not control the location of a new windows from script? Then why it STILL is allowed, that we can control the location of a new window using a mouse? Is it possibble --- as a further enhancement --- to disable also the window positioning by the mouse? I do not find how to add "Wayland" to the "affects" list, help please. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925732 Title: new in 21.04: gnome window manager ignores the --geometry location request of the gnome-terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1925732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925823] Re: losts or ignore the newline character coming from mouse paste
bash --version gives: GNU bash, version 5.1.4(1)-release (x86_64-pc- linux-gnu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925823 Title: losts or ignore the newline character coming from mouse paste To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1925823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925823] [NEW] gnome-terminal losts or ignore the newline character coming from mouse paste
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 coloring, what is very disturbing when a command is not executed, but decorated in a funny way instead. This is new in 21.04, the dropping commands into a gnome-terminal worked fine in 20.10, ... ... and in the last 27 years of my linux usage. ** Affects: bash (Ubuntu) Importance: Undecided Status: New ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Also affects: bash (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/1925823 Title: gnome-terminal losts or ignore the newline character coming from mouse paste To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1925823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925732] [NEW] new in 21.04: gnome window manager ignores the --geometry location request of the gnome-terminal
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". "--geometry=GEOMETRY Set the window size as COLSxROWS+X+Y. For example, 80x24 or 80x24+200+200." The "+X+Y" part is ignored since I upgraded from 20.10 to 21.04 yesterday, just 4 hours after the official release. ** Affects: ubuntu Importance: Undecided Status: New ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Also affects: mutter (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/1925732 Title: new in 21.04: gnome window manager ignores the --geometry location request of the gnome-terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1925732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1288655] Re: Terminal height shrinks - repeatedly restored shorter than the previous height
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, unmaximize) shrinks from 80x42 to 78x40 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1288655 Title: Terminal height shrinks - repeatedly restored shorter than the previous height To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1288655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916890] [NEW] each maximisation + un-maximisation cycle of a gnome-termial windows will shrink the terminal by 1 row and by 1 column
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 LINES; prohlep@pc56:~$ resize COLUMNS=79; LINES=41; export COLUMNS LINES; prohlep@pc56:~$ resize COLUMNS=78; LINES=40; export COLUMNS LINES; prohlep@pc56:~$ My 20.10 is almost release default state, no extension, only a few kbd shortcuts, that's all. I use gnome shell with gnome-terminals. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Also 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/1916890 Title: each maximisation + un-maximisation cycle of a gnome-termial windows will shrink the terminal by 1 row and by 1 column To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1916890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen
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 the same disturbing setting, that DVI-0 connected primary 2560x1440+0+0 (in the reality this is my main monitor) DVI-1 connected 1680x1050+2560+504 (in the reality this is located as secondary) and almost everithing arrives to DVI-1, regardless how I started, from wich termial, Extremly disturbing, since I do not find any possibility to tell a program, to wich monitor to arrive. In addition to this, the terminal and the firefox arrives maximalised, and the do not know their suggested default size what is larger, thatn the size of the wrong target, --- --- since I have 2 monitors, I have to adjust all the window sizes by hand, as if it was a Windows. Since 1995, all my programs are started with suggested locations and sizes, what does not work any longer ... OK, one thing works, because the main monitor is on the left side: if I tell gnome-terminal --geometry=+0+0 but the gnome-terminal --geometry=-0+0 it will give a maximalised trash on the wrong monitor, and forgets the default nom-maximalised size as well. In addition to this, EACH maximalization and non-maximalisation cycle SHRINKS the size of the gnome-erminal by one row and one column: 80 ... 79 ... 78 ... This is an other bug, but I mention here because it might happen the same problem: the window size and location subsystem has serious problems ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1888098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890725] Re: wacom tablet disturbs unity background, color scheme and keyboard shortcuts
the problem is still there, over the x11 based unity -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890725 Title: wacom tablet disturbs unity background, color scheme and keyboard shortcuts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-unity-meta/+bug/1890725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890725] Re: wacom tablet disturbs unity background, color scheme and keyboard shortcuts
If Wacom is plugged, then neither the settings / wacom tab comes up, but if the Wacom tablet is NOT plugged, then the settings / wacom tab comes up and reports that currently no Wacom device is connected. Unity shell is essentially disturbed with the Wacom tablet mentioned above, while Gnome shell works well. ** Also affects: ubuntu-unity-meta 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/1890725 Title: wacom tablet disturbs unity background, color scheme and keyboard shortcuts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-unity-meta/+bug/1890725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890725] Re: wacom tablet disturbs unity background, color scheme and keyboard shortcuts
If Wacom is plugged, then neither "the text entry / switch input source" works, even if I want to switch the input source by mouse in the upper right corner. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890725 Title: wacom tablet disturbs unity background, color scheme and keyboard shortcuts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1890725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890725] [NEW] wacom tablet disturbs unity background, color scheme and keyboard shortcuts
Public bug reported: If I make a fresh 20.04 install from scratch, with the default gnome desktop, then plugging the wacom tablet below does not disturb the background, color scheme and keyboard shortcuts, like ctrl+alt+T give a terminal. But as soon as I upgrade this install with ubuntu-unity-desktop, and I switch to use the corresponding LightDM, then the "system setting" (in the upper right corner) is not able to handle the background (to set it to a solid color, or a photo, it remains solid black), it is not able to set the theme from the default dark to the lighter "radiance", and the worst of all: the former keyboard bindings, like "ctrl+alt+T gives a terminal" are no longer executed, they are still there in the listing, we can change to what keystroke is e browser or a terminal is bind, but will not work if I press the usual combination. However, the tablet itself works immediately like a dumb mouse device. This tablet is according to lspci: ID 056a:0378 Wacom Co., Ltd CTL- 6100WL [Intuos BT (M)] Somehow plugging the Wacom to USB disables, paralyses a nice diverse selection of features, but only in the case of Unity, and NOT in the case of the default Gnome. ** Affects: 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/1890725 Title: wacom tablet disturbs unity background, color scheme and keyboard shortcuts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1890725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770407] Re: No device found : yet demonstrably present
ID 046d:08ad Logitech, Inc. QuickCam Communicate STX 640x480 works with cheese, if export LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libv4l/v4l1compat.so export XLIB_SKIP_ARGB_VISUALS=1 cheese but the same trick did not help in case of MicroSoft Teams / Meeting, what I should use with video, not only with voice. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770407 Title: No device found : yet demonstrably present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770407] Re: No device found : yet demonstrably present
I have very similar problem: ID 046d:08ad Logitech, Inc. QuickCam Communicate STX 640x480 works with guvcview vlc v4l2:///dev/video0 does NOT work with cheese (not a real problem for me) MicroSoft Teams / meeting (real problem as distant teaching due Covid19) 5.4.0-37-generic #41-Ubuntu SMP Wed Jun 3 18:57:02 UTC 2020 x86_64 x86_64 x86_64 I did not use this cam before, I tried only now in 20.04 focal edition. As a reference, ID 046d:0825 Logitech, Inc. HD Webcam C270 1280x720 works with cheese and MicroSoft Teams as well, not only with guvcview and vlc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770407 Title: No device found : yet demonstrably present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882939] [NEW] efi_no_storage_paranoia
Public bug reported: Due to an EFI implementation error spreaded wide a half or full decade ago, I need kernel parameter "efi_no_storage_paranoia" during the (grub efi) installation for my Lenovo Edge E125 (ThinkPad), --- and according to internet quite a lot of bit older, first generation of EFI motherboards and laptops are also effected in exactly the same way. The usual symptom is that: warning: Cannot set EFI variable Boot000A. warning: vars_set_variable: write() failed: No space left on device. error: failed to register the EFI boot entry: No such file or directory. Additional symptom is that after RE-FLUSHING the bios for the same version, the first efi install is successful, free from this error but all the later efi installations have this error The reason is that each of this early EFI bios impementations report a NV-storages usage over 50%, and kernel without "efi_no_storage_paranoia" does not want to register the fresh install Each of the ubuntu desktop, ubuntu server and debian install cd/usb resource is affected with this error, and each of these works without error, if I add the kernel parameter "efi_no_storage_paranoia" at boot time, using the edit function of the grub. Suggestion: there should be an additional grub menu item, offering this small extra feature Perhaps there could be an extra safety measure, that the installer rejects to make use of this possibility, if there is no linux item among the efi-variables what can be deleted. I.e.: this extra possibility should be allowed only if the registration of the new item can replace one of the previous linux items of any distribution, or at least an Ubuntu or Debian. ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Attachment added: "the error show in an already installed debian, looks same in en already installed ubuntu" https://bugs.launchpad.net/bugs/1882939/+attachment/5382416/+files/lenovo_e125_grub.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882939 Title: efi_no_storage_paranoia To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1882939/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761977] Re: Bug 1761977
Many thanks, Péter. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761977 Title: geogebra fails to start due to Java casting problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geogebra/+bug/1761977/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1761977] Re: geogebra fails to start due to Java casting problem
"GeoGebra 4.0.34.0 (Debian version 4.0.34.0+dfsg1-6) 22 June 2012 Java 11.0.1" starts correctly in my Cosmic 18.10 Ubuntu, ... sorry I have no 18.04 installation to try out. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761977 Title: geogebra fails to start due to Java casting problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geogebra/+bug/1761977/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755106] Re: Bug 1755106
The solution provided by Khurshid Alam seems to work correctly in the last 25 days. Day by day more likely, that the problem is solved. Many tanks for the help! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755106 Title: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1755106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755106] Re: Bug 1755106
The problem with the nature below is still there after upgrading to 18.10. > The custom binding of Ctrl+Alt+G to > >gnome-terminal --geometry=80x99-0+0 > > is missing more frequently, than the custom binding of > Ctrl+Alt+Backspace to > >gnome-session-quit --power-off > > Does this help to locate the problem? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755106 Title: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1755106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755106] Re: Bug 1755106
The custom binding of Ctrl+Alt+G to gnome-terminal --geometry=80x99-0+0 is missing more frequently, than the custom binding of Ctrl+Alt+Backspace to gnome-session-quit --power-off Does this help to locate the problem? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755106 Title: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1755106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755106] Re: Bug 1755106
The problem is still there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755106 Title: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1755106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1738500] Re: Ctrl+Shift+E not working in Bionic
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 ARE OBSCURED by this Emoji Choice. We are working hard using linux, and not sending continuosly smileys. It is not acceptable, that for the sake of emojies a widely used shortcut is taken away from many productive applications. If someone knows which package is responsible for this diverting, bind this bug please to that package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738500 Title: Ctrl+Shift+E not working in Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1738500/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1738500] Re: Ctrl+Shift+E not working in Bionic
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 of an "after intallation" script, since I don't know how to do it from terminal by issueing a command. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738500 Title: Ctrl+Shift+E not working in Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1738500/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1738500] Re: Ctrl+Shift+E not working in Bionic
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738500 Title: Ctrl+Shift+E not working in Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1738500/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1738500] Re: Ctrl+Shift+E not working in Bionic
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 of "Export As ..." menu item "since the Big Bang". Who at all thinks that he or she is allowed to divert important shortcuts? Where it can be configured back, preferably from a bash terminal? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738500 Title: Ctrl+Shift+E not working in Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1738500/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1738500] Re: Ctrl+Shift+E not working in Bionic
** Also affects: gimp (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/1738500 Title: Ctrl+Shift+E not working in Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1738500/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787916] Re: Bug 1787916
*** This bug is a duplicate of bug 1772374 *** https://bugs.launchpad.net/bugs/1772374 Thanks for the help, I hope it will solve the problem in a future release. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787916 Title: 18.04 erasing all reinstall on uefi fails to install the boot loader To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1787916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787916] Re: Bug 1787916
I have the same problem on a Lenovo Thinkpad E125 as well. Assuming the uefi and root partitions are /dev/sda1 and /dev/sda2 respectively, the following helped in the case of Lenovo, but did not help in case of Asus Eee PC 1215B : boot in UEFI the 18.04.1 pen, continue in "try" mode and then in a terminal after "sudo -s" mount "/dev/sda2 /mnt mkdir --parents /mnt/boot/efi mount "/dev/sda1 /mnt/boot/efi for x in dev dev/pts proc sys ; do mount -B /$x /mnt/$x done modprobe efivars apt-get install --reinstall grub-efi-amd64-signed grub-install --no-nvram --root-directory=/mnt chroot /mnt update-grub cd /mnt/boot/efi/EFI cp -R ubuntu/* BOOT/ cd BOOT cp grubx64.efi bootx64.efi In case of Asus 1215B the following did help: boot in UEFI the 18.04.1 pen, continue in "try" mode and then in a terminal after "sudo -s" add-apt-repository ppa:yannubuntu/boot-repair apt-get update apt-get install -y boot-repair boot-repair Now the both old (2011 = early UEFI) laptops boot 18.04 in UEFI mode. It would be nice, if the 18.04 install media would have this fairly universal, not really laptop-specific knowledge, ... what I learned from various internet resources. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787916 Title: 18.04 erasing all reinstall on uefi fails to install the boot loader To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1787916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787916] [NEW] 18.04 erasing all reinstall on uefi fails to install the boot loader
Public bug reported: There was already a working 18.04 in UEFI mode. I just reinstalled it using an USB stick with UEFI boot, asking the installer to totally erase the target disk and to make a default system. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Mon Aug 20 11:50:00 2018 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787916 Title: 18.04 erasing all reinstall on uefi fails to install the boot loader To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1787916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755106] Re: Bug 1755106
The problem is still there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755106 Title: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1755106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755106] Re: Bug 1755106
My problem is NOT whether the custom shortcuts work just after setting them or I need a log-out/log-in cycle. The problem is, that a half dozen times (= boots, usually in the morning) the ctrl-alt-g works, and then for one or two boots fails to load, and then agin works for a few days (this computer not running when I sleep). I understand, that ctrl-alt-backspace MAY be affected by the x-server. But the ctrl-alt-g is a "virgin use" of that keystroke, and they are always together good or bad, they behave never different. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755106 Title: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1755106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755106] Re: Bug 175510 custom-keybindings fails to load
Now I am just reading the referred similar bug: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1435020 I have the very similar problems. In addition to that, when I applied the suggested "unity-settings-daemon --replace" command, then not only my custon settings, but the usual Ctrl-Alt-T terminal short cut also went away. But interestingly not everything went away, for example the Alt-` is still working (switch between the windows of the same binary), this is not in the custom section, and formerly it was a default setting. prohlep@pc56:~$ ps ax | grep settings-daemon 1934 ?Sl 0:00 /usr/lib/unity-settings-daemon/unity-fallback-mount-helper 3287 pts/0Sl+0:00 unity-settings-daemon --replace 3296 pts/0Sl+0:00 /usr/lib/unity-settings-daemon/usd-locate-pointer 3340 pts/1S+ 0:00 grep settings-daemon prohlep@pc56:~$ unity-settings-daemon --replace ** (unity-settings-daemon:3287): WARNING **: 09:12:51.381: Failed to load PNP ids: Failed to open file “/usr/share/hwdata/pnp.ids”: No such file or directory (unity-settings-daemon:3287): Gtk-WARNING **: 09:12:51.462: Theme parsing error: gtk-main.css:73:38: Failed to import: Error opening file /usr/share/themes/Radiance/gtk-3.20/apps/gnome-builder.css: No such file or directory ** (unity-settings-daemon:3287): WARNING **: 09:12:51.539: Failed to load PNP ids: Failed to open file “/usr/share/hwdata/pnp.ids”: No such file or directory ** (unity-settings-daemon:3287): WARNING **: 09:12:51.539: Failed to load PNP ids: Failed to open file “/usr/share/hwdata/pnp.ids”: No such file or directory (unity-settings-daemon:3287): media-keys-plugin-WARNING **: 09:12:51.552: Grab failed for some keys, another application may already have access the them. (usd-locate-pointer:3296): Gtk-WARNING **: 09:12:51.559: Theme parsing error: gtk-main.css:73:38: Failed to import: Error opening file /usr/share/themes/Radiance/gtk-3.20/apps/gnome-builder.css: No such file or directory (unity-settings-daemon:3287): Gtk-WARNING **: 09:12:51.566: Theme parsing error: gtk-main.css:73:38: Failed to import: Error opening file /usr/share/themes/Radiance/gtk-3.20/apps/gnome-builder.css: No such file or directory ** (unity-settings-daemon:3287): WARNING **: 09:12:51.582: Failed to load PNP ids: Failed to open file “/usr/share/hwdata/pnp.ids”: No such file or directory (unity-settings-daemon:3287): GLib-GIO-CRITICAL **: 09:13:15.145: g_dbus_proxy_call_internal: assertion 'G_IS_DBUS_PROXY (proxy)' failed here the last log item shows what happens, when I wist to refresh the key binding in the custom section. Everytime I try to set a keybinding this gets printed. Also the line "(unity-settings-daemon:3287): media-keys-plugin-WARNING **: 09:12:51.552: Grab failed for some keys, another application may already have access the them." is interesting, ... is this because I started "unity-settings-daemon --replace" manually, and therfore now the original is running and my new command is also running? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755106 Title: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1755106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755106] Re: Bug 175510 custom-keybindings fails to load
In my case, I have the following result: prohlep@pc56:~$ G_MESSAGES_DEBUG=all unity-settings-daemon --replace & [1] 2773 prohlep@pc56:~$ (unity-settings-daemon:2773): Gtk-WARNING **: 09:06:24.599: Theme parsing error: gtk-main.css:73:38: Failed to import: Error opening file /usr/share/themes/Radiance/gtk-3.20/apps/gnome-builder.css: No such file or directory ** (unity-settings-daemon:2773): WARNING **: 09:06:24.746: Failed to load PNP ids: Failed to open file “/usr/share/hwdata/pnp.ids”: No such file or directory ** (unity-settings-daemon:2773): WARNING **: 09:06:24.849: Failed to load PNP ids: Failed to open file “/usr/share/hwdata/pnp.ids”: No such file or directory ** (unity-settings-daemon:2773): WARNING **: 09:06:24.849: Failed to load PNP ids: Failed to open file “/usr/share/hwdata/pnp.ids”: No such file or directory (unity-settings-daemon:2773): media-keys-plugin-WARNING **: 09:06:24.938: Grab failed for some keys, another application may already have access the them. ** (unity-settings-daemon:2773): WARNING **: 09:06:24.942: Failed to load PNP ids: Failed to open file “/usr/share/hwdata/pnp.ids”: No such file or directory (unity-settings-daemon:2773): Gtk-WARNING **: 09:06:24.960: Theme parsing error: gtk-main.css:73:38: Failed to import: Error opening file /usr/share/themes/Radiance/gtk-3.20/apps/gnome-builder.css: No such file or directory (usd-locate-pointer:2785): Gtk-WARNING **: 09:06:24.991: Theme parsing error: gtk-main.css:73:38: Failed to import: Error opening file /usr/share/themes/Radiance/gtk-3.20/apps/gnome-builder.css: No such file or directory -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755106 Title: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1755106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755106] Re: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load
Exactly the same symptoms with SHIFT instead of ALT. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755106 Title: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1755106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755106] Re: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load
https://pastebin.ubuntu.com/p/nrtyQZMPdB/
In my case the primary key is the ALT, actually the left alt.
As far as I know, no usage collision of alt-ctrl-g, alt-ctrl-backspaces,
...
I do not use any other setting manager. The problem is ther if I do it
'by hand' in Unity control center. However normally I set up almost
everything with script, here is the shortcut setting part:
CK='/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings'
DCONFWRITE='dconf write '
DCONFWRITE+="${CK}"
${DCONFWRITE}/custom0/name "'unset'"
${DCONFWRITE}/custom0/command "'unset'"
${DCONFWRITE}/custom0/binding "'unset'"
${DCONFWRITE}/custom0/name "'gnome-terminal --geometry=80x99-0+0'"
${DCONFWRITE}/custom0/command "'gnome-terminal --geometry=80x99-0+0'"
${DCONFWRITE}/custom0/binding "'g'"
${DCONFWRITE}/custom1/name "'unset'"
${DCONFWRITE}/custom1/command "'unset'"
${DCONFWRITE}/custom1/binding "'unset'"
${DCONFWRITE}/custom1/name "'gnome-session-quit --power-off'"
${DCONFWRITE}/custom1/command "'gnome-session-quit --power-off'"
${DCONFWRITE}/custom1/binding "'BackSpace'"
${DCONFWRITE} "['${CK}/custom0/','${CK}/custom1/']"
unset DCONFWRITE
unset CK
However, the problem is still there, if I do it by hand, and during the
debug command the setting is recorded only and it comes to alive after a
logout/login cycle.
I am ready to make further experiments, no comes the CTRL+SHIFT instead
of CTRL+ALT, how you have just suggested, ... many thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755106
Title:
/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/
fails to load
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1755106/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755106] Re: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load
First of all, many thanks for your help.
https://pastebin.ubuntu.com/p/nrtyQZMPdB/plain/
Firs I disabled the keystrokes at the two items in question, then I
removed the items as well.
Then I re-entered the two items ('gnome-session-quit --power-off' and
'gnome-terminal --geometry=80x99-0+0') and then configured keystrokes
for them ('BackSpace' and 'g').
The result is, that whenever I do this, the two keystrokes does NOT come
back until I logout and login again.
Later I discovered, that as soon as I commit the command "unity-
settings-daemon -r --debug", the keystrokes in question disappear.
Even later I discovered, that not only the custom bingins go away with
committing the debug command, but the redefined normal bindings: I like
the web browser (launchers / launc web browser) at 'f',
but it is not there anymore if I start the debug command.
An interesting side-effect is, that when the problem during debug
command arise, then the decoration of the Unity control center changes
from my usual Radiance back to the default Ambiance.
After logging out and back, the decoration and all the redefined or
custom bindings come back.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755106
Title:
/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/
fails to load
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1755106/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755106] Re: Bug 1755106
The problem is still there, and sometimes I need two reboots in order to get rid of the situation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755106 Title: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1755106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755106] Re: Bug 1755106
Will anyone ever tell me what to look for when the problem occurs? I did a fresh reinstall of the whole 18.04 system from scratch, but the problem is still there. I could provide more information if someone tells me what to look for. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755106 Title: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1755106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755106] /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/
The problem is much more frequent in the last few days. What shall I test or record if this problem occures next? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755106 Title: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1755106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1755106] Re: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load
The problem is still there, twice a week approx, today 3 out of the 4 reboots were erratic wrt custom keybindings. Could anybody tell me, what kind of data and information should I collect, when next time the error occurs? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755106 Title: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1755106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1761977] Re: geogebra fails to start due to Java casting problem
> Will this bug be fixed in Ubuntu 18.04 LTS? > > Title: > geogebra fails to start due to Java casting problem > > Status in geogebra package in Ubuntu: > Fix Released > Status in geogebra package in Debian: > Fix Released Bad status information: "Status in geogebra package in Ubuntu: Fix Released", ... because it is NOT fixed, the error is still there: May 23, 2018 1:56:45 PM STDERR: java.lang.ClassCastException: java.base/jdk.internal.loader.ClassLoaders$AppClassLoader cannot be cast to java.base/java.net.URLClassLoader While accordint to the suggested https://wiki.ubuntu.com/StableReleaseUpdates description, "2. When 2.1. High-impact bugs ... Bugs which represent severe regressions from the previous release of Ubuntu. This includes packages which are totally unusable, like being uninstallable or crashing on startup. ...". Since the Geogebra fails to start successfully, I think this is a "High-impact bug", ... what can not wait until 18.10 --- espcially if the fix in Debian is already released. I would be happy to know, how to import a bug fix from Debian to Ubuntu, but I have no kind of experience in handling official release packages. Reading fully the suggested https://wiki.ubuntu.com/StableReleaseUpdates description, I have still NO IDEA how to do it. What is faster, either to show me how I could do it, or to do it without me? Anyways, I thank for everybody, who collectively give us the free softwares as a high quality present. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761977 Title: geogebra fails to start due to Java casting problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geogebra/+bug/1761977/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1755106] Re: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load
The problem is still there. Can someone tell me what kind of test should I do in case of Unity? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755106 Title: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1755106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1761977] Re: geogebra fails to start due to Java casting problem
> I have fixed this bug in Debian. Tanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761977 Title: geogebra fails to start due to Java casting problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geogebra/+bug/1761977/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1761977] Re: geogebra fails to start due to Java casting problem
> This problem also affects me. I have a fresh install of 18.04 and I get > the same error when trying to start geogebra. Thanks for your valuable contribution, because my concern was that perhaps my problem is caused by the fact, that my instal is NOT a fresh install of 18.04 but a distribution upgrade, and hence I just considered to try a clean fesh install. Thanks, you saved my time! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761977 Title: geogebra fails to start due to Java casting problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geogebra/+bug/1761977/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761977] Re: geogebra fails to start due to Java casting problem
just an other trial with the same result, see the attachment ** Attachment added: "/tmp/GeoGebraLog_wacljbsyto.txt" https://bugs.launchpad.net/ubuntu/+source/geogebra/+bug/1761977/+attachment/5105523/+files/GeoGebraLog_wacljbsyto.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761977 Title: geogebra fails to start due to Java casting problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geogebra/+bug/1761977/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761977] [NEW] geogebra fails to start due to Java casting problem
Public bug reported: geogebra fails to start due to Java casting problem ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: geogebra 4.0.34.0+dfsg1-4 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Sat Apr 7 13:36:55 2018 InstallationDate: Installed on 2017-07-13 (267 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: geogebra UpgradeStatus: Upgraded to bionic on 2018-03-09 (28 days ago) ** Affects: geogebra (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "/tmp/GeoGebraLog_vjrougnpbt.txt" https://bugs.launchpad.net/bugs/1761977/+attachment/5105519/+files/GeoGebraLog_vjrougnpbt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761977 Title: geogebra fails to start due to Java casting problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geogebra/+bug/1761977/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1755106] Re: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load
> if you are using unity then the issue is rather in unity-settings-daemon > and the gsd command I suggested are wrong OK, and can you tell me what kind of test should I do in case of Unity? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755106 Title: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1755106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755106] Re: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load
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 **: 23:34:37.681: Dropping
signal AcceleratorActivated of type (uuu) since the type from the
expected interface is (ua{sv})
(gsd-media-keys:2834): GLib-GIO-WARNING **: 23:34:44.777: Dropping
signal AcceleratorActivated of type (uuu) since the type from the
expected interface is (ua{sv})
DO I EXECUTE THE RIGHT OR SUITABLE TEST?
Tell me what to test next time?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755106
Title:
/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/
fails to load
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1755106/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755106] Re: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load
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' command='gnome-terminal --geometry=80x99-0+0' name='gnome-terminal --geometry=80x99-0+0' $ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755106 Title: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1755106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755106] Re: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load
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 return to bash prompt, and initially
gives no kind of messages. However, when I try any of the custom
keystrokes, or any of the usual but overridden keystrokes, then I get
the followings:
$ /usr/lib/gnome-settings-daemon/gsd-media-keys
(gsd-media-keys:2459): GLib-GIO-WARNING **: 22:32:43.149: Dropping
signal AcceleratorActivated of type (uuu) since the type from the
expected interface is (ua{sv})
(gsd-media-keys:2459): GLib-GIO-WARNING **: 22:32:57.476: Dropping
signal AcceleratorActivated of type (uuu) since the type from the
expected interface is (ua{sv})
(gsd-media-keys:2459): GLib-GIO-WARNING **: 22:33:01.756: Dropping
signal AcceleratorActivated of type (uuu) since the type from the
expected interface is (ua{sv})
(gsd-media-keys:2459): GLib-GIO-WARNING **: 22:33:02.460: Dropping
signal AcceleratorActivated of type (uuu) since the type from the
expected interface is (ua{sv})
(gsd-media-keys:2459): GLib-GIO-WARNING **: 22:33:04.076: Dropping
signal AcceleratorActivated of type (uuu) since the type from the
expected interface is (ua{sv})
(gsd-media-keys:2459): GLib-GIO-WARNING **: 22:33:04.500: Dropping
signal AcceleratorActivated of type (uuu) since the type from the
expected interface is (ua{sv})
(gsd-media-keys:2459): GLib-GIO-WARNING **: 22:33:04.804: Dropping
signal AcceleratorActivated of type (uuu) since the type from the
expected interface is (ua{sv})
(gsd-media-keys:2459): GLib-GIO-WARNING **: 22:33:05.675: Dropping
signal AcceleratorActivated of type (uuu) since the type from the
expected interface is (ua{sv})
(gsd-media-keys:2459): GLib-GIO-WARNING **: 22:37:17.075: Dropping
signal AcceleratorActivated of type (uuu) since the type from the
expected interface is (ua{sv})
(gsd-media-keys:2459): GLib-GIO-WARNING **: 22:37:26.746: Dropping
signal AcceleratorActivated of type (uuu) since the type from the
expected interface is (ua{sv})
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755106
Title:
/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/
fails to load
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1755106/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755106] Re: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755106 Title: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1755106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1758373] Re: bison -Wconversion warning
> In the future, please use `ubuntu-bug package-name` to report bugs. Thanks. > https://help.ubuntu.com/dev/ubuntu-help/report-ubuntu-bug.html.en Many thanks, not only for the help in changing the package for the report, but also for your comment, INDEED, it is much more simple to use the "ubuntu-bug package-name", thanks! Péter. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758373 Title: bison -Wconversion warning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bison/+bug/1758373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758373] [NEW] bison -Wconversion warning
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 alter its value [-Wconversion]
*yyssp = yystate;
^~~
y.tab.c:1028:25: warning: conversion to ‘long unsigned int’ from ‘long int’ may
change the sign of the result [-Wsign-conversion]
YYSIZE_T yysize = yyssp - yyss + 1;
^
$
I get this problem even in an almost empty grammar and minimal C source
frame for it, see the attachment: an example for minimal grammar and
minimal C frame ALREADY providing the error.
This is the error in case of my Ubuntu 18.04 ( bison --version = 3.0.4,
gcc --version = (Ubuntu 7.3.0-12ubuntu1) 7.3.0).
I could try Debian jessie, where I get exactly the same error at exactly
the same line position ( bison --version = 3.0.2, gcc --version =
(Debian 4.9.2-10+deb8u1) 4.9.2).
MY SUGGESTION: IF the bison developers are sure, that "yystate" and
"yyssp - yyss + 1" will always fit into "short int" or "long unsigned
int", THEN an explicit casting could be a solution. HOWEVER in case of
"yystate" it would be much more relaxing to make a decision whether it
should be an "int" or "short int".
The compilation commands are:
CCOPTS=''
CCOPTS+=' -std=c11'
CCOPTS+=' -Og -g'
CCOPTS+=' -Wabi'
CCOPTS+=' -Wfatal-errors'
CCOPTS+=' -Wall'
CCOPTS+=' -Wextra'
CCOPTS+=' -Wreturn-type'
CCOPTS+=' -Wconversion' ### bison has 2 conversion errors
CCOPTS+=' -fexceptions'
CCOPTS+=' -pedantic-errors'
CCOPTS+=' -fmax-errors=1'
rm -f y.output y.tab.h y.tab.c y.tab.o
bison --yacc --verbose -d "EXAMPLE_GIVEN_IN_THE_ATTACHMENT.y"
gcc -c ${CCOPTS} y.tab.c
** Affects: gnome-settings-daemon (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "minimal grammar with minimal C frame"
https://bugs.launchpad.net/bugs/1758373/+attachment/5088332/+files/bison_conversion_bug.y
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758373
Title:
bison -Wconversion warning
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1758373/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758373] Re: bison -Wconversion warning
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, change it to bison. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758373 Title: bison -Wconversion warning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1758373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755106] Re: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load
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 as well. Right now I have again a boot resulting no custom keybindings while all the other keybindings work. Again: "ps acuwx | fgrep gsd" is empty, and "journalctl | grep gsd" has no new entry since "Mar 12 08:47:48". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755106 Title: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1755106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1750846] Re: several g-s-d services are timing out when booting a live session
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- daemon/+bug/1755106/+attachment/5082123/+files/journalctl_key_failed.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1750846 Title: several g-s-d services are timing out when booting a live session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1750846/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755106] Re: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load
[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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755106 Title: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1755106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755106] Re: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load
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 days. However I found interesting lines in journalctl, hence I try to add the result of "journalctl | grep -i key | grep -i failed > journalctl_key_failed.txt" as an attachment. ** Attachment added: "journalctl | grep -i key | grep -i failed > journalctl_key_failed.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1755106/+attachment/5082123/+files/journalctl_key_failed.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755106 Title: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1755106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1756387] [NEW] Whish: a Unity like desktop bar in Gnome, or the default desktop manager of Ubuntu
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. I wish this in the default desktop manager, what is currently Gnome if I know correctly. The only reason why I still use the Unity is this feature what I find very comfortable. Can I configure the Gnome desktop this way right now, or it needs an amount of programming, and a better knowledge of the gnome system? If my wish is not only a simple configuration or a bit more only, and if the solution does not need far too deep knowledge of the Gnome desktop programming, then I am ready to program it, if someone gives me the references to concise reading materials enough for this work (I use and program computers since 1972 on regular daily base, and a I am fluent in unix/linux tools, including C/C++ what I teach regularly at the university). [[it was suggested me at the AskUbuntu, that this kind of wishes fits here to the bug reports better, and somebody with enough privileges will mark this as a "wish list" item]] ** Affects: gnome-settings-daemon (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/1756387 Title: Whish: a Unity like desktop bar in Gnome, or the default desktop manager of Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1756387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755106] Re: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load
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" is empty. Interestingly the output of "journalctl | grep gsd-media-keys" remained exactly the same, as 3 days before, no new entry. But none of the two user defined shortcuts work, while all the usual system default shortcuts work. I welcome further test suggestions in order to be prepared if next time the issue appears. One thing is interesting, that just after updating to 18.04, the frequency of the issue became high for a few days, and as soon as I submitted this issue, I had to wait 3 days (4 booting) in order to get the issue again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755106 Title: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1755106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755106] Re: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load
"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 before the first entry, Mar 10): Mar 10 19:30:35 pc56 dbus-daemon[884]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus- org.freedesktop.hostname1.service' requested by ':1.116' (uid=125 pid=8253 comm="/usr/lib/gnome-settings-daemon/gsd-media-keys " label="unconfined") Mar 10 19:58:38 pc56 dbus-daemon[883]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus- org.freedesktop.hostname1.service' requested by ':1.127' (uid=125 pid=5326 comm="/usr/lib/gnome-settings-daemon/gsd-media-keys " label="unconfined") Mar 10 19:59:07 pc56 gsd-media-keys[5326]: Error releasing name org.gnome.SettingsDaemon.MediaKeys: The connection is closed Mar 11 14:39:51 pc56 dbus-daemon[903]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus- org.freedesktop.hostname1.service' requested by ':1.115' (uid=125 pid=3011 comm="/usr/lib/gnome-settings-daemon/gsd-media-keys " label="unconfined") Mar 12 08:47:22 pc56 dbus-daemon[884]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus- org.freedesktop.hostname1.service' requested by ':1.121' (uid=125 pid=5137 comm="/usr/lib/gnome-settings-daemon/gsd-media-keys " label="unconfined") "Do you have an active "gsd-media-keys" process when getting the issue?" I had no possibility to check it, because I had only two cold boots since the last "Mar 12 08:47:22" occurence of the problem, and the both vere error free. But I do not find the process in question, do I test it correctly? : ps auxw | grep gsd-media-keys -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755106 Title: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1755106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755106] Re: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load
What kind of information shall I attach? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755106 Title: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1755106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
