vte-0.51.92 includes the workaround, so the warning is no longer
emitted.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744537
Title:
Allocating size to GtkBox 0x563732796750 without calling
18.04 Bionic, to be released tomorrow, ships bash-4.4.19. So if Kieran's
guess is correct then it should no longer crash there; Simon could you
please check this once you upgrade your system?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
Using vte 0.54.0:
Open gnome-terminal, and use its Terminal -> Set Character Encoding
menu to switch to another encoding. Switch back, then again to
something different.
gnome-terminal crashes.
Mainstream vte 0.54.1 fixes this issue. Could you please sync the
upgraded
I can confirm the issue is fixed in Cosmic beta. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743373
Title:
Combobox arrow and color are inverted
To manage notifications about this bug
Thanks guys! :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796422
Title:
Crash at encoding change
To manage notifications about this bug go to:
VTE does have code in place to support these variables and they work for
me. No need for reboot, not even to restart gnome-terminal, it should
pick up the change immediately.
It stops blinking the cursor when the focus is lost, and restarts
blinking it when the terminal is focused again. Are you
> cursor-blink-time: 1200
> cursor-blink-timeout: 1
> time=463 timeout=10
Oops, time should also match and it doesn't.
Can you confirm that blinking is pretty fast for you, that is, the
duration of an entire cycle (on + off phases) is a bit less than half a
second (463 ms, rather than 1.2
Thanks for the investigation!
In the mean time I've tried xfce, icewm and windowmaker –
/org/gnome/desktop/interface/cursor-blink* weren't used by VTE in any of
them, some hardcoded defaults were used. I guess some dconf or gsettings
daemon needs to be running to have the required binding in
Please understand: It's not that we (vte and gnome-terminal developers)
don't want to hear about it. We've heard about it and we are pretty
certain that this is a bug somewhere elsewhere. Vte's and gnome-
terminal's source code has absolutely no sign of treating ^ or any other
similar simple
Public bug reported:
When a combobox is opened, the list of entries is expected to be
positioned so that the currently selected one is exactly where that
value was shown before the list was opened.
See the two screenshots demonstrating the problem.
Note that even though the mouse pointer isn't
** Attachment added: "Before opening - good so far"
https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1795745/+attachment/5196123/+files/yaru-combobox-1.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "After opening - list is mispositioned"
https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1795745/+attachment/5196124/+files/yaru-combobox-2.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
> So the cause is that the MULTILINE flag is just that not set during
compilation?
Compilation of the regex when running tilix, not compilation of the
source code.
I have to admit I don't know what this regex is for, and whether
required in unpatched vte or not. If tilix is warning-free with
Fix: "I have to admit I don't know what this regex *flag* is for..."
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1666264
Title:
FFe: Update gnome-terminal to 3.24 and vte to 0.48
To manage
Public bug reported:
Open a new tab, and close any tab by clicking on the X button.
As of vte-0.54, lxterminal crashes.
Upstream bug and fix: https://github.com/lxde/lxterminal/issues/61
Mainstream release 0.3.2 fixes the bug, this is already packaged in
Debian unstable.
Please backport the
** Also affects: sakura (Ubuntu)
Importance: Undecided
Status: New
** Tags added: cosmic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790317
Title:
Crash with vte-0.54
To manage
Hi guys,
- Due to a change in vte-0.54 around the child-exited signal,
unfortunately lxterminal (LP: #1794440) and sakura (LP: #1790317) now
crash when a tab is closed by clicking on the X button. Luckily, a fix
is available for both of them. Could you please make sure to apply those
fixes?
- I
Debian report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909744.
** Bug watch added: Debian Bug tracker #909744
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909744
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
vte 0.54.0 to 0.54.2 suffers from a potential crash if the user closes a
terminal tab/window in gnome-terminal (or any other vte-based app) and
then modifies the cursor blinking settings.
Mainstream release 0.54.3 fixes this issue.
See
** Summary changed:
- Mouse scrolling no longer moves between tabs in gnome-terminal 2.30
+ Mouse scrolling no longer moves between tabs in gnome-terminal 3.30
** Description changed:
- In gnome-terminal 2.28 and earlier, scrolling with the mouse cursor over
+ In gnome-terminal 3.28 and
Most likely a duplicate of bug 1770507.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1817438
Title:
Error displaying icon for preference menu in title bar
To manage notifications about this bug
Please do not forget to remove the pcre patch from Tilix, see
https://bugs.launchpad.net/ubuntu/+source/tilix/+bug/1818991 - thanks!
** Also affects: tilix (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
The patch itself is misleadingly still present inside
tilix_1.8.9-1build1.debian.tar.xz. It's not mentioned in 'series'
though, which I believe means it's not applied? This might have confused
OP and me as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Thanks for the report! I can confirm this; forwarded to:
https://gitlab.gnome.org/GNOME/gnome-terminal/issues/81
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1816171
Title:
Show menubar by default
What problem did you experience at the first place? What's your goal
when you execute the mentioned command?
vte-2.91.sh was written for bash and zsh. You execute it with sh (dash).
Due to -n, the commands are not executed and thus it skips the bash/zsh
check and continues. Then it fails on a
I confirm the previous suspicion: This is _not_ an upstream bug.
Upstream gnome-terminal draws the scrollbar perfectly.
This bug is introduced by one of the Ubuntu patches.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks guys for having addressed this removal! I just came here to
report the same request.
> What bugs, specifically, do you believe justify this package's removal
from the archive?
Pretty much the entire set of bugs that have been fixed in VTE in the
last 8 years :-) including potential data
I've fired up Geany, and clicked on Terminal in the bottom left corner.
The presented terminal is libvte-2.91-0, as confirmed by `echo $VERSION`
reporting its version number.
Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896101
** Bug watch added: Debian Bug tracker #896101
Public bug reported:
Geany recommends to install libvte9.
Since Bionic, Geany has been compiled against GTK3. libvte9 uses GTK2.
Hence I'm pretty sure geany cannot make any use of it.
Please remove this outdated suggestion, or replace by the GTK3 based
libvte-2.91-0 if geany can use this latter
Public bug reported:
Please remove the ancient GTK2-based vte aka. libvte9{,-common} from
Eoan.
Upstream version has been unmaintained for about 8 years, development
continued in the GTK3 branch (vte2.91 aka. libvte-2.91-0).
Geany is the only package referring to it, and it also does
Public bug reported:
The package's (and some of the subpackages') description says:
"It is using only the GTK2 toolkit and therefore you need only the GTK2
runtime libraries to run Geany."
Since Bionic it's been compiled against GTK3, and accordingly, depends
on libgtk-3-0.
Please update the
Can't reproduce on disco.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740709
Title:
GtkSpinButton's '+' changes width if insensitive
To manage notifications about this bug go to:
> Starting a gnome-terminal from this terminal
Even executing "gnome-terminal" from an xterm goes through dbus/systemd.
"gnome-terminal" is just a controlling client that asks systemd to start
up a server which then displays the window and does all the rest.
Don't ask why the architecture is
GNOME Terminal 3.33.3 (VTE 0.57.3) implements BiDi support, according to
the proposal at https://terminal-wg.pages.freedesktop.org/bidi/ .
In alignment with Diego's comments and my responses to them, it
implements multiple modes. Shuffling the characters according to the
BiDi algorithm is enabled
VTE (libvte-2.91-0) version 0.56 mostly addresses this issue, spacing
marks are now combined as desired with the preceding base letter.
(Dotted circles still might be displayed around line wraps, as well as
under the rectangle cursor. For the latter problem, a workaround is to
choose a different
Public bug reported:
GtkSpinButton consists of a (typically numeric) input field, followed by
a '-' and finally a '+' sign. The width of the '+' sign shrinks a little
bit when you open the right-click context menu of the input field. It
shouldn't, it should have a constant width.
Happens with
GNOME Terminal 3.34 (as well as all other terminals using VTE 0.58)
support RTL.
These versions appear in Ubuntu 19.10 Eoan Ermine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/562130
Public bug reported:
It took about 30 minutes for me to download the packages for a distro
upgrade, yet it reports it took 6 seconds.
I'm upgrading from Disco to Eoan test version, using the command
sudo do-release-upgrade -d
Excerpt from the output:
7 packages are going to be removed. 81
** Also affects: apt (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/1843197
Title:
Time reported for having downloaded the packages is way off
Public bug reported:
Debian/Ubuntu package of gnome-terminal 3.34.0 moved the server binary
from /usr/lib/gnome-terminal to /usr/libexec.
The Ubuntu package ships a wrapper script as /usr/bin/gnome-terminal.
This one still looks for the server at its old location in
spawn_terminal_server().
> What the script does, since you ask,
Sorry for the loose phrasing. I was aware of the global picture, just
wasn't sure (and was lazy to investigate) when exactly a bug would be
triggered, i.e. when that code would be reached, which you answered:
> It is broken if you pass --app-id
Thanks for
> I found a hacky workaround - add this to your $PS1:
The workaround of resetting relevant settings from the prompt has
already been mentioned – although without showing a concrete example.
> Given how randomly it happens, I believe there is a real bug in
Terminator
I'm about 99.999% sure that
Public bug reported:
For some (unknown) reason, my unity-lens-* packages got uninstalled.
Trying to start unity-tweak-tool from a terminal under a Unity 7 session
gives this error in the terminal:
Error: schema com.canonical.Unity.ApplicationsLens not installed
and this in a popup window:
I forgot to explicitly say: The required packages, which should be listed in
the Depends field, are:
- unity-lens-applications
- unity-lens-files
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845737
Could you please execute this command? Do you see a cursor while it is
running?
echo -ne '\e[?25h\e]112\e\\'; sleep 1000
If not, then while the previous command is still running: Please open
gnome-terminal's preferences, click on your profile in the left-side
bar. Disable cursor blinking,
gnome-terminal itself doesn't do any authentication / PAM stuff. It's
probably an issue with `systemd --user` which launches 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/1835224
*** This bug is a duplicate of bug 1849285 ***
https://bugs.launchpad.net/bugs/1849285
This is fixed in official gnome-terminal 3.34.1, which is on its way to
appear as an eoan update. So let me mark this as duplicate.
** This bug has been marked a duplicate of bug 1849285
[SRU] 3.34.2
This should be a feature request against the command line shell, not the
terminal.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856438
Title:
auto suggest previously used commands
To manage
Autocompletion is done by the shell and its configs, not by the
terminal.
** Also affects: bash-completion (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Just wondering, Jeremy, in the opening report you said
> This update is required to update gnome-terminal to 3.34.2
but there's no gnome-terminal update in progress, is there?
gnome-terminal 3.34.1 fixes a problem with fullscreen terminals not
staying fullscreen at certain operations like font
Public bug reported:
Please update to gnome-terminal 3.34.1 (or .2) for eoan.
Or, at least, cherry-pick this trivial fix:
https://gitlab.gnome.org/GNOME/gnome-
terminal/commit/2cbc9e6b9be7f4d6b2d92b40e37ec687d36ce98d
A change in GTK triggered a bug in Terminal causing a pretty bad user
Filed bug #1848156, thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847850
Title:
Update vte2.91 to 0.58.2
To manage notifications about this bug go to:
Filed #1848156, thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847850
Title:
Update vte2.91 to 0.58.2
To manage notifications about this bug go to:
> Cursor color: checked, same colors
Well, if cursor color is the same as the default color then it is
requested to be invisible. What you need for the cursor color is
something very different from the defaults (e.g. the two colors
swapped).
Nitpicking: You shouldn't need to restart
0.58.1 and 0.58.2 each fix a crash. So indeed it would be great if you
could make an exception and update these packages, thanks!
** Summary changed:
- Update vte2.91 to 2.58.2
+ Update vte2.91 to 0.58.2
** Description changed:
I'm filing a bug since we are now in Final Freeze for Ubuntu
Upstream fix: https://vcs.pcre.org/pcre2?view=revision=1228
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864364
Title:
Possible Regession: PCRE2 fails to match regex
To manage notifications
*** This bug is a duplicate of bug 1691678 ***
https://bugs.launchpad.net/bugs/1691678
** This bug has been marked a duplicate of bug 1691678
Scrollbars escape the bottom and right side of the Terminal window by 1px
--
You received this bug notification because you are a member of Ubuntu
> It appears we would need a new upstream bug to track this because the
old one didn't go anywhere.
This is not true. The old one did go somewhere: It examined the behavior
and clearly concluded that upstream gnome-terminal is NOT buggy here, it
never was. It's one of the Ubuntu patches that
> but dropping the change creates a regression on the Ubuntu
session/theme
So the situation is: Unpatched gnome-terminal looks perfect on the
default GTK theme and on many others, except Ubuntu's.
Conclusion: Let's patch gnome-terminal! Wow.
I'm wondering: Has anyone considered fixing the
Upstream report: https://bugs.exim.org/show_bug.cgi?id=2531
** Bug watch added: bugs.exim.org/ #2531
http://bugs.exim.org/show_bug.cgi?id=2531
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864364
It is really, really not the terminal emulator's job to set basic
environment variables.
It should either be done by the environment in which gnome-terminal is
started (e.g. systemd --user), so that the terminal just transparently
passes this on; or should be done by the shell initialization
I was severely annoyed by the new behavior of the Alt key (FF 75, Ubuntu
20.04, Unity 7).
If I move the window using Alt + mouse drag (which I frequently do), the
menu opens up. Subsequent letters I type aren't sent to the webpage, but
navigate the menu. Another lone Alt keypress doesn't close it
See also bug #1859123.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872377
Title:
No menus in Unity after upgrading to 20.04
To manage notifications about this bug go to:
I'd take one step back and ask the question: Why would anyone one a
graphical system need to run a terminal emulator in order to get
notified about new mail? What if someone uses all kinds of other
applications (web browser, document editor, photo viewer, music
player...), just not a terminal, why
gnome-terminal lists the fonts that are monospace according to
pango_font_family_is_monospace(). The font as well as Pango should be
examined why this one isn't believed to be a monospace one.
That being said, you can still set this font using dconf-editor, by
setting
> How did you get terminator to print the following?
With Eoan + VTE 0.60, I just execute "terminator" from another terminal
emulator.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867746
Title:
https://weechat.org/files/doc/devel/weechat_user.en.html#option_weechat.look.eat_newline_glitch:
"[eat_newline_glitch] is disabled by default because it can cause
serious display bugs"
Try the behavior in xterm, too. If it's buggy there too then it clearly
has nothing to do with gnome-terminal.
Yes the space could be relevant, search for "ignorespace" in bash's
manual.
Also, it's the shell (bash) handling the history, not the terminal.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876113
The same applies not just for the mouse mode, but a whole lot of other
terminal modes (e.g. keypad modes, alternate charset, alternate scroll
mode, bracketed paste mode, colors, attributes and many many more...).
The problem cannot be fixed in the terminal: The terminal, by design,
only sees a
Thanks for this investigation so far!
We've opened an upstream VTE issue at
https://gitlab.gnome.org/GNOME/vte/issues/222 .
We'd appreciate if QEMU developers joined us there. Apparently QEMU uses
the "commit" signal in a way that it was not meant to be used, and thus
it's unclear what the best
gnome-terminal 3.36, which is included in Ubuntu 20.04, added a config
option Preferences -> -> Command -> Preserve working
directory.
Older versions preserved the directory only when launching a shell, not
when launching a custom command. This behavior was frowned upon by some
folks,
For setting: vte-2.91.sh is intended to do that... the ".sh" extension
was missing, sorry.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1609342
Title:
Gnome-terminal sets directory to HOME for
This is not an issue with the terminals, this is a new feature of
bash-5.1. Search for the word "highlight" at
https://lists.gnu.org/archive/html/info-gnu/2020-12/msg3.html .
---
This could not theoretically be a bug in gnome-terminal/vte. Terminals
don't directly paint a letter as a
> You mean it will always be like this going forward?
I don't know. This was a change in the default shell "bash". I'm not
involved in bash's development, nor in Ubuntu's. I don't know what their
plans are. I don't know if this feature can be disabled in bash (but I
know that it's bash's
...patch its source or ask its developers...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926256
Title:
Pasted text in the terminal is always highlighted and selected
To manage notifications
> h. Bracketed paste mode is enabled by default.
> If so, it looks like this "feature" can be disabled. How?
The way to disable bracketed paste mode is presumably to place this in .inputrc:
set enable-bracketed-paste off
But DON'T do this! Bracketed paste mode is an important safety measure
> I see the benefit to the change in bash from a security perspective, so
> perhaps gnome-terminal needs to adapt to this new feature.
You missed the possibility of keeping bracketed paste mode (the
functionality) enabled (as I, for one, have had it enabled ever since
bash added this feature,
Another most likely duplicate: https://github.com/gnome-
terminator/terminator/issues/899
And yet another most likely duplicate:
https://bbs.archlinux.org/viewtopic.php?id=294164. Here a user claims
that downgrading gnome-shell and mutter fixes the issue, and points to
upstream issue
During the last barely more than 24 hours, at least 4 people have
reported/confirmed heavy latencies newly appearing in their GNOME
Terminal. One person with Ubuntu 23.10 and two people with Ubuntu 22.04
(one of which comments has just been removed).
Seems to be reported upstream at
https://gitlab.gnome.org/GNOME/mutter/-/issues/3384.
The upstream bug unfortunately also made it into Ubuntu update packages
in https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2054510.
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status:
@ Daniel van Vugt,
The faulty change has a timestamp of 22 Feb, and the package began to
arrive at users probably on 29 Mar. That's a difference of 5 weeks.
I'm not familiar with Ubuntu's internal procedures, I don't know how
things work, which component (e.g. building packages, QA, somewhat
> [amirsalarsafaei] I downgraded my mutter to 45.0-3ubuntu3 but the
issues persists
Mentioning just in case:
You should downgrade all the packages built from mutter's source that
you have installed, including libmutter-13-0, mutter-common, mutter-
common-bin etc. (Or at least I don't know which
> Upstream Gnome 46 made a lot of changes recently to improve
performance and input lag in Gnome-Terminal. Those changes are separate
from this bug.
Exactly.
> I don't know whether those changes were backported to Ubuntu 22.04,
which ships Gnome 42.
They weren't, and almost certainly won't be.
*** This bug is a duplicate of bug 2059847 ***
https://bugs.launchpad.net/bugs/2059847
Duplicate of bug 2059847.
See also: https://askubuntu.com/questions/1509058/input-delay-on-
terminal-ubuntu-22-04-4
** This bug has been marked a duplicate of bug 2059847
Input lag or freezes on Nvidia
itstool didn't change from 23.10, python3 did.
This article seems relevant: https://adamj.eu/tech/2022/11/04/why-does-
python-deprecationwarning-invalid-escape-sequence/
and it also claims that python 3.11 already gave warnings if you asked
for it (which wasn't the default), but with python
Filed upstream bug https://github.com/itstool/itstool/issues/54, but
upstream has been unmaintained for 2.5 years, not sure if we can expect
a quick "official" fix.
** Bug watch added: github.com/itstool/itstool/issues #54
https://github.com/itstool/itstool/issues/54
--
You received this bug
Public bug reported:
24.04 beta, fully updated.
Simply start 'itstool'. Notice how it spits out a lot of syntax
warnings:
/usr/bin/itstool:239: SyntaxWarning: invalid escape sequence '\s'
if re.sub('\s+', ' ', text).strip() != '':
/usr/bin/itstool:337: SyntaxWarning: invalid escape
I can reproduce the problem on two computers, both running fully-updated
24.04 beta.
For me, the bug appears if all of these circumstances are met:
- /org/gnome/desktop/interface/gtk-theme is Ambiance or Radiance
- one of the windows is focused
- the Desktop Icons NG (DING) extension is enabled
Looks remotely related: https://askubuntu.com/questions/927893/white-
line-on-left-of-ubuntu-launcher-when-desktop-icons-enabled
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1986450
Title:
Visual
I've modified /usr/share/themes/Ambiance (recursively), search-replacing
all the "1px" to "10px", and (after logging out and back in) the line at
the desktop's right edge looks about 10px wide.
So we're on the right track.
--
You received this bug notification because you are a member of Ubuntu
It's /usr/share/themes/{Amb,Rad}iance/gtk-3.20/gtk-widgets.css line 18:
.background:backdrop {
color: @backdrop_fg_color;
box-shadow: inset -1px 0 shade (@bg_color, 0.94);
}
Change that to 0 (or I guess you could remove the entire line or even
the
Without root access (or being worried of an update overwriting the
changes), this is how I could fix it as a user.
I've placed this in my ~/.config/gtk-3.0/gtk.css file:
window.desktopwindow.background:backdrop {
box-shadow: none;
}
Don't ask why it's gtk-3.0 and not 3.20 or 4.0, I have
> Wow, I didn't realize that people were still trying to use Ambiance
and Radiance (from source package ubuntu-themes) with Ubuntu 24.04 LTS.
I'd love to switch to Adwaita or Yaru, but I prefer to have dark window
header and light window contents, and I haven't found yet how to do it
in those.
Let's see what DING devs think: https://gitlab.com/rastersoft/desktop-
icons-ng/-/issues/315
** Bug watch added: gitlab.com/rastersoft/desktop-icons-ng/-/issues #315
https://gitlab.com/rastersoft/desktop-icons-ng/-/issues/315
--
You received this bug notification because you are a member of
DING developer's response is basically that they clear the "decorated"
property of the window, and the theme should handle that.
Based on this, I think the correct solution for the Ambiance/Radiance
themes is to further restrict the offending block with the ".decorated"
selector, i.e.
> .background.decorated:backdrop {
This still doesn't feel entirely good. The background can be applied to
a window, in which case it needs to be restricted to the .decorated
property; but I presume it can also be applied to many other GTK widgets
in which case it shouldn't be restricted, at
Can you describe how those artifacts look like? Or attach a screenshot
or video taken by an external camera?
Do you have fractional scaling?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063270
I'm having a hard time trying to tell apart lit pixels from dust on your
screen. :)
Do you mean these dots that blink together with the cursor?
** Attachment added: "PXL_20240424_153154820.MP_marked.jpg"
Thanks a lot!
Forwarded upstream at https://gitlab.gnome.org/GNOME/vte/-/issues/2778
for the developer most familiar with this area to take a look.
** Bug watch added: gitlab.gnome.org/GNOME/vte/-/issues #2778
https://gitlab.gnome.org/GNOME/vte/-/issues/2778
--
You received this bug
601 - 699 of 699 matches
Mail list logo