Have to report some strange behavior on Plasma. Apparently, at least on my machine, sddm can't start a plasma session, either Wayland or X11. Running manually dbus-run-session startplasma-wayland
from tty1 instead works.
Sync Updates for Week 32, 2023
- Edited
xjdwc
Ahhhhhhhhhhh Cooool
I know couple other users that will be on cloud nine if there bluetooth works
after trying to get it to work.
I just wanted comment on how the creation of this thread really helps people out and gives them
some kind of outlook about things and a sense of moving foward.
And thank the dev for creating it (It Appears to be a big Plus)
Merci
awsome, bluetooth is working fine this time love it.
- Edited
What a lovely and lively distro!
Using Solus and following this forum make using Solus feel personal and like being part of something, not like most of the other distros. I like it
We did a quick hotfix to fix the reported issue with QT applications (Virtualbox, VLC, qBittorrent etc) not appearing for 25 after launching them on Budgie and GNOME desktops.
If you had this issue please update again and reboot your computer.
I have issues with evince and leafpad.
The evince issue I observed already before this weeks sync, and it is persistent. With some pdf documents, evince starts right away, but then needs up to 10 seconds to load the document, while other pdf documents load right away.
Leafpad needs up to 30 seconds to start.
brent As of the evince issue, this might simply be a pdf file integrity issue. I have several pdf files from different sources that lead to evince needing at least 10 seconds to load them. Some of them I checked for integrity here.
With the following result:
Compliance pdfa-1a
Result Document does not conform to PDF/A.
Details
Validating file "Anlage-0.pdf" for conformance level pdfa-1a
The schema description for namespace 'pdfx:' (http://ns.adobe.com/pdfx/1.3/) is missing.
The key StructTreeRoot is required but missing.
The document does not conform to the requested standard.
The document's meta data is either missing or inconsistent or corrupt.
The document doesn't provide appropriate logical structure information.
The document does not conform to the PDF/A-1a standard.
So, evince issue might therefore only affect currupted PDF's.
Zathura by the way opens theses files without a problem.
Sebastian I'd check to see if there's an upstream issue for that
- Edited
@Sebastian thanks for sharing all that. no way would I use that site though. they get your documents and ip address, document metadata, and probably more; that's TMI for me personally.
the valuable output sorta kinda reminded me of using adobe pitstop, in the day.
I wonder if there is a standalone pdf foss app that measures pdf integrity? another way to check is to print the pdf to postscript but you'd still need preflight tools to get that data (maybe scribus?) but convoluted compared to just doing it now. all the other services they provide at that website I can do via gimp
, office suite,scribus
, pdfunite
..
ps--this is the second time I've seen zathura mentioned in a week. maybe will try it. edit/format
Lol! I was thinking "Also sprach Zarathustra" was becoming more popular:
brent I wonder if there is a standalone pdf foss app that measures pdf integrity?
@Sebastian qpdf
in terminal. qpdf --check /home/documents/your.pdf
heckuva an output. --check
was just one of many arguments.
just passing it on. I/we are off topic enough as it is.
95 updates on my Solus Budgie.
Flawless. οΈ
No boot after the update. Might be time for a rebuild.
- Edited
anthonydouwes feel free to hop on Matrix for interactive debugging help.
We're trying to track down the cause of failed boots like this.
elfprince a fellow solarized dark aficionado I see