Bug#1069228: indeed

2024-05-25 Thread VA
Indeed, the `-I` description is invalid, and after a closer look, there 
are more problems in this poorly translated manual page.

`--rfc-3339` has the same issue.

This part was also poorly translated:

> After any flags comes an optional field width, as a decimal number; 
then an optional modifier, which is either E to use the locale's 
alternate representations if available, or O to use the locale's 
alternate numeric symbols if available.


In English, it's a LATIN CAPITAL LETTER O. In French page, it became a 
DIGIT ZERO…


I tried to patch the file at 
https://salsa.debian.org/debian/manpages-l10n/-/blob/60ee9a5e/po/fr/man1/date.1.po, 
using Colomban's proposal, but I can't verify if the resulting manual 
page builds correctly and is ok. See attached patch.diff --git a/po/fr/man1/date.1.po b/po/fr/man1/date.1.po
index 7658b65c2f..b75f233089 100644
--- a/po/fr/man1/date.1.po
+++ b/po/fr/man1/date.1.po
@@ -164,9 +164,10 @@ msgid ""
 "default), \\&'hours', 'minutes', 'seconds', or 'ns' for date and time to the "
 "indicated precision.  Example: 2006-08-14T02:34:56-06:00"
 msgstr ""
-"afficher la date et l'heure au format ISO 8601. I=« date » pour la date "
-"seulement (par défaut), \\&« heures », « minutes », « secondes » ou "
-"« nanosecondes » pour la date et l'heure selon la précision indiquée. "
+"afficher la date et l'heure au format ISO 8601. FMT='date' pour la date "
+"seulement (par défaut), ou \\&'hours', 'minutes', 'seconds' ou 'ns' pour la "
+"date et l'heure avec une précision respectivement à l'heure, la minute, la "
+"seconde ou la nanoseconde. "
 "Exemple : 2006-08-14T02:34:56-06:00"
 
 #. type: TP
@@ -215,8 +216,9 @@ msgid ""
 "date and time to the indicated precision.  Example: 2006-08-14 02:34:56-06:00"
 msgstr ""
 "afficher la date et l'heure dans un format conforme aux spécifications "
-"RFC 3339. FMT=« date », « secondes » ou « ns » pour la date et l'heure à la "
-"précision indiquée. Exemple : 2006-08-14 02:34:56-06:00"
+"RFC 3339. FMT='date', 'seconds' ou 'ns' pour la date et l'heure à une "
+"précision respectivement à l'heure, à la seconde ou à la nanoseconde. "
+"Exemple : 2006-08-14 02:34:56-06:00"
 
 #. type: TP
 #: archlinux debian-bookworm debian-unstable fedora-40 fedora-rawhide
@@ -1036,7 +1038,7 @@ msgid ""
 msgstr ""
 "Chaque indicateur peut être suivi d'un attribut de largeur optionnel sous "
 "forme de nombre décimal, puis d'un commutateur optionnel qui peut être «\\ "
-"E\\ » pour utiliser la mise en forme régionale si disponible ou «\\ 0\\ » "
+"E\\ » pour utiliser la mise en forme régionale si disponible ou «\\ O\\ » "
 "pour utiliser les symboles numériques régionaux si disponibles"
 
 #. type: SH


Bug#1071733: French date(1) contains several errors

2024-05-24 Thread VA

Package: manpages-fr
Version: 4.22.0-1

French date(1) contains several errors

   %D date ; équivalent à « %d/%m/%y »

   %F date complète ; identique à « %+4A-%m-%j »

which are plain wrong. For compoarison, English manual page contains

   %D date; same as %m/%d/%y

   %F full date; like %+4Y-%m-%d

which are correct.



Bug#1068973: include upstream zsh completion

2024-04-14 Thread VA

Package: eza
Version: 0.18.9-1

Upstream has it: 
https://github.com/eza-community/eza/blob/main/completions/zsh/_eza

Should be put in /usr/share/zsh/vendor-completions I guess



Bug#1067158: pip3-* manual pages could be aliased

2024-03-19 Thread VA

Package: python3-pip
Version: 24.0+dfsg-2
Severity: wishlist

Just like `man pip` is equivalent to `man pip3`, `man pip-install` (and 
other subcommands) could be equivalent to e.g. `man pip3-install`.




Bug#1063528: calling less PAGER a second time after resizing the terminal does not use new size

2024-02-09 Thread VA

Package: ipython3
Version: 8.20.0-1

- Start with a 80x24 terminal
- Set "export PAGER=less"
- Open "ipython3"
- Run "import os"
- Run "os??"
- Press "q" to quit pager
- Maximize terminal window
- Run again "os??"
- Scroll view with pagedown/pageup

With xterm, the text scrolled is clipped into a 80x24 area in the 
top-left area corner, which is suboptimal.


With several libvte-based terminals, scrolling down displays a new 80x24 
page of the text but below the previous page. Scrolling up does very 
confusing things, which is worse.




Bug#1063519: Qt.ColorScheme enum is not exposed

2024-02-09 Thread VA

Package: python3-pyqt6
Version: 6.6.1-2

>>> PyQt6.QtCore.Qt.ClipOperation

>>> PyQt6.QtCore.Qt.ColorScheme
AttributeError: type object 'Qt' has no attribute 'ColorScheme'

It's present in the documentation: 
https://www.riverbankcomputing.com/static/Docs/PyQt6/api/qtcore/qt.html#ColorScheme

So it should be exposed



Bug#1061184: manual page is incorrect

2024-01-20 Thread VA

Package: python3-pip
Version: 23.3+dfsg-1

The pip manual page refers to options which don't exist, example:

% man pip | grep download-cache
   --download-cache 
% pip install --download-cache pip
[…]
no such option: --download-cache



Bug#1006956: Acknowledgement (tt-rss spits a lot of php warnings)

2023-11-03 Thread VA

severity 1006956 important
thanks

Are there any news on this? In just one week:

journalctl -S 2023-10-27 _SYSTEMD_UNIT=tt-rss.service | wc -l
1057249

And logs that are not about garbage:

journalctl -S 2023-10-27 _SYSTEMD_UNIT=tt-rss.service | grep -iv warning 
| grep -iv deprecated | wc -l

1051

So a whopping 99.9% of tt-rss logs are absolute garbage that just point 
at badly written code.
The best thing would be of course to fix those deprecation warnings, but 
at least we could hide them to avoid consuming disk space with 
completely useless stuff.




Bug#1053996: fails to find driver though it's in PATH

2023-10-15 Thread VA

Package: python3-selenium
Version: 4.13.0-1

It seems the packaged version can't find geckodriver even though it's in 
$PATH.


Step 1: Downloading geckodriver from documented link 
https://selenium-python.readthedocs.io/installation.html#drivers:


```
curl -L 
https://github.com/mozilla/geckodriver/releases/download/v0.33.0/geckodriver-v0.33.0-linux64.tar.gz 
| tar xzf -

mv geckodriver /bin
```

Step 2: Running python snippet taken from 
https://selenium-python.readthedocs.io/getting-started.html#example-explained:


```
from selenium import webdriver
driver = webdriver.Firefox()
```

Yields a failure accessing an undocumented env variable:

```
Traceback (most recent call last):
  File 
"/usr/lib/python3/dist-packages/selenium/webdriver/common/driver_finder.py", 
line 38, in get_path
path = SeleniumManager().driver_location(options) if path is None 
else path

   ^^
  File 
"/usr/lib/python3/dist-packages/selenium/webdriver/common/selenium_manager.py", 
line 81, in driver_location

args = [str(self.get_binary()), "--browser", browser]
^
  File 
"/usr/lib/python3/dist-packages/selenium/webdriver/common/selenium_manager.py", 
line 60, in get_binary

if not path.is_file() and os.environ["CONDA_PREFIX"]:
  ~~
  File "", line 679, in __getitem__
KeyError: 'CONDA_PREFIX'

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "", line 1, in 
  File 
"/usr/lib/python3/dist-packages/selenium/webdriver/firefox/webdriver.py", 
line 59, in __init__

self.service.path = DriverFinder.get_path(self.service, options)

  File 
"/usr/lib/python3/dist-packages/selenium/webdriver/common/driver_finder.py", 
line 41, in get_path

raise NoSuchDriverException(msg) from err
selenium.common.exceptions.NoSuchDriverException: Message: Unable to 
obtain driver for firefox using Selenium Manager.; For documentation on 
this error, please visit: 
https://www.selenium.dev/documentation/webdriver/troubleshooting/errors/driver_location

```

So I made the variable exist, but let it empty:

```
Traceback (most recent call last):
  File 
"/usr/lib/python3/dist-packages/selenium/webdriver/common/driver_finder.py", 
line 38, in get_path
path = SeleniumManager().driver_location(options) if path is None 
else path

   ^^
  File 
"/usr/lib/python3/dist-packages/selenium/webdriver/common/selenium_manager.py", 
line 81, in driver_location

args = [str(self.get_binary()), "--browser", browser]
^
  File 
"/usr/lib/python3/dist-packages/selenium/webdriver/common/selenium_manager.py", 
line 65, in get_binary
raise WebDriverException(f"Unable to obtain working Selenium 
Manager binary; {path}")
selenium.common.exceptions.WebDriverException: Message: Unable to obtain 
working Selenium Manager binary; 
/usr/lib/python3/dist-packages/selenium/webdriver/common/linux/selenium-manager



The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "", line 1, in 
  File 
"/usr/lib/python3/dist-packages/selenium/webdriver/firefox/webdriver.py", 
line 59, in __init__

self.service.path = DriverFinder.get_path(self.service, options)

  File 
"/usr/lib/python3/dist-packages/selenium/webdriver/common/driver_finder.py", 
line 41, in get_path

raise NoSuchDriverException(msg) from err
selenium.common.exceptions.NoSuchDriverException: Message: Unable to 
obtain driver for firefox using Selenium Manager.; For documentation on 
this error, please visit: 
https://www.selenium.dev/documentation/webdriver/troubleshooting/errors/driver_location

```

And on bookworm, it's not much better:

```
Traceback (most recent call last):
  File "", line 1, in 
  File 
"/usr/lib/python3/dist-packages/selenium/webdriver/firefox/webdriver.py", 
line 199, in __init__
super().__init__(command_executor=executor, options=options, 
keep_alive=True)
  File 
"/usr/lib/python3/dist-packages/selenium/webdriver/remote/webdriver.py", 
line 286, in __init__

self.start_session(capabilities, browser_profile)
  File 
"/usr/lib/python3/dist-packages/selenium/webdriver/remote/webdriver.py", 
line 378, in start_session

response = self.execute(Command.NEW_SESSION, parameters)
   ^
  File 
"/usr/lib/python3/dist-packages/selenium/webdriver/remote/webdriver.py", 
line 440, in execute

self.error_handler.check_response(response)
  File 
"/usr/lib/python3/dist-packages/selenium/webdriver/remote/errorhandler.py", 
line 245, in check_response

raise exception_class(message, screen, stacktrace)

Bug#1041351: app crashes immediately

2023-09-23 Thread VA

Le 30/07/2023 à 03:00, Patrick Franz a écrit :

Hi,

On Mon, 17 Jul 2023 22:07:49 +0200 VA  wrote:

Package: convertall
Version: 0.8.0-2
Severity: serious

[...]

I'm downgrading this as I cannot reproduce your error. I tried on 3
different systems, but the app starts as usual every time.

Unfortunately, you did not provide any information about the system
you're running. Without it, we cannot investigate this any further.




Actually, the app crashes with env var PYTHONSAFEPATH=y which is a best 
security practice.
The problem is that convertall app is not a cleanly-designed python app 
with a dedicated package (even just in local, no need to be on PyPI), so 
the python interpreter can't find the rest of convertall sources.




Bug#1052497: manual page contains errors and is obsolete

2023-09-23 Thread VA

Package: topydo
Version: 0.14-5.2

An example of error: topydo manual page mentions "|" to do a logical OR 
between terms, but it's wrong. Not only this syntax does not work, but 
the feature does not even exist! See 



An example of "obsolete": manual page does not mention the "sort" subcommand

Maybe the manual page could be generated by concatening those outputs:

- `topydo help`
- `topydo help add`
- `topydo help do`
- `topydo help ls`
- etc.

plus some hardcoded standard sections NAME, SYNOPSIS, CONFIGURATION, SEE 
ALSO, etc.




Bug#1052192: package for qt6?

2023-09-18 Thread VA

Package: python3-poppler-qt5
Version: 21.3.0-2
Severity: wishlist

Please provide python3-poppler-qt6. According to 
https://endoflife.date/qt, Qt 5.15 has no support since May 2023, only 
Qt 6 versions are maintained. So this is probably the same for libs like 
poppler-qt which depend on Qt.
It seems Debian already has the package "libpoppler-qt6-3" but not yet 
the corresponding python package.




Bug#1050078: nano should provide "editor"

2023-08-19 Thread VA

Package: nano
Version: 7.2-1

nano package does not provide virtual package "editor", though it should.



Bug#1041351: app crashes immediately

2023-07-17 Thread VA

Package: convertall
Version: 0.8.0-2
Severity: serious

When running it:

% LANG=C convertall
Traceback (most recent call last):
  File "/usr/share/convertall/convertall.py", line 143, in 
main()
  File "/usr/share/convertall/convertall.py", line 133, in main
import convertdlg
ModuleNotFoundError: No module named 'convertdlg'
% LANG=C convertall -i
Traceback (most recent call last):
  File "/usr/share/convertall/convertall.py", line 143, in 
main()
  File "/usr/share/convertall/convertall.py", line 124, in main
import cmdline
ModuleNotFoundError: No module named 'cmdline'

If not using LANG=C, there are additional errors regarding missing 
translations.




Bug#1033438: error in ascii(7)

2023-03-24 Thread VA

Package: manpages-fr
Version: 4.18.0-1

ascii(7) contains an error for character 2A (in hex), it indicates "–" 
(U+2013) instead of "+" (U+002A).
The error can be seen here too: 
https://manpages.debian.org/unstable/manpages-fr/ascii.7.fr.html




Bug#1032365: missing manual page

2023-03-04 Thread VA

Package: python3-hatchling
Version: 1.12.2-1

hatchling has no manual page



Bug#827292: news?

2023-01-28 Thread VA
So it's been almost 7 years now that the file still has not gained that 
tiny executable bit.

What's the reason for not doing it?



Bug#1025493: firefox crashes instantly at start

2022-12-06 Thread VA

Le 06/12/2022 à 19:37, Felix Zielcke a écrit :

I have exactly the same problem since Mesa 22.3.0 was uploaded to
unstable.
Downgrading all src:mesa packages to version 22.2.4 from testing fixes
this for me.
I've got a Nvidia graphic card and use the Nvidia driver packages from
Debian. It doestn't matter at all if nvidia-vaapi-driver is installed
or removed/purged.


Seems mesa 22.3.0-2 fixed the problem for me. What about you?
Maybe it was https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025312



Bug#1025493: firefox crashes instantly at start

2022-12-05 Thread VA

Package: firefox
Version: 107.0.1-1
Severity: important

It's not a broken profile, even when running "firefox --ProfileManager" 
or "firefox --safe-mode":


[GFX1-]: glxtest: VA-API test failed: failed to initialise VAAPI connection.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ExceptionHandler::GenerateDump cloned child 231737
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
ExceptionHandler::WaitForContinueSignal waiting for continue signal...



Bug#1017524: status?

2022-11-23 Thread VA
Is there a pending fix? It may be related to multiple broken jekyll 
plugins in debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024177




Bug#1024177: cannot use plugin due to incompatibility?

2022-11-15 Thread VA

Package: ruby-jekyll-feed
Version: 0.15.1-2

I'm using jekyll with those plugins in `_config.yml`:

plugins:
  - jekyll-sitemap
  - jekyll-feed

I get this error:

  Dependency Error: Yikes! It looks like you don't have jekyll-feed or 
one of its dependencies installed. In order to use Jekyll as currently 
configured, you'll need to install this gem. The full error message from 
Ruby is: 'Unable to activate jekyll-3.9.0, because liquid-5.4.0 
conflicts with liquid (~> 4.0), mercenary-0.4.0 conflicts with mercenary 
(~> 0.3.3)' If you run into trouble, you can find helpful resources at 
https://jekyllrb.com/help/!

jekyll 3.9.0 | Error:  jekyll-feed
/usr/lib/ruby/vendor_ruby/jekyll/external.rb:68:in `rescue in block in 
require_with_graceful_fail': jekyll-feed 
(Jekyll::Errors::MissingDependencyException)
	from /usr/lib/ruby/vendor_ruby/jekyll/external.rb:56:in `block in 
require_with_graceful_fail'

from /usr/lib/ruby/vendor_ruby/jekyll/external.rb:55:in `each'
[snip backtrace]
/usr/lib/ruby/vendor_ruby/rubygems/specification.rb:2248:in 
`raise_if_conflicts': Unable to activate jekyll-3.9.0, because 
liquid-5.4.0 conflicts with liquid (~> 4.0), mercenary-0.4.0 conflicts 
with mercenary (~> 0.3.3) (Gem::ConflictError)

[snip backtrace]
/usr/lib/ruby/vendor_ruby/rubygems/specification.rb:2248:in 
`raise_if_conflicts': Unable to activate jekyll-3.9.0, because 
liquid-5.4.0 conflicts with liquid (~> 4.0), mercenary-0.4.0 conflicts 
with mercenary (~> 0.3.3) (Gem::ConflictError)

