What to do when I'm getting `Encountered an unexpected error. (Dell)` #79

alexanderadam · 2024-02-25T17:45:55Z

I'm getting the error Encountered an unexpected error. (Dell) on current Fedora on an XPS 13 9300.

This message popped up after a recent upgrade and now I'd love to know what I can do to tackle this.
I usually see it after waking up from hibernate and after a reboot.

The text was updated successfully, but these errors were encountered:

maniacx · 2024-02-25T19:11:21Z

This is how it works. You can test everything with command line.

Check for executable installed

First it will check if the below file exist. if it exist it, knows it is a dell laptop. But I think it has detected it as the Dell is mentioned in the error, but no harm checking.

ls -l /sys/devices/platform/dell-laptop

For dell you need to install either one of the package. libsmbios or Dell command center. Some laptop libsmbios works but Dell command center does not, but on others laptop Dell command center works but libsmbios does not.
So next step the extension will check if the executable exist.

extensionis check if program is available in enviroment. If it doesnt find the path it will check for the default installation location.

You can try test this by running the command
Program in enviroment. (This will ouptut charging mode information)

sudo smbios-battery-ctl --get-charging-cfg

Default installation location

ls -l /usr/sbin/smbios-battery-ctl

It does the same for Dell command center.
Program in enviroment. (This will ouptut charging mode information)

sudo cctk  --PrimaryBattChargeCfg

Default installation location

ls -l /opt/dell/dcc/cctk

It willl use the package that is installed. If both are install, you will get an option to choose in extension preferences between Dell command center and libsmbios.

Test if charging mode changes using command line.

Check which package is installed.
Try changing threshold using command line. You can find command line details here
https://maniacx.github.io/Battery-Health-Charging/device-compatibility/dell#testing-charging-threshold-using-command-line
I read a that some xps doesnt work will libsmbios, but works well with Dell command center.
If you are already using Dell Command Center, there could a possibility that Fedora has automatically installed libsmbios, as libsmbios is also needed as dependencies for firmware updates. and the extension may have choosen to use libsmbios (smbios-battery-ctl) as a way to change threshold, but since xps doesnt work with libsmbios it fails.
So check if by any chance both package are install, libsmbios and dell command center. If both are installed you will find an option in extension settings can choose which package the extension should use to change threshold

alexanderadam · 2024-02-26T19:04:10Z

First it will check if the below file exist. if it exist it, knows it is a dell laptop. But I think it has detected it as the Dell is mentioned in the error, but no harm checking.

ls -l /sys/devices/platform/dell-laptop

done and I think it looks good

For dell you need to install either one of the package. libsmbios or Dell command center.

I have libsmbios and I think that it worked before. 🤔

You can try test this by running the command Program in enviroment. (This will ouptut charging mode information)
sudo smbios-battery-ctl --get-charging-cfg

looks good

Default installation location
ls -l /usr/sbin/smbios-battery-ctl

it's there

It does the same for Dell command center. Program in enviroment. (This will ouptut charging mode information)

I don't have cctk

2. Try changing threshold using command line. You can find command line details here
   https://maniacx.github.io/Battery-Health-Charging/device-compatibility/dell#testing-charging-threshold-using-command-line

I would say that this also looks like expected 🤔

So if it wouldn't work with libsmbios I would have gotten errors in the CLI as well, right?
Or am I misinterpreting this?

And if everything is working as expected is there any log or so where the extensions shows more details or a stacktrace?

PS: Your description is amazing! Also thank you so much for the extension! 🙏

maniacx · 2024-02-26T23:45:25Z

Yes everything seem fine from your end. No there are no logs. I added few logs, that will show me what command are execute and what are the response. Kindly install this test.zip and check the log journalctl -f -o cat /usr/bin/gnome-shell

How did you manage to get time taken to execution the command in terminal? never new that trick.

Also I saw pkexec commands took 3 second. Could use sudo and run those commands again. Just to check how long it takes, so that entering password time is not accounted.

alexanderadam · 2024-04-21T11:26:08Z

Kindly install this test.zip

I'd love to but how do I do that?

How did you manage to get time taken to execution the command in terminal? never new that trick.

Actually I'm not sure where this is coming from. I'm using Starship for my shell and I think that it is responsible for that output.

Also I saw pkexec commands took 3 second. Could use sudo and run those commands again. Just to check how long it takes, so that entering password time is not accounted.

The time was because of the password entering 😉

