breezy-desktop
breezy-desktop copied to clipboard
wheaney
Issues in 2.0.0-beta
after install, I ran into an issue that PyGObject wasn't installed; resolved that with pip install PyGObject (I was surprised it was using system python instead of maintaining it's own virtualenv; but idk what the actual best practice is when shipping python to end users so 🤷🏻)
But then I ran into SyntaxError: f-string: unmatched '(' on
breezydesktop/connecteddevice.py", line 265
self.focused_display_distance_label.set_markup(f"{_("Focused display")}: <b>{distance}</b>")
and
breezydesktop/connecteddevice.py", line 271
self.all_displays_distance_label.set_markup(f"{_("All displays")}: <b>{distance}</b>")
Resolved by updating line 265 to read
self.focused_display_distance_label.set_markup(f"{_('Focused display')}: <b>{distance}</b>")
and line 271
self.all_displays_distance_label.set_markup(f"{_('All displays')}: <b>{distance}</b>")
respectively. I forget off the top of my head if they allow nesting quotes in f-strings in more recent versions of python, I vaguely remember that discussion; but either way, it's not supported in 3.10 which is the system python 😂
After all that, I can get breezydesktop working; but then I enable xr mode and... nothing happens 😕
Tried resetting the driver:
2025-03-06 17:33:57.085 Retrying driver connection in 1 second
2025-03-06 17:33:58.231 Project version: 2.0.0
2025-03-06 17:33:58.231 Driver has been re-enabled
2025-03-06 17:33:58.231 Output mode has been changed to 'external_only'
2025-03-06 17:33:58.232 Using hardware id 948c5ec2679a0a5b85fc95776669513f32c017a275a2ce58e9053406dfe71fca
2025-03-06 17:33:58.233 Feature smooth_follow granted.
2025-03-06 17:33:58.233 Feature sbs granted.
2025-03-06 17:33:58.233 Feature productivity_basic granted.
2025-03-06 17:33:58.233 Starting up XR driver
2025-03-06 17:33:58.233 Waiting for glasses
2025-03-06 17:33:58.233 Found device with vendor ID 0x35ca and product ID 0x101d
2025-03-06 17:33:58.233 Found device with vendor ID 0x35ca and product ID 0x101d
2025-03-06 17:34:00.254 Device connected, redirecting input to external_only...
2025-03-06 17:34:00.254 Waiting on device calibration
2025-03-06 17:34:00.255 Feature smooth_follow granted.
2025-03-06 17:34:00.255 Feature sbs granted.
2025-03-06 17:34:00.255 Feature productivity_basic granted.
2025-03-06 17:34:02.004 Device calibration complete
2025-03-06 17:34:02.008 Centering screen
2025-03-06 17:34:05.868 Breezy desktop has been enabled
2025-03-06 17:36:02.666 Breezy desktop has been disabled
2025-03-06 17:36:04.005 Breezy desktop has been enabled
2025-03-06 17:36:59.610 Breezy desktop has been disabled
2025-03-06 17:37:01.619 Breezy desktop has been enabled
2025-03-06 17:37:28.219 Breezy Desktop follow has been enabled
2025-03-06 17:37:29.493 Breezy Desktop follow has been disabled
2025-03-06 17:39:20.044 Breezy desktop has been disabled
2025-03-06 17:39:22.634 Breezy desktop has been enabled
Looks fine?
journalctl output also looks... fine?
Mar 06 17:43:57 tinybook systemd[1034]: xr-driver.service: Consumed 19.394s CPU time.
Mar 06 17:43:57 tinybook systemd[1034]: xr-driver.service: Scheduled restart job, restart counter is at 13.
Mar 06 17:43:57 tinybook systemd[1034]: Stopped XR user-space driver.
Mar 06 17:43:57 tinybook systemd[1034]: xr-driver.service: Consumed 19.394s CPU time.
Mar 06 17:43:57 tinybook systemd[1034]: Started XR user-space driver.
Not seeing any logs coming from the breezydesktop guil app itself;
Going to try rolling back to a previous build
Interesting situation regarding Python, your system install must be pickier than the versions we've tested on since nobody else has run into that. I'll have to follow-up on your question regarding how to ship a python app to end-users, I've gotten away with this approach for a while but clearly it can be problematic.
If you have a chance to go back to the beta version, I'd like to see your GJS logs too: ~/.local/state/breezy_gnome/logs/gjs/[today].log
I mean; I've been developing python for like, 15 years now? You'd think I would actually know a good way to ship an app to end-users; but 🤷🏻 It doesn't really come up that much in web-dev. I should probably learn.
Anywoo; attached my GJS logs (thanks for the pointer to them!)
That log is very helpful, thanks. Just taking a look at your GNOME info:
Gnome-Shell 42.9 / gjs 1.72.4 (17204) / x11
First thing to note: I don't think virtual displays will work if you're not on Wayland. The README says it but I will probably end up putting some checks in the setup script.
I'm seeing this error in the log:
Object is of type Cogl.Object - cannot convert to CoglTexture
Must be something specific to the GNOME 42 API, and you're the first one to test on that version. I'll follow up!
READMEs; What a concept!
I should really actually; you know; read them more often 😂
BTW; I think the instruction in the current readme about using --tag legacy might be wrong, since there don't seem to be any builds tagged with legacy. --tag v1.1.7 seems to work alright, though.
v2.0.1-beta has fixes for the issues identified in this thread, though I wouldn't be shocked if resolving that error exposes another. Can you try it out?
Under x11 it actually runs! and XR effect works with the single display; albiet with a fair amount of scuff as much of the UI is built around maintaining multiple screens.
Under wayland it's pretty awesome! Multiple screens work well; and that annoying flash-of-underlying-cursor that I occasionally see is gone. Once I got the hang of the settings, its really cool! I do miss screen curvature more than I think I would.
Clicking "turn this off" under the screen sharing when I have multi monitors enabled causes a pretty funny crash that I don't have time to investigate, but I can look into it later file:///home/george/Pictures/Screenshots/Screenshot%20from%202025-03-07%2009-53-10.png
I am going to play around with this for a while while I work today; but I think that I am likely going to stick to the legacy version for a bit; since there is a fair amount about my personal workflows that I haven't adapted to Wayland yet; but my goodness; this is really awesome!
I had a GNOME install that was crashing when displays were disabled and an
OS update fixed it (like pulled in a patch fix that was needed). If it
continues can you send me the GJS log and also journalctl (e.g. journalctl --since "5 minutes ago" will often capture the last crash).
On Fri, Mar 7, 2025, 7:05 AM George Griffin @.***> wrote:
Under x11 it actually runs! and XR effect works with the single display; albiet with a fair amount of scuff as much of the UI is built around maintaining multiple screens.
Under wayland it's pretty awesome! Multiple screens work well; and that annoying flash-of-underlying-cursor that I occasionally see is gone. Once I got the hang of the settings, its really cool! I do miss screen curvature more than I think I would.
Clicking "turn this off" under the screen sharing when I have multi monitors enabled causes a pretty funny crash that I don't have time to investigate, but I can look into it later
file:///home/george/Pictures/Screenshots/Screenshot%20from%202025-03-07%2009-53-10.png
I am going to play around with this for a while while I work today; but I think that I am likely going to stick to the legacy version for a bit; since there is a fair amount about my personal workflows that I haven't adapted to Wayland yet; but my goodness; this is really awesome!
— Reply to this email directly, view it on GitHub https://github.com/wheaney/breezy-desktop/issues/90#issuecomment-2706678097, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKDDTBIKMF5WUBLRYQTQ2M32TGYSFAVCNFSM6AAAAABYP3FX7WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMBWGY3TQMBZG4 . You are receiving this because you commented.Message ID: @.***> [image: rgegriff]rgegriff left a comment (wheaney/breezy-desktop#90) https://github.com/wheaney/breezy-desktop/issues/90#issuecomment-2706678097
Under x11 it actually runs! and XR effect works with the single display; albiet with a fair amount of scuff as much of the UI is built around maintaining multiple screens.
Under wayland it's pretty awesome! Multiple screens work well; and that annoying flash-of-underlying-cursor that I occasionally see is gone. Once I got the hang of the settings, its really cool! I do miss screen curvature more than I think I would.
Clicking "turn this off" under the screen sharing when I have multi monitors enabled causes a pretty funny crash that I don't have time to investigate, but I can look into it later
file:///home/george/Pictures/Screenshots/Screenshot%20from%202025-03-07%2009-53-10.png
I am going to play around with this for a while while I work today; but I think that I am likely going to stick to the legacy version for a bit; since there is a fair amount about my personal workflows that I haven't adapted to Wayland yet; but my goodness; this is really awesome!
— Reply to this email directly, view it on GitHub https://github.com/wheaney/breezy-desktop/issues/90#issuecomment-2706678097, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKDDTBIKMF5WUBLRYQTQ2M32TGYSFAVCNFSM6AAAAABYP3FX7WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMBWGY3TQMBZG4 . You are receiving this because you commented.Message ID: @.***>