Bug#1065544: Cannot install samba due to missing packages
Package: samba When trying to install samba, apt complains about missing packages: root@riskie:~# apt install sambaReading package lists... DoneBuilding dependency tree... DoneReading state information... DoneSome packages could not be installed. This may mean that you haverequested an impossible situation or if you are using the unstabledistribution that some required packages have not yet been createdor been moved out of Incoming.The following information may help to resolve the situation: The following packages have unmet dependencies: samba-libs : Depends: libpam0t64 (>= 0.99.7.1) but it is not installableE: Unable to correct problems, you have held broken packages. root@riskie:~# apt install libpam0t64Reading package lists... DoneBuilding dependency tree... DoneReading state information... DonePackage libpam0t64 is not available, but is referred to by another package.This may mean that the package is missing, has been obsoleted, oris only available from another sourceHowever the following packages replace it: libpam0g E: Package 'libpam0t64' has no installation candidate I suggest that the missing package is added or that the dependencies are corrected. Additional information about my system: root@riskie:~# uname -aLinux riskie 6.6.15-powerpc64 #1 SMP Debian 6.6.15-2 (2024-02-04) ppc64 GNU/Linuxroot@riskie:~# cat /etc/debian_version trixie/sidroot@riskie:~# Best Regards, Luc
Bug#1065543: Cannot install MATE desktop environment
Package: libpam0t64 When trying to install the MATE desktop environment, apt complains about missing packages: root@riskie:~# apt install mate-desktop-environment Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: mate-desktop-environment-core : Depends: gvfs-backends but it is not installable E: Unable to correct problems, you have held broken packages. root@riskie:~# apt install gvfs-backends Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: samba-libs : Depends: libpam0t64 (>= 0.99.7.1) but it is not installable E: Unable to correct problems, you have held broken packages. root@riskie:~# apt install libpam0t64 Reading package lists... Done Building dependency tree... Done Reading state information... Done Package libpam0t64 is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source However the following packages replace it: libpam0g E: Package 'libpam0t64' has no installation candidate root@riskie:~# I suggest that the missing package is added or that the dependencies are corrected. Additional information about my system: root@riskie:~# uname -a Linux riskie 6.6.15-powerpc64 #1 SMP Debian 6.6.15-2 (2024-02-04) ppc64 GNU/Linux root@riskie:~# cat /etc/debian_version trixie/sid root@riskie:~# Best Regards, Luc
Bug#1061651: wiki.debian.org/eSCL ScannerShare.com domain is for sale
Package: www.debian.org Severity: normal Hello everyone at the end of https://wiki.debian.org/eSCL article there is a link to a domain which is for sale so not available anymore.
Bug#1053567: mhonarc: Please upgrade mhonarc to latest version
Package: mhonarc Version: 2.6.19-2.2 Severity: normal Dear Maintainer, Mhonarc is now maintained by Sympa community and has been updated 3 years early (see https://github.com/sympa-community/MHonArc/tags or https://metacpan.org/dist/MHonArc/view/mhonarc). Could you upgrade the Debian package, please? Regards, -- System Information: Debian Release: trixie/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-1-amd64 (SMP w/24 CPU threads; PREEMPT) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages mhonarc depends on: ii perl 5.36.0-9 Versions of packages mhonarc recommends: ii perl [libdigest-md5-perl] 5.36.0-9 mhonarc suggests no packages.
Bug#1052330: comment about the attached hs_err log files
Note that in the attached error log files on the original post, the first one was created with openjdk 21 and the other ones with openjdk 17, so similar errors happens in both versions.
Bug#1006774: bug seems to depend on motherboard/CPU type
The bug is still present in grub 2.06-13. It however seems to happen only with some motherboard/CPU configurations. Here are 3 different configurations I had to test recently: - motherboard MSI X570-A PRO, CPU AMD Ryzen 5 3600 bug occurs: boot freezes as soon as one key is pressed on a USB keyboard due to repeated key, only way to select menu is to use an old keyboard - motherboard ASrock Q87M vPro, CPU Intel core I7 5820K no bug: can select boot menu entries from USB keyboard - motherboard ASUS H170 pro gaming, CPU Intel core I7-6700 no bug: cas select boot menu entries from USB keyboard Every other components in the PC were exactly the same: I just mounted the motherboard/CPU in the same box at a few days interval Luc
Bug#989092: r-cran-kableextra ibn Debian
Hi, I would love to find package r-cran-kableextra in Debian. -- m.vr.gr. Luc Castermans mailto:luc.casterm...@gmail.com
Bug#1024837: lokalize: Issues displaying po files
Package: lokalize Version: 4:22.12.0-2 Followup-For: Bug #1024837 X-Debbugs-Cc: l...@castermans.org Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? open a po file * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? the text of the opened file is not displayed in the window or the text cannot be edited * What outcome did you expect instead? the text shoild be editable *** End of the template - remove these template lines *** -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'experimental'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-0-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8), LANGUAGE=nl Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lokalize depends on: ii kio5.101.0-2 ii libc6 2.36-6 ii libhunspell-1.7-0 1.7.1-1 ii libkf5completion5 5.101.0-1 ii libkf5configcore5 5.101.0-1 ii libkf5configgui5 5.101.0-1 ii libkf5configwidgets5 5.101.0-1 ii libkf5coreaddons5 5.101.0-1 ii libkf5crash5 5.101.0-1 ii libkf5dbusaddons5 5.101.0-1 ii libkf5i18n55.101.0-1 ii libkf5itemviews5 5.101.0-1 ii libkf5kiocore5 5.101.0-2 ii libkf5kiofilewidgets5 5.101.0-2 ii libkf5kiowidgets5 5.101.0-2 ii libkf5notifications5 5.101.0-1 ii libkf5sonnetcore5 5.101.0-1 ii libkf5sonnetui55.101.0-1 ii libkf5textwidgets5 5.101.0-1 ii libkf5widgetsaddons5 5.101.0-1 ii libkf5xmlgui5 5.101.0-1 ii libqt5core5a 5.15.6+dfsg-5 ii libqt5dbus55.15.6+dfsg-5 ii libqt5gui5 5.15.6+dfsg-5 ii libqt5network5 5.15.6+dfsg-5 ii libqt5sql5 5.15.6+dfsg-5 ii libqt5sql5-sqlite 5.15.6+dfsg-5 ii libqt5widgets5 5.15.6+dfsg-5 ii libqt5xml5 5.15.6+dfsg-5 ii libstdc++6 12.2.0-10 Versions of packages lokalize recommends: ii gettext0.21-10 ii sonnet-plugins 5.101.0-1 ii translate-toolkit 3.7.4-1 Versions of packages lokalize suggests: ii khelpcenter 4:22.12.0-2 ii poxml4:22.12.0-2 -- no debconf information
Bug#1006774: problem still present with grub-pc 2.06-5
A few months later, the problem is still there. Current version is 2.06-5. The repeating keys for USB keybords make grub completely impossible to use. Some new checks starting with using 'c' as the first keystroke showed that the repetition is random. Some time I get 10 characters repeated, sometimes I get more than 80 characters filling one line and an half on the screen. This is really a serious problem, please consider looking at it. Luc
Bug#1022724:
Aidez moi à récupérer mon compte eloto
Bug#1022724:
Bonsoir j'aimerais vous demander un service mon compte eloto a de problème pouvez vous m'aider à le récupérer ?
Bug#1022548: lokalize: text window does not repaint
Package: lokalize Version: 4:22.08.2-1~np1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: l...@castermans.org Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** lokalize open correctly, the window with translation memory shows correctly as well. Each file to translate opens correctly as well in a seperate window. However the text in that window is NOT SHOWN at all. With this the application is not usable. *** End of the template - remove these template lines *** -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'experimental'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.0.0-2-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8), LANGUAGE=nl Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lokalize depends on: ii kio5.98.0-1 ii libc6 2.36-1 ii libhunspell-1.7-0 1.7.1-1 ii libkf5completion5 5.98.0-1 ii libkf5configcore5 5.98.0-1 ii libkf5configgui5 5.98.0-1 ii libkf5configwidgets5 5.98.0-1 ii libkf5coreaddons5 5.98.0-1 ii libkf5crash5 5.98.0-1 ii libkf5dbusaddons5 5.98.0-1 ii libkf5i18n55.98.0-1+b1 ii libkf5itemviews5 5.98.0-1 ii libkf5kiocore5 5.98.0-1 ii libkf5kiofilewidgets5 5.98.0-1 ii libkf5kiowidgets5 5.98.0-1 ii libkf5notifications5 5.98.0-1 ii libkf5sonnetcore5 5.98.0-1 ii libkf5sonnetui55.98.0-1 ii libkf5textwidgets5 5.98.0-1 ii libkf5widgetsaddons5 5.98.0-1 ii libkf5xmlgui5 5.98.0-1+b1 ii libqt5core5a 5.15.6+dfsg-2 ii libqt5dbus55.15.6+dfsg-2 ii libqt5gui5 5.15.6+dfsg-2 ii libqt5network5 5.15.6+dfsg-2 ii libqt5sql5 5.15.6+dfsg-2 ii libqt5sql5-sqlite 5.15.6+dfsg-2 ii libqt5widgets5 5.15.6+dfsg-2 ii libqt5xml5 5.15.6+dfsg-2 ii libstdc++6 12.2.0-7 Versions of packages lokalize recommends: ii gettext0.21-9 ii sonnet-plugins 5.98.0-1 ii translate-toolkit 3.7.3-2 Versions of packages lokalize suggests: ii khelpcenter 4:22.08.2-1~np1 ii poxml4:22.08.2-1~np1 -- no debconf information
Bug#1019699: Resolved by linux-image-5.19.0-2-amd64
Hello, the issue is solved by using: linux-image-5.19.0-2-amd64 (5.19.11-1) Regards, Luc Bégault.
Bug#1017029: displaycal: fails to start, stall at spalsh screen after numerous error messages
Le 12/08/2022 à 08:06, Christian Marillat a écrit : On 11 août 2022 20:46, "Jean-Luc Coulon (f5ibh)" wrote: Package: displaycal Version: 3.9.7-1 Severity: important Tags: upstream Hi, When I launch displaycal from a console, I get a lot of error messages (the same group of messages repeated many times). Then it stalls with the splash screen displayed. I'm not sure if installing libsdl2-mixer-2.0-0. Do you have a github account ? Yes, I've Christian
Bug#1017029: displaycal: fails to start, stall at spalsh screen after numerous error messages
Hello Christian ! Yes! Good shot! It works once libsdl2-mixer-2.0-0 installed. Regards Jean-Luc Le 11/08/2022 à 23:59, Christian Marillat a écrit : On 11 août 2022 20:46, "Jean-Luc Coulon (f5ibh)" wrote: Package: displaycal Version: 3.9.7-1 Severity: important Tags: upstream Hi, Hi, When I launch displaycal from a console, I get a lot of error messages (the same group of messages repeated many times). Then it stalls with the splash screen displayed. Could you try to install the libsdl2-mixer-2.0-0 package and see if this bug is gone ? Christian
Bug#1017029: displaycal: fails to start, stall at spalsh screen after numerous error messages
Package: displaycal Version: 3.9.7-1 Severity: important Tags: upstream Hi, When I launch displaycal from a console, I get a lot of error messages (the same group of messages repeated many times). Then it stalls with the splash screen displayed. Please, find attached the session log with the first error message. I tried to build it from source and from upstream source with the same results. Regards Jean-Luc -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.19.0-i7-1.0 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages displaycal depends on: ii argyll 2.3.1+repack-1 ii dbus-x111.14.0-2 ii libc6 2.34-3 ii libjs-jquery3.6.0+dfsg+~3.5.13-1 ii libx11-62:1.8.1-2 ii libxinerama12:1.1.4-3 ii libxrandr2 2:1.5.2-2+b1 ii libxxf86vm1 1:1.1.4-1+b2 ii python3 3.10.6-1 ii python3-distro 1.7.0-1 ii python3-gi 3.42.2-1 ii python3-numpy 1:1.22.1-1 ii python3-send2trash 1.8.1~b0-1 ii python3-wxgtk4.04.0.7+dfsg-15+b1 Versions of packages displaycal recommends: ii colord1.4.6-1 ii gir1.2-colordgtk-1.0 0.3.0-3 displaycal suggests no packages. -- no debconf information ~/ displaycal Acquired lock file: displaycal 0.0.0 1970-01-01T00:00:00Z debian unstable sid x86_64 Python 3.10.6 (main, Aug 10 2022, 11:19:32) [GCC 12.1.0] Faulthandler wxPython 4.0.7 gtk3 (phoenix) wxWidgets 3.0.5 Encoding: utf-8 File system encoding: utf-8 Existing client using port 15411 Connecting to 15411... Connection to 127.0.0.1:15411 failed: [Errno 111] Connection refused listening writing to lock file: port: 42283 Démarrage… (displaycal:95059): Gtk-WARNING **: 18:42:00.679: Theme file for breeze_cursors has no directories SDL2: libSDL2-2.0.so.0 SDL: libSDL-1.2.so.0 Module audio : pyglet 1.5.26 NoneType: None ┌──┐ │ Traceback (most recent call last): │ │ File "/usr/lib/python3/dist-packages/wx/core.py", line 2251, in Notify │ │ self.notify()│ │ File "/usr/lib/python3/dist-packages/wx/core.py", line 3407, in Notify │ │ self.result = self.callable(*self.args, **self.kwargs) │ │ File "/usr/lib/python3/dist-packages/DisplayCAL/display_cal.py", line │ │ 19394, in startup│ │ wx.CallLater(1, self.startup)│ │ File "/usr/lib/python3/dist-packages/wx/core.py", line 3326, in __init__ │ │ self.Start() │ │ File "/usr/lib/python3/dist-packages/wx/core.py", line 3347, in Start │ │ self.timer.Start(self.millis, wx.TIMER_ONE_SHOT) │ │ wx._core.wxAssertionError: C++ assertion "wxThread::IsMain()" failed at │ │ ../src/common/timerimpl.cpp(59) in Start(): timer can only be started from │ │ the main thread │ └──┘
Bug#1010528: exiv2 rm file.tiff does not remove XMP data
Package: exiv2 Version: 0.27.3-3+deb11u1 Severity: normal Dear Maintainer, On Debian Stretch and Buster I'm able to run 'exiv2 rm file.tiff' to remove all metadata from a TIFF file. However, on Debian Bullseye this only removes some metadata, notably the XMP data (the whole '...' XML stuff) remains in the resulting file. I also tried version 0.27.5-3 from unstable with the same result. If desired I can provide a test file, but it's quite trivial to build one with GIMP and its metadata editor. -- System Information: Debian Release: 11.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-13-amd64 (SMP w/4 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages exiv2 depends on: ii libc62.31-13+deb11u3 ii libexiv2-27 0.27.3-3+deb11u1 ii libgcc-s110.2.1-6 ii libstdc++6 10.2.1-6 exiv2 recommends no packages. exiv2 suggests no packages. -- no debconf information
Bug#1006774: grub-pc: seems related to keys autorepeating
Hi all, Here are some more informations about this bug. I can confirm it happens on USB keyboard and it does not happen on PS/2 keyboard. I purchased an old used PS/2 keyboard on ebay to check. With this keyboard plugged on the PS/2 socket of the motherboard, everything workd fine. At boot time, I can press the arrow keys to select menu entries in Grub at will. When I have highlighted the entry I want, pressing enter runs this entry, as expected. I tried also some mixed settings, as both the Logitech MX Keys with a wireless USB dongle and the old PS/2 keyboard were plugged when booting. In this setting, if I use the PS/2 keyboard arrow keys to change selection, it works. Then, I switch to the USB keybord and try to also use the arrow keys. Freeze occurs immediately, at the first press of a key from the USB keyboard. Once grub is frozen, if I attempt to use the PS/2 keyboard again, nothing happens, grub remains frozen and I have to use the power switch to shut down the computer. Note that the problem does not occur on a notebook with an integrated keyboard, even if I use the wireless USB keyboard instead of the notebook keyboard. So the only workaround I found for using the grub menu on a desktop PC was to purchase an old PS/2 keyboard, and not touch at all the USB keyboard while grub is active. best regards, Luc
Bug#1009108: xmms2: Curl plugin: intermediate buffer overrun
Package: xmms2
Version: 0.8+dfsg-21
Severity: important
Tags: patch upstream
Dear Maintainer,
After finally doing a long procrastinated dist-upgrade, i am no longer able
to play streams.
I am running into the following:
21:23:55 INFO: ../src/xmms/xform.c:1363: Successfully setup chain for
'https://nightride.fm/stream/nightride.mp3' (39865) containing
curl:magic:mad:converter:segment
21:23:56 FAIL: xmms_curl_callback_write: assertion '(data->bufferlen + len) <=
CURL_MAX_WRITE_SIZE' failed
21:23:56 ERROR: ../src/plugins/curl/curl_http.c:378: Curl fill_buffer returned
error: (23) Failed writing received data to disk/application
While this is caused by a discrepancy between the design of xmms2 and/or the
xmms2 curl plugin, and the design of libcurl, the attached patch bumps the
intermediate buffer size to a point where the issue should no longer occur.
-- System Information:
Debian Release: 11.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-13-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages xmms2 depends on:
ii xmms2-client-cli 0.8+dfsg-21
ii xmms2-core0.8+dfsg-21
ii xmms2-icon0.8+dfsg-21
ii xmms2-plugin-alsa [xmms2-plugin-output] 0.8+dfsg-21
ii xmms2-plugin-ao [xmms2-plugin-output] 0.8+dfsg-21
ii xmms2-plugin-ices [xmms2-plugin-output] 0.8+dfsg-21
ii xmms2-plugin-id3v20.8+dfsg-21
ii xmms2-plugin-jack [xmms2-plugin-output] 0.8+dfsg-21
ii xmms2-plugin-mad 0.8+dfsg-21
ii xmms2-plugin-oss [xmms2-plugin-output]0.8+dfsg-21
ii xmms2-plugin-pulse [xmms2-plugin-output] 0.8+dfsg-21
ii xmms2-plugin-vorbis 0.8+dfsg-21
xmms2 recommends no packages.
xmms2 suggests no packages.
-- no debconf information
>From 7f7c64ac116e119851f13237d0c68d3ca0ce3343 Mon Sep 17 00:00:00 2001
From: Luc Verhaegen
Date: Thu, 7 Apr 2022 11:53:17 +0200
Subject: [PATCH 1/1] curl: set intermediate buffer to 128kB
This is pretty arbitrary, but larger than it used to be.
Curl expects us to immediately handle the data it sends over. We instead go
and copy the received data into an intermediate buffer, so our own
callback can then later copy it into the final buffer.
The intermediate buffer used to be set to CURL_MAX_WRITE_SIZE (16kB),
which is getting overrun.
Since we use an intermediate buffer, setting CURLOPT_BUFFERSIZE has no
effect for us.
There is no logic, no science to this, but at least 128kB should be large
enough to store a full second of a FLAC stream.
Signed-off-by: Luc Verhaegen
---
src/plugins/curl/curl_http.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/src/plugins/curl/curl_http.c b/src/plugins/curl/curl_http.c
index f19b6d94..d0c9e1f1 100644
--- a/src/plugins/curl/curl_http.c
+++ b/src/plugins/curl/curl_http.c
@@ -31,6 +31,7 @@
/*
* Type definitions
*/
+#define XMMS2_CURL_BUFFER_SIZE 0x20
typedef struct {
CURL *curl_easy;
@@ -212,7 +213,7 @@ xmms_curl_init (xmms_xform_t *xform)
g_snprintf (proxyuserpass, sizeof (proxyuserpass), "%s:%s", proxyuser,
proxypass);
- data->buffer = g_malloc (CURL_MAX_WRITE_SIZE);
+ data->buffer = g_malloc (XMMS2_CURL_BUFFER_SIZE);
data->url = g_strdup (url);
/* check for broken version of curl here */
@@ -463,7 +464,7 @@ xmms_curl_callback_write (void *ptr, size_t size, size_t
nmemb, void *stream)
len = size * nmemb;
- g_return_val_if_fail ((data->bufferlen + len) <= CURL_MAX_WRITE_SIZE,
0);
+ g_return_val_if_fail ((data->bufferlen + len) <=
XMMS2_CURL_BUFFER_SIZE, 0);
memcpy (data->buffer + data->bufferlen, ptr, len);
data->bufferlen = data->bufferlen + len;
--
2.30.2
Bug#1006774: grub-pc: seems related to keys autorepeating
Package: grub-pc
Version: 2.04-20
Followup-For: Bug #1006774
I have encountered numerous time the same behavior: grub freezing after first
keypress.
What happened in my case was that for repairing a system, I wanted to switch to
the second menu entry "advanced options" in order to boot in recovery. So I
pressed the down key.
Instead of having the second entry highlighted, the selection went all the way
down to last entry (i.e. memory check), and then grub froze. No other key would
work and I would be forced to shut the computer down using the power switch.
Years ago, this already happened to me numerous times, and at that time was
solved by using a different keyboard, i.e. to use a wired keyboard with the old
round violet plug. I do not have this keyboard and now only have USB keyboards,
wireless ones (Logitech MXkeys, Logitech K230) and a wired one (cheap noname).
All these keyboards exhibits the same behavior.
Upon further investigation, it seems to me that grubs receives duplicated
keystrokes. If for example instead of pressing the down key to select a non-
default menu entry I press the "c" key to get command line, grubs switches
properly to a new page with a "grub>" prompt, and a line full of "c" after the
prompt. If I press backspace to remove one "c", I remove all of them. If I
press any other letter like "f", I get perhaps 40 or 80 "f" in the line. I
cannot edit anything. As this happens with all USK keyboards I tried, even a
brand new one bought specially for the purpose and never used before, I don't
think that the keyboards are faulty with bouncing keys. Also after boot, in
regular operations, all these keyboards work properly and don't bounce.
This problem is very serious to me. It completely prevents recovering a broken
system. I *cannot* boot in recovery mode. In fact, I cannot boot in anything
except default mode, carefully taking care of not touching my keyboard at all
during grub initialization.
-- Package-specific info:
*** BEGIN /proc/mounts
/dev/mapper/vg--ssd-root / ext4 rw,relatime,errors=remount-ro 0 0
/dev/sda1 /boot ext4 rw,relatime,errors=remount-ro 0 0
/dev/mapper/vg--ssd-var /var ext4 rw,relatime 0 0
/dev/mapper/vg--raid-home /home ext4 rw,relatime,stripe=256 0 0
*** END /proc/mounts
*** BEGIN /boot/grub/device.map
(hd0) /dev/disk/by-id/ata-Samsung_SSD_840_EVO_120GB_S1D5NEAD713097K
(hd1) /dev/disk/by-id/ata-WDC_WD20EFRX-68EUZN0_WD-WCC4M0418357
(hd2) /dev/disk/by-id/ata-WDC_WD20EFRX-68EUZN0_WD-WCC4M0172970
(hd3) /dev/disk/by-id/ata-WDC_WD20EFRX-68EUZN0_WD-WCC4M0424181
(hd4) /dev/disk/by-id/ata-WDC_WD20EARS-00MVWB0_WD-WCAZA7496406
*** END /boot/grub/device.map
*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
set have_grubenv=true
load_env
fi
if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
else
set default="0"
fi
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
}
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_msdos
insmod lvm
insmod ext2
set
root='lvmid/ERn0X9-L93q-90A7-e9Mj-NgBY-rxy3-iHV630/rK1j4L-7bjq-CLkM-O7tk-6xgr-XTxt-mQKw3y'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root
--hint='lvmid/ERn0X9-L93q-90A7-e9Mj-NgBY-rxy3-iHV630/rK1j4L-7bjq-CLkM-O7tk-6xgr-XTxt-mQKw3y'
e21c2483-b9d3-46a7-90a2-9f2d4119d01c
else
search --no-floppy --fs-uuid --set=root e21c2483-b9d3-46a7-90a2-9f2d4119d01c
fi
font="/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=fr_FR
insmod gettext
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ] ; then
set timeout=30
else
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=5
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
set timeout=5
fi
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
insmod part_msdos
insmod lvm
insmod ext2
set
Bug#1006258: rstudio crashes
Package: rstudio Version: 2022.02.0+443 Severity: grave Tags: upstream Justification: renders package unusable X-Debbugs-Cc: l...@castermans.org Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? upon crash a white screen is shown, need to KILL it; fully reproducible * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'experimental'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.17.0-rc3-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8), LANGUAGE=nl Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages rstudio depends on: ii libc6 2.34-0experimental3 ii libclang-dev1:13.0-54 ii libedit23.1-20210910-1 ii libpq5 14.2-1 ii libsqlite3-03.37.2-2 ii libssl1.1 1.1.1m-1 ii libxkbcommon-x11-0 1.4.0-1 Versions of packages rstudio recommends: ii r-base 4.1.2-2 rstudio suggests no packages. -- no debconf information
Bug#963980: (no subject)
Many thanks to Sébastien MARQUE for the suggestion `nmcli radio all off`. This resolves the problem. For me, I don't need to wait for nvidia to no longer be in lsmod before I can start it again. This is with a Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31), Intel Corporation UHD Graphics 620 (rev 07), and NVIDIA Corporation GP108M [GeForce MX150] (rev a1), on an up-to-date Debian 10 using nouveau drivers if I'm not mistaken (I tried every possible setup until something worked to run Parkitect a few weeks ago, not sure what the current setup is, just that the nvidia-detect command doesn't exist and I have to prefix primusrun and add -force-opengl). If I can help by providing details about my setup or by trying something, please let me know what commands to run -- via lgms.nl/email since I expect I'll be receiving spam on the sending address before too long which means I'll have to block it. Best, Luc
Bug#999574: latte-dock: Dutch translation
Package: latte-dock Version: 0.10.3-1 Severity: normal X-Debbugs-Cc: l...@castermans.org Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** The Dutch translation is quite outdated. An improved version is available in the SVN repo svn://anonsvn.kde.org/home/kde/trunk/l10n-kf5/nl/messages Please pick up the translation from the SVN * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'experimental'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.15.0-trunk-amd64 (SMP w/4 CPU threads) Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8), LANGUAGE=nl Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages latte-dock depends on: ii kio 5.87.0-1~np2 ii kpackagetool55.87.0-1~np2 ii libc62.33-0experimental2 ii libkf5activities55.87.0-1~np2 ii libkf5archive5 5.87.0-1~np2 ii libkf5configcore55.87.0-1~np2 ii libkf5configgui5 5.87.0-1~np2 ii libkf5coreaddons55.87.0-1~np2 ii libkf5crash5 5.87.0-1~np2 ii libkf5dbusaddons55.87.0-1~np2 ii libkf5declarative5 5.87.0-1~np2 ii libkf5globalaccel-bin5.87.0-1~np2 ii libkf5globalaccel5 5.87.0-1~np2 ii libkf5guiaddons5 5.87.0-1~np2 ii libkf5i18n5 5.87.0-1~np2 ii libkf5iconthemes55.87.0-1~np2 ii libkf5kiogui55.87.0-1~np2 ii libkf5kiowidgets55.87.0-1~np2 ii libkf5newstuff5 5.87.0-1~np2 ii libkf5notifications5 5.87.0-1~np2 ii libkf5package5 5.87.0-1~np2 ii libkf5plasma55.87.0-1~np2 ii libkf5plasmaquick5 5.87.0-1~np2 ii libkf5quickaddons5 5.87.0-1~np2 ii libkf5service-bin5.87.0-1~np2 ii libkf5service5 5.87.0-1~np2 ii libkf5waylandclient5 4:5.87.0-1~np2 ii libkf5widgetsaddons5 5.87.0-1~np2 ii libkf5windowsystem5 5.87.0-1~np2 ii libkf5xmlgui55.87.0-1~np2 ii libqt5core5a 5.15.2+dfsg-12 ii libqt5dbus5 5.15.2+dfsg-12 ii libqt5gui5 5.15.2+dfsg-12 ii libqt5qml5 5.15.2+dfsg-8 ii libqt5quick5 5.15.2+dfsg-8 ii libqt5widgets5 5.15.2+dfsg-12 ii libqt5x11extras5 5.15.2-2 ii libstdc++6 11.2.0-10 ii libx11-6 2:1.7.2-2+b1 ii libxcb-randr01.14-3 ii libxcb-shape01.14-3 ii libxcb1 1.14-3 ii plasma-desktop 4:5.23.3-1 ii plasma-framework 5.87.0-1~np2 ii qml-module-org-kde-kquickcontrolsaddons 5.87.0-1~np2 ii qml-module-qtgraphicaleffects5.15.2-2 ii qml-module-qtquick-controls 5.15.2-2 ii qml-module-qtquick-controls2 5.15.2+dfsg-4 ii qml-module-qtquick-layouts 5.15.2+dfsg-8 ii qml-module-qtquick2 5.15.2+dfsg-8 latte-dock recommends no packages. latte-dock suggests no packages. -- no debconf information
Bug#998220: [Pkg-utopia-maintainers] Bug#998220: pipewire: libspa-0.2-bluetooth not installed
Le jeudi 04 novembre 2021 à 10:01 +0100, Michael Biebl a écrit : > > > I don't think this is true at least I don't see any dependency > changes > in Debian which would automatically install pipewire-pulse. Well, I am using Debian testing, and did not change anything by myself. It just happened to me that my headset did not work anymore at one time, and only after lots of search I found that pipewire (which was unknown to me), was installed and this was related to the problems. For now, my headset does not work at all, and I don't know how to fix it. Luc
Bug#998220: pipewire: libspa-0.2-bluetooth not installed
On Wed, 3 Nov 2021 21:44:43 -0400 Ralf Jung wrote: > I am having the same problem. According to > https://wiki.debian.org/BluetoothUser/a2dp, one also has to uninstall > pulseaudio-module-bluetooth. How did you manage to remove pulseaudio-module-bluetooth? There is a dependency from gnome-core to pulseaudio-module-bluetooth so while attempting to remove it I get suggestions to remove gnome completely in order to resolve dependency conflicts. Luc
Bug#998220: pipewire: libspa-0.2-bluetooth not installed
Le mercredi 03 novembre 2021 à 21:44 -0400, Ralf Jung a écrit : > > > I am also still struggling with getting BT working again; do you have a > link to > the other bug report? The other bug report is https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998221
Bug#998221: wireplumber: Headset not working after upgrade
Package: wireplumber Version: 0.4.4-1 Severity: normal Dear Maintainer, Since upgrade to piupewire 0.3.39-3 and wireplumber 0.4.4-1, my Sony WH-1000XM4 doesn't work anymore. It worked flawlessly a few days ago. After an initial problem with libspa-0.2-bluetooth not installed was solved, the headset did connect and stay connected, but no sound was produced. The sound parameters in gnome showed the device in the list for output devices and the test button. When pressing this test button, the popup window only showed a single button "Mono" for the test and not the regular "Left" and "Right" buttons I was used to. Pressing the button did not produce any sound. The popup windo also showed a new to me configuration list with three possible selections: - Headset Head Unit (HSP/HFP) - Headset Head Unit (HSP/HFP, codec CVSD) - Headset Head Unit (HSP/HFP, codec mSBC) All thee selections show the same behaviour : one "Mono" button for test and no sound at all. Looking at journalctl, I get the no messages with Headset Head Unit (HSP/HFP) or Headset Head Unit (HSP/HFP, codec CVSD) configurations. However, when using Headset Head Unit (HSP/HFP, codec mSBC) configuration, I get tons of messages from wireplumber: sco-sink: mSBC buffer overrun, dropping data -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.14.0-2-amd64 (SMP w/12 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages wireplumber depends on: ii init-system-helpers 1.60 ii libc6 2.32-4 ii libglib2.0-0 2.70.0-3 ii libpipewire-0.3-0 0.3.39-3 ii libwireplumber-0.4-0 0.4.4-1 ii pipewire 0.3.39-3 Versions of packages wireplumber recommends: ii pipewire-pulse 0.3.39-3 wireplumber suggests no packages. -- no debconf information
Bug#998220: duplicate
Hi after more searching, I found I should have sent this report to wireplumber package rather than pipewire, and indeed it is a duplicate of #997862. I however still think some dependency should be set up at some level.
Bug#998220: pipewire: libspa-0.2-bluetooth not installed
Package: pipewire Version: 0.3.39-3 Severity: normal Dear Maintainer, Since upgrade to 0.3.39-3, my Sony WH-1000XM4 doesn't work anymore. It worked flawlessly a few days ago. The first problem was that the headset disconnected immediately after connecting. There was an associated error in journalctl : src/service.c:btd_service_connect() a2dp-sink profile connect failed for Protocol not available Some search engine pointed to me that this may be associated with missing libspa-0.2-bluetooth, so I installed it and this first error disappeared. So a first suggestion would be to make sure that libspa-0.2-bluetooth is added as a dependency to some of the pipewire set. This however did not solve my problem, I will file another bug report for the remaining part -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.14.0-2-amd64 (SMP w/12 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages pipewire depends on: ii init-system-helpers 1.60 ii libpipewire-0.3-modules 0.3.39-3 ii pipewire-bin 0.3.39-3 pipewire recommends no packages. pipewire suggests no packages. -- no debconf information
Bug#982588: python2.7: impossible to import pip backport modules (but not existing in python 2.7.13 of Debian Stretch)
Package: python2.7 Version: 2.7.16-2+deb10u1 Severity: normal -- System Information: Debian Release: 10.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-13-amd64 (SMP w/20 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python2.7 depends on: ii libpython2.7-stdlib 2.7.16-2+deb10u1 ii mime-support 3.62 ii python2.7-minimal2.7.16-2+deb10u1 python2.7 recommends no packages. Versions of packages python2.7 suggests: ii binutils 2.31.1-16 pn python2.7-doc -- no debconf information -- Additional Informations When you install a python-backports-xxx package, the directory backports is created in /usr/lib/python2.7/dist-packages. Then, most data of the package are copied in this directory. then you can import modules of this package with an "import backports.xxx" If at a later time you install using pip a backported module not provided within a package, for example backports.lzma, with command pip install backports.lzma, pip create a directory backports in /usr/local/lib/python2.7/dist-packages. In this directoty pip copy most of data of this module. The problem is that this module is impossible to import import backports.lzma return ImportError: No module named lzma but, if I look at my sys path I see that /usr/local/lib/python2.7/dist-packages is in the path >>> print sys.path ['', '/usr/lib/python2.7', '/usr/lib/python2.7/plat-x86_64-linux-gnu', '/usr/lib/python2.7/lib-tk', '/usr/lib/python2.7/lib-old', '/usr/lib/python2.7/lib-dynload', '/usr/local/lib/python2.7/dist-packages', '/usr/lib/python2.7/dist-packages', '/usr/lib/python2.7/dist-packages/gtk-2.0', '/usr/lib/python2.7/dist-packages/wx-3.0-gtk3'] the only possible workaround I have found is to symlink module directories in /usr/lib/python2.7/dist-packages as if the module would have been installed from a Debian package -- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
Bug#976718: why replacing he previous version if the newer one is intentionaly non-working?
Fastboot *is* important. It is the only way we can unlock some phones to install free alternative like lineageos. If the new version cannot be built, then why replacing the old working version with an explicitly non-working script? What is the point in replacing a working version when no alternative is available? Now users are stuck trying to find their way to snapshot.debian.org and make sense of hidden dependencies. I would very much like to see the rationale here.
Bug#973574: package openfoam does not contain foamEtcFile
Package: openfoam Version: 1906.19+dfsg1-2 As far as I know, in order to use openfoam, it is necessary to source /usr/share/openfoam/etc/bashrc beforehand. However, sourcing this file fails with the message: /usr/share/openfoam/etc/config.sh/setup:30: no such file or directory: /usr/share/openfoam/bin/foamEtcFile More generally, all the files from bin/ in the source of openfoam seem to be missing from the debian package. If that is intentional, how are we supposed to run openfoam?
Bug#968042: upgrading packet python2 from 2.7.17-2 up to 2.7.18-2 asks packets deletion
On Sat, 12 Sep 2020 18:54:57 +0200 Diederik de Haas wrote: > On Fri, 07 Aug 2020 18:11:20 +0300 Vladmimir Stavrinov > wrote: > > Now there are no problems with python2 but dependencies are still broken > > for > > python itself: > > It's now a month later and this problem still exists (on my Debian Sid > system). > Are the following packages supposed to be deleted from the system? > python python-minimal libpython-stdlib > > I'd still have the python2 variants of those packages installed btw. I got a similar problem on Debian testing, but with even more weird consequences. I did accept to delete the packages, then the packages installation failed with an error: Removing update-manager-core (0.200.5-2.1) ... File "/usr/sbin/update-python-modules", line 52 print x ^ SyntaxError: Missing parentheses in call to 'print'. Did you mean print(x)? dpkg: error processing package update-manager-core (--remove): installed update-manager-core package pre-removal script subprocess returned error exit status 1 dpkg: too many errors, stopping I tried to add the missing parentheses to update-python-modules, but the installation failed at a later stage, with another syntax error. I guessed it was a python2/python3 difference, indeed /etc/alternatives/python points to python3, perhaps python2 was half-removed? So I ended up changing the link back semi-manually using update-alternatives --install /usr/bin/python python /usr/bin/python2 20 and then aptitude install update-manager-core to finish reconfiguring the half-installed package.
Bug#968346: linked to both libdrm-nouveau2 and QT?
I read again the bug report for <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927954> and realized all cases were related to QT applications: konqueror for 927954, FreeCAD and KeePassXC for 968346. I think this should really be reassigned to libdrm-nouveau2 package. Luc
Bug#968346: maybe linked to libdrm-nouveau2
]: nouveau: 0x8585 août 23 09:04:19 lehrin gnome-shell[2561]: nouveau: 0x200406c0 août 23 09:04:19 lehrin gnome-shell[2561]: nouveau: 0x août 23 09:04:19 lehrin gnome-shell[2561]: nouveau: 0x00218000 août 23 09:04:19 lehrin gnome-shell[2561]: nouveau: 0x0170 août 23 09:04:19 lehrin gnome-shell[2561]: nouveau: 0x1000f010 août 23 09:04:19 lehrin gnome-shell[2561]: Xwayland: ../nouveau/pushbuf.c:723: nouveau_pushbuf_data: Assertion `kref' failed. août 23 09:04:19 lehrin gnome-shell[2561]: (EE) août 23 09:04:19 lehrin gnome-shell[2561]: (EE) Backtrace: août 23 09:04:19 lehrin gnome-shell[2561]: (EE) 0: /usr/bin/Xwayland (OsLookupColor+0x138) [0x558414b7a7e8] août 23 09:04:19 lehrin gnome-shell[2561]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x50) [0x7f3e8c46b18f] août 23 09:04:19 lehrin gnome-shell[2561]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0x141) [0x7f3e8c2cddb1] août 23 09:04:19 lehrin gnome-shell[2561]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x123) [0x7f3e8c2b7537] août 23 09:04:20 lehrin gnome-shell[2561]: (EE) unw_get_proc_name failed: no unwind info found [-10] août 23 09:04:20 lehrin gnome-shell[2561]: (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (?+0x0) [0x7f3e8c2b7400] août 23 09:04:20 lehrin gnome-shell[2561]: (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (__assert_fail+0x42) [0x7f3e8c2c65b2] août 23 09:04:20 lehrin gnome-shell[2561]: (EE) 6: /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 (nouveau_pushbuf_data+0xff) [0x7f3e8573c43f] août 23 09:04:20 lehrin gnome-shell[2561]: (EE) 7: /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 (nouveau_pushbuf_data+0x63) [0x7f3e8573c3a3] août 23 09:04:20 lehrin gnome-shell[2561]: (EE) 8: /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 (nouveau_pushbuf_data+0x17c) [0x7f3e8573c5bc] août 23 09:04:20 lehrin gnome-shell[2561]: (EE) 9: /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 (nouveau_pushbuf_data+0x59f) [0x7f3e8573ce3f] août 23 09:04:20 lehrin gnome-shell[2561]: (EE) 10: /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 (nouveau_pushbuf_space+0x47a) [0x7f3e8573d54a] août 23 09:04:20 lehrin gnome-shell[2561]: (EE) 11: /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so (nouveau_drm_screen_create+0x1f6cc) [0x7f3e8abec89c] août 23 09:04:20 lehrin gnome-shell[2561]: (EE) 12: /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so (nouveau_drm_screen_create+0x1fc33) [0x7f3e8abed183] août 23 09:04:20 lehrin gnome-shell[2561]: (EE) 13: /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so (__driDriverGetExtensions_zink+0x1fbfd) [0x7f3e8a43fa5d] août 23 09:04:20 lehrin gnome-shell[2561]: (EE) 14: /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so (__driDriverGetExtensions_zink+0x1667ab) [0x7f3e8a6ccdab] août 23 09:04:20 lehrin gnome-shell[2561]: (EE) 15: /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so (__driDriverGetExtensions_zink+0x3d46d) [0x7f3e8a47ab9d] août 23 09:04:20 lehrin gnome-shell[2561]: (EE) 16: /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so (__driDriverGetExtensions_zink+0x167b5f) [0x7f3e8a6cf59f] août 23 09:04:20 lehrin gnome-shell[2561]: (EE) 17: /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so (__driDriverGetExtensions_zink+0x167e92) [0x7f3e8a6d00c2] août 23 09:04:20 lehrin gnome-shell[2561]: (EE) 18: /usr/bin/Xwayland (glamor_create_gc+0xfb23) [0x558414a4a3c3] août 23 09:04:20 lehrin gnome-shell[2561]: (EE) 19: /usr/bin/Xwayland (glamor_create_gc+0x20b8) [0x558414a2ef18] août 23 09:04:20 lehrin gnome-shell[2561]: (EE) 20: /usr/bin/Xwayland (XkbDDXTerminateServer+0x3396) [0x558414b32ff6] août 23 09:04:20 lehrin gnome-shell[2561]: (EE) 21: /usr/bin/Xwayland (AddTraps+0x1fe6) [0x558414adac66] août 23 09:04:20 lehrin gnome-shell[2561]: (EE) 22: /usr/bin/Xwayland (SendErrorToClient+0x354) [0x558414b44674] août 23 09:04:20 lehrin gnome-shell[2561]: (EE) 23: /usr/bin/Xwayland (InitFonts+0x3b4) [0x558414b48624] août 23 09:04:20 lehrin gnome-shell[2561]: (EE) 24: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xea) [0x7f3e8c2b8cca] août 23 09:04:20 lehrin gnome-shell[2561]: (EE) 25: /usr/bin/Xwayland (_start+0x2a) [0x558414a1a28a] août 23 09:04:20 lehrin gnome-shell[2561]: (EE) août 23 09:04:20 lehrin gnome-shell[2561]: (EE) août 23 09:04:20 lehrin gnome-shell[2561]: Fatal server error: août 23 09:04:20 lehrin gnome-shell[2561]: (EE) Caught signal 6 (Aborted). Server aborting août 23 09:04:20 lehrin gnome-shell[2561]: (EE) Luc
Bug#968346: maybe linked to libdrm-nouveau2
Looking more precisely at the backtrace in the core file, the culprit seems to be here: #10 0x7f1c4420b5b2 in __assert_fail () from /lib/x86_64-linux-gnu/libc.so.6 #11 0x7f1c3d68143f in nouveau_pushbuf_data () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 which appears in a different form in the journalctl output: août 13 11:31:51 lehrin gnome-shell[14075]: Xwayland: ../nouveau/pushbuf.c:723: nouveau_pushbuf_data: Assertion `kref' failed. This looks a lot like bug #929130, registered more than one year ago for libdrm-nouveau2 package. Luc
Bug#968346: xwayland crashes randomly (core dumped) with nouveau driver
Package: xwayland Version: 2:1.20.8-2 Severity: normal Dear Maintainer, * What led up to the situation? I upgraded my hardware and installed a new motherboard/CPU/memory and basic graphic card. The new graphic card is a very basic MSI GeForce GT 710 2GD3H LP. Now xwayland crashed randomly, causing gnome-shell to end. I get a black screen first, and then a gnome shell log screen. I can log again in a new gnome shell session, but all graphic applications have been killed at crash time. The last crash happened while I had thunderbird and firefox opened but otherwise idle, and I was working on freecad. There was not special load on the machine. After I logged in again, I found a core file in my home directory. The core was created by xwayland. Opening the core file with gdb and printing the backtrace, I got this: Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/usr/bin/Xwayland :0 -rootless -noreset -accessx -core -auth /run/user/1000/.mu'. Program terminated with signal SIGABRT, Aborted. [Current thread is 1 (Thread 0x7f1c439d9a40 (LWP 14075))] (gdb) bt #0 0x7f1c44212db1 in raise () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f1c441fc537 in abort () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x55adc1a612da in OsAbort () #3 0x55adc1a66643 in ?? () #4 0x55adc1a67496 in FatalError () #5 0x55adc1a5e745 in ?? () #6 #7 0x7f1c44212db1 in raise () from /lib/x86_64-linux-gnu/libc.so.6 #8 0x7f1c441fc537 in abort () from /lib/x86_64-linux-gnu/libc.so.6 #9 0x7f1c441fc40f in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #10 0x7f1c4420b5b2 in __assert_fail () from /lib/x86_64-linux-gnu/libc.so.6 #11 0x7f1c3d68143f in nouveau_pushbuf_data () from /usr/lib/x86_64-linux- gnu/libdrm_nouveau.so.2 #12 0x7f1c3d6813a3 in nouveau_pushbuf_data () from /usr/lib/x86_64-linux- gnu/libdrm_nouveau.so.2 #13 0x7f1c3d6814bc in ?? () from /usr/lib/x86_64-linux- gnu/libdrm_nouveau.so.2 #14 0x7f1c3d6818df in ?? () from /usr/lib/x86_64-linux- gnu/libdrm_nouveau.so.2 #15 0x7f1c3d682399 in ?? () from /usr/lib/x86_64-linux- gnu/libdrm_nouveau.so.2 #16 0x7f1c42b12acf in ?? () from /usr/lib/x86_64-linux- gnu/dri/nouveau_dri.so #17 0x7f1c42bbc2a3 in ?? () from /usr/lib/x86_64-linux- gnu/dri/nouveau_dri.so #18 0x7f1c42bbee3e in ?? () from /usr/lib/x86_64-linux- gnu/dri/nouveau_dri.so #19 0x7f1c42bbef77 in ?? () from /usr/lib/x86_64-linux- gnu/dri/nouveau_dri.so #20 0x7f1c42bc05fe in ?? () from /usr/lib/x86_64-linux- gnu/dri/nouveau_dri.so #21 0x7f1c423685a8 in ?? () from /usr/lib/x86_64-linux- gnu/dri/nouveau_dri.so #22 0x7f1c425bc9c4 in ?? () from /usr/lib/x86_64-linux- gnu/dri/nouveau_dri.so #23 0x55adc190d798 in ?? () #24 0x55adc190dc56 in ?? () #25 0x55adc1947647 in miCopyRegion () #26 0x55adc1947d86 in miDoCopy () #27 0x55adc190e6a4 in ?? () #28 0x55adc19d0076 in ?? () #29 0x55adc19c7742 in ?? () #30 0x55adc19c7c1e in ?? () #31 0x55adc19c67cc in ?? () #32 0x55adc1909c73 in ?? () #33 0x55adc1909ec7 in ?? () #34 0x55adc1a57ec0 in ?? () #35 0x55adc1a57f28 in ?? () #36 0x55adc1a58165 in WaitForSomething () #37 0x55adc1a283d3 in ?? () #38 0x55adc1a2c5e4 in ?? () #39 0x7f1c441fdcca in __libc_start_main () from /lib/x86_64-linux- gnu/libc.so.6 #40 0x55adc18fe28a in _start () I also looked at journalctl and found the following lines that seem relevant to the problem: août 13 11:31:51 lehrin kernel: nouveau :2d:00.0: gr: TRAP ch 6 [007f97a000 Xwayland[14075]] août 13 11:31:51 lehrin kernel: nouveau :2d:00.0: gr: GPC0/TPC0/TEX: 8049 août 13 11:31:51 lehrin kernel: nouveau :2d:00.0: fifo: fault 00 [READ] at 00257000 engine 00 [GR] client 01 [GPC0/T1_0] reason 02 [PTE] on channel 6 [007f97a000 Xwayland[14075]] août 13 11:31:51 lehrin kernel: nouveau :2d:00.0: fifo: channel 6: killed août 13 11:31:51 lehrin kernel: nouveau :2d:00.0: fifo: runlist 0: scheduled for recovery août 13 11:31:51 lehrin kernel: nouveau :2d:00.0: fifo: engine 0: scheduled for recovery août 13 11:31:51 lehrin kernel: nouveau :2d:00.0: Xwayland[14075]: channel 6 killed! août 13 11:31:51 lehrin gnome-shell[14075]: nouveau: kernel rejected pushbuf: No such device août 13 11:31:51 lehrin gnome-shell[14075]: nouveau: ch6: krec 0 pushes 1 bufs 9 relocs 0 août 13 11:31:51 lehrin gnome-shell[14075]: nouveau: ch6: buf 0003 0004 0004 août 13 11:31:51 lehrin gnome-shell[14075]: nouveau: ch6: buf 0001 0008 0002 0002 0002 août 13 11:31:51 lehrin gnome-shell[14075]: nouveau: ch6: buf 0002 000b 0002 0002 août 13 11:31:51 lehrin gnome-shell[14075]: nouveau: ch6: buf 0003 000a 0002 0002 0002 août 13 11:31:51 lehrin gnome-shell[14075]: nouveau: ch6: buf 0004 0006 0004 0004 août 13 11:31:51 lehrin gnome-shell[14075]:
Bug#962379: r-cran-rmysql: crash of R from within RStudio
On Sun, 07 Jun 2020 10:10:50 +0200 Luc Castermans wrote: > Package: r-cran-rmysql > Version: 0.10.20-1+b1 > Severity: important > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate *** > > * What led up to the situation? > * What exactly did you do (or not do) that was effective (or > ineffective)? > * What was the outcome of this action? > * What outcome did you expect instead? > > I run exactly the same script on two different machines, both running Debian. > The itself script is quite old and stable. I run it weekly from RStudio. Since the Debian updates > last week (or week before) as soon as I run the script in RStudio I get a R crash. If I run it > a few more times the crashes disappear. > > Below the essential part of the script. I do not know how to debug it. The crash occurs likely in the dbConnect() call. > > I would not have reported it if it would occur on one of my machines, but is it now occurs on a very different machine, > I think it is something structural and needs to be reported. > > > library(RMySQL) > library(tidyverse) > library(lubridate) > > > con <- dbConnect(RMySQL::MySQL(), > username = xx, > password = yy, > host = bla, > dbname = 'blabla) > > rs <- dbSendQuery(con, "SQL Query;"); > df_raw <- dbFetch(rs, n = -1) > > > > > *** End of the template - remove these template lines *** > > > -- System Information: > Debian Release: bullseye/sid > APT prefers testing > APT policy: (990, 'testing'), (500, 'experimental'), (500, 'unstable') > Architecture: amd64 (x86_64) > > Kernel: Linux 5.5.0-1-amd64 (SMP w/4 CPU cores) > Kernel taint flags: TAINT_UNSIGNED_MODULE > Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8), LANGUAGE=nl (charmap=UTF-8) > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages r-cran-rmysql depends on: > ii libc6 2.31-0experimental2 Hi, After upgrading RStudio from 1.25033 to 1.3.959 the bug is solved. Luc -- m.vr.gr. Luc Castermans mailto:luc.casterm...@gmail.com
Bug#962379: r-cran-rmysql: crash of R from within RStudio
Package: r-cran-rmysql Version: 0.10.20-1+b1 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? I run exactly the same script on two different machines, both running Debian. The itself script is quite old and stable. I run it weekly from RStudio. Since the Debian updates last week (or week before) as soon as I run the script in RStudio I get a R crash. If I run it a few more times the crashes disappear. Below the essential part of the script. I do not know how to debug it. The crash occurs likely in the dbConnect() call. I would not have reported it if it would occur on one of my machines, but is it now occurs on a very different machine, I think it is something structural and needs to be reported. library(RMySQL) library(tidyverse) library(lubridate) con <- dbConnect(RMySQL::MySQL(), username = xx, password = yy, host = bla, dbname = 'blabla) rs <- dbSendQuery(con, "SQL Query;"); df_raw <- dbFetch(rs, n = -1) *** End of the template - remove these template lines *** -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'experimental'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.5.0-1-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8), LANGUAGE=nl (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages r-cran-rmysql depends on: ii libc62.31-0experimental2 ii libmariadb3 1:10.3.22-1 ii r-base-core [r-api-4.0] 4.0.1-1 ii r-cran-dbi 1.1.0-3 r-cran-rmysql recommends no packages. r-cran-rmysql suggests no packages. -- no debconf information
Bug#953683: firmware-linux-nonfree: module mt76x0e for MEDIATEK MT7630e missing
Package: firmware-linux-nonfree Version: 20190717-2 Severity: normal Tags: patch Dear Maintainer, For the MEDIATEK Corp. MT7630e the module is missing. In the kernel config file the configuration item CONFIG_MT76x0E is commented out. I did uncomment it, after which the module was built correctly. *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (600, 'experimental'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8), LANGUAGE=nl (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages firmware-linux-nonfree depends on: ii firmware-amd-graphics 20190717-2 ii firmware-misc-nonfree 20190717-2 Versions of packages firmware-linux-nonfree recommends: ii amd64-microcode 3.20191218.1 ii intel-microcode 3.20191115.2 firmware-linux-nonfree suggests no packages. -- no debconf information
Bug#952731: xkb-data: Italian keyboard layout not working in some apps
Le 28/02/2020 à 20:50, Timo Aaltonen a écrit : > > I'm pretty sure the reason for the failure is that our xkbcomp is too > old, the newer versions ignore errors caused by having keycodes above > 255.. and launching Xwayland in weston clearly shows a bunch of errors > from xkbcomp. Our version (1.4.0) is almost 2y old and this was fixed > upstream in 1.4.1 in June 2018. > > So I'll update x11-xkb-utils, thanks for the patience.. > I've updated x11-xkb-utils and xkb-data (to 2.29-2) together with other related packages with the update of debien sid today. This fixes the problem [for me]. Thanks and regards Jean-Luc
Bug#952731: xkb-data: Italian keyboard layout not working in some apps
Le 28/02/2020 à 15:55, Gunnar Hjalmarsson a écrit : > On 2020-02-28 15:20, Michael Meskes wrote: >> Anyway, it seems all layouts are not working, for me it's "de". A >> manual "setxkbmap de" does fix the issue, though. > > That makes me suspect that there is some issue in some GNOME package on > Debian, which is not present on Ubuntu for some reason. > > @Jean-Luc: Can you please run: > > setxkbmap fr -variant oss > > and let us know if that workaround makes a difference for you too. > This is overwritten by gnome. If I enter the connand it works for the session. If I reboot, I've the keyboard is back to us. I already tried that before reporting the bug. --- From an other message > > I see from the gsettings command output that you have two layouts > enabled, and both those layouts work as expected for me. > > Can you please switch to "French (legacy, alt.)" and then back to > "French (alt.)" and let us know if it makes a difference. Can you also >check if the "French (legacy, alt.)" layout works as expected. Nope, it is the same. J-L
Bug#952731: xkb-data: Italian keyboard layout not working in some apps
Hi
Le 28/02/2020 à 13:29, Gunnar Hjalmarsson a écrit :
> I tested on Ubuntu, which has the very same version of xkb-data
> (2.29-1), and both the Italian - it and French (alt.) - fr+oss layouts
> seem to work for me.
>
> $ gsettings get org.gnome.desktop.input-sources sources
> [('xkb', 'se'), ('xkb', 'us'), ('xkb', 'it'), ('xkb', 'fr+oss')]
> @Domenico and @Jean-Luc: It would be good if you could clarify exactly
> which keyboard layouts were problematic for you, and in which way(s).
Well, maybe it is difficult to explain as everything is… in French ;)
but please see the attached screenshot of what I get from the gnome
preferences.
If I use 2.26, I get the attached layout [Français(variante)] from the
preferences AND it works as exected.
I suppose "Français(variante)" is "French(alt.)"
If I use 2.29, I get the same layout from the preferences but the actual
keybord is a us (at least qwerty) layout.
If I switch from 2.26/2.29 (and restart the window manager), I
repeatedly get the same behaviour (correct with 2.26 et wrong with 2.29).
> Good if you too run the above command and show us the output.
I get the following, with both the version of xkb-data.[('xkb',
'fr+oss'), ('xkb', 'fr+latin9')]
>
> Btw, @Domenico: Is the "Use the same source for all windows" option
> enabled in Settings?
Yes and BTW, I did nothing but a reboot after upgrading xkb-data.
Bug#952731: xkb-data: Same for fr layout, reverting to 2.26-2 fixes the problem
Package: xkb-data Followup-For: Bug #952731 Hi, fr [fr (variant) under gnome] stops also to work after upgrading xkb-data. Reverting to 2.26-2 fixes the problem. Regards Jean-Luc -- System Information: Debian Release: bullseye/sid APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.6.0-rc3-i7-0.1 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) -- no debconf information
Bug#947356: missing firmware rtl8125a-3.fw
On Tue, 14 Jan 2020 20:07:18 +0100 didier wrote: > Same problem here > > W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for > module r8169 > > firmware-realtek 20190717-2 > > kernel ; 5.4.0-2-amd64 #1 SMP Debian 5.4.8-1 (2020-01-05) x86_64 > > > > Same here Processing triggers for libvlc-bin:amd64 (1:3.0.8-dmo14) ... Processing triggers for initramfs-tools (0.136) ... update-initramfs: Generating /boot/initrd.img-5.4.0-4-amd64 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for module r8169 root@canne:~# ^C root@canne:~# uname -a Linux canne 5.4.0-4-amd64 #1 SMP Debian 5.4.19-1 (2020-02-13) x86_64 GNU/Linux root@canne:~# -- m.vr.gr. Luc Castermans mailto:luc.casterm...@gmail.com
Bug#951495: linux-image-4.19.0-8-armmp: unable to boot an odroid xu4, cannot load rootfs from sdcard by UUID
Package: src:linux Version: 4.19.98-1 Severity: normal Dear Maintainer, I encountered a problem when upgrading linux-image from 4.0.19-6 to 4.0.19-8 on two odroid xu4 servers. They do not boot anymore when using the vmlinuz-4.19.0-8-armmp image installed on /boot (but they still boot if I use the older vmlinuz-4.19.0-6-armmp). Using a serial console to check the boot process, I get these upon failure: Starting version 241 Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... done. Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... done. [ 10.468381] dma-pl330 388.adma: Loaded driver for PL330 DMAC-241330 [ 10.473603] dma-pl330 388.adma: DBUFF-4x8bytes Num_Chans-6 Num_Peri-16 Num_Events-6 [ 10.503820] dma-pl330 388.adma: PM domain MAU will not be powered off Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. ... lots of similar lines removed ... Begin: Running /scripts/local-block ... done. done. Gave up waiting for root file system device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Missing modules (cat /proc/modules; ls /dev) ALERT! UUID=e139ce78-9841-40fe-8823-96a304a09859 does not exist. Dropping to a shell! BusyBox v1.30.1 (Debian 1:1.30.1-4) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) So I ran the sugested commands: - cat /proc/modules returned absolutely nothing - ls /dev liste reported the following list, where there are no "disk" directory, hence no /dev/disk/by-uuid: apm_biosnetwork_throughput tty40 charnulltty41 console porttty42 cpu_dma_latency psaux tty43 fd ptmxtty44 fullpts tty45 gpiochip0 random tty46 gpiochip1 snapshottty47 gpiochip10 stderr tty48 gpiochip11 stdin tty49 gpiochip12 stdout tty5 gpiochip13 tty tty50 gpiochip14 tty0tty51 gpiochip15 tty1tty52 gpiochip16 tty10 tty53 gpiochip17 tty11 tty54 gpiochip18 tty12 tty55 gpiochip19 tty13 tty56 gpiochip2 tty14 tty57 gpiochip20 tty15 tty58 gpiochip21 tty16 tty59 gpiochip22 tty17 tty6 gpiochip23 tty18 tty60 gpiochip24 tty19 tty61 gpiochip25 tty2tty62 gpiochip26 tty20 tty63 gpiochip27 tty21 tty7 gpiochip28 tty22 tty8 gpiochip29 tty23 tty9 gpiochip3 tty24 ttyS0 gpiochip30 tty25 ttyS1 gpiochip31 tty26 ttyS2 gpiochip32 tty27 ttyS3 gpiochip33 tty28 ttySAC0 gpiochip34 tty29 ttySAC1 gpiochip35 tty3ttySAC2 gpiochip4 tty30 ttySAC3 gpiochip5 tty31 urandom gpiochip6 tty32 vcs gpiochip7 tty33 vcs1 gpiochip8 tty34 vcsa gpiochip9 tty35 vcsa1 input tty36 vcsu kmsgtty37 vcsu1 mem tty38 vga_arbiter memory_bandwidthtty39 zero network_latency tty4 - cat /proc/cmdline output was: console=tty1 console=ttySAC2,115200n8 root=UUID=e139ce78-9841-40fe-8823-96a304a09859 rootwait ro fsck.repair=yes net.ifnames=0 smsc95xx.macaddr=00:1e:06:61:7a:39 This commandline comes from the uboot and is the one I epxected, and the one that works with previous kernel image. This command line looks for the rootfs using its UUID. The previous kernel image found the rootfs directly, but the new kernel image does not find it anymore. -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information Hardware: SAMSUNG EXYNOS (Flattened Device Tree) Revision: Device Tree model: Hardkernel Odroid XU4 ** PCI devices: not available ** USB devices: not available -- System Information: Debian Release: 10.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: armhf (armv7l) Kernel: Linux 4.19.0-6-armmp
Bug#949733: python-pip: 'pip install' don't work for python2 in Debian10
I did use the system python command, it was a pip 9 version and i hacked it by changing the line "from pip._internal import main" to "from pip import main" then i could upgrade to pip 20.0.1 and now it works fine Le 25/01/2020 à 23:56, Andreas Beckmann a écrit : Control: tag -1 = moreinfo unreproducible On Fri, 24 Jan 2020 10:17:34 +0100 joanluc wrote: When invoking `usr/bin/pip' with any command of it, the program crashes with the message : "Traceback (most recent call last): File "/usr/bin/pip", line 9, in from pip._internal import main ImportError: No module named _internal" Hi, I cannot reproduce this. The pip._internal module should be located at /usr/lib/python2.7/dist-packages/pip/_internal/* Are there any local environment variables on your system that alter the python search path? Are you using the system python command or do you have a "special" python installation? Is anything corrupted? (e.g. check with debsums) Andreas -- Jean-Luc LABORDE (Joan-Luc Labòrda) CoFo CRPP 0556.84.30.13
Bug#948921: linux-image-5.4.0-2-amd64: decrypting root partition does not work on 5.4.0 (works on 5.3.0) with decrypt_keyctl
Hi Salvatore, Le 2020-01-15 21:24, Salvatore Bonaccorso a écrit : Your issue sounds like #948593. In case yes, we should reassign and merge it with that bug. Indeed, it is a duplicate! I added "essiv" to /etc/initramfs-tools/modules and regenerated the initramfs and everything worked flawlessly. Thanks a lot, and sorry to not have found this bug report. The fact my other laptop worked is probably due to it having been set up last year whereas the machine that had problem has been set up several years before, so probably with different default encryption. Thanks again! Luc Regards, Salvatore
Bug#949017: discus: invalid syntax while size > (0.9999999999 * pow(10L, 3))
Package: discus Version: 0.2.9-11 Severity: grave Justification: renders package unusable Hi, I get the following: ~/ discus File "/usr/bin/discus", line 121 while size > (0.99 * pow(10L, 3)): ^ SyntaxError: invalid syntax Regards Jean-Luc -- System Information: Debian Release: bullseye/sid APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.5.0-rc6-i7-0.1 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages discus depends on: ii python 2.7.17-2 discus recommends no packages. discus suggests no packages. -- no debconf information
Bug#948921: linux-image-5.4.0-2-amd64: decrypting root partition does not work on 5.4.0 (works on 5.3.0) with decrypt_keyctl
Here are some additional informations about the problem. I rechecked it was not a keyboard layout problem by setting up an additional luks key, a very short one that used only keys that were at the same position in both qwerty and azerty. It does not work, so it's definitely not a keyboard problem. The error I get on boot is as follows: Caching passphrase for sdb1_crypt:*** [ 15.212421] device-mapper: table: 253:0: crypt: Error allocating crypto tfm device-mapper: reload ioctl on failed: No such file or directory cryptsetup: ERROR: sdb1_crypt: cryptsetup failed, bad password or options? Caching passphrase for sdb1_crypt: I tried to use a key file instead of a key typed by user just like I did on the other laptop. I do not want to use this method for this specific machine for security reasons (it should not be abel to boot unattended), but tried it temporarily. I regenerated the initramfs after changing the /etc/crypttab file, but it didn't work either. When generating initramfs, I got the following warning, so it may explain why it didn't work. cryptsetup: WARNING: Skipping root target sdb1_crypt: uses a key file In this case (booting with a key file), the error was different: Volume group "vg-ssd" not found Cannot process volume group vg-ssd Volume group "vg-hdd" not found Cannot process volume group vg-hdd Volume group "vg-hdd" not found Cannot process volume group vg-hdd Volume group "vg-hdd" not found ... Cannot process volume group vg-hdd Volume group "vg-hdd" not found Cannot process volume group vg-hdd mdadm: error opening /dev/md?*: No such file or directory Cannot process volume group vg-hdd Volume group "vg-hdd" not found then the boot process drops to initramfs shell. Exploring the filesystem at this stage, I didn't find the key file. best regards, Luc
Bug#948921: linux-image-5.4.0-2-amd64: decrypting root partition does not work on 5.4.0 (works on 5.3.0) with decrypt_keyctl
Package: src:linux Version: 5.4.8-1 Severity: normal Dear Maintainer, * What led up to the situation? Upgrading kernel from 5.3.0 to 5.4.0 * What exactly did you do (or not do) that was effective (or ineffective)? Booting on the new kernel always fail with an error message stating I entered the wrong passphrase. Selecting kernel 5.3.0 on grub works with the same passphrase. I am sure I did not mixed passphrases, as I tried tens of times with each kernel, result was 100% failure with 5.4.0, 100% success with 5.3.0. I also checked if there was not a problem with keyboard layout, typing the passphrase as if the keyboard was configured in English QWERTY (my keyboard is a French one with AZERTY layout). It also failed 100% of time when selecting kernel 5.4.0. I regenerated several time the initramfs using update-initramfs -k all -u, this didn't change anything: kernel 5.4.0 fails to decrypt, kernel 5.3.0 succeeded. On another laptop with a comparable setting EXCEPT that the key is stored in a file, the boot completes in 5.4.0. So only the combination decrypt_keyctl and kernel 5.4.0 fails. -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: Dell Inc. product_name: XPS L521X product_version: A13 chassis_vendor: Dell Inc. chassis_version: A13 bios_vendor: Dell Inc. bios_version: A13 board_vendor: Dell Inc. board_name: 063M0K board_version: A00 ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation 3rd Gen Core processor DRAM Controller [8086:0154] (rev 09) Subsystem: Dell 3rd Gen Core processor DRAM Controller [1028:054e] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: ivb_uncore 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port [8086:0151] (rev 09) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:054e] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: i915 00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller [8086:1e31] (rev 04) (prog-if 30 [XHCI]) Subsystem: Dell 7 Series/C210 Series Chipset Family USB xHCI Host Controller [1028:054e] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: xhci_hcd 00:16.0 Communication controller [0780]: Intel Corporation 7 Series/C216 Chipset Family MEI Controller #1 [8086:1e3a] (rev 04) Subsystem: Dell 7 Series/C216 Chipset Family MEI Controller [1028:054e] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: mei_me 00:1a.0 USB controller [0c03]: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #2 [8086:1e2d] (rev 04) (prog-if 20 [EHCI]) Subsystem: Dell 7 Series/C216 Chipset Family USB Enhanced Host Controller [1028:054e] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: ehci-pci 00:1b.0 Audio device [0403]: Intel Corporation 7 Series/C216 Chipset Family High Definition Audio Controller [8086:1e20] (rev 04) Subsystem: Dell 7 Series/C216 Chipset Family High Definition Audio Controller [1028:054e] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: snd_hda_intel 00:1c.0 PCI bridge [0604]: Intel Corporation 7 Series/C216 Chipset Family PCI Express Root Port 1 [8086:1e10] (rev c4) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr-
Bug#930563: Can not start freecad
Hallo Bernhard, My system only has a single GPU (Nvidia GTX 970, see attached config) installed on a robust tower powered by a i7-4790K with plenty of RAM. It must be package related as the package (Stretch) was running without any issue. Attached my config. Cheers Jean-Luc Le 8/01/20 à 16:01, Bernhard Übelacker a écrit : Hello Gulfstream, hello Jean-Luc, this report got opened mentioning a "Thinkpad P1". Reading through some pages about that device, it looks like it contains some "hybrid graphics". Maybe you both could confirm that your devices have such "hybrid graphics", and if yes, maybe you could give some more information of both graphic devices and how the switching between them is configured? (I don't have such a device accessible.) Kind regards, Bernhard Device Class Description == system All Series (All) busZ97-A memory 64KiB BIOS memory 24GiB System Memory memory 8GiB DIMM DDR3 Synchronous 2133 MHz (0.5 ns) memory 4GiB DIMM DDR3 Synchronous 2133 MHz (0.5 ns) memory 4GiB DIMM DDR3 Synchronous 2133 MHz (0.5 ns) memory 8GiB DIMM DDR3 Synchronous 2133 MHz (0.5 ns) processor Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz memory 256KiB L1 cache memory 1MiB L2 cache memory 8MiB L3 cache bridge 4th Gen Core Processor DRAM Controller bridge Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller displayGM204 [GeForce GTX 970] multimedia GM204 High Definition Audio Controller bus9 Series Chipset Family USB xHCI Controller usb2busxHCI Host Controller busUSB2.0 Hub input USB Receiver scsi8 storageNokia 7 plus /dev/sr1disk File-CD Gadget /dev/sr1disk communication CSR8510 A10 input Logitech Illuminated Keyboard genericCanoScan usb4busxHCI Host Controller scsi6 storageLRWM04U /dev/sdedisk LRWM04U /dev/sdedisk scsi7 storageTranscend /dev/sdddisk SD Transcend /dev/sdddisk busUSB3.0 Hub communication 9 Series Chipset Family ME Interface #1 eno1networkEthernet Connection (2) I218-V bus9 Series Chipset Family USB EHCI Controller #2 usb1busEHCI Host Controller busUSB hub multimedia 9 Series Chipset Family HD Audio Controller bridge 9 Series Chipset Family PCI Express Root Port 1 bridge 82801 PCI Bridge bridge ASM1083/1085 PCIe to PCI Bridge bus9 Series Chipset Family USB EHCI Controller #1 usb3busEHCI Host Controller busUSB hub bridge 9 Series Chipset Family Z97 LPC Controller scsi0 storage9 Series Chipset Family SATA Controller [AHCI Mode] /dev/sdadisk 256GB Crucial_CT256MX1 /dev/sda1 volume 238GiB EXT4 volume /dev/sdbdisk 2TB ST2000DM001-1CH1 /dev/sdb1 volume 1863GiB EXT4 volume /dev/sdcdisk 500GB Samsung SSD 860 /dev/sdc1 volume 465GiB EXT4 volume /dev/cdrom disk CDDVDW SH-224FB bus9 Series Chipset Family SMBus Controller system PnP device PNP0c01 system PnP device PNP0c02 system PnP device PNP0b00 genericPnP device INT3f0d system PnP device PNP0c02 system PnP device PNP0c02 communication PnP device PNP0501 system PnP device PNP0c02 power To Be Filled By O.E.M.
Bug#930563: Can not start freecad
Hallo Bernard, You nailed it! That was the proprietary Nvidia driver that was the culprit. I uninstalled it and installed the debian nvidia-driver and nvidia-libopencl1 packages. Freecad is up and running now. The nvidia-libopencl1 package is not strictly required by Freecad I believe, but I need it for darktable. Thanks for your help. Cheers. Jean-Luc Le 13/01/20 à 23:20, Bernhard Übelacker a écrit : Hello Jean-Luc, thanks for your information. Please use the reply-to-all button to have the information forwarded to the bug report. Am 08.01.20 um 17:21 schrieb Jean-Luc Lacroix: Hallo Bernhard, My system only has a single GPU (Nvidia GTX 970, see attached config) installed on a robust tower powered by a i7-4790K with plenty of RAM. It must be package related as the package (Stretch) was running without any issue. Attached my config. Cheers Jean-Luc Find below the information of libGLdispatch.so.0 from a Buster VM, without any nvidia drivers. There exists the _glapi_tls_Current symbol. After installing the package nvidia-driver the files and links libGLdispatch.so.0* and libOpenGL.so.0* were unchanged. Therefore the question, where does your libGLdispatch.so.0 come from? How did you install the nvidia driver - by the Debian package or did you use the installer from NVidia? Kind regards, Bernhard # Buster stable without nvidia-drivre installed: benutzer@debian:~$ nm -D /usr/lib/x86_64-linux-gnu/libGLdispatch.so.0 | grep tls D _glapi_tls_Current benutzer@debian:~$ ls -la /usr/lib/x86_64-linux-gnu/libGLdispatch.so* /usr/lib/x86_64-linux-gnu/libOpenGL.so.0* lrwxrwxrwx 1 root root 22 Aug 10 2018 /usr/lib/x86_64-linux-gnu/libGLdispatch.so.0 -> libGLdispatch.so.0.0.0 -rw-r--r-- 1 root root 637384 Aug 10 2018 /usr/lib/x86_64-linux-gnu/libGLdispatch.so.0.0.0 lrwxrwxrwx 1 root root 18 Aug 10 2018 /usr/lib/x86_64-linux-gnu/libOpenGL.so.0 -> libOpenGL.so.0.0.0 -rw-r--r-- 1 root root 194880 Aug 10 2018 /usr/lib/x86_64-linux-gnu/libOpenGL.so.0.0.0 benutzer@debian:~$ dpkg -S /usr/lib/x86_64-linux-gnu/libGLdispatch.so.0 libglvnd0:amd64: /usr/lib/x86_64-linux-gnu/libGLdispatch.so.0 benutzer@debian:~$ dpkg -S /usr/lib/x86_64-linux-gnu/libOpenGL.so.0 libopengl0:amd64: /usr/lib/x86_64-linux-gnu/libOpenGL.so.0 benutzer@debian:~$ dpkg -l | grep -E "libglvnd0|libopengl0" ii libglvnd0:amd64 1.1.0-1 amd64Vendor neutral GL dispatch library ii libopengl0:amd64 1.1.0-1 amd64Vendor neutral GL dispatch library -- OpenGL support
Bug#930563: Same problem when starting FreeCAD
Hello maintainers, I also have this reported error when starting FreeCAD. I had no issue with previous stable running with the same proprietary Nvidia driver. Here below the output of various troubleshooting commands: [quote] $ aptitude versions freecad i 0.18~pre1+dfsg1-5 stable 500 $ ldd /usr/bin/freecad | grep libOpen libOpenGL.so.0 => /lib/x86_64-linux-gnu/libOpenGL.so.0 (0x7f441a863000) $ ls -la /lib/x86_64-linux-gnu/libOpenGL.so* /usr/lib/x86_64-linux-gnu/libOpenGL.so *lrwxrwxrwx 1 root root 18 Aug 10 2018 /lib/x86_64-linux-gnu/libOpenGL.so -> libOpenGL.so.0.0.0 lrwxrwxrwx 1 root root 18 Aug 10 2018 /lib/x86_64-linux-gnu/libOpenGL.so.0 -> libOpenGL.so.0.0.0 -rw-r--r-- 1 root root 194880 Aug 10 2018 /lib/x86_64-linux-gnu/libOpenGL.so.0.0.0 lrwxrwxrwx 1 root root 18 Aug 10 2018 /usr/lib/x86_64-linux-gnu/libOpenGL.so -> libOpenGL.so.0.0.0 lrwxrwxrwx 1 root root 18 Aug 10 2018 /usr/lib/x86_64-linux-gnu/libOpenGL.so.0 -> libOpenGL.so.0.0.0 -rw-r--r-- 1 root root 194880 Aug 10 2018 libOpenGL.so.0.0.0 $ nm -D /usr/lib/x86_64-linux-gnu/libOpenGL.so.0 | grep tls U _glapi_tls_Current $ nm -D /lib/x86_64-linux-gnu/libOpenGL.so.0.0.0 | grep tls U _glapi_tls_Current $ dpkg -S /usr/lib/x86_64-linux-gnu/libOpenGL.so.0 libopengl0:amd64: /usr/lib/x86_64-linux-gnu/libOpenGL.so.0 $ dpkg -l | grep libopengl0 ii libopengl0:amd64 1.1.0-1 amd64 Vendor neutral GL dispatch library -- OpenGL support $ dpkg -l | grep libglvnd ii libglvnd-core-dev:amd64 1.1.0-1 amd64 Vendor neutral GL dispatch library -- core development files ii libglvnd-dev:amd64 1.1.0-1 amd64 Vendor neutral GL dispatch library -- development files ii libglvnd0:amd64 1.1.0-1 amd64 Vendor neutral GL dispatch library $ ls -la /usr/lib/x86_64-linux-gnu/libGLdispatch.so* lrwxrwxrwx 1 root root 22 déc 28 10:19 /usr/lib/x86_64-linux-gnu/libGLdispatch.so -> libGLdispatch.so.0.0.0 -rwxr-xr-x 1 root root 732400 sep 7 18:02 /usr/lib/x86_64-linux-gnu/libGLdispatch.so.0 $ nm -D /usr/lib/x86_64-linux-gnu/libGLdispatch.so.0 | grep tls < nihil > [/unquote] Cheers. Jean-Luc
Bug#945604: linux-source-5.4: Failed to build linux-source-5.4 in efi_set_secure_boot
Package: linux-source-5.4 Version: 5.4-1~exp1 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I failed to build 5.4 with the following message: DESCEND objtool CALLscripts/atomic/check-atomics.sh CALLscripts/checksyscalls.sh CHK include/generated/compile.h CHK kernel/kheaders_data.tar.xz GEN .version CHK include/generated/compile.h UPD include/generated/compile.h CC init/version.o AR init/built-in.a LD vmlinux.o MODPOST vmlinux.o MODINFO modules.builtin.modinfo LD .tmp_vmlinux1 ld: drivers/firmware/efi/secureboot.o: in function `efi_set_secure_boot': /usr/src/linux/drivers/firmware/efi/secureboot.c:32: undefined reference to `lock_kernel_down' make: *** [Makefile:1065: vmlinux] Error 1 I use make-kpkg to (try to) build the package. The genuine package from kernel.org built fine. Please find attached my .config Regards Jean-Luc - -- System Information: Debian Release: bullseye/sid APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.4.0-i7-0.1 (SMP w/8 CPU cores) Kernel taint flags: TAINT_OOT_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linux-source-5.4 depends on: ii binutils 2.33.1-4 ii xz-utils 5.2.4-1+b1 Versions of packages linux-source-5.4 recommends: ii bc1.07.1-2+b2 ii bison 2:3.4.2+dfsg-1 ii flex 2.6.4-6.2 ii gcc 4:9.2.1-3.1 ii libc6-dev [libc-dev] 2.29-3 ii linux-config-5.4 5.4-1~exp1 ii make 4.2.1-1.2 Versions of packages linux-source-5.4 suggests: ii libncurses-dev [ncurses-dev] 6.1+20191019-1 ii libqt4-dev4:4.8.7+dfsg-19 ii pkg-config0.29-6 - -- no debconf information -BEGIN PGP SIGNATURE- iF0EARECAB0WIQT5el3FKLtmYO4UlQtR0YZfPMac0AUCXd7X4gAKCRBR0YZfPMac 0JNkAJ9L+UY2XktGf8QiSofB/42inzQdDwCgqZwkjl+OQMh2z8H2adU5h7MErvc= =1aDu -END PGP SIGNATURE- # # Automatically generated file; DO NOT EDIT. # Linux/x86 5.4.0 Kernel Configuration # # # Compiler: gcc (Debian 9.2.1-20) 9.2.1 20191126 # CONFIG_CC_IS_GCC=y CONFIG_GCC_VERSION=90201 CONFIG_CLANG_VERSION=0 CONFIG_CC_CAN_LINK=y CONFIG_CC_HAS_ASM_GOTO=y CONFIG_CC_HAS_ASM_INLINE=y CONFIG_CC_HAS_WARN_MAYBE_UNINITIALIZED=y CONFIG_IRQ_WORK=y CONFIG_BUILDTIME_EXTABLE_SORT=y CONFIG_THREAD_INFO_IN_TASK=y # # General setup # CONFIG_INIT_ENV_ARG_LIMIT=32 # CONFIG_COMPILE_TEST is not set # CONFIG_HEADER_TEST is not set CONFIG_LOCALVERSION="" # CONFIG_LOCALVERSION_AUTO is not set CONFIG_BUILD_SALT="" CONFIG_HAVE_KERNEL_GZIP=y CONFIG_HAVE_KERNEL_BZIP2=y CONFIG_HAVE_KERNEL_LZMA=y CONFIG_HAVE_KERNEL_XZ=y CONFIG_HAVE_KERNEL_LZO=y CONFIG_HAVE_KERNEL_LZ4=y # CONFIG_KERNEL_GZIP is not set # CONFIG_KERNEL_BZIP2 is not set # CONFIG_KERNEL_LZMA is not set CONFIG_KERNEL_XZ=y # CONFIG_KERNEL_LZO is not set # CONFIG_KERNEL_LZ4 is not set CONFIG_DEFAULT_HOSTNAME="(none)" CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_SYSVIPC_SYSCTL=y CONFIG_POSIX_MQUEUE=y CONFIG_POSIX_MQUEUE_SYSCTL=y CONFIG_CROSS_MEMORY_ATTACH=y CONFIG_USELIB=y CONFIG_AUDIT=y CONFIG_HAVE_ARCH_AUDITSYSCALL=y CONFIG_AUDITSYSCALL=y # # IRQ subsystem # CONFIG_GENERIC_IRQ_PROBE=y CONFIG_GENERIC_IRQ_SHOW=y CONFIG_GENERIC_IRQ_EFFECTIVE_AFF_MASK=y CONFIG_GENERIC_PENDING_IRQ=y CONFIG_GENERIC_IRQ_MIGRATION=y CONFIG_IRQ_DOMAIN=y CONFIG_IRQ_DOMAIN_HIERARCHY=y CONFIG_GENERIC_MSI_IRQ=y CONFIG_GENERIC_MSI_IRQ_DOMAIN=y CONFIG_GENERIC_IRQ_MATRIX_ALLOCATOR=y CONFIG_GENERIC_IRQ_RESERVATION_MODE=y CONFIG_IRQ_FORCED_THREADING=y CONFIG_SPARSE_IRQ=y # CONFIG_GENERIC_IRQ_DEBUGFS is not set # end of IRQ subsystem CONFIG_CLOCKSOURCE_WATCHDOG=y CONFIG_ARCH_CLOCKSOURCE_DATA=y CONFIG_ARCH_CLOCKSOURCE_INIT=y CONFIG_CLOCKSOURCE_VALIDATE_LAST_CYCLE=y CONFIG_GENERIC_TIME_VSYSCALL=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y CONFIG_GENERIC_CLOCKEVENTS_MIN_ADJUST=y CONFIG_GENERIC_CMOS_UPDATE=y # # Timers subsystem # CONFIG_TICK_ONESHOT=y CONFIG_NO_HZ_COMMON=y # CONFIG_HZ_PERIODIC is not set CONFIG_NO_HZ_IDLE=y # CONFIG_NO_HZ_FULL is not set # CONFIG_NO_HZ is not set CONFIG_HIGH_RES_TIMERS=y # end of Timers subsystem # CONFIG_PREEMPT_NONE is not set CONFIG_PREEMPT_VOLUNTARY=y # CONFIG_PREEMPT is not set # # CPU/Task time and stats accounting # CONFIG_TICK_CPU_ACCOUNTING=y # CONFIG_VIRT_CPU_ACCOUNTING_GEN is not set # CONFIG_IRQ_TIME_ACCOUNTING is not set CONFIG_BSD_PROCESS_ACCT=y CONFIG_BSD_PROCESS_ACCT_V3=y CONFIG_TASKSTATS=y CONFIG_TASK_DELAY_ACCT=y # CONFIG_TASK_XACCT is not set # CONFIG_PSI is not set # end of CPU/Task time and stats accounting CONFIG_CPU_ISOLATION=y # # RCU Subsystem # CONFIG_TREE_RCU=y # CONFIG_RCU_EXPERT is not set CO
Bug#451940: אני מקווה לשמוע ממך
Hello my dear.pdf Description: Adobe PDF document
Bug#928411: debian-installer: [armfh] Buster RC1: "hit any key" fails to stop autoboot sequence in SD card images
Package: debian-installer Version: Buster RC1 Severity: normal Tags: d-i Dear Maintainer, I tried testing Buster RC1 SD card images on BananaPI M1+. I took the firmware from http://ftp.nl.debian.org/debian/dists/testing/main/installer-armhf/current/images/netboot/SD-card-images/firmware.BananaPro.img.gz following http://ftp.nl.debian.org/debian/dists/testing/main/installer-armhf/current/images/netboot/SD-card-images/README.concatenateable_images. When booting the SD card, the "Hit any key to stop autoboot:" does not work. Key hits from the connected keyboard are ignored. The (auto)boot sequence goes on when it should stop and give access to u-boot prompt. This prevents using tty1 as a console as described here: https://wiki.debian.org/InstallingDebianOn/Allwinner#Installing_from_an_SD_card_image (no access to u-boot prompt). This works with Stretch installer (same keyboard). The USB keybord is detected though by Buster installer as later in the boot sequence, it is possible to reboot the board with Ctrl-Alt-Del. Best regards, Frédéric Lehobey
Bug#927887: Race condition on boot between cups and sssd
Coule you please rénové me from your email stream. Le mer. 24 avr. 2019 12:27 PM, Victor Tapia a écrit : > Package: cups > Version: 2.2.10-6 > > Problem description: > > When cups has set the "SystemGroup" directive to an external group > provided through sss and cups starts before sssd has finished booting, > cups will crash because the group does not exist. For instance, with a > group named lpadmins@tests.local served from Active Directory through > sssd, if the sssd service hasn't booted before cups: > > Mar 27 10:10:33 cups-sssd systemd[1]: Started CUPS Scheduler. > Mar 27 10:10:33 cups-sssd systemd[1]: Started CUPS Scheduler. > Mar 27 10:10:33 cups-sssd systemd[1]: Started Make remote CUPS printers > available locally. > Mar 27 10:10:33 cups-sssd cupsd[21463]: Unknown SystemGroup > "lpadmins@tests.local" on line 19 of /etc/cups/cups-files.conf. > Mar 27 10:10:33 cups-sssd cupsd[21463]: Unable to read > "/etc/cups/cups-files.conf" due to errors. > Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Main process exited, > code=exited, status=1/FAILURE > Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Failed with result > 'exit-code'. > Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Service hold-off > time over, scheduling restart. > Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Scheduled restart > job, restart counter is at 2. > Mar 27 10:10:33 cups-sssd systemd[1]: Stopping Make remote CUPS printers > available locally... > Mar 27 10:10:33 cups-sssd systemd[1]: Stopped Make remote CUPS printers > available locally. > Mar 27 10:10:33 cups-sssd systemd[1]: Stopped CUPS Scheduler. > > If sssd is running before cups starts, everything works as expected. > > Test Case: > > * Configure an external authentication service (LDAP, AD...) and create > a group, for instance "lpadmins@tests.local" > > * Set SystemGroup to match that group in /etc/cups/cups-files.conf: > SystemGroup lpadmins@tests.local > > * Reboot > > * If cups has started before sssd has finished booting, cups will crash: > Mar 27 10:10:33 cups-sssd cupsd[21463]: Unknown SystemGroup > "lpadmins@tests.local" on line 19 of /etc/cups/cups-files.conf. > > * If cups starts after sssd, it will work fine. > > --- > > This bug has been fixed upstream in 2.2.12 with this commit: > > > https://github.com/apple/cups/commit/aaebca5660fdd7f7b6f30461f0788d91ef6e2fee > > > Kind regards, > > Victor > >
Bug#511408: sparse: -E -MF doesn't work
Hi, Improvements are possible in this area but cgcc -E test.c -o test.C -MF test.d is not supposed to work as expected by OP since gcc -E test.c -o test.C -MF test.d is not working. So, it's not a bug and this PR should be closed. Best regards, -- Luc Van Oostenryck
Bug#921329: dehydrated: Update to version 0.6.2 to get ACME V02 and wildcard support
Package: dehydrated Version: 0.3.1-3+deb9u2 Severity: wishlist Dear Maintainer, Let's Encrypt has made wildcard support available since marh 2018. It implies using version 2 of the ACME protocol. Dehydrated has published support for these features as of 0.6.2, published in april 2018 (see https://github.com/lukas2511/dehydrated/releases/tag/v0.6.2). Debian only ships version 0.3.1 and hence cannot use these features. It would be nice to update the version shipped with Debian. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages dehydrated depends on: ii ca-certificates 20170717 ii curl 7.63.0-1 ii openssl 1.1.1a-1 dehydrated recommends no packages. dehydrated suggests no packages.
Bug#920776: sparse: new upstream release
On Tue, Jan 29, 2019 at 12:57:09PM -0800, Jonathan Nieder wrote: > Hi Uwe, > > Uwe Kleine-König wrote: > > On 1/29/19 2:38 AM, Jonathan Nieder wrote: > > >> Thoughts of all kinds welcome, as always. If you'd prefer this in the > >> form of a "git pull"-able repository, a push to salsa, or an NMU, just > >> ask. > > > > I didn't follow sparse development in the nearer past. Is there a > > problem with sparse 0.5.2 that would be fixed by going to 0.6.0? Yes, it does. Sparse 0.5.2 can't be used on recent glibc/gcc (like debian unstable), because their system headers use types _Float32, _Float64 & _Float128 which parse doesn't know about. This is fixed in v0.6.0. Sparse v0.6.0 contains also many others fixes and some improvements like, for example, Ramsay's patch. Another improvement is that its validation suite is substantially more complete (627 testfiles vs 288). > > My thought was not to touch it for buster and go to 0.6.0 only afterwards. > > Cc-ing Ramsay Jones and Luc to find out. In [1] I find > > | [I was a little surprised that Linux Mint 19.1 (based on Ubuntu > | 18.04) has v0.5.1 - Debian unstable has v0.5.2, but both of those > | are just a little too old for use with git on recent Linux.] > > but I wasn't able to reproduce a problem with v0.5.2 analyzing git.git > myself. It really depends on the distro you're using. > That said, v0.6.0 has been working well for me, so I suspect > upgrading is not too risky. It's my opinion too (but I admit that: * I'm sparse's maintainer and main developer * I mainly use & test sparse for kernel work, not userspace). -- Luc
Bug#920413: simple-scan: unable to connect to Brother 9020-CDW that worked out of the box a few weeks ago
Package: simple-scan
Version: 3.30.1.1-1+b1
Severity: normal
I used to scan documents on my Brother DCP 9020-CDW for months.
I never had to condigure anything, it did work out of the box,
flawlessly, despite this multifunctions machine is not cited
as a sane supported device. I used it over a wifi connection.
However, today the scanner cannot be found by simple-scan anymore.
I even tried to replace the wifi connection by an ethernet connection,
but nothing worked.
The printer is accessible through WIFI so there are no hardware or
network problems, I printed successfully a test document using CUPS.
Only the scanner cannot be found, despite it was instantly recognized
for the last one or two years.
-- Package-specific info:
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8),
LANGUAGE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages simple-scan depends on:
ii dbus-user-session [default-dbus-session-bus] 1.12.12-1
ii dbus-x11 [dbus-session-bus] 1.12.12-1
ii dconf-gsettings-backend [gsettings-backend] 0.30.1-2
ii libc6 2.28-5
ii libcairo2 1.16.0-2
ii libcolord21.4.3-4
ii libgdk-pixbuf2.0-02.38.0+dfsg-7
ii libglib2.0-0 2.58.2-3
ii libgtk-3-03.24.4-1
ii libgusb2 0.3.0-1
ii libpackagekit-glib2-181.1.12-1
ii libsane 1.0.27-3.1
ii libwebp6 0.6.1-2
ii libwebpmux3 0.6.1-2
ii xdg-utils 1.1.3-1
ii zlib1g1:1.2.11.dfsg-1
simple-scan recommends no packages.
simple-scan suggests no packages.
-- no debconf information
[+0,00s] DEBUG: simple-scan.vala:638: Starting Simple Scan 3.30.1.1, PID=29766
[+0,13s] DEBUG: app-window.vala:1715: Loading state from
/home/luc/.cache/simple-scan/state
[+0,13s] DEBUG: app-window.vala:1672: Restoring window to 1134x799 pixels
[+0,13s] DEBUG: autosave-manager.vala:64: Loading autosave information
[+0,13s] DEBUG: autosave-manager.vala:259: Waiting to autosave...
[+0,18s] DEBUG: scanner.vala:1461: sane_init () -> SANE_STATUS_GOOD
[+0,18s] DEBUG: scanner.vala:1467: SANE version 1.0.27
[+0,18s] DEBUG: scanner.vala:1528: Requesting redetection of scan devices
[+0,19s] DEBUG: scanner.vala:806: Processing request
[+0,23s] DEBUG: autosave-manager.vala:281: Autosaving book information
[+0,33s] DEBUG: app-window.vala:1776: Saving state to
/home/luc/.cache/simple-scan/state
[+0,60s] DEBUG: app-window.vala:1776: Saving state to
/home/luc/.cache/simple-scan/state
[+4,39s] DEBUG: simple-scan.vala:455: Requesting scan at 1200 dpi from device
'(null)'
[+4,39s] DEBUG: scanner.vala:1576: Scanner.scan ("(null)", dpi=1200,
scan_mode=ScanMode.GRAY, depth=2, type=ScanType.SINGLE, paper_width=0,
paper_height=0, brightness=-21, contrast=81, delay=1ms)
[+4,71s] DEBUG: app-window.vala:1776: Saving state to
/home/luc/.cache/simple-scan/state
[+5,14s] DEBUG: app-window.vala:1776: Saving state to
/home/luc/.cache/simple-scan/state
[+6,65s] DEBUG: scanner.vala:341: sane_get_devices () -> SANE_STATUS_GOOD
[+6,65s] DEBUG: scanner.vala:806: Processing request
[+6,65s] WARNING: scanner.vala:841: No scan device available
[+6,65s] DEBUG: scanner.vala:1528: Requesting redetection of scan devices
[+6,65s] DEBUG: scanner.vala:806: Processing request
[+6,75s] DEBUG: app-window.vala:1776: Saving state to
/home/luc/.cache/simple-scan/state
[+9,04s] DEBUG: app-window.vala:1776: Saving state to
/home/luc/.cache/simple-scan/state
[+11,47s] DEBUG: autosave-manager.vala:195: Deleting autosave records
[+11,47s] DEBUG: scanner.vala:1604: Stopping scan thread
[+12,92s] DEBUG: scanner.vala:341: sane_get_devices () -> SANE_STATUS_GOOD
[+12,92s] DEBUG: scanner.vala:806: Processing request
[+12,93s] DEBUG: scanner.vala:1615: sane_exit ()
[+12,93s] CRITICAL: app_window_set_scan_devices: assertion 'self != NULL' failed
No scanners were identified. If you were expecting something different,
check that the scanner is plugged in, turned on and detected by the
sane-find-scanner tool (if appropriate). Please read the documentation
which came with this software (README, FAQ, manpages).
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass9 Hub
bDeviceSubClass 0 Unuse
Bug#919025: debian-installer: [armhf] Please add image for Sinovoip_Banana_Pi_M1+
Package: debian-installer Severity: wishlist Tags: d-i Dear Maintainer, debian-installer already builds images for Banana Pro[1]. Could you please add images for Sinovoip Banana Pi M1+ ? It is a variant of Banana Pro that differs in the sound connector[2]. Best regards, Frédéric Lehobey 1. https://d-i.debian.org/daily-images/armhf/daily/u-boot/ 2. http://linux-sunxi.org/Banana_Pro#Variants
Bug#873508: sparse test failures on ppc32le (and other not so common archs)
On Wed, Jan 09, 2019 at 09:28:54PM -0500, Antoine Beaupré wrote: > Control: forwarded -1 https://github.com/br101/horst/issues/93 Hi, The issue showed there, more precisely the one: /usr/include/x86_64-linux-gnu/bits/mathcalls-helper-functions.h:21:1: error: Expected ) in function declarator is caused by sparse's lack of support for _Float128 and occurs with recent version of glibc. This has been fixed and upstreamed (see https://git.kernel.org/pub/scm/devel/sparse/sparse.git/commit/?id=4e9c8ee467dd87d41d5aaa3c5a487e3f05ffb79c for more details). Best regards, -- Luc
Bug#916698: deborphan: updated French po translation
Package: deborphan Version: 1.7.30 Severity: wishlist Tags: l10n patch -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Please find attached the updated po French translation proofreaded by the member of the debian l10n French list members. Regards Jean-Luc - -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (600, 'unstable'), (500, 'unstable-debug'), (500, 'buildd-unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.20.0-rc6-i7-0.1 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages deborphan depends on: ii libc6 2.28-3 Versions of packages deborphan recommends: ii apt 1.8.0~alpha2 ii dialog1.3-20181022-1 ii gettext-base 0.19.8.1-9 deborphan suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- iF0EARECAB0WIQT5el3FKLtmYO4UlQtR0YZfPMac0AUCXBe9wAAKCRBR0YZfPMac 0LyeAJ0d2qGzL7cEDX4ivnpa7MBvT0AUBACeOQsGvUa67Gadi+hb9y/YxEI2iNQ= =54mC -END PGP SIGNATURE- # French translation of deborphan. # Copyright (C) 2004 THE deborphan'S COPYRIGHT HOLDER # This file is distributed under the same license as the deborphan package. # # # Jean-Luc Coulon (f5ibh) , 2004, 2018. msgid "" msgstr "" "Project-Id-Version: deborphan 1.7.28\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2018-07-25 17:33+\n" "PO-Revision-Date: 2018-12-14 12:21+0100\n" "Last-Translator: Jean-Luc Coulon \n" "Language-Team: French \n" "Language: fr\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=2; plural=(n > 1);\n" "X-Generator: Lokalize 2.0\n" #: src/exit.c:52 #, c-format msgid "" "\n" "The following options are available:\n" msgstr "" "\n" "Liste des options disponibles :\n" #: src/exit.c:55 #, c-format msgid "-hThis help.\n" msgstr "-h Ce texte d'aide.\n" #: src/exit.c:58 #, c-format msgid "-f FILE Use FILE as statusfile.\n" msgstr "-f FICHIER Utiliser FICHIER comme fichier d'état.\n" #: src/exit.c:61 #, c-format msgid "-vVersion information.\n" msgstr "-v Afficher la version du programme.\n" #: src/exit.c:65 #, c-format msgid "-dShow dependencies for packages that have them.\n" msgstr "-d Afficher les dépendances des paquets.\n" #: src/exit.c:68 #, c-format msgid "-PShow priority of packages found.\n" msgstr "" "-P Afficher la priorité des paquets qui ont été\n" " trouvés.\n" #: src/exit.c:71 #, c-format msgid "-sShow the sections the packages are in.\n" msgstr "-s Afficher la section des paquets.\n" #: src/exit.c:73 #, c-format msgid "--no-show-section Do not show sections.\n" msgstr "--no-show-section Ne pas afficher les sections.\n" #: src/exit.c:76 #, c-format msgid "-zShow installed size of packages found.\n" msgstr "" "-z Afficher la taille des paquets qui ont été\n" " trouvés.\n" #: src/exit.c:80 #, c-format msgid "-aCompare all packages, not just libs.\n" msgstr "" "-a Comparer tous les paquets et pas seulement\n" " les bibliothèques.\n" #: src/exit.c:83 #, c-format msgid "-e LIST Work as if packages in LIST were not installed.\n" msgstr "" "-e LISTEFonctionnement comme si les paquets dans la LISTE\n" " n'étaient pas installés.\n" #: src/exit.c:86 #, c-format msgid "-HIgnore hold flags.\n" msgstr "" "-H Ignorer les indicateurs de maintien dans la version\n" " actuelle (« hold »).\n" #: src/exit.c:89 #, c-format msgid "Disable checks for `recommends'.\n" msgstr " Supprimer les vérifications pour « recommande ».\n" #: src/exit.c:91 #, c-format msgid "Disable checks for `suggests'.\n" msgstr " Supprimer les vérifications pour « suggère ».\n" #: src/exit.c:94 #, c-format msgid "-nDisable checks for `recommends' and `suggests'.\n" msgstr "" "-n Supprimer les vérifications pour « recommande » et\n" " « suggère ».\n" #: src/exit.c:97 #, c-format msgid &
Bug#914085: soundscaperenderer: failed to cofigure cleanly
Package: soundscaperenderer Version: 0.5.0~dfsg-1 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, While upgrading from 0.4.2~dfsg-7 to 0.5.0~dfsg-1, I get the following error: Setting up soundscaperenderer (0.5.0~dfsg-1) ... update-alternatives: error: alternative path /usr/bin/ssr-nfc-hoa.qt doesn't exist dpkg: error processing package soundscaperenderer (--configure): installed soundscaperenderer package post-installation script subprocess returned error exit status 2 Errors were encountered while processing: soundscaperenderer Regards Jean-Luc - -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (600, 'unstable'), (500, 'unstable-debug'), (500, 'buildd-unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.20.0-rc2-i7-0.1 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages soundscaperenderer depends on: ii jackd 5 ii libc6 2.27-8 ii libecasoundc1v5 2.9.1-7+b3 ii libfftw3-single3 3.3.8-2 ii libgcc1 1:8.2.0-9 ii libgl11.1.0-1 ii libglu1-mesa [libglu1]9.0.0-2.1 ii libjack-jackd2-0 [libjack-0.125] 1.9.12~dfsg-2 ii libqt5core5a 5.11.2+dfsg-7 ii libqt5gui55.11.2+dfsg-7 ii libqt5opengl5 5.11.2+dfsg-7 ii libqt5widgets55.11.2+dfsg-7 ii libsndfile1 1.0.28-4 ii libstdc++68.2.0-9 ii libxml2 2.9.8+dfsg-1 ii soundscaperenderer-common 0.5.0~dfsg-1 Versions of packages soundscaperenderer recommends: ii ecasound 2.9.1-7+b3 soundscaperenderer suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- iF0EARECAB0WIQT5el3FKLtmYO4UlQtR0YZfPMac0AUCW/JubgAKCRBR0YZfPMac 0JwNAKCVnrR7Ou1ZWaauTYe8onanljN+UACfX7e/Mk5gbNbcvWVg2IrCC2WgMgE= =V9iH -END PGP SIGNATURE-
Bug#912868: rdesktop: fails to connect to a VirtualBox 5.2 server
Package: rdesktop Version: 1.8.3-2+b1 Severity: normal Dear Maintainer, After enabling the RDP server for a VM in VirtualBox 5.2.20, I tried to connect to it using `rdesktop `. Rdesktop outputs: Autoselected keyboard map en-us Failed to negotiate protocol, retrying with plain RDP. ERROR: Connection closed And exits with status 76. My rdesktop version is 1.8.3-2+b1. When retrying with a binary built from source (not the latest release, which dates from 2015, but the current git status, branch master, as of 2018-11-04), this issue no longer occurs. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.17.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages rdesktop depends on: ii libasound21.1.6-1 ii libc6 2.27-6 ii libgssglue1 0.4-2+b2 ii libpcsclite1 1.8.23-3 ii libssl1.1 1.1.1-2 ii libx11-6 2:1.6.6-1 ii libxrandr22:1.5.1-1 rdesktop recommends no packages. Versions of packages rdesktop suggests: ii pcscd 1.8.23-3 -- no debconf information
Bug#906472: horst: FTBFS in buster/sid (unable to open 'stdarg.h')
On Tue, Sep 25, 2018 at 04:38:01PM +0200, Uwe Kleine-König wrote:
> > By *default*, if no -gcc-base-dir is used, sparse use the same dir
> > as the one used by the GCC used to compile sparse itself. It's only
> > this default that is hardcoded.
>
> I wasn't sure if this is expected to work. I had in mind, that the
> version of gcc is used somewhere but couldn't find proof for that.
Several other flags have their default value corresponding to the
GCC used to compile sparse: for example the architecture (x86, x86-64)
or the endianness. The one you're thinking about is probably the macros
for the GCC version: __GNUC__, __GNUC_MINOR__ & __GNUC_PATCHLEVEL__.
As far as I know, everything that should matter can be set explicitly
either by defining the macro via -D...=... or an explicit flag like
-m{32,64}, -m{little,big}-endian, -funsigned-char, ...
When using sparse for userspace code, it may be best to use the cgcc
wrapper since it take care to set (some of) these values. I'm saying
'may' because personnaly, I have no experience of using sparse via
cgcc (as an user, I've only used sparse for OS or bare-metal code)
but I know others use it like so (for example for git).
> > In case the default can't be used, like here, I think the best is
> > to add in your Makefile something like:
> > GCC_BASE_DIR=$(shell $(CC) -print-file-name=)
> > SPARSE_FLAGS= -gcc-base-dir $(GCC_BASE_DIR)
> > ...
> > sparse $(SPARSE_FLAGS) ...
>
> IMHO it is sensible to let sparse depend on (or at least recommend) gcc.
> And then the default value should be right.
>
> > This doesn't need to be done at each invocation of sparse (but will be done
> > at each top-level make invocation).
>
> I'd say you'd need := for this effect instead of =.
Yes, indeed.
> Best regards and thanks for your valuable input,
> Uwe
You're very welcome,
-- Luc
Bug#906472: horst: FTBFS in buster/sid (unable to open 'stdarg.h')
On Fri, Sep 14, 2018 at 09:45:44PM +0200, Uwe Kleine-König wrote:
> Hello,
>
> [Cc += sparse mailing list]
Sorry for the late answer.
> > > Santiago Vila wrote...
> > >
> > > > make -j1 check
> > > > make[1]: Entering directory '/<>'
> > > > sparse -g -O2 -fdebug-prefix-map=/<>=.
> > > > -fstack-protector-strong -Wformat -Werror=format-security -std=gnu99
> > > > -Wall -Wextra -g -I. -DDO_DEBUG -I/usr/include/libnl3 *.[ch]
> > > > /usr/include/err.h:25:11: error: unable to open 'stdarg.h'
> > >
> > > To reproduce this it's important to remove gcc-7 from the build chroot
> > > (apt purge libgcc-7-dev ; apt --purge autoremove).
> > >
> > > Problem is, sparse appearently uses hardcoded paths and looks for
> > > stdarg.h in (among other places)
Well, sparse needs to know where it can find the system header files.
There is an option for this: -gcc-base-dir (and -multiarch-dir).
Usually you will want to use either some that are installed by your
distro or the one that match the exact GCC version you're using.
By *default*, if no -gcc-base-dir is used, sparse use the same dir
as the one used by the GCC used to compile sparse itself. It's only
this default that is hardcoded.
> > > Solution is to rebuild sparse, building horst was successful then.
> > > If this is true (please check!), the interesting question is why this
> > > wasn't a problem in earlier gcc version bumps.
>
> I think this is a known limitation of sparse and there are three
> ways to fix this (in my order of preference):
>
> a) let horst use cgcc -no-compile instead of sparse; or
> b) let sparse depend on libgcc-7-dev (or whatever provides the
> necessary files); or
> c) use autodetection which gcc is used and pick its files.
>
> I'm not sure if a) fixes the problem. It fixed another problem we had
> with horst's usage of sparse in the past though[1].
>
> The downside of c) is that running this autodetection on every call to
> sparse is probably slowing down sparse a bit which isn't nice.
In case the default can't be used, like here, I think the best is
to add in your Makefile something like:
GCC_BASE_DIR=$(shell $(CC) -print-file-name=)
SPARSE_FLAGS= -gcc-base-dir $(GCC_BASE_DIR)
...
sparse $(SPARSE_FLAGS) ...
This doesn't need to be done at each invocation of sparse (but will be done
at each top-level make invocation).
Regards,
-- Luc
Bug#909177: snapper-gui should depend on snapper otherwise it crashes at start
Package: snapper-gui
Version: 0git.960a94834f-2
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
snapper-gui doesnt work if snapper has not be previously installed.
I get:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/dbus/bus.py", line 175, in
activate_name_owner
return self.get_name_owner(bus_name)
File "/usr/lib/python3/dist-packages/dbus/bus.py", line 361, in get_name_owner
's', (bus_name,), **keywords)
File "/usr/lib/python3/dist-packages/dbus/connection.py", line 651, in
call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NameHasNoOwner: Could
not get owner of name 'org.opensuse.Snapper': no such name
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/bin/snapper-gui", line 11, in
load_entry_point('snappergui==0.1', 'gui_scripts', 'snapper-gui')()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 484, in
load_entry_point
return get_distribution(dist).load_entry_point(group, name)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2707,
in load_entry_point
return ep.load()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2325,
in load
return self.resolve()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2331,
in resolve
module = __import__(self.module_name, fromlist=['__name__'], level=0)
File "/usr/lib/python3/dist-packages/snappergui/__init__.py", line 9, in
'/org/opensuse/Snapper'),
File "/usr/lib/python3/dist-packages/dbus/bus.py", line 241, in get_object
follow_name_owner_changes=follow_name_owner_changes)
File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 248, in __init__
self._named_service = conn.activate_name_owner(bus_name)
File "/usr/lib/python3/dist-packages/dbus/bus.py", line 180, in
activate_name_owner
self.start_service_by_name(bus_name)
File "/usr/lib/python3/dist-packages/dbus/bus.py", line 278, in
start_service_by_name
'su', (bus_name, flags)))
File "/usr/lib/python3/dist-packages/dbus/connection.py", line 651, in
call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The
name org.opensuse.Snapper was not provided by any .service files
Regards
Jean-Luc
- -- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (600, 'unstable'), (500, 'unstable-debug'), (500,
'buildd-unstable'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-rc4-i7-0.1 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8),
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages snapper-gui depends on:
ii gir1.2-gtksource-3.0 3.24.9-1
ii python3 3.6.6-1
snapper-gui recommends no packages.
snapper-gui suggests no packages.
- -- no debconf information
-BEGIN PGP SIGNATURE-
iF0EARECAB0WIQT5el3FKLtmYO4UlQtR0YZfPMac0AUCW6IShwAKCRBR0YZfPMac
0I9RAKCL3Q19iSDNdj6cMUR3oKVNV8YVGgCdGb9Ji+puC7wx/1nR5eMn87OOtD4=
=rjRm
-END PGP SIGNATURE-
Bug#901302: Crash on monitor rotation
Same problem I guess on my Thinkpad X220 upgraded from stretch to buster (testing): When I try to rotate a monitor in "Displays" (tried several ones), the mouse is freezing, the fan is racing (infinite loop ? :-) ) and I must reboot. Maybe related to https://gitlab.gnome.org/GNOME/mutter/issues/216 Kind regards, Luc PS: Sep 7 16:59:26 x220 org.gnome.SettingsDaemon.MediaKeys.desktop[13972]: [2019:2019:0907/165926.201824:ERROR:gl_surface_presentation_helper.cc(115)] GetVSyncParametersIfAvailable() failed! Sep 7 16:59:26 x220 org.gnome.SettingsDaemon.MediaKeys.desktop[13972]: [2019:2019:0907/165926.203076:ERROR:gl_surface_presentation_helper.cc(115)] GetVSyncParametersIfAvailable() failed! Sep 7 16:59:26 x220 org.gnome.SettingsDaemon.MediaKeys.desktop[13972]: [2019:2019:0907/165926.207092:ERROR:gl_surface_presentation_helper.cc(115)] GetVSyncParametersIfAvailable() failed! Sep 7 16:59:26 x220 org.gnome.SettingsDaemon.MediaKeys.desktop[13972]: [2019:2019:0907/165926.220308:ERROR:gl_surface_presentation_helper.cc(115)] GetVSyncParametersIfAvailable() failed! Sep 7 16:59:26 x220 org.gnome.SettingsDaemon.MediaKeys.desktop[13972]: [2019:2019:0907/165926.224835:ERROR:gl_surface_presentation_helper.cc(115)] GetVSyncParametersIfAvailable() failed! Sep 7 16:59:26 x220 org.gnome.SettingsDaemon.MediaKeys.desktop[13972]: [2019:2019:0907/165926.226449:ERROR:gl_surface_presentation_helper.cc(115)] GetVSyncParametersIfAvailable() failed! Sep 7 16:59:26 x220 org.gnome.SettingsDaemon.MediaKeys.desktop[13972]: [2019:2019:0907/165926.228240:ERROR:gl_surface_presentation_helper.cc(115)] GetVSyncParametersIfAvailable() failed! Sep 7 16:59:26 x220 org.gnome.SettingsDaemon.MediaKeys.desktop[13972]: [2019:2019:0907/165926.230209:ERROR:gl_surface_presentation_helper.cc(115)] GetVSyncParametersIfAvailable() failed! Sep 7 16:59:26 x220 gnome-shell[13822]: Object St.Icon (0x55b531070d10), has been already finalized. Impossible to set any property to it. Sep 7 16:59:26 x220 gnome-shell[13822]: Object St.BoxLayout (0x55b53106fc50), has been already finalized. Impossible to set any property to it. Sep 7 16:59:26 x220 org.gnome.Shell.desktop[13822]: == Stack trace for context 0x55b530b3b320 == Sep 7 16:59:26 x220 org.gnome.Shell.desktop[13822]: #0 0x55b530ee3848 i resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f562bbc7450 @ 231) Sep 7 16:59:26 x220 org.gnome.Shell.desktop[13822]: #1 0x7ffc7592f200 b resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f562beb5de0 @ 71) Sep 7 16:59:26 x220 org.gnome.Shell.desktop[13822]: #2 0x7ffc7592f2c0 b self-hosted:916 (0x7f562bef1230 @ 367) Sep 7 16:59:26 x220 org.gnome.Shell.desktop[13822]: #3 0x7ffc7592f3b0 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7f562bed2230 @ 386) Sep 7 16:59:26 x220 org.gnome.Shell.desktop[13822]: #4 0x55b530ee37c0 i resource:///org/gnome/shell/ui/layout.js:523 (0x7f562bb04230 @ 127) Sep 7 16:59:26 x220 org.gnome.Shell.desktop[13822]: #5 0x7ffc759306f0 b resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f562beb5de0 @ 71) Sep 7 16:59:26 x220 org.gnome.Shell.desktop[13822]: #6 0x7ffc75930ee0 b self-hosted:916 (0x7f562bef1230 @ 367) Sep 7 16:59:26 x220 org.gnome.Shell.desktop[13822]: == Stack trace for context 0x55b530b3b320 == Sep 7 16:59:26 x220 org.gnome.Shell.desktop[13822]: #0 0x55b530ee3848 i resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7f562bbc7450 @ 273) Sep 7 16:59:26 x220 org.gnome.Shell.desktop[13822]: #1 0x7ffc7592f200 b resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f562beb5de0 @ 71) Sep 7 16:59:26 x220 org.gnome.Shell.desktop[13822]: #2 0x7ffc7592f2c0 b self-hosted:916 (0x7f562bef1230 @ 367) Sep 7 16:59:26 x220 org.gnome.Shell.desktop[13822]: #3 0x7ffc7592f3b0 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7f562bed2230 @ 386) Sep 7 16:59:26 x220 org.gnome.Shell.desktop[13822]: #4 0x55b530ee37c0 i resource:///org/gnome/shell/ui/layout.js:523 (0x7f562bb04230 @ 127) Sep 7 16:59:26 x220 org.gnome.Shell.desktop[13822]: #5 0x7ffc759306f0 b resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f562beb5de0 @ 71) Sep 7 16:59:26 x220 org.gnome.Shell.desktop[13822]: #6 0x7ffc75930ee0 b self-hosted:916 (0x7f562bef1230 @ 367) Sep 7 16:59:26 x220 gnome-shell[13822]: Object St.Icon (0x55b53404c090), has been already finalized. Impossible to set any property to it. Sep 7 16:59:26 x220 gnome-shell[13822]: Object St.BoxLayout (0x55b5343a8310), has been already finalized. Impossible to set any property to it. Sep 7 16:59:26 x220 org.gnome.Shell.desktop[13822]: == Stack trace for context 0x55b530b3b320 == Sep 7 16:59:26 x220 org.gnome.Shell.desktop[13822]: #0 0x55b530ee3848 i resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f562bbc7450 @ 231) Sep 7 16:59:26 x220 org.gnome.Shell.desktop[13822]: #1 0x7ffc7592f200 b resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f562beb5de0 @ 71) Sep 7 16:59:26 x220 org.gnome.Shell.desktop[
Bug#908112: ganeti: Unable to move an instance to an other node
Package: ganeti Version: 2.15.2-7+deb9u2 Severity: important Dear Maintainer, * What led up to the situation? I tried to move an instance to an other node: ``` gnt-instance move -n node2.foo.org instance_to_move.foo.org ``` It failed at disk copy with: ``` Thu Sep 6 08:45:15 2018 - WARNING: export 'export-disk0-2018-09-06_08_45_14-AczCFY' on node1.foo.org failed: Unhandled error occurred: global name 'SOCAT_PATH' is not defined Thu Sep 6 08:45:15 2018 disk/0 failed to send data: Unhandled error occurred: global name 'SOCAT_PATH' is not defined (recent output: ) Thu Sep 6 08:45:16 2018 - WARNING: Aborting import 'import-disk0-2018-09-06_08_45_09-hsDCKv' on 54c96f74-2ea7-461a-90f6-8652fac2942f ``` I added this in /usr/share/ganeti/2.15/ganeti/impexpd/__init__.py, line 68 ``` SOCAT_PATH = '/usr/bin/socat' ``` Then it still failed with: ``` Thu Sep 6 08:49:20 2018 - WARNING: export 'export-disk0-2018-09-06_08_49_19-vDGWD9' on node1.foo.org failed: Unhandled error occurred: global name 'm' is not defined Thu Sep 6 08:49:20 2018 disk/0 failed to send data: Unhandled error occurred: global name 'm' is not defined (recent output: ) Thu Sep 6 08:49:20 2018 - WARNING: Aborting import 'import-disk0-2018-09-06_08_49_14-2WLKY4' on 54c96f74-2ea7-461a-90f6-8652fac2942f ``` I managed to move my instance by downgrading ganeti, ganeti-2.15, ganeti-haskell-2.15 and ganeti-htools-2.15 to the previous version (2.15.2-7+deb9u1) -- Package-specific info: Version symlinks: /etc/ganeti/share -> /usr/share/ganeti/2.15 /etc/ganeti/lib -> /usr/lib/ganeti/2.15 Cluster config version: 2.15.2 Address family: IPv4 Enabled hypervisors: kvm kvm hypervisor parameters: acpi=True boot_order=disk cpu_cores=0 cpu_mask=all cpu_sockets=0 cpu_threads=0 disk_aio=threads disk_cache=default disk_type=paravirtual kernel_args=ro kernel_path=/boot/vmlinuz-3-kvmU kvm_path=/usr/bin/kvm migration_bandwidth=32 migration_downtime=30 migration_mode=live migration_port=8102 nic_type=paravirtual reboot_behavior=reboot root_path=/dev/vda1 security_model=none serial_console=True serial_speed=38400 spice_ip_version=0 spice_playback_compression=True spice_tls_ciphers=HIGH:-DES:-3DES:-EXPORT:-ADH spice_use_tls=False spice_use_vdagent=True use_chroot=False use_localtime=False user_shutdown=False vhost_net=False virtio_net_queues=1 vnc_tls=False vnc_x509_verify=False vnet_hdr=True -- System Information: Debian Release: 9.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-5-amd64 (SMP w/12 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages ganeti depends on: ii adduser 3.115 ii ganeti-2.15 2.15.2-7+deb9u2 ii ganeti-haskell-2.15 2.15.2-7+deb9u2 ii ganeti-htools-2.15 2.15.2-7+deb9u2 ii lsb-base 9.20161125 ii python 2.7.13-2 Versions of packages ganeti recommends: ii drbd-utils 8.9.10-2 ii drbd8-utils 2:8.9.10-2 ii ganeti-instance-debootstrap 0.16-2.1 ii ndisc6 1.0.3-3 ii qemu-kvm 1:2.8+dfsg-6+deb9u4 Versions of packages ganeti suggests: pn blktap-dkms ii ganeti-doc 2.15.2-7+deb9u2 pn molly-guard -- Configuration Files: /etc/default/ganeti changed [not included] -- no debconf information
Bug#894153: the bugs seems to be fixed now
Le 23/07/2018 à 15:23, Rene Engelhard a écrit : On Fri, Jul 20, 2018 at 11:07:40AM +0200, Rene Engelhard wrote: close 89153 1:6.0.6~rc1-1 thanks [...] What about the 6.1.0 rc1 in experimental? Is it fixed there, too? I didn't find 6.1.0 in the experimental repository for the amd64 architecture, it was still 1:6.0.6~rc1-1 (6.1.0 was there only for ppc64 and alpha architectures). (or only in rc2 - which isn't officially released yet). Since [...] (I plan to upload said 6.1.0 rc2 to unstable soonish after it "survived" a test build in experimenal when it's there and uploaded.) Ping? :) That now happened. OK, I have tried this 6.1.0~rc2-2 from unstable. The unicode input shortcut works. Would try myself, but apparently I am not skkilled anpough to actually make Ctrl-U 61 print anything else than a "61". How are you supposed to do that? Maybe you forgot the "shift"? I used uppercase U in the description of the shortcut to denote that, it was probably not explicit, sorry. I should probably have written it as Ctrl-Shift-U. See <https://en.wikipedia.org/wiki/Unicode_input#In_X11_(Linux_and_Unix_variants)> or <https://help.gnome.org/users/gnome-help/stable/tips-specialchars.html.en#ctrlshiftu>. Once you have entered the prefix Ctrl-shift-u, an underlined 'u' should appear to show that the next character will be a unicode code point, and this undelined u should disappear when you enter the code point (in hexadecimal) and end b You can try with 61 for the ASCII character for 'a', or 03B1 for greek alpha (α), or 2202 for the mathematical partial differential symbol (∂), or 2026 for the ellipsis… best regards, Luc Regards, Rene
Bug#894153: the bugs seems to be fixed now
I don't know when or why it happened, but as of 2018-07-20 and version 1:6.0.6~rc1-1, the bug doesn't happen anymore. I now can use Ctrl-U prefix in libreoffice just like I use it in other desktop applications to input any unicode character. thanks
Bug#902596: firefox: Since upgrade from 60.0.2 to 61.0, there is no mean to have spell checking
Package: firefox Version: 61.0-1 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Sice the upgrade from 60.0.2 to 61.0, spell checking inside firefox doesnt work. All the words are underlined in red. I tried various dictionnaries (add-ons) without any success. Reverting to 60.0.2 gives the expected behaviour. Regards Jean-Luc - -- Package-specific info: - -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (600, 'unstable'), (500, 'unstable-debug'), (500, 'buildd-unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-rc2-i7-0.1 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages firefox depends on: ii debianutils 4.8.6 ii fontconfig2.13.0-5 ii libatk1.0-0 2.28.1-1 ii libc6 2.27-3 ii libcairo-gobject2 1.15.10-3 ii libcairo2 1.15.10-3 ii libdbus-1-3 1.12.8-3 ii libdbus-glib-1-2 0.110-2 ii libevent-2.1-62.1.8-stable-4 ii libffi6 3.2.1-8 ii libfontconfig12.13.0-5 ii libfreetype6 2.8.1-2 ii libgcc1 1:8.1.0-9 ii libgdk-pixbuf2.0-02.36.11-2 ii libglib2.0-0 2.56.1-2 ii libgtk-3-03.22.30-2 ii libhunspell-1.6-0 1.6.2-1+b1 ii libjsoncpp1 1.7.4-3 ii libnspr4 2:4.19-3 ii libnss3 2:3.38-1 ii libpango-1.0-01.42.1-1 ii libsqlite3-0 3.24.0-1 ii libstartup-notification0 0.12-5 ii libstdc++68.1.0-9 ii libvpx5 1.7.0-3 ii libx11-6 2:1.6.5-1 ii libx11-xcb1 2:1.6.5-1 ii libxcb-shm0 1.13-1 ii libxcb1 1.13-1 ii libxcomposite11:0.4.4-2 ii libxdamage1 1:1.1.4-3 ii libxext6 2:1.3.3-1+b2 ii libxfixes31:5.0.3-1 ii libxrender1 1:0.9.10-1 ii libxt61:1.1.5-1 ii procps2:3.3.15-2 ii zlib1g1:1.2.11.dfsg-1 firefox recommends no packages. Versions of packages firefox suggests: ii fonts-lmodern 2.004.5-3 ii fonts-stix [otf-stix] 1.1.1-4 ii libcanberra0 0.30-6 ii libgssapi-krb5-2 1.16-2 ii libgtk2.0-02.24.32-2 - -- no debconf information -BEGIN PGP SIGNATURE- iFwEARECAB0WIQT5el3FKLtmYO4UlQtR0YZfPMac0AUCWzSf+gAKCRBR0YZfPMac 0AmuAJ4zoODqcqb2EGS4KXgX4h0PGe1qWACY8bD+R696Kwuf3UiDUMdm/CYlww== =LVIn -END PGP SIGNATURE-
Bug#902595: firefox-l10n-fr: Package firefox-l10n-fr has no effect
Package: firefox-l10n-fr Version: 61.0-1 Severity: normal Tags: l10n -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, (this applies also to some previous versions) After installation of the l10n-fr package, the ui is still in english (I've restarted firefox). But if I use the xpi file from mozilla and install it as an add-on, then the ui is localized. Regards Jean-Luc - -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (600, 'unstable'), (500, 'unstable-debug'), (500, 'buildd-unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-rc2-i7-0.1 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages firefox-l10n-fr depends on: ii firefox 61.0-1 Versions of packages firefox-l10n-fr recommends: pn myspell-fr | myspell-fr-gut firefox-l10n-fr suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- iF0EARECAB0WIQT5el3FKLtmYO4UlQtR0YZfPMac0AUCWzSerAAKCRBR0YZfPMac 0Md8AJ9AKvhfU4OqmAELRVwVTLrvvS8F0wCgrLdG93TU26LmKa5U+mRnuP5Wy90= =pfYc -END PGP SIGNATURE-
Bug#902266: dictd: Refuse to restart after upgrade to 1.12.1+dfsg-5
Package: dictd Version: 1.12.1+dfsg-5 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, (Maybe it is related to #835257) While upgrading, I get the following: Setting up dictd (1.12.1+dfsg-5) ... insserv: warning: current stop runlevel(s) (1) of script `dictd' overrides LSB defaults (0 1 6). Job for dictd.service failed because the control process exited with error code. See "systemctl status dictd.service" and "journalctl -xe" for details. invoke-rc.d: initscript dictd, action "restart" failed. * dictd.service - LSB: Start and stop dictionary server daemon Loaded: loaded (/etc/init.d/dictd; generated) Active: failed (Result: exit-code) since Sun 2018-06-24 08:45:17 CEST; 3ms ago Docs: man:systemd-sysv-generator(8) Process: 14317 ExecStart=/etc/init.d/dictd start (code=exited, status=1/FAILURE) Jun 24 08:45:17 tangerine systemd[1]: Starting LSB: Start and stop dictionary server daemon... Jun 24 08:45:17 tangerine dictd[14317]: Starting dictionary server: dictd failed! Jun 24 08:45:17 tangerine systemd[1]: dictd.service: Control process exited, code=exited status=1 Jun 24 08:45:17 tangerine systemd[1]: dictd.service: Failed with result 'exit-code'. Jun 24 08:45:17 tangerine systemd[1]: Failed to start LSB: Start and stop dictionary server daemon. dpkg: error processing package dictd (--configure): installed dictd package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: dictd Output of "systemctl status dictd.service": ● dictd.service - LSB: Start and stop dictionary server daemon Loaded: loaded (/etc/init.d/dictd; generated) Active: failed (Result: exit-code) since Sun 2018-06-24 08:45:17 CEST; 55s ag Docs: man:systemd-sysv-generator(8) Process: 14317 ExecStart=/etc/init.d/dictd start (code=exited, status=1/FAILUR juin 24 08:45:17 tangerine systemd[1]: Starting LSB: Start and stop dictionary s juin 24 08:45:17 tangerine dictd[14317]: Starting dictionary server: dictd faile juin 24 08:45:17 tangerine systemd[1]: dictd.service: Control process exited, co juin 24 08:45:17 tangerine systemd[1]: dictd.service: Failed with result 'exit-c juin 24 08:45:17 tangerine systemd[1]: Failed to start LSB: Start and stop dicti lines 1-11/11 (END) Output of "journalctl -xe": - -- L'unité (unit) dictd.service a commencé à démarrer. juin 24 08:45:17 tangerine dictd[14317]: Starting dictionary server: dictd failed! juin 24 08:45:17 tangerine systemd[1]: dictd.service: Control process exited, code=exited status=1 juin 24 08:45:17 tangerine systemd[1]: dictd.service: Failed with result 'exit-code'. juin 24 08:45:17 tangerine systemd[1]: Failed to start LSB: Start and stop dictionary server daemon. - -- Subject: L'unité (unit) dictd.service a échoué - -- Defined-By: systemd - -- Support: https://www.debian.org/support - -- - -- L'unité (unit) dictd.service a échoué, avec le résultat RESULT. Regards Jean-Luc - -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (600, 'unstable'), (500, 'unstable-debug'), (500, 'buildd-unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-rc1-i7-0.1 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages dictd depends on: ii adduser3.117 ii debconf [debconf-2.0] 1.5.67 ii dictzip1.12.1+dfsg-5 ii libc6 2.27-3 ii libmaa41.4.2-1 ii lsb-base 9.20170808 ii netbase5.4 ii ucf3.0038 ii update-inetd 4.45 ii zlib1g 1:1.2.11.dfsg-1 Versions of packages dictd recommends: ii gnome-dictionary [dict-client] 3.26.1-4 ii xfce4-dict [dict-client]0.8.0-1 Versions of packages dictd suggests: pn dict-foldoc ii dict-freedict-eng-fra [dictd-dictionary] 2016.12.12-1 pn dict-jargon pn dict-wn - -- debconf information: dictd/run_mode: daemon -BEGIN PGP SIGNATURE- iF0EARECAB0WIQT5el3FKLtmYO4UlQtR0YZfPMac0AUCWy9AgwAKCRBR0YZfPMac 0BOcAJ4lbc9XBqsInEVis9xoe3v5lSPMEwCePPj44CxCkZADL5SxdOCH+9yE70c= =M+tU -END PGP SIGNATURE-
Bug#899232: thunderbird: Main screen corrupted with 52.8.0-1
Hello Carsten, Le 21/05/2018 à 17:02, Carsten Schoenert a écrit : Hello Jean-Luc, On Mon, May 21, 2018 at 11:18:36AM +0200, Jean-Luc Coulon (f5ibh) wrote: Since the latest update to 52.8.0-1, the main window is corrupted. And the problem is becoming worse as I use thunderbird: it seems that the old data arent correctly overwritten. I remarked this kind of behaviour also with the experimental version. looks like a GTK+3 related issue which I can't reproduce on my installations (under Testing). If you say you see this also with Thunderbird from experimental I even more think this is mostly related to GTK+3. The Thunderbird version 52.7.0-1 is now almost 6 weeks old, version 52.8.0 and 60.0 are just some days or weeks and things in unstable moving fast. Thanks for the informations. Currently there is nothing I can suggest to do. Except to play around with Wayland/X11 and some other Desktop Environment. FYI, I just tried gnome/xwayland , gnome/x11, gnome flashback (metacity): all these flavours of gnome give the same problem (them icorrectly managed). But on the other hand, it works fine with xfce. But I will not switch to xfce, I still have some colour managment with it. I think it will not be easy to have a fix. The gtk guys have sometimes a stange way to manage the updates (API change without correct versioning for instance) Regards Jean-Luc
Bug#899099: freecad crashes at start with reference to XInitThreads
Package: freecad
Version: 0.16.6712+dfsg1-1+b2
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
I don't know, I didn't use freecad for a few weeks, there was probably an
update in X libraries.
* What exactly did you do (or not do) that was effective (or
ineffective)?
try to launch freecad, from Gnome or from the command line
* What was the outcome of this action?
nothing in the Gnome case, and the following message in the
command line case:
FreeCAD 0.16, Libs: 0.16R
© Juergen Riegel, Werner Mayer, Yorik van Havre 2001-2015
# ###
## # # # #
# ## # # # # #
# # # # # # # # # #
# # ## # # #
# # ## ## # # # ## ## ##
# # ### # # ## ## ##
failed to create drawable
[xcb] Unknown sequence number while processing queue
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been
called
[xcb] Aborting, sorry about that.
freecad: ../../src/xcb_io.c:259: poll_for_event: Assertion
`!xcb_xlib_threads_sequence_lost' failed.
Abandon
* What outcome did you expect instead?
I would have expected freecad to run
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.16.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8),
LANGUAGE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages freecad depends on:
ii libboost-atomic1.62.0 1.62.0+dfsg-5+b1
ii libboost-chrono1.62.0 1.62.0+dfsg-5+b1
ii libboost-date-time1.62.01.62.0+dfsg-5+b1
ii libboost-filesystem1.62.0 1.62.0+dfsg-5+b1
ii libboost-program-options1.62.0 1.62.0+dfsg-5+b1
ii libboost-python1.62.0 1.62.0+dfsg-5+b1
ii libboost-regex1.62.01.62.0+dfsg-5+b1
ii libboost-signals1.62.0 1.62.0+dfsg-5+b1
ii libboost-system1.62.0 1.62.0+dfsg-5+b1
ii libboost-thread1.62.0 1.62.0+dfsg-5+b1
ii libc6 2.27-3
ii libcoin80v5 3.1.4~abc9f50+dfsg3-2
ii libfreeimage3 3.17.0+ds1-5+b4
ii libfreetype62.8.1-2
ii libgcc1 1:8.1.0-3
ii libgl1 1.0.0+git20180308-2
ii libglu1-mesa [libglu1] 9.0.0-2.1
ii liboce-foundation11 0.18.2-3
ii liboce-modeling11 0.18.2-3
ii liboce-ocaf-lite11 0.18.2-3
ii liboce-ocaf11 0.18.2-3
ii liboce-visualization11 0.18.2-3
ii libpyside1.21.2.2+source1-1
ii libpython2.72.7.15-1
ii libqt4-network 4:4.8.7+dfsg-16
ii libqt4-opengl 4:4.8.7+dfsg-16
ii libqt4-svg 4:4.8.7+dfsg-16
ii libqt4-xml 4:4.8.7+dfsg-16
ii libqtcore4 4:4.8.7+dfsg-16
ii libqtgui4 4:4.8.7+dfsg-16
ii libshiboken1.2v51.2.2-5+b1
ii libsoqt4-20 1.6.0~e8310f-4
ii libspnav0 0.2.3-1
ii libstdc++6 8.1.0-3
ii libx11-62:1.6.5-1
ii libxerces-c3.2 3.2.1+debian-2
ii libxext62:1.3.3-1+b2
ii libzipios++0v5 0.1.5.9+cvs.2007.04.28-10
ii pyside-tools0.2.15-1+b1
ii python 2.7.15~rc1-1
ii python-collada 0.4-3
ii python-matplotlib 2.1.1-2
ii python-pivy 0.5.0~v609hg-4
ii python-ply 3.11-2
ii python-pyside 1.2.2+source1-1
ii python2.7 2.7.15-1
ii zlib1g 1:1.2.11.dfsg-1
freecad recommends no packages.
Versions of packages freecad suggests:
pn graphviz
pn povray
-- no debconf information
Bug#898295: libcurl3 provide libcurl4 (?), but not in the package "control" file
Package: libcurl3 Version: 7.58.0-2 Severity: normal Dear Maintainer, When I have try to install Kicad from the "ppa:js-reynaud/ppa-kicad" PPA. Synaptic say that's "kicad" package require "libcurl4" but is not installable. After some research, I have discover that's libcurl3 contain a "libcurl.so.4". I suggest to add "Provides: libcurl4" in libcurl3 package control, or to split in separate package both versions to solve this little problem. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.16.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libcurl3 depends on: ii libc6 2.27-3 ii libcomerr21.44.1-2 ii libgssapi-krb5-2 1.16-2 ii libidn2-0 2.0.4-1.1 ii libk5crypto3 1.16-2 ii libkrb5-3 1.16-2 ii libldap-2.4-2 2.4.45+dfsg-1 ii libnghttp2-14 1.31.1-1 ii libpsl5 0.20.1-1 ii librtmp1 2.4+20151223.gitfa8646d.1-1+b1 ii libssh2-1 1.8.0-1 ii libssl1.0.2 1.0.2o-1 ii zlib1g1:1.2.11.dfsg-1 Versions of packages libcurl3 recommends: ii ca-certificates 20170717 libcurl3 suggests no packages. -- no debconf information
Bug#897169: gimp: gegl version mismatch in gimp.pc.in leading to problems with gimptool
Package: gimp Version: 2.10.0-2 Severity: normal Tags: upstream -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, gimp.pc.in has still geg-0.3 harcoded in it while gimp depends on gegl-0.4 So this can lead to problems with gimptool which complains about missing lib. For instance, the error message from bulding gmic: g++ -o gmic_gimp_gtk gmic_gimp_gtk.cpp gmic_gimp_gtk.o `gimptool-2.0 --cflags` `gimptool-2.0 --libs` -I. -I/usr/include/libavcodec/ -I/usr/include/libavformat/ -I/usr/include/libswscale/ -Dgmic_build -Dcimg_use_zlib -Dgmic_prerelease=\"180429\" -std=c++11 -pedantic -Wall -Wextra -Wfatal-errors -Dcimg_use_vt100 -Dcimg_use_abort -Dgmic_is_parallel -Dcimg_use_fftw3 -Dcimg_use_curl -I/usr/include/x86_64-linux-gnu -Dcimg_use_png -I/usr/include/libpng16 -Dcimg_use_rng -DGIMP_DISABLE_DEPRECATED -fopenmp -Dcimg_use_openmp -Dcimg_display=1 -Ofast -mtune=generic -lz -L/usr/lib -lm -lpthread -lfftw3 -lfftw3_threads -lcurl -lpng16 -lz -lgomp -lX11 -lpthread Package gegl-0.3 was not found in the pkg-config search path. Perhaps you should add the directory containing `gegl-0.3.pc' to the PKG_CONFIG_PATH environment variable Package 'gegl-0.3', required by 'gimp-2.0', not found This has been addressed in the developement version of gimp: commit f6a8d93190e2e6295ed1c1a7c34b770989d6 Author: Jehan <je...@girinstud.io> Date: Sat Apr 28 01:30:19 2018 +0200 configure, gimp.pc: do no hardcode the major.minor version of GEGL. commit 7e19906827d301eb70275dba089849a632a0eabe Author: Jehan <je...@girinstud.io> Date: Sat Apr 28 00:27:31 2018 +0200 gimp.pc: Fix reference to gegl-0.3. I think this can be backported. Regards Jean-Luc - -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (600, 'unstable'), (500, 'unstable-debug'), (500, 'buildd-unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.17.0-rc2-i7-0.1 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gimp depends on: ii gimp-data2.10.0-2 ii libaa1 1.4p5-44+b1 ii libbabl-0.1-00.1.47-1.4 ii libbz2-1.0 1.0.6-8.1 ii libc62.27-3 ii libcairo21.15.10-3 ii libfontconfig1 2.13.0-4 ii libfreetype6 2.8.1-2 ii libgcc1 1:8-20180425-1 ii libgdk-pixbuf2.0-0 2.36.11-2 ii libgegl-0.4-00.4.0-1.6 ii libgexiv2-2 0.10.8-1 ii libgimp2.0 2.10.0-2 ii libglib2.0-0 2.56.1-2 ii libgs9 9.22~dfsg-2.1 ii libgtk2.0-0 2.24.32-1 ii libgudev-1.0-0 232-2 ii libharfbuzz0b1.7.6-1 ii libilmbase23 2.2.1-2 ii libjpeg62-turbo 1:1.5.2-2+b1 ii liblcms2-2 2.9-1 ii liblzma5 5.2.2-1.3 ii libmng1 1.0.10+dfsg-3.1+b5 ii libmypaint-1.3-0 1.3.0-2 ii libopenexr23 2.2.1-4 ii libopenjp2-7 2.3.0-1 ii libpango-1.0-0 1.42.1-1 ii libpangocairo-1.0-0 1.42.1-1 ii libpangoft2-1.0-01.42.1-1 ii libpng16-16 1.6.34-1 ii libpoppler-glib8 0.63.0-2 ii librsvg2-2 2.40.20-2 ii libstdc++6 8-20180425-1 ii libtiff5 4.0.9-5 ii libwebp6 0.6.1-2 ii libwebpdemux20.6.1-2 ii libwebpmux3 0.6.1-2 ii libwmf0.2-7 0.2.8.4-12 ii libx11-6 2:1.6.5-1 ii libxcursor1 1:1.1.15-1 ii libxext6 2:1.3.3-1+b2 ii libxfixes3 1:5.0.3-1 ii libxmu6 2:1.1.2-2 ii libxpm4 1:3.5.12-1 ii xdg-utils1.1.2-2 ii zlib1g 1:1.2.11.dfsg-1 Versions of packages gimp recommends: ii ghostscript 9.22~dfsg-2.1 Versions of packages gimp suggests: pn gimp-data-extras pn gimp-help-en | gimp-help pn gimp-python ii gvfs-backends 1.36.1-1 ii libasound21.1.3-5 - -- no debconf information -BEGIN PGP SIGNATURE- iF0EARECAB0WIQT5el3FKLtmYO4UlQtR0YZfPMac0AUCWuW5rgAKCRBR0YZfPMac 0DeqAKCjdEcpLcDpXxiH9TY6/HO28VRtmwCZASkqLvz14NJm0FQLM5REPMqZOJ4= =639p -END PGP SIGNATURE-
Bug#873508: sparse test failures & PATH_MAX
On Fri, Apr 27, 2018 at 09:33:55AM +0200, Uwe Kleine-König wrote: > On 04/27/2018 09:33 AM, Luc Van Oostenryck wrote: > > On Fri, Apr 27, 2018 at 07:56:38AM +0200, Uwe Kleine-König wrote: > >> Hello, > >> > >>> [..] > >> > >> Just a heads up: I uploaded 0.5.2 to Debian and there are problems left > >> on hurd-i386 (where PATH_MAX isn't defined[1]) > >> ... > >> [1] > >> https://buildd.debian.org/status/fetch.php?pkg=sparse=hurd-i386=0.5.2-1=1524168405=0 > > > > Thanks for the repport. > > I'll see what can be done. > > I think the default idiom is: > > #ifndef PATH_MAX > #define PATH_MAX 4096 > #endif Yes. I had hoped to avoid this together with removing a memcpy() but things are more annoying than I had first thought. Best regards, -- Luc
Bug#873508: sparse test failures on x32
On Fri, Apr 27, 2018 at 07:56:38AM +0200, Uwe Kleine-König wrote: > Hello, > > On 08/30/2017 06:14 PM, Uwe Kleine-König wrote: > > Antoine Beaupre (on Cc:) noticed that sparse doesn't work on some not so > > common architectures like ppc32le, s390x, ppc64 and sparc64[1]. This is > > nicely catched by the testsuite, e.g.: > > > > [..] > > Just a heads up: I uploaded 0.5.2 to Debian and there are problems left > ... > and x32 where I get: > > env CHECK=./sparse ./cgcc -no-compile memops.c > /usr/include/x86_64-linux-gnux32/gnu/stubs.h:10:12: error: unable to > open 'gnu/stubs-64.h' > > The stubs.h file looks as follows: > > #if !defined __x86_64__ > # include > #endif > #if defined __x86_64__ && defined __LP64__ > # include > #endif > #if defined __x86_64__ && defined __ILP32__ > # include > #endif > > Given that libc6-dev only provides stubs-x32.h from these three, I guess > we must not define __LP64__ in this case. Mmmm, yes, surely. For the moment sparse use __LP64__ unconditionnaly for __x86_64__. > I don't have a x32 machine But can you launch a test build for sparse easily enough? I guess that there is no install CD available yet? -- Luc
Bug#873508: sparse test failures & PATH_MAX
On Fri, Apr 27, 2018 at 07:56:38AM +0200, Uwe Kleine-König wrote: > Hello, > > On 08/30/2017 06:14 PM, Uwe Kleine-König wrote: > > Antoine Beaupre (on Cc:) noticed that sparse doesn't work on some not so > > common architectures like ppc32le, s390x, ppc64 and sparc64[1]. This is > > nicely catched by the testsuite, e.g.: > > > > [..] > > Just a heads up: I uploaded 0.5.2 to Debian and there are problems left > on hurd-i386 (where PATH_MAX isn't defined[1]) > ... > [1] > https://buildd.debian.org/status/fetch.php?pkg=sparse=hurd-i386=0.5.2-1=1524168405=0 Thanks for the repport. I'll see what can be done. -- Luc
Bug#895223: debhelper: Many packages using cmake failed to build from source since upgrade to 11.2
Le 08/04/2018 à 16:02, Mattia Rizzolo a écrit : Control: notfound -1 11.1.6 Control: forcemerge 895181 -1 On Sun, Apr 08, 2018 at 03:36:03PM +0200, Jean-Luc Coulon (f5ibh) wrote: Version: 11.1.6 I've upgraded debhelper from 11.1-6 to 11.2. Then please use a correct Version there… Sorry for that... Very sorry. Since then, many packages dont build from source. I've attached the build log of rawtherapee as an example. The same applies to hugin, lensfun,... Already fixed by 11.2.1 Ok, fine, thanks. Was not available yet when I've reported the bug. Sorry. Jean-Luc
Bug#895223: debhelper: Many packages using cmake failed to build from source since upgrade to 11.2
Package: debhelper Version: 11.1.6 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I've upgraded debhelper from 11.1-6 to 11.2. Since then, many packages dont build from source. I've attached the build log of rawtherapee as an example. The same applies to hugin, lensfun,... Regards Jean-Luc - -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (600, 'unstable'), (500, 'unstable-debug'), (500, 'buildd-unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.16.0-i7-0.1 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages debhelper depends on: ii autotools-dev20180224.1 ii dh-autoreconf17 ii dh-strip-nondeterminism 0.040-1 ii dpkg 1.19.0.5 ii dpkg-dev 1.19.0.5 ii file 1:5.32-2 ii libdpkg-perl 1.19.0.5 ii man-db 2.8.3-2 ii perl 5.26.1-5 ii po-debconf 1.0.20 debhelper recommends no packages. Versions of packages debhelper suggests: ii dh-make 2.201701 pn dwz - -- no debconf information -BEGIN PGP SIGNATURE- iF0EARECAB0WIQT5el3FKLtmYO4UlQtR0YZfPMac0AUCWsoawwAKCRBR0YZfPMac 0NoAAJ9xyprUpEsFpgw+wGUG/bMhpWlKFwCeLEZp7hF4DDjjx6QKUCedR6KvhUc= =cwdH -END PGP SIGNATURE- dpkg-buildpackage -rfakeroot -us -uc -ui dpkg-buildpackage: info: paquet source rawtherapee dpkg-buildpackage: info: version source 5.4-1 dpkg-buildpackage: info: distribution source unstable dpkg-buildpackage: info: source changé par Philip Rinn <ri...@inventati.org> dpkg-source --before-build rawtherapee-5.4 dpkg-buildpackage: info: architecture hôte amd64 fakeroot debian/rules clean dh clean dh_auto_clean dh_clean dpkg-source -b rawtherapee-5.4 dpkg-source: info: utilisation du format source « 3.0 (quilt) » dpkg-source: info: construction de rawtherapee en utilisant le ./rawtherapee_5.4.orig.tar.xz existant dpkg-source: info: construction de rawtherapee dans rawtherapee_5.4-1.debian.tar.xz dpkg-source: info: construction de rawtherapee dans rawtherapee_5.4-1.dsc debian/rules build dh build dh_update_autotools_config dh_autoreconf debian/rules override_dh_auto_configure make[1] : on entre dans le répertoire « /usr/local/src/rawtherapee/orig/rawtherapee-5.4 » dh_auto_configure -- -DCMAKE_BUILD_TYPE=Release -DCREDITSDIR=/usr/share/doc/rawtherapee -DLICENCEDIR=/usr/share/doc/rawtherapee -DPROC_FORCED_LABEL=generic -DCACHE_NAME_SUFFIX="" cd obj-x86_64-linux-gnu && cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run "-GUnix Makefiles" -DCMAKE_BUILD_TYPE=Release -DCREDITSDIR=/usr/share/doc/rawtherapee -DLICENCEDIR=/usr/share/doc/rawtherapee -DPROC_FORCED_LABEL=generic -DCACHE_NAME_SUFFIX= -- The C compiler identification is GNU 7.3.0 -- The CXX compiler identification is GNU 7.3.0 -- Check for working C compiler: /usr/bin/cc -- Check for working C compiler: /usr/bin/cc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Detecting C compile features -- Detecting C compile features - done -- Check for working CXX compiler: /usr/bin/c++ -- Check for working CXX compiler: /usr/bin/c++ -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Detecting CXX compile features -- Detecting CXX compile features - done -- CMAKE_BUILD_TYPE: Release -- Found PkgConfig: /usr/bin/pkg-config (found version "0.29") -- Checking for module 'gtk+-3.0>=3.16' -- Found gtk+-3.0, version 3.22.29 -- Checking for module 'gtkmm-3.0>=3.16' -- Found gtkmm-3.0, version 3.22.2 -- Checking for module 'glib-2.0>=2.44' -- Found glib-2.0, version 2.56.0 -- Checking for module 'glibmm-2.4>=2.44' -- Found glibmm-2.4, version 2.56.0 -- Checking for module 'cairomm-1.0' -- Found cairomm-1.0, version 1.12.2 -- Checking for module 'gio-2.0>=2.44' -- Found gio-2.0, version 2.56.0 -- Checking for module 'giomm-2.4>=2.44' -- Found giomm-2.4, version 2.56.0 -- Checking for module 'gthread-2.0>=2.44' -- Found gthread-2.0, version 2.56.0 -- Checking for module 'gobject-2.0>=2.44' -- Found gobject-2.0, version 2.56.0 -- Checking for module 'sigc++-2.0>=2.3.1' -- Found sigc++-2.0, version 2.10.0 -- Checking for module 'lensfun>=0.2' -- Found lensfun, version 0.3.2.0 -- Checking for module 'lcms2>=2.6' -- Found lcms2, version 2.9 -- Checking for module 'expat>=2.1' -- Found expat, version 2.2.5 -- Chec
Bug#894153: libreoffice-common: crash on writer, calc and impress when entering unicode codes with Ctrl-U, even for ASCII characters
Package: libreoffice-common Version: 1:6.0.2-1 Severity: normal Dear Maintainer, Since version 6, all libreoffice programs crash immediately when trying to enter characters using their unicode encoding with a Ctrl-U sequence. I used this a lot for entering greek letters in scientific documents (Ctrl-U 0 3 B 1 gives alpha: α for example) or for some typesettings characters (Ctrl-U 2 0 2 6 gives the ellipsis …). The Ctrl-U encoding still works on all applications, like terminal or event reportbug as I just used it above), but now it crashes libreoffice immediately. How to reproduce: 1) from the command line, run "libreoffice" 2) in the window, select "Create: writer document" 3) in the body of the empty "Untitled 1" document, type Ctrl-U 6 1 4) libreoffice crashes and propose to attempt recovery of the untitled document 5) after recovery, the document is still empty The hexadecimal code given in the procedure above 0x61, represents the ASCII character 'a', so it is not a problem of encoding or fonts or anything like this. The crash occurs for all characters I tried. I tried to see if it was linked to the non-ASCII characters, but this is not the case. If I type the codes above, even for greek or typesettings characters in a terminal window and then copy-paste the character in Libreoffice, the character is displayed correctly. The crash seems related to the fact I enter them from keyboard with the Ctrl-U prefix, which is pretty much standard nowadays for other Debian applications. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libreoffice-common depends on: ii libreoffice-style-tango 1:6.0.2-1 ii ure 6.0.2-1+b1 Versions of packages libreoffice-common recommends: ii fonts-liberation2 2.00.1-5 ii libexttextcat-data 3.4.5-1 ii python3-uno 1:6.0.2-1+b1 ii xdg-utils 1.1.2-2 Versions of packages libreoffice-common suggests: ii libreoffice-style-galaxy [libreoffice-style] 1:6.0.2-1 ii libreoffice-style-tango [libreoffice-style] 1:6.0.2-1 Versions of packages python3-uno depends on: ii libc6 2.27-2 ii libgcc1 1:8-20180312-2 ii libpython3.6 3.6.5~rc1-1 ii libreoffice-core 1:6.0.2-1+b1 ii libstdc++68-20180312-2 ii python3 3.6.4-1 ii python3.6 3.6.5~rc1-1 ii uno-libs3 6.0.2-1+b1 ii ure 6.0.2-1+b1 -- no debconf information
Bug#892849: [3dprinter-general] Bug#892849: Bug#892849: cura: Exception while launching cura
Hi, It was my fault. I've installed rapid-photo-downloader (https://www.damonlynch.net/rapid/). And the install process uses pip and crates some files in .local/lib .local/lib/python3.5 └── site-packages ├── arrow │ ├── api.py │ ├── arrow.py │ ├── factory.py │ ├── formatter.py │ ├── __init__.py │ ├── locales.py │ ├── parser.py [etc.] .local/lib/python3.6 └── site-packages ├── arrow │ ├── api.py │ ├── arrow.py │ ├── factory.py [etc.] and there is a whole bunch of libs there. sip.so is there also. I've (re)moved it and then I managed to have cura running. Regards Jean-Luc Le 14/03/2018 à 22:07, Gregor Riepl a écrit : ii libarcus3 3.1.0-1 amd64 message queue for Cura based on p ii python3-arcus 3.1.0-1 amd64 message queue for Cura based on p ii python3-sip 4.19.8+dfsg- amd64 Python 3/C++ bindings generator r Thank you. Unfortunately, I cannot reproduce the problem on my machine, even with these exact versions from sid installed. But I'm using a sid/stretch mix, not pure sid, so it may be related to that. On the other hand, I will submit Cura 3.2.1 soon, so perhaps a new build will help. I'll keep the bug open until then. If it still happens with 3.2.1, we'll need to debug this further.
Bug#892849: [3dprinter-general] Bug#892849: cura: Exception while launching cura
These are the available version for sid Le 13/03/2018 à 20:52, Gregor Riepl a écrit : dpkg-query -l libarcus3 python3-arcus python3-sip dpkg-query -l libarcus3 python3-arcus python3-sip Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder | État=Non/Installé/fichier-Config/dépaqUeté/échec-conFig/H=semi-installé/W=attend-traitement-déclenchements |/ Err?=(aucune)/besoin Réinstallation (État,Err: majuscule=mauvais) ||/ Nom Version Architecture Description +++-==---= ii libarcus3 3.1.0-1 amd64 message queue for Cura based on p ii python3-arcus 3.1.0-1 amd64 message queue for Cura based on p ii python3-sip 4.19.8+dfsg- amd64 Python 3/C++ bindings generator r
Bug#892849: cura: Exception while launching cura
Package: cura Version: 3.1.0-1 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, While laaunching cura, I get the following: Error in sys.excepthook: Traceback (most recent call last): File "", line 983, in _find_and_load File "", line 967, in _find_and_load_unlocked File "", line 677, in _load_unlocked File "", line 678, in exec_module File "", line 219, in _call_with_frames_removed File "/usr/lib/python3/dist-packages/cura/CrashHandler.py", line 20, in from UM.Application import Application File "/usr/lib/python3/dist-packages/UM/Application.py", line 15, in from UM.Settings.ContainerRegistry import ContainerRegistry File "/usr/lib/python3/dist-packages/UM/Settings/ContainerRegistry.py", line 36, in import UM.Qt.QtApplication File "/usr/lib/python3/dist-packages/UM/Qt/QtApplication.py", line 15, in from UM.FileHandler.ReadFileJob import ReadFileJob File "/usr/lib/python3/dist-packages/UM/FileHandler/ReadFileJob.py", line 5, in from UM.Application import Application ImportError: cannot import name 'Application' Original exception was: Traceback (most recent call last): File "/usr/bin/cura", line 54, in import Arcus #@UnusedImport RuntimeError: the sip module implements API v12.0 to v12.2 but the Arcus module requires API v12.3 Regards Jean-Luc - -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (600, 'unstable'), (500, 'unstable-debug'), (500, 'buildd-unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.16.0-rc5-i7-0.1 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages cura depends on: ii cura-engine 1:3.1.0-2 ii fonts-open-sans 1.11-1 ii python3 3.6.4-1 ii python3-pyqt5 5.9.2+dfsg-1 ii python3-pyqt5.qtopengl 5.9.2+dfsg-1 ii python3-savitar 3.1.0-1 ii python3-serial 3.4-1 ii python3-uranium 3.1.0-1 ii qml-module-qt-labs-folderlistmodel 5.9.2-3 ii qml-module-qt-labs-settings 5.9.2-3 ii qml-module-qtqml-models25.9.2-3 ii qml-module-qtquick-controls 5.9.2-2 ii qml-module-qtquick-dialogs 5.9.2-2 ii uranium-plugins 3.1.0-1 Versions of packages cura recommends: ii fdm-materials 3.1.0-1 ii python3-zeroconf 0.19.1-1 cura suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- iF0EARECAB0WIQT5el3FKLtmYO4UlQtR0YZfPMac0AUCWqgdMQAKCRBR0YZfPMac 0E/FAJ41rnMVzefh1QCGodicZkcNUbPH5gCffL6QLGqTuOgyQOGxU/9uo1Gj/P4= =nEEw -END PGP SIGNATURE-
Bug#868218: problem still there, only workaround available would be to disclose confidential information to remote users
Hello, I have files this bug report more than 7 months ago and no progress have been seen so far, depite several new versions of the package have been published. The bug was files against version 52.2.1, were are now at 52.6.0. I really think this is big problem and even a security threat. The current behaviour forces user to either put the exact same password to several accounts (hence someone guessing one password will get access to all accounts and their confidential informations) or to store passwords (and by the way thunderbird seems to not even be able to use passwords it already stored, it keeps asking for them, despite having already registered them, pre-filling all entries it its popup and checking by itself the "store password field", but this is another story). May be I was not clear enough in the first report, so lets try again. I have one (really only ONE) server that holds several caldav accounts, say "work", "teaching", "health", "legal", "shared-with-family", "shared-with-business-partners", "shared-with-friends", "you-name-it". Some calendars are accessed not only by me, but by other people and the people having access to "shared-with-business-partners" should not have access to "shared-with-family", so the passwords are different. the only work-around would be to use the same username/password for all calendars, but this would imply the confidential informations from one calendar becomes available to people having access to another calendar, even when they should not be able to access it. And this happens regardless of their cladav client: the thunderbird bug forces to configure the *server* in an insecure way because it is the only way thunderbird will be able to access properly a bunch of calendars hosted by a single server. The current behaviour only ask me for a pair username/password *without* even telling me to which calendar name correspond each popup. Upon launching thunderbird, I get a bunch of requests, all the same, only ginving me the name of the server, but this name is the same for all calendars, so I cannot guess. If I try pairs of usernames/password at random, I even get kicked of the server after too many attempts due to protections like fail2ban. Before July 2017, the requests included the name for which the password was requested (i.e. here the calendar name) in the popup asking for the credentials. The current behaviour is akin to a program telling you: I need a password but I will not tell you what for, just give one to me and I will not even tell you what I will do with it Removing from the credentials request popup the information allowing to provide the correct credentials is counter-productive and, imho, decreases security. As explained above, either you allow everyone to see all your confidential information because you end up using the same password for everything, or you don't have access to your own data because you are kicked off the server after too many failed attempts. best regards, Luc
Bug#891082: Fwd: Bug#891082: xvkbd: Regression in using some definition for mouse "back" a nd "forward" buttons
Hi Paul,
Le 24/02/2018 à 19:41, Paul Gevers a écrit :
Control: tags -1 patch confirmed
Hi Jean-Luc,
Are you in the position to test a patch?
Done...
And it works for me [tm]!
Whaou... very reactive!
Thanks and regards
Jezn-Luc
Paul
--- ../xvkbd-3.8/xvkbd.c2017-06-06 19:24:16.897060353 +0900
+++ xvkbd.c 2018-02-24 16:27:45.559394153 +0900
@@ -1513,6 +1513,11 @@
unsigned junk_u;
int cur_x, cur_y;
+ if (need_read_keymap) {
+need_read_keymap = FALSE;
+ReadKeymap();
+ }
+
shift_state = 0;
for (cp = str; *cp != '\0'; cp++) {
if (0 < appres.text_delay) usleep(appres.text_delay * 1000);
Bug#891082: xvkbd: Regression in using some definition for mouse "back" and "forward" buttons
Package: xvkbd Version: 3.3-2 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I've a Logitech M560 Mouse. It has 2 extra buttons on the side. I used to use them for back and forward in the browser. To affect these keys, I've the follwing in my .xbindkeysrc confiuration file: "/usr/bin/xvkbd -xsendevent -text "\[Alt_L]\[Left]"" m:0x0 + b:11 "/usr/bin/xvkbd -xsendevent -text "\[Alt_L]\[Right]"" m:0x0 + b:10 this works as expected with version 3.2 for years. After the recent upgrade to 3.8, this stops working. Regards Jean-Luc - -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (600, 'unstable'), (500, 'unstable-debug'), (500, 'buildd-unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.16.0-rc2-i7-0.1 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages xvkbd depends on: ii libc6 2.26-6 ii libice6 2:1.0.9-2 ii libsm62:1.2.2-1+b3 ii libx11-6 2:1.6.4-3 ii libxext6 2:1.3.3-1+b2 ii libxmu6 2:1.1.2-2 ii libxpm4 1:3.5.12-1 ii libxt61:1.1.5-1 ii libxtst6 2:1.2.3-1 ii xaw3dg1.5+E-18.3 Versions of packages xvkbd recommends: ii wamerican [wordlist] 2017.08.24-1 ii wfrench [wordlist]1.2.3-11 xvkbd suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- iF0EARECAB0WIQT5el3FKLtmYO4UlQtR0YZfPMac0AUCWo6LiQAKCRBR0YZfPMac 0OnZAKCqyR4y8LSXi70JZokZIL7FInZMUgCfW+QCwxIciZwQi33cHZD4GezzVxw= =h+dK -END PGP SIGNATURE-
Bug#884372: openshot-qt hangs at start: No module named 'PyQt5.QtWebKitWidgets'
Package: openshot-qt
Version: 2.4.0-1
Severity: important
Tags: upstream
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
When I start openshot-qt, I get the log you can see below. Then the application
stays in this state, nothing else happening.
I've tested with upstream package, I get the same problem.
If I use the upstream AppImage package, it works.
I've seen on upstream discussions the same kind of problem reported, and the
answer is "use the AppImage".
You will see in the log it complains about missing PyQt5.QtWebKitWidgets module.
But the module is on the system from python-pyqt5 package.
ls /usr/lib/python2.7/dist-packages/PyQt5 | grep WebKitWidgets
QtWebKitWidgets.x86_64-linux-gnu_d.so
QtWebKitWidgets.x86_64-linux-gnu.so
and the related py/pyc files are there also:
ls /usr/lib/python2.7/dist-packages/PyQt5/uic/widget-plugins | grep -i webkit
qtwebkit.py
qtwebkit.pyc
Regards
Jean-Luc
openshot-qt
Loaded modules from installed directory:
/usr/lib/python3/dist-packages/openshot_qt
launch:INFO
launch:INFOOpenShot (version 2.4.0)
launch:INFO
app:INFO openshot-qt version: 2.4.0
app:INFO libopenshot version: 0.1.9
app:INFO platform:
Linux-4.15.0-rc3-i7-0.1-x86_64-with-debian-buster-sid
app:INFO processor:
app:INFO machine: x86_64
app:INFO python version: 3.6.4rc1
app:INFO qt5 version: 5.9.1
app:INFO pyqt5 version: 5.9
language:INFO Attempting to load qt_fr_FR.UTF-8 in
'/home/jean-luc/.local/lib/python3.6/site-packages/PyQt5/Qt/translations'
language:INFO Attempting to load qt_fr in
'/home/jean-luc/.local/lib/python3.6/site-packages/PyQt5/Qt/translations'
language:INFO Attempting to load fr_FR.UTF-8/LC_MESSAGES/OpenShot in
'/usr/lib/python3/dist-packages/openshot_qt/locale'
language:INFO Attempting to load fr/LC_MESSAGES/OpenShot in
'/usr/lib/python3/dist-packages/openshot_qt/locale'
language:INFO Successfully loaded fr/LC_MESSAGES/OpenShot in
'/usr/lib/python3/dist-packages/openshot_qt/locale'
language:INFO Qt Detected Languages: ['fr-FR']
language:INFO LANG Environment Variable: fr_FR.UTF-8
language:INFO LOCALE Environment Variable: fr_FR
language:INFO Attempting to load qt_fr_FR.UTF-8 in
'/home/jean-luc/.local/lib/python3.6/site-packages/PyQt5/Qt/translations'
language:INFO Attempting to load qt_fr in
'/home/jean-luc/.local/lib/python3.6/site-packages/PyQt5/Qt/translations'
language:INFO Attempting to load qtbase_fr_FR.UTF-8 in
'/home/jean-luc/.local/lib/python3.6/site-packages/PyQt5/Qt/translations'
language:INFO Successfully loaded qtbase_fr_FR.UTF-8 in
'/home/jean-luc/.local/lib/python3.6/site-packages/PyQt5/Qt/translations'
language:INFO Attempting to load qt_fr_FR.UTF-8 in
'/usr/lib/python3/dist-packages/openshot_qt/locale/QT'
language:INFO Attempting to load qt_fr in
'/usr/lib/python3/dist-packages/openshot_qt/locale/QT'
language:INFO Attempting to load qtbase_fr_FR.UTF-8 in
'/usr/lib/python3/dist-packages/openshot_qt/locale/QT'
language:INFO Attempting to load qtbase_fr in
'/usr/lib/python3/dist-packages/openshot_qt/locale/QT'
language:INFO Attempting to load fr_FR.UTF-8/LC_MESSAGES/OpenShot in
'/usr/lib/python3/dist-packages/openshot_qt/locale'
language:INFO Attempting to load fr/LC_MESSAGES/OpenShot in
'/usr/lib/python3/dist-packages/openshot_qt/locale'
language:INFO Successfully loaded fr/LC_MESSAGES/OpenShot in
'/usr/lib/python3/dist-packages/openshot_qt/locale'
language:INFO Exiting translation system (since we successfully loaded:
fr_FR.UTF-8)
project_data:INFO Setting default profile to HDV 720 24p
app:INFO Setting font to
/usr/lib/python3/dist-packages/openshot_qt/images/fonts/Ubuntu-R.ttf
logger_libopenshot:INFO Connecting to libopenshot with debug port: 5556
app:INFO Setting custom dark theme
exceptions:ERROR Unhandled Exception
Traceback (most recent call last):
File "/usr/bin/openshot-qt", line 11, in
load_entry_point('openshot-qt==2.4.0', 'gui_scripts', 'openshot-qt')()
File "/usr/lib/python3/dist-packages/openshot_qt/launch.py", line 70, in main
app = OpenShotApp(sys.argv)
File "/usr/lib/python3/dist-packages/openshot_qt/classes/app.py", line 163,
in __init__
from windows.main_window import MainWindow
File "/usr/lib/python3/dist-packages/openshot_qt/windows/main_window.py",
line 43, in
from windows.views.timeline_webview import TimelineWebView
File
"/usr/lib/python3/dist-packages/openshot_qt/windows/views/timeline_webview.py",
line 40, in
from PyQt5.QtWebKitWidgets import QWebView
ModuleNotFoundError: No module named 'PyQt5.QtWebKitWidgets'
metrics:INFO Track exception: [200]
http://www.openshot.org/exception/json/ | *old-exception-ignored*
- -- System In
Bug#880223: build log attached
Sorry, I forgot the build log
Jena-Luc
dpkg-buildpackage -rfakeroot -us -uc -ui
dpkg-buildpackage: info: paquet source calibre
dpkg-buildpackage: info: version source 3.10.0+dfsg-1
dpkg-buildpackage: info: distribution source unstable
dpkg-buildpackage: info: source changé par Norbert Preining
<prein...@debian.org>
dpkg-source --before-build calibre-3.10.0+dfsg
dpkg-buildpackage: info: architecture hôte amd64
fakeroot debian/rules clean
test -x debian/rules
dh_clean
rm -rf debian/orig
[ ! -d build ] || python2.7 setup.py build -c
find . -name *.pyc -delete
find . -name *.so -delete
find . -name *.qrc -delete
dpkg-source -b calibre-3.10.0+dfsg
dpkg-source: info: utilisation du format source « 3.0 (quilt) »
dpkg-source: info: construction de calibre en utilisant le
./calibre_3.10.0+dfsg.orig.tar.xz existant
dpkg-source: avertissement: suppression du fichier resources/images.qrc
ignorée, utilisez --include-removal pour la prendre en compte
dpkg-source: info: construction de calibre dans
calibre_3.10.0+dfsg-1.debian.tar.xz
dpkg-source: info: construction de calibre dans calibre_3.10.0+dfsg-1.dsc
debian/rules build
test -x debian/rules
mkdir -p "."
CDBS WARNING:DEB_DH_INSTALL_ARGS is deprecated since 0.4.85
[ -d build ] || python2.7 setup.py build
*
* Running build
*
qmake: could not exec '/usr/lib/x86_64-linux-gnu/qt5/bin/qmake' since it links
to qmake itself. Check your installation.
Traceback (most recent call last):
File "setup.py", line 119, in
sys.exit(main())
File "setup.py", line 104, in main
command.run_all(opts)
File "/usr/local/src/calibre/orig/calibre-3.10.0+dfsg/setup/__init__.py",
line 236, in run_all
self.run_cmd(self, opts)
File "/usr/local/src/calibre/orig/calibre-3.10.0+dfsg/setup/__init__.py",
line 232, in run_cmd
cmd.run(opts)
File "/usr/local/src/calibre/orig/calibre-3.10.0+dfsg/setup/build.py", line
245, in run
self.env = init_env()
File "/usr/local/src/calibre/orig/calibre-3.10.0+dfsg/setup/build.py", line
140, in init_env
from setup.build_environment import msvc, is64bit, win_inc, win_lib, NMAKE
File
"/usr/local/src/calibre/orig/calibre-3.10.0+dfsg/setup/build_environment.py",
line 71, in
qraw = subprocess.check_output([QMAKE, '-query']).decode('utf-8')
File "/usr/lib/python2.7/subprocess.py", line 219, in check_output
raise CalledProcessError(retcode, cmd, output=output)
subprocess.CalledProcessError: Command '['/usr/bin/qmake', '-query']' returned
non-zero exit status 1
debian/rules:21 : la recette pour la cible « common-build-arch » a échouée
make: *** [common-build-arch] Erreur 1
dpkg-buildpackage: erreur: debian/rules build subprocess returned exit status 2
Bug#880223: calibre: Doesnt build from source since latest qtchooser update in sid
Package: calibre Version: 3.10.0+dfsg-1 Severity: serious Justification: fails to build from source (but built successfully in the past) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Since latest qtchooser update, calibre fails to build from source. See #880159. According to this bug report, this problem should be fixed with qtchooser 4-ga1b6736-4 I've tested several other packages and this is true for them but not for calibre. Regards Jean-Luc - -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (600, 'unstable'), (500, 'unstable-debug'), (500, 'buildd-unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-rc7-i7-0.1 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages calibre depends on: ii calibre-bin 3.10.0+dfsg-1+b1 ii fonts-liberation 1:1.07.4-5 ii imagemagick 8:6.9.7.4+dfsg-16 ii imagemagick-6.q16 [imagemagick] 8:6.9.7.4+dfsg-16 ii libjs-coffeescript 1.12.7~dfsg-3 ii libjs-mathjax2.7.0-2 ii poppler-utils0.57.0-2 ii python-apsw 3.16.2-r1-2+b1 ii python-beautifulsoup 3.2.1-1 ii python-chardet 3.0.4-1 ii python-cherrypy3 3.5.0-2 ii python-cssselect 1.0.1-1 ii python-cssutils 1.0.2-1 ii python-dateutil 2.6.1-1 ii python-dbus 1.2.4-1+b3 ii python-feedparser5.1.3-3 ii python-html5-parser 0.4.3-1 ii python-lxml 4.0.0-1 ii python-markdown 2.6.9-1 ii python-mechanize 1:0.2.5-3 ii python-msgpack 0.4.8-1+b1 ii python-netifaces 0.10.4-0.1+b3 ii python-pil 4.3.0-2 ii python-pkg-resources 36.2.7-2 ii python-pyparsing 2.1.10+dfsg1-1 ii python-pyqt5 5.9+dfsg-2+b2 ii python-pyqt5.qtsvg 5.9+dfsg-2+b2 ii python-pyqt5.qtwebkit5.9+dfsg-2+b2 ii python-regex 0.1.20170117-1+b1 ii python-routes2.4.1-1 ii python2.72.7.14-2 ii xdg-utils1.1.2-1 Versions of packages calibre recommends: ii python-dnspython 1.15.0-1 calibre suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- iF0EARECAB0WIQT5el3FKLtmYO4UlQtR0YZfPMac0AUCWfduTQAKCRBR0YZfPMac 0MEiAJwKtH0jzl0qosP2hRU6PT8venxAxwCdGwBlnty4xzDxnJ25+7l8YjfRE/o= =8YuU -END PGP SIGNATURE-
Bug#873508: sparse test failures on ppc32le (and other not so common archs)
On Wed, Sep 27, 2017 at 10:00 AM, Uwe Kleine-König
<u...@kleine-koenig.org> wrote:
> Hello,
>
> On Tue, Sep 26, 2017 at 08:11:01PM +0200, Uwe Kleine-König wrote:
>> And ppc64 and x32 need the respective cpp defines added I think. If
>> noone beats me to it, I will look into the latter at least during the
>> next few days.
>
> Looking at ppc64, the following fixes the build:
>
> diff --git a/cgcc b/cgcc
> index a8d7b4f217fe..a1c02899c623 100755
> --- a/cgcc
> +++ b/cgcc
> @@ -286,7 +286,7 @@ sub add_specs {
> } elsif ($spec eq 'ppc64') {
> return (' -D__powerpc__=1 -D__PPC__=1 -D_STRING_ARCH_unaligned=1' .
> ' -D__powerpc64__=1 -D__PPC64__=1' .
> - ' -D_CALL_ELF=2' .
> + ' -D_CALL_ELF=1' .
> ' -m64' .
> _types (1, 1, 21, [24,8], [53,11], [113,15]));
> } elsif ($spec eq 's390x') {
>
> I wonder if that could be right. Luc, you added =2 in
> e0306fe0b725af6e2e7ff59d7f0d99c96315791a, maybe you can comment?
Neither =2 or =1 is correct, it depends on which version of the ELF
ABI you're using.
This in turn (as I understood) is most of the time tied to fact that
you're using ppc64le
(which normally needs ELFv2) or not.
I can't look at this now but will do this evening.
-- Luc
Bug#876336: clementine: related to libqt4-network from experimental
Package: clementine Followup-For: Bug #876336 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The segfault is related to libqt4-network. I have it from experimental: 4:4.8.7+dfsg-12 and clementine segfaults with it. I've reverted to 4:4.8.7+dfsg-11 and the problem is gone. Regards Jean-Luc - -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (600, 'unstable'), (500, 'unstable-debug'), (500, 'buildd-unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-rc1-i7-0.1 (SMP w/8 CPU cores; PREEMPT) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages clementine depends on: ii gstreamer1.0-plugins-base 1.12.3-1 ii gstreamer1.0-plugins-good 1.12.3-1 ii gstreamer1.0-plugins-ugly 1.12.3-1 ii libc6 2.24-17 ii libcdio13 0.83-4.3+b1 ii libchromaprint1 1.4.2-1 ii libcrypto++65.6.4-8 ii libfftw3-double33.3.6p2-2 ii libgcc1 1:7.2.0-6 ii libgdk-pixbuf2.0-0 2.36.10-2 ii libglib2.0-02.54.0-1 ii libgpod40.8.3-8.2 ii libgstreamer-plugins-base1.0-0 1.12.3-1 ii libgstreamer1.0-0 1.12.3-1 ii libimobiledevice6 1.2.0+dfsg-3.1+b1 ii liblastfm1 1.0.9-1 ii libmtp9 1.1.13-1 ii libmygpo-qt11.0.9-2 ii libplist3 2.0.0-2 ii libprojectm2v5 2.1.0+dfsg-4+b3 ii libprotobuf10 3.0.0-9 ii libpulse0 11.1-1 ii libqjson0 0.8.1-3+b1 ii libqt4-dbus 4:4.8.7+dfsg-11 ii libqt4-network 4:4.8.7+dfsg-11 ii libqt4-opengl 4:4.8.7+dfsg-11 ii libqt4-sql 4:4.8.7+dfsg-11 ii libqt4-sql-sqlite 4:4.8.7+dfsg-11 ii libqt4-xml 4:4.8.7+dfsg-11 ii libqtcore4 4:4.8.7+dfsg-11 ii libqtgui4 4:4.8.7+dfsg-11 ii libqxt-gui0 0.6.2-3 ii libsqlite3-03.20.1-1 ii libstdc++6 7.2.0-6 ii libtag1v5 1.11.1+dfsg.1-0.1 ii libx11-62:1.6.4-3 ii projectm-data 2.1.0+dfsg-4 ii zlib1g 1:1.2.8.dfsg-5 Versions of packages clementine recommends: ii gstreamer1.0-pulseaudio 1.12.3-1 Versions of packages clementine suggests: ii gstreamer1.0-plugins-bad 1.12.3-1 - -- no debconf information -BEGIN PGP SIGNATURE- iF0EARECAB0WIQT5el3FKLtmYO4UlQtR0YZfPMac0AUCWcPoYwAKCRBR0YZfPMac 0In4AJ9Os1nJdpbHLRm8eicUSgalaK/7bwCgo5Qetob2hf2grAKcfyetljLEcoU= =i82O -END PGP SIGNATURE-
Bug#876391: libqt4-network:amd64: libqt4-network 4:4.8.7+dfsg-11 from experimental causes clementine to segfault
Package: libqt4-network Version: 4:4.8.7+dfsg-11 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I've got libqt4-network from experimental : 4:4.8.7+dfsg-12 (and other parts of qt4 as well). With this version, clementine segfault. I've reported the bug on clementine, see: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876336 But I remarked that reversing to 4:4.8.7+dfsg-11 fixes the problem. Regards Jean-Luc - -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (600, 'unstable'), (500, 'unstable-debug'), (500, 'buildd-unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-rc1-i7-0.1 (SMP w/8 CPU cores; PREEMPT) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages libqt4-network:amd64 depends on: ii libc6 2.24-17 ii libgcc1 1:7.2.0-6 ii libqtcore4 4:4.8.7+dfsg-11 ii libqtdbus4 4:4.8.7+dfsg-11 ii libstdc++6 7.2.0-6 ii zlib1g 1:1.2.8.dfsg-5 Versions of packages libqt4-network:amd64 recommends: ii ca-certificates 20170717 libqt4-network:amd64 suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- iF0EARECAB0WIQT5el3FKLtmYO4UlQtR0YZfPMac0AUCWcPppwAKCRBR0YZfPMac 0O7lAKCBUxYzqBxLkodn1+bBHlPubY6oXgCeKb6pOZb+oPYZ1/8dg1TDNs3J2po= =9OBV -END PGP SIGNATURE-
Bug#876336: clementine: Clementine segfault at start
Package: clementine Version: 1.3.1+git276-g3485bbe43+dfsg-1 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I experience systemetic segfault at start. Please find attached the backtrace. Regards Jean-Luc - -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (600, 'unstable'), (500, 'unstable-debug'), (500, 'buildd-unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-rc1-i7-0.1 (SMP w/8 CPU cores; PREEMPT) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages clementine depends on: ii gstreamer1.0-plugins-base 1.12.3-1 ii gstreamer1.0-plugins-good 1.12.3-1 ii gstreamer1.0-plugins-ugly 1.12.3-1 ii libc6 2.24-17 ii libcdio13 0.83-4.3+b1 ii libchromaprint1 1.4.2-1 ii libcrypto++65.6.4-8 ii libfftw3-double33.3.6p2-2 ii libgcc1 1:7.2.0-6 ii libgdk-pixbuf2.0-0 2.36.10-2 ii libglib2.0-02.54.0-1 ii libgpod40.8.3-8.2 ii libgstreamer-plugins-base1.0-0 1.12.3-1 ii libgstreamer1.0-0 1.12.3-1 ii libimobiledevice6 1.2.0+dfsg-3.1+b1 ii liblastfm1 1.0.9-1 ii libmtp9 1.1.13-1 ii libmygpo-qt11.0.9-2 ii libplist3 2.0.0-2 ii libprojectm2v5 2.1.0+dfsg-4+b3 ii libprotobuf10 3.0.0-9 ii libpulse0 11.1-1 ii libqjson0 0.8.1-3+b1 ii libqt4-dbus 4:4.8.7+dfsg-12 ii libqt4-network 4:4.8.7+dfsg-12 ii libqt4-opengl 4:4.8.7+dfsg-12 ii libqt4-sql 4:4.8.7+dfsg-12 ii libqt4-sql-sqlite 4:4.8.7+dfsg-12 ii libqt4-xml 4:4.8.7+dfsg-12 ii libqtcore4 4:4.8.7+dfsg-12 ii libqtgui4 4:4.8.7+dfsg-12 ii libqxt-gui0 0.6.2-3 ii libsqlite3-03.20.1-1 ii libstdc++6 7.2.0-6 ii libtag1v5 1.11.1+dfsg.1-0.1 ii libx11-62:1.6.4-3 ii projectm-data 2.1.0+dfsg-4 ii zlib1g 1:1.2.8.dfsg-5 Versions of packages clementine recommends: ii gstreamer1.0-pulseaudio 1.12.3-1 Versions of packages clementine suggests: ii gstreamer1.0-plugins-bad 1.12.3-1 - -- no debconf information -BEGIN PGP SIGNATURE- iF0EARECAB0WIQT5el3FKLtmYO4UlQtR0YZfPMac0AUCWcNshQAKCRBR0YZfPMac 0NF2AJ90mTfPFOhCDS3im0WQvXMrdEobxwCcDxJ/N08wnk/udkzF7yqgfsLaFr8= =rXlJ -END PGP SIGNATURE- clementine-gdb-bt.txt.gz Description: application/gzip
