Bug#1075858: mesa-vulkan-drivers > 24.1 should include NVK driver on amd64
I'd love to see NVK packaged in Debian too. Patiently waiting for it. Cheers, -Paul
Bug#1008992: xwayland: all X clients hang indefinitely waiting for /tmp/.X11-unix/X0
Le mer., juil. 6 2022 at 18:56:47 +0200, Michel Dänzer a écrit : On 2022-07-06 18:00, Paul Cercueil wrote: Le mer., juil. 6 2022 at 16:44:46 +0200, Michel Dänzer a écrit : On 2022-07-06 14:33, Paul Cercueil wrote: I don't see it even trying to open the socket… I think Olivier Fourdan figured it out on IRC #gnome-shell: All your symptoms can be reproduced if the environment variable GDK_BACKEND=wayland is set for gnome-shell & gsd-xsettings. It's likely that this is in your environment for some reason (it's not set by default by anything I know of). That was it! I set GDK_BACKEND=wayland in my ~/.bash_profile in order to get Firefox to use Wayland. FWIW, I use MOZ_ENABLE_WAYLAND=1 for this. Yes, I do set MOZ_ENABLE_WAYLAND=1 as well. It used to also require GDK_BACKEND=wayland, but it is not the case anymore, apparently. Removing GDK_BACKEND=wayland from the environment fixes it. Great. I've created https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2496 & https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/merge_requests/302 to make mutter & gnome-settings-daemon robust against this. Assuming it was the same cause for Harlan, I suggest reassigning this bug to libmutter-10-0. Understood. Thanks again. Cheers, -Paul
Bug#1008992: xwayland: all X clients hang indefinitely waiting for /tmp/.X11-unix/X0
Le mer., juil. 6 2022 at 16:44:46 +0200, Michel Dänzer a écrit : On 2022-07-06 14:33, Paul Cercueil wrote: I don't see it even trying to open the socket… I think Olivier Fourdan figured it out on IRC #gnome-shell: All your symptoms can be reproduced if the environment variable GDK_BACKEND=wayland is set for gnome-shell & gsd-xsettings. It's likely that this is in your environment for some reason (it's not set by default by anything I know of). That was it! I set GDK_BACKEND=wayland in my ~/.bash_profile in order to get Firefox to use Wayland. Removing GDK_BACKEND=wayland from the environment fixes it. Thanks! Cheers, -Paul
Bug#1008992: xwayland: all X clients hang indefinitely waiting for /tmp/.X11-unix/X0
Hi Michel, Le mer., juil. 6 2022 at 10:09:31 +0200, Michel Dänzer a écrit : On 2022-07-05 21:09, Paul Cercueil wrote: Le mar., juil. 5 2022 at 20:46:44 +0200, Michel Dänzer a écrit : The message in french from gsd-xsettings is "Cannot open display:" Thanks for the clarification (I thought "affichage" meant "file" :). It seems likely then that gnome-shell's failure to initialize GDK is due to failing to open the X11 display as well. What value does $DISPLAY contain after logging in? [...] $DISPLAY is :0 after logging in. Using DISPLAY=:1 does not seem to change anything. Let's take a step back. The journal should contain a line like gnome-shell[]: Using public X11 display :0, (using :1 for managed services) The display number before "for managed services" is what gnome-shell itself and gsd-xsettings use for connecting to Xwayland. Does the corresponding socket exist under /tmp/.X11-unix, e.g. /tmp/.X11-unix/X1 ? If yes, what does lsof say for it? paul@frank:~$ lsof /tmp/.X11-unix/X* COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME gnome-she 5382 paul 55u unix 0xf9c78a52 0t0 55362 /tmp/.X11-unix/X1 type=STREAM (LISTEN) Xwayland 16890 paul5u unix 0x4a4eebcd 0t0 55360 /tmp/.X11-unix/X0 type=STREAM (LISTEN) Assuming the socket exists and Xwayland is listening on it, maybe try running gsd-xsettings with that display number under strace, to see if that gives any clues about the failure. Output of "strace" here: https://paste.debian.net/1246358/ I don't see it even trying to open the socket… -Paul
Bug#1008992: xwayland: all X clients hang indefinitely waiting for /tmp/.X11-unix/X0
Le mar., juil. 5 2022 at 20:46:44 +0200, Michel Dänzer a écrit : On 2022-07-05 18:28, Paul Cercueil wrote: Le mar., juil. 5 2022 at 15:51:08 +0200, Michel Dänzer a écrit : On 2022-07-05 14:48, Paul Cercueil wrote: Is there a way I can provide more information? Come to think of it, capturing the journal output after trying to start an X11 client might be interesting: journalctl --user -b0 This was giving me zero results so I ran 'journalctl -b0' and some things happened when trying to run 'xterm': [...] juil. 05 17:24:03 frank gsd-xsettings[3959]: Impossible d’ouvrir l’affichage : juil. 05 17:24:03 frank systemd[2111]: org.gnome.SettingsDaemon.XSettings.service: Main process exited, code=exited, status=1/FAILURE juil. 05 17:24:03 frank systemd[2111]: org.gnome.SettingsDaemon.XSettings.service: Failed with result 'exit-code'. juil. 05 17:24:03 frank systemd[2111]: Failed to start GNOME XSettings service. juil. 05 17:24:03 frank gnome-shell[2215]: Window manager warning: L’initialisation de GDK a échoué juil. 05 17:24:03 frank gnome-shell[2215]: Failed to initialize X11 display: Failed to initialize GDK Looks like the problem is either that gsd-xsettings fails to start, or that gnome-shell fails to initialize GDK. On the former, does journalctl --user-unit=org.gnome.SettingsDaemon.XSettings.service -b0 or systemctl --user status org.gnome.SettingsDaemon.XSettings.service provide more information about the failure? journalctl gives me this: juil. 05 19:58:04 frank systemd[2014]: Starting GNOME XSettings service... juil. 05 19:58:05 frank systemd[2014]: Started GNOME XSettings service. juil. 05 19:58:40 frank systemd[2014]: Dependency failed for GNOME XSettings service. juil. 05 19:58:40 frank systemd[2014]: org.gnome.SettingsDaemon.XSettings.service: Job org.gnome.SettingsDaemon.XSettings.service/start failed with result 'dependency'. juil. 05 19:58:55 frank systemd[2014]: Starting GNOME XSettings service... juil. 05 19:58:55 frank gsd-xsettings[4159]: Impossible d’ouvrir l’affichage : juil. 05 19:58:55 frank systemd[2014]: org.gnome.SettingsDaemon.XSettings.service: Main process exited, code=exited, status=1/FAILURE juil. 05 19:58:55 frank systemd[2014]: org.gnome.SettingsDaemon.XSettings.service: Failed with result 'exit-code'. juil. 05 19:58:55 frank systemd[2014]: Failed to start GNOME XSettings service. juil. 05 19:58:55 frank systemd[2014]: org.gnome.SettingsDaemon.XSettings.service: Scheduled restart job, restart counter is at 1. The message in french from gsd-xsettings is "Cannot open display:" Also, does setting DISPLAY=:1 (or whatever is the default number + 1) work better? It does not seem to change anything, running 'DISPLAY=:1 xterm' just hangs (doesn't open a window), the only difference I can see is that no Xwayland process is started. What value does $DISPLAY contain after logging in? What if you try DISPLAY=:1 once Xwayland is running? If that works, maybe try DISPLAY=:1 /usr/libexec/gsd-xsettings -v to see if that gives more information about the failure. $DISPLAY is :0 after logging in. Using DISPLAY=:1 does not seem to change anything. I tried: DISPLAY=:0 /usr/libexec/gsd-xsettings -v DISPLAY=:1 /usr/libexec/gsd-xsettings -v Both print the exact same error message as above, and nothing else. I tried as well: /usr/libexec/gsd-xsettings -v --display=:0 /usr/libexec/gsd-xsettings -v --display=:1 I get the same error message, but this time it did print back the display on the error message: "Cannot open display: :1" On 2022-07-05 18:26, Paul Cercueil wrote: Le mar., juil. 5 2022 at 15:31:25 +0200, Michel Dänzer a écrit : On 2022-07-05 14:48, Paul Cercueil wrote: I end up having to work under Windows, ugh. Surely you can use a GNOME on Xorg session in the worst case. Is that still a thing? I can't select Gnome on X11 anymore since the last few releases of Gnome. GDM simply doesn't give me the option. That's unexpected, I can still choose "GNOME on Xorg" on my machines. Do you have xserver-xorg installed? Ha, good point. I re-installed the "xserver-xorg" package and now I do have the "GNOME on Xorg" option back. Cheers, -Paul
Bug#1008992: xwayland: all X clients hang indefinitely waiting for /tmp/.X11-unix/X0
Le mar., juil. 5 2022 at 15:51:08 +0200, Michel Dänzer a écrit : On 2022-07-05 14:48, Paul Cercueil wrote: Is there a way I can provide more information? Come to think of it, capturing the journal output after trying to start an X11 client might be interesting: journalctl --user -b0 This was giving me zero results so I ran 'journalctl -b0' and some things happened when trying to run 'xterm': juil. 05 17:24:02 frank gnome-shell[3952]: (WW) Option "-listen" for file descriptors is deprecated juil. 05 17:24:02 frank gnome-shell[3952]: Please use "-listenfd" instead. juil. 05 17:24:02 frank gnome-shell[3952]: (WW) Option "-listen" for file descriptors is deprecated juil. 05 17:24:02 frank gnome-shell[3952]: Please use "-listenfd" instead. juil. 05 17:24:03 frank kernel: nouveau :01:00.0: Enabling HDA controller juil. 05 17:24:03 frank kernel: nouveau :01:00.0: bus: MMIO write of e56bf91f FAULT at 6013d4 [ PRIVRING ] juil. 05 17:24:03 frank gnome-shell[3952]: libEGL warning: DRI2: failed to create dri screen juil. 05 17:24:03 frank gnome-shell[3952]: libEGL warning: DRI2: failed to create dri screen juil. 05 17:24:03 frank gnome-shell[3957]: The XKEYBOARD keymap compiler (xkbcomp) reports: juil. 05 17:24:03 frank gnome-shell[3957]: > Warning: Could not resolve keysym XF86EmojiPicker juil. 05 17:24:03 frank gnome-shell[3957]: Errors from xkbcomp are not fatal to the X server juil. 05 17:24:03 frank systemd[2111]: Starting GNOME XSettings service... juil. 05 17:24:03 frank gnome-shell[3960]: The XKEYBOARD keymap compiler (xkbcomp) reports: juil. 05 17:24:03 frank gnome-shell[3960]: > Warning: Unsupported maximum keycode 708, clipping. juil. 05 17:24:03 frank gnome-shell[3960]: > X11 cannot support keycodes above 255. juil. 05 17:24:03 frank gnome-shell[3960]: Errors from xkbcomp are not fatal to the X server juil. 05 17:24:03 frank gsd-xsettings[3959]: Impossible d’ouvrir l’affichage : juil. 05 17:24:03 frank systemd[2111]: org.gnome.SettingsDaemon.XSettings.service: Main process exited, code=exited, status=1/FAILURE juil. 05 17:24:03 frank systemd[2111]: org.gnome.SettingsDaemon.XSettings.service: Failed with result 'exit-code'. juil. 05 17:24:03 frank systemd[2111]: Failed to start GNOME XSettings service. juil. 05 17:24:03 frank gnome-shell[2215]: Window manager warning: L’initialisation de GDK a échoué juil. 05 17:24:03 frank gnome-shell[2215]: Failed to initialize X11 display: Failed to initialize GDK juil. 05 17:24:03 frank systemd[2111]: org.gnome.SettingsDaemon.XSettings.service: Scheduled restart job, restart counter is at 1. juil. 05 17:24:03 frank systemd[2111]: Stopped GNOME XSettings service. juil. 05 17:24:03 frank systemd[2111]: Starting GNOME XSettings service... juil. 05 17:24:03 frank gsd-xsettings[3962]: Impossible d’ouvrir l’affichage : juil. 05 17:24:03 frank systemd[2111]: org.gnome.SettingsDaemon.XSettings.service: Main process exited, code=exited, status=1/FAILURE juil. 05 17:24:03 frank systemd[2111]: org.gnome.SettingsDaemon.XSettings.service: Failed with result 'exit-code'. juil. 05 17:24:03 frank systemd[2111]: Failed to start GNOME XSettings service. juil. 05 17:24:04 frank systemd[2111]: org.gnome.SettingsDaemon.XSettings.service: Scheduled restart job, restart counter is at 2. juil. 05 17:24:04 frank systemd[2111]: Stopped GNOME XSettings service. juil. 05 17:24:04 frank systemd[2111]: Starting GNOME XSettings service... juil. 05 17:24:04 frank gsd-xsettings[3964]: Impossible d’ouvrir l’affichage : juil. 05 17:24:04 frank systemd[2111]: org.gnome.SettingsDaemon.XSettings.service: Main process exited, code=exited, status=1/FAILURE juil. 05 17:24:04 frank systemd[2111]: org.gnome.SettingsDaemon.XSettings.service: Failed with result 'exit-code'. juil. 05 17:24:04 frank systemd[2111]: Failed to start GNOME XSettings service. juil. 05 17:24:04 frank systemd[2111]: org.gnome.SettingsDaemon.XSettings.service: Scheduled restart job, restart counter is at 3. juil. 05 17:24:04 frank systemd[2111]: Stopped GNOME XSettings service. juil. 05 17:24:04 frank systemd[2111]: Starting GNOME XSettings service... juil. 05 17:24:04 frank gsd-xsettings[3966]: Impossible d’ouvrir l’affichage : juil. 05 17:24:04 frank systemd[2111]: org.gnome.SettingsDaemon.XSettings.service: Main process exited, code=exited, status=1/FAILURE juil. 05 17:24:04 frank systemd[2111]: org.gnome.SettingsDaemon.XSettings.service: Failed with result 'exit-code'. juil. 05 17:24:04 frank systemd[2111]: Failed to start GNOME XSettings service. juil. 05 17:24:04 frank systemd[2111]: org.gnome.SettingsDaemon.XSettings.service: Scheduled restart job, restart counter is at 4. juil. 05 17:24:04 frank systemd[2111]: Stopped GNOME XSettings service. juil. 05 17:24:04 frank systemd[2111]: Starting GNOME XSettin
Bug#1008992: xwayland: all X clients hang indefinitely waiting for /tmp/.X11-unix/X0
Le mar., juil. 5 2022 at 15:31:25 +0200, Michel Dänzer a écrit : On 2022-07-05 14:48, Paul Cercueil wrote: Hi Michel, I hate to bump bug reports, but this one is pretty crippling - lots of applications I use every day end up not booting. Is that all the X11 ones, or only some of them? All of them. Even the simple ones like 'xterm' fail to start. I end up having to work under Windows, ugh. Surely you can use a GNOME on Xorg session in the worst case. Is that still a thing? I can't select Gnome on X11 anymore since the last few releases of Gnome. GDM simply doesn't give me the option. -Paul Is there a way I can provide more information? I have no clue what's going on here, nor what to look for. :( -- Earthling Michel Dänzer| https://redhat.com Libre software enthusiast | Mesa and Xwayland developer
Bug#1008992: xwayland: all X clients hang indefinitely waiting for /tmp/.X11-unix/X0
Hi Michel, I hate to bump bug reports, but this one is pretty crippling - lots of applications I use every day end up not booting. I end up having to work under Windows, ugh. Is there a way I can provide more information? I know Xwayland has a -verbose option, but I don't even know how to set it, as Xwayland is executed by gnome-shell directly. Cheers, -Paul
Bug#1008992: xwayland: all X clients hang indefinitely waiting for /tmp/.X11-unix/X0
Hi Michel, Xwayland is started automatically when I am trying to run "xterm", and it does not crash. coredumpctl reports "no coredumps found" and I can see Xwayland running in htop - but xterm does not start. -Paul Le mar., juin 21 2022 at 13:06:35 +0200, Michel Dänzer a écrit : On 2022-06-21 12:35, Paul Cercueil wrote: Package: xwayland Version: 2:22.1.2-1 Followup-For: Bug #1008992 I get that too. This is the result of lsof /tmp/.X11-unix/X0: lsof: WARNING: can't stat() tracefs file system /sys/kernel/debug/tracing Output information may be incomplete. COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME Xwayland 6587 paul5u unix 0xe0c291f2 0t0 26890 /tmp/.X11-unix/X0 type=STREAM (LISTEN) Does coredumpctl | tail show any Xwayland crashes which happened after logging in? If so, can you run coredumpctl gdb Xwayland and then at the gdb prompt bt full and provide the output? -- Earthling Michel Dänzer| https://redhat.com Libre software enthusiast | Mesa and Xwayland developer
Bug#1008992: xwayland: all X clients hang indefinitely waiting for /tmp/.X11-unix/X0
Note that trying to downgrade xwayland to the stable version (2:1.20.11-1+deb11u1 at the moment) will cause GDM to fail starting, rendering the computer unusable. Cheers, -Paul
Bug#1008992: xwayland: all X clients hang indefinitely waiting for /tmp/.X11-unix/X0
Package: xwayland Version: 2:22.1.2-1 Followup-For: Bug #1008992 I get that too. This is the result of lsof /tmp/.X11-unix/X0: lsof: WARNING: can't stat() tracefs file system /sys/kernel/debug/tracing Output information may be incomplete. COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME Xwayland 6587 paul5u unix 0xe0c291f2 0t0 26890 /tmp/.X11-unix/X0 type=STREAM (LISTEN) Cheers, -Paul -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'stable'), (200, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: aarch64, arm64, armhf, arm Kernel: Linux 5.18.0-1-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR:fr Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages xwayland depends on: ii libc6 2.33-7 ii libdrm2 2.4.110-1 ii libepoxy0 1.5.10-1 hi libgbm1 21.3.8-1 ii libgcrypt20 1.10.1-2 ii libgl1 1.4.0-1 ii libpixman-1-0 0.40.0-1 ii libtirpc3 1.3.2-2 ii libwayland-client0 1.20.0-1 ii libxau6 1:1.0.9-1 ii libxcvt00.1.1-3 ii libxdmcp6 1:1.1.2-3 ii libxfont2 1:2.0.5-1 ii libxshmfence1 1.3-1 ii xserver-common 2:21.1.3-2 xwayland recommends no packages. xwayland suggests no packages. -- no debconf information
Bug#1004130: debian logo displayed partly off screen
Package: plymouth Version: 22.02.122-1 Followup-For: Bug #1004130 I have this bug too. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'stable'), (200, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: aarch64, arm64, armhf, arm Kernel: Linux 5.10.0-13-amd64 (SMP w/8 CPU threads) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR:fr Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages plymouth depends on: ii init-system-helpers 1.62 ii initramfs-tools 0.140 ii libc62.33-7 ii libdrm2 2.4.110-1 ii libplymouth5 22.02.122-1 ii lsb-base 11.1.0 ii systemd 250.4-1 ii udev 250.4-1 plymouth recommends no packages. Versions of packages plymouth suggests: ii desktop-base 11.0.3 pn plymouth-themes -- no debconf information
Bug#990714: thermald: Thermald cannot control CPU if intel_pstate status is passive
Package: thermald Version: 2.4.2-1 Severity: important Dear Maintainer, On my system (Asus N56VB with a i7-3630QM), the intel_pstate status is "passive" by default. This prevents thermald from being able to control the CPU frequency. Manually switching it to "active" makes it work. I address the problem locally, with a /etc/tmpfiles.d/pstate.conf file with the following content: w /sys/devices/system/cpu/intel_pstate/status - - - - active Then thermald works perfectly. I suppose the Debian package of thermald should provide a similar file. Cheers, -Paul -- System Information: Debian Release: 11.0 APT prefers testing APT policy: (990, 'testing'), (500, 'stable'), (200, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.46+ (SMP w/8 CPU threads) Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR:fr Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages thermald depends on: ii libc6 2.31-12 ii libdbus-1-3 1.12.20-2 ii libdbus-glib-1-2 0.110-6 ii libevdev2 1.11.0+dfsg-1 ii libgcc-s1 10.2.1-6 ii libglib2.0-0 2.66.8-1 ii liblzma5 5.2.5-2 ii libstdc++610.2.1-6 ii libupower-glib3 0.99.11-2 ii libxml2 2.9.10+dfsg-6.7 ii lsb-base 11.1.0 thermald recommends no packages. thermald suggests no packages. -- Configuration Files: /etc/thermald/thermal-cpu-cdev-order.xml changed: intel_pstate
Bug#962372: linux-image-5.7.0-rc5-amd64: Silead module not installed
Package: linux-image-5.7.0-rc5-amd64 Severity: wishlist Dear Maintainer, The Silead module, present in the upstream kernel for a long time now, adds support for the Silead touchscreen present notably on some Teclast tablets. Right now, these tablets require a custom-built kernel just because this module is absent. Please consider adding it to the default config. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.6.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR:fr (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linux-image-5.7.0-rc5-amd64 depends on: ii initramfs-tools [linux-initramfs-tool] 0.137 ii kmod27+20200310-2 ii linux-base 4.6 Versions of packages linux-image-5.7.0-rc5-amd64 recommends: ii apparmor 2.13.4-1+b1 ii firmware-linux-free 20200122-1 Versions of packages linux-image-5.7.0-rc5-amd64 suggests: pn debian-kernel-handbook pn grub-pc | grub-efi-amd64 | extlinux pn linux-doc-5.7
Bug#800375: qtbase5-dev-tools: uic generates wrong include directive
Package: qtbase5-dev-tools Version: 5.5.0+dfsg-6 Severity: normal Dear Maintainer, When using uic (Qt5 version) with the following UI file: https://github.com/gnuradio/gnuradio/blob/master/gr-qtgui/lib/spectrumdisplayform.ui The generated header file will include . This file does not exist on Debian. Instead, the generated header file should include as provided by the qtbase5-dev package. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable'), (50, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages qtbase5-dev-tools depends on: ii libc62.19-22 ii libgcc1 1:5.2.1-17 ii libqt5core5a [qtbase-abi-5-5-0] 5.5.0+dfsg-6 ii libqt5dbus5 5.5.0+dfsg-6 ii libqt5xml5 5.5.0+dfsg-6 ii libstdc++6 5.2.1-17 ii perl 5.20.2-6 ii qtchooser52-gae5eeef-2 ii zlib1g 1:1.2.8.dfsg-2+b1 qtbase5-dev-tools recommends no packages. qtbase5-dev-tools suggests no packages. -- no debconf information
