redox-os issueshttps://gitlab.redox-os.org/groups/redox-os/-/issues2024-02-10T18:33:05Zhttps://gitlab.redox-os.org/redox-os/orbutils/-/issues/52(Feature Request) Mount volume option for File Manager.2024-02-10T18:33:05ZRibbon(Feature Request) Mount volume option for File Manager.https://gitlab.redox-os.org/redox-os/orbutils/-/issues/51(Feature Request) Split panels for File Manager.2024-02-10T18:32:54ZRibbon(Feature Request) Split panels for File Manager.![image](/uploads/f67f88cc24d3563bdb699ee7ab4cf8c4/image.png)![image](/uploads/f67f88cc24d3563bdb699ee7ab4cf8c4/image.png)https://gitlab.redox-os.org/redox-os/uutils/-/issues/4uname -r reports 0.3.42023-07-01T07:53:41ZRon Williamsuname -r reports 0.3.4`uname` is reporting an old version number. Can we automate the update of version number?`uname` is reporting an old version number. Can we automate the update of version number?https://gitlab.redox-os.org/redox-os/orbclient/-/issues/46Update `redox_syscall` to v0.32023-04-28T13:46:34ZdaxpeddaUpdate `redox_syscall` to v0.3I was just trying the new `winit` release on Redox OS and noticed the duplicate dependency.I was just trying the new `winit` release on Redox OS and noticed the duplicate dependency.https://gitlab.redox-os.org/redox-os/ion/-/issues/1017Ion crashes after pressing `enter` key frequently2023-06-25T02:29:58ZIvan TanIon crashes after pressing `enter` key frequentlybug: Ion crashes after pressing `enter` key frequently
expect: Ion runs normally after pkg exiting abnormally
code: input
```
user:/usr/bin# pkg list vim
* Requesting https://static.redox-os.org/pkg/x86_64-unknown-redox/vim.sig
126 B ...bug: Ion crashes after pressing `enter` key frequently
expect: Ion runs normally after pkg exiting abnormally
code: input
```
user:/usr/bin# pkg list vim
* Requesting https://static.redox-os.org/pkg/x86_64-unknown-redox/vim.sig
126 B / 126 B [===========================================] 100.00 % 12.11 KB/s
* Requesting https://static.redox-os.org/pkg/x86_64-unknown-redox/vim.tar.gz
smolnetd::scheme: poll error: dropped by socket
smolnetd::scheme: poll error: dropped by socket
560.00 KB / 11.54 MB [=>-------------------------------] 4.74 % 292.13 KB/s 39s ion: pipeline execution error: process (112) ended by signal SIGINT
user:/usr/bin#
user:/usr/bin#
# ...
user:/usr/bin# cat /sys:context
PID PGID PPID RUID RGID RNS EUID EGID ENS STAT CPU TICKS MEM NAME
1 1 0 0 0 0 0 0 0 RR 0 00:19:48 512 B
2 2 0 0 0 0 0 0 0 RR+ 3 00:00:00 512 B
3 3 0 0 0 0 0 0 0 RR+ 1 00:00:00 512 B
4 4 0 0 0 0 0 0 0 RR+ 2 00:00:00 512 B
5 5 0 0 0 0 0 0 0 UB 0 00:00:00 2 MB initfs:bin/init
6 5 5 0 0 1 0 0 1 UB 0 00:00:00 12 MB bootstrap
8 5 5 0 0 0 0 0 0 UB 0 00:00:00 1 MB /bin/nulld
10 5 5 0 0 0 0 0 0 UB 0 00:00:00 1 MB /bin/zerod
12 5 5 0 0 0 0 0 0 UB 0 00:00:00 2 MB /bin/randd
15 5 5 0 0 0 0 0 0 UB 0 00:00:00 1 MB /bin/logd
19 5 5 0 0 0 0 0 0 UB 0 00:00:03 2 MB /bin/ramfs
21 5 5 0 0 0 0 0 0 UB 0 00:00:01 2 MB /bin/acpid
25 5 5 0 0 0 0 0 0 UB 0 00:00:05 2 MB /bin/ahcid
27 5 5 0 0 0 0 0 0 UB 0 00:00:04 35 MB /bin/redoxfs
29 5 5 0 0 0 0 0 0 UB 0 00:00:00 1 MB file:/bin/ipcd
31 5 5 0 0 0 0 0 0 UB 0 00:00:06 2 MB file:/bin/ptyd
34 5 5 0 0 1 0 0 1 UB 0 00:00:00 7 MB file:/bin/pcid
35 5 5 0 0 0 0 0 0 UR 0 00:02:02 2 MB file:/bin/ihdad
38 5 5 0 0 0 0 0 0 UB 0 00:00:02 1 MB file:/bin/e1000d
40 5 5 0 0 1 0 0 1 UB 0 00:00:00 2 MB file:/bin/escalated
42 5 5 0 0 0 0 0 0 UB 0 00:00:06 3 MB file:/bin/smolnetd
44 5 5 0 0 0 0 0 0 UB 0 00:00:00 2 MB file:/bin/dnsd
48 5 5 0 0 0 0 0 0 UR 0 00:02:27 4 MB file:/bin/audiod
49 5 48 0 0 0 0 0 0 UB 0 00:02:10 4 MB file:/bin/audiod
54 5 5 0 0 1 0 0 1 UB 0 00:00:02 2 MB file:/bin/getty
55 5 54 0 0 1 0 0 1 UB 0 00:00:00 2 MB file:/bin/login
56 56 55 1000 1000 1 1000 1000 1 UB 0 00:00:02 4 MB file:/bin/ion
122 122 56 1000 1000 1 1000 1000 1 UR+ 0 00:00:00 8 MB file:/bin/cat
user:/usr/bin#
user:/usr/bin# smolnetd::scheme: poll error: unaddressable destination
user:/usr/bin#
user:/usr/bin#
user:/usr/bin#
thread 'main' panicked at 'wait() should either return Ok or panic', library/std/src/sys/unix/process/process_unix.rs:117:21
Invalid opcode fault
RFLAG: 0000000000000206
CS: 0000000000000033
RIP: 000000000061647e
RSP: 00007fffffff8730
SS: 000000000000002b
FSBASE 0000000000005000
GSBASE 0000000000000000
KGSBASE fffffd8000000050
RAX: 0000000000000000
RCX: 00000000006348a3
RDX: 000000000000000f
RDI: 0000000000000002
RSI: 0000000000684bcb
R8: 00007fffffff8640
R9: 0000000000000002
R10: 00007fffffff8488
R11: 0000000000000202
RBX: 0000000000000001
RBP: 00000000008c1130
R12: 0000000000000001
R13: 00000000008bb598
R14: 0000000000000000
R15: 00007fffffff8860
TRACE: FFFFFE80006532C0
FFFFFE80006532C0: FFFFFF000008B867
FFFFFF000008B730+0137
kernel::arch::x86_64::interrupt::exception::invalid_opcode::inner
FFFFFE8000653350: FFFFFF00000896CD
FFFFFF00000896A0+002D
kernel::arch::x86_64::interrupt::exception::invalid_opcode
00000000008C1130: EMPTY RETURN
kernel:INFO -- SIGNAL 4, CPU 0, PID ContextId(56)
kernel:INFO -- NAME file:/bin/ion
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
abort() called
########## Redox OS ##########
# Login with the following: #
# `user` #
# `root`:`password` #
##############################
redox login:
redox login:
redox login:
redox login: smolnetd::scheme: poll error: unaddressable destination
smolnetd::scheme: poll error: unaddressable destination
redox login:
redox login:
redox login: smolnetd::scheme: poll error: unaddressable destination
smolnetd::scheme: poll error: unaddressable destination
smolnetd::scheme: poll error: unaddressable destination
redox login:
redox login: user
Welcome to Redox OS!
```
For details, see the [test.log](/uploads/95263cd6701a4c442b2035f818dd5a3b/test.log)
expect: output
```
result
```
kernel: redox `git rev-parse HEAD` == e5c3be86cd2febcf4292ad4170943d4d3330f278
version:
```
user:~# ion --version
ion 1.0.0-alpha (x86_64-unknown-redox)
rev 3bb8966fc99ba223033e1e02b0a6d50fc25cbef4
```
interaction:
* 1. Press `enter` frequently
* 5. Shell crashes.
context: run redox without GUI `make qemu kvm=no vga=no`https://gitlab.redox-os.org/redox-os/kernel/-/issues/111kmain is not guaranteed to be PID 1, causing shutdown to not work correctly2023-02-27T16:22:47ZRon Williamskmain is not guaranteed to be PID 1, causing shutdown to not work correctly`shutdown` sends SIGKILL to kmain using PID 1. However, kmain is not guaranteed to have PID 1. You can verify this by running the system multiple times and doing `grep BSP sys:/log`, it shows e.g. Ok(ContextId(3)) about 50% of the time. ...`shutdown` sends SIGKILL to kmain using PID 1. However, kmain is not guaranteed to have PID 1. You can verify this by running the system multiple times and doing `grep BSP sys:/log`, it shows e.g. Ok(ContextId(3)) about 50% of the time. There needs to be a mechanism to ensure kmain has PID 1, or `shutdown` needs a way to determine the PID of kmain.https://gitlab.redox-os.org/redox-os/redox/-/issues/1366root cannot delete user's files2023-03-01T16:28:59ZRon Williamsroot cannot delete user's filesLog in as user `user`, create a file in your home directory. Then `sudo rm file`. It fails with permission denied.Log in as user `user`, create a file in your home directory. Then `sudo rm file`. It fails with permission denied.https://gitlab.redox-os.org/redox-os/redox-initfs/-/issues/1Redox would not boot after installing with fs password.2023-10-14T15:26:02ZRon WilliamsRedox would not boot after installing with fs password.User reported that Redox would not boot after installing with fs password. No password prompt was displayed.
https://matrix.to/#/!VRFarxUZgQhGPZpROi:matrix.org/$6oB9BNYbUVG7Wmj4ZT-u1NIofMClVG7i4KB9WHcrD9I?via=matrix.org&via=mozilla.org&v...User reported that Redox would not boot after installing with fs password. No password prompt was displayed.
https://matrix.to/#/!VRFarxUZgQhGPZpROi:matrix.org/$6oB9BNYbUVG7Wmj4ZT-u1NIofMClVG7i4KB9WHcrD9I?via=matrix.org&via=mozilla.org&via=westwork.orghttps://gitlab.redox-os.org/redox-os/book/-/issues/142Update Chat chapter to refer to Redox space in Matrix, and clarify how to use...2023-06-13T04:50:25ZRon WilliamsUpdate Chat chapter to refer to Redox space in Matrix, and clarify how to use /SupportRedox OS is a space in Matrix, users should join that.
Redox OS/Support requires a user to join if they use Element, there are guest accounts available on some other Matrix apps.Redox OS is a space in Matrix, users should join that.
Redox OS/Support requires a user to join if they use Element, there are guest accounts available on some other Matrix apps.https://gitlab.redox-os.org/redox-os/netutils/-/issues/31Ping Doesn't Work As Execpted, Return ERROR CODE == EAGAIN2023-01-10T14:28:27ZIvan TanPing Doesn't Work As Execpted, Return ERROR CODE == EAGAIN# Description
Ping command does't work properly, for example `ping 8.8.8.8`. I am sure that `8.8.8.8` is reachable.
Console output:
```
redox login: user
Welcome to Redox OS!
user:~# ping 8.8.8.8
: io error : Try again (os error 11)
...# Description
Ping command does't work properly, for example `ping 8.8.8.8`. I am sure that `8.8.8.8` is reachable.
Console output:
```
redox login: user
Welcome to Redox OS!
user:~# ping 8.8.8.8
: io error : Try again (os error 11)
user:~# ping www.google.com
: io error : Try again (os error 11)
```
# Environment info
* `git rev-parse HEAD`: `34d1ec9c2e9f7904b57547ca16d4c3145c109880`
* `rustc -V`: `rustc 1.61.0-nightly (58f11791a 2022-03-17)`
* `uname -a`: `Linux ccs-PC 5.15.0-56-generic #62~20.04.1-Ubuntu SMP Tue Nov 22 21:24:20 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux`
# Steps to reproduce
* Log in (`make FILESYSTEM_SIZE=512 qemu kvm=no vga=no`)
* Open terminal
* Input `ping X.X.X.X`
# Extra
When `event_queue.trigger_all` is called, the `on_echo_event` callback is triggered. However, the io read function returns `EAGAIN` because of nothing to read in `ping_fd`'s buffer during this period.
```
// netstack/source/src/smolnetd/scheme/icmp.rs
fn write_buf(
&mut self,
file: &mut SocketFile<Self::DataT>,
buf: &[u8],
) -> SyscallResult<Option<usize>> {
if self.can_send() {
match file.data.socket_type {
IcmpSocketType::Echo => {
if buf.len() < mem::size_of::<u16>() {
return Err(SyscallError::new(syscall::EINVAL));
}
let (seq_buf, payload) = buf.split_at(mem::size_of::<u16>());
let seq_no = NetworkEndian::read_u16(seq_buf);
let icmp_repr = Icmpv4Repr::EchoRequest {
ident: file.data.ident,
seq_no,
data: payload,
};
let icmp_payload = self.send(icmp_repr.buffer_len(), file.data.ip)
.map_err(|_| syscall::Error::new(syscall::EINVAL))?;
let mut icmp_packet = Icmpv4Packet::new_unchecked(icmp_payload);
//TODO: replace Default with actual caps
icmp_repr.emit(&mut icmp_packet, &Default::default());
Ok(Some(buf.len()))
}
IcmpSocketType::Udp => {
Err(SyscallError::new(syscall::EINVAL))
}
}
} else if file.flags & syscall::O_NONBLOCK == syscall::O_NONBLOCK {
Err(SyscallError::new(syscall::EAGAIN))
} else {
Ok(None) // internally scheduled to re-read
}
}
```
I try to figure it out by triggering time event only, and it seems to work:
```
diff --git a/src/ping/main.rs b/src/ping/main.rs
index 2c94104..3bbda3a 100644
--- a/src/ping/main.rs
+++ b/src/ping/main.rs
@@ -340,11 +340,11 @@ fn run() -> Result<()> {
move |_| ping_.borrow_mut().on_echo_event())?;
let ping_ = ping.clone();
- event_queue
+ let time_queue_id = event_queue
.add(time_fd as RawFd,
move |_| ping_.borrow_mut().on_time_event())?;
- event_queue.trigger_all(event::Event {
+ event_queue.trigger(time_queue_id, event::Event {
fd: 0,
flags: syscall::EventFlags::empty(),
})?;
```https://gitlab.redox-os.org/redox-os/relibc/-/issues/172Add UTIME_OMIT and UTIME_NOW2023-10-25T01:32:47ZSteve LauAdd UTIME_OMIT and UTIME_NOW~~>This is NOT an issue, I am new to GitLab and don't find anything similar to `discussions` on GitHub, so I post it as an issue.~~
-------
The [futimens(2)](https://pubs.opengroup.org/onlinepubs/9699919799/functions/futimens.html) sys...~~>This is NOT an issue, I am new to GitLab and don't find anything similar to `discussions` on GitHub, so I post it as an issue.~~
-------
The [futimens(2)](https://pubs.opengroup.org/onlinepubs/9699919799/functions/futimens.html) syscall,
which is used to update `atime` and `mtime` timestamps of a file, has two advantages over `utimes(2)`, cite
the man page from open group:
> If the `tv_nsec` field of a `timespec` structure has the special value `UTIME_NOW`,
> the file's relevant timestamp shall be set to the greatest value supported by
> the file system that is not greater than the current time.
> If the `tv_nsec` field has the special value `UTIME_OMIT`, the file's relevant
> timestamp shall not be changed. In either case, the `tv_sec` field shall be ignored.
Redox does not ~~seem to~~ support these two features as there is no `UTIME_NOW` and `UTIME_OMIT`
in `relibc`,
```shell
$ cd relibc
$ rg "UTIME_OMIT"
$ rg "UTIME_NOW"
```
~~Is there any plan to support these features?~~
~~Yes.~~https://gitlab.redox-os.org/redox-os/ion/-/issues/1016Panic on `&&` and `||` operators2022-11-19T07:45:37ZAurélien CléracPanic on `&&` and `||` operatorsbug: Logical operators `&&` and `||` may panic if not followed by a command.
expect: syntax error.
related: none.
test case#1
code: input
```
ls &&||
```
test case#2
code: input
```
ls &&;
```
actual: output
```
[...]
thread 'main' ...bug: Logical operators `&&` and `||` may panic if not followed by a command.
expect: syntax error.
related: none.
test case#1
code: input
```
ls &&||
```
test case#2
code: input
```
ls &&;
```
actual: output
```
[...]
thread 'main' panicked at 'begin <= end (6 <= 5) when slicing `ls &&||`', src/lib/parser/statement/splitter.rs:55:35
stack backtrace:
[...]
4: ion_shell::parser::statement::splitter::StatementSplitter::get_statement
5: <ion_shell::parser::statement::splitter::StatementSplitter as core::iter::traits::iterator::Iterator>::next
6: ion_shell::shell::flow::<impl ion_shell::shell::Shell>::on_command
7: ion::binary::InteractiveShell::exec
8: ion::binary::InteractiveShell::execute_interactive
9: ion::main
Abandon (core dumped)
```
expect: output
```
ion: syntax error: expected command, but found `||`
```
version: ion 1.0.0-alpha (x86_64-unknown-linux-gnu), rev 814ed5a887ad88b98b142af28f653ff4f249de6c
interaction: none
---
According to backtrace, the bug came from src/lib/parser/statement/splitter.rs:55:35 which is :
```
fn get_statement(&self, start: usize, end: usize) -> StatementVariant<'a> {
if self.logical == LogicalOp::And {
StatementVariant::And(self.data[start + 1..end].trim())
^^^^^^^^^^^^^^^
} else if self.logical == LogicalOp::Or {
StatementVariant::Or(self.data[start + 1..end].trim())
} else {
StatementVariant::Default(self.data[start..end].trim())
}
}
```
called by src/lib/parser/statement/splitter.rs:160:42 and src/lib/parser/statement/splitter.rs:171:42 :
```
b';' if self.paren_level == 0 => {
let statement = self.get_statement(start, i);
^^^^^^^^^^^^^^^^^^^^^^^
self.logical = LogicalOp::None;
self.read = i + 1;
return match error {
Some(error) => Some(Err(error)),
None => Some(Ok(statement)),
};
}
b'&' | b'|' if self.paren_level == 0 && last == Some(character) => {
// Detecting if there is a 2nd `&` character
let statement = self.get_statement(start, i - 1);
^^^^^^^^^^^^^^^^^^^^^^^^^^^
self.logical = if character == b'&' { LogicalOp::And } else { LogicalOp::Or };
self.read = i + 1;
return match error {
Some(error) => Some(Err(error)),
None => Some(Ok(statement)),
};
}
_ => {}
}
last = Some(character);
}
```
On both calls, _get_statement_ try to slice the command line with incorrect index.
If we pick test case#1, `ls &&||`, _start_ equals 5 but is added 1 and _i_ equals 6 minus 1 which gives `&"ls &&||"[6..5]`.
As I understand, syntax is checked along the command execution so a syntax error can be raised while Ion
has already executed N statements from a given command line. Ion could check if `self.logical` is already
set to _And_ or _Or_ instead of _None_ while performing `&&`, `||` or `;` but it does not look quite right
and did not pass cargo test(infinity loop) when I tried to implement it.
I'm pretty new to Rust and it feels a bit overwhelming for now to find an elegant solution which does fit well
with Ion's codebase.
Thanks in advance for your help,
Aurélienhttps://gitlab.redox-os.org/redox-os/redox/-/issues/1363Can't use apps downloaded with pkg2022-09-23T20:33:33ZNoé LopezCan't use apps downloaded with pkg<!-- Thank you for taking the time to submit an issue! By following these comments and filling out the sections below, you can help the developers get the necessary information to fix your issue. Please provide a single issue per report....<!-- Thank you for taking the time to submit an issue! By following these comments and filling out the sections below, you can help the developers get the necessary information to fix your issue. Please provide a single issue per report. You can also preview this report before submitting it. Feel free to modify/remove sections to fit the nature of your issue. -->
<!-- Please search to check that your issue has not been created already. By preventing duplicate issues, you can help keep the repository organized. If your current issue has already been created and is still unresolved, you can contribute by commenting there. -->
<!-- Replace the empty checkbox [ ] below with a checked one [x] if you have already searched for your issue. -->
- [x] I agree that I have searched opened and closed issues to prevent duplicates.
--------------------
## Description
<!-- Briefly summarize/describe the issue that you are experiencing below. -->
I can't launch applications that I downloaded with pkg (tested sodium and rusthello, same error)
## Environment info
<!-- To understand where your issue originates, please include some relevant information about your environment. -->
<!-- If you are using a pre-built release of Redox, please specify the release version below. -->
- Redox OS Release:
0.6.0
<!-- Depending on your issue, additional information about your environment (network config, package versions, dependencies, etc.) can also help. You can list that below. -->
Running on qemu kvm using the command listed in the book :
```
qemu-system-x86_64 -serial mon:stdio -d cpu_reset -d guest_errors -smp 4 -m 1024 -s -machine q35 -device ich9-intel-hda -device hda-duplex -net nic,model=e1000 -net user -device nec-usb-xhci,id=xhci -device usb-tablet,bus=xhci.0 -enable-kvm -cpu host -drive file=harddrive.bin,format=raw
```
## Steps to reproduce
<!-- If possible, please list the steps to reproduce ("trigger") your issue below. Being detailed definitely helps speed up bug fixes. -->
1. Download a package (`pkg install sodium`)
2. Open it (`$ sodium`)
3. Doesn't open
## Behavior
<!-- It may seem obvious to know what to expect, but isolating the behavior from everything else simplifies the development process. Remember to provide a single issue in this report. You can use the References section below to link your issues together. -->
<!-- Describe the behavior you expect your steps should yield (i.e., correct behavior). -->
- **Expected behavior**:
The app opens
<!-- Describe the behavior you observed when running your steps (i.e., buggy behavior). -->
- **Actual behavior**:
I get the following error in the kernel logs:
```
Invalid opcode fault
RFLAG: 0000000000010206
CS: 0000000000000023
RIP: 000000000044F96D
RAX: 0000000000000000
RCX: 000000000045D9E3
RDX: 0000000000000001
RDI: 0000000000000002
RSI: 000000000056FCA4
R8: 00000180000FFBD0
R9: 0000000001010000
R10: FFFFFFFFFFFFFFFF
R11: 0000000000000202
RBX: 00000180000FFE30
RBP: 0000000000000000
R12: 0000000000000000
R13: 0000000000000000
R14: 00000180000FFE30
R15: 0000000000000000
FS: 0000000000000033
TRACE: FFFFFF00004B72C8
FFFFFF00004B72C8: FFFF8000001389B8
FFFF8000001388C0+00F8
__interrupt_invalid_opcode
FFFFFF00004B7348: FFFF8000001011CF
FFFF8000001011A4+002B
invalid_opcode
0000000000000000: GUARD PAGE
kernel:INFO -- SIGNAL 4, CPU 3, PID ContextId(167)
kernel:INFO -- NAME file:/ui/bin/sodium
Ok("file:/ui/bin/orbterm") using deprecated funmap(...) call
```
And this one in the terminal:
```
panicked in ld.so: failed to open handle for process registers: expect failed for Result with err: No such device
ion: pipeline execution error: process (161) ended by signall SIGILL
```https://gitlab.redox-os.org/redox-os/ion/-/issues/1014README documentation links broken2022-09-17T14:22:20ZzraktvorREADME documentation links brokenBoth links to documentation in the README point to https://doc.redox-os.org/ion-manual/html, which gives an http error 404.
The correct link seems to be https://doc.redox-os.org/ion-manual.Both links to documentation in the README point to https://doc.redox-os.org/ion-manual/html, which gives an http error 404.
The correct link seems to be https://doc.redox-os.org/ion-manual.https://gitlab.redox-os.org/redox-os/redox/-/issues/1362Browser Resizing doesn't work as intended2023-10-27T13:50:46ZKtoksBrowser Resizing doesn't work as intended<!-- Thank you for taking the time to submit an issue! By following these comments and filling out the sections below, you can help the developers get the necessary information to fix your issue. Please provide a single issue per report....<!-- Thank you for taking the time to submit an issue! By following these comments and filling out the sections below, you can help the developers get the necessary information to fix your issue. Please provide a single issue per report. You can also preview this report before submitting it. Feel free to modify/remove sections to fit the nature of your issue. -->
<!-- Please search to check that your issue has not been created already. By preventing duplicate issues, you can help keep the repository organized. If your current issue has already been created and is still unresolved, you can contribute by commenting there. -->
<!-- Replace the empty checkbox [ ] below with a checked one [x] if you have already searched for your issue. -->
- [x] I agree that I have searched opened and closed issues to prevent duplicates.
--------------------
## Description
<!-- Briefly summarize/describe the issue that you are experiencing below. -->
When the user attempts to resize the browser horizontally or diagonally to the left, the browser drags in the direction the user is attempting to expand or contract the window size, vertical and right changes aren't registered, resizing does not work, and just places the browser at the top left of the screen
Upon further investigation, resizing in any way freezes the browser, and prevents the user from closing it. See second log for the second window I opened and attempted to resize vertically.
The third log is for maximizing the window- which also froze the browser.
## Environment info
<!-- To understand where your issue originates, please include some relevant information about your environment. -->
<!-- If you are using a pre-built release of Redox, please specify the release version below. -->
- Redox OS Release:
0.7.0
<!-- If you have built Redox OS yourself, please provide the following information: -->
- Operating system:
Pop! OS
- `uname -a`:
`Linux pop-os 5.18.10-76051810-generic #202207071639~1659108431~22.04~c9172fb SMP PREEMPT_DYNAMIC Fri J x86_64 x86_64 x86_64 GNU/Linux`
- `rustc -V`:
`rustc 1.62.1 (e092d0b6b 2022-07-16)`
- `git rev-parse HEAD`:
`git rev-parse HEAD`
<!-- Depending on your issue, additional information about your environment (network config, package versions, dependencies, etc.) can also help. You can list that below. -->
1080 16 x 9 resolution
## Steps to reproduce
<!-- If possible, please list the steps to reproduce ("trigger") your issue below. Being detailed definitely helps speed up bug fixes. -->
1. Open the browser
2. resize left moves the browser
3. resize vertical or right does nothing
## Behavior
<!-- It may seem obvious to know what to expect, but isolating the behavior from everything else simplifies the development process. Remember to provide a single issue in this report. You can use the References section below to link your issues together. -->
<!-- Describe the behavior you expect your steps should yield (i.e., correct behavior). -->
- **Expected behavior**:
The browser should resize in the direction the edge of the window is dragged, and when the maximize button is pressed, the browser should fill the screen
<!-- Describe the behavior you observed when running your steps (i.e., buggy behavior). -->
- **Actual behavior**:
left resize attempt causes dragging, right and vertical attempt fails to resize, the maximize button moves the browser to the top left of the screen without resizing, any form of resizing freezes the browser
<!-- **Logs?** Posting a log can help developers find your particular issue more easily. Please wrap your code in code blocks using triple back-ticks ``` to increase readability. -->
```
thread 'main' panicked at 'orbclient: failed to unmap memory in resize: Invalid argument', /home/papapop/.cargo/registry/src/github.com-1ecc6299db9ec823/orbclient-0.3.32/src/sys/orbital.rs:260:18
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
launcher: /ui/bin/file_manager (267) exited with exit status: 101
launcher: reaping zombie 268: exit status: 0
launcher: reaping zombie 269: exit status: 0
launcher: reaping zombie 270: exit status: 0
launcher: reaping zombie 271: exit status: 0
launcher: reaping zombie 272: exit status: 0
launcher: reaping zombie 273: exit status: 0
launcher: reaping zombie 274: exit status: 0
launcher: reaping zombie 275: exit status: 0
launcher: reaping zombie 276: exit status: 0
launcher: reaping zombie 277: exit status: 0
launcher: reaping zombie 278: exit status: 0
launcher: reaping zombie 279: exit status: 0
launcher: reaping zombie 280: exit status: 0
launcher: reaping zombie 281: exit status: 0
launcher: reaping zombie 282: exit status: 0
pte_osSemaphoreCancellablePend 0xa30c0 0x0
WARNING: You are using the SDL orbital video driver!
kernel::scheme::user:WARN -- Unaligned map size for context Some("/bin/netsurf-fb")
Setting mode 800x600@32
setsockopt(12, 6, 1, 0x7ffffffff4fc, 4) - unknown option
setsockopt(13, 6, 1, 0x7ffffffff4fc, 4) - unknown option
setsockopt(14, 6, 1, 0x7ffffffff4fc, 4) - unknown option
setsockopt(15, 6, 1, 0x7ffffffff4fc, 4) - unknown option
setsockopt(16, 6, 1, 0x7ffffffff4fc, 4) - unknown option
redoxfs: funmap 0xF000, 8192
thread '<unnamed>' panicked at 'orbclient: failed to unmap memory in resize: Invalid argument', /home/papapop/.cargo/registry/src/github.com-1ecc6299db9ec823/orbclient-0.3.29/src/sys/orbital.rs:260:18
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
fatal runtime error: failed to initiate panic, error 5
abort() called
Invalid opcode fault
RFLAG: 0000000000010202
CS: 0000000000000033
RIP: 00000000009a07ee
RSP: 00007ffffffff610
SS: 000000000000002b
FSBASE 0000000000004000
GSBASE 0000000000000000
KGSBASE fffffd8000000050
RAX: 0000000000000000
RCX: 0000000000a1bb63
RDX: 000000000000000f
RDI: 0000000000000002
RSI: 0000000000dc00a7
R8: 00007ffffffff520
R9: 0000000000000001
R10: 00007ffffffff528
R11: 0000000000000202
RBX: 0000000000d71ec0
RBP: 00000000010efa88
R12: 0000000000000001
R13: 00007ffffffff8e8
R14: 0000000000000000
R15: 00000000010a1868
TRACE: FFFFFE80018C52C0
FFFFFE80018C52C0: FFFFFF000008A0C7
FFFFFF0000089F90+0137
kernel::arch::x86_64::interrupt::exception::invalid_opcode::inner
FFFFFE80018C5350: FFFFFF0000087F2D
FFFFFF0000087F00+002D
kernel::arch::x86_64::interrupt::exception::invalid_opcode
00000000010EFA88: EMPTY RETURN
kernel:INFO -- SIGNAL 4, CPU 0, PID ContextId(283)
kernel:INFO -- NAME /bin/netsurf-fb
launcher: /bin/netsurf-fb (283) exited with signal: 4
pte_osSemaphoreCancellablePend 0xa30c0 0x0
WARNING: You are using the SDL orbital video driver!
kernel::scheme::user:WARN -- Unaligned map size for context Some("/bin/netsurf-fb")
Setting mode 800x600@32
setsockopt(12, 6, 1, 0x7ffffffff4fc, 4) - unknown option
setsockopt(13, 6, 1, 0x7ffffffff4fc, 4) - unknown option
setsockopt(14, 6, 1, 0x7ffffffff4fc, 4) - unknown option
setsockopt(15, 6, 1, 0x7ffffffff4fc, 4) - unknown option
setsockopt(16, 6, 1, 0x7ffffffff4fc, 4) - unknown option
redoxfs: funmap 0xF000, 8192
launcher: /bin/netsurf-fb (285) exited with exit status: 0
smolnetd::scheme: poll error: dropped by socket
```
Second resize log:
```
smolnetd::scheme: poll error: dropped by socket
pte_osSemaphoreCancellablePend 0xa30c0 0x0
WARNING: You are using the SDL orbital video driver!
kernel::scheme::user:WARN -- Unaligned map size for context Some("/bin/netsurf-fb")
Setting mode 800x600@32
setsockopt(12, 6, 1, 0x7ffffffff4fc, 4) - unknown option
setsockopt(13, 6, 1, 0x7ffffffff4fc, 4) - unknown option
setsockopt(14, 6, 1, 0x7ffffffff4fc, 4) - unknown option
setsockopt(15, 6, 1, 0x7ffffffff4fc, 4) - unknown option
setsockopt(16, 6, 1, 0x7ffffffff4fc, 4) - unknown option
redoxfs: funmap 0xF000, 8192
thread '<unnamed>' panicked at 'orbclient: failed to unmap memory in resize: Invalid argument', /home/papapop/.cargo/registry/src/github.com-1ecc6299db9ec823/orbclient-0.3.29/src/sys/orbital.rs:260:18
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
fatal runtime error: failed to initiate panic, error 5
abort() called
Invalid opcode fault
RFLAG: 0000000000010202
CS: 0000000000000033
RIP: 00000000009a07ee
RSP: 00007ffffffff610
SS: 000000000000002b
FSBASE 0000000000004000
GSBASE 0000000000000000
KGSBASE fffffd8000000050
RAX: 0000000000000000
RCX: 0000000000a1bb63
RDX: 000000000000000f
RDI: 0000000000000002
RSI: 0000000000dc00a7
R8: 00007ffffffff520
R9: 0000000000000001
R10: 00007ffffffff528
R11: 0000000000000202
RBX: 0000000000d71ec0
RBP: 00000000010efa88
R12: 0000000000000001
R13: 00007ffffffff8e8
R14: 0000000000000000
R15: 00000000010a1868
TRACE: FFFFFE80019232C0
FFFFFE80019232C0: FFFFFF000008A0C7
FFFFFF0000089F90+0137
kernel::arch::x86_64::interrupt::exception::invalid_opcode::inner
FFFFFE8001923350: FFFFFF0000087F2D
FFFFFF0000087F00+002D
kernel::arch::x86_64::interrupt::exception::invalid_opcode
00000000010EFA88: EMPTY RETURN
kernel:INFO -- SIGNAL 4, CPU 0, PID ContextId(287)
kernel:INFO -- NAME /bin/netsurf-fb
launcher: /bin/netsurf-fb (287) exited with signal: 4
```
Maximize log:
```
pte_osSemaphoreCancellablePend 0xa30c0 0x0
WARNING: You are using the SDL orbital video driver!
kernel::scheme::user:WARN -- Unaligned map size for context Some("/bin/netsurf-fb")
Setting mode 800x600@32
setsockopt(12, 6, 1, 0x7ffffffff4fc, 4) - unknown option
setsockopt(13, 6, 1, 0x7ffffffff4fc, 4) - unknown option
setsockopt(14, 6, 1, 0x7ffffffff4fc, 4) - unknown option
setsockopt(15, 6, 1, 0x7ffffffff4fc, 4) - unknown option
setsockopt(16, 6, 1, 0x7ffffffff4fc, 4) - unknown option
redoxfs: funmap 0xF000, 8192
thread '<unnamed>' panicked at 'orbclient: failed to unmap memory in resize: Invalid argument', /home/papapop/.cargo/registry/src/github.com-1ecc6299db9ec823/orbclient-0.3.29/src/sys/orbital.rs:260:18
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
fatal runtime error: failed to initiate panic, error 5
abort() called
Invalid opcode fault
RFLAG: 0000000000010202
CS: 0000000000000033
RIP: 00000000009a07ee
RSP: 00007ffffffff610
SS: 000000000000002b
FSBASE 0000000000004000
GSBASE 0000000000000000
KGSBASE fffffd8000000050
RAX: 0000000000000000
RCX: 0000000000a1bb63
RDX: 000000000000000f
RDI: 0000000000000002
RSI: 0000000000dc00a7
R8: 00007ffffffff520
R9: 0000000000000001
R10: 00007ffffffff528
R11: 0000000000000202
RBX: 0000000000d71ec0
RBP: 00000000010efa88
R12: 0000000000000001
R13: 00007ffffffff8e8
R14: 0000000000000000
R15: 00000000010a1868
TRACE: FFFFFE800195A2C0
FFFFFE800195A2C0: FFFFFF000008A0C7
FFFFFF0000089F90+0137
kernel::arch::x86_64::interrupt::exception::invalid_opcode::inner
FFFFFE800195A350: FFFFFF0000087F2D
FFFFFF0000087F00+002D
kernel::arch::x86_64::interrupt::exception::invalid_opcode
00000000010EFA88: EMPTY RETURN
kernel:INFO -- SIGNAL 4, CPU 0, PID ContextId(289)
kernel:INFO -- NAME /bin/netsurf-fb
launcher: /bin/netsurf-fb (289) exited with signal: 4
```
<!-- **Solution?** Have a solution in mind? Propose your solution below. -->
- **Proposed solution**:
<!-- **Screenshots?** Make it easier to get your point across with screenshots. You can drag & drop or paste your images below. -->
## Optional references
<!-- If you have found issues or pull requests that are related to or blocking this issue, please link them below. See https://help.github.com/articles/autolinked-references-and-urls/ for more options. You can also link related code snippets by providing the permalink. See https://help.github.com/articles/creating-a-permanent-link-to-a-code-snippet/ for more information. -->
Related to:
- #1360
## Optional extras
<!-- If you have other relevant information not found in other sections, you can include it below. -->
<!-- **Code?** Awesome! You can also create a pull request with a reference to this issue. -->
<!-- **Files?** Attach your relevant files by dragging & dropping or pasting them below. -->
<!-- You also can preview your report before submitting it. Thanks for contributing to Redox! -->https://gitlab.redox-os.org/redox-os/redox/-/issues/1360Resize Display Horizontally Crashes Current Window2023-10-27T13:49:36ZKtoksResize Display Horizontally Crashes Current Window<!-- Thank you for taking the time to submit an issue! By following these comments and filling out the sections below, you can help the developers get the necessary information to fix your issue. Please provide a single issue per report....<!-- Thank you for taking the time to submit an issue! By following these comments and filling out the sections below, you can help the developers get the necessary information to fix your issue. Please provide a single issue per report. You can also preview this report before submitting it. Feel free to modify/remove sections to fit the nature of your issue. -->
<!-- Please search to check that your issue has not been created already. By preventing duplicate issues, you can help keep the repository organized. If your current issue has already been created and is still unresolved, you can contribute by commenting there. -->
<!-- Replace the empty checkbox [ ] below with a checked one [x] if you have already searched for your issue. -->
- [x] I agree that I have searched opened and closed issues to prevent duplicates.
--------------------
## Description
<!-- Briefly summarize/describe the issue that you are experiencing below. -->
Upon opening nearly any app and attempting to resize it horizontally or diagonally, or hitting the maximize button in full screen, the app will crash and close.
## Environment info
<!-- To understand where your issue originates, please include some relevant information about your environment. -->
<!-- If you are using a pre-built release of Redox, please specify the release version below. -->
- Redox OS Release:
0.7.0
<!-- If you have built Redox OS yourself, please provide the following information: -->
- Operating system:
Pop! OS
- `uname -a`:
`Linux pop-os 5.18.10-76051810-generic #202207071639~1659108431~22.04~c9172fb SMP PREEMPT_DYNAMIC Fri J x86_64 x86_64 x86_64 GNU/Linux`
- `rustc -V`:
`rustc 1.62.1 (e092d0b6b 2022-07-16)`
- `git rev-parse HEAD`:
`git rev-parse HEAD`
<!-- Depending on your issue, additional information about your environment (network config, package versions, dependencies, etc.) can also help. You can list that below. -->
1080 16 x 9 resolution
## Steps to reproduce
<!-- If possible, please list the steps to reproduce ("trigger") your issue below. Being detailed definitely helps speed up bug fixes. -->
1. Log in
2. Open an app with resize-ability (Except for the browser, see #1362)
3. Resize horizontally, or diagonally, or returning from full screen with 'maximize' button
## Behavior
<!-- It may seem obvious to know what to expect, but isolating the behavior from everything else simplifies the development process. Remember to provide a single issue in this report. You can use the References section below to link your issues together. -->
<!-- Describe the behavior you expect your steps should yield (i.e., correct behavior). -->
- **Expected behavior**:
App window resizes and is fully adjustable to whatever size without crashing
<!-- Describe the behavior you observed when running your steps (i.e., buggy behavior). -->
- **Actual behavior**:
Crashes on resize horizontally or diagonally
<!-- **Logs?** Posting a log can help developers find your particular issue more easily. Please wrap your code in code blocks using triple back-ticks ``` to increase readability. -->
```
thread 'main' panicked at 'orbclient: failed to unmap memory in resize: Invalid argument', /home/papapop/.cargo/registry/src/github.com-1ecc6299db9ec823/orbclient-0.3.32/src/sys/orbital.rs:260:18
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
launcher: /ui/bin/editor (266) exited with exit status: 101
```
<!-- **Solution?** Have a solution in mind? Propose your solution below. -->
- **Proposed solution**:
Fix the unmapping error shown above
<!-- **Screenshots?** Make it easier to get your point across with screenshots. You can drag & drop or paste your images below. -->
## Optional references
<!-- If you have found issues or pull requests that are related to or blocking this issue, please link them below. See https://help.github.com/articles/autolinked-references-and-urls/ for more options. You can also link related code snippets by providing the permalink. See https://help.github.com/articles/creating-a-permanent-link-to-a-code-snippet/ for more information. -->
## Optional extras
<!-- If you have other relevant information not found in other sections, you can include it below. -->
<!-- **Code?** Awesome! You can also create a pull request with a reference to this issue. -->
<!-- **Files?** Attach your relevant files by dragging & dropping or pasting them below. -->
<!-- You also can preview your report before submitting it. Thanks for contributing to Redox! -->https://gitlab.redox-os.org/redox-os/redox/-/issues/1358Redox Menu Doesn't Close2023-06-13T02:04:55ZKtoksRedox Menu Doesn't Close<!-- Thank you for taking the time to submit an issue! By following these comments and filling out the sections below, you can help the developers get the necessary information to fix your issue. Please provide a single issue per report....<!-- Thank you for taking the time to submit an issue! By following these comments and filling out the sections below, you can help the developers get the necessary information to fix your issue. Please provide a single issue per report. You can also preview this report before submitting it. Feel free to modify/remove sections to fit the nature of your issue. -->
<!-- Please search to check that your issue has not been created already. By preventing duplicate issues, you can help keep the repository organized. If your current issue has already been created and is still unresolved, you can contribute by commenting there. -->
<!-- Replace the empty checkbox [ ] below with a checked one [x] if you have already searched for your issue. -->
- [x] I agree that I have searched opened and closed issues to prevent duplicates.
--------------------
## Description
<!-- Briefly summarize/describe the issue that you are experiencing below. -->
Upon starting the shell, it doesn't display the directory it is in.
## Environment info
<!-- To understand where your issue originates, please include some relevant information about your environment. -->
<!-- If you are using a pre-built release of Redox, please specify the release version below. -->
- Redox OS Release:
0.7.0 Commit: 8e0af3b8475f28670c38275971e454d3146561ac
<!-- If you have built Redox OS yourself, please provide the following information: -->
- Operating system:
Pop! OS
- `uname -a`:
`Linux pop-os 5.18.10-76051810-generic #202207071639~1659108431~22.04~c9172fb SMP PREEMPT_DYNAMIC Fri J x86_64 x86_64 x86_64 GNU/Linux`
- `rustc -V`:
`rustc 1.62.1 (e092d0b6b 2022-07-16)`
- `git rev-parse HEAD`:
`git rev-parse HEAD`
<!-- Depending on your issue, additional information about your environment (network config, package versions, dependencies, etc.) can also help. You can list that below. -->
- Environment:
Brand new install
Desktop PC
Ethernet
Recent Pop! install
## Steps to reproduce
<!-- If possible, please list the steps to reproduce ("trigger") your issue below. Being detailed definitely helps speed up bug fixes. -->
1. Started Redox for first time
2. Logged in
3. Clicked menu button on bottom left corner of screen, clicked out.
## Behavior
<!-- It may seem obvious to know what to expect, but isolating the behavior from everything else simplifies the development process. Remember to provide a single issue in this report. You can use the References section below to link your issues together. -->
<!-- Describe the behavior you expect your steps should yield (i.e., correct behavior). -->
- **Expected behavior**:
Menu closes upon clicking out, or on a menu object
<!-- Describe the behavior you observed when running your steps (i.e., buggy behavior). -->
- **Actual behavior**:
Menu stays visible, but unable to select objects upon further clicks until the menu button is selected again
<!-- **Logs?** Posting a log can help developers find your particular issue more easily. Please wrap your code in code blocks using triple back-ticks ``` to increase readability. -->
```
kernel::scheme::user:WARN -- Unaligned map size for context Some("/ui/bin/launcher")
```
<!-- **Solution?** Have a solution in mind? Propose your solution below. -->
- **Proposed solution**:
Fix the above warning that is displayed every time the menu is selected? Or perhaps the object is just not removed properly after selection
<!-- **Screenshots?** Make it easier to get your point across with screenshots. You can drag & drop or paste your images below. -->
![image](/uploads/f14b3fe657975f950fce431cafb1a916/image.png)
## Optional references
<!-- If you have found issues or pull requests that are related to or blocking this issue, please link them below. See https://help.github.com/articles/autolinked-references-and-urls/ for more options. You can also link related code snippets by providing the permalink. See https://help.github.com/articles/creating-a-permanent-link-to-a-code-snippet/ for more information. -->
## Optional extras
<!-- If you have other relevant information not found in other sections, you can include it below. -->
<!-- **Code?** Awesome! You can also create a pull request with a reference to this issue. -->
<!-- **Files?** Attach your relevant files by dragging & dropping or pasting them below. -->
<!-- You also can preview your report before submitting it. Thanks for contributing to Redox! -->https://gitlab.redox-os.org/redox-os/orbclient/-/issues/45Panic on resizing windows2022-08-03T17:09:23ZNagy Tiborxnagytibor@gmail.comPanic on resizing windowsAfter some recent Redox kernel/syscall changes orbclient started panicking on resizing windows:
```
thread 'main' panicked at 'orbclient: failed to unmap memory in resize: Invalid argument', /home/user/.cargo/registry/src/github.com-1ec...After some recent Redox kernel/syscall changes orbclient started panicking on resizing windows:
```
thread 'main' panicked at 'orbclient: failed to unmap memory in resize: Invalid argument', /home/user/.cargo/registry/src/github.com-1ecc6299db9ec823/orbclient-0.3.32/src/sys/orbital.rs:260:18
```
The panic is reproducible with any Redox desktop app with resizable windows.https://gitlab.redox-os.org/redox-os/kernel/-/issues/109initfs: Kernel panic when reading directory entries2022-07-29T21:56:31ZNagy Tiborxnagytibor@gmail.cominitfs: Kernel panic when reading directory entries**Repro:**
```rust
use std::{fs::File, io::{Read, Seek, SeekFrom}};
fn main() -> std::io::Result<()> {
let mut file = File::open("initfs:")?;
let mut pos1: [u8; 2] = [0, 0];
file.seek(SeekFrom::Start(1))?;
file.read_ex...**Repro:**
```rust
use std::{fs::File, io::{Read, Seek, SeekFrom}};
fn main() -> std::io::Result<()> {
let mut file = File::open("initfs:")?;
let mut pos1: [u8; 2] = [0, 0];
file.seek(SeekFrom::Start(1))?;
file.read_exact(&mut pos1)?;
println!("{:?}", pos1);
Ok(())
}
```
**Stack trace:**
```
KERNEL PANIC: panicked at 'index out of bounds: the len is 2 but the index is 2', src/scheme/initfs.rs:185:25
TRACE: FFFFFE80002947F0
FFFFFE80002947F0: FFFFFF00000BD167
FFFFFF00000BD010+0157
rust_begin_unwind
FFFFFE80002948F0: FFFFFF0000015C93
FFFFFF0000015C60+0033
core::panicking::panic_fmt
FFFFFE8000294930: FFFFFF0000015C56
FFFFFF0000015BF0+0066
core::panicking::panic_bounds_check
FFFFFE80002949A0: FFFFFF00000C475B
FFFFFF00000C4390+03CB
<kernel::scheme::initfs::InitFsScheme as syscall::scheme::scheme::Scheme>::read
FFFFFE8000294A40: FFFFFF00000C42DF
FFFFFF00000C4050+028F
syscall::scheme::scheme::Scheme::handle
FFFFFE8000294A90: FFFFFF00000BF277
FFFFFF00000BEF00+0377
kernel::syscall::fs::file_op
FFFFFE8000294B50: FFFFFF0000059A31
FFFFFF0000058BA0+0E91
kernel::syscall::syscall
FFFFFE8000294EE0: FFFFFF00000BCFB0
FFFFFF00000BCF40+0070
__inner_syscall_instruction
FFFFFE8000294F50: FFFFFF00000BCEF3
FFFFFF00000BCEB0+0043
kernel::arch::x86_64::interrupt::syscall::syscall_instruction
0000000000411EF0: 7FFFFFFFFFFFFFFF
B8483E8BFB894853: GUARD PAGE
CPU 1, PID ContextId(65)
```https://gitlab.redox-os.org/redox-os/kernel/-/issues/108initfs: Directory entries are not separated anymore2022-07-29T21:56:30ZNagy Tiborxnagytibor@gmail.cominitfs: Directory entries are not separated anymore**Repro:**
Open the shell then run:
```
$ ls initfs:/bin
pcidramfsnvmedlogdranddps2dvesadredoxfsinitzerodahcidnulldacpid
```
Notice how the directory names are clumped together without any separators. The `initfs:` scheme doesn't prop...**Repro:**
Open the shell then run:
```
$ ls initfs:/bin
pcidramfsnvmedlogdranddps2dvesadredoxfsinitzerodahcidnulldacpid
```
Notice how the directory names are clumped together without any separators. The `initfs:` scheme doesn't properly separate the directory entries anymore.