[snip backtrace]
:85:in 
`require': cannot load such file -- jekyll-feed (LoadError)

Did you mean?  jekyll
[snip backtrace]

This is what's installed:

jekyll   3.9.0+dfsg-5
ruby-jekyll-feed 0.15.1-2
ruby-jekyll-sass-converter   1.5.2-3
ruby-jekyll-sitemap  1.4.0-2
ruby-jekyll-watch2.2.1-1
ruby-liquid  5.4.0-2
ruby-mercenary   0.4.0-1



Bug#1021563: also exclude fuse.gocryptfs from index

2022-10-10 Thread VA

Package: plocate
Version: 1.1.16-1

In /etc/updatedb.conf 's PRUNEFS option, just like "fuse.cryfs" and 
"fuse.encfs" are present, PRUNEFS should also contain "fuse.gocryptfs" 
to prevent indexing (and leaking!) files from an encrypted filesystem,




Bug#1004027: Acknowledgement (aunpack should support unrar command)

2022-09-08 Thread VA
Same thing about .7z archives: I have `7zip` and `p7zip` packages 
installed, which are fine for unpacking .7z archives, but aunpack 
refuses to unpack them because none of these 2 packages ship a 7z command.
They do ship 7zr and p7zip commands though, which are suitable for 
extracting .7z archives.




Bug#1017787: ikhal crashes regularly when creating events

2022-08-20 Thread VA

Package: khal
Version: 1:0.10.4~ds-3

ikhal crashes regularly when creating events, with this backtrace:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/khal/ui/__init__.py", line 1358, 
in start_pane

loop.run()
  File "/usr/lib/python3/dist-packages/urwid/main_loop.py", line 287, 
in run

self._run()
  File "/usr/lib/python3/dist-packages/urwid/main_loop.py", line 385, 
in _run

self.event_loop.run()
  File "/usr/lib/python3/dist-packages/urwid/main_loop.py", line 790, 
in run

self._loop()
  File "/usr/lib/python3/dist-packages/urwid/main_loop.py", line 827, 
in _loop

self._watch_files[fd]()
  File "/usr/lib/python3/dist-packages/urwid/raw_display.py", line 416, 
in 

wrapper = lambda: self.parse_input(
  File "/usr/lib/python3/dist-packages/urwid/raw_display.py", line 515, 
in parse_input

callback(processed, processed_codes)
  File "/usr/lib/python3/dist-packages/urwid/main_loop.py", line 412, 
in _update

self.process_input(keys)
  File "/usr/lib/python3/dist-packages/urwid/main_loop.py", line 513, 
in process_input

k = self._topmost_widget.keypress(self.screen_size, k)
  File "/usr/lib/python3/dist-packages/urwid/wimp.py", line 651, in 
keypress

return self._current_widget.keypress(size, key)
  File "/usr/lib/python3/dist-packages/urwid/container.py", line 1135, 
in keypress

return self.body.keypress( (maxcol, remaining), key )
  File "/usr/lib/python3/dist-packages/urwid/container.py", line 2316, 
in keypress

key = w.keypress((mc,) + size[1:], key)
  File "/usr/lib/python3/dist-packages/urwid/container.py", line 1626, 
in keypress

key = self.focus.keypress(tsize, key)
  File "/usr/lib/python3/dist-packages/urwid/container.py", line 2316, 
in keypress

key = w.keypress((mc,) + size[1:], key)
  File "/usr/lib/python3/dist-packages/khal/ui/editor.py", line 530, in 
keypress

return super().keypress(size, key)
  File "/usr/lib/python3/dist-packages/khal/ui/widgets.py", line 376, 
in keypress

key = super().keypress(size, key)
  File "/usr/lib/python3/dist-packages/urwid/listbox.py", line 968, in 
keypress

key = focus_widget.keypress((maxcol,),key)
  File "/usr/lib/python3/dist-packages/urwid/container.py", line 2316, 
in keypress

key = w.keypress((mc,) + size[1:], key)
  File "/usr/lib/python3/dist-packages/urwid/wimp.py", line 543, in 
keypress

self._emit('click')
  File "/usr/lib/python3/dist-packages/urwid/widget.py", line 461, in _emit
signals.emit_signal(self, name, self, *args)
  File "/usr/lib/python3/dist-packages/urwid/signals.py", line 265, in emit
result |= self._call_callback(callback, user_arg, user_args, args)
  File "/usr/lib/python3/dist-packages/urwid/signals.py", line 295, in 
_call_callback

return bool(callback(*args_to_pass))
  File "/usr/lib/python3/dist-packages/khal/ui/editor.py", line 503, in 
save

self.collection.new(self.event)
  File "/usr/lib/python3/dist-packages/khal/khalendar/khalendar.py", 
line 208, in new

event.href, event.etag = self._storages[calendar].upload(event)
  File "/usr/lib/python3/dist-packages/khal/khalendar/vdir.py", line 
212, in upload

if not isinstance(item.raw, str):
  File "/usr/lib/python3/dist-packages/khal/khalendar/event.py", line 
382, in raw

timezone = create_timezone(tzinfo, self.start)
  File "/usr/lib/python3/dist-packages/khal/khalendar/event.py", line 
858, in create_timezone

for one, two in iter(tz._tzinfos.items())
AttributeError: '_PytzShimTimezone' object has no attribute '_tzinfos'


---

Also, there are a lot of warnings (not crashes though) when doing almost 
anything in ikhal or simply running khal list, like this:


/usr/lib/python3/dist-packages/khal/khalendar/event.py:543: 
PytzUsageWarning: The localize method is no longer necessary, as this 
time zone supports the fold attribute (PEP 495). For more details on 
migrating to a PEP 495-compliant implementation, see 
https://pytz-deprecation-shim.readthedocs.io/en/latest/migration.html

  end_local_datetime = self._locale['local_timezone'].localize(
/usr/lib/python3/dist-packages/khal/khalendar/event.py:546: 
PytzUsageWarning: The localize method is no longer necessary, as this 
time zone supports the fold attribute (PEP 495). For more details on 
migrating to a PEP 495-compliant implementation, see 
https://pytz-deprecation-shim.readthedocs.io/en/latest/migration.html

  day_start = self._locale['local_timezone'].localize(
/usr/lib/python3/dist-packages/khal/khalendar/event.py:549: 
PytzUsageWarning: The localize method is no longer necessary, as this 
time zone supports the fold attribute (PEP 495). For more details on 
migrating to a PEP 495-compliant implementation, see 
https://pytz-deprecation-shim.readthedocs.io/en/latest/migration.html




Bug#1016810: i386 package should ship x86_64 binfmt

2022-08-18 Thread VA

Le 11/08/2022 à 10:56, Michael Tokarev a écrit :

So overall, the issue is very minor (as in, with very limited use case),
and I think implementing it properly (with runtime detection) isn't worth
the effort.


Maybe create a separate package shipping amd64 binfmt info for i386-only 
installs? Something like qemu-user-binfmt-amd64, where the description 
makes it clear (or the install script) it shouldn't be installed on 
amd64-capable systems.



Marking it as wontfix for now.

Not having them prevents from using mmdebstrap to install an amd64 
system from a i386 system:


I suggest you to use x64 kernel there.  Again, it is a very specific,
very limited use case.


Precisely, and this is exactly what I was trying to do with 
*debootstrap! But I couldn't because the binfmt are not shipped.




Bug#1017346: crashes immediately when using webengine view

2022-08-14 Thread VA

Le 14/08/2022 à 16:12, Dmitry Shachnev a écrit :

Please install libqt6webenginecore6-bin package.


Indeed installing it fixes the problem.

However, as a more general note, could simple python exceptions like 
this not quit the whole app? If there was unsaved text, and the user 
tries to enable such an innocent-looking option, then the app may fail 
in enabling it, sure, it happens, but it's not critical enough to quit 
the app immediately, and to lose all unsaved user data.
At the very least print the exception on stderr but do not quit at all. 
At best, display an error message in a dialogbox.




Bug#1017346: crashes immediately when using webengine view

2022-08-14 Thread VA

Package: retext
Version: 8.0.0-1

When selecting the "use webengine chromium view" from menu, retext 
immediately crashes:


Could not find QtWebEngineProcess
Process Process-1:
Traceback (most recent call last):
  File "/usr/lib/python3.10/multiprocessing/process.py", line 314, in 
_bootstrap

self.run()
  File "/usr/lib/python3.10/multiprocessing/process.py", line 108, in run
self._target(*self._args, **self._kwargs)
  File "/usr/share/retext/ReText/converterprocess.py", line 72, in 
_converter_process_func

job = receiveObject(conn_child)
  File "/usr/share/retext/ReText/converterprocess.py", line 41, in 
receiveObject

sizeBuf = recvall(sock, 4)
  File "/usr/share/retext/ReText/converterprocess.py", line 34, in recvall
raise EOFError('Received 0 bytes from socket while more bytes were 
expected. Did the sender process exit unexpectedly?')
EOFError: Received 0 bytes from socket while more bytes were expected. 
Did the sender process exit unexpectedly?

zsh: IOT instruction  retext



Bug#1016810: i386 package should ship x86_64 binfmt

2022-08-07 Thread VA

Package: qemu-user-binfmt
Version: 1:7.0+dfsg-7

Architectures that are not i386 or amd64 ship files like
/usr/lib/binfmt.d/qemu-x86_64.conf and /usr/lib/binfmt.d/qemu-i386.conf

However, i386 and amd64 flavours of the package ship neither.
The i386 flavour should ship x86_64 related files, and conversely.

Not having them prevents from using mmdebstrap to install an amd64 
system from a i386 system:


I: automatically chosen mode: root
update-binfmts: warning: qemu-x86_64 not in database of installed binary 
formats.

update-binfmts: exiting due to previous errors
W: qemu-x86_64 is not a supported binfmt name
E: amd64 can neither be executed natively nor via qemu user emulation 
with binfmt_misc




Bug#1016805: retext crashes at start

2022-08-07 Thread VA

Package: retext
Version: 8.0.0-1
Severity: grave
Justification: renders package unusable

When starting retext:

qt.qpa.plugin: Could not find the Qt platform plugin "xcb" in ""
This application failed to start because no Qt platform plugin could be 
initialized. Reinstalling the application may fix this problem.


zsh: IOT instruction  retext

It seems qt6-qpa-plugins is only a "Recommends" dependency but retext 
does not work **at all** without it, so it should be a plain "Depends".




Bug#1014022: kalendar segfaults immediately on start

2022-06-28 Thread VA

Package: kalendar
Version: 22.04.2-3

This is my first run of kalendar after a fresh install.

```
user@host ~ % kalendar
QML debugging is enabled. Only use this in a safe environment.
Connecting to deprecated signal 
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)

