R0bur
Crew Member
Posts: 186
Likes: 128
|
Post by R0bur on Jun 11, 2023 18:11:15 GMT
Hi there. I get an error saying that the image is not signed when booting from the usb flash drive. I used rufus with DD. Any ideas? Maybe the UEFI Secure Boot is enabled in the settings of your computer. Try to disable it. |
|
|
|
Post by alfredo on Jun 13, 2023 19:39:37 GMT
I'm unable to deactivate the secure boot for some reason.. smh. I guess I'll wait for the final version.
I believe the kernel should receive updated. Maybe we can use one that has a long term support?
Thx
|
|
oscarb75
Crew Member
Posts: 80
Likes: 93
|
Post by oscarb75 on Jun 17, 2023 10:10:23 GMT
On some Laptop, you have to set a BIOS Password ( or Supervisor Password, Admin Password... ) to be allowed to deactivate Secure Boot. It works like that on the "recent" Acer Laptops, for example.
|
|
oscarb75
Crew Member
Posts: 80
Likes: 93
|
Post by oscarb75 on Jun 22, 2023 14:50:26 GMT
I´m using Bodhi 7.0b for a test server.
Installed on a Thinkpad T400 ( Core2Duo - 4gb Ram ) and it works very good, so far.
There is no task manager out of the box. Is it intentional?
Anyway, I´ve used top and installed htop.
|
|
|
|
Post by ylee on Jun 22, 2023 15:19:20 GMT
I´m using Bodhi 7.0b for a test server. Installed on a Thinkpad T400 ( Core2Duo - 4gb Ram ) and it works very good, so far. There is no task manager out of the box. Is it intentional? Anyway, I´ve used top and installed htop. A task manager in the sense you mean either GUI or CLI is usually not installed by default on Bodhi. So yes it is intentional. You can use the ps command and kill or killall. Or you can install a taskmanger. Htop is great for a cli app. Lots of options here. |
|
|
|
Post by ylee on Jun 22, 2023 19:36:05 GMT
I haven't ignored your post above enigma9o7. Trust me Štefan and I talked about a lot of it in Discord over the last few weeks ... The following are observations and suggestions from my experience two weeks testing Bodhi 7 beta hwe in virtualbox. 1. Web Browser Manager suggestions
1a. Have web manager add/remove mozillateam ppa with Firefox (and thus remove it from Bodhi's default sources)
1b. Add epiphany-browser (from ubuntu repo) I want Firefox on the appcenter and that install link to work there. Therefore I have to keep the mozillateam ppa. On other Web Browser suggestions, adding more browsers is not a bad idea but for now it is on hold. I want scroll bars in that app and without them, the app is too large in the default resolution on a VirtualBox VM. Development on that app is on hold at least for me until I get thru this release cycle. More urgently needed is localization. All in time. 2. Suggestion: Remove nvidia-legacy ppa from default sources (see previous post; security issues, not that there's anything wrong with it)
I am leaving it in the sources But I am making it possible to uninstall just the nvidia-legacy ppa asa package. It was included in bodhi-settings now it is a separate package. sudo apt remove nvidia-ppaApt does not like removing things in /etc so after the purge if anything is left in /etc/apt/ you can manually remove it. 3. Terminology
3a. Default background isnt bodhi.png although it is available. 3b. BUG: With picom running, if background is set, transparency doesn't work when terminology launched. (it will work if adjusted/enabled while already loaded). This is regression, used to work fine. The bodhi default background was removed from terminologies configuration when terminology in git had issues displaying it. It did not display it. At some point latter Raster fixed that issue. I have added it back, should work on the next ISOs. I do not maintain terminology so any issues or bugs with it need reported to the e-devs. 4. Google Chrome isn't themed like chromium - needed to be set to gtk and uncheck system titlebar. Not that important, but if easy to do in skel, why not.... I am not gonna mess with that. Really several of the browsers installed by Web Browser Manager need some tweaks to get the best look on Bodhi. If I tweak one in bodhi-skel it sorta forces me to at least want to them all ... Probably this sorta info would be best in a wiki article or forum tutorial. At least for now. 5. Intermittent Moksha Bugs 5a. Tasks sometimes scroll left/right a little bit even when set to shrink-to-fit. 5b. Sometimes green dot on terminology ibar even when it's not open. 6. Suggest Disable Phased Updates, let real ubuntu users deal with this confusion, as mentioned in alpha thread.
APT::Get::Always-Include-Phased-Updates "1"; 7. MokshaGreen Theme 7a. CPU % gadget still difficult to read. ideas: get rid of % symbol or put it underneath the value, and/or make font brighter or thicker or bold or something. 7b. network monitor gadget has white text, not green. (I don't use this normally, just observed while testing all modules). 7c. inconsistent behavior: sometimes using small shelf icon size results in unusable space at far right end of shelf. may depend on which gadgets installed? 8. Useless Places Warnings: 8a. /dev/sr0 is 100% full (This is a CD image, I don't need a warning!)
8b. 98% of my 5tb drive still has over 100GB free. Perhaps allow us to specify GB instead of percent? Theme module and moksha bugs I think Štefan took it upon himself to address. Ubuntu's phased updates have nothing to do with moksha, but it is a bad idea to disable that for all users: These packages are not as "stable" as regular Ubuntu packages. I go ahead and install them myself but I have the troubleshooting experience. The mythological average user does not. 9. Picom
9a. compton-conf (in ubu repo) does not seem compatible with picom, default config crashes picom. Perhaps block install? 9bi. suggestion: package picom-conf and make it a recommend of moksha-module-compton 9bii. copy /etc/compton.conf to ~/.config/picom.conf and remove the deprecated refresh-rate option, maybe as skel file if thats the only way to get it local? (the gui only sees the .config/picom.conf even tho picom still loads the /etc/compton.conf so gui shows inaccurate values the way bodhi is currently configured) At some point soonish I will repackage picom as well as look at packaging picom-conf. 10. Third Party App Issues with Moksha Window Manager10a. my weather-indicator is supposed to pin to desktop, but instead its drawing a border and floating around, and I can't find any Moksha setting to fix it. 10b. nheko verification window is too narrow and difficult to open.
This only happens if you already have an encrypted matrix account, then try to login to it from nheko; it pops up a window to verify from, but it is like 1 pixel wide and VERY difficult to click on to make it big. I mentioned to nheko dev and he said it's a window manager issue. Same thing happens on old version, ubu repo version, debian sid version, flatpak version.... I haven't look at this maybe Štefan has. I remember him talking about it in Discord. Need to reread this entire thread anyway and see if there are any suggestions or issues I missed or forgot. |
|
|
|
Post by thewaiter on Jun 23, 2023 5:56:54 GMT
I continuously announced my work on this post. All stuff related to my work been checked. From what I can see on the last post:
Tasks shrink bug fixed (Moksha)
Places full disk warning for CD ROM fixed (Moksha)
CPU % char fixed (An extra module which needs to be packaged and added to the repo)
Some stuff left as it is because it does not make sense or I can not reproduce here (iBar dot on not running Terminology). We will wait for last official BL7 release and its feedback. If some serious bugs still remain, we will solve them.
Stefan
|
|
jns55
Member
Posts: 12
Likes: 1
|
Post by jns55 on Jun 23, 2023 10:42:14 GMT
Good morning,
Problem entering wifi code:
Nothing is displayed in the input window until the 8th character of the key has been typed. It's embarrassing because it doesn't seem to work.
Bodhi linux 7.0 beta on live usb.
|
|
jns55
Member
Posts: 12
Likes: 1
|
Post by jns55 on Jun 23, 2023 11:16:28 GMT
|
|
jns55
Member
Posts: 12
Likes: 1
|
Post by jns55 on Jun 23, 2023 11:32:35 GMT
Finally ignoring the error message, the installation succeeds and the pc restarts on Bodhi.
After the difficulty in entering the wifi code, such an error message is enough to scare a newcomer to linux and encourage him to look elsewhere.
Such behavior is really confusing.
|
|
|
|
Post by thewaiter on Jun 23, 2023 15:23:59 GMT
Yea, I can confirm no asterisks while typing Wifi password. After a while I found it is a GTK theme issue. Let me fix it and thx for feedback...
Stefan
EDIT: fixed, commited
|
|
|
|
Post by ylee on Jun 23, 2023 19:52:56 GMT
I have never ran into that or saw that warning message, but for the record we use Ubiquity, Ubuntu's installer. Bodhi does not maintain that program. Not much I am willing to do about its various bugs and quirks. |
|
|
|
Post by escuelaslinux on Jun 23, 2023 20:47:31 GMT
I have never ran into that or saw that warning message, but for the record we use Ubiquity, Ubuntu's installer. Bodhi does not maintain that program. Not much I am willing to do about its various bugs and quirks.
We actually ran into that issue when doing early tests for Escuelas Linux 8.0 (our first version based on the upcoming Bodhi 7), which was one reason that prompted us to switch to the Calamares installer. By doing so, possibly another issue was also solved, as when installing Escuelas Linux, it does detect other OSes and adds them to the GRUB menu without even having to add GRUB_DISABLE_OS_PROBER=false (although we’re not quite sure if Calamares is the app responsible for that feat, as an installed Escuelas Linux system is still able to do all that when running update-grub).
However, switching to Calamares may not be a good idea for Bodhi. It was easy in Escuelas Linux as we include many KDE and Qt apps, so we already had almost all the libraries and dependencies that Calamares requires.
Adding Calamares to Bodhi would mean a distro bloated with KDE/Qt stuff merely to be able to run the installer!
|
|
enigma9o7
Crew Member
Posts: 1,502 
Likes: 1,381
|
Post by enigma9o7 on Jun 23, 2023 23:13:00 GMT
I'm pretty sure I saw that message about no uefi partition when I installed 7 alpha on my athlon. Since it is an old machine without UEFI I just clicked continue. But don't quote me on it, maybe it was somewhere else I saw that message, but I've definitely seen it and just continued fine.
|
|
|
|
Post by ylee on Jun 23, 2023 23:46:37 GMT
Ubuntu will be using a new installer in the future and development on Ubiquity will probably slow down if not stop. So when all that comes to pass our choices are to either fork Ubiquity and continue development on it or switch to another installer. Unless someone else forks Ubiquity. I have read through the reported issues on Ubiquity and as a result, I have no desire to take on maintaining yet another application and package. Calamares seems to be the only other widely used GUI installer suitable for use in a Debian/Ubuntu Distro. I am just not ready to switch at this point. For the record Calamares seems to be a Ubiquity Qt port anyway, at least it was originally. The code is really similar as far as i can tell. I would have to look and see how much QT bloat it would add to our ISO, but it would add none to the installed system as I would add it and all its unneeded dependencies to the filesystem.manifest-remove file on the ISO. Meaning they would be removed on the installed system.
Since this is a warning that was reported and not an error and the installation was successful, I don't regard this as a real issue. Maybe confusing to Newbies but overall Ubiquity is easy to use and does the job. Covers most user cases.
|
|