maniacx · 2024-04-22T00:06:51Z

Extract the test.zip. open the folder. Either right click on file install.sh and run as program. Or you can open terminal and type ./install.sh

alexanderadam · 2024-05-30T19:08:18Z

Hello @maniacx, I'm very sorry for the late response.

I think now it stopped working completely.
This happens after activating it:

Battery Health Charging: ---- argv = pkexec,/usr/local/bin/batteryhealthchargingctl-user,CHECKINSTALLATION,/home/user/.local/share/gnome-shell/extensions/[email protected]/resources,user ----
Battery Health Charging: ---- stdout = Battery Health Charging: checking rules !
Battery Health Charging: checking ctl !
Battery Health Charging: installation is up to date 
 ----
Battery Health Charging: ---- status = 0 ----
Battery Health Charging: ---- argv = pkexec,/usr/local/bin/batteryhealthchargingctl-user,DELL_RELATIVE_SMBIOS_BAT_READ ----
Battery Health Charging: ---- stdout = Charging mode: custom
Charging interval: (55, 60)
 ----
Battery Health Charging: ---- status = 0 ----
Battery Health Charging: ---- argv = pkexec,/usr/local/bin/batteryhealthchargingctl-user,DELL_RELATIVE_SMBIOS_BAT_WRITE,100,95 ----
Battery Health Charging: ---- stdout = Charging mode has been set to: custom
Custom charge interval has been set to (95, 100)
 ----
Battery Health Charging: ---- status = 0 ----
Battery Health Charging: ---- argv = pkexec,/usr/local/bin/batteryhealthchargingctl-user,DELL_RELATIVE_SMBIOS_BAT_READ ----
Battery Health Charging: ---- stdout = Charging mode: custom
Charging interval: (55, 60)
 ----
Battery Health Charging: ---- status = 0 ----
Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
_checkCompatibility@file:///home/user/.local/share/gnome-shell/extensions/[email protected]/lib/driver.js:108:30
IntializeDriver@file:///home/user/.local/share/gnome-shell/extensions/[email protected]/lib/driver.js:19:14
enable@file:///home/user/.local/share/gnome-shell/extensions/[email protected]/extension.js:30:32
_callExtensionEnable@resource:///org/gnome/shell/ui/extensionSystem.js:266:38
_onEnabledExtensionsChanged@resource:///org/gnome/shell/ui/extensionSystem.js:626:24
_loadExtensions/<@resource:///org/gnome/shell/ui/extensionSystem.js:731:18
createCheckedMethod/<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:730:46
enableExtension@resource:///org/gnome/shell/ui/extensionSystem.js:289:29
EnableExtension@resource:///org/gnome/shell/ui/shellDBus.js:453:38
_handleMethodCall@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:329:38
_wrapJSObject/<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:408:34
@resource:///org/gnome/shell/ui/init.js:21:20

maniacx · 2024-06-01T19:03:18Z

Install this and send me the logs again.
test2.zip

alexanderadam · 2024-06-02T18:27:35Z

here you are:

Battery Health Charging: ---- argv = pkexec,/usr/local/bin/batteryhealthchargingctl-user,CHECKINSTALLATION,/home/user/.local/share/gnome-shell/extensions/[email protected]/resources,user ----
Battery Health Charging: ---- stdout = Battery Health Charging: checking rules !
Battery Health Charging: checking ctl !
Battery Health Charging: installation is up to date 
 ----
Battery Health Charging: ---- status = 0 ----
Battery Health Charging: ---- argv = pkexec,/usr/local/bin/batteryhealthchargingctl-user,DELL_RELATIVE_SMBIOS_BAT_READ ----
Battery Health Charging: ---- stdout = Charging mode: custom
Charging interval: (55, 60)
 ----
Battery Health Charging: ---- status = 0 ----
Battery Health Charging: ---- output = Charging mode: custom
Charging interval: (55, 60)

Battery Health Charging: ---- filteredOutput = Charging mode custom
Charging interval 55 60
Battery Health Charging: ---- splitOutput = Charging mode custom,Charging interval 55 60
Battery Health Charging: ---- firstLine = Charging,mode,custom
Battery Health Charging: ---- modeRead = custom
Battery Health Charging: ---- secondLine = Charging,interval,55,60
Battery Health Charging: ---- parseInt(secondLine[2]) = 55
Battery Health Charging: ---- parseInt(secondLine[3]) = 60
Battery Health Charging: ---- argv = pkexec,/usr/local/bin/batteryhealthchargingctl-user,DELL_RELATIVE_SMBIOS_BAT_WRITE,100,95 ----
Battery Health Charging: ---- stdout = Charging mode has been set to: custom
Custom charge interval has been set to (95, 100)
 ----
