redox-os issueshttps://gitlab.redox-os.org/groups/redox-os/-/issues2023-12-13T18:39:56Zhttps://gitlab.redox-os.org/redox-os/kernel/-/issues/143kernel hang on ls command with pipe2023-12-13T18:39:56ZRon Williamskernel hang on ls command with pipe`ls -C /bin | less` seems to hang the kernel some times. It was seen twice in a row on Orbterm.`ls -C /bin | less` seems to hang the kernel some times. It was seen twice in a row on Orbterm.https://gitlab.redox-os.org/redox-os/syscall/-/issues/34Update `bitflags` to v22023-12-07T15:29:58ZdaxpeddaUpdate `bitflags` to v2As in the title.
See https://github.com/bitflags/bitflags/releases/tag/2.0.0.
This is a breaking change as it modifies the exposed API.As in the title.
See https://github.com/bitflags/bitflags/releases/tag/2.0.0.
This is a breaking change as it modifies the exposed API.https://gitlab.redox-os.org/redox-os/cookbook/-/issues/187Add folders to organize recipes/packages2023-12-01T08:51:28ZRon WilliamsAdd folders to organize recipes/packagesProposed:
1. Add organizing directories for packages. e.g `recipes/core/recipe_name`. Packages will still appear in the config file as only their basename, so `cook` and `installer` will need to search for the recipes.
2. Organizing dire...Proposed:
1. Add organizing directories for packages. e.g `recipes/core/recipe_name`. Packages will still appear in the config file as only their basename, so `cook` and `installer` will need to search for the recipes.
2. Organizing directories are optional. e.g. A package can appear as `recipes/recipe_name` or `recipes/core/recipe_name`. If a directory at the base level contains a `recipe.toml` or `recipe.sh`, it cannot also contain package dirs. This allows for migration.
3. If two packages have the same name but are in different organizing directories, e.g. "lib/libx" and "core/libx", (or if one is directly under `recipes`) a build error will occur when that package name is included in the filesystem config file.
4. [Optional - TBD] A special directory named `wip` or something similar is allowed to contain packages that duplicate names of packages in other directories. The package in `wip` takes priority. The "[source]" section of recipes in this directory is ignored, so the source is not updated if the git repo changes. This allows a developer to work with their own fork/branch without concern that it may get updated from `master`.
This requires changes to `installer` as well as `cookbook`.https://gitlab.redox-os.org/redox-os/event/-/issues/1New version not on crates.io2023-11-18T17:39:58ZRose HudsonNew version not on crates.ioThis crate has not been published to crates.io since the new event system was introduced.This crate has not been published to crates.io since the new event system was introduced.https://gitlab.redox-os.org/redox-os/redox/-/issues/1415Add a "ci.sh" bootstrap script for the CI server2023-11-08T17:24:04ZRibbonAdd a "ci.sh" bootstrap script for the CI serverThe current [bootstrap.sh](https://gitlab.redox-os.org/redox-os/redox/-/blob/master/bootstrap.sh?ref_type=heads) script contains packages to build the Redox base system and recipes on the [demo](https://gitlab.redox-os.org/redox-os/redox...The current [bootstrap.sh](https://gitlab.redox-os.org/redox-os/redox/-/blob/master/bootstrap.sh?ref_type=heads) script contains packages to build the Redox base system and recipes on the [demo](https://gitlab.redox-os.org/redox-os/redox/-/blob/master/config/x86_64/demo.toml?ref_type=heads) Cookbook configuration.
As Redox receive more recipes they require more build tools to be installed on the CI server, but the current script don't accept "non-demo recipes" dependencies.
The solution is to create a specific script to configure the CI server, it will be a reduced version of the `bootstrap.sh` script with:
- The command to install the Ubuntu/Debian packages (to build all recipes from Cookbook)
- The commands to download the Redox build system
- The command to install the Rust toolchain
- The command to enable a source-based toolchain
- The commands to build all Cookbook configurations and recipes
This will reduce the maintenance effort of the CI server, the script name can be `ci.sh`https://gitlab.redox-os.org/redox-os/redox/-/issues/1402(Feature request) Recipe override list2023-11-06T17:47:08ZRibbon(Feature request) Recipe override listBy default the build system change the active Git branch of all recipe sources to `master` (`make rebuild` and `make r.recipe`, even after `make f.recipe`).
This auto-checkout can be time-consuming because you need to manually comment o...By default the build system change the active Git branch of all recipe sources to `master` (`make rebuild` and `make r.recipe`, even after `make f.recipe`).
This auto-checkout can be time-consuming because you need to manually comment out the `[source]` and `git =` fields of each `recipe.toml` to avoid this.
The solution is to create a file called `.overrides` and add the names of the recipes that you want to disable the Git checkout.https://gitlab.redox-os.org/redox-os/redox/-/issues/1401(Feature request) Enable the recipe binary syntax by default2023-11-06T17:45:06ZRibbon(Feature request) Enable the recipe binary syntax by defaultWhen you enable the `REPO_BINARY` environment variable the build system treat the default recipe syntax as binary (`recipe = {}`) that will download packages from the CI server, to treat a recipe as source-based you need to use `recipe =...When you enable the `REPO_BINARY` environment variable the build system treat the default recipe syntax as binary (`recipe = {}`) that will download packages from the CI server, to treat a recipe as source-based you need to use `recipe = "recipe"`.
A switch for the `recipe = {}` syntax is not flexible, it's an annoying behavior if you just want to use a few recipe binaries from the CI server (my case).
The solution is to enable the `recipe = "binary"` syntax by default.https://gitlab.redox-os.org/redox-os/redox/-/issues/1409Replace the Hugo static site generator by a Rust-written alternative2023-11-05T21:30:06ZRibbonReplace the Hugo static site generator by a Rust-written alternativeCurrently our website and book use Hugo to work, Hugo is written in Go, AFAIK its garbage collector would reduce the website/book uptime and probably has more bugs.
## Current Rust candidates:
- [Cobalt](https://cobalt-org.github.io/)
...Currently our website and book use Hugo to work, Hugo is written in Go, AFAIK its garbage collector would reduce the website/book uptime and probably has more bugs.
## Current Rust candidates:
- [Cobalt](https://cobalt-org.github.io/)
- [Shokunin](https://shokunin.one/)
- [Zola](https://www.getzola.org/)
- [Mandy](https://github.com/angeldollface/mandy)https://gitlab.redox-os.org/redox-os/website/-/issues/192(Feature Request) Dark theme by default.2023-11-05T21:27:41ZRibbon(Feature Request) Dark theme by default.It's better for the eyes, less stress to read.It's better for the eyes, less stress to read.https://gitlab.redox-os.org/redox-os/kernel/-/issues/116HPET instability when running with qemu2023-10-30T14:50:46ZWill AngenentHPET instability when running with qemuWhen running the desktop build, compiled under ubuntu linux, with qemu 7.2.0 installed with brew, under MacOS 12.2, intel CPU, I get random crashes like these:
- [1.log](/uploads/4ccde03be543891b7ee62e3479738760/1.log)
- [2.log](/upload...When running the desktop build, compiled under ubuntu linux, with qemu 7.2.0 installed with brew, under MacOS 12.2, intel CPU, I get random crashes like these:
- [1.log](/uploads/4ccde03be543891b7ee62e3479738760/1.log)
- [2.log](/uploads/da0e0a18c88ab05177c7c67f67bef43b/2.log)
- [3.log](/uploads/cd2545ab71fc02b740ba6498a7a62524/3.log)
- [4.log](/uploads/d63827ee4a174c4db5dd79d5816b135e/4.log)
- [5.log](/uploads/fb8eabb94c3c490e4d7d062013e55b87/5.log)
It appears that `period_fs` [here](https://gitlab.redox-os.org/redox-os/kernel/-/blob/master/src/arch/x86_64/time.rs#L19) is becoming zero.
When adding this debug print:
```
// Calculate divisor
if period_fs == 0 {
let capability2 = unsafe { hpet.base_address.read_u64(hpet::CAPABILITY_OFFSET) };
println!(
"hpet={:?} capability={:?} capability2={:?}",
hpet, capability, capability2
);
}
```
I managed to get this output:
```
capability=10164 capability2=42949675116306945
```
By the way:
42949675116306945 translates to 0x9896808086A201.
0x9896808086A201 >> 32 is 0x989680. In decimal, this is 10000000, the clock period.
The contents of hpet struct is the same in good & bad boots.https://gitlab.redox-os.org/redox-os/redox/-/issues/1272Enable authentication with Gitlab2023-10-27T13:53:47ZKelly Thomas KlineEnable authentication with GitlabPlease consider enabling authentication with Gitlab in your Gitlab instance.Please consider enabling authentication with Gitlab in your Gitlab instance.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/1284GUI window freezes when process is killed2023-10-27T13:47:26ZBenjaminRiGUI window freezes when process is killed**Reproduction:**
- Boot the Redox 0.5.0 harddrive.bin
- Choose any resolution (1280x1024@32 will do)
- Log in as `user`
- Start a terminal inside the GUI
- Start a calculator
- Run `ps` in the terminal, find calculator PID (e.g. `53` in...**Reproduction:**
- Boot the Redox 0.5.0 harddrive.bin
- Choose any resolution (1280x1024@32 will do)
- Log in as `user`
- Start a terminal inside the GUI
- Start a calculator
- Run `ps` in the terminal, find calculator PID (e.g. `53` in my case)
- Run `kill 9 53`
- The calculator process (PID `53`) is now gone if we run `ps` again
- However, the window is still on the desktop, it can be moved but its contents are frozen and it cannot be closed
- The same problem can be reproduced with file manager and character map (and potentially more if not all GUI applications)
- The problem can also be reproduced with signal `15`, `SIGTERM`
**Expected behavior:**
- After a successful `kill` invocation, the Window that belongs to the process is closed and its resources are freedhttps://gitlab.redox-os.org/redox-os/redox/-/issues/1228Avoid kernel rebuild on directory timestamp change2023-10-27T13:39:07ZDato SimóAvoid kernel rebuild on directory timestamp changeHi—
In mk/kernel.mk, a long list of wildcards is given as dependencies for libkernel:
```
build/libkernel.a: kernel/Cargo.lock kernel/Cargo.toml kernel/src/* kernel/src/*/* kernel/src/*/*/* kernel/src/*/*/*/* build/initfs.tag
```
The ...Hi—
In mk/kernel.mk, a long list of wildcards is given as dependencies for libkernel:
```
build/libkernel.a: kernel/Cargo.lock kernel/Cargo.toml kernel/src/* kernel/src/*/* kernel/src/*/*/* kernel/src/*/*/*/* build/initfs.tag
```
The only problem I encountered is that, when expanded, they will include the (sub-)directories themselves; this means that, for example, opening a file with Vim (without editing it) will trigger a rebuild of the kernel. (Because Vim opens a .swp file in the file's directory, thus altering its mtime.)
This should be easily fixable by wildcarding on `*.rs` instead of `*`, since there seem to be no other file extensions in the tree. I can send a PR if you'd like.
Thanks for considering.https://gitlab.redox-os.org/redox-os/redox/-/issues/1343Redox Build fails in Ubuntu 21.042023-10-27T13:33:19ZkarachikoraiRedox Build fails in Ubuntu 21.04<!-- If you have built Redox OS yourself, please provide the following information: -->
- Operating system:
Ubuntu 21.04
- `uname -a`:
`Linux ubuntu 5.11.0-18-generic #19-Ubuntu SMP Fri May 7 14:22:03 UTC 2021 x86_64 x86_64 x86_64 GNU/L...<!-- If you have built Redox OS yourself, please provide the following information: -->
- Operating system:
Ubuntu 21.04
- `uname -a`:
`Linux ubuntu 5.11.0-18-generic #19-Ubuntu SMP Fri May 7 14:22:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux`
- `rustc -V`: rustc 1.47.0-nightly (6c8927b0c 2020-07-26)
- `git rev-parse HEAD`:
901108353f2427809f98e29d8e4165d432bbd715
Hello Team,
I am trying to build a React OS in Ubuntu 21.04. While running make all, I am getting the below error.
xz-5.2.5/windows/vs2019/liblzma.vcxproj
xz-5.2.5/windows/vs2019/liblzma_dll.vcxproj
xz-5.2.5/windows/vs2019/xz_win.sln
+ ./autogen.sh
+ autopoint -f
./autogen.sh: 15: autopoint: not found
cook - xz - error: failed to fetch: failed to run "bash" "-ex": exited with status exit code: 127
./repo.sh failed.make: *** [mk/filesystem.mk:18: build/filesystem.bin] Error 1
Could you please let me know what i am missing?
Thankshttps://gitlab.redox-os.org/redox-os/redox/-/issues/2Re-organize to make use of rustdoc2023-10-25T17:39:40ZJeremy SollerRe-organize to make use of rustdochttps://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/redox/-/issues/1403Problem compiling either native or with podman2023-10-18T18:17:40ZCoderdreams IncProblem compiling either native or with podman* [x] I agree that I have searched opened and closed issues to prevent duplicates.
---
## Description
I'm getting this error:
**Compiling** redox-exec v0.1.0 (/mnt/redox/relibc/src/platform/redox/redox-exec) \
**error\[E0432\]: unr...* [x] I agree that I have searched opened and closed issues to prevent duplicates.
---
## Description
I'm getting this error:
**Compiling** redox-exec v0.1.0 (/mnt/redox/relibc/src/platform/redox/redox-exec) \
**error\[E0432\]: unresolved imports \`syscall::GrantDesc\`, \`syscall::GrantFlags\`** \
**\--\>** src/platform/redox/redox-exec/src/lib.rs:27:5 \
**|** \
**27** **|** GrantDesc, GrantFlags, PROT_READ, PROT_EXEC, MAP_SHARED, MAP_FIXED_NOREPLACE, \
**|** **^^^^^^^^^** **^^^^^^^^^^** \
**|** **|** **|** \
**|** **|** **no \`GrantFlags\` in the root** \
**|** **|** **help: a similar name exists in the module: \`EventFlags\`** \
**|** **no \`GrantDesc\` in the root** \
\
**For more information about this error, try \`rustc --explain E0432\`.** \
**error:** could not compile \`redox-exec\` (lib) due to previous error
## Environment info
- Redox OS Release: master branch
- Operating system: Manjaro 23.0.3
- `uname -a`: Linux tetsuo-ms7b84 6.4.16-5-MANJARO #1 SMP PREEMPT_DYNAMIC Thu Sep 28 10:59:52 UTC 2023 x86_64 GNU/Linux
- `rustc -V`: rustc 1.75.0-nightly (cae0791da 2023-10-05)
- `git rev-parse HEAD`: a55f8bfab0c049114d4aaa160be8407e949b948f
## Steps to reproduce
1. run: make all
2.
##https://gitlab.redox-os.org/redox-os/coreutils/-/issues/187cp and mv always report "No destination found."2023-10-15T18:24:54ZJeremy Sollercp and mv always report "No destination found."*Created by: sajattack**Created by: sajattack*