package-helpers issueshttps://gitlab.trisquel.org/trisquel/package-helpers/-/issues2024-03-17T00:53:54Zhttps://gitlab.trisquel.org/trisquel/package-helpers/-/issues/151Trying to add a user with mate-user-admin may fail due to invalid username2024-03-17T00:53:54ZprosperoTrying to add a user with mate-user-admin may fail due to invalid usernameWhen adding a user, mate-user-admin assumes that `useradd` will be called and checks the username string based on what `useradd` accepts. But then `adduser` is called and the username may still be rejected due to the stricter NAME_REGEX ...When adding a user, mate-user-admin assumes that `useradd` will be called and checks the username string based on what `useradd` accepts. But then `adduser` is called and the username may still be rejected due to the stricter NAME_REGEX in /etc/adduser.conf, triggering this error message: `running '/usr/sbin/adduser' failed: Child process exited with code 1`.
It looks like `accountsservice` was patched by Debian to use `adduser` instead of `useradd`:
https://sources.debian.org/patches/accountsservice/22.08.8-6/0002-create-and-manage-groups-like-on-a-debian-system.patch
* Screenshot: https://trisquel.info/files/Screenshot%20at%202024-03-02%2012-25-34.png
* Upstream report: https://github.com/zhuyaliang/user-admin/issues/62
* Debian bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065773https://gitlab.trisquel.org/trisquel/package-helpers/-/issues/152Caja readability issue on selected elements of inactive panel at list view2024-03-21T18:03:22ZIgnacio AgullóCaja readability issue on selected elements of inactive panel at list view### Affected revisions/versions
* greybird-gtk-theme - 3.23.1-0ubuntu1+11.0trisquel11
### Description of the issue.
`Trisquel Dark` theme shows small readability problems as the `Trisquel` theme in Caja:
When using Caja with two panels...### Affected revisions/versions
* greybird-gtk-theme - 3.23.1-0ubuntu1+11.0trisquel11
### Description of the issue.
`Trisquel Dark` theme shows small readability problems as the `Trisquel` theme in Caja:
When using Caja with two panels (F3), the text of the selected elements of the inactive panel is unreadable because of having ink and background both in white color.
### How to trigger
It only happens with the "list" layout, and not with the "icons" nor the "compact" layout:
![selected_elements_inactive_panel](/uploads/bbe68b9f1f76c7efcc83b27a0a0709f9/selected_elements_inactive_panel.png)
![selected_elements_inactive_panel_list](/uploads/873f22c70cddfc51ac548a020994e4e8/selected_elements_inactive_panel_list.png)
### Current behavior
Here is how Trisquel and Trisquel Dark currently display list views on active (left) and inactive (right) panels:
![default_list](/uploads/848375a4b55e4d9965d508f0715dc08f/default_list.png)
![Trisquel_Dark](/uploads/f812a6def900fe51e6598d0597d3ef44/Trisquel_Dark.png)
### Workaround
There has been some progress here:
- `#84add6` looks even better as a background color as things stand, it is somewhere between the above two and balances better the constraints from the font colors,
- it appears that I had, in fact, managed to change the font for selected items, but failed to notice a difference, probably for failing to reload the theme properly. So I'll do a diff a test those values one by one.
### Upstream issue
* https://github.com/shimmerproject/Greybird/issues/345Luis GuzmánLuis Guzmánhttps://gitlab.trisquel.org/trisquel/package-helpers/-/issues/150Icedove: depending on font size, message list doesn't go/show the bottom mess...2024-03-14T19:33:06ZAdonay Felipe NogueiraIcedove: depending on font size, message list doesn't go/show the bottom message in both "Compact" and "Default" view densities**Affected revisions/versions**
115.8.1 (package version: 1:115.8.1+build1-0ubuntu0.22.04.1+11.0trisquel21)
**Steps to reproduce**
1. Do one of the following methods:
- From Trisquel's start menu:
1. Trisquel's start menu > Sy...**Affected revisions/versions**
115.8.1 (package version: 1:115.8.1+build1-0ubuntu0.22.04.1+11.0trisquel21)
**Steps to reproduce**
1. Do one of the following methods:
- From Trisquel's start menu:
1. Trisquel's start menu > System > Preferences > Visual and Behavior > Appearance.
2. Fonts tab.
3. Applications font.
4. Change the size to "24".
- Run `mate-appearance-properties` and steps 2 to 4 from the first method.
- From `dconf-editor`:
1. Edit `/org/mate/desktop/interface/font-name`.
2. Change it according to step 4 of the first method.
2. View > Density.
- Select either "Compact" or "Default". ![1](/uploads/1ba57338bd2336cf0dba13a4bfe319f2/1.png)
3. Try to scroll, go to, open/enter or click any message near the bottom, both using mouse and keyboard. The following image was taken after using the End key. ![2](/uploads/9c61825766f3060ee9d9f7140eaefb5c/2.png)
**Current behavior**
- "Compact" view density:
- Any visibility, overflow or scroll is limited to messages not in the bottom. Notice that in the image from step 3, after using the End key, the messages in view are not those from the bottom, the scroll bar shows that there are more messages after the current view, but the bottom message is selected anyways because the dark blue background is not visible.
- Opening/entering messages at the bottom works so long as you use only the keyboard, but you won't see any change in the list due to the item above.
- Using the mouse to click on any message affected by the issue causes the list to scroll upwards to a range which **doesn't have** the selected message, while keeping the selection for further navigation using the keyboard. After step 3, I used the mouse to click on the message with "Pale Moon" subject from image at step 3, which caused the scroll that led to the following image. ![3](/uploads/155547a07494647b35f269e9164bd5a6/3.png)
- "Default" view density:
- Using the End key as seen from step 3 also causes the scroll bar and message list go to an incorrect range before the bottom message, while still selecting that message, just like in "Compact" view density.
- You **can** use the mouse scroll to reach the last message in the list.
- You **can** click on any message in the list in order to select it and the scroll bar and view will only move slightly in order to center the view on the selection, that is, it **won't** jump to a range that doesn't have the selected message.
**Expected behavior**
- Mouse and keyboard should have the same effect, and visibility shouldn't be affected.
**Workaround**
View > Density > Relaxed.
**Other tests**
1. With `/org/mate/desktop/interface/font-name` set to "24" and "Font size" from Icedove's menu set to the maximum (30px), the problem persists.
2. With `/org/mate/desktop/interface/font-name` set to default ("9") and "Font size" from Icedove's menu set to the maximum (30px), the problem **still** persists and also makes other programs, not Icedove, have small text. Besides, due to subnormal sight of this user, anything on a screen with fonts smaller than 24pt in high DPI screens is next to unreadable.
3. With `/org/mate/desktop/interface/font-name` set to default ("9") and "Font size" from Icedove's menu set to 24px, **only the "Compact" view density presents the issue, with a slight change of behavior:**
- You **can** use the mouse scroll to reach the last message in the list.
- You **can** click on any message in the list in order to select it and the scroll bar and view will only move slightly in order to center the view on the selection, that is, it **won't** jump to a range that doesn't have the selected message.
4. Any font size in Icedove > Edit > Settings > General > Fonts & Colors > Advanced is ignored, this is known because in most of the tests so far, the size was set to "24" to places that accept a size in that settings dialog.
5. With `/org/mate/desktop/interface/font-name` set to the default ("9") and "Font size" from Icedove's menu set to the default of 12px, **the issue is not reproducible**.
6. With `/org/mate/desktop/interface/font-name` set to "24" and "Font size" from Icedove's menu set to 24px, **only the "Compact" view density presents the issue, with a slight change of behavior:**
- You **can** use the mouse scroll to reach the last message in the list.
- You **can** click on any message in the list in order to select it and the scroll bar and view will only move slightly in order to center the view on the selection, that is, it **won't** jump to a range that doesn't have the selected message.
7. Assuming that **order matters**, with "Font size" from Icedove's menu set to the maximum (30px) and with `/org/mate/desktop/interface/font-name` set to "24", **in this order**, all the problems still persist.
8. Assuming that **order matters**, with "Font size" from Icedove's menu set to the maximum (30px) and with `/org/mate/desktop/interface/font-name` set to default ("9"), **in this order**, all the problems still persist.
9. Assuming that **order matters**, with "Font size" from Icedove's menu set to 24px and with `/org/mate/desktop/interface/font-name` set to default ("9"), **in this order**, **only the "Compact" view density presents the issue, with a slight change of behavior:**
- You **can** use the mouse scroll to reach the last message in the list.
- You **can** click on any message in the list in order to select it and the scroll bar and view will only move slightly in order to center the view on the selection, that is, it **won't** jump to a range that doesn't have the selected message.
10. With `/org/mate/desktop/interface/font-name` set to "24" and by restarting Icedove (notice that the number next to "Font size" from Icedove's menu changes to 32px), the problem persists.
11. With `/org/mate/desktop/interface/font-name` set to the default ("9") and by restarting Icedove (notice that the number next to "Font size" from Icedove's menu changes to 12px), **the issue is not reproducible**.
12. Assuming that the message panel at the bottom from View > Layout might produce a different behavior, have it enabled, set `/org/mate/desktop/interface/font-name` to "24" and restart Icedove (notice that the number next to "Font size" from Icedove's menu changes to 32px), as a result the problem persists.
13. Assuming that the message panel at the bottom from View > Layout might produce a different behavior, have it enabled, set `/org/mate/desktop/interface/font-name` to its default ("9") and restart Icedove (notice that the number next to "Font size" from Icedove's menu changes to 12px), as a result **the issue is not reproducible**.
**Suggestions for investigation and possible causes**
- The scripts that are run after attribute changes of `tbody[is="tree-view-table-body"]`.
- How Icedove calculates the client height in the overall scroll area vs. the new set of rows that should be displayed.
- Find a way for the calculations from the previous item to take into account the user's choice of font and size.
- This issue might be related to how the DPI settings are applied to the screen that the user has.
- Set the "Relaxed" view density as the default.https://gitlab.trisquel.org/trisquel/package-helpers/-/issues/146Does Trisquel use/backport the CVE-2022-35978 Minetest patch?2024-02-27T16:26:28ZCody ArnoldDoes Trisquel use/backport the CVE-2022-35978 Minetest patch?https://trisquel.info/en/forum/does-trisquel-usebackport-cve-2022-35978-minetest-patch
has a post about this question, and maybe how to backport a patch.
It partly shows
> dpkg-source: info: extracting minetest in minetest-5.4.1+repack...https://trisquel.info/en/forum/does-trisquel-usebackport-cve-2022-35978-minetest-patch
has a post about this question, and maybe how to backport a patch.
It partly shows
> dpkg-source: info: extracting minetest in minetest-5.4.1+repack
dpkg-source: info: unpacking minetest_5.4.1+repack.orig.tar.gz
dpkg-source: info: unpacking minetest_5.4.1+repack-2build1.debian.tar.xz
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: applying kfreebsd-gettext.patch
dpkg-source: info: applying shared_mods.patch
dpkg-source: info: applying rawlua.patch
dpkg-source: info: applying postgresql.patch
dpkg-source: info: applying fix_typos.patch
dpkg-source: info: applying gcc_11.patch
Though just pulling code or binaries from upstream may introduce a vulnerability into Trisquel.
https://trisquel.info/en/forum/glibc-vulnerability-newer-versions
https://gitlab.trisquel.org/trisquel/trisquel-packages/-/issues/28
https://blog.qualys.com/vulnerabilities-threat-research/2024/01/30/qualys-tru-discovers-important-vulnerabilities-in-gnu-c-librarys-syslog
shows in part.
> For the first vulnerability (CVE-2023-6246), a significant security flaw has been identified in the GNU C Library’s __vsyslog_internal() function, affecting syslog() and vsyslog(). This heap-based buffer overflow vulnerability was inadvertently introduced in glibc 2.37 (August 2022) and subsequently backported to glibc 2.36 while addressing a different, less severe vulnerability (CVE-2022-39046). Major Linux distributions like Debian (versions 12 and 13), Ubuntu (23.04 and 23.10), and Fedora (37 to 39) are confirmed to be vulnerable. This flaw allows local privilege escalation, enabling an unprivileged user to gain full root access, as demonstrated in Fedora 38.https://gitlab.trisquel.org/trisquel/package-helpers/-/issues/61openfwwf in aramo build-depends on non-existing package b43-asm2023-09-22T14:38:54ZSimon Josefssonopenfwwf in aramo build-depends on non-existing package b43-asmHi. Where does the openfwwf package in aramo come from? It doesn't come with all sources to rebuild it -- the `b43-asm` package is not in Trisquel.
https://packages.trisquel.org/source/aramo/openfwwf
```
jas@kaka:~$ sudo apt-get buil...Hi. Where does the openfwwf package in aramo come from? It doesn't come with all sources to rebuild it -- the `b43-asm` package is not in Trisquel.
https://packages.trisquel.org/source/aramo/openfwwf
```
jas@kaka:~$ sudo apt-get build-dep openfwwf
Reading package lists... Done
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
builddeps:openfwwf : Depends: b43-asm but it is not installable
E: Unable to correct problems, you have held broken packages.
jas@kaka:~$
```