org.kde.pim.akonadiserver: Starting up the Akonadi Server...
org.kde.pim.akonadiserver: database server stopped unexpectedly
org.kde.pim.akonadiserver: Database process exited unexpectedly during 
initial connection!

org.kde.pim.akonadiserver: executable: "/usr/sbin/mysqld"
org.kde.pim.akonadiserver: arguments: 
("--defaults-file=/home-x/.local/share/akonadi/mysql.conf", 
"--datadir=/home-x/.local/share/akonadi/db_data/", 
"--socket=/run/user/1000/akonadi/mysql.socket", 
"--pid-file=/run/user/1000/akonadi/mysql.pid")

org.kde.pim.akonadiserver: stdout: ""
org.kde.pim.akonadiserver: stderr: "2022-06-28 19:05:37 0 [Note] 
/usr/sbin/mysqld (server 10.6.8-MariaDB-1) starting as process 112145 ...\n"

org.kde.pim.akonadiserver: exit code: 1
org.kde.pim.akonadiserver: process error: "Unknown error"
org.kde.pim.akonadiserver: Failed to remove runtime connection config file
org.kde.pim.akonadiserver: Shutting down AkonadiServer...
org.kde.pim.akonadicontrol: Application '/usr/bin/akonadiserver' exited 
normally...

org.kde.pim.akonadicore: Could not start/stop Akonadi!
Connecting to deprecated signal 
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)

org.kde.pim.akonadiserver: Starting up the Akonadi Server...
QQmlApplicationEngine failed to load component
qrc:/main.qml:7:1: module "org.kde.kirigami" is not installed
zsh: segmentation fault  kalendar
user@host 139? ~ % org.kde.pim.akonadiserver: database server stopped 
unexpectedly
org.kde.pim.akonadiserver: Database process exited unexpectedly during 
initial connection!

org.kde.pim.akonadiserver: executable: "/usr/sbin/mysqld"
org.kde.pim.akonadiserver: arguments: 
("--defaults-file=/home-x/.local/share/akonadi/mysql.conf", 
"--datadir=/home-x/.local/share/akonadi/db_data/", 
"--socket=/run/user/1000/akonadi/mysql.socket", 
"--pid-file=/run/user/1000/akonadi/mysql.pid")

org.kde.pim.akonadiserver: stdout: ""
org.kde.pim.akonadiserver: stderr: "2022-06-28 19:05:43 0 [Note] 
/usr/sbin/mysqld (server 10.6.8-MariaDB-1) starting as process 112171 ...\n"

org.kde.pim.akonadiserver: exit code: 1
org.kde.pim.akonadiserver: process error: "Unknown error"
org.kde.pim.akonadiserver: Shutting down AkonadiServer...
org.kde.pim.akonadicontrol: Application '/usr/bin/akonadiserver' exited 
normally...

