BitCurator v. 1.8.12 still booting to terminal

[Dorothy Waugh]

Hi all,

Apologies for bringing this up again, but we still haven't been able to solve the BitCurator booting to terminal issue. We tried disabling Fast Startup and Secure Boot, but this didn't help. We've also tried reinstalling to ensure we're not using legacy mode and to make sure we haven't been affected by any upgrades, as Kam suggested previously.

We have now tried installing the latest version on it's own hard drive (in order to avoid the dual-boot/Windows issue), but it is still frequently booting to terminal. Sometimes it works just fine--immediately after we installed onto the new hard drive (yesterday), it booted to the GUI just fine several times--but today it's back to booting to terminal. We haven't been able to use BitCurator since July, because we just can't work out this problem! So sad!

If anyone has any suggestions for us, we would be very appreciative!

Thanks so much,

Dorothy

[Lora Woodford]

I don't have an answer for you, Dorothy, but I'm glad you brought it up.  As I wrote a few months ago now, I wasn't able to reach a point of confidence using 1.8.x because of this issue, so ultimately made the decision to roll back to last pre-Xenial release (1.6.22) and manually update select applications as needed.  

So, I'm no help, but you aren't alone!

Lora

--
You received this message because you are subscribed to the Google Groups "BitCurator Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcurator-users+unsubscribe@googlegroups.com.
To post to this group, send email to bitcurator-users@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bitcurator-users/a7056411-ba0e-454a-a9ae-11de0d13f74e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Kam Woods]

Per suggestions in previous threads, disabling rbfstab *prior to installing* (by clicking on the green disk icon and selecting "Set mount policy WRITEABLE") and then leaving the read-only enforcement disabled permanently will place BitCurator in a state where it should be functionally the same as stock Ubuntu at boot time. If it still boots to terminal after *that*, it's likely a Ubuntu issue rather than a BitCurator-specific issue.

Also, per my previous comments, if nobody with sufficient udev expertise comes forward to try and fix the read-only enforcement mechanism for permanent installs, this leaves at least one additional option, which is to remove rbfstab and the BitCurator policy app from future releases.

If there's a consensus on making this happen, it can happen, but the path towards involves one of two methods:

1. Opening a Jira ticket on the Consortium issue site and getting enough votes or comments from the community to prioritize this action in the next release cycle, or

2. Some sort of formal vote of the Consortium members to agree upon this change

Regards,

Kam

To view this discussion on the web visit https://groups.google.com/d/msgid/bitcurator-users/CAD1basOZrhbjAdn%3DeWRGythmR2QqhvMCaH_Lcvp4Df4RaoC7-g%40mail.gmail.com.

[Jonathan Farbowitz]

Hi Kam,

I have a quick question on your suggestion of disabling rbfstab prior to installation. If Bitcurator is installed in this way can users still choose to enable read-only enforcement later on? I realize that this could potentially cause the issue mentioned, but want to make sure that it would be still be possible to try software write blocking later on. 

Best,

Jonathan

On Monday, October 9, 2017 at 4:44:01 PM UTC-4, Kam Woods wrote:

Per suggestions in previous threads, disabling rbfstab *prior to installing* (by clicking on the green disk icon and selecting "Set mount policy WRITEABLE") and then leaving the read-only enforcement disabled permanently will place BitCurator in a state where it should be functionally the same as stock Ubuntu at boot time. If it still boots to terminal after *that*, it's likely a Ubuntu issue rather than a BitCurator-specific issue.

Also, per my previous comments, if nobody with sufficient udev expertise comes forward to try and fix the read-only enforcement mechanism for permanent installs, this leaves at least one additional option, which is to remove rbfstab and the BitCurator policy app from future releases.

If there's a consensus on making this happen, it can happen, but the path towards involves one of two methods:

1. Opening a Jira ticket on the Consortium issue site and getting enough votes or comments from the community to prioritize this action in the next release cycle, or

2. Some sort of formal vote of the Consortium members to agree upon this change

Regards,

Kam

On Fri, Oct 6, 2017 at 3:04 PM, Lora Woodford <lorawo...@gmail.com> wrote:

I don't have an answer for you, Dorothy, but I'm glad you brought it up.  As I wrote a few months ago now, I wasn't able to reach a point of confidence using 1.8.x because of this issue, so ultimately made the decision to roll back to last pre-Xenial release (1.6.22) and manually update select applications as needed.  

So, I'm no help, but you aren't alone!

Lora

On Fri, Oct 6, 2017 at 11:25 AM, Dorothy Waugh <dorry...@gmail.com> wrote:

Hi all,

Apologies for bringing this up again, but we still haven't been able to solve the BitCurator booting to terminal issue. We tried disabling Fast Startup and Secure Boot, but this didn't help. We've also tried reinstalling to ensure we're not using legacy mode and to make sure we haven't been affected by any upgrades, as Kam suggested previously.

We have now tried installing the latest version on it's own hard drive (in order to avoid the dual-boot/Windows issue), but it is still frequently booting to terminal. Sometimes it works just fine--immediately after we installed onto the new hard drive (yesterday), it booted to the GUI just fine several times--but today it's back to booting to terminal. We haven't been able to use BitCurator since July, because we just can't work out this problem! So sad!

If anyone has any suggestions for us, we would be very appreciative!

Thanks so much,

Dorothy

--
You received this message because you are subscribed to the Google Groups "BitCurator Users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to bitcurator-use...@googlegroups.com.
To post to this group, send email to bitcurat...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/bitcurator-users/a7056411-ba0e-454a-a9ae-11de0d13f74e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "BitCurator Users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to bitcurator-use...@googlegroups.com.
To post to this group, send email to bitcurat...@googlegroups.com.

[Kam Woods]

Yes, it can. The icon will remain in the app bar and the underlying script will still be present.

To unsubscribe from this group and stop receiving emails from it, send an email to bitcurator-users+unsubscribe@googlegroups.com.
To post to this group, send email to bitcurator-users@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/bitcurator-users/a66066e9-8690-4e6b-b21b-28c666cd75f6%40googlegroups.com.

[walker]

Hey Dorothy,

I know this is an older post, but for what is worth, I had the same problem you describe and have had success with the 2.0.0-RC2 ISO release listed on the Releases page.

Best,

Walker