Page MenuHomeSolus

feuerstein (Timo)
User

Projects

User does not belong to any projects.

Today

  • Clear sailing ahead.

Tomorrow

  • Clear sailing ahead.

Saturday

  • Clear sailing ahead.

User Details

User Since
Oct 8 2018, 7:58 PM (32 w, 3 d)
Availability
Available

Recent Activity

Feb 28 2019

feuerstein awarded T7595: CinelerraGG a Like token.
Feb 28 2019, 8:21 AM · Package Requests

Feb 26 2019

feuerstein added a comment to T7634: GoogleDocs Speech to text doesn't work.

@JoshStrobl It's not that speech-to-text isn't working. It is indeed working in Google Chrome under Solus but the quality of the engine is just not good and doesn't match the results I get under Windows 10 using an identical version of Google Chrome. I'm wondering whether the Chrome built is a totally different one under Solus or maybe there are any other optimizations that can be done?
@mate-user Did you compare the engine in an identical version of Google Chrome under Windows 10?

Feb 26 2019, 12:28 PM · Upstream Issue, Third Party Software

Feb 25 2019

feuerstein created T7634: GoogleDocs Speech to text doesn't work.
Feb 25 2019, 10:46 PM · Upstream Issue, Third Party Software

Jan 26 2019

feuerstein added a comment to T7538: Mouse cursor gets stuck in left upper corner.

inxi gives this output:
CPU: Dual Core Intel Core i5-6200U (-MT MCP-)
speed/min/max: 800/400/2800 MHz Kernel: 4.20.3-108.current x86_64 Up: 3m
Mem: 1297.6/7859.9 MiB (16.5%)

Jan 26 2019, 7:20 PM · Hardware
feuerstein added a comment to T7538: Mouse cursor gets stuck in left upper corner.

It's a trackpoint, not a mouse. I just realized that this also sometimes happens before login.

Jan 26 2019, 7:17 PM · Hardware

Jan 25 2019

Herald added a project to T7538: Mouse cursor gets stuck in left upper corner: Lacks Project.
Jan 25 2019, 7:17 PM · Hardware

Jan 18 2019

feuerstein updated the task description for T7510: Printer utilities and drivers for Lexmark MS710dn.
Jan 18 2019, 8:57 AM · Package Requests
feuerstein created T7510: Printer utilities and drivers for Lexmark MS710dn.
Jan 18 2019, 8:52 AM · Package Requests

Jan 4 2019

Lorien awarded T7284: Stuck in emergency mode after regular Solus reboot a Yellow Medal token.
Jan 4 2019, 5:42 PM · Software
feuerstein closed T7284: Stuck in emergency mode after regular Solus reboot as Resolved.

Will do :) Learnt a lot in the process and it was worth the effort. Thanks again!

Jan 4 2019, 5:24 PM · Software
feuerstein added a comment to T7284: Stuck in emergency mode after regular Solus reboot.


Filesystem is modified and I rebooted and it worked! Thank you all for helping me in this process @Lorien @Girtablulu and @DataDrake
I will do a backup and see if the next couple of updates and reboots work. As I understand changes with fsck are not permanent but only for one session? Is this correct? Are there any more things I should do to ensure a safe system or can I help find out what caused this problem? Apparently there was another Solus user with the same problem?

Jan 4 2019, 4:14 PM · Software
feuerstein added a comment to T7284: Stuck in emergency mode after regular Solus reboot.

I clicked y. It says:
Inode 3670134 was part of the orphaned inode list. FIXED.
Deleted inode 4194399 has zero dtime. Fix<y>?

Jan 4 2019, 3:47 PM · Software
feuerstein added a comment to T7284: Stuck in emergency mode after regular Solus reboot.


I'll go ahead and try to fix it? Will this be permanent or only for the session? I've never had to deal with fsck before and like to be careful...

Jan 4 2019, 3:40 PM · Software
feuerstein added a comment to T7284: Stuck in emergency mode after regular Solus reboot.

When I check my previous screenshots/pictures, it looks that udev and systemd configurations were skipped?