```

Then I installed akonadi sqlite backend and uninstalled default mysql 
backend, thinking it could help. But it wasn't better, it still crashed 
the same. Worse, it seemed to still look for mysql stuff.




Bug#1010269: crashes immediately at start

2022-04-27 Thread VA

Package: wine-development
Version: 6.23~repack-1

Whenever I run any wine-development command, for example 
`wine-development winecfg`, even in a new, empty, WINEPREFIX, I get a 
crash immediately:


% wine-development winecfg
err:environ:read_nls_file failed to load 10/0
zsh: segmentation fault  wine-development winecfg

with more verbose logging:

% WINEDEBUG=+all wine-development winecfg
err:environ:read_nls_file failed to load 10/0
trace:virtual:NtAllocateVirtualMemory 0x 0x7ffe 1000 
3000 0002

trace:virtual:dump_view View: 0x7ffe - 0x7ffe0fff (valloc)
trace:virtual:dump_view   0x7ffe - 0x7ffe0fff c-r--
trace:virtual:NtAllocateVirtualMemory 0x (nil) 0020 102000 
0004

trace:virtual:map_view got mem in reserved area 0x3fe0-0x4000
trace:virtual:dump_view View: 0x3fe0 - 0x3fff (valloc)
trace:virtual:dump_view   0x3fe0 - 0x3fff --rw-
trace:virtual:NtAllocateVirtualMemory 0x 0x3ffe 0002 
1000 0004

trace:virtual:dump_view View: 0x3fe0 - 0x3fff (valloc)
trace:virtual:dump_view   0x3fe0 - 0x3ffd --rw-
trace:virtual:dump_view   0x3ffe - 0x3fff c-rw-
sock_init: shutdown() causes EOF
wineserver: starting (pid=1315093)
0020: *fd* 02e1 -> 23
0024: *fd* 7 <- 23
0024: *fd* 9 <- 24
0024: init_first_thread( unix_pid=1315091, unix_tid=1315091, 
debug_level=1, reply_fd=7, wait_fd=9 )
0024: init_first_thread() = 0 { pid=0020, tid=0024, 
server_start=1d85a3ae26eac84 (-0.630), session_id=0001, 
info_size=0, machines={8664,014c} }
0024: open_mapping( access=000f001f, attributes=, rootdir=, 
name=L"\\KernelObjects\\__wine_user_shared_data" )

0024: open_mapping() = 0 { handle=0004 }
0024: get_handle_fd( handle=0004 )
0024: *fd* 0004 -> 20
0024: get_handle_fd() = 0 { type=1, cacheable=1, access=000f001f, 
options=0020 }

0024: close_handle( handle=0004 )
0024: close_handle() = 0
3189712.026:0020:0024:trace:ntdll:init_cpu_info <- CPU arch 0, level 23, 
rev 28928, features 0xebf9bfff
3189712.026:0020:0024:trace:ntdll:NtQueryInformationToken 
(0xfffa,1,0xffc6efd4,76,0xffc6efb0)

0024: get_token_sid( handle=fffa, which_sid=0001 )
0024: get_token_sid() = 0 { sid_len=28, sid={S-1-5-21-0-0-0-1000} }
3189712.027:0020:0024:trace:reg:NtCreateKey 
((nil),L"\\Registry\\User\\S-1-5-21-0-0-0-1000\\Software\\Wine",,0,f003f,0xffc6f360)
0024: create_key( access=000f003f, options=, 
objattr={rootdir=,attributes=0040,sd={},name=L"\\Registry\\User\\S-1-5-21-0-0-0-1000\\Software\\Wine"}, 
class=L"" )

0024: create_key() = OBJECT_NAME_NOT_FOUND { hkey=, created=0 }
3189712.027:0020:0024:trace:reg:NtCreateKey <- (nil)
3189712.027:0020:0024:trace:file:find_drive_rootA "/tmp/plop-262610" -> 
drive Z:, root="/", name="/tmp/plop-262610"

0024: *killed* exit_code=0
zsh: segmentation fault  WINEDEBUG=+all wine-development winecfg



Bug#1007724: no locking at all

2022-03-22 Thread VA

severity 1007724 serious
thanks

Given that due to this bug, xscreensaver does not lock at all the screen 
or even run, then the package does not work at all in the current state, 
and worse, it prevents locking, its main security feature.




Bug#1006956: tt-rss spits a lot of php warnings

2022-03-08 Thread VA

Package: tt-rss
Version: 21~git20210204.b4cbc79+dfsg-1

tt-rss spits a lot of logs. In 8 hours it did that:

% journalctl -S today | grep -c tt-rss
36715

Logs are all php warnings like this:

mars 09 07:56:17 xxx php[478978]: [tt-rss] E_WARNING (2) 
(classes/urlhelper.php:99) Undefined array key "port"
mars 09 07:56:17 xxx php[478978]: [tt-rss] E_WARNING (2) 
(classes/db/prefs.php:63) Undefined global variable $_SESSION
mars 09 07:56:17 xxx php[478978]: [tt-rss] E_WARNING (2) 
(classes/db/prefs.php:63) Trying to access array offset on value of type 
null
mars 09 07:56:17 xxx php[478978]: [tt-rss] E_WARNING (2) 
(classes/db/prefs.php:86) Undefined global variable $_SESSION
mars 09 07:56:17 xxx php[478978]: [tt-rss] E_WARNING (2) 
(classes/db/prefs.php:86) Trying to access array offset on value of type 
null
mars 09 07:56:17 xxx php[478978]: [tt-rss] E_WARNING (2) 
(classes/db/prefs.php:63) Undefined global variable $_SESSION
mars 09 07:56:17 xxx php[478978]: [tt-rss] E_WARNING (2) 
(classes/db/prefs.php:63) Trying to access array offset on value of type 
null
mars 09 07:56:17 xxx php[478978]: [tt-rss] E_WARNING (2) 
(classes/db/prefs.php:86) Undefined global variable $_SESSION
mars 09 07:56:17 xxx php[478978]: [tt-rss] E_WARNING (2) 
(classes/db/prefs.php:86) Trying to access array offset on value of type 
null
mars 09 07:56:17 xxx php[478978]: [tt-rss] E_DEPRECATED (8192) 
(classes/rssutils.php:703) strip_tags(): Passing null to parameter #1 
($string) of type string is deprecated
mars 09 07:56:17 xxx update.php[478973]: PHP Warning:  Array to string 
conversion in /usr/share/tt-rss/www/include/errorhandler.php on line 24
mars 09 07:56:17 xxx update.php[478973]: PHP Warning:  Array to string 
conversion in /usr/share/tt-rss/www/include/errorhandler.php on line 24
mars 09 07:56:17 xxx php[478973]: [tt-rss] E_WARNING (2) 
(classes/userhelper.php:78) Undefined global variable $_SESSION
mars 09 07:56:17 xxx php[478973]: [tt-rss] E_WARNING (2) 
(classes/userhelper.php:78) Trying to access array offset on value of 
type null
mars 09 07:56:17 xxx update.php[478973]: PHP Warning:  Array to string 
conversion in /usr/share/tt-rss/www/include/errorhandler.php on line 24
mars 09 07:56:17 xxx update.php[478973]: PHP Warning:  Array to string 
conversion in /usr/share/tt-rss/www/include/errorhandler.php on line 24
mars 09 07:56:17 xxx update.php[478973]: PHP Warning:  Array to string 
conversion in /usr/share/tt-rss/www/include/errorhandler.php on line 24
mars 09 07:56:17 xxx update.php[478973]: PHP Warning:  Array to string 
conversion in /usr/share/tt-rss/www/include/errorhandler.php on line 24
mars 09 07:56:17 xxx php[478973]: [tt-rss] E_WARNING (2) 
(classes/db/prefs.php:11) Undefined global variable $_SESSION
mars 09 07:56:17 xxx php[478973]: [tt-rss] E_WARNING (2) 
(classes/db/prefs.php:11) Trying to access array offset on value of type 
null
mars 09 07:56:17 xxx php[478973]: [tt-rss] E_WARNING (2) 
(classes/db/prefs.php:63) Undefined global variable $_SESSION
mars 09 07:56:17 xxx php[478973]: [tt-rss] E_WARNING (2) 
(classes/db/prefs.php:63) Trying to access array offset on value of type 
null
mars 09 07:56:17 xxx update.php[478973]: PHP Warning:  Array to string 
conversion in /usr/share/tt-rss/www/include/errorhandler.php on line 24
mars 09 07:56:17 xxx update.php[478973]: PHP Warning:  Array to string 
conversion in /usr/share/tt-rss/www/include/errorhandler.php on line 24
mars 09 07:56:17 xxx php[478973]: [tt-rss] E_WARNING (2) 
(classes/db/prefs.php:86) Undefined global variable $_SESSION
mars 09 07:56:17 xxx php[478973]: [tt-rss] E_WARNING (2) 
(classes/db/prefs.php:86) Trying to access array offset on value of type 
null
mars 09 07:56:17 xxx update.php[478973]: PHP Warning:  Array to string 
conversion in /usr/share/tt-rss/www/include/errorhandler.php on line 24
mars 09 07:56:17 xxx update.php[478973]: PHP Warning:  Array to string 
conversion in /usr/share/tt-rss/www/include/errorhandler.php on line 24
mars 09 07:56:17 xxx php[478973]: [tt-rss] E_WARNING (2) 
(classes/pluginhost.php:143) Undefined array key 2
mars 09 07:56:17 xxx update.php[478973]: PHP Warning:  Array to string 
conversion in /usr/share/tt-rss/www/include/errorhandler.php on line 24
mars 09 07:56:17 xxx update.php[478973]: PHP Warning:  Array to string 
conversion in /usr/share/tt-rss/www/include/errorhandler.php on line 24
mars 09 07:56:17 xxx update.php[478973]: PHP Warning:  Array to string 
conversion in /usr/share/tt-rss/www/include/errorhandler.php on line 24
mars 09 07:56:17 xxx update.php[478973]: PHP Warning:  Array to string 
conversion in /usr/share/tt-rss/www/include/errorhandler.php on line 24
mars 09 07:56:17 xxx update.php[478973]: PHP Warning:  Array to string 
conversion in /usr/share/tt-rss/www/include/errorhandler.php on line 24
mars 09 07:56:17 xxx update.php[478973]: PHP Warning:  Array to string 
conversion in /usr/share/tt-rss/www/include/errorhandler.php on line 24
mars 09 07:56:17 xxx update.php[478973]: PHP 

Bug#1005350: big icons despite compact mode

2022-02-11 Thread VA

Version: 2.6.6+dfsg.1-1
Package: keepassxc

In the app, icons are way too big, bigger than they were before, even 
when "compact mode" is enabled (actually this option doesn't seem to 
work at all).
See attached screenshot of how it looks now. Previously, the icon size 
used to be more like this: 
https://keepassxc.org/images/screenshots/database_view.png

Bug#1004984: incorrect context menu shown

2022-02-04 Thread VA

Package: xfce4-panel
Version: 4.16.3-1

I'm comparing the situation between Debian stable and Debian unstable. 
In both cases, XFCE is used, with xfce-panel and a tray area in the 
panel, plus VLC as an example. VLC must be running, so it has an icon 
sitting in the xfce-panel tray area.


On Debian stable, right-clicking on the VLC icon from tray pops VLC's 
context menu, as expected.


On Debian unstable though, right-clicking on the VLC icon from tray pops 
xfce-panel's context menu (more specifically, the one from the tray 
applet), which is incorrect. Still on unstable, right-clicking on 
Pidgin's tray icon pops Pidgin's context menu, not xfce-panel's, which 
is correct.
In fact, right-clicking on any Qt app's tray icon will show xfce-panel's 
context menu on unstable.

This might be a regression in Qt or in xfce's systray. I'm unsure.



Bug#1004027: aunpack should support unrar command

2022-01-19 Thread VA

Package: atool
Version: 0.39.0-11

When running aunpack on .rar files, I would expect it to run unrar 
command, but it doesn't…
So whether I installed `unrar-free` or `unrar` package, it's not used. 
It only supports rar files if the `rar` package is installed.


See log:

Can't exec "rar": No such file or directory at /usr/bin/aunpack line 1868.
rar: cannot execute - No such file or directory
aunpack: rar ...: non-zero return-code



Bug#1003881: js error on home page

2022-01-17 Thread VA

Package: jupyter-notebook
Version: 6.4.5-3
Severity: serious

When starting `jupyter-notebook`, a browser is spawned to land (after 
some redirects) on http://localhost:/tree but the page stays blank. 
The browser console reports some javascript error:


Uncaught ReferenceError: exports is not defined
 marked.js:14
marked.js:14
 marked.js:14

So jupyter is basically unusable because nothing can be accessed.



Bug#1001966: missing a dependency and unclear description

2021-12-19 Thread VA

Package: giara
Version: 0.3-3

Running after install:

Traceback (most recent call last):
  File "/usr/bin/giara", line 69, in 
gi.require_version('Handy', '1')
  File "/usr/lib/python3/dist-packages/gi/__init__.py", line 126, in 
require_version

raise ValueError('Namespace %s not available' % namespace)
ValueError: Namespace Handy not available

Seems it should add libhandy to package dependencies.

Also, the description should make it clear that this app requires to 
log-in and thus an account on reddit. Anonymous browsing is not possible 
in giara.




Bug#1001937: lots lots lots of crashes

2021-12-19 Thread VA

Package: inkscape
Version: 1.1.1-2+b1

The new inkscape version crashes very very often (every few minutes). 
Here's a simple way to make it crash:

- load the attached file
- select "wall" object in layers/object pane
- go to edit menu > copy
-> inkscape crashes...

Bug#1000263: package broken after php8 upgrade

2021-11-20 Thread VA

Package: tt-rss
Version: 21~git20210204.b4cbc79+dfsg-1
Severity: serious

Since upgrade from php packages 7.4 to 8.1, tt-rss is unusable. Logs 
contain several occurrences of:


[Sat Nov 20 17:11:06.950555 2021] [php:error] [pid 2895803] [client 
127.0.0.1:40988] PHP Fatal error:  Uncaught ValueError: 
mb_convert_encoding(): Argument #2 ($to_encoding) must be a valid 
encoding, "" given in 
/usr/share/php/php-php-gettext/gettext.inc:181\nStack trace:\n#0 
/usr/share/php/php-php-gettext/gettext.inc(181): 
mb_convert_encoding()\n#1 
/usr/share/php/php-php-gettext/gettext.inc(278): _encode()\n#2 
/usr/share/php/php-php-gettext/gettext.inc(285): _gettext()\n#3 
/usr/share/tt-rss/www/include/functions.php(102): __()\n#4 
/usr/share/tt-rss/www/include/functions.php(141): get_translations()\n#5 
/usr/share/tt-rss/www/classes/userhelper.php(124): startup_gettext()\n#6 
/usr/share/tt-rss/www/index.php(31): UserHelper::login_sequence()\n#7 
{main}\n  thrown in /usr/share/php/php-php-gettext/gettext.inc on line 181


I'm not sure if the culprit is tt-rss or php-php-gettext package.

On https://www.php.net/manual/en/function.mb-convert-encoding.php:

8.0.0 	mb_convert_encoding() will now throw a ValueError when 
to_encoding is passed an invalid encoding.


So, it really is a misusage of mb_convert_encoding() either by tt-rss or 
by php-php-gettext.


php-php-gettext: 1.0.12-4



Bug#994845: project changed maintainer (not a fork)

2021-09-21 Thread VA

Package: python3-prettytable
Version: 0.7.2-5

Hi,

PrettyTable is now officially maintained by JazzBand at 
https://github.com/jazzband/prettytable, see the PyPI page: 
https://pypi.org/project/prettytable/

Version is now 2.2.0.



Bug#989501: new upstream releases since 2016

2021-06-05 Thread VA

Package: ffmpegthumbnailer
Version:  2.1.1-0.2

ffmpegthumbnailer 2.1.2 isn't in Debian, though it was released 5 years 
ago! And current ffmpegthumbnailer upstream version is 2.2.2, it would 
be good to update what's in Debian.




Bug#983639: docker-run manual page is not super readable

2021-02-27 Thread VA

Package: docker.io
Version: 20.10.3+dfsg1-2
Severity: minor

When viewing docker-run(1) manual page, the --network option description 
has a very large ASCII table that doesn't fit even in a wide terminal.


% man docker-run | grep -C5 -- --network | wc -L
warning: file '', around line 689:
  table wider than line width
290



Bug#981414: unreadable text with dark theme

2021-01-30 Thread VA

Package: lutris
Version: 0.5.8.3-1

I am using "darkcold" GTK theme from debian 
(https://packages.debian.org/buster/darkcold-gtk-theme), and Lutris' 
"manage runners" window is simply unreadable because of dark text on 
dark background. Is the text color hardcoded?




Bug#979973: no such file or directory when PAM accesses it

2021-01-12 Thread VA

Package: libpam-yubico
Version: 2.26-1.1
Severity: important

I use pam_yubico.so in /etc/pam.d/sshd

This is the error I now get:

xxx sshd[x]: PAM unable to dlopen(pam_yubico.so): 
/lib/x86_64-linux-gnu/security/pam_yubico.so: cannot open shared object 
file: No such file or directory

xxx sshd[x]: PAM adding faulty module: pam_yubico.so

It seems the file is in /lib/security/pam_yubico.so

This command seems to solve the problem but the package seems unusable 
as is:

ln -s /lib/security/pam_yubico.so /lib/x86_64-linux-gnu/security



Bug#963005: tig: new upstream release

2021-01-04 Thread VA

It's been quite some time 2.5.x has been released, any progress on it?



Bug#975731: package breaks with python3.9

2020-11-25 Thread VA

Package: python3-asttokens
Version: 2.0.3-1

Since Debian upgraded to Python 3.9, asttokens is mostly broken, for 
example this program fails:


from asttokens import ASTTokens

src = """
from x import Foo
class C:
def __init__(self):
self.foo = Foo(a=1)
"""

astt = ASTTokens(src, parse=True)

It works with:
- Python 3.8 and asttokens 2.0.3
- Python 3.9 and asttokens 2.0.4

But not with Python 3.9 and asttokens 2.0.3.
See https://github.com/gristlabs/asttokens/pull/56

Please update asttokens for Python 3.9.



Bug#975475: package takes much more space

2020-11-22 Thread VA

Package: dxvk-wine64-development
Version: 1.7.2+ds1-2

For some reason, the new version consumes much more storage space:

dxvk-wine32-development:i386+268 MB   1.7.2+ds1-11.7.2+ds1-2
dxvk-wine64-development +287 MB   1.7.2+ds1-11.7.2+ds1-2

while the changelog doesn't give a hint on what would take that much space



Bug#974847: Can't update initramfs-tools

2020-11-15 Thread VA

Package: initramfs-tools
Version: 0.139
Severity: important

initramfs-tools fails to update:

# LANG=C dpkg --configure --pending
Setting up initramfs-tools (0.139) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools (0.139) ...
update-initramfs: Generating /boot/initrd.img-5.7.0-2-amd64
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-2.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-1.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168fp-3.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168h-2.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168h-1.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-3.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-2.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-2.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-1.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-2.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-1.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8402-1.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-2.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-1.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8105e-1.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-3.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-2.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-1.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-2.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-1.fw for 
module r8169

E: /usr/share/initramfs-tools/hooks/mdadm failed with return 1.
update-initramfs: failed for /boot/initrd.img-5.7.0-2-amd64 with 1.
dpkg: error processing package initramfs-tools (--configure):
 installed initramfs-tools package post-installation script subprocess 
returned error exit status 1

Processing triggers for chkboot (1.3-6) ...
Errors were encountered while processing:
 initramfs-tools


mdadm version: 4.1-9



Bug#974177: Info received (serious)

2020-11-13 Thread VA

severity 974177 important
thanks

Oops, I thought the bug was on the pidgin package, sorry.



Bug#974177: serious

2020-11-13 Thread VA

severity -1 serious
thanks

The package is mostly unusable because of that bug.



Bug#971781: change default url

2020-10-07 Thread VA

Package: revolt
Version: 0.0+git20180813.6b10d57-2

When connecting to riot.im (the default) with Revolt, we are nagged by a 
periodic message demanding to switch to https://app.element.io

This should be the default instance URL instead of riot.im



Bug#971011: missing "webp" extension

2020-09-26 Thread VA

Package: mime-support
Version: 3.64

"webp" extension should have "image/webp" MIME type.
That's the type used by browser, for example 
https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types/Common_types




Bug#970643: "pytest" command is missing

2020-09-20 Thread VA

Package: python3-pytest
Version: 3.10.1-2

The standard runner "pytest" command present in most pytest files 
shebang isn't shipped by python3-pytest package.
It used to be shipped by python2 "python-pytest" package which is 
neither present in testing nor unstable, so there's room for shipping it 
in python3-pytest without a conflict, and it would prevent a scripts 
from failing to run with their shebang.




Bug#970251: mysqld manual page is worthless

2020-09-13 Thread VA

Package: mysql-server-core-8.0
Version: 8.0.21-1

mysqld(8) does not describe any of the options taken by mysqld command. 
It merely mentions:


   The mysqld program has many options that can be specified at 
startup. For a complete list of options, run this command:


   shell> mysqld --verbose --help

And indeed, the runtime help is more informative:

% mysqld --verbose --help | wc -l
2638

Why not simply take the --verbose --help message and use it inside the 
manpage? That would improve the situation without requiring much effort.




Bug#969985: new upstream releases

2020-09-09 Thread VA

Package: pipx
Version: 0.12.3.1-3

pipx is currently at version 0.15.5.1. But Debian is still at 0.12.3.1, 
which was released on February 2019, more than 20 releases away.




Bug#961717: The whole Firefox process crashes quite often

2020-05-28 Thread VA

Package: firefox
Version: 76.0.1-2

Before (<76), it used to crash some tabs when running low on memory.
Now (>=76), not only it takes more memory than before, but the whole 
process crashes, with all its tabs.




Bug#810890: caddy 2

2020-05-23 Thread VA
A few weeks ago, caddy 2.0.0 was released. Is there any progress on 
packaging?




Bug#960996: please provide a manual page

2020-05-19 Thread VA

Package: pipx
Version: 0.12.3.1-3

There is no manual page, which is sad, it could be generated from -h for 
example (and -h for each subcommand).


% man pipx
No manual entry for pipx
% pipx -h
usage: pipx [-h] [--version] 
{install,inject,upgrade,upgrade-all,uninstall,uninstall-all,reinstall-all,list,run,ensurepath} 
...


Install and execute binaries from Python packages.

Binaries can either be installed globally into isolated Virtual Environments
or run directly in an temporary Virtual Environment.

[...]



Bug#668021: any news?

2020-05-09 Thread VA

severity 668021 important
thanks

Hi,

Are there any news on this? The bug is still present as of today, and 
the proposed workaround does not work.




Bug#953880: problem confirmed

2020-03-14 Thread VA

severity 953880 grave
thanks

I have the same problem. GIMP is completely unusable as-is.



Bug#948178: python3-config forces no-pie

2020-01-04 Thread VA

Package: python3-dev
Version: 3.7.5-3

I'm trying to compile a C++ app which uses SWIG and embeds a Python 
interpreter. So it uses `python3-config --cflags` to compile and 
`python3-config --ldflags` to link. A few other libs like SDL are 
included with `pkg-config` too, but no weird gcc option is added.
Compiling cpp files runs fine, but when linking the final executable 
file, it fails badly:


```
g++ -I ../SWIG -I-I/usr/include/python3.7m 
-I/usr/include/python3.7m  -Wno-unused-result -Wsign-compare -g 
-fdebug-prefix-map=/build/python3.7-neQ7kp/python3.7-3.7.6=. 
-specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector -Wformat 
-Werror=format-security  -DNDEBUG -g -fwrapv -O3 -Wall 
-I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT  -I/usr/include/libdrm 
 -lglut -lGLU -lGL -L/usr/lib/x86_64-linux-gnu -lSDL 
-lSDL_image -lSDL_mixer -lSDL 
-L/usr/lib/python3.7/config-3.7m-x86_64-linux-gnu -L/usr/lib 
-lpython3.7m -lcrypt -lpthread -ldl  -lutil -lm  -o kiki
/usr/bin/ld: ../src/base/KikiAction.o: relocation R_X86_64_32S against 
symbol `_ZTV10KikiAction' can not be used when making a PIE object; 
recompile with -fPIE
/usr/bin/ld: ../src/base/KikiActionObject.o: relocation R_X86_64_32S 
against symbol `_ZTV16KikiActionObject' can not be used when making a 
PIE object; recompile with -fPIE


/usr/bin/ld: final link failed: nonrepresentable section on output
collect2: error: ld returned 1 exit status
```

And `python3-config --cflags` generates the following params:

```
-I/usr/include/python3.7m -I/usr/include/python3.7m  -Wno-unused-result 
-Wsign-compare -g 
-fdebug-prefix-map=/build/python3.7-neQ7kp/python3.7-3.7.6=. 
-specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector -Wformat 
-Werror=format-security  -DNDEBUG -g -fwrapv -O3 -Wall

