Bug#1020460: xdaliclock: New version ignores Xresource settings and can't be made transparent

2023-02-26 Thread ydld1pw02
Any progress on making version xdaliclock 2.44 available as a separate package?



Bug#1020460: xdaliclock: New version ignores Xresource settings and can't be made transparent

2022-11-27 Thread Larry Doolittle
I can confirm that the xdaliclock 2.46 in Bookworm/testing works nothing like
historical copies of the program.  In my case, I have an ancient incantation
buried in my .xsession file
/usr/bin/xdaliclock -noseconds -nocycle -builtin1 -bg steelblue -fg black -geom 
-0-0
and the new xdaliclock understands none of those options.

Also, five minutes of digging revealed no documentation that any of those
features are supported in some other way.

Like Stefan, I reverted to the 2.44 binary that's part of Bullseye,
and that works fine.  I also confirmed that the xdaliclock_2.44+debian-2
source package builds and runs without issue in a Bookworm environment.

If we keep xdaliclock 2.46 in Debian despite Jamie's hostility,
can we at least give it a new name, and keep xdaliclock as
the traditional (2.44) version?

  - Larry

P.S. Can someone fix the Version tag here?  It seems to have been
confused by Stefan reverting to 2.44 before filing the bug report.
This bug actually applies to 2.46 but not 2.44.



Bug#1020460: xdaliclock: New version ignores Xresource settings and can't be made transparent

2022-09-26 Thread Jamie Zawinski
Congrats, you are well on your way to understanding that Linux is a trash fire 
all the way down!

On Sep 26, 2022, at 11:07 AM, Stefan Monnier  wrote:
> 
> Oh, it's worse: I installed `picom` which made the opacity slider work,
> but that affects the whole window, whereas I only want the background to
> be transparent.
> 
> Along the way I noticed another problem with the opacity compared to the
> old code that relied on the "Shape" X11 extension: even if I can use the
> "opacity" setting to let me see my windows underneath the clock,
> clicking in the background of the clock sends the even to the clock
> rather than to the underlying window  :-(
> 
> 
>Stefan



Bug#1020460: xdaliclock: New version ignores Xresource settings and can't be made transparent

2022-09-26 Thread Jamie Zawinski
Less snarkily: none of these things can or will be fixed. Adapting xdaliclock 
to more modern toolkits in order to have fully scalable antialiasing and a real 
GUI for preferences has some other side effects.

If you want to party like it's 1991, run the code from 1991. It still exists.



Bug#1020460: xdaliclock: New version ignores Xresource settings and can't be made transparent

2022-09-26 Thread Stefan Monnier
Oh, it's worse: I installed `picom` which made the opacity slider work,
but that affects the whole window, whereas I only want the background to
be transparent.

Along the way I noticed another problem with the opacity compared to the
old code that relied on the "Shape" X11 extension: even if I can use the
"opacity" setting to let me see my windows underneath the clock,
clicking in the background of the clock sends the even to the clock
rather than to the underlying window  :-(


Stefan



Bug#1020460: xdaliclock: New version ignores Xresource settings and can't be made transparent

2022-09-21 Thread Stefan Monnier
Package: xdaliclock
Version: 2.44+debian-2
Severity: normal

The version of xdaliclock in Debian testing seems to be quite different from
the version I've been running for the last ... 20 years(?).  The most obvious
difference is that it disregards my Xresource settings.

But more importantly, I was running it with `XDaliClock.transparent: true`,
but with the new code I can't seem to make it transparent.
I tried to play with the opacity slider in the GUI config, but it has no effect
on my system.  That might be due to my window-manager (ctwm) but the
transparency was the main feature which made me use this program, but this
failure makes it pointless.

I reverted to the xdaliclock in Debian stable for now.  Could there be two
builds of `xdaliclock` available, a bit like the `emacs-lucid` and `emacs-gtk`
alternatives?


Stefan


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'stable-security'), (100, 'stable')
Architecture: i386 (x86_64)
Foreign Architectures: amd64

Kernel: Linux 5.19.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_CH.UTF-8, LC_CTYPE=fr_CH.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages xdaliclock depends on:
ii  libc6 2.34-7
ii  libx11-6  2:1.8.1-2
ii  libxext6  2:1.3.4-1
ii  libxt61:1.2.1-1

xdaliclock recommends no packages.

xdaliclock suggests no packages.

-- no debconf information