djtech @ djtech @lemmy.world

Experience programmer.

---

Read more

Posts

17

Comments

58

Joined

2 yr. ago

Moderating

---

The repository is https://github.com/djtech-dev/reblued but at the moment is pretty much empty, just the project's skeleton, license, README and disussions for collaborators.

Thanks for your reply; i won't work with firmware-level aspects of the stack, as my plan is to write the userspace daemon, while keeping the kernel-levels modules identical and to communicate to them via HCI sockets, as they are implemented by Linux and with them I can talk directly to the bluetooth controllers.

I'll check out Android's project and double-check for security vulnerabilities in older version of the protocols tho, so thank you again for replying.

Fork the feature one, get the diff of the commit that patches the bug and apply the diff to your fork.

Now compile and test.

Why not?

A quick research tells me that there aren't patches for other emulators, but the protocol seems well described, so making those patches is possible. I could also take a look at Alacritty source code and deicide if I could make this project work.

For rendering high quality images in the terminal, check out the Kitty graphical protocol. I don't know if they are any python libraries to use, but I think that they are. P.S. This seems to work well https://stackoverflow.com/questions/58138638/how-to-display-graphical-images-in-kitty-terminal-using-python

So... emacs?

mhhhhhhhhhh

The project is trolling fs

What do you mean by AppImage permissions? A sandboxing feature like "access only those directories, those /dev devices, ..."

EDIT: obviously this isn't just for AppImage, but I tested it with AppImage and it work well. Another tip: if you want a package manager for managing AppImage installations try zap (https://github.com/srevinsaju/zap)

In that case, take a look at bubblejail. (https://github.com/igo95862/bubblejail)

Before the "systemctl" command: try removing the GPU and booting it up without the GPU If it works, you can skip the "systemctl" commands

Bro really spamming ads on Lemmy.

Run "journalctl --lines 200" and send photos of output.

NOTE: This is all of the logging of the computer, and it's long (that command select the last 200 entries), so you might have to scroll down using the PageDown key (or arrow down) in order make the photos of everything

The Shell where you typed "systemctl reboot" and "exit".

If you are running KDE neon, try "apt update" and "apt upgrade". If It doesn't work do "sudo apt update" and "sudo apt upgrade"

Try updating your DM / your entire system from the emergency mode.

Yes, but I can still play steam, any Valve game and atm any Linux steam game on X11.

I don't hate Wayland as a project, I just don't like Wayland as it current state. Give me better stability, better support with multiple monitors and a compositor with more customization, and I'll be happy.

But, in my opinion, Wayland is by design opinionated. Some ideas are good, such as the security model, some are both good and bad, such as the Compositor VS Server+WM debate (both good systems in my opinion), some are just bad (no unified screen management option; obviously there are LOTS of protocol extension, but not all are supporting everywhere)

So, imo, WayLand just needs a stable, (really) customizable Compositor with all useful extensions and designed to put other components together; I'm still on my X11+awesomewm+rofi+polybar, and I want a customizable, stable and module approach on Wayland.

Yes, but I can still play steam, any Valve game and atm any Linux steam game on X11.

I don't hate Wayland as a project, I just don't like Wayland as it current state. Give me better stability, better support with multiple monitors and a compositor with more customization, and I'll be happy.

But, in my opinion, Wayland is by design opinionated. Some ideas are good, such as the security model, some are both good and bad, such as the Compositor VS Server+WM debate (both good systems in my opinion), some are just bad (no unified screen management option; obviously there are LOTS of protocol extension, but not all are supporting everywhere)

So, imo, WayLand just needs a stable, (really) customizable Compositor with all useful extensions and designed to put other components together; I'm still on my X11+awesomewm+rofi+polybar, and I want a customizable, stable and module approach on Wayland.

TIL

But if it has all those limitations, why would anyone buy it?

Been some times since I installed Windows, but Calamares is a great tool