redox-os issueshttps://gitlab.redox-os.org/groups/redox-os/-/issues2018-06-15T11:40:03Zhttps://gitlab.redox-os.org/redox-os/redox/-/issues/651Switch from multirust to rustup2018-06-15T11:40:03ZJeremy SollerSwitch from multirust to rustup*Created by: s22h*
I'd like to start a motion to move from multirust to [rustup](https://www.rustup.rs/) in bootstrap.sh.
According to the multirust repository it is not maintained anymore and recommends to migrate to rustup, which is ...*Created by: s22h*
I'd like to start a motion to move from multirust to [rustup](https://www.rustup.rs/) in bootstrap.sh.
According to the multirust repository it is not maintained anymore and recommends to migrate to rustup, which is an official Rust project.
The change shouldn't be too difficult (at least on Linux and OSX, I don't know how it's handled in Windows), since the syntax is the same as in multirust.
https://gitlab.redox-os.org/redox-os/redox/-/issues/650build failed2018-06-15T11:40:03ZJeremy Sollerbuild failed*Created by: since2016-05-22*
**Reproduction**: [run "lazy" script on https://doc.redox-os.org/book/getting_started/preparing_the_build.html]
**Expected behavior**: []
**Actual behavior**: [Compiling fuse v0.2.7
error: failed to run c...*Created by: since2016-05-22*
**Reproduction**: [run "lazy" script on https://doc.redox-os.org/book/getting_started/preparing_the_build.html]
**Expected behavior**: []
**Actual behavior**: [Compiling fuse v0.2.7
error: failed to run custom build command for `fuse v0.2.7`
Process didn't exit successfully: `/home/user/Downloads/redox/redox/crates/redoxfs/target/debug/build/fuse-5b87eb71951205b4/build-script-build` (exit code: 101)
--- stderr
thread '<main>' panicked at 'called `Result::unwrap()` on an `Err` value: "Failed to run `\"pkg-config\" \"--libs\" \"--cflags\" \"fuse\"`: No such file or directory (os error 2)"', ../src/libcore/result.rs:785
note: Run with `RUST_BACKTRACE=1` for a backtrace.
Makefile:566: recipe for target 'build/i386-unknown-redox/debug/filesystem.bin' failed
make: **\* [build/i386-unknown-redox/debug/filesystem.bin] Error 101].
**Build information**: [output of `rustc -V`:multirust: no default toolchain configured, `git rev-parse HEAD`: d307aa23de0a1fe8de1e8254ce33626816ef6f84, `uname -a`: Linux debian 4.5.0-0.bpo.2-amd64 #1 SMP Debian 4.5.3-2~bpo8+1 (2016-05-13) x86_64 GNU/Linux]
---
https://gitlab.redox-os.org/redox-os/redox/-/issues/646Building for x86_64 on Mac OS X Yosemite appears to try to link i386 intermed...2018-06-15T11:40:03ZJeremy SollerBuilding for x86_64 on Mac OS X Yosemite appears to try to link i386 intermediates*Created by: rowedonalde*
**Prereq**: Obtain x86_64 tools per the instructions at https://github.com/redox-os/redox/issues/165#issuecomment-152465299
**Reproduction**: cd to root of cloned repo, and then:
```
export ARCH=x86_64
make a...*Created by: rowedonalde*
**Prereq**: Obtain x86_64 tools per the instructions at https://github.com/redox-os/redox/issues/165#issuecomment-152465299
**Reproduction**: cd to root of cloned repo, and then:
```
export ARCH=x86_64
make all
```
**Expected behavior**: Redox builds successfully in x86_64, and I can run it with `make qemu`
**Actual behavior**: `make all` fails while compiling `crates/init/main.rs` and complains that linking fails because the input files are i386
**Build information**: Output from `make all`:
```
mkdir -p build/x86_64-unknown-redox/debug
RUST_BACKTRACE=1 rustc --target=x86_64-unknown-redox.json -L build/x86_64-unknown-redox/debug -C no-prepopulate-passes -C no-stack-check -C opt-level=2 -Z no-landing-pads -A dead_co
de -C ar=x86_64-elf-ar -C linker=x86_64-elf-gcc -o build/x86_64-unknown-redox/debug/libcore.rlib rust/src/libcore/lib.rs
RUST_BACKTRACE=1 rustc --target=x86_64-unknown-redox.json -L build/x86_64-unknown-redox/debug -C no-prepopulate-passes -C no-stack-check -C opt-level=2 -Z no-landing-pads -A dead_co
de -C ar=x86_64-elf-ar -C linker=x86_64-elf-gcc --crate-name bitflags --crate-type lib -o build/x86_64-unknown-redox/debug/libbitflags.rlib crates/bitflags/src/lib.rs
RUST_BACKTRACE=1 rustc --target=x86_64-unknown-redox.json -L build/x86_64-unknown-redox/debug -C no-prepopulate-passes -C no-stack-check -C opt-level=2 -Z no-landing-pads -A dead_co
de -C ar=x86_64-elf-ar -C linker=x86_64-elf-gcc -o build/x86_64-unknown-redox/debug/libio.rlib crates/io/lib.rs
RUST_BACKTRACE=1 rustc --target=x86_64-unknown-redox.json -L build/x86_64-unknown-redox/debug -C no-prepopulate-passes -C no-stack-check -C opt-level=2 -Z no-landing-pads -A dead_co
de -C ar=x86_64-elf-ar -C linker=x86_64-elf-gcc -o build/x86_64-unknown-redox/debug/liballoc_malloc.rlib liballoc_malloc/lib.rs -L native=libc/lib/
RUST_BACKTRACE=1 rustc --target=x86_64-unknown-redox.json -L build/x86_64-unknown-redox/debug -C no-prepopulate-passes -C no-stack-check -C opt-level=2 -Z no-landing-pads -A dead_co
de -C ar=x86_64-elf-ar -C linker=x86_64-elf-gcc -o build/x86_64-unknown-redox/debug/liballoc_system.rlib liballoc_system/lib.rs
RUST_BACKTRACE=1 rustc --target=x86_64-unknown-redox.json -L build/x86_64-unknown-redox/debug -C no-prepopulate-passes -C no-stack-check -C opt-level=2 -Z no-landing-pads -A dead_co
de -C ar=x86_64-elf-ar -C linker=x86_64-elf-gcc -o build/x86_64-unknown-redox/debug/liballoc.rlib rust/src/liballoc/lib.rs
RUST_BACKTRACE=1 rustc --target=x86_64-unknown-redox.json -L build/x86_64-unknown-redox/debug -C no-prepopulate-passes -C no-stack-check -C opt-level=2 -Z no-landing-pads -A dead_co
de -C ar=x86_64-elf-ar -C linker=x86_64-elf-gcc -o build/x86_64-unknown-redox/debug/librustc_unicode.rlib rust/src/librustc_unicode/lib.rs
RUST_BACKTRACE=1 rustc --target=x86_64-unknown-redox.json -L build/x86_64-unknown-redox/debug -C no-prepopulate-passes -C no-stack-check -C opt-level=2 -Z no-landing-pads -A dead_co
de -C ar=x86_64-elf-ar -C linker=x86_64-elf-gcc -o build/x86_64-unknown-redox/debug/libcollections.rlib rust/src/libcollections/lib.rs
RUST_BACKTRACE=1 rustc --target=x86_64-unknown-redox.json -L build/x86_64-unknown-redox/debug -C no-prepopulate-passes -C no-stack-check -C opt-level=2 -Z no-landing-pads -A dead_co
de -C ar=x86_64-elf-ar -C linker=x86_64-elf-gcc -o build/x86_64-unknown-redox/debug/librand.rlib rust/src/librand/lib.rs
RUST_BACKTRACE=1 rustc --target=x86_64-unknown-redox.json -L build/x86_64-unknown-redox/debug -C no-prepopulate-passes -C no-stack-check -C opt-level=2 -Z no-landing-pads -A dead_co
de -C ar=x86_64-elf-ar -C linker=x86_64-elf-gcc -o build/x86_64-unknown-redox/debug/libsystem.rlib crates/system/lib.rs
RUST_BACKTRACE=1 rustc --target=x86_64-unknown-redox.json -L build/x86_64-unknown-redox/debug -C no-prepopulate-passes -C no-stack-check -C opt-level=2 -Z no-landing-pads -A dead_co
de -C ar=x86_64-elf-ar -C linker=x86_64-elf-gcc -o build/x86_64-unknown-redox/debug/libstd.rlib libstd/src/lib.rs -L native=libc/lib/
mkdir -p initfs/bin/
RUST_BACKTRACE=1 rustc --target=x86_64-unknown-redox.json -L build/x86_64-unknown-redox/debug -C no-prepopulate-passes -C no-stack-check -C opt-level=2 -Z no-landing-pads -A dead_co
de -C ar=x86_64-elf-ar -C linker=x86_64-elf-gcc -C lto --crate-type bin -o initfs/bin/init crates/init/main.rs
error: linking with `x86_64-elf-gcc` failed: exit code: 1
note: "x86_64-elf-gcc" "-m64" "-nostdlib" "-static" "-L" "/Users/don/.multirust/toolchains/nightly/lib/rustlib/x86_64-unknown-redox.json/lib" "initfs/bin/init.0.o" "-o" "initfs/bin/
init" "-Wl,--gc-sections" "-nodefaultlibs" "-L" "build/x86_64-unknown-redox/debug" "-L" "/Users/don/.multirust/toolchains/nightly/lib/rustlib/x86_64-unknown-redox.json/lib" "-Wl,-Bs
tatic" "-Wl,-Bdynamic" "/var/folders/x6/r9vc_y8n0hqc_txxy1wz7r9w0000gn/T/rustc.lruKETKEvdFz/libstd.rlib" "/var/folders/x6/r9vc_y8n0hqc_txxy1wz7r9w0000gn/T/rustc.lruKETKEvdFz/libcoll
ections.rlib" "/var/folders/x6/r9vc_y8n0hqc_txxy1wz7r9w0000gn/T/rustc.lruKETKEvdFz/libsystem.rlib" "/var/folders/x6/r9vc_y8n0hqc_txxy1wz7r9w0000gn/T/rustc.lruKETKEvdFz/liballoc.rlib
" "/var/folders/x6/r9vc_y8n0hqc_txxy1wz7r9w0000gn/T/rustc.lruKETKEvdFz/liballoc_malloc.rlib" "/var/folders/x6/r9vc_y8n0hqc_txxy1wz7r9w0000gn/T/rustc.lruKETKEvdFz/librand.rlib" "/var
/folders/x6/r9vc_y8n0hqc_txxy1wz7r9w0000gn/T/rustc.lruKETKEvdFz/librustc_unicode.rlib" "/var/folders/x6/r9vc_y8n0hqc_txxy1wz7r9w0000gn/T/rustc.lruKETKEvdFz/libcore.rlib"
note: /usr/local/Cellar/x86_64-elf-gcc/5.3.0/lib/gcc/x86_64-elf/5.3.0/../../../../x86_64-elf/bin/ld: i386 architecture of input file `/var/folders/x6/r9vc_y8n0hqc_txxy1wz7r9w0000gn/
T/rustc.lruKETKEvdFz/liballoc_malloc.rlib(lib_a-malloc.o)' is incompatible with i386:x86-64 output
/usr/local/Cellar/x86_64-elf-gcc/5.3.0/lib/gcc/x86_64-elf/5.3.0/../../../../x86_64-elf/bin/ld: i386 architecture of input file `/var/folders/x6/r9vc_y8n0hqc_txxy1wz7r9w0000gn/T/rust
c.lruKETKEvdFz/liballoc_malloc.rlib(lib_a-mallocr.o)' is incompatible with i386:x86-64 output
[...and so on...]
```
Running `readelf -h build/x86_64-unknown-redox/debug/*.rlib` reveals a mixture of ELF32 and ELF64 classes like
```
File: build/x86_64-unknown-redox/debug/libsystem.rlib(libsystem.0.o)
ELF Header:
Magic: 7f 45 4c 46 02 01 01 00 00 00 00 00 00 00 00 00
Class: ELF64
Data: 2's complement, little endian
Version: 1 (current)
OS/ABI: UNIX - System V
ABI Version: 0
Type: REL (Relocatable file)
Machine: Advanced Micro Devices X86-64
Version: 0x1
Entry point address: 0x0
Start of program headers: 0 (bytes into file)
Start of section headers: 49096 (bytes into file)
Flags: 0x0
Size of this header: 64 (bytes)
Size of program headers: 0 (bytes)
Number of program headers: 0
Size of section headers: 64 (bytes)
Number of section headers: 357
Section header string table index: 1
```
and
```
File: build/x86_64-unknown-redox/debug/libstd.rlib(lib_a-w_tgamma.o)
ELF Header:
Magic: 7f 45 4c 46 01 01 01 00 00 00 00 00 00 00 00 00
Class: ELF32
Data: 2's complement, little endian
Version: 1 (current)
OS/ABI: UNIX - System V
ABI Version: 0
Type: REL (Relocatable file)
Machine: Intel 80386
Version: 0x1
Entry point address: 0x0
Start of program headers: 0 (bytes into file)
Start of section headers: 10356 (bytes into file)
Flags: 0x0
Size of this header: 52 (bytes)
Size of program headers: 0 (bytes)
Number of program headers: 0
Size of section headers: 40 (bytes)
Number of section headers: 14
Section header string table index: 11
```
https://gitlab.redox-os.org/redox-os/redox/-/issues/675What happened to "This Week in Redox"?2018-06-15T11:40:03ZJeremy SollerWhat happened to "This Week in Redox"?*Created by: flosse*
I'm quite curious how everything is going on :) And I'd love to read a new TWR :)
*Created by: flosse*
I'm quite curious how everything is going on :) And I'd love to read a new TWR :)
https://gitlab.redox-os.org/redox-os/redox/-/issues/667multirust Deprecated2018-06-15T11:40:03ZJeremy Sollermultirust Deprecated*Created by: qaute*
**Problem**: [describe the problem you try to solve with this issue.]
README.md recommends [multirust](https://github.com/brson/multirust), whose documentation states it has been deprecated in favor of [rustup.rs](ht...*Created by: qaute*
**Problem**: [describe the problem you try to solve with this issue.]
README.md recommends [multirust](https://github.com/brson/multirust), whose documentation states it has been deprecated in favor of [rustup.rs](https://github.com/rust-lang-nursery/rustup.rs). This might be worth consideration (though maybe multirust is still preferred and works just fine, IDK).
https://gitlab.redox-os.org/redox-os/redox/-/issues/640Use PNGs instead of uncompressed BMP images for UI2018-06-15T11:40:02ZJeremy SollerUse PNGs instead of uncompressed BMP images for UI*Created by: archshift*
PNGs are smaller, and it's likely that more time will be spent reading bitmaps from the disk than decoding the image from PNGs.
*Created by: archshift*
PNGs are smaller, and it's likely that more time will be spent reading bitmaps from the disk than decoding the image from PNGs.
https://gitlab.redox-os.org/redox-os/redox/-/issues/662Page fault when using file explorer2018-06-15T11:40:02ZJeremy SollerPage fault when using file explorer*Created by: skylerberg*
**Reproduction**:
Cannot repro. Here is what I did:
- Start orbital using the third screen size (1024x748 or something like that).
- Open the file explorer
- Navigate to the ui folder
- Triple click on cursor.b...*Created by: skylerberg*
**Reproduction**:
Cannot repro. Here is what I did:
- Start orbital using the third screen size (1024x748 or something like that).
- Open the file explorer
- Navigate to the ui folder
- Triple click on cursor.bmp
**Expected behavior**:
Image opens three times.
**Actual behavior**:
Page fault crashes file explorer. One of the instances of the image failed to load as well, but I will detail that in a different issue.
**Build information**:
qemu on Ubuntu 14.04
rustc 1.11.0-nightly (696b703b5 2016-07-03)
current commit: e2b5a29946f003eed13be678460e145ec27727b6
**Misc**:
```
[163.879] DEBUG PID 24: file:/apps/file_manager/main.bin
[163.879] DEBUG SYS 80624CE: 120 clone 4100 0 1804C298
[163.879] DEBUG INT E: Page fault
[163.879] DEBUG CS: 00000008 IP: 00123903 FLG: 00010006
[163.879] DEBUG SS: 00000000 SP: 84B52000 BP: 05844E88
[163.879] DEBUG AX: 07FAF000 BX: 05844F00 CX: 00099000 DX: 00100000
[163.879] DEBUG DI: 81B1E030 SI: 81B1E030
[163.879] DEBUG CR0: 80010033 CR2: 08048000 CR3: 01000000 CR4: 00000600
[163.879] DEBUG FSW: 00000120 FCW: 0000037F
[163.879] DEBUG ERR: 00000003
```
https://gitlab.redox-os.org/redox-os/redox/-/issues/663Open an image multiple times quickly causes the image to fail to load.2018-06-15T11:40:02ZJeremy SollerOpen an image multiple times quickly causes the image to fail to load.*Created by: skylerberg*
**Reproduction**: Open the file explorer and triple click an image file.
**Expected behavior**: Image opens thrice.
**Actual behavior**: The first attempt to open the image loads a box that says `failed to rea...*Created by: skylerberg*
**Reproduction**: Open the file explorer and triple click an image file.
**Expected behavior**: Image opens thrice.
**Actual behavior**: The first attempt to open the image loads a box that says `failed to read image: Bad file number (o`... The rest is not visible and I don't know of a way to scroll the box.
**Build information**: See https://github.com/redox-os/redox/issues/662 for build information, this happened at the same time.
https://gitlab.redox-os.org/redox-os/redox/-/issues/636feature wish: multiple input devices2023-06-13T04:42:45ZJeremy Sollerfeature wish: multiple input devices*Created by: tiborgats*
I wish for the possibility to be able to handle two mouses, two keyboards, or more. For example if someone already has two monitors, it would be nice for two users to be able to work simultaneously on the same ma...*Created by: tiborgats*
I wish for the possibility to be able to handle two mouses, two keyboards, or more. For example if someone already has two monitors, it would be nice for two users to be able to work simultaneously on the same machine by connecting an extra mouse & keyboard. (Even if one of them is working inside a virtual machine.)
It would also open new possibilities for gaming if it were possible to use two mouses, for both hands at the same time.https://gitlab.redox-os.org/redox-os/redox/-/issues/658Boostrap script does not download Redox repositories2018-06-15T11:40:02ZJeremy SollerBoostrap script does not download Redox repositories*Created by: Csega*
**Reproduction**: Run bootstrap script: curl -sf https://raw.githubusercontent.com/redox-os/redox/master/bootstrap.sh -o bootstrap.sh && bash -e bootstrap.sh
**Expected behavior**: Download the newest Rust version a...*Created by: Csega*
**Reproduction**: Run bootstrap script: curl -sf https://raw.githubusercontent.com/redox-os/redox/master/bootstrap.sh -o bootstrap.sh && bash -e bootstrap.sh
**Expected behavior**: Download the newest Rust version and download the repositories.
**Actual behavior**: The newest Rust version (changing multirust to rustup) is installed, but the redox repositories are not copied.
**Build information**: rustc 1.11.0-nightly (ad7fe6521 2016-06-23), qemu-i386 version 2.0.0 (Debian 2.0.0+dfsg-2ubuntu1.24), Copyright (c) 2003-2008 Fabrice Bellard, Linux eOS 3.19.0-61-generic #69~14.04.1-Ubuntu SMP Thu Jun 9 09:09:13 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
**Blocking/related**: [issues or PRs blocking or being related to this issue.]
**Misc**: [optional: for other relevant information that should be known or cannot be described in the other fields.]
---
_If the above does not fit the nature of the issue feel free to modify it._
https://gitlab.redox-os.org/redox-os/redox/-/issues/656Mattermost chat server has SSL certificate issues.2018-06-15T11:40:02ZJeremy SollerMattermost chat server has SSL certificate issues.*Created by: ca1ek*
cc @ticki @jackpot51 #649
Someone forgot to renew the certificate. Manjaro Linux much?
*Created by: ca1ek*
cc @ticki @jackpot51 #649
Someone forgot to renew the certificate. Manjaro Linux much?
https://gitlab.redox-os.org/redox-os/redox/-/issues/629[Book] Missing words on Microkernels page2018-06-15T11:40:02ZJeremy Soller[Book] Missing words on Microkernels page*Created by: aidylewis*
On the [Microkernels page](https://doc.redox-os.org/book/design/kernel/microkernels.html#Microkernels) we currently have:
"""
Redox's kernel is a microkernel. Microkernels stands out in their design by providing...*Created by: aidylewis*
On the [Microkernels page](https://doc.redox-os.org/book/design/kernel/microkernels.html#Microkernels) we currently have:
"""
Redox's kernel is a microkernel. Microkernels stands out in their design by providing minimal abstractions in kernel-space. Microkernels have an emphasis on user space, unlike Monolithic kernels which have an emphasis on .
"""
Do we need to add 'kernel space' at the end of the last sentence?
https://gitlab.redox-os.org/redox-os/redox/-/issues/654Race conditions in the kernel2018-06-15T11:40:02ZJeremy SollerRace conditions in the kernel*Created by: ticki*
**Reproduction**: A severe overuse of UnsafeCell results in serious data races.
**Expected behavior**: Use some form of sync primitive, e.g. Mutex.
**Actual behavior**: No form of syncronization primitive.
**Block...*Created by: ticki*
**Reproduction**: A severe overuse of UnsafeCell results in serious data races.
**Expected behavior**: Use some form of sync primitive, e.g. Mutex.
**Actual behavior**: No form of syncronization primitive.
**Blocking/related**: Related to #652.
**Misc**: I am working on a patch for many of these cases.
https://gitlab.redox-os.org/redox-os/redox/-/issues/632dm-crypt/LUKS support2023-06-13T04:42:45ZJeremy Sollerdm-crypt/LUKS support*Created by: solenoids*
As someone using disk encryption, this would be a nice feature to see in the redox kernel in the future. LUKS and dm-crypt is a good established standard for doing this and shouldn't be too hard to implement sinc...*Created by: solenoids*
As someone using disk encryption, this would be a nice feature to see in the redox kernel in the future. LUKS and dm-crypt is a good established standard for doing this and shouldn't be too hard to implement since it sits below the filesystem and directly maps the encrypted volume to a virtual device.https://gitlab.redox-os.org/redox-os/redox/-/issues/631[help wanted] Build error2018-06-15T11:40:02ZJeremy Soller[help wanted] Build error*Created by: SunyDays*
**Reproduction**: make all ([compile-help](https://github.com/redox-os/redox#compile-help) didn't help)
**Expected behavior**: compilation finished without errors
**Actual behavior**: following error:
`RUST_BACK...*Created by: SunyDays*
**Reproduction**: make all ([compile-help](https://github.com/redox-os/redox#compile-help) didn't help)
**Expected behavior**: compilation finished without errors
**Actual behavior**: following error:
`RUST_BACKTRACE=1 rustc --target=x86_64-unknown-redox.json -L build/x86_64-unknown-redox/debug -C no-prepopulate-passes -C no-stack-check -C opt-level=2 -Z no-landing-pads -A dead_code -o build/x86_64-unknown-redox/debug/libcore.rlib rust/src/libcore/lib.rs`
`multirust: no default toolchain configured`
`Makefile:427: recipe for target 'build/x86_64-unknown-redox/debug/libcore.rlib' failed`
`make: *** [build/x86_64-unknown-redox/debug/libcore.rlib] Error 1`
**Build information**:
`$ multirust show-override`
`rustc 1.10.0-nightly (8da2bcac5 2016-04-28)`
`cargo 0.11.0-nightly (afac7fc 2016-04-27)`
`$ uname -a`
`Linux sunydays 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt25-2 (2016-04-08) x86_64 GNU/Linux`
https://gitlab.redox-os.org/redox-os/redox/-/issues/628[Book] Dead Why MIT link2018-06-15T11:40:02ZJeremy Soller[Book] Dead Why MIT link*Created by: aidylewis*
On the [Why Redox page](https://doc.redox-os.org/book/introduction/why_redox.html), the link to Why MIT is broken (https://doc.redox-os.org/book/why_mit.html). It should be this (https://doc.redox-os.org/book/int...*Created by: aidylewis*
On the [Why Redox page](https://doc.redox-os.org/book/introduction/why_redox.html), the link to Why MIT is broken (https://doc.redox-os.org/book/why_mit.html). It should be this (https://doc.redox-os.org/book/introduction/why_mit.html).
https://gitlab.redox-os.org/redox-os/redox/-/issues/633Mouse disappearance after starting orbital with qemu2018-06-15T11:40:02ZJeremy SollerMouse disappearance after starting orbital with qemu*Created by: Csega*
**Reproduction**: run 'sudo make qemu kvm=no', then start orbital
**Expected behavior**: a working mouse pointer on the screen
**Actual behavior**: the mouse pointer disappears, and sodium starts, when I move the m...*Created by: Csega*
**Reproduction**: run 'sudo make qemu kvm=no', then start orbital
**Expected behavior**: a working mouse pointer on the screen
**Actual behavior**: the mouse pointer disappears, and sodium starts, when I move the mouse or click (anywhere).
**Build information**: rustc 1.10.0-nightly (8da2bcac5 2016-04-28), d0d84010c9f5bd9f56dbb3dbb6f5b67c6404f39c, qemu-i386 version 2.0.0 (Debian 2.0.0+dfsg-2ubuntu1.22), Copyright (c) 2003-2008 Fabrice Bellard, Linux eOS 3.19.0-58-generic #64~14.04.1-Ubuntu SMP Fri Mar 18 19:05:43 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
**Blocking/related**: [issues or PRs blocking or being related to this issue.]
**Misc**: [optional: for other relevant information that should be known or cannot be described in the other fields.]
---
_If the above does not fit the nature of the issue feel free to modify it._
https://gitlab.redox-os.org/redox-os/redox/-/issues/649Chat Server not loading properly.2018-06-15T11:40:02ZJeremy SollerChat Server not loading properly.*Created by: stratact*
@ticki is there something lagging the Mattermost server? I'm not able to get to the login prompt.
*Created by: stratact*
@ticki is there something lagging the Mattermost server? I'm not able to get to the login prompt.
https://gitlab.redox-os.org/redox-os/redox/-/issues/620Build Fails (Manjaro)2018-06-15T11:40:02ZJeremy SollerBuild Fails (Manjaro)*Created by: BunnyApocalypse*
**Reproduction**: [describe how you are able to reproduce ("trigger") this bug/issue.]
I attempted to install rust using the auto install script.
**Expected behavior**: [describe the behavior you would e...*Created by: BunnyApocalypse*
**Reproduction**: [describe how you are able to reproduce ("trigger") this bug/issue.]
I attempted to install rust using the auto install script.
**Expected behavior**: [describe the behavior you would expect the repro to yield.]
It installs properly
**Actual behavior**: [describe the actual behavior, which is presented through the repro.].
At the end of the install script it returns this before telling me to make make all etc it gives me this error
`
Travis reports that the last build *FAILED* :(
Might want to check out the issues before building
`
Then, when i do cd into the redox directory and make all it returns
```
mkdir -p build/i386-unknown-redox/debug
RUST_BACKTRACE=1 rustc --target=i386-unknown-redox.json -L build/i386-unknown-redox/debug -C no-prepopulate-passes -C no-stack-check -C opt-level=2 -Z no-landing-pads -A dead_code -o build/i386-unknown-redox/debug/libcore.rlib rust/src/libcore/lib.rs
error: internal compiler error: unexpected panic
note: the compiler unexpectedly panicked. this is a bug.
note: we would appreciate a bug report: https://github.com/rust-lang/rust/blob/master/CONTRIBUTING.md#bug-reports
note: run with RUST_BACKTRACE=1 for a backtrace
thread 'rustc' panicked at 'Field data-layout in target specification is required', ../src/librustc_back/target/mod.rs:370
stack backtrace:
1: 0x7f162121a9f0 - std::sys::backtrace::tracing::imp::write::h9fb600083204ae7f
2: 0x7f162122811b - std::panicking::default_hook::_$u7b$$u7b$closure$u7d$$u7d$::hca543c34f11229ac
3: 0x7f1621227cbc - std::panicking::default_hook::hc2c969e7453d080c
4: 0x7f16211eccaf - std::sys_common::unwind::begin_unwind_inner::h30e12d15ce2b2e25
5: 0x7f16211eed98 - std::sys_common::unwind::begin_unwind_fmt::hb2de8a9968d38523
6: 0x7f161d2800ca - rustc_back::target::Target::from_json::h0865f3d0efe9d5a8
7: 0x7f161d2822bf - rustc_back::target::Target::search::load_file::h10b754eb1c29e7bb
8: 0x7f161d2816ba - rustc_back::target::Target::search::h5d24d442a2ed9dcf
9: 0x7f161db7c471 - rustc::session::config::build_target_config::h59bc6d485b6e9271
10: 0x7f161db7a6bd - rustc::session::build_session_::h6f9ae75b9cc92e18
11: 0x7f161db79631 - rustc::session::build_session::h01e19ac98308258a
12: 0x7f162172af77 - rustc_driver::run_compiler::h8902aebf8b1849a8
13: 0x7f1621728851 - std::sys_common::unwind::try::try_fn::h4c74456035d0fcc7
14: 0x7f16212181cb - __rust_try
15: 0x7f162121815d - std::sys_common::unwind::inner_try::h47a4d9cd4a369dcd
16: 0x7f162172909a - _<F as std..boxed..FnBox<A>>::call_box::h27f542a39f1d61ef
17: 0x7f16212262b4 - std::sys::thread::Thread::new::thread_start::h6f266e069bf4ec2b
18: 0x7f1619043423 - start_thread
19: 0x7f1620e84cbc - clone
20: 0x0 - <unknown>
Makefile:424: recipe for target 'build/i386-unknown-redox/debug/libcore.rlib' failed
make: *** [build/i386-unknown-redox/debug/libcore.rlib] Error 101
**Build information**: [output of `rustc -V`, `git rev-parse HEAD`, `qemu-i386 -version`, `uname -a`, etc.]
```
`
[christopher@christopher-Manjaro redox]$ rustc -V
rustc 1.10.0-nightly (a0c325980 2016-04-20)
`
`
[christopher@christopher-Manjaro redox]$ git rev-parse HEAD
f1faf592be62eaa6a48e905e50a0a5ea6daf157b
`
`
[christopher@christopher-Manjaro ~]$ qemu-i386 -version
qemu-i386 version 2.5.0, Copyright (c) 2003-2008 Fabrice Bellard
`
`
[christopher@christopher-Manjaro ~]$ uname -a
Linux christopher-Manjaro 4.4.6-1-MANJARO #1 SMP PREEMPT Sat Mar 19 06:00:37 CET 2016 x86_64 GNU/Linux
`
**Blocking/related**: [issues or PRs blocking or being related to this issue.]
**Misc**: [optional: for other relevant information that should be known or cannot be described in the other fields.]
---
_If the above does not fit the nature of the issue feel free to modify it._
https://gitlab.redox-os.org/redox-os/redox/-/issues/624Run Redox on OS X failing.2018-06-15T11:40:02ZJeremy SollerRun Redox on OS X failing.*Created by: Viknet*
**Reproduction**:
Build Redox with `make clean && make all`
Try to run `make qemu kvm=no`
**Expected behavior**:
Launching to desktop.
**Actual behavior**:
`init: failed to execute 'init': No such file or director...*Created by: Viknet*
**Reproduction**:
Build Redox with `make clean && make all`
Try to run `make qemu kvm=no`
**Expected behavior**:
Launching to desktop.
**Actual behavior**:
`init: failed to execute 'init': No such file or directory (os error 2)`
**Build information**:
```
git rev-parse HEAD
f59e32aaed3fba1edc8d8eee14e751515c57ebad
```
```
uname -a
Darwin Viktors-MBP 15.4.0 Darwin Kernel Version 15.4.0: Fri Feb 26 22:08:05 PST 2016; root:xnu-3248.40.184~3/RELEASE_X86_64 x86_64
```
**Misc**:
Probably error in running scripts (nonstandard "cp" flags on OS X works differently):
```
redoxfs: opened filesystem build/i386-unknown-redox/debug/filesystem.bin
cp -rL filesystem/* build/i386-unknown-redox/debug/filesystem/
cp: the -H, -L, and -P options may not be specified with the -r option.
make: [build/i386-unknown-redox/debug/filesystem.bin] Error 1 (ignored)
```