https://bugs.kde.org/show_bug.cgi?id=454505

            Bug ID: 454505
           Summary: [wayland] latte does not show on startup #2
           Product: lattedock
           Version: git (master)
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: application
          Assignee: mvourla...@gmail.com
          Reporter: dreamc...@gmail.com
  Target Milestone: ---

(In reply to thewitcher861 from comment #6)
> Updated latte, didn't help. As for monitors, I have 2: 1920x1080 at HDMI and
> 1280x1024 at DP. Unplugging the HDMI one helps. Dock starts normally. I
> guess the problem is the extra monitor that appears for some reason.

Hello m'dears.

Currently experiencing the same bug here on wayland.... tried so many different
things. But no luck. But unfortunately it didn't change anything. At no time
does latte appear (after restarting latte on the cmdline and with the correct
flags). I can attach the --debug log here but it's probably not going to help.

If it is any small clue, IDK. But when running latte from the cmdline it stops
logging output and never prints anything after the screens / displays detection
bit. And then if I try to interrupt latte-dock process by sending a ctrl+C on
the keyboard (SIGINT). That is ignored. So then I have to ctrl+z and forcibly
kill it off. So IDK if that means latte is actually hung and crashed process.
Or if that is just normal correct running program behaviour of it to ignore
ctrl+c....

Things I have tried

* Thoroughly updating my system, including re-installing the nvidia proprietary
drivers AND libmesa ones (AND kernel). Check.
* Recompiled Latte using today's `./install.sh` from the git repo? Check.
* Try latte on gnome wayland instead of plasma? Check. (but it segfaults on
gnome. So was no help)
* Unplug dual displays and reboot? On either monitor has no effect. Latte is
still completely AFK. Check.
* Add environment var `QT_QPA_PLATFORM=wayland` ? Check. No difference.

Overall situation seems difficult to probe or get a better understand of, (for
myself here). Because it might in fact not be latte itself, but some other bugs
in either qt5 libraries, or in wayland (in kwin). Or in the nvidia proprietary
drivers 510. Since there's certainly other things going on and causing other
types of bugs within the wayland session. Even when Latte is not running.

And this is supposed to have been fixed recently? This specific bug?

My system configuration:

* Ubuntu 22.04 (upgraded from 21.10, 21.04, 20.04, etc etc)
* All of the qt5 and other libraries as per ubuntu 22.04 distro
* Plasma version `plasma-desktop/jammy,jammy,now
4:5.24.5-0ubuntu1~ubuntu22.04~ppa1 amd64 [installed]` (=5.24.5, from kde
backports?)
* nvidia-driver-510 verison `nvidia/510.73.05`
* Kernel `5.17.11-xanmod1 #0~git20220525.9ffe6c5`
* Latte version: `lattedock 0.10.77`
* GPU = nvidia gt1030 Pascal generation (this prevents installing the new open
source nvidia drivers)
* MESA = `mesa-vdpau-drivers/jammy,now
22.1.0+git2205261808.f8b312559ba~j~mesarc0`

Other main bug on wayland here: The plasma panels (not latte) are slow and
unresponsive. Like you right click on the desktop and it's laggy / gets
progressively less responsive. IDK if that would affect Latte Dock. However
other regular applications are mostly not being affected. There is a suspicion
of 'nvidia timers bug' existing on closed source nvidia drivers? However the
problem there is that it's kernele non-GPL symbols (cannot be fixed by
nvidia?). Since the nvidia open source driver does not support cards like mine
(pascal), anything older than 2000 series nvidia gpus. Cannot try the open
source driver to eliminate that.

Again, no idea if such other kde bug would affect Latte adversely in this way.
And no idea why removing 2nd display works for other guy here. But not for
myself. Or if it's indeed some seperate bug here in latte dock. Which maybe was
not fully fixed?

Anyhow that's my report, and heres a link to my logfile,
https://gist.github.com/dreamcat4/09dda9074fed6b2270ef4273b9f73f0a

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to