|
2 years ago Architecture: amd64 Type: Cinnamon Status: Rejected |
FWIW, the Rotation bug is in ubuntu Jammy SRU queue, should get tested and approved sooner-or-later, hopefully in time for Mint21 release.
Sorry for the delay. I found another issue affecting the ISO embedded repository. This affects broadcom compatibility at the very least so I'm trying to get it fixed.
New ISO on the way to remove memtest in EFI and to update blueman to 2.3. We'll address the other issues during BETA.
bookmarks/places issue should be fixed: https://github.com/linuxmint/cinnamon/commit/b7fba516886a984625193b3b273eaef0f74f26fc
The radeon rotation problem is LP bug 1970131 and linked.
Reportedly -- https://gitlab.freedesktop.org/xorg/driver/xf86-video-ati/-/merge_requests/9 fixes this, and after my asking-about, reportedly fix uploaded to Sid which will go into Kinetic automatically.
This may (should?) get an SRU (reportedly might not be for few weeks) to fix this is 22.04.
Finally for now (Maybe these would be considered feature-requests to keep for Mint-21.1):-
(1) 'zram-config' package works nicely, would much prefer if this is installed by default', works absolute treat to reduce actual swapping to disk, almost-always a performance benefit!
(2) Would prefer to see Mozilla collab for Thunderbird same as Firefox, have Thunderbird 102.1 in Mint-21 final-release etc...
@Monsta .... that will create problems for some BIOSes as they won't boot from disks without an active partition on the MBR ... e.g. seen this on Intel boards, D945GCLF etc.
They would then need to do hybird-mbr with 'bootable' partition listed in MBR to work around that... I shall try to test this on an empty hdd.
@enyc: Ubiquity not only uses ESP on legacy, it also uses GPT partitioning scheme on legacy now. The very first partition is "bios_grub" or something - that's what allows booting from GPT drive on legacy. Also ESP is actually filled with EFI stuff now (I think /boot/efi was empty in 20.x installations on legacy).
I don't know why Ubuntu guys did it, maybe it's for booting on UEFI system with legacy mode on and off...
I guess this will be left in Mint 21 as is, so we'll have to live with it.
r.e. rotation regression: Can confirm machine runs PCMemtest fine,
mint 20.3 with kernel 5.15 is fine
mint21-test installed fully updated is not fine (same Xorg crash when try to rotate DVI-0)
pop-os 22.04 latest boot image has the same issue, same Xorg crash when try to rotate second display. (i.e. this is not mint-specific issue).
@clem
Solution for you r.e. memtest86+ !! -- Install package "pcmemtest" instead -- this is a FOSS fork that works for me on installed mint21-system and also supports UEFI as I understand-it. Would highly reccomend that as fix for memtest in install-image.
installation of mint-21-cinnamon in UK, even with network connected, immediately asks for "install the language packs" i.e. "openoffice.org-hyphenation", which seems rather needless to me, packages.ubuntu.com confirms this is a "dummy transitional package" ..., I think mintreport needs updating to not report this any more, or report the actual hyphen- packages relating to language in use, at least.
On a Non-UEFI system (older AMD64 bios) here, with existing Mint20.3 (only) on hard disk, which has that Fat partition mounted in /boot/efi (A known quirk in 20.3 legacy installs)...
Doing the automated dual-boot installation with Mint-21 results in new system having an ESP (EFI System Partition) i.e. /target/boot/efi while installing.
This dual-boot installation does ''works' on this legacy-only booting-system, however.
Looking at the resultant system seems to have efi and non-efi grub both installed, maybe this is a deliberate decision to make new installations more easily bootable/portable, something I do not disagree with.
I note in particular that creating an ESP (actual 0xEF partition type or GPT equivalent) when it did not exist before can be a problem because the presence of this when not there before affects booting priority on some systems e.g. netbook I have here always boots ESP first no matter what unless you use boot menu key manually every-time.
nvidia prime- works except going from powersave -> on-demand, you need to log out twice(same as previous iso). The other issue, on-demand missing from the tray applet, is fixed in git.
Commenting on the places: Noticed on a USB live boot only "Home", "Desktop" and "Connect to..." are shown. After a fresh install, the same thing. After a reboot all the /home/user places showed up. Went back and booted the LM 20.3 ISO in a live session, this was not the case. Everything showed up on the live boot session. Must be a small difference some where.
Regarding Places menu order: after rebooting the system the menu is now in the right order.
Don't know what happened. It's is a fresh install with home directory encryption. I have not applied updates yet. This is the 2nd time logging in on the new install.
The Places menu seems to be in reverse order from how it was on 20.3, and also in reverse order from how it is in Nemo. Just me or anybody else have the same?
When running from live session (where updates are not so relevant), update mirrors to mirrorservice.org and then when refresh get:-
E:The repository 'cdrom://Linux Mint 21 _Vanessa_ - Release amd64 20220707 jammy Release' does not have a Release file.
I don't remember this on previous releases so thought I should mention.
Noticing weird segfaults in dmesg :-
[ 36.377946] usbcore: registered new interface driver snd-usb-audio
[ 37.088045] gutenprint53+us[1440]: segfault at 38 ip 00007fc065507f74 sp 00007ffd54300868 error 4 in libc.so.6[7fc065498000+195000]
[ 37.088064] Code: 14 00 e8 ff 1e fa ff 48 8d 0d e8 98 14 00 ba 53 02 00 00 48 8d 35 2a 16 14 00 48 8d 3d 4e 16 14 00 e8 e0 1e fa ff f3 0f 1e fa <8b> 47 10 89 c2 81 e2 7f 01 00 00 90 83 e0 7c 0f 85 a7 00 00 00 53
[ 37.188411] usblp0: removed
[ 36.377946] usbcore: registered new interface driver snd-usb-audio
[ 37.088045] gutenprint53+us[1440]: segfault at 38 ip 00007fc065507f74 sp 00007ffd54300868 error 4 in libc.so.6[7fc065498000+195000]
[ 37.088064] Code: 14 00 e8 ff 1e fa ff 48 8d 0d e8 98 14 00 ba 53 02 00 00 48 8d 35 2a 16 14 00 48 8d 3d 4e 16 14 00 e8 e0 1e fa ff f3 0f 1e fa <8b> 47 10 89 c2 81 e2 7f 01 00 00 90 83 e0 7c 0f 85 a7 00 00 00 53
[ 37.188411] usblp0: removed
This (appears) to be harmless, Printing to Hp1320n network printer works, and printer-driver-dymo installable etc...
The segfaults repeat in dmesg ...
On that note, I will memtest the system but it works solidly fine under mint 20.3 ....
Regression to Mint 20.3 on older AMD64 Desktop with 02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series]
Trying to rotate second screen using xrandr or cinnamon GUI tools results on Xorg crash:-
[ 338.488] (EE) Backtrace:
[ 338.488] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x55c6d5ab02b9]
[ 338.489] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) [0x7f774245c520]
[ 338.490] (EE) 2: ? (?+0x0) [0x0]
[ 338.491] (EE) 3: ? (?+0x0) [0x0]
[ 338.491] (EE)
[ 338.491] (EE) Segmentation fault at address 0x0
[ 338.491] (EE)
Fatal server error:
[ 338.491] (EE) Caught signal 11 (Segmentation fault). Server aborting
May of course not be mint-specific but I notice this now.... Happy to try new kernel on the mint 20.3 to compare with, etc.
+Acheron
Yes. memtest only works in Legacy/BIOS booting, not UEFI booting, which was what I was expecting, similar to mint 20.3.
I think it should not be included in the UEFI grub menu.
This can be reviewed when new FOSS Memtest86+ is released, etc.
Does anyone else have an issue with Memtest hanging instead of loading to the initial menu? When the GRUB boot item "Test memory" is selected the system just sits there and nothing happens. Ctrl+alt+del won't break out of it. Have to power off. I know Memtest86 loads since I just tested version 9.4 on a USB memory stick boot and it loads to the initial menu. Could someone else please confirm?
Fixed:
- /etc/upstream-release/lsb-release
- cinnamon control center menu items
- memtest comes back
- codecs don't install properly in ubiquity
- live repo doesn't exist