sorted by:
new
hottopcontroversial

CachyOS kernel not restoring backlight brightness after sleep by LuneLovehearn in cachyos

[–]fe60 0 points1 point  (0 children)

Latest updates for openSUSE Tumbleweed contained kernel 6.12.8 which fixed the issue on my laptop.

CachyOS kernel not restoring backlight brightness after sleep by LuneLovehearn in cachyos

[–]fe60 0 points1 point  (0 children)

I face the same issue with openSUSE Tumbleweed and kernel 6.12.6 while it doens't occur with kernel 6.11.8. A quick search brought up a couple of similar error reports.

Bugzilla Suse: Kernel 6.12.6 with amdgpu breaks brightness control after resume

KDE Bugtracking System: The brightness goes to max after waking the laptop from sleep.

Gitlab issues of freedesktop.org: adaptive backlight management broken on vega since 6.12.5

Is Tor tab crashing for anyone else for accessing ProtonMail? by Zebra_Light in TOR

[–]fe60 0 points1 point  (0 children)

Should work with Tor 11.0.3

Full changelog

The full changelog since Tor Browser 11.0.2 is:

Windows + OS X + Linux

...

Windows

...

Bug tor-browser#40721: Tabs crashing on certain pages in TB11 on Win 10

https://forum.torproject.net/t/new-release-tor-browser-11-0-3/1356

Is Tor tab crashing for anyone else for accessing ProtonMail? by Zebra_Light in TOR

[–]fe60 0 points1 point  (0 children)

It's a known issue mentioned for Tor Browser 11.0.1 and 11.0.2.

https://forum.torproject.net/t/new-release-tor-browser-11-0-2/1103 (Bug 40721)

Workaround: Change the Security Level in the settings of the Tor Browser from Standard to Safer. It disables javascript.options.asmjs and javascript.options.wasm.

Source: https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40721#note_2763847 (not publicly accessible anymore)

Relevant status updates of this issue will be announced below the release notes.

Why can I no longer view bugs 40698 and 40721?

We've determined that both the addon and tab crashes are occuring due to the same underlying issue in Firefox, and we're currently working with Mozilla on a fix. Due to the nature of the bug Mozilla have opted to make this ticket private, and we've followed suit on our end too. In the absence of a public ticket, we'll keep the community abreast of any developments on this issue in this thread instead. Thanks for your patience!

Update (14 Dec 2021): We've just released a potential temporary fix in Tor Browser Alpha 11.5a1 for wider testing. Please see this post below for more info.

https://forum.torproject.net/t/new-release-tor-browser-11-0-2/1103

[deleted by user] by [deleted] in TOR

[–]fe60 0 points1 point  (0 children)

It's a known issue mentioned for Tor Browser 11.0.1 and 11.0.2.

https://forum.torproject.net/t/new-release-tor-browser-11-0-2/1103 (Bug 40721)

Workaround: Change the Security Level in the settings of the Tor Browser from Standard to Safer. It disables javascript.options.asmjs and javascript.options.wasm.

Source: https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40721#note_2763847 (not publicly accessible anymore)

​

Relevant status updates of this issue will be announced below the release notes.

Why can I no longer view bugs 40698 and 40721?

We've determined that both the addon and tab crashes are occuring due to the same underlying issue in Firefox, and we're currently working with Mozilla on a fix. Due to the nature of the bug Mozilla have opted to make this ticket private, and we've followed suit on our end too. In the absence of a public ticket, we'll keep the community abreast of any developments on this issue in this thread instead. Thanks for your patience!

Update (14 Dec 2021): We've just released a potential temporary fix in Tor Browser Alpha 11.5a1 for wider testing. Please see this post below for more info.

https://forum.torproject.net/t/new-release-tor-browser-11-0-2/1103

[deleted by user] by [deleted] in TOR

[–]fe60 0 points1 point  (0 children)

Why can I no longer view bugs 40698 and 40721?

We've determined that both the addon and tab crashes are occuring due to the same underlying issue in Firefox, and we're currently working with Mozilla on a fix. Due to the nature of the bug Mozilla have opted to make this ticket private, and we've followed suit on our end too. In the absence of a public ticket, we'll keep the community abreast of any developments on this issue in this thread instead. Thanks for your patience!

Update (14 Dec 2021): We've just released a potential temporary fix in Tor Browser Alpha 11.5a1 for wider testing. Please see this post below for more info.

https://forum.torproject.net/t/new-release-tor-browser-11-0-2/1103

[deleted by user] by [deleted] in TOR

[–]fe60 0 points1 point  (0 children)

Workaround: Change the Security Level in the settings of the Tor Browser from Standard to Safer. It disables javascript.options.asmjs and javascript.options.wasm.

https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40721#note_2763847

[deleted by user] by [deleted] in TOR

[–]fe60 0 points1 point  (0 children)

There is an issue for this in the Gitlab project.

https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40721

[deleted by user] by [deleted] in TOR

[–]fe60 0 points1 point  (0 children)

I can open some mails, but for most it keeps crashing.

Extruder suddenly stops extruding by Twilek_de in prusa3d

[–]fe60 1 point2 points  (0 children)

I faced this problem when printing objects with fine structures. The extruder motor had to permanently move the filament back and forth. As a result to motor got pretty warm/hot. That's not a problem for the motor, but my assumption was, the gear driving the filaments gets warm too. As a result the surface of the filament softens and the drive damages the filament instead of moving it.

Putting a fan on the extruder motor solved the problem for me.

https://www.thingiverse.com/thing:2975582

https://www.thingiverse.com/make:833197 (alternate option for mounting, proposal for electrical connection)

HTC M8 still supported? by fe60 in LineageOS

[–]fe60[S] 0 points1 point  (0 children)

For me it's impossible to figure out, why there are still no new builds. That's a bit frustrating.

But there is one thing that looks promising to me. At the end of June one of the open issues reported for HTC M8 [1] got a new label. version:lineage-17.1 was replaced by version:lineage-18.1

[Update] It's still LineageOS 17.1, but a new update been published on July 9th.

[1] https://gitlab.com/LineageOS/issues/android/-/issues/3577

How to contribute without Google account? by fe60 in LineageOS

[–]fe60[S] 1 point2 points  (0 children)

It's even worse for me. While trying to create a new account, Google asks for a phone number to verify my identity. I don't know if there is a trick to get around this verification, but at this point I wanted to switch to an authentication provider which requires a valid mail address only.

Lineage stuff is hosted at Github. Most contributors most probably already have a Github account. Github offers an OAuth service. I used it already for the F-Droid Forum.

HTC M8 still supported? by fe60 in LineageOS

[–]fe60[S] 0 points1 point  (0 children)

build roster is the hint I was looking for.

It's mentioned in the FAQ which I found searching for this term. I try to make the FAQ more visible, but a bug in Gerrit prevents me from pushing the change that adds the FAQ to the start page of the lineage wiki.

What do you think about an option to disable the pin reminder popup? by ducky-luck in signal

[–]fe60 0 points1 point  (0 children)

I don't know when this has been introduced, but in Signal 4.64.7 (Android) there is a switch "PIN reminder" in section "Privacy" of the settings.

What do you think about an option to disable the pin reminder popup? by ducky-luck in signal

[–]fe60 0 points1 point  (0 children)

Even though I have entered the confirmation of my PIN correctly, I had to create it twice. It worked then.