Debian: after upgrading the system the program became unusable. How to approach the problem?

ChrisW67

@JanuszSB I get plugin debug information for both debug and release builds of a small example. For example:

$ ~/Qt/6.6.1/gcc_64/bin/qmake CONFIG+=release

$ make
...

$ file ./simple_example
./simple_example: ELF 64-bit LSB pie executable, x86-64, version 1 (GNU/Linux), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=89d8e1eca37d300fbcfd802cd1f2bb82ce9e708c, for GNU/Linux 3.2.0, not stripped

$ QT_DEBUG_PLUGINS=1 QT_QPA_PLATFORM=xcb ./simple_example 
qt.core.plugin.factoryloader: checking directory path "/home/chrisw/Qt/6.6.1/gcc_64/plugins/platforms" ...
qt.core.plugin.factoryloader: looking at "/home/chrisw/Qt/6.6.1/gcc_64/plugins/platforms/libqminimal.so"
qt.core.plugin.loader: Found metadata in lib /home/chrisw/Qt/6.6.1/gcc_64/plugins/platforms/libqminimal.so, metadata=
{
    "IID": "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3",
    "MetaData": {
        "Keys": [
            "minimal"
        ]
    },
    "archlevel": 1,
    "className": "QMinimalIntegrationPlugin",
    "debug": false,
    "version": 394752
}
...
qt.core.library: "/home/chrisw/Qt/6.6.1/gcc_64/plugins/platforms/libqxcb.so" loaded library
...

I guess your application could be doing something creative to trash the output.

JanuszSB

@ChrisW67 said in Debian: after upgrading the system the program became unusable. How to approach the problem?:

@JanuszSB I get plugin debug information for both debug and release builds of a small example. For example:
$ ~/Qt/6.6.1/gcc_64/bin/qmake CONFIG+=release

What is it for?

$ make
...

$ file ./simple_example
./simple_example: ELF 64-bit LSB pie executable, x86-64, version 1 (GNU/Linux), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=89d8e1eca37d300fbcfd802cd1f2bb82ce9e708c, for GNU/Linux 3.2.0, not stripped

Can you somehow share the program?

$ QT_DEBUG_PLUGINS=1 QT_QPA_PLATFORM=xcb ./simple_example

I guess your application could be doing something creative to trash the output.

The program was written12 years ago, can this be relevant?

SGaist

@JanuszSB can you share your own build ?

Tested on KDE Neon with wayland as backend and it looks like it's working as expected. The widget on the left is a scroll area where widgets are added. It does not do anything special.

JanuszSB

@SGaist said in Debian: after upgrading the system the program became unusable. How to approach the problem?:

@JanuszSB can you share your own build ?

If a Debian package will do, it is available in the repository https://github.com/jsbien/djview4shapes in the Releases. I can also upload somewhere just the binaries.

On the other hand it seems the problem is not reproducible on KDE...

JanuszSB

@SGaist After upgrading yesterday to Debian 11.9, the situation changed slightly. The left panel still doesn't open but QT_DEBUG_PLUGINS=1 produced some output. I uploaded it to
https://github.com/jsbien/djview4shapes/issues/5#issuecomment-1938158253

SGaist

@JanuszSB It's something else, if it was a plugin problem, you wouldn't see the application at all. There's no error in the logs.

JanuszSB

Any idea how to diagnose the problem? BTW, does this forum have a function of mail notification?

ChrisW67

@JanuszSB Your code saves and restores the main window and splitter geometry. Are you absolutely sure you have not just collapsed the left panel of the splitter entirely? This would persist by virtue of the state save/restore.

Find the save configuration and remove/move it sideways before starting the application.
One or more of these locations:

~/.config/djview-poliqarp/djview-poliqarp.conf
~/.config/djview-poliqarp.conf
for D in $(echo $XDG_CONFIG_DIRS | tr ':' ' ') 
do 
  echo $D/djview-poliqarp/djview-poliqarp.conf
  echo $D/djview-poliqarp.conf
done

SGaist

@ChrisW67 Interesting take, I didn't think of that one !