Jan 4 2019, 3:28 PM · Software
feuerstein added a comment to T7284: Stuck in emergency mode after regular Solus reboot.

I typed journalctl and looked through most of the lines. The error messages that stood out were two systemd related messages in bold:

Jan 4 2019, 3:26 PM · Software
feuerstein added a comment to T7284: Stuck in emergency mode after regular Solus reboot.


This is the emergency boot message I get.

Jan 4 2019, 3:19 PM · Software
feuerstein added a comment to T7284: Stuck in emergency mode after regular Solus reboot.

I see, sudo eopkg check | grep Broken | awk '{print $4}' | xargs sudo eopkg it --reinstall worked better than before but still some items were skipped as seen in the screenshot. @Girtablulu

Jan 4 2019, 2:29 PM · Software
feuerstein added a comment to T7284: Stuck in emergency mode after regular Solus reboot.

I ran sudo eopkg up and it upated nearly 1.1 GB. This is quite a lot and I remember having kept my system always up to do. Not sure why it is so much to update. It looks like some were skipped:


I exited chroot, rebooted and it still boots into emergency mode.

Jan 4 2019, 1:32 PM · Software
feuerstein added a comment to T7284: Stuck in emergency mode after regular Solus reboot.

Thanks a lot! Internet is working now in chroot. I ran sudo eopkg check | grep Broken | awk '{print $4}' | xargs sudo eopkg it --reinstall again and got another system error "25, inappropriate ioctl for device":

Jan 4 2019, 1:11 PM · Software
feuerstein added a comment to T7284: Stuck in emergency mode after regular Solus reboot.

This is how it looks like:

Jan 4 2019, 12:07 PM · Software
feuerstein added a comment to T7284: Stuck in emergency mode after regular Solus reboot.

@Girtablulu Thanks, there's indeed no internet connection when in chroot. I typed nano /etc/resolv.conf but don't know how to save the addition of the nameserver with the IP. How can I do that?

Jan 4 2019, 12:02 PM · Software
feuerstein added a comment to T7284: Stuck in emergency mode after regular Solus reboot.

In my terminal window it says root@solus / #
I guess I should be correctly in chroot?

Jan 4 2019, 10:47 AM · Software
feuerstein added a comment to T7284: Stuck in emergency mode after regular Solus reboot.

The output of eopkg list-repo is https://mirrors.rit.edu/solus/packages/shannon/eopkg-index.xml.xz
While the output of eopkg ur points to the .../eopkg-index.xml.xz.sha1sum
Is this correct?
When opening mirrors.rit.edu/solus/packages/shannon through a web browser there's three options: .xml.sha1sum, .xml.xz, and .xml.xz.sha1sum?

Jan 4 2019, 10:42 AM · Software
feuerstein added a comment to T7284: Stuck in emergency mode after regular Solus reboot.

I connect with a cable and it is still the same issue. Is the repo mirror down or an alternative one I can try?

Jan 4 2019, 10:34 AM · Software
feuerstein added a comment to T7284: Stuck in emergency mode after regular Solus reboot.

It looks like the repo link doesn't work? Wifi is working well and I can open other websites from the live iso.

Jan 4 2019, 10:10 AM · Software
feuerstein added a comment to T7284: Stuck in emergency mode after regular Solus reboot.

It says: https://mirrors.rit.edu/solus/packages/shannon/eopkg-index.xml.xz

Jan 4 2019, 8:31 AM · Software

Jan 3 2019

feuerstein added a comment to T7284: Stuck in emergency mode after regular Solus reboot.

@Girtablulu After the previous terminal command I exited chroot and rebooted but it still boots to emergency mode. Is there a command to add system.base and to update the repositories while in chroot?

Jan 3 2019, 10:26 PM · Software
feuerstein added a comment to T7284: Stuck in emergency mode after regular Solus reboot.

Thanks, I got this result now:


How shall I proceed?

Jan 3 2019, 4:26 PM · Software
feuerstein added a comment to T7284: Stuck in emergency mode after regular Solus reboot.

I followed the suggestions by @Girtablulu but I'm not sure what to look for or how to interpret the results I've got. This is how it looks like:


