Re: [Trisquel-users] Trisquel 8 codename "Flidas" Release Candidate is ready for testing
The thing is I wasn't sure if ppa-purge would just remove the exact package while leaving the dependencies alone. That's why I didn't use it. I'm just happy I didn't have to wipe my system for the 20th time. I'm very thankful for being able to access all of this information on the web and getting help from knowledgeable people such as yourself to help me get through this. Thanks very much.
Re: [Trisquel-users] Trisquel 8 codename "Flidas" Release Candidate is ready for testing
I just fixed it. :D In the past I always just shrugged and said, you know what, I'll just do a clean install... However, this time I decided I try to figure this out. It turns out the main issue my upgrade wasn't working was because I had lots of packages that were from non-trisquel repositories. When I installed apps from some repository or ppa, some things the upgrader wasn't expecting were being included. I think in hindsight it may have been the fact I had 3 versions of gcc installed (versions 5, 6 and 7). This is how I fixed everything: 1) Remove all non-trisquel PPAs and repositories from the Software & Updates app. 2) Do the folloiw ing the terminal: $ sudo apt install apt-show-versions $ sudo apt-show-versions | grep 'No available' This shows a list of packages I have installed that aren't from a repository on my system. 3) Purge packages that are on the list using the following command: $ sudo dpkg -P --force-all This command removes the package without removing dependencies, which is what is needed here. 4) I rebooted noticed that I got a notification in my tool bar that many packages were now broken, so I went to Synaptic Package manager and it told me that stuff was too broken so I closed that program and went back to the terminal and typed the following command: $ sudo aptitude -f install Aptitude then suggested a dependency fix which was aggressive but worked. I just hit "Y" to proceed. 5) Then I typed the following commands to make sure thatI didn't remove anything that Trisquel needed: $ sudo apt-get autoremove $ sudo apt-get autoclean $ sudo apt install trisquel I noticed that aptitudes "fix" removed the trisquel package so I installed it again. 6) I rebooted and did one last autoremove, autoclean, update and upgrade. Then typed the following commands to get the upgrade to Trisquel 8 going: $ sudo apt install upgrade-manager $ sudo upgrade-manager -d At this point the GUI upgrader boots and I just went through the prompts saying "Yes" and "OK" to everything. I selected "Restart" at the end of the upgrade and I computer booted just fine! I think this technique could help a lot of people who are having issues upgrading.
Re: [Trisquel-users] Trisquel 8 codename "Flidas" Release Candidate is ready for testing
Yes it does! However apt is broken and even using wget to install packages that may be missing doesn't acknowledge the pkg files as being installable. :/
Re: [Trisquel-users] Trisquel 8 codename "Flidas" Release Candidate is ready for testing
Magic Banana, after rebooting the system shows a black screen and won't allow me to login at all :/
Re: [Trisquel-users] Trisquel 8 codename "Flidas" Release Candidate is ready for testing
Thanks Magic. I appreciate your response. Booting back in works fine. But I feel like some things may be semi-broken if the installer says it could not complete... I will update this thread with pictures of the behavior I find post reboot. === OTHER SEMI-RELATED ISSUE === By the way, on my other Trisquel laptop, a Macbook Pro 17inch from mid-2010, I installed Ubuntu 14.04 (to get EFI booting on a Mac), then I Triquelized it and then tried to upgrade to Trisquel 8. There were issues. I rebooted and the Trisquel 8 GUI seemed to have issues like no spacing between menu items and the try icons are very large. I will add screenshots of my experience with this in another thread. I was just wondering if you have a sense of what may be happening. Are there any expected issues with upgrading from a Trisquelized system? === OTHER SEMI-RELATED ISSUE ===
Re: [Trisquel-users] Trisquel 8 codename "Flidas" Release Candidate is ready for testing
Yeah, in the Secure Boot world someone could make their own key and enroll it
to be trusted in the computer. But yeah, I imagine that most distros that
support Secure Boot probably take the time (and spend the $99) to get signed
by Microsoft's key so that they can be trusted and "run out of the box",
since that seems to be what non-technical people like for how their computers
to work. ("Trisquel is so easy!") This avoids them having to write up
documentation for lots of different machines talking about how to enroll the
distro's key since there's no standard process.
Re: [Trisquel-users] Trisquel 8 codename "Flidas" Release Candidate is ready for testing
"Since when does Secure Boot require Microsoft's approval? That sounds like a version of Restricted Boot." This is too simplistic of a view. Allow me to explain then. I'll copy various things from Matthew Garrett's blog at https://mjg59.dreamwidth.org here. Starting from scratch... "Secure Boot means different things to different people. I think the FSF's definition is a useful one - Secure Boot is any boot validation scheme in which ultimate control is in the hands of the owner of the device, while Restricted Boot is any boot validation scheme in which ultimate control is in the hands of a third party. What Microsoft require for x86 Windows 8 devices falls into the category of Secure Boot - assuming that OEMs conform to Microsoft's requirements, the user must be able to both disable Secure Boot entirely and also leave Secure Boot enabled, but with their own choice of trusted keys and binaries. If the FSF set up a signing service to sign operating systems that met all of their criteria for freeness, Microsoft's requirements would permit an end user to configure their system such that it refused to run non-free software. My system is configured to trust things shipped by Fedora or built locally by me, a decision that I can make because Microsoft require that OEMs support it. Any system that meets Microsoft's requirements is a system that respects the freedom of the computer owner to choose how restrictive their computer's boot policy is. This isn't to say that it's ideal. The lack of any common UI or key format between hardware vendors makes it difficult for OS vendors to document the steps users must take to assert this freedom." So keep in mind that, even with Secure Boot where people can tell their computer what keys are to be trusted, there is no common UI or key format between hardware vendors. So even though people ***can*** revoke keys and use their own trusted keys the lack of standardization in how it's done creates problems with making documentation. Sure: The Trisquel Project might create a key on their own and then tell people to go and revoke the keys that came with their computer and enroll the Trisquel key. But the lack of standardization means we can't tell people exactly *how* to go do that. They'll need to check the documentation that came with the computer. Or maybe with whoever made the computer. Anyway, if Trisquel made a key it needs to get into the computer somehow. Having people revoke the keys that came with the computer and enroll new keys adds an extra layer during the install process which might turn people off. Making free software seem "hard", especially with no standard process from one computer to another. Making it harder for people to move to free software doesn't seem good. This is problem #1. But a lack of a standard process between computers doesn't make it Restricted Boot because people still *can* do it. They just have to follow their docs. More from Matthew... "Most hardware you'll be able to buy towards the end of the year will be Windows 8 certified. That means that it'll be carrying a set of secure boot keys, and if it comes with Windows 8 pre-installed then secure boot will be enabled by default. This set of keys isn't absolutely fixed and will probably vary between manufacturers, but anything with a Windows logo will carry the Microsoft key. We explored the possibility of producing a Fedora key and encouraging hardware vendors to incorporate it, but turned it down for a couple of reasons. First, while we had a surprisingly positive response from the vendors, there was no realistic chance that we could get all of them to carry it. That would mean going back to the bad old days of scouring compatibility lists before buying hardware, and that's fundamentally user-hostile." So we're back to talking to making things easy to use. Okay; so you've got a process where people can enroll and remove keys that are to be trusted (even though there's no standard process for how to do that; so people will need to figure out how to do that on their own... go back to problem #1.) But; most of these computers will come with Microsoft's key pre-installed already. So hmmm... Maybe there's a way to use that to make Secure Boot easier for people. Since the computer comes with Microsoft's key already loaded (even if it can be removed) you can pay $99 to get YOUR stuff signed too. Then, since the chain of key signing trust goes from the Microsoft key to all the way to yours, then *POOF* the distro's stuff is automatically trusted out of the box and people don't have to go do whatever process their computer uses to enroll Trisquel's key first. So perhaps when I said "requires" was too strong a word. Perhaps I should have said "to do it in an easy and user-friendly way" would have been better. But it's still Secure Boot because the computer ***can*** still
Re: [Trisquel-users] Trisquel 8 codename "Flidas" Release Candidate is ready for testing
Is self-signed key now a thing? Linux Foundation is a member of UEFI.org but I was under the impression all distributions used Microsoft's key. I may be wrong as I haven't been following the debate lately.
Re: [Trisquel-users] Trisquel 8 codename "Flidas" Release Candidate is ready for testing
Hm? But this is what you said: "With the exception of Secure Boot, which requires Microsoft to sign stuff for the project so it can be trusted." Since when does Secure Boot require Microsoft's approval? That sounds like a version of Restricted Boot.
Re: [Trisquel-users] Trisquel 8 codename "Flidas" Release Candidate is ready for testing
To both onpon4 and lolider, No I did meant Secure Boot. In a Secure Boot environment the user gets to decide what keys the computer treats as trusted or not. Restricted Boot describes a different setup where they can't. The FSF even draws this distinction: "When done correctly, 'Secure Boot' is designed to protect against malware by preventing computers from loading unauthorized binary programs when booting. In practice, this means that computers implementing it won't boot unauthorized operating systems -- including initially authorized systems that have been modified without being re-approved. This could be a feature deserving of the name, as long as the user is able to authorize the programs she wants to use, so she can run free software written and modified by herself or people she trusts." In that they're describing Secure Boot, not Restricted Boot. So we can use both terms (Secure Boot and Restricted Boot) depending on the specifics of the situation. And in this case I was talking of Secure Boot.
Re: [Trisquel-users] Trisquel 8 codename "Flidas" Release Candidate is ready for testing
Blueman package is not installed but bluez the bluetooth stack is. Install blueman ’sudo apt install blueman’.
Re: [Trisquel-users] Trisquel 8 codename "Flidas" Release Candidate is ready for testing
Hi all! I have been lurking for a while now, following the development of Trisquel 8. Does flidas come with bluetooth support out of the box? I have a Qualcomm Atheros AR9462 card and it has me a little bit confused, supposedly this card should have functional WiFi and Bluetooth without anything special, however Debian still requires the non-free firmware to get bluetooth from it, while the live session of Trisquel 7 detects there is bluetooth, however I am not able to test it because of a bug that disables my touchpad (I don't have a wired mouse to test) and I couldn't find a way to do it via keyboard, I tried the live session of Trisquel 8 and it didn't pick up anything related with bluetooth, I superficially looked around I didn't found anything related to bluetooth installed, is blueman installed? does MATE have its own bluetooth setup tool? has anybody tested AR9462 in recent releases of Linux-libre? ThinkPenguin has the following note: "Almost all recently released distributions are compatible. The bluetooth may not work however on some versions of Parabola GNU/Linux-Libre. A bug was introduced with some kernel(s) that effectively disabled the driver rather than just the loading of non-free firmware for which is not needed for this particular card" Cheers.
Re: [Trisquel-users] Trisquel 8 codename "Flidas" Release Candidate is ready for testing
... Does anyone know why my upgrade from Trisquel 7 to 8 is failing?
Re: [Trisquel-users] Trisquel 8 codename "Flidas" Release Candidate is ready for testing
Yes, 2 is no such file or directory. So it seems this is another device that magically starts working with this change.
Re: [Trisquel-users] Trisquel 8 codename "Flidas" Release Candidate is ready for testing
I now remember that you wrote that some weeks ago. The logs say that "direct
firmware load failed with error -2":
$ grep rtl /var/log/kern.log | cut -d [ -f 2-
(... previous boots: same messsages ...)
11.705433] rtl8188ee: rtl8188ee: Power Save off (module option)
11.705437] rtl8188ee: rtl8188ee: FW Power Save off (module option)
11.705443] rtl8188ee: Requesting firmware
11.735403] ieee80211 phy0: Selected rate control algorithm 'rtl_rc'
11.735616] rtlwifi: rtlwifi: wireless switch is on
11.742946] rtl8188ee :01:00.0: Direct firmware load failed with error
-2
11.742950] rtlwifi: Firmware not available
12.193543] rtl8188ee :01:00.0 wlp1s0: renamed from wlan0
885]: [1523964027.8407] rfkill0: found WiFi radio killswitch (at
/sys/devices/pci:00/:00:1c.0/:01:00.0/ieee80211/phy0/rfkill0)
(driver rtl8188ee)
Is -2 the return code for ENOENT ("No such file or directory")?
Re: [Trisquel-users] Trisquel 8 codename "Flidas" Release Candidate is ready for testing
Check your logs. What do they say? Linux-libre had some deblobbing changes
with 4.16 - see
http://www.fsfla.org/pipermail/linux-libre/2018-April/003284.html
The most notable one here is changing from EINVAL ("Invalid argument") to
ENOENT ("No such file or directory") which, in some cases, has allowed things
like an rtl8821ae card to work without its firmware. I wonder if Trisquel has
incorporated this change. Anyway, check your logs. What do they say?
Re: [Trisquel-users] Trisquel 8 codename "Flidas" Release Candidate is ready for testing
Is there any possibility the bootloader might have loaded the wireless card's firmware (perhaps newly so because it's using UEFI)?
Re: [Trisquel-users] Trisquel 8 codename "Flidas" Release Candidate is ready for testing
2018-04-16T03:09:41+0200 ja...@bluehome.net wrote: > "now is booting as a... UEFI OS?" > > Yup. Trisquel 8 should be fully UEFI compatible. Yay! With the > exception of Secure Boot, which requires Microsoft to sign stuff for > the project so it can be trusted. Our fearless leader said on IRC that > that's not gonna happen. No kowtowing to Microsoft. I think he means Restricted Boot. Because in compliant Secure Boot implementations, the end-user would be able to specify/set the trust for an official Trisquel key used for self-signed releases. -- - Formas de contato: https://libreplanet.org/wiki/User:Adfeno#vCard - Ativista do /software/ livre (não confundir com gratuito). Avaliador da liberdade de /software/ e de /sites/. - Membro do LibrePlanet Brasil: https://libreplanet.org/wiki/Group:LibrePlanet_Brasil - Comunicações sociais federadas padronizadas, onde o "social" permanece independente do fornecedor. - #DeleteWhatsApp. Use o pai dele, #XMPP, federado e com padrão internacional: https://libreplanet.org/wiki/XMPP.pt - #DeleteFacebook #DeleteInstagram #DeleteTwitter #DeleteYouTube. Use redes sociais federadas que suportam #ActivityPub, padrão internacional, como a rede Mastodon: https://joinmastodon.org/ - #DeleteNetflix #CancelNetflix. Evite #DRM: https://www.defectivebydesign.org/ - Quer enviar arquivos para mim? Veja: https://libreplanet.org/wiki/User:Adfeno#Arquivos - Quer doar para mim, ou me contratar? Veja: https://libreplanet.org/wiki/User:Adfeno#Suporte - Minhas contribuições: https://libreplanet.org/wiki/User:Adfeno#Contributions
Re: [Trisquel-users] Trisquel 8 codename "Flidas" Release Candidate is ready for testing
Yeah,it should be restricted not 'secure'. When they say 'security', always ask "whose security?" https://www.fsf.org/campaigns/secure-boot-vs-restricted-boot
Re: [Trisquel-users] Trisquel 8 codename "Flidas" Release Candidate is ready for testing
Don't you mean Restricted Boot?
Re: [Trisquel-users] Trisquel 8 codename "Flidas" Release Candidate is ready for testing
So it's Monday 16. Should I be uncorking a grape juice and rolling up in preparation to celebrate the release of Flidas? Or has it been decided enough things need fixing that the release needs to wait a little longer?
Re: [Trisquel-users] Trisquel 8 codename "Flidas" Release Candidate is ready for testing
"now is booting as a... UEFI OS?" Yup. Trisquel 8 should be fully UEFI compatible. Yay! With the exception of Secure Boot, which requires Microsoft to sign stuff for the project so it can be trusted. Our fearless leader said on IRC that that's not gonna happen. No kowtowing to Microsoft.
Re: [Trisquel-users] Trisquel 8 codename "Flidas" Release Candidate is ready for testing
Hello I din't have any problems installing Trisquel 8 mini i686.iso in an netbook atom N280. checksum md5 ok, live image done witn "creador de discos de arranque" in USB ok, booting and installing ok. Success installing Trisquel 8 amd64.iso on a desktop ASUS/Intel. Some problems whith BIOS, now is booting as a... UEFI OS? Libre greetings
Re: [Trisquel-users] Trisquel 8 codename "Flidas" Release Candidate is ready for testing
Loldier wrote: "[Fedora Media Writer] writes any ISO." My apologies, you are of course correct. I skim read the first of the links you shared, and got the impression that the instructions given there was the limit of what the program could do. Now that I look again, the images make it clear that impression was, as you say, quite incorrect: https://developers.redhat.com/blog/2016/04/26/fedora-media-writer-the-fastest-way-to-create-live-usb-boot-media/ It would be interesting to see what libraries and other dependencies FMW is using under the hood, and how they compare to those used by Etcher. I will suggest to The Assassin that we have at least a cursory glance at the FMW code (as well as the UNetbootin code) as part of creating our fork of Etcher. Perhaps forking an app other than Etcher might be easier or better, or perhaps we can hybridize the best elements of multiple programs.
Re: [Trisquel-users] Trisquel 8 codename "Flidas" Release Candidate is ready for testing
I recently attempted an upgrade from my existing laptops install of Trisquel 7 to Trisquel 8 and the upgrade failed. I have many screenshots showing each prompt. Where do I post this?
Re: [Trisquel-users] Trisquel 8 codename "Flidas" Release Candidate is ready for testing
It writes any ISO. Just select "custom image" and pick a file from your drive. The only part that would be changed is the automatic download which points to Fedora.
Re: [Trisquel-users] Trisquel 8 codename "Flidas" Release Candidate is ready for testing
It might also be good to have a wiki page on some of the common problems people run into when trying to create and use bootable USBs. For example, I flashed both main and Trisquel-Mini versions of Flidas onto an old 4GB USB with Etcher. Trisquel-Mini worked initially, but failed during the process of booting the live session. Trisquel main got to the live session, but then I ran into some problems with web pages crashing. I'm currently trying to figure out whether the problem is the USB being too old to work reliably, but the Disks benchmark failed (in Belenos) due to a well-know bug, and I'm struggling to find any other way to test the health of the USB that isn't super complicated. Here is the best advice I've found so far, after an hour or so of web searching and skimming: https://superuser.com/questions/376274/how-to-check-the-physical-health-of-a-usb-stick-in-linux I'm going to test the same USB with a different burning method, and see if that makes any difference. If it works fine with Startup Disc Creator or DD, that points to the problem being Etcher, which would be good to know.
Re: [Trisquel-users] Trisquel 8 codename "Flidas" Release Candidate is ready for testing
I'm guessing that modifying Fedora Media Writer, to make it work with Debian-based systems and burn distros other than Fedora, is probably more work than forking Etcher and removing the offending behaviour. Don't let me discourage you though, if that's your itch, you go ahead and scratch it! :)
Re: [Trisquel-users] Trisquel 8 codename "Flidas" Release Candidate is ready for testing
There's a lot that could be said on both the topics in this comments. I've started a new thread to discuss Mac-specific problems with Trisquel here: https://trisquel.info/en/forum/getting-trisquel-8-working-macs I've also started a new thread on the user respect issues with Etcher here: https://trisquel.info/en/forum/user-respect-issues-etcher
Re: [Trisquel-users] Trisquel 8 codename "Flidas" Release Candidate is ready for testing
Is there a way to download images, checksums, etc of Trisquel 8 over https? For now, all the links are plain, unencrypted http
Re: [Trisquel-users] Trisquel 8 codename "Flidas" Release Candidate is ready for testing
I'd love to contribute; just don't see how it's feasible. I've tried Trisquel on macs many times in the past and now with the latest ISO. Etcher is no magic silver bullet. DD, my personal favourite, or any other program is capable of writing the ISO to disk but they won't show up. There's something awry in Trisquel's UEFI/EFI implementation that mac's boot firmware doesn't recognize as bootable. I'm on a live session, booted from a USB stick written on my ma with Etcher. It works on this HP but on my mac no cigar.
Re: [Trisquel-users] Trisquel 8 codename "Flidas" Release Candidate is ready for testing
OK, so at least two of us have access to Macs for testing (my wife's is an older MacBook - about 7-8 years old), that's great. It would be great to come up with a fairly reliable set of instructions for installing Flidas on Macs. Shall we start a separate thread to focus on this?
Re: [Trisquel-users] Trisquel 8 codename "Flidas" Release Candidate is ready for testing
Trisquel 8 doesn't work. Burned an ISO to DVD using Finder's built in burner. All is fine but the disc won't show up at boot. At the same time, Debian 9 and Puppy Xenialpup boot just fine.
Re: [Trisquel-users] Trisquel 8 codename "Flidas" Release Candidate is ready for testing
I wonder if Red Hats's Fedora Media Writer could be modified to download and write Trisquel ISO to USB. It's available for Win/Mac/Linux. https://developers.redhat.com/blog/2016/04/26/fedora-media-writer-the-fastest-way-to-create-live-usb-boot-media/ https://getfedora.org/en/workstation/download/
Re: [Trisquel-users] Trisquel 8 codename "Flidas" Release Candidate is ready for testing
MagicBanana: >> Software dos not necessarily stop working because it is old. > If there is usable free software to install the live ISO, let us recommend that! We value freedom over convenience.
Re: [Trisquel-users] Trisquel 8 codename "Flidas" Release Candidate is ready for testing
Just tried using the Flidas USB I successfully used on my AA1 to boot up a live session on my wife's Mac (El Capitan). No dice. I held down the Option key, and got a screen allowing me to choose boot sources, but it didn't pick up the OS on the USB. Do I have to use a live USB *made* on a Mac to boot up on a Mac? Any suggestions?
Re: [Trisquel-users] Trisquel 8 codename "Flidas" Release Candidate is ready for testing
Success! Today I: * used wget to download trisquel_8.0_i686.iso - check! * checked the md5sum - check! * used Startup Disk Creator in Belenos to create a bootable USB - check! * rebooted using the USB - check! * checked the integrity of the USB - check! * rebooted and launched a live session using the USB - check! * connected to WiFi - check! * logged in here and posted this message - check! At times, I have worried that I wouldn't be able to run Flidas on my poor old Aspire One, and that I'd have to fall back to Trisquel-Mini, or maybe abandon Trisquel for a more lightweight distro. I'm happy to report Flidas works like a dream with the new Mate DE, and I'll be staying with standard Trisquel! Next I will try installing to my test partition. I will also test making a T8 USB using my wife's MacOS, following the instructions on the wiki, and try booting into Trisquel on her Mac too. I'll also download Trisquel-Mini and test that. Will report back on the results.
Re: [Trisquel-users] Trisquel 8 codename "Flidas" Release Candidate is ready for testing
Since my last post, I managed to get a bootable system by extracting the .iso archive onto a formatted flash drive, having one FAT partition, taking up the whole disk. Once I booted this version, I tried running the screen reader, and got it started, only to have it turn off within 5 seconds, or so. I tried using the toggle shortcut, 'alt+super+s' and by using the 'run' dialogue and typing "orca", then hitting 'enter'. I tried several reboots, waiting different amounts of time before starting orca, perhaps the desktop wasn't ready? Still no joy. Is anyone else using orca on this edition?
Re: [Trisquel-users] Trisquel 8 codename "Flidas" Release Candidate is ready for testing
"Given that Trisquel, like its Ubuntu base, is meant to be the most
user-friendly distro for people new to GNU-Linux,"
I would say Trisquel is meant to be the most user-friendly distro that is
fully free. That last clause matters a lot, since there are other distros
that put user-friendliness (defined by ease of use rather than respecting the
user's freedom and privacy) above all other considerations.
One benefit of using MATE is that it should be fairly easy to shift the look
and feel of the user interface to match what users accustomed to other OSes
expect. The default of course strongly resembles Windows, especially Windows
95 through Vista. MATE (at least the version in Ubuntu MATE) has a "Panels"
dropmenu in the MATE Tweak tool's "Interface" portion that lets you switch to
a Mac-like look and feel ("Cupertino") or Ubuntu-style ("Mutiny"). Does
Trisquel 8's implementation of MATE have this? I would also recommend a
"Mountain View" option that replicates the ChromeOS or Chromium OS look and
feel.
Re: [Trisquel-users] Trisquel 8 codename "Flidas" Release Candidate is ready for testing
I downloaded the 64-bit version from Jenkins.trisquel.info/makeiso/RC/ and wrote it to flash drive using the 'dd' command; resulting image is not bootable. I used http in the browser, which works for all other distros' live images but Trisquel.
Re: [Trisquel-users] Trisquel 8 codename "Flidas" Release Candidate is ready for testing
I'm also getting a weird issue with downloading trisquel_8.0_i686.iso from: http://jenkins.trisquel.info/makeiso/iso/RC/ I've tried it twice, and both times, it almost downloaded, then displayed an error in the ABrowser downloads menu, saying "file moved or missing". I haven't moved the file, and it's not missing, there's a 2.6GB file with that name in my Downloads folder. But running md5sum on that file gives me a hash that doesn't match the md5sum file downloaded from the same source. I have almost 90GB free on my drive, so that's not the problem. I'm mystified. Could it be that too many of us are hitting that server, causing downloads to fail? Is there another download source I could try? What's really strange is that I successfully downloaded the Sugar edition from the same source, and the download completed and passed the md5sum just fine. I made a bootable USB with the Startup Disc Creator in System Settings, and booted into a live system just fine too (first time I've managed to get a Sugar DE working, yay!).
Re: [Trisquel-users] Trisquel 8 codename "Flidas" Release Candidate is ready for testing
InfraRecorder works just fine with win 10. It's practical because it need not be installed. There's a zip portable archive.
Re: [Trisquel-users] Trisquel 8 codename "Flidas" Release Candidate is ready for testing
Windows 10 burning an image is easy. Just open Explorer, right-click on the ISO and select 'Burn to disc'. Pix to follow if somebody needs them to write up instructions.
Re: [Trisquel-users] Trisquel 8 codename "Flidas" Release Candidate is ready for testing
What’s up with this devel not found? I get this when attempting to initiate a download from the RC link.
Re: [Trisquel-users] Trisquel 8 codename "Flidas" Release Candidate is ready for testing
My wife has a Mac (running El Capitan), which I can use (with her permission) to test the MacOS instructions. We no longer own any devices running Windows (yay!), but I'm sure there are GNUbies out there who still have a dual-boot, or run Windows on a separate PC. Anybody willing to do some testing and help update the wiki if needed? It would be good to make sure the instructions work for 2000/XP, Vista/7, and 8/10, with separate instructions for different versions if needed. Burning .ISO to CD I note that the code of Infrarecorder, the app recommended for burning the .ISO on Windows, doesn't appear to have been worked on since 2012 according to its GitHub repo: https://github.com/kindahl/infrarecorder There is a FOSSHub page last updated in 2014, which suggests it worked then on all Windows versions from 2000 > 8: https://www.fosshub.com/InfraRecorder.html/ Similarly, the Burn app recommended for burning the .ISO on MacOS hasn't had a new version released since 2011, and I could fine no sign of the developer moving it to another forge: (https://sourceforge.net/projects/burn-osx/files/) Since the goal is to help a user transition to a fully free OS from an OS they're already running, why not simply give instructions for using the default disc burning software in that OS (per version if they differ)? Or if there isn't one, the most common disc burning freeware for that OS? That way the instructions are more likely to stay up-to-date, regardless of the fortunes of free code Windows/ Mac apps. Making Bootable USB The Windows instructions for making a bootable USB recommend the Universal USB Installer from PenDriveLinux. According to the homepage for that program, it now requires Vista or higher to work: "Windows Vista/7/8/10 or WINE to create the USB (Win 98/XP/2K WILL NOT Work!)" http://www.pendrivelinux.com/universal-usb-installer-easy-as-1-2-3/#button The devices running these older version are more likely to have a CD-ROM drive, and also more likely not to have a BIOS that allows booting from USB. It might be good to include a note under the 'Boot Media' section of the Installation Guide page, advising people running these older versions of Windows that the USB method may not work, and recommending they install by burning a CD.
Re: [Trisquel-users] Trisquel 8 codename "Flidas" Release Candidate is ready for testing
Given that Trisquel, like its Ubuntu base, is meant to be the most user-friendly distro for people new to GNU-Linux, what are the recommended methods for installing Trisquel for people currently using: * Windows * Mac * Ubuntu Is there any kind of 'introducing Trisquel' wiki page or document that we can distribute to people, encouraging them to try it for the first time, and supplying these installation instructions? If so, will it need to be updated for Trisquel 8?
Re: [Trisquel-users] Trisquel 8 codename "Flidas" Release Candidate is ready for testing
Hi david, thanks! This is what I'm waiting for.
Re: [Trisquel-users] Trisquel 8 codename "Flidas" Release Candidate is ready for testing
Yeah, the torrents never work on the development versions.
Re: [Trisquel-users] Trisquel 8 codename "Flidas" Release Candidate is ready for testing
> What's the most appropriate way of reporting these bugs? https://trisquel.info/en/project/issues signature.asc Description: PGP signature
Re: [Trisquel-users] Trisquel 8 codename "Flidas" Release Candidate is ready for testing
I found a couple smaller bugs. One is a typo, and another relates to the spell checker/dictionary in Abrowser. What's the most appropriate way of reporting these bugs?
Re: [Trisquel-users] Trisquel 8 codename "Flidas" Release Candidate is ready for testing
When trying to open the file "trisquel_8.0_amd64.iso.torrent" in Transmission, I get the error: "Tracker gave an error: "Requested download is not authorized for use with this tracker"."
Re: [Trisquel-users] Trisquel 8 codename "Flidas" Release Candidate is ready for testing
Beautiful! I Googled "tee" before my post, but I wasn't sure if it would work with a terminal session like this. Thanks!
Re: [Trisquel-users] Trisquel 8 codename "Flidas" Release Candidate is ready for testing
> $ sudo apt upgrade > upgrade.log Actually, never mind. If you do this the output won't be printed to the terminal, so you won't be prompted to confirm that you want to upgrade packages. Instead use $ sudo apt upgrade | tee upgrade.log which will both print the output to the terminal and write to the file. signature.asc Description: PGP signature
Re: [Trisquel-users] Trisquel 8 codename "Flidas" Release Candidate is ready for testing
> how would we capture the > terminal output during the upgrade/install? If I understand your question correctly, you can write the output of a terminal command to a file with '>'. $ the-command > the-file.log or in the case of your question, $ sudo apt upgrade > upgrade.log signature.asc Description: PGP signature
Re: [Trisquel-users] Trisquel 8 codename "Flidas" Release Candidate is ready for testing
That's great news. Is there a document or URL that you could point us to that gives instructions on how to capture upgrade/install output? I know about /var/log/dist-upgrade, but how would we capture the terminal output during the upgrade/install? Or is that not valuable? And any other suggestions would be helpful. Thanks.
[Trisquel-users] Trisquel 8 codename "Flidas" Release Candidate is ready for testing
Hi all! Trisquel 8 is almost ready, and we've got a full set of Release Candidate ISO images for testing at http://jenkins.trisquel.info/makeiso/iso/RC/ These latest images should have fixed all the issues some of us had with bootable USB drives and untimely initramfs prompts. They also include of course all the recent functional and freedom fixes and the new artwork. If no release-blocking bugs (i.e., something that renders these images unusable for someone or new freedom issues) are found, we'll proceed with the release on Monday 16. That gives us a full week for testing and feedback and also for fixing an small but relevant issue I'll write about below. Please test these images for those release-blocking bugs and have in mind that we'll try to work on the rest of the old and new non-critical pending issues right after the public release. We'll also share our plan for the soon-to-be started Trisquel 9 development with the Flidas announcement. One issue that we'll be fixing this week is the implementation of proper translation hooks for the new Abrowser homepage privacy settings. We'll also include some translations (it's currently only available in English) with the help of several community members, and we'll share the details for adding more languages to this increasingly relevant component later. Thanks all for your help!
