Dear Maintainer,

   * What led up to the situation?

apt dist-upgrade


   * What was the outcome of this action?

Reading changelogs... Done
(Reading database ... 692589 files and directories currently installed.)
Preparing to unpack .../lxqt-panel_2.3.2-1_amd64.deb ...
Unpacking lxqt-panel (2.3.2-1) over (2.2.2-1+b1) ...
dpkg: error processing archive /var/cache/apt/archives/lxqt-
panel_2.3.2-1_amd64.deb (--unpack):
 trying to overwrite '/etc/xdg/lxqt/panel.conf', which is also in
package lxqt- branding-debian (0.14.0.7)
Errors were encountered while processing:
 /var/cache/apt/archives/lxqt-panel_2.3.2-1_amd64.deb
needrestart is being skipped since dpkg has failed
Error: Sub-process /usr/bin/dpkg returned an error code (1)

Dear ChangZhuo,

Any plan to for this bug?

I would suggest to merge the upstream configurations into
lxqt-branding-debian package to avoid the file conflicts and also keep
the LXQt desktop Debian branding not broken in the same time.

Best regards,

Hi,

Ping. This package is a key package. Please attend to issues like this.

Paul

We believe that the bug you reported is fixed in the latest version of
lxqt-panel, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1124685@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
ChangZhuo Chen (陳昌倬) <czchen@debian.org> (supplier of updated lxqt-panel package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Sat, 28 Mar 2026 22:44:03 +0800
Source: lxqt-panel
Architecture: source
Version: 2.3.2-2
Distribution: unstable
Urgency: medium
Maintainer: LXQt Packaging Team <team+lxqt@tracker.debian.org>
Changed-By: ChangZhuo Chen (陳昌倬) <czchen@debian.org>
Closes: 1124685
Changes:
 lxqt-panel (2.3.2-2) unstable; urgency=medium
 .
   * d/control: Fix conflict between lxqt-branding-debian (Closes: #1124685)
Checksums-Sha1:
 0a0f8ed70f462f5767f4433c8960088b5b346760 2955 lxqt-panel_2.3.2-2.dsc
 3c2b87af59dfb7f273fe08326d223eb587d9cd8a 11632 lxqt-panel_2.3.2-2.debian.tar.xz
 03ddabb5022ffc02d75abb1220822bb62cd58e40 19079 lxqt-panel_2.3.2-2_amd64.buildinfo
Checksums-Sha256:
 6f430efa909b202d8ec6d9b394c1b2d64dc5bd1197e7a095deb7b1eab1b7ed5c 2955 lxqt-panel_2.3.2-2.dsc
 ef068aae17aa6297fd37ac9384b7da9489af67ebf05491134bcb26232f43c145 11632 lxqt-panel_2.3.2-2.debian.tar.xz
 983f08e31f380363bb52b5b635f1691d519399b1a4eb924d554034d224581854 19079 lxqt-panel_2.3.2-2_amd64.buildinfo
Files:
 a2223506ab5f8b189ed5d49bd21be2a6 2955 x11 optional lxqt-panel_2.3.2-2.dsc
 98e8c5c439da43545cbf012ae7d19deb 11632 x11 optional lxqt-panel_2.3.2-2.debian.tar.xz
 db68d610bcc861eab5b6381c70a1fb5d 19079 x11 optional lxqt-panel_2.3.2-2_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEugQ0bcLh/mPHkIeTzGWwzewnXVsFAmnH60oACgkQzGWwzewn
XVteUA/8DyaqoXycw/qggSvywr3qCbccrS2FVs37AI34tFNWFW9mbh0Rl8OT2A+0
fZjmPNxSqcfRP6RqhO+/o5M4/i33xiu0pjA+dk0NxNumiBwltbmeB1j7bewBxZzd
/S3JLyFwFfVFyXdU6OiMxIAajMK0QveQ6A8gymqvtKTyLI3TxFYOKaSDe1ANmChE
AVPXTZuVcQmLoiyPEi5eZM6iYnevumkQRdVcjudQuY5PD+WzEg19UUJuglng44sF
ngINudVikA9dJik6bm7Rz5lQlBNTBZ5PF1sTwXlckEBca7FXPwT+fJvGxWGqbku1
tD403xVGqqqymkZmKiSx0Oaweb5buKT7P+Py0GKk+aGWCP+jgX9cYcV51WJiIG9z
D6/sC6zUFtyk9xtWxsK45SkPgchJXPMGHdueEyzrGoKY8kAn1aMA/1r0F2j0E3GQ
JsGOh6+AtZseDuzKFHYMZeBRfSrmeQy3q3DfDX39mxUMLl0FYLey4kkpu15RDFyO
0u3x69XMre72YRPMguum+/YEuWVnOp/1TMIrEwMCe5ovrLTB5qooWF2lPwp53TJe
NhaNnDaei0mVQo/ukXz40QeMBJfyM9N9eFqgq5cPPaK5Pl9ooB8fTprgF5YDdW4f
JsFHQfTvOfTDoH5v/LQHU4JGPDHPwWJzT12PQEswQSpjE/QEFtU=
=qOgg
-----END PGP SIGNATURE-----

Dear CZChen,

Thank you for bringing this up for discussion.

The option 2 is existing design for keeping Debian-specific default looks
and feel in LXQt desktop for all the previous Debian releases. Which
benefits for updating the icon theme, wallpaper, menu style, menu icon,
quick launcher, taskbar and clock layouts. It helps to maintain all the
LXQt default desktop looks and feel without any additional changes to other
lxqt packages. It’s easier and more efficient to change the whole defaults
looks and test locally before uploading to Debian. And also easier for
downstream distributions to do their own branding.

I know your attention was focused on resolving the RC bug on config file
conflicts between lxqt-branding-lxqt and lxqt-panel. So that you choose to
dropped the default panel.conf in lxqt-branding-debian and uploaded
upstream’s config file as option 1 in lxqt-panel to resolve the conflicts
and closed the RC bugs. Thank you for preventing auto removal for
lxqt-panel.

However, this RC fix made a regression as it changed the existing default
looks and feel design for LXQt desktop in Debian. So that it triggers
OpenQA team found the menu icon and panel layout broken in OpenQA’s d-I
daily tests screenshots.

I hope you may take this chance to have a look at lxqt-branding-debian
package to understand the existing design for LXQt desktop in Debian.
Please simply revert the config file in lxqt-branding-debian. And then
please also feel free to send MR if you want to propose any other
customized default settings to enhance LXQt desktop.

Best regards,

I think using option 2 is okay. However, do we need to support the case
when only lxqt-panel is installed, but not lxqt-branding-debian? In this
case, when the config for lxqt-panel is only in lxqt-brakding-debian,
there is no config for lxqt-panel.

Hi czchen,

Upstream already supported that and we used to also support that until
we shipping the incorprated panel.conf in lxqt-panel package. When
lxqt-panel launched without any panel.conf specified. The built-in
empty config will be used for user to custom their own panel profile.
This is the default behevior in upstream and also for all of our
previous releases in debian.

The new config you saw from upstream was because upstream wants to
switch fancymenu plugin as default in the panel.conf in version 2.3.
And we have already switched to use fancymenu as default for trixie
release in lxqt-branding-debian package. So we are safe or please
correct me if I am wrong.

On another hand. The panel.conf we currently ship in lxqt-panel
package if we only installed lxqt-panel. You will find it's broken as
it cannot work alone without other parts that shiped in
lxqt-branding-debian package. Because it requires other componments
and depends to works together as a Debian LXQt desktop environment.

In short, we need to revert the corprated panel.conf in
lxqt-branding-package(please correct me if still some modification are
needed) and drop the panel.conf from lxqt-panel package to solve the
problem properly.

Best regards,

Hi Andrew and ChangZhuo,

On Mon, 27 Apr 2026 15:56:36 +0200 Andrew Lee <ajqlee@debian.org> wrote:

I would appreciate if you could confirm, but it looks like the
upstream behaviour has changed when there is no
/etc/xdg/lxqt/panel.conf.  With lxqt-panel 2.1 or 2.2, a default panel
is populated.  With 2.3+, the panel is created, but it's empty, which
is awkward.  So, I'm not sure lxqt-panel should be left without any
panel.conf.

Thanks,
Bryan

Bryan Gardiner <bog@khumba.net>於 2026年5月9日週六，06:43寫道：


There isn’t an upstream behavior changed, but a changes in packaging. Now
we ship a panel.conf template directly from upstream and dropped the
designed panel.conf from lxqt-branding-debian package which I wish we can
revert.


Left without any panel.conf, a panel will be created but it’s empty for
user to customize. The designed panel.conf was shipped in
lxqt-branding-debian among with other lxqt looks and feel design.

You may test and confirm it by installing the older version of
lxqt-branding-debian package which still ships the designed panel.conf.

Best regards,

Hi Andrew, thanks for your reply.

Prior to 2.3, the initial panel was populated (under LXQt sessions)
even without panel.conf in /etc, because the stock panel.conf was in
/usr/share/lxqt [1].  lxqt-panel now not installing panel.conf reverts
back to the default empty panel for all sessions unless
lxqt-branding-debian is installed, which feels like the opposite
direction of the fix for [1].

It would be nice if the panel started with widgets even without
lxqt-branding-debian, but I understand if you consider this a corner
case.  Maybe Debian's lxqt-panel could continue to install it under
/usr/share/lxqt, if lxqt-branding-debian is more important?

[1] https://github.com/lxqt/lxqt-panel/issues/2175

Cheers,
Bryan

Hi Bryan,

Thanks for the info. I hope you assumaion is correct that panel.conf
from lxqt-branding-debian under /etc is higher prioity than panel.conf
from /usr/share/lxqt. And we can satisfy both cases.

Feel free to submit patches or Merge Request via salsa. I will test
them and make upload to fix these shortly.

Best regards,

Hi Andrew,

On Sat, 9 May 2026 15:54:31 +0200 Andrew Lee <ajqlee@debian.org> wrote:

According to the docs for QSettings, this should be how it works.
First ~/.config is checked, then each directory in XDG_CONFIG_DIRS.
LXQt sessions set that variable to "/etc:/etc/xdg:/usr/share".  And if
that variable is unset, Qt defaults it to /etc/xdg.

Thanks, I would be happy to open a MR.  Before I do though, if we
revert to installing under /usr/share/lxqt, that will leave the
upstream bug #2175 above unfixed, so without lxqt-branding-debian
installed, non-LXQt sessions will default to empty panels.  I
confirmed that this happens with an Openbox session when the panel
config is only in /usr/share/lxqt and not /etc/xdg/lxqt.  LXQt
probably can't (and shouldn't) force XDG_CONFIG_DIRS into other
sessions.

One option that respects #2175 might be to have an alternate "stock"
branding package that provides the default panel.conf (and I assume
this is all that would need to be in there at the moment), and give
lxqt-panel "Depends: lxqt-branding" or some variant on that.

Or maybe there's some other way.  But it feels like lxqt-panel depends
on *some* panel.conf existing now.  How should we proceed?

Thanks,
Bryan

Hi Bryan,

Thank you for checking this. If all these are correct. We better ship
the upstream default panel.conf from lxqt-panel to /usr/share and
change the defaults to read it from from `/etc/xdg:/usr/share` instead
of `/etc/xdg`.

This way respects #2175, and without needing depend on any panel.conf
from other package. And also works when one available under `/etc/xdg`
from lxqt-branding-debian.

Am I missing anything?

Best regards,

Hi Bryan,

It seem this is a regrassion issue from upstream.

See details:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883034

I will make a revert patch for now to resolve this in Debian package.

Best regards,

Hi czchen,

Here are the merge requests to revert the regression:
https://salsa.debian.org/lxqt-team/lxqt-panel/-/merge_requests/18
https://salsa.debian.org/lxqt-team/lxqt-branding-debian/-/merge_requests/8

Hi Bryan,

It would be nice if upstream may fix it properly to allow panel to
read it's config from /usr/share instead of /etc/xdg.
However, currently revert the regression commit probably is the best
way for a distribution ships it's own configs like in Debian.

Best regards,

Hi Andrew,

Sorry for being slow to get back to this.

I don't see a good way to change the defaults to read from /usr/share
unconditionally.  QSettings would need a function to append a fallback
directory in code.  Without that, XDG_CONFIG_DIRS *is* the way.
(Without having the panel copy a default config file into place or
something.)  I'm not sure this is worth the effort.

On Sun, 24 May 2026 13:25:15 +0200 Andrew Lee <ajqlee@debian.org> wrote:

I hadn't seen this bit of history.  Reverting sounds good to me.

Agreed.  Thanks for your work.

Cheers,
Bryan

Dear team,

Can some of you please do these important reviews:
https://salsa.debian.org/lxqt-team/lxqt-panel/-/merge_requests/18
https://salsa.debian.org/lxqt-team/lxqt-branding-debian/-/merge_requests/8

If still no response. I will do the merge and upload them to close this
RC bug on 27 June.

Best regards,