```

Given the linking error, I believe the incorrect option is in 
`python3-config`'s output, and is 
`-specs=/usr/share/dpkg/no-pie-compile.specs`. If I strip it, linking 
works fine and so does the app.


By contrast, in Python 2, `python-config --cflags` does not have the 
offending param:


```
-I/usr/include/python2.7 -I/usr/include/x86_64-linux-gnu/python2.7 
-fno-strict-aliasing -Wdate-time -D_FORTIFY_SOURCE=2 -g 
-fdebug-prefix-map=/build/python2.7-07FOaN/python2.7-2.7.17=. 
-fstack-protector-strong -Wformat -Werror=format-security  -DNDEBUG -g 
-fwrapv -O2 -Wall -Wstrict-prototypes

```

Testing with a vanilla Python 3 installation from python.org, not from 
Debian packages, `python3-config --cflags` does NOT have the offending 
param either, so it is purely Debian-related.


Please remove the `-specs=/usr/share/dpkg/no-pie-compile.specs` option 
for Debian's `python3-config`.




Bug#947544: Please provide an egg-info

2019-12-27 Thread VA

Package: python3-pyqt5.qtwebengine
Version: 5.13.2-1

Hi,

TL;DR: Like https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890200, 
but for python3-pyqt5.qtwebengine instead of just python3-pyqt5.


Providing an egg-info or a dist-info correctly filled in a Python 
package is useful because if avoids installing with pip something 
already installed with the Debian packages.


These are packages I installed with the Debian packages 
(python3-requests and python3-pyqt5), and they are fine:


% pip install requests
Requirement already satisfied: requests in 
/usr/lib/python3/dist-packages (2.22.0)

% pip install PyQt5
Requirement already satisfied: PyQt5 in /usr/lib/python3/dist-packages 
(5.13.2)


I installed python3-pyqt5.qtwebengine with the Debian package too, but 
it doesn't work as expected:


% pip install PyQtWebEngine
Collecting PyQtWebEngine
  Downloading 
https://files.pythonhosted.org/packages/71/be/cd5243a456aae37788eebd8333d2326fd830de7ce1f1ac6618e966a66862/PyQtWebEngine-5.14.0-5.14.0-cp35.cp36.cp37.cp38-abi3-manylinux1_x86_64.whl 
(65.3MB)

[...snip...]

If python3-pyqt5.qtwebengine shipped the correct metadata, then pip 
would have told me PyQtWebEngine is already installed.


Thanks



Bug#941633: synfigstudio crashes on almost every operation

2019-12-16 Thread VA

There you go, log as attachment. Let me know if I did something wrong.

I drew 2 rectangles and pressed ctrl-z -> segfault.
% LANG=C gdb --arg synfigstudio
GNU gdb (Debian 8.3.1-1) 8.3.1
Copyright (C) 2019 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from synfigstudio...
Reading symbols from /usr/lib/debug/.build-id/6d/56da46b9c5d5c54ba4eaf6f08e491fa1f40faf.debug...
(No debugging symbols found in /usr/lib/debug/.build-id/6d/56da46b9c5d5c54ba4eaf6f08e491fa1f40faf.debug)
(gdb) r
Starting program: /usr/bin/synfigstudio 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

   synfig studio -- starting up application...

[New Thread 0x71bed700 (LWP 3373)]
[New Thread 0x713ec700 (LWP 3374)]
synfig(3368) [23:32:35] info: Starting Subsystem "Sound"
No LADSPA plugins were found!

Check your LADSPA_PATH environment variable.
synfig(3368) [23:32:36] info: Starting Subsystem "Types"
synfig(3368) [23:32:36] info: Starting Subsystem "Rendering"
[New Thread 0x7fffddbb3700 (LWP 3375)]
[New Thread 0x7fffdd3b2700 (LWP 3376)]
[New Thread 0x7fffdcbb1700 (LWP 3377)]
[New Thread 0x7fffdc3b0700 (LWP 3378)]
[New Thread 0x7fffdbbaf700 (LWP 3379)]
[New Thread 0x7fffdb3ae700 (LWP 3380)]
[New Thread 0x7fffdabad700 (LWP 3381)]
[New Thread 0x7fffda3ac700 (LWP 3382)]
[New Thread 0x7fffd9bab700 (LWP 3383)]
[New Thread 0x7fffd93aa700 (LWP 3384)]
[New Thread 0x7fffd8ba9700 (LWP 3385)]
[New Thread 0x7fffd83a8700 (LWP 3386)]
synfig(3368) [23:32:36] info: rendering threads 12
synfig(3368) [23:32:36] info: Starting Subsystem "Modules"
synfig(3368) [23:32:36] info: Starting Subsystem "Layers"
synfig(3368) [23:32:36] info: Starting Subsystem "Targets"
synfig(3368) [23:32:36] info: Starting Subsystem "Importers"
synfig(3368) [23:32:36] info: Starting Subsystem "Cairo Importers"
synfig(3368) [23:32:36] warning: Cannot open ./synfig_modules.cfg
synfig(3368) [23:32:36] warning: Cannot open /home/user/.local/share/synfig/synfig_modules.cfg
synfig(3368) [23:32:36] info: Loading modules from /etc/synfig/synfig_modules.cfg
synfig(3368) [23:32:36] info: Loading modules from /etc/synfig/synfig_modules.cfg
synfig(3368) [23:32:36] info: Loading lyr_std..
synfig(3368) [23:32:36] info: Attempting to register "lyr_std"
synfig(3368) [23:32:36] info: Found module "lyr_std"
synfig(3368) [23:32:36] info: Success for "lyr_std"
synfig(3368) [23:32:36] info: Loading lyr_freetype..
synfig(3368) [23:32:36] info: Attempting to register "lyr_freetype"
synfig(3368) [23:32:36] info: Found module "lyr_freetype"
synfig(3368) [23:32:36] info: Initializing FreeType...
synfig(3368) [23:32:36] info: Success for "lyr_freetype"
synfig(3368) [23:32:36] info: Loading mod_geometry..
synfig(3368) [23:32:36] info: Attempting to register "mod_geometry"
synfig(3368) [23:32:36] info: Found module "mod_geometry"
synfig(3368) [23:32:36] info: Success for "mod_geometry"
synfig(3368) [23:32:36] info: Loading mod_gradient..
synfig(3368) [23:32:36] info: Attempting to register "mod_gradient"
synfig(3368) [23:32:36] info: Found module "mod_gradient"
synfig(3368) [23:32:36] info: Success for "mod_gradient"
synfig(3368) [23:32:36] info: Loading mod_particle..
synfig(3368) [23:32:36] info: Attempting to register "mod_particle"
synfig(3368) [23:32:36] info: Found module "mod_particle"
synfig(3368) [23:32:36] info: Success for "mod_particle"
synfig(3368) [23:32:36] info: Loading mod_example..
synfig(3368) [23:32:36] info: Attempting to register "mod_example"
synfig(3368) [23:32:37] info: Found module "mod_example"
synfig(3368) [23:32:37] info: Success for "mod_example"
synfig(3368) [23:32:37] info: Loading mod_gif..
synfig(3368) [23:32:37] info: Attempting to register "mod_gif"
synfig(3368) [23:32:37] info: Found module "mod_gif"
synfig(3368) [23:32:37] info: Success for "mod_gif"
synfig(3368) [23:32:37] info: Loading mod_imagemagick..
synfig(3368) [23:32:37] info: Attempting to register "mod_imagemagick"
synfig(3368) [23:32:37] info: Found module "mod_imagemagick"
synfig(3368) [23:32:37] info: Success for "mod_imagemagick"
synfig(3368) [23:32:37] info: Loading mod_magickpp..
synfig(3368) [23:32:37] info: Attempting to register "mod_magickpp"
synfig(3368) [23:32:37] info: Found module "mod_magickpp"
synfig(3368) [23:32:37] info: Success for "mod_magickpp"
synfig(3368) [23:32:37] info: 

Bug#941633: synfigstudio crashes on almost every operation

2019-12-08 Thread VA

retitle 941633 synfigstudio crashes on almost every operation
severity 941633 serious
thanks

In fact, it's much more general than just when importing an image, it 
crashes for almost everything.


Here are a few example scenarios where synfigstudio crashes:

- start synfigstudio
- draw a rectangle
- press ctrl-z (undo)
-> synfigstudio segfaults

or

- start synfigstudio
- draw 2 rectangles
- select both rectangles
- choose "group layer"
-> synfigstudio segfaults

etc.

Sometimes it doesn't segfault but will fail to do something basic:

- start synfigstudio
- draw a rectangle
- delete the rectangle layer
-> synfigstudio doesn't do it and pop an error dialog mentioning 
"std::exception"


Same when trying to move layers, etc.

In this current state, synfigstudio is unusable.



Bug#945951: hp driver crashes for all documents

2019-12-01 Thread VA

Package: printer-driver-hpcups
Version: 3.19.11+dfsg0-1
Severity: important

All jobs I submit to CUPS fail with "Filter error". The most likely 
cuplrit in /var/log/cups/error_log is probably this:


D [01/Dec/2019:17:29:22 +0100] [Job 578] *** stack smashing detected 
***:  terminated
D [01/Dec/2019:17:29:22 +0100] [Job 578] prnt/backend/hp.c 919: ERROR: 
null print job total=0
D [01/Dec/2019:17:29:22 +0100] [Job 578] PID 1575 
(/usr/lib/cups/filter/hpcups) crashed on signal 6.
D [01/Dec/2019:17:29:22 +0100] [Job 578] PID 1576 
(/usr/lib/cups/backend/hp) exited with no errors.


Even the CUPS test page fails that way, so I guess it's not some 
malformed document but really something terribly wrong in hp driver.




Bug#933771: AppArmor profile prevents reading password on tty

2019-08-03 Thread VA

Package: msmtp
Version: 1.8.3-1

msmtp is capable of reading SMTP passwords in a conf file, using an 
external command, or reading it on the TTY. So it tests by opening /dev/tty:


https://git.marlam.de/gitweb/?p=msmtp.git;a=blob;f=src/password.c;h=aa3b1b530e6e17f3e6d45b395bf399ba99924ecc;hb=HEAD#l198

However, the AppArmor profile prevents this, so in the default 
configuration, msmtp cannot read the tty:


msmtp: authentication method PLAIN needs a password
msmtp: could not send mail (account xxx from xxx/.msmtprc)

It would be enough to add

#include 

in /etc/apparmor.d/usr.bin.msmtp though.



Bug#923661: unusable

2019-05-08 Thread VA

severity 923661 grave
thanks

Cannot access feeds as a result, so the package is worthless as-is.



Bug#919793: prospector won't run at all

2019-03-16 Thread VA

found 919793 0.12.7-2.1
thanks

prospector is still completely unusable in latest package, but with 
different errors.


Without pyroma installed:

Traceback (most recent call last):
  File "/usr/bin/prospector", line 11, in 
load_entry_point('prospector==0.12.7', 'console_scripts', 
'console_script')()

  File "/usr/share/prospector/prospector/run.py", line 165, in main
prospector.execute()
  File "/usr/share/prospector/prospector/run.py", line 53, in execute
for tool in self.config.get_tools(found_files):
  File "/usr/share/prospector/prospector/config/__init__.py", line 45, 
in get_tools

config_result = tool.configure(self, found_files)
  File "/usr/share/prospector/prospector/tools/pylint/__init__.py", 
line 172, in configure

linter.reset_options()
  File "/usr/share/prospector/prospector/tools/pylint/linter.py", line 
30, in reset_options

OptionsManagerMixIn.__init__(self, usage=PyLinter.__doc__, quiet=True)
TypeError: __init__() got an unexpected keyword argument 'quiet'

And with pyroma installed:

Traceback (most recent call last):
  File "/usr/bin/prospector", line 11, in 
load_entry_point('prospector==0.12.7', 'console_scripts', 
'console_script')()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 
489, in load_entry_point

return get_distribution(dist).load_entry_point(group, name)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 
2793, in load_entry_point

return ep.load()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 
2411, in load

return self.resolve()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 
2417, in resolve

module = __import__(self.module_name, fromlist=['__name__'], level=0)
  File "/usr/share/prospector/prospector/run.py", line 8, in 
from prospector import blender, postfilter, tools
  File "/usr/share/prospector/prospector/tools/__init__.py", line 48, 
in 

'pyroma': _optional_tool('pyroma'),
  File "/usr/share/prospector/prospector/tools/__init__.py", line 29, 
in _optional_tool

tool_package = __import__(package_name, fromlist=[tool_class_name])
  File "/usr/share/prospector/prospector/tools/pyroma/__init__.py", 
line 27, in 

ratings.PEP386Version: 'PYR04',
AttributeError: module 'pyroma.ratings' has no attribute 'PEP386Version'



Bug#919793: prospector won't run at all

2019-01-19 Thread VA

Package: prospector
Version: 0.12.7-2
Severity: important

Wherever I try to run prospector, it just fails with this backtrace:

Traceback (most recent call last):
  File "/usr/bin/prospector", line 11, in 
load_entry_point('prospector==0.12.7', 'console_scripts', 
'console_script')()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 
487, in load_entry_point

return get_distribution(dist).load_entry_point(group, name)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 
2728, in load_entry_point

return ep.load()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 
2346, in load

return self.resolve()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 
2352, in resolve

module = __import__(self.module_name, fromlist=['__name__'], level=0)
  File "/usr/share/prospector/prospector/run.py", line 8, in 
from prospector import blender, postfilter, tools
  File "/usr/share/prospector/prospector/tools/__init__.py", line 7, in 


from prospector.tools.pylint import PylintTool
  File "/usr/share/prospector/prospector/tools/pylint/__init__.py", 
line 6, in 

from pylint.config import find_pylintrc
  File "/usr/lib/python3/dist-packages/pylint/config.py", line 58, in 


from pylint import utils
  File "/usr/lib/python3/dist-packages/pylint/utils.py", line 56, in 


from astroid import nodes, Module
  File "/usr/lib/python3/dist-packages/astroid/__init__.py", line 63, 
in 

from astroid.nodes import *
  File "/usr/lib/python3/dist-packages/astroid/nodes.py", line 23, in 


from astroid.node_classes import (
  File "/usr/lib/python3/dist-packages/astroid/node_classes.py", line 
38, in 

from astroid import bases
  File "/usr/lib/python3/dist-packages/astroid/bases.py", line 33, in 


MANAGER = manager.AstroidManager()
  File "/usr/lib/python3/dist-packages/astroid/util.py", line 26, in 


lambda: importlib.import_module("." + module_name, "astroid")
  File "/usr/lib/python3.6/importlib/__init__.py", line 126, in 
import_module

return _bootstrap._gcd_import(name[level:], package, level)
  File "/usr/lib/python3/dist-packages/astroid/manager.py", line 25, in 


from astroid import modutils
  File "/usr/lib/python3/dist-packages/astroid/modutils.py", line 35, 
in 
from distutils.sysconfig import get_python_lib  # pylint: 
disable=import-error

ModuleNotFoundError: No module named 'distutils.sysconfig'



Bug#911467: gcalcli fails to delete events

2018-10-20 Thread VA

Package: gcalcli
Version: 4.0.0~a4-1

When trying to delete events with gcalcli, I get this traceback:

  File "/bin/gcalcli", line 2538, in 
BowChickaWowWow()
  File "/bin/gcalcli", line 2510, in BowChickaWowWow
FLAGS.iamaexpert, eStart, eEnd)
  File "/bin/gcalcli", line 1876, in DeleteEvents
yearDate=True, work=self._DeleteEvent)
  File "/bin/gcalcli", line 1568, in _IterateEvents
work(event)
  File "/bin/gcalcli", line 1386, in _DeleteEvent
val = raw_input()
NameError: name 'raw_input' is not defined

Indeed, gcalcli seems to be a Python 3 program, where raw_input doesn't 
exist.
By looking at the upstream source code, it seems the problem is not 
present in the latest version: 
https://github.com/insanum/gcalcli/blob/master/gcalcli/gcalcli.py




Bug#907788: "dh key too small" since openssl upgrade

2018-09-02 Thread VA

Package: curl
Version: 7.61.0-1

Since openssl upgrade to 1.1.1~~pre9-1, curl is not able anymore to do 
requests to some sites. For example:


% curl https://www.credit-cooperatif.coop/
curl: (35) error:141A318A:SSL routines:tls_process_ske_dhe:dh key too small

It used to work with curl, and it still works with wget (which uses gnutls).

I suspect it's related to #907015.



Bug#905479: cannot import urllib3.contrib.pyopenssl

2018-08-05 Thread VA

Package: python-urllib3
Version: 1.22-1

I cannot import urllib3.contrib.pyopenssl:

>>> import urllib3.contrib.pyopenssl
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python2.7/dist-packages/urllib3/contrib/pyopenssl.py", 
line 62, in 

from ..packages import six
ImportError: cannot import name six

But python-six is installed.
"import urllib3.contrib.pyopenssl" works fine with python3-urllib3 though.



Bug#894606: kross wrong dependency

2018-04-02 Thread VA

Package: kross
Version: 5.44.0-1

"kross" package depends on libqt5core5a and other Qt5 lib packages. But 
in reality, the "kross" binary depends on Qt4:


% ldd =kross | grep Qt
	libQtGui.so.4 => /usr/lib/x86_64-linux-gnu/libQtGui.so.4 
(0x7f9eb59dc000)
	libQtCore.so.4 => /usr/lib/x86_64-linux-gnu/libQtCore.so.4 
(0x7f9eb5008000)
	libQtScript.so.4 => /usr/lib/x86_64-linux-gnu/libQtScript.so.4 
(0x7f9eb4408000)
	libQtXml.so.4 => /usr/lib/x86_64-linux-gnu/libQtXml.so.4 
(0x7f9eb41c2000)
	libQtNetwork.so.4 => /usr/lib/x86_64-linux-gnu/libQtNetwork.so.4 
(0x7f9eb3449000)
	libQtSvg.so.4 => /usr/lib/x86_64-linux-gnu/libQtSvg.so.4 
(0x7f9eb31f)
	libQtDBus.so.4 => /usr/lib/x86_64-linux-gnu/libQtDBus.so.4 
(0x7f9eb2929000)


So there's a mismatch between what the package claims and what the 
package contains.


In contrast, the "krosspython" package provides a Qt5 plugin. All in 
all, "kross" command cannot be used to run krosspython scripts.




Bug#893730: Missing dependency?

2018-03-21 Thread VA

Package: python3-botan
Version: 2.4.0-3

After installing Python bindings for botan, it seems some dependency is 
missing (or not installable):


>>> import botan2
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/botan2.py", line 39, in 
botan = CDLL('libbotan-2.so') # pylint: disable=invalid-name
  File "/usr/lib/python3.6/ctypes/__init__.py", line 348, in __init__
self._handle = _dlopen(self._name, mode)
OSError: libbotan-2.so: cannot open shared object file: No such file or 
directory




Bug#890200: PyQt5 package should provide an egg-info

2018-02-11 Thread VA

Package: python-pyqt5
Version: 5.9.2+dfsg-1

Many Debian python packages include an egg-info folder, but python-pyqt5 
does not.


For example, when python-requests is installed with apt:

% dpkg -L python-requests | grep egg-info
/usr/lib/python2.7/dist-packages/requests-2.18.4.egg-info
/usr/lib/python2.7/dist-packages/requests-2.18.4.egg-info/PKG-INFO
/usr/lib/python2.7/dist-packages/requests-2.18.4.egg-info/dependency_links.txt
/usr/lib/python2.7/dist-packages/requests-2.18.4.egg-info/not-zip-safe
/usr/lib/python2.7/dist-packages/requests-2.18.4.egg-info/requires.txt
/usr/lib/python2.7/dist-packages/requests-2.18.4.egg-info/top_level.txt
% dpkg -L python-pyqt5 | grep egg-info
%

When installing a pip package which requires a python dependency that is 
already installed with Debian packages, pip finds it and uses the 
Debian-installed package.
Since python-pyqt5 does not provide any, pip fails to find 'PyQt5' 
locally and so programs may fail to run even though PyQt5 is installed.




Bug#886020: wrong help message

2018-01-01 Thread VA

Version: 1.0-1.2+b2
Package: gnome-xcf-thumbnailer

When I try to display gnome-xcf-thumbnailer help, it tells me about NDS 
files, not XCF:


% gnome-xcf-thumbnailer -h
Usage:
  gnome-xcf-thumbnailer [OPTION?] [FILE...] Thumbnail Nintendo DS ROMs



Bug#862024: Split More Widely Used Plugins into a Separate Package

2017-12-12 Thread VA
I second this wish, the upgrade suddenly takes a lot of space for who 
knows which obscure format.




Bug#873642: not "serious"

2017-09-06 Thread VA

Control: severity -1 normal

This bug is not "serious", only qvideoob is affected by this lack of 
dependency, other commands in weboob-qt do not have this issue. It does 
not make the package useless.
Furthermore, you can make qvideoob work by simply installing the 
aforementioned dependency...




Bug#870469: Should use a fork of pdfminer

2017-08-02 Thread VA

Package: python-pdfminer
Version: 20140328+dfsg-1

python-pdfminer upstream is unmaintained and is not compatible with 
Python 3: https://pypi.python.org/pypi/pdfminer


However, there's a drop-in fork which is Python 3-compatible and 
maintainted:

https://pypi.python.org/pypi/pdfminer.six
https://github.com/pdfminer/pdfminer.six
It could be used instead.



Bug#865885: weboob plugin is unusable

2017-06-25 Thread VA

Package: kmymoney
Version: 4.8.0-2+b1

When I try to use the weboob plugin with "map to online account", I get 
nothing if click on "select backends".

On stderr, kmymoney outputs :

Kross: "Error error=Failed to determine interpreter for scriptfile 
"/usr/share/kde4/apps/kmm_weboob/weboob.py" lineno=-1 trace=


However, I have the kross and krosspython packages installed (4:16.08.0-1).
I think the problem might be that krosspython uses Qt5 while kmymoney 
uses Qt4.




Bug#860148: python-crypto is unmaintained

2017-04-12 Thread VA

Package: python-crypto
Version: 2.6.1-7

The python-crypto project seems abandoned, the issues are accumulating: 
https://github.com/dlitz/pycrypto/issues
Also, it may have unreleased security fixes, see 
https://github.com/ansible/ansible/issues/23179


On the other hand, the pycryptodome project is a fork of python-crypto 
and a drop-in for it: https://github.com/Legrandin/pycryptodome.

I think it should be considered to replace python-crypto.



Bug#854488: missing dependency

2017-02-18 Thread VA

reopen 854488
thanks

Hello,

I started thunderbird and got anxious seeing it was taking more than 30 
seconds. After some investigation by running htop, I saw it was 
migrating my profile, but it was unexpected.


I searched a bit and stumbled upon this bug report. However, I didn't 
get any message.
Judging 
https://anonscm.debian.org/cgit/pkg-mozilla/icedove.git/tree/debian/thunderbird-wrapper.sh?h=debian/sid 
I guess it's because I'm running xfce, but zenity is not installed by 
xfce...
Either zenity should be added as a dependency, or the migration script 
should rather check which message box tool is installed and run that 
one, instead of the most cosmetic - yet unavailable - tool.




Bug#854242: dbg packages?

2017-02-05 Thread VA

Source: qtbase-opensource-src
Version: 5.7.1+dfsg-3

It seems there are no more -dbg packages for Qt5?



Bug#841563: typescript failure

2016-12-05 Thread VA
From what can be seen from the build log, it seems the build fails 
because typescript is not found:

"tsserver not found. TypeScript 1.5 or higher is required"



Bug#844225: please rebuild

2016-11-13 Thread VA

Package: python-pyqt5.qsci
Version: 2.9.3+dfsg-3

Since update of Qt to 5.7 in Debian, a basic program using Python 
QScintilla segfaults:


from PyQt5.QtWidgets import *
from PyQt5.Qsci import *
app = QApplication([])
ed = QsciScintilla()
ed.show()
print(ed.text())
app.exec_()

Is this due to the qscintilla bindings not having been updated/rebuilt?



Bug#841830: please provide qtwebengine

2016-10-23 Thread VA

Source: pyqt5
Version: 5.7+dfsg-2

Qt Webkit has been deprecated since Qt 5.5 
(https://wiki.qt.io/New_Features_in_Qt_5.5#Deprecated_Functionality) and 
is to be replaced by Qt WebEngine (which was introduced in Qt 5.4). Qt 
WebEngine has a corresponding PyQt module.


Please provide a package for accessing QtWebEngine (like 
python-pyqt5.qtwebkit).




Bug#831974: black screen with nvidia driver

2016-09-14 Thread VA
So since all this time I have this ugly vesa resolution, nothing has
worked so far, the recent kernel upgrade didn't solve the problem, and
there are no updates for the nvidia driver...

However, there's something, I created a new partition and did a fresh
stable i386 install then upgrade to unstable, to ensure it was not my
old setup which had a specific problem, but it seems not.
So on that new install, I still get a black screen. dmesg shows a
desperate output:

[  100.314324] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver
for UNIX platforms  361.45.18  Tue Jun 21 17:58:16 PDT 2016
[  100.315130] nvidia-modeset: Allocated GPU:0
(GPU-5e911e77-bb03-4910-7d0a-8201558cf33b) @ PCI::01:00.0
[  100.709686] nvidia-modeset: Freed GPU:0
(GPU-5e911e77-bb03-4910-7d0a-8201558cf33b) @ PCI::01:00.0
[  101.045590] gnome-shell[1019]: segfault at 24448b2c ip b6118b81 sp
bfded03c error 4 in libc-2.24.so[b60a3000+1b1000]
[  101.449901] nvidia-modeset: Allocated GPU:0
(GPU-5e911e77-bb03-4910-7d0a-8201558cf33b) @ PCI::01:00.0
[  101.823843] nvidia-modeset: Freed GPU:0
(GPU-5e911e77-bb03-4910-7d0a-8201558cf33b) @ PCI::01:00.0
[  102.169960] gnome-shell[1074]: segfault at 24448b2c ip b60e2b81 sp
bfbd651c error 4 in libc-2.24.so[b606d000+1b1000]
[  102.546999] nvidia-modeset: Allocated GPU:0
(GPU-5e911e77-bb03-4910-7d0a-8201558cf33b) @ PCI::01:00.0
[  102.936657] nvidia-modeset: Freed GPU:0
(GPU-5e911e77-bb03-4910-7d0a-8201558cf33b) @ PCI::01:00.0
[  103.259820] gnome-shell[1128]: segfault at 24448b2c ip b614bb81 sp
bfcb89dc error 4 in libc-2.24.so[b60d6000+1b1000]

And it goes on until I reset the machine.

I had a lead though, I tried another fresh stable install then upgrade
to unstable, but on amd64 this time, and this time, the nvidia driver
worked fine.

So it seems to be an architecture problem to solve.



Bug#836526: syntax error in apache conf file

2016-09-03 Thread VA
Package: yubikey-ksm
Version: 1.15-6

The shipped /etc/apache2/conf-enabled/yubikey-ksm.conf seems to have a
syntax error, a  tag is open but a  is closed.
See:
https://sources.debian.net/src/yubikey-ksm/1.15-6/debian/conf/apache.conf/



Bug#831974: black screen with nvidia driver

2016-07-31 Thread VA
I suddenly realise I forgot again to reply to the debian bug...

Le 24/07/2016 à 14:48, Luca Boccassi a écrit :
> Did you try with the new version that was just uploaded to
> experimental, 361.45.18-1, or was it the previous 358 version? Could
> you please attach the report while running the new version, including
> the logs with backtraces? Thanks!

Here's the reportbug with nvidia-driver from experimental. It seems this
time dmesg doesn't report freezes, I don't get beeps, but the screen is
still desperately black when starting Xorg. At least I can switch to
TTYs too.

-- Package-specific info:
uname -a:
Linux hostx 4.6.0-1-686-pae #1 SMP Debian 4.6.4-1 (2016-07-18) i686
GNU/Linux

/proc/version:
Linux version 4.6.0-1-686-pae (debian-ker...@lists.debian.org) (gcc
version 5.4.0 20160609 (Debian 5.4.0-6) ) #1 SMP Debian 4.6.4-1 (2016-07-18)

/proc/driver/nvidia/version:
NVRM version: NVIDIA UNIX x86 Kernel Module  361.45.18  Tue Jun 21
17:29:18 PDT 2016
GCC version:  gcc version 5.4.0 20160609 (Debian 5.4.0-6)

lspci 'VGA compatible controller [0300]':
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF104
[GeForce GTX 460] [10de:0e22] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Gigabyte Technology Co., Ltd GF104 [GeForce GTX 460] 
[1458:34fc]
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: nvidia
Kernel modules: nvidia

dmesg:
[0.00] Console: colour VGA+ 80x25
[0.523436] vgaarb: setting as boot device: PCI::01:00.0
[0.523575] vgaarb: device added:
PCI::01:00.0,decodes=io+mem,owns=io+mem,locks=none
[0.523785] vgaarb: loaded
[0.523901] vgaarb: bridge control possible :01:00.0
[1.446467] Linux agpgart interface v0.103
[   17.460382] nvidia: module license 'NVIDIA' taints kernel.
[   17.469770] vgaarb: device changed decodes:
PCI::01:00.0,olddecodes=io+mem,decodes=none:owns=io+mem
[   17.470472] nvidia-nvlink: Nvlink Core is being initialized, major
device number 249
[   17.471420] [drm] Initialized nvidia-drm 0.0.0 20150116 for
:01:00.0 on minor 0
[   17.471634] NVRM: loading NVIDIA UNIX x86 Kernel Module  361.45.18
Tue Jun 21 17:29:18 PDT 2016
[   19.352813] snd_hda_intel :01:00.1: Handle vga_switcheroo audio
client
[   20.254722] input: HDA NVidia HDMI/DP,pcm=3 as
/devices/pci:00/:00:03.0/:01:00.1/sound/card1/input18
[   20.255015] input: HDA NVidia HDMI/DP,pcm=7 as
/devices/pci:00/:00:03.0/:01:00.1/sound/card1/input19
[   20.257372] input: HDA NVidia HDMI/DP,pcm=8 as
/devices/pci:00/:00:03.0/:01:00.1/sound/card1/input20
[   20.257834] input: HDA NVidia HDMI/DP,pcm=9 as
/devices/pci:00/:00:03.0/:01:00.1/sound/card1/input21
[   54.037653] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver
for UNIX platforms  361.45.18  Tue Jun 21 17:58:16 PDT 2016
[   54.038190] nvidia-modeset: Allocated GPU:0
(GPU-5e911e77-bb03-4910-7d0a-8201558cf33b) @ PCI::01:00.0
[   55.489082] nvidia-modeset: Freed GPU:0
(GPU-5e911e77-bb03-4910-7d0a-8201558cf33b) @ PCI::01:00.0
[   55.978705] nvidia-modeset: Allocated GPU:0
(GPU-5e911e77-bb03-4910-7d0a-8201558cf33b) @ PCI::01:00.0
[   56.350452] nvidia-modeset: Freed GPU:0
(GPU-5e911e77-bb03-4910-7d0a-8201558cf33b) @ PCI::01:00.0
[   57.605929] nvidia-modeset: Allocated GPU:0
(GPU-5e911e77-bb03-4910-7d0a-8201558cf33b) @ PCI::01:00.0
[   57.978218] nvidia-modeset: Freed GPU:0
(GPU-5e911e77-bb03-4910-7d0a-8201558cf33b) @ PCI::01:00.0
[   58.468168] nvidia-modeset: Allocated GPU:0
(GPU-5e911e77-bb03-4910-7d0a-8201558cf33b) @ PCI::01:00.0
[   58.839802] nvidia-modeset: Freed GPU:0
(GPU-5e911e77-bb03-4910-7d0a-8201558cf33b) @ PCI::01:00.0
[   59.479531] nvidia-modeset: Allocated GPU:0
(GPU-5e911e77-bb03-4910-7d0a-8201558cf33b) @ PCI::01:00.0
[   59.867520] nvidia-modeset: Freed GPU:0
(GPU-5e911e77-bb03-4910-7d0a-8201558cf33b) @ PCI::01:00.0
[   60.475159] nvidia-modeset: Allocated GPU:0
(GPU-5e911e77-bb03-4910-7d0a-8201558cf33b) @ PCI::01:00.0
[   60.844949] nvidia-modeset: Freed GPU:0
(GPU-5e911e77-bb03-4910-7d0a-8201558cf33b) @ PCI::01:00.0
[  381.950246] nvidia-modeset: Allocated GPU:0
(GPU-5e911e77-bb03-4910-7d0a-8201558cf33b) @ PCI::01:00.0
[  382.338811] nvidia-modeset: Freed GPU:0
(GPU-5e911e77-bb03-4910-7d0a-8201558cf33b) @ PCI::01:00.0
[  383.011809] nvidia-modeset: Allocated GPU:0
(GPU-5e911e77-bb03-4910-7d0a-8201558cf33b) @ PCI::01:00.0
[  383.401053] nvidia-modeset: Freed GPU:0
(GPU-5e911e77-bb03-4910-7d0a-8201558cf33b) @ PCI::01:00.0
[  383.989224] nvidia-modeset: Allocated GPU:0
(GPU-5e911e77-bb03-4910-7d0a-8201558cf33b) @ PCI::01:00.0
[  384.381447] nvidia-modeset: Freed GPU:0
(GPU-5e911e77-bb03-4910-7d0a-8201558cf33b) @ PCI::01:00.0
[  385.005208] nvidia-modeset: Allocated GPU:0

Bug#831016: qscintilla text cursor wrong position

2016-07-24 Thread VA
Le 24/07/2016 à 17:45, Scott Kitterman a écrit :
> I can reproduce what's in your screen cast. Every single version of PyQSci I 
> try does exactly that regardless of Python version, Qt (4 or 5) version, or 
> QScintilla version.

I already reassigned to bug to SciTE, since the same issue appears with
SciTE (and SciTE is THE app using the Scintilla lib).

> I think your screen cast shows normal behavior.

Definitely not. When typing characters, the cursor should visually be
right after the character typed, at max a few pixels on the right. In
the screencast, we can see that the cursor gets further away from the
typed character each time. After a string of a dozen characters, the
cursor seems to be very far in void space, while it should be right
after the last letter.
>From what I observed, certain letters do positive offset (cursor goes
further on the right), while some letters do negative offset (cursor
goes further on the left)...

I can't say exactly when this regression started, but it was probably
within the few previous weeks on unstable. I can say that Scintilla and
QScintilla don't show the problem on stable.

> I don't think your test case demonstrates it's a QScintilla problem.

Agreed, the report has been reassigned to SciTE.

However, it's worth nothing that using a monospaced font (Ctrl+F11 in
SciTE, or adding "sci.setFont(QFont('monospace'))" in the example python
script) may give a normal result, i.e. no offset incrementally moving
away the cursor from its character.
Unexplainably, on my machine, it also depends on the desktop used
(problems with XFCE, no bug with fluxbox/openbox).



Bug#831974: Fwd: Re: Bug#831974: black screen with nvidia driver

2016-07-24 Thread VA
And I forgot to cc the bugreport...

Le 21/07/2016 à 00:02, Luca Boccassi a écrit :
> Not the first time I see that backtrace, but I don't think it has
> anything to do with the packaging, I'm beginning to think it might be an
> incompatibility between the kernel modules in the older releases and
> newer kernel versions..

I've tried the experimental package of nvidia-driver, and it seems to
give a black screen too (I didn't check the logs though)

> Still, could you please attach the full system report with:

Here it is:


-- Package-specific info:
uname -a:
Linux hostx 4.6.0-1-686-pae #1 SMP Debian 4.6.4-1 (2016-07-18) i686
GNU/Linux

/proc/version:
Linux version 4.6.0-1-686-pae (debian-ker...@lists.debian.org) (gcc
version 5.4.0 20160609 (Debian 5.4.0-6) ) #1 SMP Debian 4.6.4-1 (2016-07-18)

/proc/driver/nvidia/version:
NVRM version: NVIDIA UNIX x86 Kernel Module  352.79  Wed Jan 13 15:28:49
PST 2016
GCC version:  gcc version 5.4.0 20160609 (Debian 5.4.0-6)

lspci 'VGA compatible controller [0300]':
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF104
[GeForce GTX 460] [10de:0e22] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Gigabyte Technology Co., Ltd GF104 [GeForce GTX 460] 
[1458:34fc]
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: nvidia
Kernel modules: nvidia

dmesg:
[1.448239] Linux agpgart interface v0.103
[   20.223203] nvidia: module license 'NVIDIA' taints kernel.
[   20.230978] vgaarb: device changed decodes:
PCI::01:00.0,olddecodes=io+mem,decodes=none:owns=io+mem
[   20.231372] [drm] Initialized nvidia-drm 0.0.0 20150116 for
:01:00.0 on minor 0
[   20.231585] NVRM: loading NVIDIA UNIX x86 Kernel Module  352.79  Wed
Jan 13 15:28:49 PST 2016
[   23.301894] snd_hda_intel :01:00.1: Handle vga_switcheroo audio
client
[   24.285966] input: HDA NVidia HDMI/DP,pcm=3 as
/devices/pci:00/:00:03.0/:01:00.1/sound/card1/input18
[   24.286258] input: HDA NVidia HDMI/DP,pcm=7 as
/devices/pci:00/:00:03.0/:01:00.1/sound/card1/input19
[   24.287304] input: HDA NVidia HDMI/DP,pcm=8 as
/devices/pci:00/:00:03.0/:01:00.1/sound/card1/input20
[   24.287585] input: HDA NVidia HDMI/DP,pcm=9 as
/devices/pci:00/:00:03.0/:01:00.1/sound/card1/input21
[   90.530316]  [] ? _nv000666rm+0x84/0xdc [nvidia]
[   90.530385]  [] ? os_io_read_byte+0xc/0x10 [nvidia]
[   90.530454]  [] ? rm_shutdown_gvi_device+0x73/0x260 [nvidia]
[   90.530525]  [] ? _nv016241rm+0x76b6/0xacb0 [nvidia]
[   90.530595]  [] ? _nv000817rm+0x74/0x8c [nvidia]
[   90.530664]  [] ? _nv012223rm+0x146/0x4d0 [nvidia]
[   90.530734]  [] ? _nv012593rm+0x63/0x140 [nvidia]
[   90.530803]  [] ? _nv000712rm+0x25e/0x2e0 [nvidia]
[   90.530872]  [] ? _nv000636rm+0x24a/0x4dc [nvidia]
[   90.530941]  [] ? _nv000648rm+0xc5/0x358 [nvidia]
[   90.531010]  [] ? rm_disable_adapter+0x46/0xc4 [nvidia]
[   90.531062]  [] ? nvidia_close+0x1a0/0x410 [nvidia]
[   90.53]  [] ? nvidia_frontend_compat_ioctl+0x1d/0x30
[nvidia]
[   90.531161]  [] ? nvidia_frontend_close+0x3d/0x90 [nvidia]
[  116.438678]  snd_hda_codec_hdmi(E) fuse(E) snd_hda_codec_via(E)
joydev(E) iTCO_wdt(E) iTCO_vendor_support(E) coretemp(E) kvm_intel(E)
snd_hda_codec_generic(E) kvm(E) snd_hda_intel(E) evdev(E) i7core_edac(E)
snd_hda_codec(E) edac_core(E) snd_hda_core(E) sg(E) snd_hwdep(E)
i2c_i801(E) irqbypass(E) pcspkr(E) serio_raw(E) 8250_fintek(E) shpchp(E)
snd_pcm_oss(E) snd_mixer_oss(E) snd_pcm(E) snd_timer(E) snd(E)
lpc_ich(E) mfd_core(E) soundcore(E) asus_atk0110(E) button(E)
acpi_cpufreq(E) tpm_tis(E) tpm(E) processor(E) nvidia(POE) drm(E)
parport_pc(E) ppdev(E) lp(E) parport(E) loop(E) autofs4(E) ext4(E)
xts(E) lrw(E) gf128mul(E) ablk_helper(E) cryptd(E) aes_i586(E) crc16(E)
jbd2(E) crc32c_generic(E) mbcache(E) ecb(E) cbc(E) algif_skcipher(E)
af_alg(E) dm_crypt(E) dm_mod(E) sd_mod(E) hid_generic(E) ata_generic(E)
[  116.438771] EIP is at os_io_read_byte+0xc/0x10 [nvidia]
[  116.438898]  [] ? rm_shutdown_gvi_device+0x73/0x260 [nvidia]
[  116.438968]  [] ? _nv016241rm+0x76b6/0xacb0 [nvidia]
[  116.439039]  [] ? _nv000817rm+0x74/0x8c [nvidia]
[  116.439107]  [] ? _nv012223rm+0x146/0x4d0 [nvidia]
[  116.439177]  [] ? _nv012593rm+0x63/0x140 [nvidia]
[  116.439246]  [] ? _nv000712rm+0x25e/0x2e0 [nvidia]
[  116.439315]  [] ? _nv000636rm+0x24a/0x4dc [nvidia]
[  116.439384]  [] ? _nv000648rm+0xc5/0x358 [nvidia]
[  116.439453]  [] ? rm_disable_adapter+0x46/0xc4 [nvidia]
[  116.439506]  [] ? nvidia_close+0x1a0/0x410 [nvidia]
[  116.439555]  [] ? nvidia_frontend_compat_ioctl+0x1d/0x30
[nvidia]
[  116.439605]  [] ? nvidia_frontend_close+0x3d/0x90 [nvidia]
[  144.439226]  snd_hda_codec_hdmi(E) fuse(E) snd_hda_codec_via(E)
joydev(E) iTCO_wdt(E) iTCO_vendor_support(E) coretemp(E) kvm_intel(E)
snd_hda_codec_generic(E) kvm(E) snd_hda_intel(E) evdev(E) 

Bug#831016: qscintilla text cursor wrong position

2016-07-24 Thread VA
I don't understand, you can't see what's wrong when viewing my
screencast (you think it's normal behavior?) or you can't reproduce it
on your system?



Bug#831974: black screen with nvidia driver

2016-07-20 Thread VA
Package: nvidia-kernel-dkms
Version: 352.79-10
Severity: important

After upgrade to kernel 4.6, nvidia driver does not seem to work
anymore, I just get a black screen. There's some flickering, Xorg seems
to be restarting though nothing appears.

Here's what I get in dmesg:

[   58.134694] pmd_set_huge: Cannot satisfy [mem 0xf400-0xf420]
with a huge-page mapping due to MTRR override.
[   87.050458] INFO: rcu_sched self-detected stall on CPU
[   87.050460]  2-...: (5249 ticks this GP) idle=8eb/141/0
softirq=7323/7323 fqs=5248
[   87.050462]   (t=5250 jiffies g=3816 c=3815 q=1064)
[   87.050462] Task dump for CPU 2:
[   87.050464] XorgR running  0  3279   3274 0x0048
[   87.050466]  0003 844c7874 f77dbe70 c10cc1cd c1735e80 c1735e80
f78fa880 c1735e80
[   87.050467]  f77dbec0 c10cf6c1 c1664320 1482 0ee8 0ee7
0428 
[   87.050468]  f78fa040  c1861040 f77dbec0 c109985a f0374f00
 1b6b
[   87.050469] Call Trace:
[   87.050477]  [] ? rcu_dump_cpu_stacks+0x6d/0xb0
[   87.050479]  [] ? rcu_check_callbacks+0x4a1/0x700
[   87.050483]  [] ? account_process_tick+0x5a/0x160
[   87.050484]  [] ? update_process_times+0x32/0x60
[   87.050486]  [] ? tick_sched_handle.isra.12+0x26/0x60
[   87.050487]  [] ? tick_sched_timer+0x3a/0x80
[   87.050488]  [] ? __remove_hrtimer+0x3f/0x80
[   87.050489]  [] ? __hrtimer_run_queues+0xce/0x2a0
[   87.050491]  [] ? __wake_up+0x37/0x50
[   87.050492]  [] ? tick_sched_handle.isra.12+0x60/0x60
[   87.050493]  [] ? hrtimer_interrupt+0x93/0x1a0
[   87.050495]  [] ? add_interrupt_randomness+0x15c/0x1c0
[   87.050498]  [] ? hpet_interrupt_handler+0x15/0x40
[   87.050499]  [] ? handle_irq_event_percpu+0x7e/0x1c0
[   87.050501]  [] ? find_next_bit+0x17/0x30
[   87.050502]  [] ? handle_irq_event+0x2f/0x50
[   87.050504]  [] ? handle_edge_irq+0x6d/0x120
[   87.050505]  [] ? handle_level_irq+0xe0/0xe0
[   87.050506]  [] ? handle_irq+0x54/0x70
[   87.050509][] ? do_IRQ+0x3c/0xc0
[   87.050510]  [] ? common_interrupt+0x33/0x38
[   87.050601]  [] ? rm_is_supported_device+0x188/0x18c [nvidia]
[   87.050659]  [] ? os_io_read_byte+0xc/0x10 [nvidia]
[   87.050737]  [] ? rm_shutdown_gvi_device+0x73/0x260 [nvidia]
[   87.050817]  [] ? _nv016241rm+0x76b6/0xacb0 [nvidia]
[   87.050896]  [] ? _nv000817rm+0x74/0x8c [nvidia]
[   87.050971]  [] ? _nv012223rm+0x146/0x4d0 [nvidia]
[   87.051050]  [] ? _nv012593rm+0x63/0x140 [nvidia]
[   87.051128]  [] ? _nv000712rm+0x25e/0x2e0 [nvidia]
[   87.051205]  [] ? _nv000636rm+0x24a/0x4dc [nvidia]
[   87.051274]  [] ? _nv000648rm+0xc5/0x358 [nvidia]
[   87.051343]  [] ? rm_disable_adapter+0x46/0xc4 [nvidia]
[   87.051345]  [] ? down+0x13/0x50
[   87.051396]  [] ? nvidia_close+0x1a0/0x410 [nvidia]
[   87.051446]  [] ? nvidia_frontend_compat_ioctl+0x1d/0x30
[nvidia]
[   87.051496]  [] ? nvidia_frontend_close+0x3d/0x90 [nvidia]
[   87.051499]  [] ? __fput+0xca/0x1d0
[   87.051502]  [] ? task_work_run+0x87/0xa0
[   87.051503]  [] ? exit_to_usermode_loop+0xd5/0xe0
[   87.051504]  [] ? do_fast_syscall_32+0x127/0x140
[   87.051506]  [] ? sysenter_past_esp+0x47/0x75
[  112.356682] NMI watchdog: BUG: soft lockup - CPU#2 stuck for 22s!
[Xorg:3279]
[  112.356694] Modules linked in: pci_stub(E) vboxpci(OE) vboxnetadp(OE)
vboxnetflt(OE) vboxdrv(OE) nf_conntrack_ipv6(E) nf_defrag_ipv6(E)
xt_multiport(E) xt_tcpudp(E) ip6table_filter(E) ip6_tables(E)
iptable_filter(E) ip_tables(E) nf_conntrack_irc(E) nf_conntrack_pptp(E)
nf_conntrack_proto_sctp(E) nf_conntrack_sip(E) nf_conntrack_tftp(E)
nf_conntrack_netlink(E) nfnetlink(E) nf_conntrack_snmp(E)
xt_conntrack(E) x_tables(E) nf_conntrack_proto_udplite(E)
nf_conntrack_sane(E) nf_conntrack_ftp(E) nf_conntrack_h323(E)
nf_conntrack_proto_dccp(E) nf_conntrack_proto_gre(E)
nf_conntrack_netbios_ns(E) nf_conntrack_broadcast(E) ts_kmp(E)
nf_conntrack_amanda(E) nf_conntrack_ipv4(E) nf_defrag_ipv4(E)
nf_conntrack(E) cpufreq_stats(E) cpufreq_powersave(E)
cpufreq_conservative(E) cpufreq_userspace(E) binfmt_misc(E)
[  112.356711]  fuse(E) snd_hda_codec_hdmi(E) snd_hda_codec_via(E)
snd_hda_codec_generic(E) iTCO_wdt(E) joydev(E) coretemp(E)
iTCO_vendor_support(E) evdev(E) kvm_intel(E) kvm(E) snd_hda_intel(E)
snd_hda_codec(E) serio_raw(E) snd_hda_core(E) snd_hwdep(E)
snd_pcm_oss(E) pcspkr(E) irqbypass(E) i7core_edac(E) snd_mixer_oss(E)
edac_core(E) i2c_i801(E) snd_pcm(E) sg(E) snd_timer(E) snd(E)
soundcore(E) asus_atk0110(E) lpc_ich(E) mfd_core(E) button(E)
8250_fintek(E) shpchp(E) acpi_cpufreq(E) tpm_tis(E) tpm(E) processor(E)
nvidia(POE) drm(E) parport_pc(E) ppdev(E) lp(E) parport(E) loop(E)
autofs4(E) ext4(E) xts(E) lrw(E) gf128mul(E) ablk_helper(E) cryptd(E)
aes_i586(E) crc16(E) jbd2(E) crc32c_generic(E) mbcache(E) ecb(E) cbc(E)
algif_skcipher(E) af_alg(E) dm_crypt(E) dm_mod(E) sd_mod(E)
hid_generic(E) ata_generic(E)
[  112.356715]  usbhid(E) hid(E) crc32c_intel(E) psmouse(E) ata_piix(E)
ahci(E) pata_jmicron(E) libahci(E) libata(E) r8169(E) mii(E) scsi_mod(E)

Bug#831685: blank screen with nouveau

2016-07-18 Thread VA

Package: libdrm-nouveau2
Version: 2.4.68-1

When I boot, I see the sequence and logs, until at some point screen 
gets blank with backlight off, like on standby mode, so I can't do 
anything apart from rebooting.
If I put "nomodeset" on kernel command line, I can have Xorg running, 
but only with the "vesa" driver.


On freenode#nouveau, I was told to blacklist nouveau in 
/etc/modprobe.d, log "dmesg -w" and try to modprobe nouveau. When I 
modprobed nouveau, the screen went blank so I had to reboot.

However, this was output to the logged dmesg when I did the modprobe:

[  234.725410] [drm] Initialized drm 1.1.0 20060810
[  234.784099] wmi: Mapper loaded
[  234.837482] nouveau :01:00.0: NVIDIA GF104 (0c4100a1)
[  234.837569] pmd_set_huge: Cannot satisfy [mem 0xf400-0xf420] 
with a huge-page mapping due to MTRR override.

[  234.992273] nouveau :01:00.0: bios: version 70.04.13.00.01



Bug#831016: qscintilla text cursor wrong position

2016-07-16 Thread VA
retitle 831016 scintilla text cursor wrong position
reassign 831016 scite 3.6.6-1
thanks

Actually, this bug applies to every Scintilla app, even to SciTE.

Screencast for example when pressing 'z' continuously in SciTE:
https://lut.im/IrTSSr0Lh0/yOFxWNExNwJErOkN.gif



Bug#831016: qscintilla text cursor wrong position

2016-07-13 Thread VA
Sorry, the link was broken, here's the screencast:
https://lut.im/hOTAlzwXHM/HeRoQS3HhxGD2yt4.gif



Bug#831016: qscintilla text cursor wrong position

2016-07-13 Thread VA
Package: python-pyqt5.qsci
Version: 2.9.2+dfsg-3

The text cursor in qscintilla widgets seems to offset on the right
compared to the position it should be, and the offset seems to move.
Here's a little screencast to show the problem:
https://lut.im/35DY1KfuWK/iBqSApFpNCFf1t3O.gif
The text cursor should be right after the character typed, but it's much
more to the right. Situation is even worse when editing text in the
middle of a line.

The issue appears when using "eric", and can also be demonstrated with a
basic PyQt program:


#!/usr/bin/env python
from PyQt5.QtWidgets import QApplication
from PyQt5.Qsci import QsciScintilla
app = QApplication([])
sci = QsciScintilla()
sci.show()
app.exec_()

I'm using XFCE, in case it affects the style.



Bug#828173: glitch in clang-format manpage

2016-06-25 Thread VA
Package: clang-format
Version: 1:3.6-33

When displaying the clang-format(1) manpage, I get the following:

[...]
DESCRIPTION
   ERROR: ld.so: object 'libfakeroot-sysv.so' from LD_PRELOAD cannot
be preloaded (cannot open shared object file): ignored.  OVERVIEW: A
tool to format C/C++/Obj-C code.
[...]

The "ERROR: ld.so..." is verbatim, it should not be in the manpage.



Bug#827417: unmatching types with qscintilla

2016-06-15 Thread VA
Package: python-pyqt5.qsci
Version: 2.9.2+dfsg-1

I just upgraded Qt5 libraries and now functions from PyQt5.Qsci taking a
QString cannot take anything from Python:

from PyQt5.QtWidgets import QApplication
from PyQt5.Qsci import QsciScintilla
app = QApplication([])
s = QsciScintilla()
s.show()
s.setText('foo')
app.exec_()

Raises:

TypeError: setText(self, str): argument 1 has unexpected type 'str'

Using an unicode string equally fails.
Non-Qsci widgets (for example QtWidgets.QLineEdit) seem unaffected by
this issue.

ii  libqt5clucene5:i386 5.6.1-2
ii  libqt5concurrent5:i386  5.6.1+dfsg-2
ii  libqt5core5a:i386   5.6.1+dfsg-2
ii  libqt5dbus5:i3865.6.1+dfsg-2
ii  libqt5designer5:i3865.6.1-2
ii  libqt5designercomponents5:i386  5.6.1-2
ii  libqt5gui5:i386 5.6.1+dfsg-2
ii  libqt5help5:i3865.6.1-2
ii  libqt5keychain0:i3860.5.0-1
ii  libqt5multimedia5:i386  5.6.1-2
ii  libqt5multimedia5-plugins:i386  5.6.1-2
ii  libqt5multimediaquick-p5:i386   5.6.1-2
ii  libqt5multimediawidgets5:i386   5.6.1-2
ii  libqt5network5:i386 5.6.1+dfsg-2
ii  libqt5opengl5:i386  5.6.1+dfsg-2
ii  libqt5printsupport5:i3865.6.1+dfsg-2
ii  libqt5qml5:i386 5.6.1-3
ii  libqt5quick5:i386   5.6.1-3
ii  libqt5quickwidgets5:i3865.6.1-3
ii  libqt5scintilla2-12v5   2.9.2+dfsg-1
ii  libqt5scintilla2-12v5-dbg   2.9.2+dfsg-1
ii  libqt5scintilla2-l10n   2.9.2+dfsg-1
ii  libqt5script5:i386  5.6.1+dfsg-2
ii  libqt5sql5:i386 5.6.1+dfsg-2
ii  libqt5sql5-sqlite:i386  5.6.1+dfsg-2
ii  libqt5svg5:i386 5.6.1-2
ii  libqt5test5:i3865.6.1+dfsg-2
ii  libqt5webkit5:i386  5.6.1+dfsg-3
ii  libqt5widgets5:i386 5.6.1+dfsg-2
ii  libqt5x11extras5:i386   5.6.1-2
ii  libqt5xml5:i386 5.6.1+dfsg-2
ii  phonon4qt5:i386 4:4.9.0-3
ii  phonon4qt5-backend-vlc:i386 0.9.0-1
ii  pyqt5-dev   5.6+dfsg-1
ii  pyqt5-dev-tools 5.6+dfsg-1+b1
ii  pyqt5.qsci-dev  2.9.2+dfsg-1
ii  python-pyqt55.6+dfsg-1+b1
ii  python-pyqt5-dbg5.6+dfsg-1+b1
ii  python-pyqt5.qsci   2.9.2+dfsg-1
ii  python-pyqt5.qsci-dbg   2.9.2+dfsg-1
ii  python-pyqt5.qtmultimedia   5.6+dfsg-1+b1
ii  python-pyqt5.qtsvg  5.6+dfsg-1+b1
ii  python-pyqt5.qtwebkit   5.6+dfsg-1+b1
ii  python3-pyqt5   5.6+dfsg-1+b1
ii  python3-pyqt5.qsci  2.9.2+dfsg-1
ii  qt5-qmake:i386  5.6.1+dfsg-2



  1   2   >