Shall I proceed by just typing nano /etc/fstab now?

Jan 3 2019, 3:52 PM · Software

Jan 2 2019

feuerstein added a comment to T7284: Stuck in emergency mode after regular Solus reboot.

Interesting. Is this related to the rollback functionality of clr-boot-manager so that there are always automatically two kernels installed? I hit the "space bar" several times and booted into Solus-current-4.18.16-96 first and then tried with Solus-current-4.18.16-97 but both lead to emergency mode.

Jan 2 2019, 5:25 PM · Software
feuerstein added a comment to T7284: Stuck in emergency mode after regular Solus reboot.


It looks like more or less the same?

Jan 2 2019, 3:30 PM · Software
feuerstein renamed T7284: Stuck in emergency mode after regular Solus reboot from clr-boot-manager update cannot determine currently running kernel after chrooting to resolve emergency boot mode to Stuck in emergency mode after regular Solus reboot.
Jan 2 2019, 3:27 PM · Software
feuerstein added a comment to T7284: Stuck in emergency mode after regular Solus reboot.

Just exit chroot, the rebooted and I am still stuck in emergency mode.

Jan 2 2019, 3:26 PM · Software
feuerstein updated subscribers of T7284: Stuck in emergency mode after regular Solus reboot.

Apparently, this happened before: https://getsol.us/forums/viewtopic.php?t=10871
@sunnyflunk You replied to this message in the forums. Does that mean this is perfectly normal and the sudo clr-boot-manager update command was successful despite the error?

Jan 2 2019, 3:19 PM · Software
feuerstein added a comment to T7284: Stuck in emergency mode after regular Solus reboot.

Thanks for your help. Yes, I first typed mount /dev/sda3/target, then mount /dev/sda1/target/boot and then the three mount --bind ones, and after that chroot /target. Not sure why - as in the screenshot - the Solus repository could not be reached and clr-boot-manager cannot determine the currently running kernel.

Jan 2 2019, 3:10 PM · Software
feuerstein added a comment to T7284: Stuck in emergency mode after regular Solus reboot.


This is the latest series of commands. I should add that I am a fairly conservative user and always used the stable repositories and didn't install any software outside what is available in the software center.

Jan 2 2019, 2:54 PM · Software
feuerstein renamed T7284: Stuck in emergency mode after regular Solus reboot from Solus boots into emergency mode to clr-boot-manager update cannot determine currently running kernel after chrooting to resolve emergency boot mode.
Jan 2 2019, 2:46 PM · Software
feuerstein added a comment to T7284: Stuck in emergency mode after regular Solus reboot.

I found out that I'm using EFI and I followed all steps - at least I think - however, the sudo clr-boot-manager update command failed with the following error: [Error] cbm (src/bootman/update.c:L270): Cannot determine currently running kernel. I tried following the instructions via https://www.reddit.com/r/SolusProject/comments/9gc4gk/help_with_fresh_installation/ by sudo eopkg dr Solus, sudo eopkg rr Solus, and sudo eopkg ar Solus https://mirrors.rit.edu/solus/packages/shannon/eopkg-index.xml.xz and got the following error: No repository found. Automatically adding Solus stable. Repo already present with name Solus and same URL. Removing first. Repo Solus added to system. Updating repository: Solus. Solus repository could not be reached. Removing Solus from system. Is there anyone who could give a hint what seems to be the problem?

Jan 2 2019, 2:31 PM · Software
feuerstein added a comment to T7284: Stuck in emergency mode after regular Solus reboot.
Jan 2 2019, 11:54 AM · Software

Jan 1 2019

feuerstein added a comment to T7284: Stuck in emergency mode after regular Solus reboot.

Jan 1 2019, 4:33 PM · Software
feuerstein added a comment to T7284: Stuck in emergency mode after regular Solus reboot.

@Girtablulu I don't understand the instructions in the Help Center. I booted the Live ISO and typed sudo su. Not sure how to proceed. Do I need to replace the mkdir /target command with something and if yes, with what? I think my system uses Grub.

Jan 1 2019, 4:20 PM · Software

Dec 9 2018

