Bug#1019891: mycli: Always crashes at runtime because the module 'sqlglot' is missing

Package: mycli Version: 1.26.1-1 Severity: grave Justification: renders package unusable Dear Maintainer, after upgrading the package `mycli`, the command fails to run. ❯ mycli Traceback (most recent call last): File "/usr/bin/mycli", line 33, in

Bug#941572: gitinspector: --format=html crashes

Package: gitinspector Version: 0.4.4+dfsg-6 Severity: important Dear Maintainer, The command line option that outputs HTML instead of plain text always leads to a crash. Here is the command and its output: % gitinspector --since 2019-09-01 --format=html Traceback (most recent call last): File

Bug#941283: libvte: terminal crashes after a VTE error

Package: libvte-2.91-0 Version: 0.58.0-1 Severity: important File: libvte Dear maintainer, since last week, I've seen several terminal windows crash, with gnome-terminal (official Debian testing) and roxterm (unofficial). This happened on two computers, both using Debian testing and the same

Bug#901793: Info received (Bug#901793: certbot: Fails to renew because of a SSL/TLSv1 error and more)

Here is the explanation: the /etc/hosts files had lines that gave static IPs to the servers that renew certificates: # /etc/hosts 104.85.23.247 acme-v01.api.letsencrypt.org 104.85.23.247 acme-staging.api.letsencrypt.org These point to Akamai server. They were probably proxing letsencrypt

Bug#901793: certbot: Fails to renew because of a SSL/TLSv1 error and more

bugtracker tonight, and update this ticket if there's something on their side. Many thanks again, now I have a faint hope to make sense of all this. -- François Gannaz

Bug#901793: certbot: Fails to renew because of a SSL/TLSv1 error and more