Battery Health Charging: ---- status = 0 ----
Battery Health Charging: ---- argv = pkexec,/usr/local/bin/batteryhealthchargingctl-user,DELL_RELATIVE_SMBIOS_BAT_READ ----
Battery Health Charging: ---- stdout = Charging mode: custom
Charging interval: (55, 60)
 ----
Battery Health Charging: ---- status = 0 ----
Battery Health Charging: ---- output = Charging mode: custom
Charging interval: (55, 60)

Battery Health Charging: ---- filteredOutput = Charging mode custom
Charging interval 55 60
Battery Health Charging: ---- splitOutput = Charging mode custom,Charging interval 55 60
Battery Health Charging: ---- firstLine = Charging,mode,custom
Battery Health Charging: ---- modeRead = custom
Battery Health Charging: ---- secondLine = Charging,interval,55,60
Battery Health Charging: ---- parseInt(secondLine[2]) = 55
Battery Health Charging: ---- parseInt(secondLine[3]) = 60
Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
_checkCompatibility@file:///home/user/.local/share/gnome-shell/extensions/[email protected]/lib/driver.js:108:30
IntializeDriver@file:///home/user/.local/share/gnome-shell/extensions/[email protected]/lib/driver.js:19:14
enable@file:///home/user/.local/share/gnome-shell/extensions/[email protected]/extension.js:30:32
_callExtensionEnable@resource:///org/gnome/shell/ui/extensionSystem.js:266:38
_onEnabledExtensionsChanged@resource:///org/gnome/shell/ui/extensionSystem.js:626:24
_loadExtensions/<@resource:///org/gnome/shell/ui/extensionSystem.js:731:18
createCheckedMethod/<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:730:46
enableExtension@resource:///org/gnome/shell/ui/extensionSystem.js:289:29
EnableExtension@resource:///org/gnome/shell/ui/shellDBus.js:453:38
_handleMethodCall@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:329:38
_wrapJSObject/<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:408:34
@resource:///org/gnome/shell/ui/init.js:21:20

thank you so much for your help! 🥺

maniacx · 2024-06-03T01:31:32Z

There are two issues, that I see.

Is your charging threshold when applied it , the extension reads them to verify, when read it seems to be not updated.
After verification fails, (which happens in your case) it should give a notificaion.

Encountered an unexpected error. (Dell)

But the extension errors out.

Did you see this notification when you enable extension? or do you still see this.
Can you disable the extension and copy all these command, and paste in terminal. And send me the output.
Note: Do not copy one command at a time. Copy the whole list of command and paste in terminal

echo "---Read 1"
sudo smbios-battery-ctl --get-charging-cfg
echo "---Write 1 55 60"
sudo smbios-battery-ctl --set-charging-mode='custom'
sudo smbios-battery-ctl --set-custom-charge-interval=55 60
echo "---Read 2"
sudo smbios-battery-ctl --get-charging-cfg
echo "---Write 2 95 100"
sudo smbios-battery-ctl --set-charging-mode='custom'
sudo smbios-battery-ctl --set-custom-charge-interval=95 100
echo "---Read 3"
sudo smbios-battery-ctl --get-charging-cfg
echo "---Write 3 75 80"
sudo smbios-battery-ctl --set-charging-mode='custom'
sudo smbios-battery-ctl --set-custom-charge-interval=75 80
echo "---Read 4"
sudo smbios-battery-ctl --get-charging-cfg
echo "---Write 4 55 60"
sudo smbios-battery-ctl --set-charging-mode='custom'
sudo smbios-battery-ctl --set-custom-charge-interval=55 60
echo "---Read 5"
sudo smbios-battery-ctl --get-charging-cfg

maniacx · 2024-06-03T01:38:57Z

Also I think you may have already move to GNOME46. And the test2 I gave you was still an older version (Sorry I was lazy)
Anyways test this extension test3 (I have updated it). It may not fix the threshold issue, but it shoudl fix the error in extension that prevents it from sending notification and start the UI.
test3.zip
install it, and send me the logs. Let me know if you see the notification this time

