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
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
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
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
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 ch
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
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
*** 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 maximisa
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 notifi
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/b
** 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
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
** 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
** 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
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
"* 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 subscribe
** 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 locat
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
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
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
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
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
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
shortcu
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:
** 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
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
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
*** 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
"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
"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
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
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
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
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
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 p
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
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 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
> 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 Ubu
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/me
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 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
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 ab
> 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
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: amd
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 me
*** This bug is a duplicate of bug 1552577 ***
https://bugs.launchpad.net/bugs/1552577
"Comment here only if you think the duplicate status is wrong.", OK I do
it.
Because that bug is "Crash displayed after logging in.".
And this bug is: apport-gtk crash IF no running firefox, and the apport
*** This bug is a duplicate of bug 1552577 ***
https://bugs.launchpad.net/bugs/1552577
Half of this bug is the duplicate of https://bugs.launchpad.net/bugs/1754885
and NOT of https://bugs.launchpad.net/bugs/1552577 SINCE in 1552577 and 1754885
the situations what caus the problems are differe
Public bug reported:
$ 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
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 not
"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
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
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.
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
[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
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
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
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
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
> 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
"ubunt
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/175
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
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-de
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/bu
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
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 generati
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
C
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
"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://bug
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://bu
> 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 u
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
*** 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.launch
** 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 ab
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
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 t
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
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 A
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
ProcVersionSig
> 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
Rel
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 Ubunt
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
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
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 ab
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-da
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
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
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
T
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
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
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
I have just installed the kernel package:
linux-
image-3.19.0-031900rc3-generic_3.19.0-031900rc3.201501060135_amd64.deb
and it does NOT work, it showes the same, original problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
I have just tried the kernel given in your comment #52:
linux-image-3.16.0-29-generic_3.16.0-29.39~lp1386534v1_amd64.deb
linux-image-extra-3.16.0-29-generic_3.16.0-29.39~lp1386534v1_amd64.deb
It WORKS, ther is NO view crash on X strartup, I use it now for this
report:
Linux pc56 3.16.0-29-gener
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
> 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
> 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
> 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
Tahks again, I have just upgraded to Ubuntu 15.04, and
the kernel included in it works without radeon.dpm=0.
3.19.0-15-generic #15-Ubuntu SMP Thu Apr 16 23:32:37 UTC 2015 x86_64
x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
1 - 100 of 177 matches
Mail list logo
