Yaru Bark Gtk theme, custom Yaru Sardi Bark icon theme and custom Yaru Plank theme
Yaru Bark with custom Plank theme
@jfaulk1230 would you have your live-build files available? I did not see it on Peppermint's Codeberg. Also a suggestion/request ---> could the additional Pep Repos be added for things like xfdashboard? Thanks
@jfaulk1230 would you have your live-build files available? I did not see it on Peppermint's Codeberg. Also a suggestion/request ---> could the additional Pep Repos be added for things like xfce4-panel-profiles and xfdashboard? Thanks
Did anyone get back with you on the Xfce forums about this issue?
It appears options are also locked in the Settings Editor as well. Perhaps a permissions issue?
Check this link for more info about Bullseye: https://wiki.debian.org/LTS
![]https://imgur.com/dXALCgm.png()
https://imgur.com/dXALCgm.png
The default application shortcut key for Xfce Whisker Menu is the Left Windows/Super Key. This interferes with any other application shortcuts that use the super key, as it opens whatever you selected and the Whisker menu at the same time as it stands at the moment. Also, this might cause confusion when a user first presses the super key before the next selected key. Here is an example: https://imgur.com/4Pu5Ena.png Xfce display settings is set by default to Super + P, so those 2 keys pressed brings...
The default application shortcut key for Xfce Whisker Menu is the Left Windows/Super Key. This interferes with any other application shortcuts that use the super key, as it opens whatever you selected and the Whisker menu at the same time as it stands at the moment. Also, this might cause confusion when a user first presses the super key before the next selected key. Here is an example: https://imgur.com/4Pu5Ena.png Maybe Whisker Menu can be linked to something like Super + Spacebar, etc.?
The default application shortcut key for Xfce Whisker Menu is the Left Windows/Super Key. This interferes with any other application shortcuts that use the super key, as it opens whatever you selected and the Whisker menu at the same time as it stands at the moment. Also, this might cause confusion when a user first presses the super key before the next selected key. Here is an example: https://imgur.com/4Pu5Ena.png Maybe Whisker Menu can be linked to something like Super + Spacebar, etc.?
Note Clicked link to Codeburg in Welcome Screen, then selected Bubbles repo. When there, scrolling did not work, and reloading the screen did not correct it. J/K and arrow keys still work as expected
Note Clicked link to Codeburg in Welcome Screen, then selected Bubbles repo. When there, scrolling did not work, and reloading the screen did not correct it
I noticed that mouse scrolling didn't seem to work when opening links from the Peppermint Welcome Screen, but after reloading the page it started working. Maybe a lua module isn't being loaded at first launch? I added a ticket, hopefully I did it correctly.
I noticed that mouse scrolling didn't seem to work when opening links from the Peppermint Welcome Screen, but after reloading the page it started working. Maybe a lua module isn't being loaded at first launch? I added a ticket, hopefully I did it correctly
I noticed that mouse scrolling didn't seem to work when opening links from the Peppermint Welcome Screen, but after reloading the page it started working. Maybe a lua module isn't being loaded at first launch?
May have flagged this to wrong Milestone. Resubmit if incorrect
Luakit Mouse Scrolling
Maybe on the next iso build have the clock match the Cantarell Regular 11 font? It is extremely small to read, even on a 24 inch monitor. Also noticed there is a duplicate listing of "Cantarell Regular" as well as others in Xfce Appearance. One does apply the right font, the other does not.
Maybe on the next iso build have the clock match the Cantarell Regular 11 font? It is extremely small to read, even on a 24 inch monitor. Also noticed there is a duplicate listing of "Cantarell Regular" in Xfce Appearance
Could this be a result of the new "non-free-firmware" that is present on Debian 12?
https://packages.debian.org/sid/nvidia-legacy-340xx-driver Info shows it works up kernel 5.17. However, from a person that has an old laptop with a Nvidia GPU slightly older than yours, I would see if the legacy-304 was an option if you continue to have issues. Even though all documentation for my GPU says to use 340, it crashes and kills the system to an unusable state. Downgrading to 304 driver made it smooth as silk. I had to make a custom driver build on Ubuntu 18.04 to make it work. Just note...
https://packages.debian.org/sid/nvidia-legacy-340xx-driver Info shows it works up kernel 5.17. However, from a person that has an old laptop with a Nvidia GPU slightly older than yours, I would see if the legacy-304 was an option if you continue to have issues. Even though all documentation for my GPU says to use 340, it crashes and kills the system to an unusable state. Downgrading to 304 driver made it smooth as silk. I had to make a custom driver build on Ubuntu 18.04 to make it work. Just note...
https://packages.debian.org/sid/nvidia-legacy-340xx-driver Info shows it works up kernel 5.17. However, from a person that has an old laptop with a Nvidia GPU slightly older than yours, I would see if the legacy-304 was an option if you continue to have issues. Even though all documentation for my GPU says to use 340, it crashes and kills the system to an unusable state. Downgrading to 304 driver made it smooth as silk.
If I recall correctly, Ubuntu used Upstart before SystemD. I hear great things about OpenRC, being based on sysvinit, but more added features and more powerful.
No Trinity Peter? lol