[Bug 1341138] [NEW] package tor (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/tor', which is also in package tor-browser 3.5.4
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 install/upgrade: trying to overwrite '/usr/bin/tor', which is also in package tor-browser 3.5.4'. Apparently the packages 'tor' and 'tor-browser' are in conflict. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: tor (not installed) ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 Date: Sat Jul 12 16:52:14 2014 DpkgTerminalLog: Preparing to unpack .../tor_0.2.4.20-1_amd64.deb ... Unpacking tor (0.2.4.20-1) ... dpkg: error processing archive /var/cache/apt/archives/tor_0.2.4.20-1_amd64.deb (--unpack): trying to overwrite '/usr/bin/tor', which is also in package tor-browser 3.5.4 DuplicateSignature: package:tor:(not installed):trying to overwrite '/usr/bin/tor', which is also in package tor-browser 3.5.4 ErrorMessage: trying to overwrite '/usr/bin/tor', which is also in package tor-browser 3.5.4 InstallationDate: Installed on 2014-05-02 (70 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: tor Title: package tor (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/tor', which is also in package tor-browser 3.5.4 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: tor (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1341138 Title: package tor (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/tor', which is also in package tor-browser 3.5.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tor/+bug/1341138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726325] [NEW] Log-out button has no effect
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 is added by the GNOME Shell extension (prompts to) log out the current user. 4) What happened instead: Nothing. ** Affects: gnome-shell-extension-log-out-button (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/1726325 Title: Log-out button has no effect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-log-out-button/+bug/1726325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745273] Re: Cannot open terminal with long working directory name containing Unicode characters
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 directory name containing Unicode characters To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1745273/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745273] Re: Cannot open terminal with long working directory name containing Unicode characters
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 working directory name containing Unicode characters To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1745273/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745273] Re: Cannot open terminal with long working directory name containing Unicode characters
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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1745273/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743471] [NEW] nautilus-actions-config-tool crashes with segmentation fault
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 Segmentation fault (core dumped) ** Affects: nautilus-actions (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/1743471 Title: nautilus-actions-config-tool crashes with segmentation fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus-actions/+bug/1743471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745273] [NEW] Cannot open gnome-terminal with long working directory name containing Unicode characters
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/01234567890123456789/01234567890123456789/ä/01234567890123456789/01234567890123456789/01234567890123456789/01234567890123456789” in a 80×24 window), gnome-terminal opens normally. 4) What happened instead: gnome-terminal closes immediately, both when opened using gnome-terminal --working-directory=/home/test/01234567890123456789/01234567890123456789/ä/01234567890123456789/01234567890123456789/01234567890123456789/01234567890123456789 and when changing to this directory using “cd”. There is no output on stderr or anywhere else, the window just closes. This makes it impossible to use gnome-terminal for many directories with long paths. This did NOT happen in Ubuntu 16.04. ** Affects: gnome-terminal (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/1745273 Title: Cannot open gnome-terminal with long working directory name containing Unicode characters To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1745273/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745271] [NEW] Input prompt behaves incorrectly if working directory path spans two lines
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 overlapping the working directory text (see attached screenshot, which shows a 80×24 terminal window in a directory called “/home/test/01234567890123456789/01234567890123456789/a/01234567890123456789/01234567890123456789/01234567890123456789/01234567890123456789”). On text input, the inputted text overwrites the working directory text. When pressing backspace, the entire second line is deleted (including the $ character). This makes using the history (up arrow) very confusing because afterwards, the actual input line characters do not seem to correspond to the displayed text anymore, i.e. characters inserted at a certain point are actually shifted in the resulting line, making it very difficult to properly type in commands. ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot illustrating the issue" https://bugs.launchpad.net/bugs/1745271/+attachment/5042542/+files/screenshot.png -- 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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1745271/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745273] Re: Cannot open terminal with long working directory name containing Unicode characters
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_MEASUREMENT=de_DE.UTF-8
LC_IDENTIFICATION=de_DE.UTF-8
LC_ALL=
Using “unset PROMPT_COMMAND” had no effect at all (and seems to be empty
for me, anyway?). This is pretty much a fresh install, so I’m using
Ubuntu’s default value of PS1:
$ echo "'$PS1'"
'\[\e]0;\u@\h:
\w\a\]${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$
'
However, when I change that to
PS1='\[\033[01;34m\]\w\[\033[00m\]\$ '
there seems to be no more crashing. So it seems that certain values of
PS1 do indeed trigger this bug.
I have also tried the bash development version, as suggested. Even with
the default value of PS1, I haven’t been able to cause a crash there.
However, this version goes REALLY crazy with the input prompt (junk
characters, erratically printing parts of the history or working
directory path to the terminal when pressing the arrow keys, invisible
text input etc.) for long working directory paths (with or without
Unicode characters), making input all but impossible. So whatever the
difference between the two versions is, it’s not an improvement.
Anyway, thanks a lot for the help so far. Since I’m not seeing the crash in the
newer version, I’m assuming it will be gone when Ubuntu updates (with the weird
behavior for long paths hopefully due to different compiler flags or something
like that). As a workaround, modifying PS1 seems to work.
--
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 manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1745273/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745271] Re: Input prompt behaves incorrectly if working directory path spans two lines
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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1745271/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745271] Re: Input prompt behaves incorrectly if working directory path spans two lines
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-terminal, I also got the issue in xterm. So, it does seem like a bash issue once again. Thanks for checking! ** Also affects: bash (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Input prompt behaves incorrectly if working directory path spans two lines + Input prompt behaves incorrectly if working directory path spans three lines ** Description changed: 1) The release of Ubuntu you are using: Ubuntu 17.10 - 2) The version of the package you are using: 3.24.2-0ubuntu4 + 2) The version of the package you are using: gnome-terminal version + 3.24.2-0ubuntu4; bash version 4.4-5ubuntu1 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 overlapping the working directory text (see attached screenshot, which shows a 80×24 terminal window in a directory called “/home/test/01234567890123456789/01234567890123456789/a/01234567890123456789/01234567890123456789/01234567890123456789/01234567890123456789”). On text input, the inputted text overwrites the working directory text. When pressing backspace, the entire second line is deleted (including the $ character). This makes using the history (up arrow) very confusing because afterwards, the actual input line characters do not seem to correspond to the displayed text anymore, i.e. characters inserted at a certain point are actually shifted in the resulting line, making it very difficult to properly type in commands. -- 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 three lines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1745271/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745273] Re: Cannot open gnome-terminal with long working directory name containing Unicode characters
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 happen there with the path from the original report because this machine’s hostname is shorter, so the input prompt is shorter as well. Using an even longer path, however, the same happens on this machine. The “ä” is a precomposed character. Using your command, the output is 000 c3 a4 0a 005 c3 a4 is the UTF-8 representation of the Unicode character U+00E4 LATIN SMALL LETTER A WITH DIAERESIS. So I’m not sure if that specific bash bug has anything to do with this (since there are no surrogates anywhere in my example), but since xterm is also affected, the cause does seem to be a lower-level component (bash? readline?). -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1745273/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745273] Re: Cannot open gnome-terminal with long working directory name containing Unicode characters
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 fault (core dumped) $ At this point, no more terminal input is possible. ** Description changed: 1) The release of Ubuntu you are using: Ubuntu 17.10 - 2) The version of the package you are using: 3.24.2-0ubuntu4 + 2) The version of the package you are using: gnome-terminal version + 3.24.2-0ubuntu4; bash version 4.4-5ubuntu1 3) What you expected to happen: When opening a terminal window with a long working directory path containing Unicode characters (such as “/home/test/01234567890123456789/01234567890123456789/ä/01234567890123456789/01234567890123456789/01234567890123456789/01234567890123456789” in a 80×24 window), gnome-terminal opens normally. 4) What happened instead: gnome-terminal closes immediately, both when opened using gnome-terminal --working-directory=/home/test/01234567890123456789/01234567890123456789/ä/01234567890123456789/01234567890123456789/01234567890123456789/01234567890123456789 and when changing to this directory using “cd”. There is no output on stderr or anywhere else, the window just closes. - This makes it impossible to use gnome-terminal for many directories with - long paths. This did NOT happen in Ubuntu 16.04. + It seems that gnome-terminal closes because bash crashes with a + segmentation fault, see https://bugs.launchpad.net/ubuntu/+source/gnome- + terminal/+bug/1745273/comments/4. + + This makes it impossible to use the shell for many directories with long + paths. This did NOT happen in Ubuntu 16.04. ** Also affects: bash (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Cannot open gnome-terminal with long working directory name containing Unicode characters + Cannot open terminal with long working directory name containing Unicode characters -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1745273/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746622] [NEW] Okular snap package cannot open URLs due to AppArmor
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 behavior: Clicking a link in a PDF document opens the URL in an appropriate program (e.g. a browser). 4) Observed behavior: When clicking the link, Okular opens a window prompting to choose the application which should be used to open the URL. When choosing “Applications → Url handler script”, Okular displays the following error message: KLauncher could not be reached via D-Bus. Error when calling start_service_by_desktop_path: An AppArmor policy prevents this sender from sending this message to this recipient; type="method_call", sender=":1.411" (uid=1000 pid=29799 comm="okular /path/to/document.pdf ") interface="org.kde.KLauncher" member="start_service_by_desktop_path" error name="(unset)" requested_reply="0" destination="org.kde.klauncher5" (uid=1000 pid=32653 comm="/usr/lib/x86_64-linux-gnu/libexec/kf5/klauncher --") ** Affects: okular (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/1746622 Title: Okular snap package cannot open URLs due to AppArmor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/okular/+bug/1746622/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745999] [NEW] Okular snap package cannot access files outside home directory
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: Universal document viewer publisher: kde contact: https://www.kde.org description: | Okular is a universal document viewer developed by KDE. Okular works on multiple platforms, including but not limited to Linux, Windows, Mac OS X, \*BSD, etc. Features: - Supported Formats: PDF, PS, Tiff, CHM, DjVu, Images, DVI, XPS, ODT, Fiction Book, Comic Book, Plucker, EPub, Fax - Sidebar with contents, thumbnails, reviews and bookmarks - Annotations support snap-id: SfUqQ280Y4bJ0k64qtBKTTXq5ml46tvQ commands: - okular tracking:stable installed: 16.12.3 (3) 7MB - refreshed: 2017-03-27 12:56:54 +0200 CEST channels: stable:16.12.3(3) 7MB - candidate: 17.04.3(5) 8MB - beta: 17.04.3(5) 8MB - edge: master+782a5fe (27) 5MB - The okular snap seems to use “strict” confinement and is thus unable to access files outside the user’s home directory even for reading. However, for a “viewer”-type application like okular, this is very problematic: – When downloading a file (e.g. PDF) in a browser like Firefox and choosing to open the file (instead of saving it somewhere in the home directory), the browser will typically place the file in /tmp/ and then open it using the default viewer for that file type. Since /tmp/ is outside the user’s home directory, okular is unable to open the file. – When opening documentation which is installed to system directories (e.g. /usr/share/…) along with its corresponding application, okular is likewise unable to open the documentation files for viewing. For example, the “texdoc” program for the TeX typesetting system looks up the documentation for a specified package (typically in PDF format) and runs the default (PDF) viewer to show the documentation. This fails if the okular snap application is set as the default PDF viewer. – Any files on mounted file systems, such as external storage (USB drives, SD cards, external hard drives…), network shares, etc., cannot be viewed with okular. Attempting to open any such files results in a dialog with the following error message: “Could not open file:///path/to/file”. This does not provide any explanation for the reason of the failure. ** Affects: kdegraphics Importance: Unknown Status: Unknown ** Affects: okular (Ubuntu) Importance: Undecided Status: New ** Bug watch added: KDE Bug Tracking System #389576 https://bugs.kde.org/show_bug.cgi?id=389576 ** Also affects: kdegraphics via https://bugs.kde.org/show_bug.cgi?id=389576 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1745999 Title: Okular snap package cannot access files outside home directory To manage notifications about this bug go to: https://bugs.launchpad.net/kdegraphics/+bug/1745999/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1748881] [NEW] Okular exits when machine is suspended
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: okular (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/1748881 Title: Okular exits when machine is suspended To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/okular/+bug/1748881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800179] [NEW] Search in recent files list only works with lowercase letters
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-lowercase letters, does yield results (see attached screenshot). So it seems that gedit converts the recently used file names to lowercase before comparing to the search term, which is incorrect. ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Tags: cosmic ** Attachment added: "screenshot of the problematic behavior" https://bugs.launchpad.net/bugs/1800179/+attachment/5205885/+files/gedit_recent_search.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800179 Title: Search in recent files list only works with lowercase letters To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1800179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793322] [NEW] “Domain” field missing when editing WPA2 Enterprise connection
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 field from the “create connection” dialog is conspicuously missing from the “edit connection” dialog: the “Domain:” field! (Marked in red in the screenshot.) In other words, it is not possible to change the domain for a WPA2 Enterprise connection after creating it. The field should be present in both dialogs. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: bionic ** Attachment added: "screenshot illustrating the problem" https://bugs.launchpad.net/bugs/1793322/+attachment/5190538/+files/screenshot.png -- 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 connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1793322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793322] Re: “Domain” field missing when editing WPA2 Enterprise connection
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 connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1793322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769383] Re: Ubuntu dock/launcher is shown on the lock screen
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 is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769383 Title: Ubuntu dock/launcher is shown on the lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769383/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815480] Re: “Extract Here” only creates empty files (0 bytes) for .zip files created by ownCloud
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” only creates empty files (0 bytes) for .zip files created by ownCloud To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1815480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815480] [NEW] “Extract Here” only creates empty files (0 bytes) for .zip files created by ownCloud
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, unzip or 7z: $ unzip -t test.zip Archive: test.zip testing: test/OK testing: test/f1.txt OK testing: test/f2.txt OK testing: test/f3.txt OK No errors detected in compressed data of test.zip. $ unzip test Archive: test.zip creating: test/ extracting: test/f1.txt extracting: test/f2.txt extracting: test/f3.txt $ 7z x test.zip 7-Zip [64] 16.02 : Copyright (c) 1999-2016 Igor Pavlov : 2016-05-21 p7zip Version 16.02 (locale=en_US.UTF-8,Utf16=on,HugeFiles=on,64 bits,4 CPUs Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz (306D4),ASM,AES-NI) Scanning the drive for archives: 1 file, 8656 bytes (9 KiB) Extracting archive: test.zip -- Path = test.zip Type = zip Physical Size = 8656 64-bit = + Everything is Ok Folders: 1 Files: 3 Size: 7850 Compressed: 8656 Expected behavior: Download the attached file “test.zip”, right-click the file in Nautilus and choose “Extract Here”. A directory “test” containing three non-empty files “f1.txt”, “f2.txt” and “f3.txt” should be created. Actual behavior: All three files are empty (0 bytes). Nautilus version: 1:3.26.4-0ubuntu7.1 (cosmic) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: cosmic ** Attachment added: "Example .zip archive which exhibits the problem" https://bugs.launchpad.net/bugs/1815480/+attachment/5237721/+files/test.zip -- 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” only creates empty files (0 bytes) for .zip files created by ownCloud To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1815480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 156201] Re: gedit handles opening big files badly
“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. https://bugs.launchpad.net/bugs/156201 Title: gedit handles opening big files badly To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/156201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1932159] Re: bcmwl/6.30.223.271+bdcom-0ubuntu7~20.04.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
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 named differently? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1932159 Title: bcmwl/6.30.223.271+bdcom-0ubuntu7~20.04.2 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1932159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940722] [NEW] Package bcmwl-kernel-source version 6.30.223.271+bdcom-0ubuntu7~20.04.3 is not installed because apt thinks it’s a downgrade
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 20.04). The bcmwl-kernel-source package should be updated to the version in focal-updates. 4) Actual result: apt considers the package from focal-updates a downgrade, leaving the system with broken WiFi after updating to the HWE kernel. $ apt-cache policy bcmwl-kernel-source bcmwl-kernel-source: Installed: 6.30.223.271+bdcom-0ubuntu7 Candidate: 6.30.223.271+bdcom-0ubuntu7 Version table: *** 6.30.223.271+bdcom-0ubuntu7 100 100 /var/lib/dpkg/status 6.30.223.271+bdcom-0ubuntu7~20.04.3 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/restricted amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/restricted amd64 Packages 6.30.223.271+bdcom-0ubuntu5 500 500 http://de.archive.ubuntu.com/ubuntu focal/restricted amd64 Packages $ sudo apt install bcmwl-kernel-source=6.30.223.271+bdcom-0ubuntu7~20.04.3 Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: libllvm11 libllvm11:i386 shim Use 'sudo apt autoremove' to remove them. The following packages will be DOWNGRADED: bcmwl-kernel-source 0 upgraded, 0 newly installed, 1 downgraded, 0 to remove and 0 not upgraded. Need to get 1,546 kB of archives. After this operation, 8,192 B of additional disk space will be used. Do you want to continue? [Y/n] ** Affects: bcmwl (Ubuntu) Importance: Undecided Status: New ** Tags: focal ** Description changed: 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 #1932159 (building the kernel module with HWE kernel 5.11 on Ubuntu 20.04). The bcmwl-kernel-source package should be updated to the version in focal-updates. + 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 20.04). The bcmwl-kernel-source package should be updated to the version in focal-updates. 4) Actual result: apt considers the package from focal-updates a downgrade, leaving the system with broken WiFi after updating to the HWE kernel. $ apt-cache policy bcmwl-kernel-source bcmwl-kernel-source: - Installed: 6.30.223.271+bdcom-0ubuntu7 - Candidate: 6.30.223.271+bdcom-0ubuntu7 - Version table: - *** 6.30.223.271+bdcom-0ubuntu7 100 - 100 /var/lib/dpkg/status - 6.30.223.271+bdcom-0ubuntu7~20.04.3 500 - 500 http://de.archive.ubuntu.com/ubuntu focal-updates/restricted amd64 Packages - 500 http://security.ubuntu.com/ubuntu focal-security/restricted amd64 Packages - 6.30.223.271+bdcom-0ubuntu5 500 - 500 http://de.archive.ubuntu.com/ubuntu focal/restricted amd64 Packages + Installed: 6.30.223.271+bdcom-0ubuntu7 + Candidate: 6.30.223.271+bdcom-0ubuntu7 + Version table: + *** 6.30.223.271+bdcom-0ubuntu7 100 + 100 /var/lib/dpkg/status + 6.30.223.271+bdcom-0ubuntu7~20.04.3 500 + 500 http://de.archive.ubuntu.com/ubuntu focal-updates/restricted amd64 Packages + 500 http://security.ubuntu.com/ubuntu focal-security/restricted amd64 Packages + 6.30.223.271+bdcom-0ubuntu5 500 + 500 http://de.archive.ubuntu.com/ubuntu focal/restricted amd64 Packages $ sudo apt install bcmwl-kernel-source=6.30.223.271+bdcom-0ubuntu7~20.04.3 Reading package lists... Done - Building dependency tree + Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: - libllvm11 libllvm11:i386 shim + libllvm11 libllvm11:i386 shim Use 'sudo apt autoremove' to remove them. The following packages will be DOWNGRADED: - bcmwl-kernel-source + bcmwl-kernel-source 0 upgraded, 0 newly installed, 1 downgraded, 0 to remove and 0 not upgraded. Need to get 1,546 kB of archives. After this operation, 8,192 B of additional disk space will be used. Do you want to continue? [Y/n] -- 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 version 6.30.223.271+bdcom-0ubuntu7~20.04.3 is not installed because apt thinks it’s a downgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1940722/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940722] Re: Package bcmwl-kernel-source version 6.30.223.271+bdcom-0ubuntu7~20.04.3 is not installed because apt thinks it’s a downgrade
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 version 6.30.223.271+bdcom-0ubuntu7~20.04.3 is not installed because apt thinks it’s a downgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1940722/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940417]
(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 bookmarks toolbar. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940417 Title: On Wayland toolbar menus are sometimes invisible/flickering To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1940417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940417]
(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 preferred value of `1.2`; either resetting > `layout.css.devPixelsPerPx` to its default (`-1.0`), or running Firefox > without `MOZ_ENABLE_WAYLAND=1` will make the toolbar items work again. > [Here's the graphics portion of my > `about:support`](https://pastebin.mozilla.org/OdgM9Oox). > > **So my steps to reproduce this are:** > 1. start Firefox with `MOZ_ENABLE_WAYLAND=1` > 2. set `layout.css.devPixelsPerPx` to `1.2` > 3. click on the hamburger menu button > > **What I expect to happen:** > For the hamburger menu content to show. > > **What happens instead:** > The hamburger menu content flickers or doesn't show at all. Just for reference/as a workaround: A value of `1.25` for `layout.css.devPixelsPerPx` seems to work flawlessly for me (I was also using `1.2` :-) ). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940417 Title: On Wayland toolbar menus are sometimes invisible/flickering To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1940417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940417]
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. https://bugs.launchpad.net/bugs/1940417 Title: On Wayland toolbar menus are sometimes invisible/flickering To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1940417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed
@#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 zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/1906476/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862329] [NEW] Cannot add okular to favorites in the dock
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, which allows one to pin the program to the dock so that it can be launched from there. 4) What happened instead: The option “Add to Favorites” is missing for the okular icon. This can be fixed by adding the line StartupWMClass=okular to the file “/usr/share/applications/org.kde.okular.desktop”. ** Affects: okular (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/1862329 Title: Cannot add okular to favorites in the dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/okular/+bug/1862329/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