feuerstein added a comment to T7284: Stuck in emergency mode after regular Solus reboot.

@Girtablulu I'm afraid that I will lose all my data if I run a LiveISO. Could you walk me through the steps I have to take? I can have a LiveISO ready tomorrow.

Dec 9 2018, 10:50 PM · Software

Dec 6 2018

feuerstein added a comment to T7284: Stuck in emergency mode after regular Solus reboot.

@Girtablulu Thank you for trying to help me with this but I already cannot pass the first issue as I don't understand the instructions for boot rescue given in the Help Center. All commands I entered are not working in emergency mode but most likely I'm not sure with which one to proceed. For example I started with sudo su but it says: command not found.

Dec 6 2018, 1:04 PM · Software

Dec 5 2018

feuerstein added a comment to T7284: Stuck in emergency mode after regular Solus reboot.

@Girtablulu How would I do this? I use Solus because it's easy to use but never had to deal with the emergency mode before.

Dec 5 2018, 9:44 AM · Software

Dec 4 2018

Herald added a project to T7284: Stuck in emergency mode after regular Solus reboot: Lacks Project.
Dec 4 2018, 9:19 PM · Software

Nov 21 2018

feuerstein updated the task description for T7031: Publii.
Nov 21 2018, 9:23 AM · Needs Maintainer, Package Requests

Nov 12 2018

feuerstein updated the task description for T7031: Publii.
Nov 12 2018, 10:55 AM · Needs Maintainer, Package Requests
feuerstein created T7190: Pelican.
Nov 12 2018, 10:48 AM · Package Requests

Oct 24 2018

feuerstein added a comment to T2361: caddy.

Regarding plugins I'd only say as much as don't trust any plugin as long as you didn't enable it yourself.

Oct 24 2018, 1:57 PM · Needs Maintainer, Package Requests
feuerstein added a comment to T2361: caddy.

@der_eismann Thank you, I'll check them out. AFAIK there's no automatic enablement and auto-renewal of SSL certificates though.

Oct 24 2018, 1:29 PM · Needs Maintainer, Package Requests
feuerstein created T7092: Unresponsive Files icon in panel.
Oct 24 2018, 1:24 PM · Invalid Tracker (Budgie)
feuerstein added a comment to T7084: Cannot launch Publii .AppImage.

Thank you @sunnyflunk I totally overlooked the fact that I had a local Publii text file which was indeed the problem. Sorry for the trouble. It is indeed solved now and the .AppImage is starting just fine. I'd still very much prefer a native package to work with though: T7031. I suppose there'll be an advantage performance-wise and receiving the latest updates will be easier?

Oct 24 2018, 1:14 PM · Software

Oct 23 2018

feuerstein added a comment to T2361: caddy.

+1 for caddy! Is there an easy to use alternative to caddy in the Solus repo that I can use?

Oct 23 2018, 12:22 PM · Needs Maintainer, Package Requests
feuerstein added a comment to T7084: Cannot launch Publii .AppImage.

I deleted the file and downloaded with wget but I still get the same error message as mentioned above.

Oct 23 2018, 12:10 PM · Software
feuerstein added a comment to T7084: Cannot launch Publii .AppImage.

Apologies, I took the following steps to launch the .AppImage: chmod a+x Publii_0.31.3.AppImage, and then ./Publii_0.31.3.AppImage. This resulted in:

Oct 23 2018, 11:28 AM · Software
feuerstein added a comment to T7082: Fix Gnome To Do theming.


Apologies, I'm on the default Shannon repo with the latest updates using Budgie.

Oct 23 2018, 11:15 AM · Software
Herald added a project to T7084: Cannot launch Publii .AppImage: Lacks Project.
Oct 23 2018, 11:08 AM · Software
feuerstein created T7083: Fix DNSCryptClient tray icon size.
Oct 23 2018, 11:03 AM · Upstream Issue
feuerstein created T7082: Fix Gnome To Do theming.
Oct 23 2018, 10:57 AM · Software

Oct 8 2018

feuerstein created T7031: Publii.
Oct 8 2018, 9:30 PM · Needs Maintainer, Package Requests