(In reply to simon.may from comment #28)
> In fact, it seems really strange what values for `layout.css.devPixelsPerPx`
> trigger this – `1.22` also seems to work without issues, while other values
> (like `1.21`) don’t.
Sorry, nevermind, `1.22` does have problems with some entries in the
bookma
In fact, it seems really strange what values for
`layout.css.devPixelsPerPx` trigger this – `1.22` also seems to work
without issues, while other values (like `1.21`) don’t.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubunt
(In reply to Jani Uusitalo from comment #26)
> I can't speak for Jeroen, but I played around with the upstream builds (both
> 92 and 91) and my faulty profile a bit and managed to isolate the trigger
> combination for this: `MOZ_ENABLE_WAYLAND=1` and setting
> `layout.css.devPixelsPerPx` to my p
Is there anything specific I should do? Just extracting the file in
Nautilus doesn’t generate any entries in journalctl.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1815480
Title:
Public bug reported:
For any .zip archive generated by the ownCloud software, it seems that
extracting the files using Nautilus results in correctly-named
directories/files to be created, but all files are actually empty (0
bytes). The archive can be extracted without issues using file-roller,
unz
“Unfortunately nano doesn't have syntax highlighting.”
nano does have syntax highlighting!
https://wiki.archlinux.org/index.php/nano#Syntax_highlighting
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launch
I can also confirm that this issue still occurs even with the version in
-proposed. The only difference I’ve noticed with the new version is that
the text on the keyboard layout indicator sometimes disappears.
--
You received this bug notification because you are a member of Desktop
Packages, whi
Reported at https://gitlab.gnome.org/GNOME/gnome-control-
center/issues/325
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1793322
Title:
“Domain” field missing when edit
Public bug reported:
When clicking “Open” and typing to search the recently opened files, any
search involving uppercase letters fails to return any result, even if
files with uppercase letters in their file names have recently been
opened. Searching for the same file names, but using all-lowercas
Public bug reported:
Ubuntu release: 18.04.1 LTS
Package version: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2
When *adding* a WPA2 Enterprise connection, the dialog that appears is
very similar to the “Security” tab when *editing* the connection (see
the attached screenshot). However, one fiel
Fixed in Ubuntu 18.04
** Changed in: bash (Ubuntu)
Status: Confirmed => Fix Released
--
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/1745273
Title:
Cannot open terminal
Caused by a bash bug/crash
** Changed in: gnome-terminal (Ubuntu)
Status: Confirmed => Invalid
--
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/1745273
Title:
Cannot open
Indeed, it seems to be gone/fixed in 18.04.
--
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/1745273
Title:
Cannot open terminal with long working directory name containing
Uni
Oh, sorry about that. Apparently, xterm uses a different value for PS1
than gnome-terminal by default. It seems that this issue only happens
when color escape sequences are involved, which is why it didn’t happen
for me in xterm. However, when I manually set xterm to the same value as
in gnome-term
Nope, not happening in xterm.
--
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/1745271
Title:
Input prompt behaves incorrectly if working directory path spans two
lines
Status
My locale is as follows:
$ locale
LANG=en_US.UTF-8
LANGUAGE=
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC=de_DE.UTF-8
LC_TIME=de_DE.UTF-8
LC_COLLATE="en_US.UTF-8"
LC_MONETARY=de_DE.UTF-8
LC_MESSAGES="en_US.UTF-8"
LC_PAPER=de_DE.UTF-8
LC_NAME=de_DE.UTF-8
LC_ADDRESS=de_DE.UTF-8
LC_TELEPHONE=de_DE.UTF-8
LC_MEASU
As a quick update, it does seem to be bash that crashes – see the
following terminal session:
user@host:~$ sh
$ cd
/home/test/01234567890123456789/01234567890123456789/ä/01234567890123456789/01234567890123456789/01234567890123456789/01234567890123456789/01234567890123456789/
$ bash
Segmentation f
When I change to that same directory in xterm, it closes just like
gnome-terminal. So it doesn’t seem to be specific to gnome-terminal, but
it DOES seem to be important that the input prompt fills more than two
lines in the terminal to trigger the bug.
I’ve tested this on my laptop, and it doesn’t
Public bug reported:
1) The release of Ubuntu you are using: Ubuntu 17.10
2) The version of the package you are using: 3.24.2-0ubuntu4
3) What you expected to happen: When opening a terminal window with a
long working directory path containing Unicode characters (such as
“/home/test/012345678901
Public bug reported:
1) The release of Ubuntu you are using: Ubuntu 17.10
2) The version of the package you are using: 3.24.2-0ubuntu4
3) What you expected to happen: The input prompt should behave the same,
no matter what the working directory is.
4) What happened instead: The cursor starts ov
20 matches
Mail list logo
