[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 Desktop Bugs, which is subscribed to nautilus in 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 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-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 Desktop Bugs, which is subscribed to nautilus in 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 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-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 Desktop Bugs, which is a bug assignee. 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 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-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 Desktop Bugs, which is subscribed to gnome-shell in 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 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-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 Desktop Bugs, which is subscribed to gnome-control-center in 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 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-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 Desktop Bugs, which is subscribed to gedit in 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 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-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 Desktop Bugs, which is subscribed to gnome-control-center in 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 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-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 Desktop Bugs, which is subscribed to gnome-terminal in 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 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-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 Desktop Bugs, which is subscribed to gnome-terminal in 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 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-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 Desktop Bugs, which is subscribed to gnome-terminal in 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 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-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 Desktop Bugs, which is subscribed to gnome-terminal in 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 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-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 Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1745271/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-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
Desktop Bugs, which is subscribed to gnome-terminal in 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
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-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 Desktop Bugs, which is subscribed to gnome-terminal in 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 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-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 Desktop Bugs, which is subscribed to gnome-terminal in 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 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-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 Desktop Bugs, which is subscribed to gnome-terminal in 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 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-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 Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1745271/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
