Opened 2 years ago
Closed 8 months ago
#65974 closed defect (fixed)
gtkwave 3.3.111: Can't add signals
| Reported by: | DanielO (Daniel O'Connor) | Owned by: | mascguy (Christopher Nielsen) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.8.1 |
| Keywords: | Cc: | ||
| Port: | gtkwave |
Description
The gtkwave port runs but I am unable to add signals to the display. Whenever I click on an entry in the SST pane it prints a log message:
(gtkwave:48181): Gdk-WARNING **: 13:30:34.458: Source with depth 1 unsupported
This appears to be an OSX/GTK error: https://gitlab.gnome.org/GNOME/gtk/-/blob/gtk-2-24/gdk/quartz/gdkdrawable-quartz.c#L468
The pre-built version (https://sourceforge.net/projects/gtkwave/files/gtkwave-3.3.107-osx-app/) doesn't have this problem (but not sure what version of GTK etc it's built against)
I have attached a vcd file to the ticket as a test case - simply open it and click on the SST pane to see the error.
Attachments (1)
Change History (9)
Changed 2 years ago by DanielO (Daniel O'Connor)
| Attachment: | up_counter.vcd added |
|---|
comment:1 Changed 17 months ago by langly (Kenneth Ostby)
I have the same problem myself. I updated the gtkwave in ports to 3.3.115, however it has not solved this particular problem. I tried getting it to build using gtk3, but there seems to be some issues with their makefiles on OSX.
comment:2 Changed 17 months ago by mascguy (Christopher Nielsen)
| Owner: | set to mascguy |
|---|---|
| Status: | new → assigned |
| Version: | → 2.8.1 |
I'll take a look at upstream's issues for gtk2, to see if there's a patch available.
comment:3 Changed 17 months ago by mascguy (Christopher Nielsen)
It looks like there's a proposed upstream patch, which was never merged:
- https://gitlab.gnome.org/GNOME/gtk/-/issues/580
- https://gitlab.gnome.org/GNOME/gtk/uploads/2a194d81de8e8346a81816870264b3bf/gdkimage.patch
The patch does work verbatim, without any further changes. So that's something we can potentially try, at least via gtk2-devel.
I need to do some testing with it first, though. More to follow, hopefully over the next day or two.
comment:4 Changed 17 months ago by Christopher Nielsen <mascguy@…>
comment:5 Changed 17 months ago by Christopher Nielsen <mascguy@…>
comment:6 Changed 17 months ago by mascguy (Christopher Nielsen)
Replying to mascguy:
It looks like there's a proposed upstream patch, which was never merged:
- https://gitlab.gnome.org/GNOME/gtk/-/issues/580
- https://gitlab.gnome.org/GNOME/gtk/uploads/2a194d81de8e8346a81816870264b3bf/gdkimage.patch
The patch does work verbatim, without any further changes. So that's something we can potentially try, at least via
gtk2-devel.I need to do some testing with it first, though. More to follow, hopefully over the next day or two.
Support for this was just added to gtk2-devel, via new variant bit_depth_1. (Disabled by default, since it's considered experimental.)
If you want to try it, wait at least three hours, then re-sync your ports tree via sudo port selfupdate.
Once that's done, you'll need to do the following:
$ sudo port -f deactivate gtk2 $ sudo port -N install gtk2-devel +quartz +bit_depth_1
And would love to hear back, in terms of whether it fixes the issue!
comment:7 follow-up: 8 Changed 8 months ago by langly (Kenneth Ostby)
This seems to have gone away with the version I just got merged into main. https://github.com/macports/macports-ports/pull/22128 . Should be possible to close this now.
comment:8 Changed 8 months ago by mascguy (Christopher Nielsen)
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Replying to langly:
This seems to have gone away with the version I just got merged into main. https://github.com/macports/macports-ports/pull/22128. Should be possible to close this now.
That's great news, thanks for the heads-up!
VCD file to show problem