alexanderadam · 2024-06-03T09:25:09Z

Did you see this notification when you enable extension? or do you still see this.

I'm seeing this:

Can you disable the extension and copy all these command, and paste in terminal. And send me the output.

Also I think you may have already move to GNOME46.

Exactly, it's Fedora Linux 40 with GNOME 46.

install it, and send me the logs. Let me know if you see the notification this time

I don't see the JS exception anymore but I'm still seeing the aforementioned notification in GNOME notification tray.
The output is this:

Battery Health Charging: ---- argv = pkexec,/usr/local/bin/batteryhealthchargingctl-user,CHECKINSTALLATION,/home/user/.local/share/gnome-shell/extensions/[email protected]/resources,user ----
Battery Health Charging: ---- stdout = Battery Health Charging: checking rules !
Battery Health Charging: checking ctl !
Battery Health Charging: installation is up to date 
 ----
Battery Health Charging: ---- status = 0 ----
Battery Health Charging: ---- argv = pkexec,/usr/local/bin/batteryhealthchargingctl-user,DELL_RELATIVE_SMBIOS_BAT_READ ----
Battery Health Charging: ---- stdout = Charging mode: custom
Charging interval: (55, 60)
 ----
Battery Health Charging: ---- status = 0 ----
Battery Health Charging: ---- output = Charging mode: custom
Charging interval: (55, 60)

Battery Health Charging: ---- filteredOutput = Charging mode custom
Charging interval 55 60
Battery Health Charging: ---- splitOutput = Charging mode custom,Charging interval 55 60
Battery Health Charging: ---- firstLine = Charging,mode,custom
Battery Health Charging: ---- modeRead = custom
Battery Health Charging: ---- secondLine = Charging,interval,55,60
Battery Health Charging: ---- parseInt(secondLine[2]) = 55
Battery Health Charging: ---- parseInt(secondLine[3]) = 60
Battery Health Charging: ---- argv = pkexec,/usr/local/bin/batteryhealthchargingctl-user,DELL_RELATIVE_SMBIOS_BAT_WRITE,100,95 ----
Battery Health Charging: ---- stdout = Charging mode has been set to: custom
Custom charge interval has been set to (95, 100)
 ----
Battery Health Charging: ---- status = 0 ----
Battery Health Charging: ---- argv = pkexec,/usr/local/bin/batteryhealthchargingctl-user,DELL_RELATIVE_SMBIOS_BAT_READ ----
Battery Health Charging: ---- stdout = Charging mode: custom
Charging interval: (55, 60)
 ----
Battery Health Charging: ---- status = 0 ----
Battery Health Charging: ---- output = Charging mode: custom
Charging interval: (55, 60)

Battery Health Charging: ---- filteredOutput = Charging mode custom
Charging interval 55 60
Battery Health Charging: ---- splitOutput = Charging mode custom,Charging interval 55 60
Battery Health Charging: ---- firstLine = Charging,mode,custom
Battery Health Charging: ---- modeRead = custom
Battery Health Charging: ---- secondLine = Charging,interval,55,60
Battery Health Charging: ---- parseInt(secondLine[2]) = 55
Battery Health Charging: ---- parseInt(secondLine[3]) = 60

maniacx · 2024-06-03T17:00:46Z

For some reason your libsmbios doesn't update your threshold.
As you can see, changing threshold to doesn't work even using commandline it still stays on 55-60

When I was adding support for Dell, I read that most older laptop works well with libsmbios, but newer laptop have issues with it, but they work with Dell command configure.

You could try installing Dell command configure (dcc)

And try changing threshold using Dell command configure. If changing threshold works using dcc, you can change setting in extension preference > device to use Dell

https://maniacx.github.io/Battery-Health-Charging/device-compatibility/dell

maniacx · 2024-06-03T17:59:08Z

Since I have fedora 40 too, i tried to install dcc even though my laptop is not dell.

First time for me installing rpm package locally. (I could be wrong or there might be a better way)
I downloaded the dcc package 4.11.0 for RHEL 9.0 (64-bit) from this website.
extract the package.

To install I used.

sudo rpm -i /home/$USER/Downloads/command-configure-4.11.0-3.el9.x86_64/srvadmin-hapi-9.5.0-4063.16816.el8.x86_64.rpm

and then

sudo rpm -i /home/$USER/Downloads/command-configure-4.11.0-3.el9.x86_64/command-configure-4.11.0-3.el9.x86_64.rpm

