@#41: Dataset “rpool/ROOT/ubuntu_” sounds like bug 1894329, although
that one should have been fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906476
Title:
PANIC at
(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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
(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
This seems to have hit multiple users, see e.g. a post on Ask Ubuntu:
https://askubuntu.com/q/1356061
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940722
Title:
Package bcmwl-kernel-source
Public bug reported:
1) Ubuntu release: 20.04
2) Installed package version: 6.30.223.271+bdcom-0ubuntu7
3) Expectation: bcmwl-kernel-source version 6.30.223.271+bdcom-0ubuntu7~20.04.3
was released to focal-updates to fix LP: #1932159 (building the kernel module
with HWE kernel 5.11 on Ubuntu
Unfortunately, it seems that this update is not actually arriving on
systems because apt considers package version
6.30.223.271+bdcom-0ubuntu7~20.04.3 from focal-updates a downgrade
compared to version 6.30.223.271+bdcom-0ubuntu7, see LP: #1940722. Not
sure why that is, maybe the version should be
Public bug reported:
1) Ubuntu version: 19.10
2) Package version: okular 4:19.04.3-0ubuntu1 (APT package)
3) What you expected to happen:
When starting okular, its icon appears in the dock (as for any other program).
When right-clicking this icon, the option “Add to Favorites” should appear,
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815480
Title:
“Extract Here”
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,
“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 Ubuntu
Bugs, which is subscribed to Ubuntu.
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 Ubuntu
Bugs, which
Reported at https://gitlab.gnome.org/GNOME/gnome-control-
center/issues/325
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1793322
Title:
“Domain” field missing when editing WPA2 Enterprise
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
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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745273
Title:
Cannot open terminal with long
Indeed, it seems to be gone/fixed in 18.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745273
Title:
Cannot open terminal with long working directory name containing
Unicode characters
To
Fixed in Ubuntu 18.04
** Changed in: bash (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745273
Title:
Cannot open terminal with long working
Public bug reported:
1) Ubuntu release: Ubuntu 17.10
2) Package version: okular 4:17.04.3-0ubuntu1
3) Expected behavior: When suspending while Okular is open, it should
still be open in the same state when resuming.
4) Observed behavior: There are no Okular windows after resuming.
** Affects:
Public bug reported:
1) Ubuntu release: Ubuntu 17.10
2) Package version: Installed using “snap install okular”. “snap info okular”
shows
snap-id: SfUqQ280Y4bJ0k64qtBKTTXq5ml46tvQ
tracking:stable
installed: 16.12.3 (3) 7MB -
refreshed: 2017-03-27 12:56:54 +0200 CEST
3) Expected
Public bug reported:
I’m not sure where the correct place is to report issues in snap
packages, so I hope this isn’t completely wrong.
I installed okular on Ubuntu 17.10 via snap (“sudo snap install
okular”). “snap info okular” gives me the following output:
name: okular
summary:
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
Nope, not happening in xterm.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745271
Title:
Input prompt behaves incorrectly if working directory path spans two
lines
To manage notifications
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
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
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
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
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
Public bug reported:
1) Ubuntu release: 17.10 (running Wayland session)
2) Package: nautilus-actions 3.2.3-1build5
3) When running nautilus-actions-config-tool, the Nautilus Actions
configuration tool should be starrted.
4) Nothing (the program crashed):
$ nautilus-actions-config-tool
Public bug reported:
The extension doesn’t seem to work with Ubuntu 17.10. The log-out button
is correctly added to the shell menu, but clicking it does nothing.
1) Ubuntu release: Ubuntu 17.10 (artful)
2) Package version: 1.0.6-1
3) What you expected to happen: Clicking the log-out button which
Public bug reported:
Ubuntu version: 14.04, latest updates (as of 2014-07-12)
Package version (package 'tor'): 0.2.4.20-1
Expected to happen: The tor package is installed successfully
What happened instead: Installation of package failed with message package tor
(not installed) failed to
31 matches
Mail list logo
