https://github.com/mate-desktop/caja/issues/1704
stupid Linux distro release cycles make important fixes like this take a
million years... And a few OS upgrades smh.
** Bug watch added: github.com/mate-desktop/caja/issues #1704
https://github.com/mate-desktop/caja/issues/1704
--
You received
Funny, I just came back to post that after all I've come to think it's
something to do the way platform (GTK et al) libs are built in Ubuntu
(Debian too?).
Because for me even the Arch binary exibits (on 22.04) the same broken
behaviour.
BTW after this bug is "initiated" (by opening the torrent p
FWIW, the Debian Sid package transmission-gtk_3.00-2.1_amd64.deb also
exhibits this behaviour for me (Ubuntu MATE 22.04). Couldn't find a
relevant bug report in the Debian BTS though.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to transm
Dupe of
https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1969315
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to transmission in Ubuntu.
https://bugs.launchpad.net/bugs/1979143
Title:
Segmentation fault after UI elements mis
Sure enough I hit the problem with LANGUAGE=en_US transmission-gtk
http://file-
st06.karelia.ru/7nqk5q/9b587eaf2d8bdc4c751ca979bbb321aa/a186e8a2a0f5d8d1249ad69c8a6648f4/1.png
I've noticed that the labels change to this mess in a fraction of a
second after the widgets are drawn.
And there are tho
It's not about a specific dialog or menu, it's like the translation
strings are all over the place getting assigned to random
buttons/places/whatever even in the file chooser dialog (guess it uses
the GTK3 default one). E.g. a sentence reporting free space (or some
such) gets assigned to a director
>A workaround is to use transmission-qt
Some workaround...
And yes it does spew all these errors for me as well. Ultimately it just
crashed.
I fully understand everything and all and I do try to withhold from
ranting/ whining especially towards a "freebie" service, but managing to
make a somethi
Did the old patch work for you? I mean could you switch the layout
pressing Ctrl while combos like Ctrl-S also worked as expected?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/3681
(In reply to Serge Roussak from comment #146)
> Try, please, apply your patch, assign the left Ctrl as switching key and
> then to save something in the kate editor (or other) using Ctrl+S...
You mean to say the new patch doesn't work for you? Please be more
clear.
--
You received this bug notif
(In reply to Serge Roussak from comment #148)
> Yes, exactly. If I assign the left Ctrl as the switching key, then if I try
> to save a file in a text editor with the Ctrl+S, I got the "s" char in the
> file.
And the layout switching - does it occur when you press Ctrl+s? Could
you please test wit
(In reply to Serge Roussak from comment #152)
> (In reply to Oleg from comment #151)
> > Did the old patch work for you? I mean could you switch the layout pressing
> > Ctrl while combos like Ctrl-S also worked as expected?
>
> Which patch do you mean when you say "old"?
The one that was made for
сАлюшн пересобрать руками с патчем? хабра такая хабра.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1683383
Title:
Keyboard layout change on hotkeys press instead of release and
well yeah more than a couple. I actually remember when I got fed up with
this and went looking on the net what can be done and later found out
that Ubuntu would accept the patch - I was on another distro then. just
don't remember when exactly.
I do the 10 fingers typing but even if you don't it's
Not exactly a bug, it's just how it works by default and that is what the xkb
specs supposedly say. So this behavior dates way back certainly more that 15
yrs ))
And the fix was incorporated by Ubuntu only a couple of yrs ago certainly not
in 2002 )))
The 'workaround' suggested above is what I
Thats the problem - the old patch doesn't work for the newer Xorg
server.
AFAIU the upstream won't accept this anyway.
Thus it's the matter of testing the patch and getting it into Ubuntu. AFAIK
Ubuntu was the only major distro that applied the old patch. Was yet another
reason to use it.
--
Y
Timo Aaltonen (tjaalton) wrote 10 hours ago:#3
And if you had a look at the upstream bug you'd see that the patch doesn't
work. It needs to get upstream first anyway.
---
1) It's just one (incomplete) report that it doesn't. I'll try the patch myself
soon.
2) The
I see the patch's been dropped for zesty
changelog.Debian for xserver-xorg-core says:
xorg-server (2:1.19.3-1ubuntu1) zesty; urgency=medium
* 208_switch_on_release.diff: Dropped, doesn't work with 1.19.
There's a new patch posted to the corresponding bug on freedesktop
https://bugs.freedesktop.
I'v just installed Ubuntu Mate 17.04 and this patch doesn't appear to work
anymore - suspect it's because Xorg has moved from evdev to libinput for
handling the issue of input.
Really would like to bring the old behavior back. If anyone knows of a solution
I'd be grateful if you point me at it.
18 matches
Mail list logo