But for me runnning cctk doesnt do anything (May be because my laptop is not dell)

To Read threshold

sudo /opt/dell/dcc/cctk --PrimaryBattChargeCfg

To apply threshold

sudo /opt/dell/dcc/cctk --PrimaryBattChargeCfg=Custom:95-100

sudo /opt/dell/dcc/cctk --PrimaryBattChargeCfg=Custom:75-80

sudo /opt/dell/dcc/cctk --PrimaryBattChargeCfg=Custom:55-60

You can try to apply threshold and read threshold again and check if it reads back the applied threshold.

Incase. You want to uninstall dcc you can do it by

sudo rpm -ev srvadmin-hapi-9.5.0-4063.16816.el8.x86_64

sudo rpm -ev command-configure-4.11.0-3.el9.x86_64

Note: Install at your own risk.

alexanderadam · 2024-06-03T19:26:55Z

Okay, so for a short moment I thought that I found the culprit:
Dell also allows to set charging thresholds in the BIOS!
And apparently I did that and I forgot about it.
Now I set it back to "standard".

Setting the thresholds via terminal works now:

However, the Battery Health Charging extension still shows the very same notification with the error.

This is how its log looks like:

Battery Health Charging: ---- argv = pkexec,/usr/local/bin/batteryhealthchargingctl-user,CHECKINSTALLATION,/home/user/.local/share/gnome-shell/extensions/[email protected]/resources,user ----
Battery Health Charging: ---- stdout = Battery Health Charging: checking rules !
Battery Health Charging: checking ctl !
Battery Health Charging: installation is up to date 
 ----
Battery Health Charging: ---- status = 0 ----
Battery Health Charging: ---- argv = pkexec,/usr/local/bin/batteryhealthchargingctl-user,DELL_RELATIVE_SMBIOS_BAT_READ ----
Battery Health Charging: ---- stdout = Charging mode: standard
 ----
Battery Health Charging: ---- status = 0 ----
Battery Health Charging: ---- output = Charging mode: standard

Battery Health Charging: ---- filteredOutput = Charging mode standard
Battery Health Charging: ---- splitOutput = Charging mode standard
Battery Health Charging: ---- firstLine = Charging,mode,standard
Battery Health Charging: ---- modeRead = standard
Battery Health Charging: ---- argv = pkexec,/usr/local/bin/batteryhealthchargingctl-user,DELL_RELATIVE_SMBIOS_BAT_WRITE,100,95 ----
Battery Health Charging: ---- stdout = Charging mode has been set to: custom
Custom charge interval has been set to (95, 100)
 ----
Battery Health Charging: ---- status = 0 ----
Battery Health Charging: ---- argv = pkexec,/usr/local/bin/batteryhealthchargingctl-user,DELL_RELATIVE_SMBIOS_BAT_READ ----
Battery Health Charging: ---- stdout = Charging mode: standard
 ----
Battery Health Charging: ---- status = 0 ----
Battery Health Charging: ---- output = Charging mode: standard

Battery Health Charging: ---- filteredOutput = Charging mode standard
Battery Health Charging: ---- splitOutput = Charging mode standard
Battery Health Charging: ---- firstLine = Charging,mode,standard
Battery Health Charging: ---- modeRead = standard

The charging mode is now in standard:

A little code change for the extension could be that if the charging mode stays at custom (compare the charging mode of the first snippets to the one in this comment), and can't get over a certain threshold, then no error could be shown if the threshold is the same anyway (i.e. when it is set to 60 either way).
And if it can't get higher than a certain threshold a notification could be shown like "The Battery Health Extension can't set higher thresholds. It's appears that there's a custom threshold set in BIOS."

However, it doesn't explain why the extension still doesn't work although setting it via CLI works now.

maniacx · 2024-06-03T21:32:14Z

So when we change the threshold in libsmbios (or dell command center) it makes changes in the bios, that is how the laptop limits the battery threshold even though the laptop is powered off and not runnning linux/windows os. (Unless dell does it differently, I do not know for sure)

And as you can see, libsmbios is not working on your laptop.
Once you apply custom mode, it should switch from standard to custom, but in your case it doesnt change to custom and still reads standard*

Look at this post on the link below to check, how it behave on for other dell laptops with libsmbios working.
#7 (comment)
You can go through that thread(issue) to understand how it works for Dell laptops. That was request from dell user to support dell laptops.

