This bug disappeared in my case, just when I switched to 2204 Jammy. I
made a fresh install from scratch, not a dist-upgrade only.
Is there anybody who still has this bug in Jammy, if his/her system is a
fresh install from scratch?
--
You received this bug notification because you are a member
tags: added: impish
** Tags added: impish
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1888098
Title:
Ubuntu 20.04 gnome-shell places windows on second screen when started
*** 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 Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.l
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 Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1925732
Title:
gnome-terminal ignores
tags:added: impish
** Tags added: impish
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1925732
Title:
gnome-terminal ignores the --geometry location requests
Status in gnome-termina
*** 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 Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1936238
Title:
Lock scr
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 Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1928317
Title:
window focus is l
tags:added: impish
** Tags added: impish
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1928317
Title:
window focus is lost after blank screen
Status in gnome-shell package in U
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 Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.laun
** 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
** 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 Desktop
Packages, which is subscribed to mutter in Ubunt
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 w
** 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 Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs
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 Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https
The problem is still there.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1888098
Title:
Ubuntu 20.04 gnome-shell places windows on second screen when started
from primary scre
*** 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 Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1916890
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
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 repo
"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 doe
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 Desktop
Packages, which is subscribed to gnome-ter
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-term
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
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 t
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 n
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 t
** Also affects: gnome-shell
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1925732
Title:
new in 21.04: gnome window manager ignor
"* 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 Desktop
Packages, which is subs
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
wi
"... 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
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
colo
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".
"--geometr
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, un
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 LINE
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
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 Desktop
Packages, which is subscribed to unity-settings-daemon in
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
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 mem
The problem is still there.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1755106
Title:
/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/
fails to lo
The problem is still there.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1755106
Title:
/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/
fails to lo
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 com
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 usu
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/Rad
Exactly the same symptoms with SHIFT instead of ALT.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1755106
Title:
/org/gnome/settings-daemon/plugins/media-keys/custom-k
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. Howeve
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
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 Desktop
Packages, which is subscribed to unity-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1755106
Title:
/org/gn
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 memb
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 Desktop
Packages, which is subscribed to unity-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1755106
T
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 Deskt
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 Desktop
Packages, which is subscribed to unity-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1755106
Title:
/org/gnome
> 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 Desktop
Packages, which is subscribed t
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
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-ter
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 r
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 Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https
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, chang
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 alte
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
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/50821
[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 notific
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
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.
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" i
"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 bef
If the bug is that terrorists abruptly divert aircrafts into high buildings,
then the total disabling the whole air traffic IS NOT A BUGFIX, but it is a
TEMPORARY WORK AROUND only! The real bug fix is when you reopen the public
air traffic with a better safety configuration!
To disable the apparm
Public bug reported:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1386534
the problem in question is kernel dependent, I use ALWAYS the current NOT
necessairly LTS version,
at the moment the version 14.10
3.13.0-36-generic NO problem
3.13.0-37-generic problem in question
3.16.0-23-gene
There is a typo at the last item of the list above, so the correct list
is:
3.13.0-36-generic NO problem
3.13.0-37-generic problem in question
3.16.0-23-generic problem in question
3.16.0-24-generic problem in question
--
You received this bug notification because you are a member of Desktop
I have just received the new kernel 3.16.0-24-generic. but the problem
is still there.
3.13.0-36-generic NO problem using the SAME system and config as in the
problematik 3 other cases below:
3.13.0-37-generic problem in question
3.16.0-23-generic problem in question
3.16.0-23-generic problem i
WARNING: the apport above is with the kernel 3.13.0-36-generic, where
there is no problem (see the origonal post), hence it is useful only for
getting the configuration of my machine.
In case of 3.16.0-23-generic I am not able to get a non-blank X neither
a readable console, hence I can not provid
apport information
** Attachment added: "LightdmGreeterLogOld.txt"
https://bugs.launchpad.net/bugs/1386534/+attachment/4247523/+files/LightdmGreeterLogOld.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bu
apport information
** Attachment added: "LightdmGreeterLog.txt"
https://bugs.launchpad.net/bugs/1386534/+attachment/4247522/+files/LightdmGreeterLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.lau
apport information
** Attachment added: "LightdmLog.txt"
https://bugs.launchpad.net/bugs/1386534/+attachment/4247524/+files/LightdmLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bug
apport information
** Attachment added: "BootLog.txt"
https://bugs.launchpad.net/bugs/1386534/+attachment/4247517/+files/BootLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1386
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1386534/+attachment/4247518/+files/Dependencies.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "XorgLog.txt"
https://bugs.launchpad.net/bugs/1386534/+attachment/4247534/+files/XorgLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1386
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1386534/+attachment/4247530/+files/ProcModules.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1386534/+attachment/4247532/+files/UdevLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1386
apport information
** Attachment added: "UnitySupportTest.txt"
https://bugs.launchpad.net/bugs/1386534/+attachment/4247533/+files/UnitySupportTest.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launc
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1386534/+attachment/4247529/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "xdpyinfo.txt"
https://bugs.launchpad.net/bugs/1386534/+attachment/4247537/+files/xdpyinfo.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/13
apport information
** Attachment added: "LightdmDisplayLog.txt"
https://bugs.launchpad.net/bugs/1386534/+attachment/4247521/+files/LightdmDisplayLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.lau
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1386534/+attachment/4247526/+files/Lsusb.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1386534
apport information
** Attachment added: "xserver.outputs.txt"
https://bugs.launchpad.net/bugs/1386534/+attachment/4247538/+files/xserver.outputs.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchp
apport information
** Attachment added: "GconfCompiz.txt"
https://bugs.launchpad.net/bugs/1386534/+attachment/4247520/+files/GconfCompiz.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "DpkgLog.txt"
https://bugs.launchpad.net/bugs/1386534/+attachment/4247519/+files/DpkgLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1386
apport information
** Attachment added: "XorgLogOld.txt"
https://bugs.launchpad.net/bugs/1386534/+attachment/4247535/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bug
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1386534/+attachment/4247531/+files/UdevDb.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1386534
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1386534/+attachment/4247525/+files/Lspci.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1386534
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1386534/+attachment/4247527/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Tags added: apport-collected compiz-0.9 ubuntu utopic
** Description changed:
kernel 3.13.0-37 and 3.16.0-23, but not kernel 3.13.0-36
The phenomenon: just when the user interface starts at the end of the
Ununtu startup, the screen reamins in one solid color (very
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1386534/+attachment/4247528/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "Xrandr.txt"
https://bugs.launchpad.net/bugs/1386534/+attachment/4247536/+files/Xrandr.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1386534
Public bug reported:
kernel 3.13.0-37 and 3.16.0-23, but not kernel 3.13.0-36
The phenomenon: just when the user interface starts at the end of the
Ununtu startup, the screen reamins in one solid color (very light grey,
this is the everage of my colors), except for the topmost 3-4 scan
lines, whe
> What matters is that the *physical* keyboard shortcuts like Ctrl-Alt-T
> or Ctrl-C, Ctrl-V should just work no matter what the current layout is.
That is, what you say, that the four layers, i.e. the plain, the Alt, the
Ctrl and the Ctrl-Alt layers shuld be INDEPENDENT-ly configurable, and so
> There is a letter T in the Greek layout. Also, "terminal" in Greek
> translates to "τερματικό", both words start with a letter T. So, there
> is no excuse for the Ctrl-Alt-T Unity shortcut not working in Greek
> layout.
Greek T is NOT identical to Latin T, they are DISTINCT letters, which only
c
> Ctrl-Alt-T doesn't open Terminal in russian layout.
> However, with m17n workaround works OK.
Is there a latin letter T in the russian layout?
I mean a real latin letter T, and not only a correspondig cyrillic
letter.
This is the REAL question.
While it is not comfortable, but it is according
Dear Norbert!
> IMHO below. In present time many problems come from GNOME fast
> destruction and simpility/stupidity behavior. GNOME reduces its
> functionality very fast, and this changes are not tested for all
> regressions and bugs, this changes are not discussed with gnome-users.
> So many
Public bug reported:
My case is a close variant of the following two bugs closely related to
each other:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
daemon/+bug/885730
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/622965
My usual setting in "system settings
98 matches
Mail list logo