domains do not appear anywhere under /etc/. Sincerly, François Gannaz -- System Information: Debian Release: 9.4 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-6-amd64 (SMP w/1 CPU core) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (cha

Bug#893865: claws-mail: Fetching emails crashes with a X Window System error

Hi. Claws-mail does not crash anymore on my system. I suppose one of its dependencies got updated recently, because my Debian is a frequently updated testing release, but I have no real clue. When it crashed, I had of course restarted the whole system, and it still crashed every time. I

Bug#834527: claws-mail: Deleting a message used to move the cursor to the next message, now it's the previous one

Thanks to both of you for your fast responses. Le 2016-08-17, Paul a écrit : > From this I deduce that you sort with the newest messages at the top > and oldest at the bottom. (Which is not the default, btw.) No, this folder was sorted by threads with the newest

Bug#834527: claws-mail: Deleting a message used to move the cursor to the next message, now it's the previous one

Package: claws-mail Version: 3.14.0-1 Severity: normal Tags: upstream Dear Maintainer, I updated Claws-mail to 3.14, and the behaviour of deletions changed. After selecting a read message whose neighbours had also been read, I pressed 3 times on the "delete" key. The selected message and the two

Bug#809719: roxterm: Most shortcuts are ineffective

Le 2016-01-06, Tony Houghton a écrit : > So for the moment you would prefer the config to be in English, I > think. Even that will be a bit difficult to fix and test, but ideally > there should be some sort of system to allow users to edit the > shortcuts in their own language

Bug#809719: roxterm: Most shortcuts are ineffective

Le 2016-01-06, Tony Houghton <h...@realh.co.uk> a écrit : > On 05/01/16 18:32, François Gannaz wrote: > > Removing the locale with `LANG=C roxterm --separate` does fix it. > > > > And just as you suggested, the problem lies within the matching of > > action nam

Bug#809719: roxterm: Most shortcuts are ineffective

Le 2016-01-05, Tony Houghton a écrit : > > Can you try building replacement debian packages to test? You should > just be able to run debuild -b in the git/source directory. I had to install itstool and po4a. The resulting package had no keyboard shortcuts. The new roxterm

Bug#809719: roxterm: Most shortcuts are ineffective

On my laptop, I compiled roxterm from the source, using the git tag 3.3.1. I wanted to bisect the bug, but shortcuts worked flawlessly with this self-compiled roxterm. I followed the default process, didn't set any configuration option, and simply run `./build/roxterm --separate`. If I copy this

Bug#809719: roxterm: Most shortcuts are ineffective

a écrit : > tags 809719 + unreproducible moreinfo > thanks > > On 03/01/16 11:13, François Gannaz wrote: > > > After updating my distribution, most shortcuts defined in the default > > profile of roxterm are ineffective. The same behaviour occurs on my > > laptop, aft

Bug#809719: roxterm: Most shortcuts are ineffective

Package: roxterm Version: 3.3.1-1 Severity: important Dear Maintainer, After updating my distribution, most shortcuts defined in the default profile of roxterm are ineffective. The same behaviour occurs on my laptop, after updating it to the latest Stretch. The configuration file for shortcuts

Bug#806415: mycli: No way to execute the query

Package: mycli Version: 1.5.2-1 Severity: important Dear Maintainer, Launching `mycli mydb` connects to the DB and I am able to write a SQL query with proper completion. Yet I cannot execute it. Placing `;` at the end of the line is ineffective. Pressing Enter or Ctrl-j has no visible

Bug#779836: mumble: Hibernation floods ~/.xsession-errors with messages

with `systemctl enable root-suspend`, then `systemctl hibernate` will kill Mumble. This workaround is okay, I just need to launch it on resume. -- François Le 2015-03-07, Chris Knadle chris.kna...@coredump.us a écrit : Greetings François. On 03/05/2015 06:27 AM, François Gannaz wrote: Package

Bug#779836: mumble: Hibernation floods ~/.xsession-errors with messages

Package: mumble Version: 1.2.8-2 Severity: important Tags: upstream Dear Maintainer, when running Mumble with an ALSA backend, after hibernation, resuming the system causes Mumble to flood ~/.xsession-errors with ALSA warning messages. In a few minutes, several GB of text are written, until the

Bug#774697: xmobar: Localized dates are disabled

Package: xmobar Severity: wishlist Dear Maintainer, please compile xmobar with the parameter `with_datezone`. Currently the following configuration is not allowed with the Debian package: , Run DateZone %a %F %H:%M fr_FR.utf8 Europe/Paris date 10 Regards -- System Information: Debian

Bug#729503: Backtrace

Dear Maintainer, I compiled Tellico from source (tellico-2.3.8+dfsg.2), with the symbols. Then I run it inside gdb to get a meaningfull backtrace. I just chose a CSV file, waited for 20 seconds with no reaction, then hit Ctrl-C. Tellico gets stuck as soon as I choose a CSV file. The dialog

Bug#711329: chktex: ChkTeX complains about ASC codes of character I don't type

Package: chktex Version: 1.7.2-1 Followup-For: Bug #711329 Dear Maintainer, I suffer from the same problem: chktex warns about a bad apostrophe on each line that contains a ô character. My files are encoded with UTF-8. I suppose UTF-8's ô share a byte with the offending apostrophe in some

Bug#729503: tellico: Import CSV from the menu hangs on loading the file

My bad. Here is the file.ISBN# 978-2-253-15781-6

Bug#729499: tellico: segfaults on each CSV import by CLI (option --ris)

Package: tellico Version: 2.3.8+dfsg.1-2 Severity: normal Dear Maintainer, here is the command I used: tellico --nocrashhandler --nofile --ris t.csv It segfaults almost immediately after displaying the application window. Tested with several CSV files, including some exported from Tellico. Here

Bug#729503: tellico: Import CSV from the menu hangs on loading the file

Package: tellico Version: 2.3.8+dfsg.1-2 Severity: normal Dear Maintainer, I select the entry Import CSV data... from the File menu, then I select a file, then tellico hangs. Tested with several CSV files. One core reports an activity of 100%, and ltrace seems to point out an infinite loop on

Bug#686454: CVE-2011-5129: xchat buffer overflow

Hi, I can't reproduce this bug on my amd64 testing debian, using XFCE and xchat 2.8.8-6. With the proof of concept script referenced in the CVE, I get no crash. Only the following line on STDERR repeated thousands of times: *** XCHAT WARNING: Buffer overflow - shit server! The part of the code

Bug#613602: reminiscence: Crash at menu start with the message Bad CRC for collision data

Package: reminiscence Version: 0.1.9-1 Severity: important Tags: patch On an amd64 debian, I can start the application, but each time I select start in the menu, it crashes with the message: Bad CRC for collision data. This bug is known and fixed in Gentoo, see

Bug#499399: phpmyadmin: Ignores LoginCookieValidity

Hi Thijs Le sam 20 sep 12:49, Thijs Kinkhorst a écrit : Thank you for your report. I looked into this, but could confirm that setting LoginCookieValidity in /etc/phpmyadmin/config.inc.php does indeed cause that information to end up in the appropriate function. Are you sure that your

Bug#499399: phpmyadmin: Ignores LoginCookieValidity

Package: phpmyadmin Version: 4:2.11.8.1-1 Severity: normal phpMyAdmin ignores the configuration parameters that extend the duration of a session. In my /et/phpmyadmin/config.inc.php: $cfg['Servers'][$i]['LoginCookieValidity'] = 72000; // 20 h $cfg['LoginCookieValidity'] = 72000; // 20 h But I