alexanderadam · 2024-06-03T22:39:16Z

as you can see, libsmbios is not working on your laptop. Once you apply custom mode, it should switch from standard to custom, but in your case it doesnt change to custom and still reads standard*

Oh, I see. That was my fault. 🫣
But I finally found the culprit now: it's libsmbios issue 103.
libsmbios doesn't work when an admin password is set. 🙄

So this means that this is an 🐛 libsmbios bug.
The Battery Health extension could only give users a hint (i.e. "The Battery Health Extension can't set higher thresholds. Please check that you don't have an admin password set in BIOS and check dell/libsmbios#103 for more information.")

I'll close this issue now since I believe that other nothing else than a helpful message can be done here.

Thank you for your help! 🙏

maniacx · 2024-06-03T23:44:31Z

@alexanderadam
There is no-one fault here, we are all learning something new. It is difficult to know why libsmbios is not working (there could be several factors) and the sending a notification that admin passwords is set would be incorrect unless unless extension could confirm it.

Also dell command configure support changing threshold with admin password, and so does this extension.
Another users requested it, and I was able to implement it and user confirmed it is working.

Check the discussion here.
#54

Feel free to open this if you have any other issue.

alexanderadam mentioned this issue Jun 3, 2024

Question: what's the best way to determine whether the charging mode was set in BIOS and can't be overridden? dell/libsmbios#145

Closed

alexanderadam closed this as completed Jun 3, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

What to do when I'm getting `Encountered an unexpected error. (Dell)` #79

What to do when I'm getting `Encountered an unexpected error. (Dell)` #79

alexanderadam commented Feb 25, 2024 •

edited

Loading

maniacx commented Feb 25, 2024 •

edited

Loading

alexanderadam commented Feb 26, 2024

maniacx commented Feb 26, 2024 •

edited

Loading

alexanderadam commented Apr 21, 2024

maniacx commented Apr 22, 2024

alexanderadam commented May 30, 2024

maniacx commented Jun 1, 2024

alexanderadam commented Jun 2, 2024

maniacx commented Jun 3, 2024

maniacx commented Jun 3, 2024 •

edited

Loading

alexanderadam commented Jun 3, 2024 •

edited

Loading

maniacx commented Jun 3, 2024 •

edited

Loading

maniacx commented Jun 3, 2024 •

edited

Loading

alexanderadam commented Jun 3, 2024

maniacx commented Jun 3, 2024 •

edited

Loading

alexanderadam commented Jun 3, 2024

maniacx commented Jun 3, 2024 •

edited

Loading

What to do when I'm getting Encountered an unexpected error. (Dell) #79

What to do when I'm getting Encountered an unexpected error. (Dell) #79

Comments

alexanderadam commented Feb 25, 2024 • edited Loading

maniacx commented Feb 25, 2024 • edited Loading

Check for executable installed

Test if charging mode changes using command line.

alexanderadam commented Feb 26, 2024

maniacx commented Feb 26, 2024 • edited Loading

alexanderadam commented Apr 21, 2024

maniacx commented Apr 22, 2024

alexanderadam commented May 30, 2024

maniacx commented Jun 1, 2024

alexanderadam commented Jun 2, 2024

maniacx commented Jun 3, 2024

maniacx commented Jun 3, 2024 • edited Loading

alexanderadam commented Jun 3, 2024 • edited Loading

maniacx commented Jun 3, 2024 • edited Loading

maniacx commented Jun 3, 2024 • edited Loading

alexanderadam commented Jun 3, 2024

maniacx commented Jun 3, 2024 • edited Loading

alexanderadam commented Jun 3, 2024

maniacx commented Jun 3, 2024 • edited Loading

What to do when I'm getting `Encountered an unexpected error. (Dell)` #79

What to do when I'm getting `Encountered an unexpected error. (Dell)` #79

alexanderadam commented Feb 25, 2024 •

edited

Loading

maniacx commented Feb 25, 2024 •

edited

Loading

maniacx commented Feb 26, 2024 •

edited

Loading

maniacx commented Jun 3, 2024 •

edited

Loading

alexanderadam commented Jun 3, 2024 •

edited

Loading

maniacx commented Jun 3, 2024 •

edited

Loading

maniacx commented Jun 3, 2024 •

edited

Loading

maniacx commented Jun 3, 2024 •

edited

Loading

maniacx commented Jun 3, 2024 •

edited

Loading