Bug#1080459: Problem remains with 6.10.9-amd64
The kernel (here on testing) was updated today to 6.10.9-amd64 with # ls -l /boot/initrd.img-6.10.9-amd64 -rw-r--r-- 1 root root 8448795 Sep 14 13:36 /boot/initrd.img-6.10.9-amd64 The snd_hda_intel options are still broken requiring # modprobe -r snd_hda_intel # modprobe snd_hda_intel to correct the situation.
Bug#1080459: Comparing initramfs versions
Following my last message comparing the contents of initrd.img-6.10.6-amd64 (failing) with those of initrd.img-6.10.4-amd64 (working) in which I found firmware in 6.10.4 which was not in 6.10.6, I have now looked more carefully, and I can see nothing relevant to sound in there. In passing, here is part of the output of lspci -k : 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06) Subsystem: CLEVO/KAPOK Computer Device 5455 Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel which shows the details of the hardware being controlled by snd-hda_intel. Not sure that any of this helps track down what is wrong.
Bug#1080459: update initramfs did not help. REverting to 6.10.4-amd64 worked
On Wed, Sep 11, 2024 at 06:47:34PM +0200, Marco d'Itri wrote: > On Sep 11, ael wrote: > > > Yes, I did that and no change. I thought that I said I had done that > > under 1). > Then compare the content with lsinitramfs. That was an excellent suggestion! I compared initrd.img-6.10.6-amd64 (failing, size 8.1M) with initrd.img-6.10.4-amd64 (working, size 14M) and it looks as if 6.10.4 contains relevant firmware: usr/lib/firmware/i915.* whereas the 6.10.6 has no such entries. In fact 6.10.4 also has usr/lib/modules/6.10.4-amd64/kernel/drivers/gpu/drm/i915/i915.ko but there is no such entry in initrd.img-6.10.6-amd64 This looks very significant! But why are the entries missing? Is the problem in update-initramfs maybe ??
Bug#1080459: update initramfs did not help. REverting to 6.10.4-amd64 worked
I have some more data points:- 1) I regenerated initrd.img-6.10.6-amd64 using # update-initramfs -uv and rebooted. The problem remains. 2) I reverted to kernel 6.10.4-amd64 ( with its rw-r--r-- 1 root root 14M Aug 24 12:14 initrd.img-6.10.4-amd64) and all was well. Comment: I have only just noticed the large difference in the size of initrd.img-6.10.4-amd64 (14M) and of initrd.img-6.10.6-amd64 (8.1M) I assume, but have not checked, that they use the same compression, if any. Maybe this is a kernel regression of some sort after all? Does this bug need to be re-assigned? Maybe there is some kernal debug parameter that might help with diagnosis?
Bug#1080459: Possible clues
Trawling through journalctl for any clues, I see the following when sound was working properly, ie. the parameters were being loaded properly and sound delivered to the PCH port: kernel: snd_hda_intel :00:1b.0: Unstable LPIB (131072 >= 8192); disabling LPIB delay counting kernel: snd_hda_intel :00:1b.0: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj. Since bdl-pos-adj is itself a parameter, adjusting it would presumably hit the same problem... As I say, above were reported when all was well, but maybe could hint at what is now going wrong.
Bug#1080459: Correction: probably not systemd after all.
Earlier in my attempts to resolve this problem, I have placed a copy of snd-hda.conf under /etc/modules-load.d/ Systemd only expects such files to contain the names of modules, not options, so the error that I have just reported in journalctl is to be expected, and is thus spurious. I have now, of course, deleted sdn-hda.conf from /etc/modules-load.d/ But why in the world doesn't systemd handle options there? But then why in the world do we have systemd?
Bug#1080459: systemd after all? Failed to find module 'options snd_hda_intel...
I have just checked journalctl -b and today I have an entry: systemd-modules-load[352]: Failed to find module 'options snd_hda_intel id=[HDMI,PCH] index=1,0' So as usual maybe this is systemd fault somehow? I find systemd documentation impenetrable, but I suppose that I will have to try and find out what is happening. Obviously it is somehow taking an parameter option as the name of a module.
Bug#1080459: Why are module parameters under /etc/modprobe.d not respected?
On Fri, Sep 06, 2024 at 10:00:20AM +0700, Max Nikulin wrote: > > Have you read log messages reported by journalctl? There is a systemd unit > to load modules, but I expect that this one should be autoloaded in response > to an udev event. Yes, I did try to find anything relevant using journalctl. There were no hits for snd_hda_intel with journalctl -b . In 1080...@bugs.debian.org you will see that that it appears that the options are included properly in the initrd.image which is where the initial kernel is set up, I think before invoking PID 1 = systemd . Somehow those options are not being set properly by snd_hda_intel. Or so it seems. Very odd since it has only just started happening, very likely when the a new initrd.image was generated by an unrelated dpkg trigger was fired. No, I have not (yet) tried to rebuild the initrd.image. I should try that when I have more time. I will copy this to the bug report in case it is useful. ael
Bug#1080459: Why are module parameters under /etc/modprobe.d not respected?
On Thu, Sep 05, 2024 at 08:52:26PM +0200, Franco Martelli wrote: > > I am running debian testing, updated daily. > I'm on stable, so I can't help much > > > > > After yesterday's update, the kernel module snd_hda_intel is being > > loaded with the wrong (default) parameters. > Have you verified this by running the following commands: > > ~$ cat /sys/module/snd_hda_intel/parameters/id > ~$ cat /sys/module/snd_hda_intel/parameters/index Thanks for the suggestion. No I hadn't checked there, and the results are peculiar: it is looking like an obscure bug in the snd_hda_intel driver. The parameter that matters is "index". Checking /sys/module/snd_hda_intel/parameters/index gives 1,0,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1 which is "correct" as if the options have been correctly set. BUT sound is still connected to the HDMI port (index 0,1) !! As usual, manually removing and restoring snd_hda_intel fixes the problem: sound is then connected to PCH (index 1,0): # modprobe -r snd_hda_intel # modprobe snd_hda_intel /sys/module/snd_hda_intel/parameters/index does not change, but is now reflecting the truth. This is now a debian bug against modprobe, although it is probably not modprobe at fault: 1080...@bugs.debian.org As noted there, bug=663436 many years ago had something similar going on with snd_hda_intel. I will copy this reply to that the current bug because it adds significant information. I am wondering whether to contact the maintainer for snd_hda_intel, but I wnatto be sure that I am not overlooking something silly. > > I have /etc/modprobe.d/snd-hda.conf > > which specifies: > > options snd_hda_intel id=[HDMI,PCH] index=1,0 > > > > The details are very unlikely to be important, but if you are > > interested, the snd_hda_intel module defaults to emitting sound on the > > HDMI port instead of the PCH port connected to the speakers and > > headphone. > as workaround try to specify those parameters in the kernel-line in the boot > loader. See: Yes, I know about the kernel command line possibility, but I already have a workaround. Rather I wnat to nail this bug. But thanks for the suggestion. ael
Bug#1080459: kmod: Option parameters under /etc/modprobe.d are not obeyed on system initialization
On Wed, Sep 04, 2024 at 10:33:22PM +0200, Marco d'Itri wrote: > On Sep 04, ael wrote: > > > Or could there be another explanation? Puzzled. > This suspiciously looks like > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=663436 . Indeed. Very odd. I read the alsa list and the authors from Intel often post there. I am tempted to send a note to one of them to ask if they have any ideas. But I don't want to make a fool of myself if there is a trivial explanation somehow...
Bug#1080459: kmod: Option parameters under /etc/modprobe.d are not obeyed on system initialization
Ok,I think that I have now checked the contents of /boot/initrd.img-6.10.6-amd64 and conformed that it has a correct etc/modprobe.d/snd-hda.conf entry. And I know that modprobe operates correctly manually on snd-hda.conf. So I can't see how that initramfs can be a problem, although it is the obvious candidate since it sets up the kernel initially. It was last built on Aug 31 probably as triggered by a dpkg upgrade. It could be that I didn't notice that sound was astray until a day or so later. So I guess there has to be something astray there, but what? Or could there be another explanation? Puzzled.
Bug#1080459: kmod: Option parameters under /etc/modprobe.d are not obeyed on system initialization
On Wed, Sep 04, 2024 at 02:47:03PM +0200, Marco d'Itri wrote: > On Sep 04, ael wrote: > > > # cat /boot/initrd.img-6.10.6-amd64 | cpio -t > These are multiple concatenated archives. Use lsinitramfs. I have now used unmkinitramfs to extract the contents and the correct modprobe.d/snd-hda.conf is there: $ /tmp/image/main/etc/modprobe.d$ less snd-hda.conf ptions snd_hda_intel id=[HDMI,PCH] index=1,0 # Don't need to specify id above, [HDMI,PCH] is the default #See /usr/local/src/linux-stable/Documentation/sound/alsa-configuration.rst #and /usr/local/src/linux-stable/Documentation/sound/hd-audio.rst # modinfo snd_hda_intel, of course... # also /sys/module/snd_hda_intel/ etc. Actually, I did wonder whether it should be called snd_hda_intel.conf ? Why did I ever call it snd_hda.conf I better read the modprobe man page again.
Bug#1080459: kmod: Option parameters under /etc/modprobe.d are not obeyed on system initialization
On Wed, Sep 04, 2024 at 02:47:03PM +0200, Marco d'Itri wrote: > On Sep 04, ael wrote: > > > # cat /boot/initrd.img-6.10.6-amd64 | cpio -t > These are multiple concatenated archives. Use lsinitramfs. Ah. I had missed that. A quick look is showing etc/modprobe.d/snd-hda.conf so you are probably right. I will extract it and check... ael
Bug#1080459: kmod: Option parameters under /etc/modprobe.d are not obeyed on system initialization
On Wed, Sep 04, 2024 at 01:51:19PM +0200, Marco d'Itri wrote: > On Sep 04, ael wrote: > > > Yet manually correcting with > > > > # modprobe -r snd_hda_intel > > # modprobe snd_hda_intel > Unpack your initramfs and check: > - if snd_hda_intel is there (so it is probably loaded in early boot) > - if so, if the module parameter configuration is there too I had already checked that: # cat /boot/initrd.img-6.10.6-amd64 | cpio -t kernel kernel/x86 kernel/x86/microcode kernel/x86/microcode/.enuineIntel.align.0123456789abc kernel/x86/microcode/GenuineIntel.bin 48 blocks so only microcode. I would not expect sound support there. Have I missed something? I see it dated as -rw-r--r-- 1 root root 8.1M Aug 31 10:32 initrd.img-6.10.6-amd64 and I think that sound was working properly after that.
Bug#1080459: kmod: Option parameters under /etc/modprobe.d are not obeyed on system initialization
Package: kmod Version: 33+20240816-2 Severity: normal This is a strange one and maybe is not directly a modprobe problem. I have etc/modprobe.d/snd-hda.conf containing the line options snd_hda_intel id=[HDMI,PCH] index=1,0 It has been working on testing for many years correcting the default sound output from HDMI to PCH (which is connected to speakers etc. But in a very recent testing update (I haven't been able to identify which), the kernel no longer sees this parameter setting which it had been doing properly for years. Yet manually correcting with # modprobe -r snd_hda_intel # modprobe snd_hda_intel which seems to let modprobe itself off the hook. Yet I thought that modprobe was invoked by the kernel when loading modules so I am very confused. Maybe this is related to udev? I see in my /var/log/dpkg triggers-pending udev:amd64 256.5-1 about the time this problem showed up. -- System Information: Debian Release: trixie/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.10.6-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages kmod depends on: ii libc6 2.40-2 ii libkmod233+20240816-2 ii liblzma55.6.2-2 ii libssl3t64 3.3.1-7 ii libzstd11.5.6+dfsg-1 kmod recommends no packages. kmod suggests no packages. -- no debconf information
Bug#1080458: kmod: Option parameters under /etc/modprobe.d are not obeyed on system initialization
Package: kmod Version: 33+20240816-2 Severity: normal This is a strange one and maybe is not directly a modprobe problem. I have etc/modprobe.d/snd-hda.conf containing the line options snd_hda_intel id=[HDMI,PCH] index=1,0 It has been working on testing for many years correcting the default sound output from HDMI to PCH (which is connected to speakers etc. But in a very recent testing update (I haven't been able to identify which), the kernel no longer sees this parameter setting which it had been doing properly for years. Yet manually correcting with # modprobe -r snd_hda_intel # modprobe snd_hda_intel which seems to let modprobe itself off the hook. Yet I thought that modprobe was invoked by the kernel when loading modules so I am very confused. Maybe this is related to udev? I see in my /var/log/dpkg triggers-pending udev:amd64 256.5-1 about the time this problem showed up. -- System Information: Debian Release: trixie/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.10.6-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages kmod depends on: ii libc6 2.40-2 ii libkmod233+20240816-2 ii liblzma55.6.2-2 ii libssl3t64 3.3.1-7 ii libzstd11.5.6+dfsg-1 kmod recommends no packages. kmod suggests no packages. -- no debconf information
Bug#1080388: linux-image-6.10.6-amd64: Module parameters in /etc/modprobe.d/ are not configured
Package: src:linux Version: 6.10.6-1 Severity: normal The module parameters from /etc/modprobe.d/ seem to be ignored as of an update yesterday (2/9/24). In particular, I have /etc/modprobe.d/snd-hda.conf which is: options snd_hda_intel id=[HDMI,PCH] index=1,0 This because alsa otherwise uses the "wrong" HDMI port by default. Above corrects this to use the PCH port for sound. If I manually # modprobe -r snd_hda_intel # modprobe snd_hda_intel corrects the problem. So modprobe is working properly and reads the files under /etc/modprobe.d/. I see that there is now a directory /etc/modules-load.d/ and there is not link there to /etc/modprobe.d. Is this some undocumented change? -- Package-specific info: ** Version: Linux version 6.10.6-amd64 (debian-ker...@lists.debian.org) (x86_64-linux-gnu-gcc-13 (Debian 13.3.0-5) 13.3.0, GNU ld (GNU Binutils for Debian) 2.43.1) #1 SMP PREEMPT_DYNAMIC Debian 6.10.6-1 (2024-08-19) ** Command line: BOOT_IMAGE=/boot/vmlinuz-6.10.6-amd64 root=UUID=5b8060f7-f126-4534-a051-db5d205bd315 ro elevator=deadline ** Not tainted ** Kernel log: Unable to read kernel log; any relevant messages should be attached ** Model information sys_vendor: Notebook product_name: W54_55SU1,SUW product_version: Not Applicable chassis_vendor: Notebook chassis_version: N/A bios_vendor: American Megatrends Inc. bios_version: 4.6.5 board_vendor: Notebook board_name: W54_55SU1,SUW board_version: Not Applicable ** Loaded modules: mptcp_diag xsk_diag tcp_diag udp_diag raw_diag inet_diag unix_diag af_packet_diag netlink_diag snd_hda_intel snd_intel_dspcfg xt_recent ipt_REJECT nf_reject_ipv4 xt_comment xt_hashlimit xt_addrtype xt_mark xt_NFLOG nfnetlink_log xt_LOG nf_log_syslog nf_nat_tftp nf_nat_snmp_basic nf_conntrack_snmp nf_nat_sip nf_nat_pptp nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat_amanda ts_kmp nf_conntrack_amanda nf_conntrack_sane nf_conntrack_tftp nf_conntrack_sip nf_conntrack_pptp nf_conntrack_netlink nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp xt_tcpudp xt_conntrack nft_compat nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables libcrc32c qrtr tun uinput binfmt_misc btusb btrtl btintel btbcm btmtk bluetooth snd_hda_codec_hdmi pktcdvd intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm cpufreq_ondemand iwlmvm crc32_pclmul ghash_clmulni_intel snd_hda_codec_realtek sha512_ssse3 i915 sha256_ssse3 sha1_ssse3 mac80211 snd_hda_codec_generic libarc4 snd_hda_scodec_component aesni_intel iwlwifi drm_buddy crypto_simd snd_intel_sdw_acpi cryptd drm_display_helper snd_hda_codec iTCO_wdt rapl intel_pmc_bxt rtsx_pci_sdmmc iTCO_vendor_support intel_cstate mmc_core mei_hdcp mei_pxp snd_hda_core at24 cec watchdog xhci_pci snd_hwdep intel_uncore cfg80211 xhci_hcd r8169 ehci_pci rc_core snd_pcm ehci_hcd ttm sr_mod realtek cdrom mei_me snd_timer mdio_devres usbcore drm_kms_helper pcspkr libphy mei snd i2c_algo_bit rtsx_pci i2c_i801 video sg i2c_smbus lpc_ich soundcore wmi usb_common rfkill battery button ac joydev nfsd auth_rpcgss nfs_acl lockd grace drm sunrpc msr parport_pc ppdev lp parport configfs efi_pstore nfnetlink ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic sd_mod t10_pi crc64_rocksoft crc64 crc_t10dif crct10dif_generic ahci libahci libata scsi_mod psmouse crct10dif_pclmul evdev crct10dif_common crc32c_intel serio_raw scsi_common ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller [8086:0c04] (rev 06) Subsystem: CLEVO/KAPOK Computer Device [1558:5455] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel modules: ie31200_edac 00:02.0 VGA compatible controller [0300]: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:5455] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: i915 Kernel modules: i915 00:03.0 Audio device [0403]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller [8086:0c0c] (rev 06) Subsystem: CLEVO/KAPOK Computer Device [1558:5455] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_
Bug#1075981: offlineimap3: invalid escape sequence
Package: offlineimap3
Version: 0.0~git20231218.d29a4dc+dfsg-3
Severity: normal
Some python3 packages were updated on testing recently, perhaps
2024-07-08 13:42:27 upgrade python3-all:amd64 3.11.8-1 3.12.2-1
Since then running offlineimap displays warnings like
/usr/lib/python3/dist-packages/imaplib2.py:2472: SyntaxWarning: invalid escape
sequence '\D'
('store', ('1', 'FLAGS', '(\Deleted)')),
/usr/lib/python3/dist-packages/imaplib2.py:2577: SyntaxWarning: invalid escape
sequence '\D'
run('uid', ('STORE', uid[-1], 'FLAGS', '(\Deleted)'))
/usr/lib/python3/dist-packages/imaplib2.py:2591: SyntaxWarning: invalid escape
sequence '\S'
run('store', (num, '-FLAGS', '(\Seen)'), cb=False),
/usr/lib/python3/dist-packages/imaplib2.py:2594: SyntaxWarning: invalid escape
sequence '\D'
run('uid', ('STORE', num, 'FLAGS', '(\Deleted)'))
OfflineIMAP 8.0.0
An extremely quick glance at the code suggested that I would need to
dig a bit to see what is happening.
I could not see any mention of this issue upstream in the git
repository.
-- System Information:
Debian Release: trixie/sid
APT prefers testing-debug
APT policy: (500, 'testing-debug'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.9.7-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages offlineimap3 depends on:
ii ca-certificates 20240203
ii python3 3.12.2-1
ii python3-distro 1.9.0-1
ii python3-gssapi 1.8.3-1
ii python3-imaplib2 2.57-5.2
ii python3-keyring 25.2.1-1
ii python3-portalocker 2.2.1-1
ii python3-rfc6555 0.0~git20190913.1a181b4-3
ii python3-urllib3 1.26.18-2
offlineimap3 recommends no packages.
offlineimap3 suggests no packages.
-- no debconf information
Bug#1068018: Perhaps resolved
This morning the display blanked and flittered shortly after a boot. This appears to be an ongoing problem with xfce4-power-manager version 4.18.3-2. I could not regain control and had to reboot. The immediate problem did not recur on that reboot, and I investigated the settings to see if something had changed. There I discovered that the "Handle display brightness keys" toggle was off. I turned it on, and the brightness keys then worked again. So that would seem to have cleared this bug. However it apears that something changed those settings, perhaps during the upgrade. There is clearly a bug here somewhere, but perhaps not with the plugins. So with some hesitation, I will provisionally close this bug. ael
Bug#1068018: xfce4-power-manager: Brightness control keys no longer work
Package: xfce4-power-manager Version: 4.18.3-2 Severity: normal After a upgrade this morning which did not include this package, the brightness keys on this Clevo laptop no longer work. I tried to install the version from experimental xfce4-power-manager_4.19.1-1_amd64.deb but there were too many problematic dependencies to sort out for a quick test. After the upgrade the only way I could control the screen brightness was using an echo as root to /sys/class/backlight/intel_backlight/brightness -- System Information: Debian Release: trixie/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.6.15-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages xfce4-power-manager depends on: ii libc6 2.37-15 ii libcairo-gobject2 1.18.0-1+b1 ii libcairo2 1.18.0-1+b1 ii libglib2.0-0 2.78.4-1 ii libgtk-3-03.24.41-1 ii libnotify40.8.3-1 ii libpango-1.0-01.52.0+ds-1 ii libpangocairo-1.0-0 1.52.0+ds-1 ii libupower-glib3 1.90.2-8 ii libx11-6 2:1.8.7-1 ii libxext6 2:1.3.4-1+b1 ii libxfce4ui-2-04.18.4-1 ii libxfce4util7 4.18.1-2 ii libxfconf-0-3 4.18.1-1+b1 ii libxrandr22:1.5.4-1 ii upower1.90.2-8 ii xfce4-power-manager-data 4.18.3-2 Versions of packages xfce4-power-manager recommends: ii libpam-systemd [logind] 255.4-1 ii xfce4-power-manager-plugins 4.18.3-2 xfce4-power-manager suggests no packages. -- no debconf information
Bug#1064855: xfce4-power-manager: Display is shutdown despite activity
Package: xfce4-power-manager Version: 4.18.3-2 Severity: normal Since the recent update on testing, several things are broken. 1) The display shuts down ignoring activity rendering machine useless. I have to inactivate the "Display power management" entirely. 2) "Suspend" is now completely broken, and requires a reboot! Echos of Windoze : I am not quite sure if this is also the power manager. Whereas before pressing the "sleep" key reliably just suspended this machine which then resumed properly on another press, now: a) The "sleep" key displays a whole menu of icons. Clicking on the "Suspend" icon does appear to suspend. b) However, on pressing the "sleep" key again does at least reactivate the display. However both the keyboard and mouse are inactive, so the only option is to cycle power. I wish I could offer some diagnostics but where is the documentation? --- -- System Information: Debian Release: trixie/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.6.15-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages xfce4-power-manager depends on: ii libc6 2.37-15 ii libcairo-gobject2 1.18.0-1+b1 ii libcairo2 1.18.0-1+b1 ii libglib2.0-0 2.78.4-1 ii libgtk-3-03.24.41-1 ii libnotify40.8.3-1 ii libpango-1.0-01.51.0+ds-4 ii libpangocairo-1.0-0 1.51.0+ds-4 ii libupower-glib3 1.90.2-8 ii libx11-6 2:1.8.7-1 ii libxext6 2:1.3.4-1+b1 ii libxfce4ui-2-04.18.4-1 ii libxfce4util7 4.18.1-2 ii libxfconf-0-3 4.18.1-1+b1 ii libxrandr22:1.5.2-2+b1 ii upower1.90.2-8 ii xfce4-power-manager-data 4.18.3-2 Versions of packages xfce4-power-manager recommends: ii libpam-systemd [logind] 255.3-2 ii xfce4-power-manager-plugins 4.18.3-2 xfce4-power-manager suggests no packages. -- no debconf information
Bug#1054130: It probably was trivial
It looks as if the URI may have changed. Anyway adding OPT_CONTENT_DISPOSITION to the entry works and the remainder of the list now completes. So a minor bug I guess ael
Bug#1059813: qterminal: /tmp/ storage not released
Package: qterminal Version: 1.2.0-2 Severity: normal After running rsync from an instance of qterminal, the /tmp/ filesystem was full:- # df -h /tmp Filesystem Size Used Avail Use% Mounted on tmpfs 984M 984M 0 100% /tmp However, there were no files shown in /tmp/ using ls -l and lsof /tmp also only showed deleted entries. But df still showed no available space and no new files could be created in /tmp/. /tmp had the usual options: findmnt /tmp gave TARGET SOURCE FSTYPE OPTIONS /tmp tmpfs tmpfs rw,nosuid,nodev,relatime,inode64 Closing the instance of qterminal released the memory: # df -h /tmp Filesystem Size Used Avail Use% Mounted on tmpfs 984M 100K 984M 1% /tmp I do not know what was using the /tmp space, but presumably rsync. Because this system has only about 2GB of RAM, the /tmp directory filled up, although I thought it was supposed to start swapping in some (these?) circumstances. I am filling this against qterminal just because closing it corrected the problem: perhaps some lock/mutex/semaphore was released? I experimented with dd under a qterminal to fill /tmp/ and the deleted the file and that worked properly. The /tmp/ storage was released. -- System Information: Debian Release: 12.0 merged-usr: no Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-16-amd64 (SMP w/1 CPU thread; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled Versions of packages qterminal depends on: ii libc6 2.36-9+deb12u3 ii libqt5core5a 5.15.8+dfsg-11 ii libqt5dbus55.15.8+dfsg-11 ii libqt5gui5 5.15.8+dfsg-11 ii libqt5widgets5 5.15.8+dfsg-11 ii libqt5x11extras5 5.15.8-2 ii libqtermwidget5-1 1.2.0-2 ii libstdc++6 12.2.0-14 ii libx11-6 2:1.8.4-2+deb12u2 Versions of packages qterminal recommends: ii qterminal-l10n 1.2.0-2 qterminal suggests no packages. -- no debconf information
Bug#1054345: usbcore call trace
I now seem to have captured a call trace which may be related: INFO: task kworker/0:0:7395 blocked for more than 120 seconds. [ 1088.815089] Not tainted 6.5.0-3-amd64 #1 Debian 6.5.8-1 [ 1088.815093] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 1088.815095] task:kworker/0:0 state:D stack:0 pid:7395 ppid:2 flags:0x4000 [ 1088.815105] Workqueue: usb_hub_wq hub_event [usbcore] [ 1088.815183] Call Trace: [ 1088.815186] [ 1088.815192] __schedule+0x3df/0xb80 [ 1088.815205] schedule+0x61/0xe0 [ 1088.815211] schedule_timeout+0x98/0x160 [ 1088.815218] ? __pfx_process_timeout+0x10/0x10 [ 1088.815227] wait_for_completion_timeout+0x83/0x170 [ 1088.815236] usb_start_wait_urb+0xa7/0x180 [usbcore] [ 1088.815299] usb_control_msg+0xef/0x150 [usbcore] [ 1088.815359] get_bMaxPacketSize0+0x5f/0xc0 [usbcore] [ 1088.815410] hub_port_init+0x418/0xff0 [usbcore] [ 1088.815465] hub_event+0x1207/0x1c10 [usbcore] [ 1088.815521] ? __schedule+0x3e7/0xb80 [ 1088.815528] process_one_work+0x1e1/0x3f0 [ 1088.815537] worker_thread+0x51/0x390 [ 1088.815542] ? _raw_spin_lock_irqsave+0x27/0x60 [ 1088.815549] ? __pfx_worker_thread+0x10/0x10 [ 1088.815554] kthread+0xf7/0x130 [ 1088.815562] ? __pfx_kthread+0x10/0x10 [ 1088.815570] ret_from_fork+0x34/0x50 [ 1088.815578] ? __pfx_kthread+0x10/0x10 [ 1088.815584] ret_from_fork_asm+0x1b/0x30 [ 1088.815597] [ 1209.646327] INFO: task kworker/0:0:7395 blocked for more than 241 seconds. [ 1209.646341] Not tainted 6.5.0-3-amd64 #1 Debian 6.5.8-1 [ 1209.646345] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 1209.646348] task:kworker/0:0 state:D stack:0 pid:7395 ppid:2 flags:0x4000 [ 1209.646363] Workqueue: usb_hub_wq hub_event [usbcore] [ 1209.646465] Call Trace: [ 1209.646469] [ 1209.646476] __schedule+0x3df/0xb80 [ 1209.646493] schedule+0x61/0xe0 [ 1209.646501] schedule_timeout+0x98/0x160 [ 1209.646509] ? __pfx_process_timeout+0x10/0x10 [ 1209.646520] wait_for_completion_timeout+0x83/0x170 [ 1209.646532] usb_start_wait_urb+0xa7/0x180 [usbcore] [ 1209.646620] usb_control_msg+0xef/0x150 [usbcore] [ 1209.646703] get_bMaxPacketSize0+0x5f/0xc0 [usbcore] [ 1209.646772] hub_port_init+0x418/0xff0 [usbcore] [ 1209.646849] hub_event+0x1207/0x1c10 [usbcore] [ 1209.646925] ? __schedule+0x3e7/0xb80 [ 1209.646935] process_one_work+0x1e1/0x3f0 [ 1209.646946] worker_thread+0x51/0x390 [ 1209.646954] ? _raw_spin_lock_irqsave+0x27/0x60 [ 1209.646962] ? __pfx_worker_thread+0x10/0x10 [ 1209.646969] kthread+0xf7/0x130 [ 1209.646980] ? __pfx_kthread+0x10/0x10 [ 1209.646990] ret_from_fork+0x34/0x50 [ 1209.647002] ? __pfx_kthread+0x10/0x10 [ 1209.647011] ret_from_fork_asm+0x1b/0x30 [ 1209.647028] [ 1330.478037] INFO: task kworker/0:0:7395 blocked for more than 362 seconds. [ 1330.478048] Not tainted 6.5.0-3-amd64 #1 Debian 6.5.8-1 [ 1330.478052] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 1330.478055] task:kworker/0:0 state:D stack:0 pid:7395 ppid:2 flags:0x4000 [ 1330.478066] Workqueue: usb_hub_wq hub_event [usbcore] [ 1330.478149] Call Trace: [ 1330.478152] [ 1330.478158] __schedule+0x3df/0xb80 [ 1330.478172] schedule+0x61/0xe0 [ 1330.478179] schedule_timeout+0x98/0x160 [ 1330.478186] ? __pfx_process_timeout+0x10/0x10 [ 1330.478196] wait_for_completion_timeout+0x83/0x170 [ 1330.478206] usb_start_wait_urb+0xa7/0x180 [usbcore] [ 1330.478276] usb_control_msg+0xef/0x150 [usbcore] [ 1330.478342] get_bMaxPacketSize0+0x5f/0xc0 [usbcore] [ 1330.478397] hub_port_init+0x418/0xff0 [usbcore] [ 1330.478458] hub_event+0x1207/0x1c10 [usbcore] [ 1330.478520] ? __schedule+0x3e7/0xb80 [ 1330.478527] process_one_work+0x1e1/0x3f0 [ 1330.478536] worker_thread+0x51/0x390 [ 1330.478542] ? _raw_spin_lock_irqsave+0x27/0x60 [ 1330.478549] ? __pfx_worker_thread+0x10/0x10 [ 1330.478555] kthread+0xf7/0x130 [ 1330.478564] ? __pfx_kthread+0x10/0x10 [ 1330.478572] ret_from_fork+0x34/0x50 [ 1330.478580] ? __pfx_kthread+0x10/0x10 [ 1330.478588] ret_from_fork_asm+0x1b/0x30 [ 1330.478601] However this was on hotplugging a garmin Etrex 20 which is always very slow and after increasing /sys/module/usbcore/parameters/initial_descriptor_timeout to a very large value (60 !), so it may not be related.
Bug#1055463: Removal of sysvinit
My debian testing installation cannot boot from systemd. I can only use sysvinit under Debian. This seems to be a complete betrayal of the whole linux philosopy. I forget just now why systemd cannot handle that particular box. I will presumably be forced to dump Debian, and probably go to Devuan if this ridiculous proposal goes through. ael
Bug#1054345: Bug presebt on all recent kernel versions
just tested on kernel versions 6.5.0-1-amd64, 6.4.0-4-amd64, 6.4.0-3-amd64 & 6.4.0-2-amd64 and same bug present on all. So it is long standing, and not specific to 6.5.0-2. ael
Bug#1054345: linux-image-6.5.0-2-amd64: Segfault with USB Mass storage
Package: src:linux Version: 6.5.6-1 Severity: normal Dear Maintainer, This is just a very preliminary report with little proper information as yet: perhaps a placeholder which may be useful if other are seein this problem. Since installing 6.5.0-2, when hot plugging USB sticks, I see segfault messages in dmesq such as: --- [ 2538.645420] usb 2-9: new high-speed USB device number 3 using xhci_hcd [ 2538.800696] usb 2-9: New USB device found, idVendor=090c, idProduct=1000, bcdDevice=20.40 [ 2538.800705] usb 2-9: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 2538.800708] usb 2-9: Product: USB 2.0 Flash Drive [ 2538.800711] usb 2-9: Manufacturer: Super Talent Flash [ 2538.800713] usb 2-9: SerialNumber: 13005672 [ 2538.915612] w[15439]: segfault at 4c ip 55bcdea2d09e sp 7ffd80083c00 error 4 in w[55bcdea2c000+3000] likely on CPU 5 (core 1, socket 0) [ 2538.915624] Code: 0f be c3 48 8b 12 f6 44 42 01 40 74 7f 80 fb 20 74 7a 0f be fb 48 83 c5 01 e8 6e f1 ff ff 49 39 ee 0f 84 7d 00 00 00 45 89 e7 <0f> b6 5d 00 84 db 75 ba 45 85 ff 75 65 48 8b 35 76 3f 00 00 bf 2d [ 2539.107372] usb-storage 2-9:1.0: USB Mass Storage device detected [ 2539.107500] scsi host6: usb-storage 2-9:1.0 [ 2539.107576] usbcore: registered new interface driver usb-storage [ 2539.110315] usbcore: registered new interface driver uas [ 2539.194645] w[16015]: segfault at 4c ip 55595990709e sp 7ffd9dc81ca0 error 4 in w[555959906000+3000] likely on CPU 2 (core 2, socket 0) [ 2539.194662] Code: 0f be c3 48 8b 12 f6 44 42 01 40 74 7f 80 fb 20 74 7a 0f be fb 48 83 c5 01 e8 6e f1 ff ff 49 39 ee 0f 84 7d 00 00 00 45 89 e7 <0f> b6 5d 00 84 db 75 ba 45 85 ff 75 65 48 8b 35 76 3f 00 00 bf 2d [ 2540.114671] scsi 6:0:0:0: Direct-Access Flash/SM Super Talent 2.0 2040 PQ: 0 ANSI: 0 CCS [ 2540.115312] sd 6:0:0:0: Attached scsi generic sg2 type 0 [ 2540.116750] sd 6:0:0:0: [sdb] 1014784 512-byte logical blocks: (520 MB/496 MiB) [ 2540.117302] sd 6:0:0:0: [sdb] Write Protect is off [ 2540.117308] sd 6:0:0:0: [sdb] Mode Sense: 43 00 00 00 [ 2540.117876] sd 6:0:0:0: [sdb] No Caching mode page found [ 2540.117883] sd 6:0:0:0: [sdb] Assuming drive cache: write through [ 2540.172366] sdb: sdb1 sdb2 [ 2540.172729] sd 6:0:0:0: [sdb] Attached SCSI removable disk This has happened with at least two different usb sticks of very different vintages. I did run a memtest check on RAM, but this only seem to happen when hotplugging USB sticks, so I am confident that this is a kernel/module bug. When I have more time, I will attempt to turn on debugging options and symbols and more. But I doubt that I am the only one seeing this, and maybe the bug is already fixed upstream. -- Package-specific info: ** Version: Linux version 6.5.0-2-amd64 (debian-ker...@lists.debian.org) (gcc-13 (Debian 13.2.0-5) 13.2.0, GNU ld (GNU Binutils for Debian) 2.41) #1 SMP PREEMPT_DYNAMIC Debian 6.5.6-1 (2023-10-07) ** Command line: BOOT_IMAGE=/boot/vmlinuz-6.5.0-2-amd64 root=UUID=5b8060f7-f126-4534-a051-db5d205bd315 ro elevator=deadline ** Not tainted ** Kernel log: Unable to read kernel log; any relevant messages should be attached ** Model information sys_vendor: Notebook product_name: W54_55SU1,SUW product_version: Not Applicable chassis_vendor: Notebook chassis_version: N/A bios_vendor: American Megatrends Inc. bios_version: 4.6.5 board_vendor: Notebook board_name: W54_55SU1,SUW board_version: Not Applicable ** Loaded modules: uas usb_storage mptcp_diag xsk_diag tcp_diag udp_diag raw_diag inet_diag unix_diag af_packet_diag netlink_diag xt_recent ipt_REJECT nf_reject_ipv4 xt_comment xt_hashlimit xt_addrtype xt_mark xt_NFLOG nfnetlink_log xt_LOG nf_log_syslog nf_nat_tftp nf_nat_snmp_basic nf_conntrack_snmp nf_nat_sip nf_nat_pptp nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat_amanda ts_kmp nf_conntrack_amanda nf_conntrack_sane nf_conntrack_tftp nf_conntrack_sip nf_conntrack_pptp nf_conntrack_netlink nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp xt_tcpudp xt_conntrack nft_compat nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables libcrc32c nfnetlink qrtr tun uinput binfmt_misc btusb btrtl btbcm btintel btmtk bluetooth sha3_generic jitterentropy_rng drbg ansi_cprng ecdh_generic ecc pktcdvd intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel iwlmvm kvm cpufreq_ondemand irqbypass crc32_pclmul mac80211 ghash_clmulni_intel sha512_ssse3 sha512_generic snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi libarc4 aesni_intel snd_hda_intel snd_intel_dspcfg crypto_simd snd_intel_sdw_acpi cryptd snd_hda_codec iwlwifi iTCO_wdt intel_
Bug#1054346: linux-image-6.5.0-2-amd64: Segfault with USB Mass storage
Package: src:linux Version: 6.5.6-1 Severity: normal Dear Maintainer, This is just a very preliminary report with little proper information as yet: perhaps a placeholder which may be useful if other are seein this problem. Since installing 6.5.0-2, when hot plugging USB sticks, I see segfault messages in dmesq such as: --- [ 2538.645420] usb 2-9: new high-speed USB device number 3 using xhci_hcd [ 2538.800696] usb 2-9: New USB device found, idVendor=090c, idProduct=1000, bcdDevice=20.40 [ 2538.800705] usb 2-9: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 2538.800708] usb 2-9: Product: USB 2.0 Flash Drive [ 2538.800711] usb 2-9: Manufacturer: Super Talent Flash [ 2538.800713] usb 2-9: SerialNumber: 13005672 [ 2538.915612] w[15439]: segfault at 4c ip 55bcdea2d09e sp 7ffd80083c00 error 4 in w[55bcdea2c000+3000] likely on CPU 5 (core 1, socket 0) [ 2538.915624] Code: 0f be c3 48 8b 12 f6 44 42 01 40 74 7f 80 fb 20 74 7a 0f be fb 48 83 c5 01 e8 6e f1 ff ff 49 39 ee 0f 84 7d 00 00 00 45 89 e7 <0f> b6 5d 00 84 db 75 ba 45 85 ff 75 65 48 8b 35 76 3f 00 00 bf 2d [ 2539.107372] usb-storage 2-9:1.0: USB Mass Storage device detected [ 2539.107500] scsi host6: usb-storage 2-9:1.0 [ 2539.107576] usbcore: registered new interface driver usb-storage [ 2539.110315] usbcore: registered new interface driver uas [ 2539.194645] w[16015]: segfault at 4c ip 55595990709e sp 7ffd9dc81ca0 error 4 in w[555959906000+3000] likely on CPU 2 (core 2, socket 0) [ 2539.194662] Code: 0f be c3 48 8b 12 f6 44 42 01 40 74 7f 80 fb 20 74 7a 0f be fb 48 83 c5 01 e8 6e f1 ff ff 49 39 ee 0f 84 7d 00 00 00 45 89 e7 <0f> b6 5d 00 84 db 75 ba 45 85 ff 75 65 48 8b 35 76 3f 00 00 bf 2d [ 2540.114671] scsi 6:0:0:0: Direct-Access Flash/SM Super Talent 2.0 2040 PQ: 0 ANSI: 0 CCS [ 2540.115312] sd 6:0:0:0: Attached scsi generic sg2 type 0 [ 2540.116750] sd 6:0:0:0: [sdb] 1014784 512-byte logical blocks: (520 MB/496 MiB) [ 2540.117302] sd 6:0:0:0: [sdb] Write Protect is off [ 2540.117308] sd 6:0:0:0: [sdb] Mode Sense: 43 00 00 00 [ 2540.117876] sd 6:0:0:0: [sdb] No Caching mode page found [ 2540.117883] sd 6:0:0:0: [sdb] Assuming drive cache: write through [ 2540.172366] sdb: sdb1 sdb2 [ 2540.172729] sd 6:0:0:0: [sdb] Attached SCSI removable disk This has happened with at least two different usb sticks of very different vintages. I did run a memtest check on RAM, but this only seem to happen when hotplugging USB sticks, so I am confident that this is a kernel/module bug. When I have more time, I will attempt to turn on debugging options and symbols and more. But I doubt that I am the only one seeing this, and maybe the bug is already fixed upstream. -- Package-specific info: ** Version: Linux version 6.5.0-2-amd64 (debian-ker...@lists.debian.org) (gcc-13 (Debian 13.2.0-5) 13.2.0, GNU ld (GNU Binutils for Debian) 2.41) #1 SMP PREEMPT_DYNAMIC Debian 6.5.6-1 (2023-10-07) ** Command line: BOOT_IMAGE=/boot/vmlinuz-6.5.0-2-amd64 root=UUID=5b8060f7-f126-4534-a051-db5d205bd315 ro elevator=deadline ** Not tainted ** Kernel log: Unable to read kernel log; any relevant messages should be attached ** Model information sys_vendor: Notebook product_name: W54_55SU1,SUW product_version: Not Applicable chassis_vendor: Notebook chassis_version: N/A bios_vendor: American Megatrends Inc. bios_version: 4.6.5 board_vendor: Notebook board_name: W54_55SU1,SUW board_version: Not Applicable ** Loaded modules: uas usb_storage mptcp_diag xsk_diag tcp_diag udp_diag raw_diag inet_diag unix_diag af_packet_diag netlink_diag xt_recent ipt_REJECT nf_reject_ipv4 xt_comment xt_hashlimit xt_addrtype xt_mark xt_NFLOG nfnetlink_log xt_LOG nf_log_syslog nf_nat_tftp nf_nat_snmp_basic nf_conntrack_snmp nf_nat_sip nf_nat_pptp nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat_amanda ts_kmp nf_conntrack_amanda nf_conntrack_sane nf_conntrack_tftp nf_conntrack_sip nf_conntrack_pptp nf_conntrack_netlink nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp xt_tcpudp xt_conntrack nft_compat nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables libcrc32c nfnetlink qrtr tun uinput binfmt_misc btusb btrtl btbcm btintel btmtk bluetooth sha3_generic jitterentropy_rng drbg ansi_cprng ecdh_generic ecc pktcdvd intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel iwlmvm kvm cpufreq_ondemand irqbypass crc32_pclmul mac80211 ghash_clmulni_intel sha512_ssse3 sha512_generic snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi libarc4 aesni_intel snd_hda_intel snd_intel_dspcfg crypto_simd snd_intel_sdw_acpi cryptd snd_hda_codec iwlwifi iTCO_wdt intel_
Bug#1054132: podget: line 2532: ITEM_TITLE: unbound variable
Package: podget Version: 0.9.1-1 Severity: normal I haven't had time to see whether this is something trivial, but just to report that the new podget is giving: /usr/bin/podget: line 2532: ITEM_TITLE: unbound variable In context: Downloading feed index from http://www.thenakedscientists.com/naked_scientists_podcast.xml 2023-10-17 16:59:51 URL:https://www.thenakedscientists.com/naked_scientists_podcast.xml [2448064/2448064] -> "-" [1] /usr/bin/podget: line 2532: ITEM_TITLE: unbound variable serverlist entry is http://www.thenakedscientists.com/naked_scientists_podcast.xml sci n_sci -- System Information: Debian Release: trixie/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-1-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages podget depends on: ii gawk 1:5.2.1-2 ii mawk 1.3.4.20230808-1 ii wget 1.21.4-1+b1 podget recommends no packages. podget suggests no packages. -- no debconf information
Bug#1054131: podget: line 2532: ITEM_TITLE: unbound variable
Package: podget Version: 0.9.1-1 Severity: normal I haven't had time to see whether this is omething trivial, but just to report that the new podget is giving: /usr/bin/podget: line 2532: ITEM_TITLE: unbound variable In context: Downloading feed index from http://www.thenakedscientists.com/naked_scientists_podcast.xml 2023-10-17 16:59:51 URL:https://www.thenakedscientists.com/naked_scientists_podcast.xml [2448064/2448064] -> "-" [1] /usr/bin/podget: line 2532: ITEM_TITLE: unbound variable serverlist entry is http://www.thenakedscientists.com/naked_scientists_podcast.xml sci n_sci -- System Information: Debian Release: trixie/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-1-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages podget depends on: ii gawk 1:5.2.1-2 ii mawk 1.3.4.20230808-1 ii wget 1.21.4-1+b1 podget recommends no packages. podget suggests no packages. -- no debconf information
Bug#1054130: podget: line 2532: ITEM_TITLE: unbound variable
Package: podget Version: 0.9.1-1 Severity: normal I haven't had time to see whether this is omething trivial, but just to report that the new podget is giving: /usr/bin/podget: line 2532: ITEM_TITLE: unbound variable In context: Downloading feed index from http://www.thenakedscientists.com/naked_scientists_podcast.xml 2023-10-17 16:59:51 URL:https://www.thenakedscientists.com/naked_scientists_podcast.xml [2448064/2448064] -> "-" [1] /usr/bin/podget: line 2532: ITEM_TITLE: unbound variable serverlist entry is http://www.thenakedscientists.com/naked_scientists_podcast.xml sci n_sci -- System Information: Debian Release: trixie/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-1-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages podget depends on: ii gawk 1:5.2.1-2 ii mawk 1.3.4.20230808-1 ii wget 1.21.4-1+b1 podget recommends no packages. podget suggests no packages. -- no debconf information
Bug#1051134: AttributeError: 'str' object has no attribute '__suppress_context__'
Package: offlineimap
Version: 7.3.3+dfsg1-1+0.0~git20230519.c9f44ad+dfsg-1
Severity: important
After an upgrade on testing which included python3-pyparsing,
I got this error while trying to download from an
outlook.office365.com imap server using M365-IMAP
(https://github.com/UvA-FNWI/M365-IMAP)
While attempting to sync account 'xx'
urllib.error.HTTPError: HTTP Error 400: Bad Request
===
Traceback:
File "/usr/share/offlineimap3/offlineimap/accounts.py", line 298, in
syncrunner
self.__sync()
File "/usr/share/offlineimap3/offlineimap/accounts.py", line 375, in __sync
remoterepos.getfolders()
File "/usr/share/offlineimap3/offlineimap/repository/IMAP.py", line 681, in
getfolders
imapobj = self.imapserver.acquireconnection()
^^^
File "/usr/share/offlineimap3/offlineimap/imapserver.py", line 593, in
acquireconnection
self.__authn_helper(imapobj)
File "/usr/share/offlineimap3/offlineimap/imapserver.py", line 445, in
__authn_helper
if func(imapobj):
File "/usr/share/offlineimap3/offlineimap/imapserver.py", line 379, in
__authn_xoauth2
imapobj.authenticate('XOAUTH2', self.__xoauth2handler)
File "/usr/lib/python3/dist-packages/imaplib2.py", line 691, in authenticate
typ, dat = self._simple_command('AUTHENTICATE', mechanism.upper())
^^^
File "/usr/lib/python3/dist-packages/imaplib2.py", line 1684, in
_simple_command
return self._command_complete(self._command(name, *args), kw)
^^
File "/usr/lib/python3/dist-packages/imaplib2.py", line 1404, in _command
literal = literator(data, rqb)
File "/usr/lib/python3/dist-packages/imaplib2.py", line 2247, in process
ret = self.mech(self.decode(data))
File "/usr/share/offlineimap3/offlineimap/imapserver.py", line 249, in
__xoauth2handler
response = urllib.request.urlopen(
^^^
File "/usr/lib/python3.11/urllib/request.py", line 216, in urlopen
return opener.open(url, data, timeout)
^^^
File "/usr/lib/python3.11/urllib/request.py", line 525, in open
response = meth(req, response)
^^^
File "/usr/lib/python3.11/urllib/request.py", line 634, in http_response
response = self.parent.error(
^^
File "/usr/lib/python3.11/urllib/request.py", line 563, in error
File "/usr/lib/python3.11/urllib/request.py", line 496, in _call_chain
result = func(*args)
^^^
File "/usr/lib/python3.11/urllib/request.py", line 643, in http_error_default
raise HTTPError(req.full_url, code, msg, hdrs, fp)
ERROR: AttributeError: 'str' object has no attribute '__suppress_context__'
==
I see that M365-IMAP uses urllibparse so this may be an M365-IMAP bug.
I will report that on the gitlab repository.
ael
-- System Information:
Debian Release: trixie/sid
APT prefers testing-debug
APT policy: (500, 'testing-debug'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.4.0-3-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages offlineimap depends on:
ii offlineimap3 0.0~git20230519.c9f44ad+dfsg-1
offlineimap recommends no packages.
offlineimap suggests no packages.
-- no debconf information
Bug#1041508: tex-common: Installation fails if system is missing the set locale
On Sat, Sep 02, 2023 at 06:39:07PM +0100, Samuel Henrique wrote: > > This has happened now, every testing user is getting the following error: > """ > Building format(s) --all. > This may take some time... > fmtutil failed. Output has been stored in > /tmp/fmtutil.isqbK6Rx > Please include this file if you report a bug. Confirmed. I am seeing this on my testing boxes. ael
Bug#1043204: A fix has been posted on the linphone emailing list
This has been answered on the linphone-us...@nongnu.org list. There is an icon which can be clicked to hide the keyboard window. ael
Bug#1043204: linphone-desktop: When DTMF keypad set to show automatically, prevents outgoing calls
Package: linphone-desktop Version: 5.0.2-4 Severity: normal Preferences->Calls and Chat -> show DTMF keyboard automatically I normally have this selected. But then the DTMF keyboard window overlays the main window, so it is impossible to make an outgoing call since that cannot be selected. I will attach a screenshot which shows the problem. The DTMF window overlays the "call out" button, and there seems to be no way to move the keyboard window. ael Information: --System Information: Debian Release: trixie/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.4.0-1-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages linphone-desktop depends on: ii libbctoolbox1 5.2.0-2 ii libbelcard1 5.2.0-2 ii libc6 2.37-6 ii libgcc-s1 13.2.0-1 ii libjsoncpp251.9.5-6 ii liblinphone++11 5.2.0-4 ii liblinphone11 5.2.0-4 ii libmediastreamer13 1:5.2.0+dfsg-3 ii libqt5core5a5.15.10+dfsg-3 ii libqt5dbus5 5.15.10+dfsg-3 ii libqt5gui5 5.15.10+dfsg-3 ii libqt5network5 5.15.10+dfsg-3 ii libqt5qml5 [qtdeclarative-abi-5-15-10] 5.15.10+dfsg-2 ii libqt5quick55.15.10+dfsg-2 ii libqt5quickcontrols2-5 5.15.10+dfsg-2 ii libqt5svg5 5.15.10-2 ii libqt5texttospeech5 5.15.10-2 ii libqt5widgets5 5.15.10+dfsg-3 ii libstdc++6 13.2.0-1 ii linphone-common 5.2.0-4 ii qml-module-qt-labs-platform 5.15.10+dfsg-2 ii qml-module-qtgraphicaleffects 5.15.10-2 ii qml-module-qtquick-controls 5.15.10-2 ii qml-module-qtquick-controls25.15.10+dfsg-2 ii qml-module-qtquick-dialogs 5.15.10-2 ii qml-module-qtquick-layouts 5.15.10+dfsg-2 ii qml-module-qtquick-shapes 5.15.10+dfsg-2 ii qml-module-qtquick-window2 5.15.10+dfsg-2 ii qml-module-qtquick2 5.15.10+dfsg-2 Versions of packages linphone-desktop recommends: pn qt5-gtk2-platformtheme linphone-desktop suggests no packages. -- no debconf information
Bug#1039008: M365-IMAP
I completely forgot to mention that I was/am using M365-IMAP with offlineimap to access the MS servers. However the problem seems to have been transient and has not recurred, so I intend to close this bug in the near future.
Bug#1039008: Perhaps resolved
The connection to outlook.office365.com:993 worked again just now, so this might have been a transient change in MSland. I will leave this bug open for a day or so to see whether the problem resurfaces, but will otherwise close the bug. Sorry for what may be just noise...
Bug#1039008: offlineimap3: User is authenticated but not connected
Package: offlineimap3
Version: 0.0~git20211018.e64c254+dfsg-2
Severity: normal
Trying to connect to outlook.office365.com:993 today I am getting the
quite well known
"'User is authenticated but not connected.'" LIST command error
I have checked that my refresh token in .offlineimaprc file is up to
date, although the error saying that I am authenticated really excluded
that. offlineimap3 is working normally with other imap servers. It is
just the OAUTH connection to the micros$$$ server which seems to be
broken.
I should add that I am using the shortcut oauth2_client_id for thunderbird.
I suppose that just might be relevant.
Here is the dialogue, but it doesn't help much:
-
offlineimap -a somewhere
OfflineIMAP 8.0.0
Licensed under the GNU GPL v2 or any later version (with an OpenSSL exception)
imaplib2 v3.05, Python v3.11.4, OpenSSL 3.0.9 30 May 2023
Account sync somewhere:
*** Processing account somewhere
Establishing connection to outlook.office365.com:993 (somewhereRemote)
ERROR: While attempting to sync account 'somewhere'
LIST command error: BAD [b'User is authenticated but not connected.']. Data:
b'BENK7 LIST "" ""\r\n'
*** Finished account 'somewhere' in 0:00
ERROR: Exceptions occurred during the run!
ERROR: While attempting to sync account 'somewhere'
LIST command error: BAD [b'User is authenticated but not connected.']. Data:
b'BENK7 LIST "" ""\r\n'
Traceback:
File "/usr/share/offlineimap3/offlineimap/accounts.py", line 298, in
syncrunner
self.__sync()
File "/usr/share/offlineimap3/offlineimap/accounts.py", line 374, in __sync
remoterepos.getfolders()
File "/usr/share/offlineimap3/offlineimap/repository/IMAP.py", line 681, in
getfolders
imapobj = self.imapserver.acquireconnection()
^^^
File "/usr/share/offlineimap3/offlineimap/imapserver.py", line 612, in
acquireconnection
listres = imapobj.list(self.reference, '""')[1]
^^
File "/usr/lib/python3/dist-packages/imaplib2.py", line 896, in list
return self._simple_command(name, directory, pattern, **kw)
File "/usr/lib/python3/dist-packages/imaplib2.py", line 1684, in
_simple_command
return self._command_complete(self._command(name, *args), kw)
^^
File "/usr/lib/python3/dist-packages/imaplib2.py", line 1431, in
_command_complete
raise self.error('%s command error: %s %s. Data: %.100s' % (rqb.name, typ,
dat, rqb.data))
I have checked the upstream github for any recent changes that might be
relevant, but found nothing obvious. I looked through the traceback path
in the sources, but could see nothing helpful.
offlineimap3 was working on this connection yesterday. It failed after
my routine "apt (dist)upgrade" this morning, but that is probably a
coincidence. Perhaps MS have changed something? Searching suggests that
their Imap server is buggy as usual with MS...
If this error persists, it may need investigating...
As below, I don't have python3-gssapi installed in case that is
relevant.
-- System Information:
Debian Release: trixie/sid
APT prefers testing-debug
APT policy: (500, 'testing-debug'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.3.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages offlineimap3 depends on:
ii ca-certificates 20230311
ii python3 3.11.2-1+b1
ii python3-distro1.8.0-1
ii python3-imaplib2 2.57-5.2
offlineimap3 recommends no packages.
Versions of packages offlineimap3 suggests:
pn python3-gssapi
-- no debconf information
Bug#1034145: htop: Sort does not work?
On Mon, Apr 10, 2023 at 01:08:42PM +0200, Daniel Lange wrote: > Am 10.04.23 um 13:00 schrieb ael: > > Using F6/sort option, I find that the list is usually sorted by PID > > regardless of whetehr I have chooseb other choices. I usually want a > > sort by CP usage or Memory. > > > > This seems to be a problem with the user interface: ncurses?. Using the -s > > option > > as in > > $ htop -s PERCENT_CPU > > it sorts as expected. > > Can you delete / move away your ~/.config/htoprc (which htop is not running) > and try again? Just another note. The problem happened on at least two different installations running testing. I haven't yet checked whether deleting htoprc on the other box will also fix the problem, but it seems very likely. Thanks again, ael
Bug#1034145: htop: Sort does not work?
On Mon, Apr 10, 2023 at 01:08:42PM +0200, Daniel Lange wrote: > Am 10.04.23 um 13:00 schrieb ael: > > Using F6/sort option, I find that the list is usually sorted by PID > > regardless of whetehr I have chooseb other choices. I usually want a > > sort by CP usage or Memory. > > > > This seems to be a problem with the user interface: ncurses?. Using the -s > > option > > as in > > $ htop -s PERCENT_CPU > > it sorts as expected. > > Can you delete / move away your ~/.config/htoprc (which htop is not running) > and try again? I should have thought of looking there.. It included .tree_sort_key=PERCENT_MEM which was not being respected. I have now deleted it, and htop seems to be sorting properly again. So this seems to have fixed things for now at least. Thanks. ael
Bug#1034145: htop: Sort does not work?
Package: htop Version: 3.2.2-2 Severity: normal I have noticed for some time now that htop does not seem to sort properly. Using F6/sort option, I find that the list is usually sorted by PID regardless of whetehr I have chooseb other choices. I usually want a sort by CP usage or Memory. This seems to be a problem with the user interface: ncurses?. Using the -s option as in $ htop -s PERCENT_CPU it sorts as expected. -- System Information: Debian Release: 12.0 APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-7-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages htop depends on: ii libc6 2.36-8 ii libncursesw6 6.4-2 ii libnl-3-200 3.7.0-0.2+b1 ii libnl-genl-3-200 3.7.0-0.2+b1 ii libtinfo6 6.4-2 htop recommends no packages. Versions of packages htop suggests: ii lm-sensors 1:3.6.0-7.1 ii lsof4.95.0-1 ii strace 6.1-0.1 -- no debconf information
Bug#961508: ifupdown: RTNETLINK answers: File exists
On Fri, Feb 03, 2023 at 03:29:54PM +0100, Santiago Ruano Rincón wrote: > Hi! > > El 31/01/23 a las 14:10, Antoine Beaupré escribió: [..snip..] > > One might argue this should be the default and that ifup should clear > > interfaces before bringing them up, but I'm not familiar enough with > > ifup's intricacies to be certain. > ... > > I suppose this could be safe on a static configuration. > > ael , your interfaces content is not available. > Could you please confirm your eth0 configuration is static? Yes, static. ael
Bug#961508: ifupdown: RTNETLINK answers: File exists
On Tue, Jan 31, 2023 at 02:10:46PM -0500, Antoine Beaupré wrote: > I have a similar problem with ifupdown on my home server which has > accumulated a rather unfortunate pile of crap... > > iface eth0 inet static > # fix RTNETLINK errors on boot see https://bugs.debian.org/961508 > pre-up ip addr flush dev eth0 || true > address 192.168.0.3 > netmask 255.255.255.0 > gateway 192.168.0.1 I have not encountered this for a long time now. It looks as if ipdown now flushes: # ifdown -v eth0 ... ip -4 addr flush dev eth0 ... ael
Bug#1021884: libical3 bug was responsible
Sorry, I should have closed this bug. The problem was caused by a regression in libical3: see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021698 Mind you, korganizer should not have dumped core... ael
Bug#1021938: libical bug
Somehow I was not subcribed to this bug so have only just seen the replies. Yes, I had already suspected libical3, especially after evolution showed the same effect. I confirm that upgrading to libical 3.0.16 "fixes" the problem. Noting that you are the author, I would like to ask for a way of supressing a huge number of alarms triggered when I read in an old calendar.ics to restore kalarm. I have had that before. The ics file contained appointments from at least 5 years ago, many with weekly repeats. That saturated the toolbar and generated hundred of alarm windows which were a huge pain to clear away. I could find no way to get kAlarm to suppress such old alarms. Perhaps I missed it somewhere. I guess this bug should now be closed. Should I do that? ael
Bug#1021698: Seen here
I too seem to be seeing this problem with evolution just as reported here: https://bbs.archlinux.org/viewtopic.php?id=280363 I did try to downgrade but 3.0.14-1+b1 didn't seem to be in the pool at https://ftp.uk.debian.org/debian/pool/main/libi/libical3/ ? I am also sseing problems with reading ics file with kalarm and organizer. Not sure if these are also calling libical3.
Bug#1021938: kalarm: .local/share/kalarm/expired.ics is not a valid iCalendar file
Package: kalarm Version: 4:22.08.0-2 Severity: normal kalarm has been broken on testing since a recent upgrade on testing. It appears to have lost all the events. I suspect that this was upgrade kalarm:amd64 4:22.04.3-1 4:22.08.0-2 (from my /var/log/dpkg... ) It reports that various *.ics files cannot be read. These are files that the previous version wrote. Example from a "gdb kalarm" run: kf.calendarcore: "/home/ael/.local/share/kalarm/expired.ics" is not a valid iCalendar file kf.calendarcore: Error parsing vCalendar file: pop on empty Object Stack at line 106 I have tried various attempts to rewite the file(s), and I no longer remember the details. But I have certainly not touched expired.ics above. Just deleting, say calendar.ics, and allowing kalarm to recreate seems to work so far. It is a major bug if kalarm loses all the future events amd has not kept a backup (so far as I can determine). I think korganizer also accesses some of the same files, and also seems to be working incorrectly. Trying to import from other *.ics files also silently fails. ael -- System Information: Debian Release: bookworm/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.19.0-2-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages kalarm depends on: ii akonadi-server4:22.08.0-2 ii kdepim-runtime4:22.08.0-2 ii kio 5.98.0-1 ii libc6 2.35-3 ii libgcc-s1 12.2.0-3 ii libkf5akonadicontact5 [libkf5akonadicontact5-22.08] 4:22.08.0-2 ii libkf5akonadicore5abi2 [libkf5akonadicore5-22.08] 4:22.08.0-2 ii libkf5akonadimime5 [libkf5akonadimime5-22.08] 4:22.08.0-2 ii libkf5akonadiwidgets5abi1 [libkf5akonadiwidgets5-22.08] 4:22.08.0-2 ii libkf5authcore5 5.98.0-1 ii libkf5calendarcore5abi2 5:5.98.0-1 ii libkf5calendarutils5 [libkf5calendarutils5-22.08] 4:22.08.0-2 ii libkf5codecs5 5.98.0-1 ii libkf5completion5 5.98.0-1 ii libkf5configcore5 5.98.0-1 ii libkf5configgui5 5.98.0-1 ii libkf5configwidgets5 5.98.0-1 ii libkf5contacts5 5:5.98.0-1 ii libkf5coreaddons5 5.98.0-1 ii libkf5crash5 5.98.0-1 ii libkf5dbusaddons5 5.98.0-1 ii libkf5globalaccel-bin 5.98.0-1 ii libkf5globalaccel55.98.0-1 ii libkf5guiaddons5 5.98.0-2 ii libkf5holidays5 1:5.98.0-1 ii libkf5i18n5 5.98.0-1 ii libkf5identitymanagement5 [libkf5identitymanagement5-22.08] 22.08.0-2 ii libkf5identitymanagementwidgets5 [libkf5identitymanagementwi 22.08.0-2 ii libkf5idletime5 5.98.0-1 ii libkf5itemmodels5 5.98.0-1 ii libkf5jobwidgets5 5.98.0-1 ii libkf5kiocore55.98.0-1 ii libkf5kiofilewidgets5 5.98.0-1 ii libkf5kiowidgets5 5.98.0-1 ii libkf5mailtransport5 [libkf5mailtransport5-22.08] 22.08.0-2 ii libkf5mailtransportakonadi5 [libkf5mailtransportakonadi5-22. 22.08.0-2 ii libkf5mime5abi1 [libkf5mime5-22.08] 22.08.0-2 ii libkf5notifications5 5.98.0-1 ii libkf5notifyconfig5 5.98.0-1 ii libkf5pimtextedit5abi2 [libkf5pimtextedit5-22.08] 22.08.0-2 ii libkf5textwidgets55.98.0-1 ii libkf5widgetsaddons5 5.98.0-1 ii libkf5windowsystem5 5.98.0-1 ii libkf5xmlgui5 5.98.0-1 ii libphonon4qt5-4
Bug#1021884: korganizer segfaults when adding new event
Package: korganizer Version: 4:22.08.0-2 Severity: normal Dear Maintainer, Kalarm stopped working on this testing system a few days ago, so I removed it and tried to use the inbuilt support for events and reminders in korganizer. It seem to be hit and miss whether new events are recorded, but now I get a consistent segfault when adding a new event. That new event might overlap the time slot for an existing event. But whatever, a seg fault is always serious I ran under gdb to try to get some diagnostics. gdb.txt session log attached. ael -- System Information: Debian Release: bookworm/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.19.0-2-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages korganizer depends on: ii kdepim-runtime 4:22.08.0-2 ii kio 5.98.0-1 ii libc62.35-3 ii libgcc-s112.2.0-3 ii libkf5akonadicalendar5abi1 [libkf5akonadicalendar5-22.08]4:22.08.0-2 ii libkf5akonadicontact5 [libkf5akonadicontact5-22.08] 4:22.08.0-2 ii libkf5akonadicore5abi2 [libkf5akonadicore5-22.08]4:22.08.0-2 ii libkf5akonadinotes5 [libkf5akonadinotes5-22.08] 4:22.08.0-2 ii libkf5akonadiwidgets5abi1 [libkf5akonadiwidgets5-22.08] 4:22.08.0-2 ii libkf5calendarcore5abi2 5:5.98.0-1 ii libkf5calendarsupport5abi1 [libkf5calendarsupport5-22.08]4:22.08.0-2 ii libkf5calendarutils5 [libkf5calendarutils5-22.08]4:22.08.0-2 ii libkf5completion55.98.0-1 ii libkf5configcore55.98.0-1 ii libkf5configgui5 5.98.0-1 ii libkf5configwidgets5 5.98.0-1 ii libkf5contacts5 5:5.98.0-1 ii libkf5coreaddons55.98.0-1 ii libkf5crash5 5.98.0-1 ii libkf5eventviews5abi1 [libkf5eventviews5-22.08] 4:22.08.0-2 ii libkf5holidays5 1:5.98.0-1 ii libkf5i18n5 5.98.0-1 ii libkf5iconthemes55.98.0-2 ii libkf5identitymanagement5 [libkf5identitymanagement5-22.08] 22.08.0-2 ii libkf5incidenceeditor5abi1 [libkf5incidenceeditor5-22.08]22.08.0-2 ii libkf5itemmodels55.98.0-1 ii libkf5itemviews5 5.98.0-1 ii libkf5jobwidgets55.98.0-1 ii libkf5kcmutils5 5.98.0-1 ii libkf5kiocore5 5.98.0-1 ii libkf5kiogui55.98.0-1 ii libkf5kiowidgets55.98.0-1 ii libkf5kontactinterface5 [libkf5kontactinterface5-22.08] 22.08.0-2 ii libkf5libkdepim5 [libkf5libkdepim5-22.08]4:22.08.0-2 ii libkf5mailtransport5 [libkf5mailtransport5-22.08]22.08.0-2 ii libkf5mime5abi1 [libkf5mime5-22.08] 22.08.0-2 ii libkf5newstuffcore5 5.98.0-1 ii libkf5newstuffwidgets5 5.98.0-1 ii libkf5notifications5 5.98.0-1 ii libkf5parts5 5.98.0-1 ii libkf5pimcommon5abi2 [libkf5pimcommon5-22.08]4:22.08.0-2 ii libkf5pimcommonakonadi5abi1 [libkf5pimcommonakonadi5-22.08] 4:22.08.0-2 ii libkf5widgetsaddons5 5.98.0-1 ii libkf5windowsystem5 5.98.0-1 ii libkf5xmlgui55.98.0-1 ii libkuserfeedbackcore11.2.0-2 ii libkuserfeedbackwidgets1 1.2.0-2 ii libqt5core5a 5.15.4+dfsg-5 ii libqt5dbus5 5.15.4+dfsg-5 ii libqt5gui5 5.15.4+dfsg-5 ii libqt5widgets5 5.15.4+dfsg-5 ii libstdc++6 12.2.0-3 Versions of packages korganizer recommends: pn kale
Bug#1021576: linphone documentation
On Thu, Oct 13, 2022 at 06:13:34PM +0200, Dennis Filder wrote: > > Well, there's your answer right there: Your > ~/.config/linphone/linphonerc still contains a lime= entry in the > [sip] section from earlier releases. Somehow it must have been set to Just a further comment which may also be upstream: linphone seems to lack any documentation on linphonerc and so on. $ apropos linphone gives no results, which is where I would expect to find this sort of thing. And /usr/share/doc/linphone-desktop doesn't seem to have anything relevant. I am not sure about the interaction between the GUI "Preferences" settings and linphonrc. I don't see anything about lime there. Maybe I need to read the source to discover this sort of thing? ael
Bug#1021576: can't have both LIME and LIME X3DH enabled at the same time
On Thu, Oct 13, 2022 at 06:13:34PM +0200, Dennis Filder wrote: > X-Debbugs-Cc: ael > > On Thu, Oct 13, 2022 at 12:42:52PM +0100, ael wrote: > > Another gdb log after installing liblinphone*10-dbgsym*. > > > > one line that may be relevant is > > > > #5 0x77b37798 in bctbx_fatal(char const*, ...) > > (fmt=fmt@entry=0x77bc1670 "You can't have both LIME and LIME X3DH > > enabled at the same time !\nConflicting settings are [sip] lime and [lime] > > lime_server_url") > > at /usr/include/bctoolbox/logging.h:245 > > > > This is another quick and dirty interim report for now... > > Well, there's your answer right there: Your > ~/.config/linphone/linphonerc still contains a lime= entry in the > [sip] section from earlier releases. Somehow it must have been set to > 1 which conflicts with the newer LIME X3DH support that has its own > section. Just delete that line from the [sip] section and you should > be good to go. It is unfortunate that the error message is only > written to the log, not to stderr where it would be helpful. I don't remember editing linphonerc: it must have been many months if not years ago. > I just wonder why it didn't manifest before (assuming you didn't make > any changes to your configuration recently). Have you used the > AppImage version recently? If so it may have touched your > configuration. Definitely not (AppImage), and I made no recent changes to the configuration. Perhaps a while ago I may have modified via the GUI: I don't remember. But I use linphone regularly, and it had been working fine until a few day ago. But thanks so much for the diagnosis. I confirm that it seems to work after deleting the lime=1 entry. It does seem to leave some error handling attention if it dumps core on a simple configuration error. I guess that is for upstream. Thanks again, ael PS. I assume you will close the bug report, or should I do so? > > Regards.
Bug#1021576: can't have both LIME and LIME X3DH enabled at the same time
Another gdb log after installing liblinphone*10-dbgsym*. one line that may be relevant is #5 0x77b37798 in bctbx_fatal(char const*, ...) (fmt=fmt@entry=0x77bc1670 "You can't have both LIME and LIME X3DH enabled at the same time !\nConflicting settings are [sip] lime and [lime] lime_server_url") at /usr/include/bctoolbox/logging.h:245 This is another quick and dirty interim report for now... ael Temporary breakpoint 1 at 0xd9180: file ./linphone-app/src/app/main.cpp, line 30. Starting program: /usr/bin/linphone [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Temporary breakpoint 1, main (argc=1, argv=0x7fffe1b8) at ./linphone-app/src/app/main.cpp:30 30 ./linphone-app/src/app/main.cpp: No such file or directory. Continuing. [New Thread 0x7fffe81ff640 (LWP 13609)] [New Thread 0x7fffe57ff640 (LWP 13610)] [New Thread 0x7fffe4ffe640 (LWP 13611)] [New Thread 0x7fffd7dff640 (LWP 13612)] [New Thread 0x7fffd75fe640 (LWP 13613)] [New Thread 0x7fffd6dfd640 (LWP 13614)] [New Thread 0x7fffd65fc640 (LWP 13615)] [New Thread 0x7fffd5dfb640 (LWP 13616)] [New Thread 0x7fffd55fa640 (LWP 13617)] [New Thread 0x7fffd4df9640 (LWP 13618)] [New Thread 0x7fffa640 (LWP 13619)] [New Thread 0x7fffaf7fe640 (LWP 13620)] [New Thread 0x7fffaeffd640 (LWP 13621)] [New Thread 0x7fffae7fc640 (LWP 13622)] [Thread 0x7fffae7fc640 (LWP 13622) exited] [New Thread 0x7fffae7fc640 (LWP 13623)] Thread 1 "linphone" received signal SIGABRT, Aborted. __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44 44 ./nptl/pthread_kill.c: No such file or directory. #0 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44 #1 0x748895df in __pthread_kill_internal (signo=6, threadid=) at ./nptl/pthread_kill.c:78 #2 0x7483da02 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #3 0x74828469 in __GI_abort () at ./stdlib/abort.c:79 #4 0x77d0ca3f in () at /lib/x86_64-linux-gnu/libbctoolbox.so.1 #5 0x77b37798 in bctbx_fatal(char const*, ...) (fmt=fmt@entry=0x77bc1670 "You can't have both LIME and LIME X3DH enabled at the same time !\nConflicting settings are [sip] lime and [lime] lime_server_url") at /usr/include/bctoolbox/logging.h:245 #6 0x77b4b5c6 in sip_config_read (lc=0x56435fc0) at ./coreapi/linphonecore.c:1645 #7 _linphone_core_read_config(LinphoneCore*) (lc=0x56435fc0) at ./coreapi/linphonecore.c:2336 #8 0x77b4cc6a in linphone_core_init(LinphoneCore*, LinphoneCoreCbs*, LinphoneConfig*, void*, bool_t, void*) (lc=0x56435fc0, cbs=0x0, config=, userdata=, automatically_start=, system_context=) at ./coreapi/linphonecore.c:2924 #9 0x77b4d109 in _linphone_core_new_with_config(_LinphoneCoreCbs*, _LpConfig*, void*, void*, unsigned char, unsigned char) (cbs=0x0, config=0x55f55c60, userdata=0x0, system_context=, automatically_start=, main_core=) at ./coreapi/linphonecore.c:3021 #10 0x779c3a2c in LinphonePrivate::Factory::_createCore(_LinphoneCoreCbs*, char const*, char const*, void*, void*, unsigned char) const (this=, cbs=cbs@entry=0x0, config_path=, factory_config_path=0x55f59e00 "/usr/share/linphone/linphonerc-factory", user_data=user_data@entry=0x0, system_context=0x0, automatically_start=0 '\000') at ./src/factory/factory.cpp:132 #11 0x779c3b29 in LinphonePrivate::Factory::createCore(char const*, char const*, void*) const (this=, config_path=, factory_config_path=, system_context=) at ./src/factory/factory.cpp:179 #12 0x77f3c60d in linphone::Factory::createCore(std::__cxx11::basic_string, std::allocator > const&, std::__cxx11::basic_string, std::allocator > const&, void*) const (this=this@entry=0x562e1f50, configPath="/home/ael/.config/linphone/linphonerc", factoryConfigPath="/usr/share/linphone/linphonerc-factory", systemContext=systemContext@entry=0x0) at ./obj-x86_64-linux-gnu/wrappers/cpp/src/linphone++.cc:4128 #13 0x556fa359 in CoreManager::createLinphoneCore(QString const&) (this=0x562c4b20, configPath=) at ./linphone-app/src/components/core/CoreManager.cpp:234 #14 0x752ec852 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x752dd0bd in QObject::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x76162f4e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x752b1618 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x753085c1 in QTimerInfoList::activateTimers() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x75308e54 in () a
Bug#1021576: Interim gdb log
Sorry. Had no time to look at this today. Meanwhile, I attach the gbd log following the suggestion to run linphone directly under gdb. I suspect that I need some more dbgsym packages installed to be more useful. My previous use of gdb was mainly for checking my own programs with source available etc. Will need to refresh my memory on gdb when I have time. Meanwhile the log attached in case in it useful at this stage. ael Temporary breakpoint 1 at 0xd9180: file ./linphone-app/src/app/main.cpp, line 30. Starting program: /usr/bin/linphone [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Temporary breakpoint 1, main (argc=1, argv=0x7fffe1b8) at ./linphone-app/src/app/main.cpp:30 30 ./linphone-app/src/app/main.cpp: No such file or directory. Continuing. [New Thread 0x7fffe81ff640 (LWP 9424)] [New Thread 0x7fffe57ff640 (LWP 9425)] [New Thread 0x7fffe4ffe640 (LWP 9426)] [New Thread 0x7fffd7dff640 (LWP 9427)] [New Thread 0x7fffd75fe640 (LWP 9428)] [New Thread 0x7fffd6dfd640 (LWP 9429)] [New Thread 0x7fffd65fc640 (LWP 9430)] [New Thread 0x7fffd5dfb640 (LWP 9431)] [New Thread 0x7fffd55fa640 (LWP 9432)] [New Thread 0x7fffd4df9640 (LWP 9433)] [New Thread 0x7fffa640 (LWP 9434)] [New Thread 0x7fffaf7fe640 (LWP 9435)] [New Thread 0x7fffaeffd640 (LWP 9436)] [New Thread 0x7fffae7fc640 (LWP 9437)] [Thread 0x7fffae7fc640 (LWP 9437) exited] [New Thread 0x7fffae7fc640 (LWP 9438)] Thread 1 "linphone" received signal SIGABRT, Aborted. __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44 44 ./nptl/pthread_kill.c: No such file or directory. Continuing. Couldn't get registers: No such process. [Thread 0x7fffae7fc640 (LWP 9438) exited] [Thread 0x7fffaeffd640 (LWP 9436) exited] [Thread 0x7fffaf7fe640 (LWP 9435) exited] [Thread 0x7fffd4df9640 (LWP 9433) exited] [Thread 0x7fffd55fa640 (LWP 9432) exited] [Thread 0x7fffd5dfb640 (LWP 9431) exited] [Thread 0x7fffd65fc640 (LWP 9430) exited] [Thread 0x7fffd6dfd640 (LWP 9429) exited] [Thread 0x7fffd75fe640 (LWP 9428) exited] [Thread 0x7fffd7dff640 (LWP 9427) exited] [Thread 0x7fffe4ffe640 (LWP 9426) exited] [Thread 0x7fffe57ff640 (LWP 9425) exited] [Thread 0x7fffe81ff640 (LWP 9424) exited] [Thread 0x7fffa640 (LWP 9434) exited] Program terminated with signal SIGABRT, Aborted. The program no longer exists. No stack. Temporary breakpoint 1 at 0xd9180: file ./linphone-app/src/app/main.cpp, line 30. Starting program: /usr/bin/linphone [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Temporary breakpoint 1, main (argc=1, argv=0x7fffe1b8) at ./linphone-app/src/app/main.cpp:30 30 ./linphone-app/src/app/main.cpp: No such file or directory. Continuing. [New Thread 0x7fffe81ff640 (LWP 9459)] [New Thread 0x7fffe57ff640 (LWP 9460)] [New Thread 0x7fffe4ffe640 (LWP 9461)] [New Thread 0x7fffd7dff640 (LWP 9462)] [New Thread 0x7fffd75fe640 (LWP 9463)] [New Thread 0x7fffd6dfd640 (LWP 9464)] [New Thread 0x7fffd65fc640 (LWP 9465)] [New Thread 0x7fffd5dfb640 (LWP 9466)] [New Thread 0x7fffd55fa640 (LWP 9467)] [New Thread 0x7fffd4df9640 (LWP 9468)] [New Thread 0x7fffa640 (LWP 9469)] [New Thread 0x7fffa77fe640 (LWP 9470)] [New Thread 0x7fffaf7fe640 (LWP 9471)] [New Thread 0x7fffaeffd640 (LWP 9472)] [Thread 0x7fffaeffd640 (LWP 9472) exited] [New Thread 0x7fffaeffd640 (LWP 9473)] Thread 1 "linphone" received signal SIGABRT, Aborted. __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44 44 ./nptl/pthread_kill.c: No such file or directory. #0 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44 #1 0x748895df in __pthread_kill_internal (signo=6, threadid=) at ./nptl/pthread_kill.c:78 #2 0x7483da02 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #3 0x74828469 in __GI_abort () at ./stdlib/abort.c:79 #4 0x77d0ca3f in () at /lib/x86_64-linux-gnu/libbctoolbox.so.1 #5 0x77b37798 in () at /lib/x86_64-linux-gnu/liblinphone.so.10 #6 0x77b4b5c6 in () at /lib/x86_64-linux-gnu/liblinphone.so.10 #7 0x77b4cc6a in () at /lib/x86_64-linux-gnu/liblinphone.so.10 #8 0x77b4d109 in _linphone_core_new_with_config(_LinphoneCoreCbs*, _LpConfig*, void*, void*, unsigned char, unsigned char) () at /lib/x86_64-linux-gnu/liblinphone.so.10 #9 0x779c3a2c in LinphonePrivate::Factory::_createCore(_LinphoneCoreCbs*, char const*, char const*, void*, void*, unsigned char) const () at /lib/x86_64-linux-gnu/liblinphone.so.10 #10 0x779c3b29 in LinphonePrivate::Factory::createCore(char const*, char const*, void*) const () at /lib/x86_64-linux-gnu/liblinphone.so.10 #11 0x77f3c60d in linphone::Factor
Bug#1021576: Small update
A quick note in haste. Seems that I had ulimit still slightly too small. Trying to get a backtrace on a full core ($ ls -ltrh core -rw--- 1 ael ael 229M Oct 12 11:06 core ) gives: (gdb) bt #0 0x7f623be8957c in ?? () Backtrace stopped: Cannot access memory at address 0x7fff724b0460 ael
Bug#1021576: linphone-desktop: Core dumped: Program terminated with signal SIGABRT, Aborted.
> > Severity: normal > > > > After updating to linphone-common:all 5.0.37-6 and liblinphone10:amd64 > > 5.0.37-6 > > as part of routine testing updates, I find that /usr/bin/linphone from > > linphone-desktop aborts and dumps core as of today. > > > > Reportbug highlighted linphone-desktop_4.3.2-2+b1_amd64.deb > > in unstable. Trying to install that failed on a depedency on > > libqt5qml5_5.15.6+dfsg-2_amd64.deb > > > > Trying to install those broke again on a dependency on > > qtdeclarative-abi-5-15-6 > > which does not appear to exist. > > The qtbase-abi-5-15-6 transition is still on-going[0], so any 5-15-6 > packages should not be installed yet. You must downgrade any you have > installed back to 5-15-4. Thanks for the quick reply. I had already downgraded back to 5-15-4. As noted above I tried to use the unstable packages, and got a partial upgrade as you gathered. I had alraedy cleaned out those packages and confirmed that linphone still crashed. > > > So linphone is broken on testing. > > > > $gdb -c core > > does help much probably because I have set ulimit too small, and right > > now I can't remember where ulimit gets set. I have since increased unlimit, but gdb -c core gives the same lack of information. > > But it ends with > > Core was generated by `linphone'. > > Program terminated with signal SIGABRT, Aborted. > > Did you maybe forget to attach some files before sending this message? > I ask because your bug report is very light on details. You only say > that 5.0.37-6 crashes with SIGABRT, but not what version you used > before and where it crashes. Indeed. I was surprised that gdb gave so little information. I was sure that I had linphone-desktop-dbgsym installed, but somehow it was not present. Now installed, but gdb -c core still not giving anything useful. I may need to install further -dbgsym packages. It does say "failed to read a valid object file image from memory". >You don't provide any stderr output or > logs either. And if you have gdb installed and your APT preferences > are on testing-debug you are clearly skilled enough to install -dbgsym > packages and provide a stack backtrace. I currently have no > information I can work with. Understood. I don't use gdb very often, so will need to refresh my memory. This is a just a quick response untill I have time to explore further. But I emphasize that I just did my routine (normally daily) apt-get upgrade and apt-get dist-upgrade, and that broke linphone. I can't remember when I last used linphone, but it was within a few days. Hope to report much more soon...
Bug#1021561: Twinkle problem resolved
Apologies. The problem was caused by an attempt to update linphone from an unstable package which updated some qt packages. Reverting that cleared the problem with twinkle. SO it lloks as if twinkle will need to be recompiled for the new qt stuff in unstable, but it is currently fine on testing. I will attempt to close this bug. ael
Bug#1021576: linphone-desktop: Core dumped: Program terminated with signal SIGABRT, Aborted.
Package: linphone-desktop Version: 4.3.2-2+b1 Severity: normal After updating to linphone-common:all 5.0.37-6 and liblinphone10:amd64 5.0.37-6 as part of routine testing updates, I find that /usr/bin/linphone from linphone-desktop aborts and dumps core as of today. Reportbug highlighted linphone-desktop_4.3.2-2+b1_amd64.deb in unstable. Trying to install that failed on a depedency on libqt5qml5_5.15.6+dfsg-2_amd64.deb Trying to install those broke again on a dependency on qtdeclarative-abi-5-15-6 which does not appear to exist. So linphone is broken on testing. $gdb -c core does help much probably because I have set ulimit too small, and right now I can't remember where ulimit gets set. But it ends with Core was generated by `linphone'. Program terminated with signal SIGABRT, Aborted. -- System Information: Debian Release: bookworm/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.19.0-2-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages linphone-desktop depends on: ii libbctoolbox1 5.0.37-3 ii libbelcard15.0.37-2 ii libc6 2.35-2 ii libgcc-s1 12.2.0-3 ii liblinphone++105.0.37-6 ii liblinphone10 5.0.37-6 ii libmediastreamer11 1:5.0.37+dfsg-4 ii libqt5core5a 5.15.4+dfsg-5 ii libqt5dbus55.15.4+dfsg-5 ii libqt5gui5 5.15.4+dfsg-5 ii libqt5network5 5.15.4+dfsg-5 iu libqt5qml5 [qtdeclarative-abi-5-15-6] 5.15.6+dfsg-2 ii libqt5quick5 5.15.4+dfsg-4 ii libqt5quickcontrols2-5 5.15.4+dfsg-2 ii libqt5svg5 5.15.4-2 ii libqt5texttospeech55.15.4-2 ii libqt5widgets5 5.15.4+dfsg-5 ii libstdc++6 12.2.0-3 ii linphone-common5.0.37-6 ii qml-module-qt-labs-platform5.15.4+dfsg-2 ii qml-module-qtgraphicaleffects 5.15.4-2 ii qml-module-qtquick-controls5.15.4-2 ii qml-module-qtquick-controls2 5.15.4+dfsg-2 ii qml-module-qtquick-dialogs 5.15.4-2 ii qml-module-qtquick-layouts 5.15.4+dfsg-4 ii qml-module-qtquick-shapes 5.15.4+dfsg-4 ii qml-module-qtquick-window2 5.15.4+dfsg-4 ii qml-module-qtquick25.15.4+dfsg-4 Versions of packages linphone-desktop recommends: pn qt5-gtk2-platformtheme linphone-desktop suggests no packages. -- no debconf information
Bug#1021561: twinkle: Cannot mix incompatible Qt library (5.15.6) with this library (5.15.4)
Package: twinkle Version: 1:1.10.2+dfsg-1 Severity: normal Both linphone and twikle are broken on testing. Twinkle reports Cannot mix incompatible Qt library (5.15.6) with this library (5.15.4) so it looks as if QT is broken on testing. -- System Information: Debian Release: bookworm/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.19.0-2-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages twinkle depends on: ii libasound2 1.2.7.2-1 ii libc62.35-2 ii libccrtp2v5 2.0.9-2.3 ii libgcc-s112.2.0-3 ii libgsm1 1.0.22-1 ii libmagic11:5.41-4 ii libqt5core5a 5.15.4+dfsg-5 ii libqt5gui5 5.15.4+dfsg-5 iu libqt5qml5 5.15.6+dfsg-2 ii libqt5quick5 5.15.4+dfsg-4 ii libqt5widgets5 5.15.4+dfsg-5 ii libreadline8 8.2-1 ii libsndfile1 1.1.0-3 ii libspeex11.2.1-1 ii libspeexdsp1 1.2.1-1 ii libstdc++6 12.2.0-3 ii libucommon8 7.0.1-0.1 ii libxml2 2.9.14+dfsg-1+b1 ii qml-module-qtquick2 5.15.4+dfsg-4 ii twinkle-common 1:1.10.2+dfsg-1 twinkle recommends no packages. twinkle suggests no packages. -- no debconf information
Bug#997933: offlineimap3: 'int' object is not subscriptable when connecting to outlook.office365.com
Package: offlineimap3 Version: 0.0~git20211018.e64c254+dfsg-1 Severity: serious Justification: 4 In the last week or so, offlineimap is usually (but not always) failing to connect to outlook.office365.com reporting: $ offlineimap -a x OfflineIMAP 8.0.0 Licensed under the GNU GPL v2 or any later version (with an OpenSSL exception) imaplib2 v3.05, Python v3.9.7, OpenSSL 1.1.1l 24 Aug 2021 Account sync x: *** Processing account x Establishing connection to outlook.office365.com:993 (oRemote) ERROR: While attempting to sync account 'x' 'int' object is not subscriptable *** Finished account 'x' in 0:00 ERROR: Exceptions occurred during the run! ERROR: While attempting to sync account 'x' 'int' object is not subscriptable Traceback: File "/usr/share/offlineimap3/offlineimap/accounts.py", line 298, in syncrunner self.__sync() File "/usr/share/offlineimap3/offlineimap/accounts.py", line 374, in __sync remoterepos.getfolders() File "/usr/share/offlineimap3/offlineimap/repository/IMAP.py", line 681, in getfolders imapobj = self.imapserver.acquireconnection() File "/usr/share/offlineimap3/offlineimap/imapserver.py", line 683, in acquireconnection e.args[0][:35] == 'IMAP4 protocol error: socket error:': - I suspect perhaps a change in some python package? When this first showed up, it was nondeterministic: it looked like some sort of time out of, presumably some state somewhere. But now it seems to be pretty solid. Of course, MS maybe have messed up their IMAP server. -- System Information: Debian Release: bookworm/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.14.0-2-amd64 (SMP w/8 CPU threads) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages offlineimap3 depends on: ii ca-certificates 20210119 ii python3 3.9.2-3 ii python3-distro1.6.0-2 ii python3-imaplib2 2.57-5.2 offlineimap3 recommends no packages. Versions of packages offlineimap3 suggests: pn python3-gssapi -- no debconf information Here is the relevant part of offlineimap.rc: --- [general] accounts = one,two,three,... #fsync false to conserve flash write cycles fsync = false [Account x] localrepository = sLocal remoterepository = sRemote [Repository sRemote] type = IMAP ssl = yes ssl_version = tls1 sslcacertfile = /etc/ssl/certs/ca-certificates.crt remoteprt = 993 remotehost = outlook.office365.com remoteuser = xx@somewhere.something folderfilter = lambda foldername: foldername in ['INBOX', 'Junk Email', 'Sent Items'] [Repository sLocal] type = Maildir localfolders = ~/Mail/x sep = / # Next again to help flash conservation & because noatime set restoreatime = yes -
Bug#993350: [sane-devel] Epson Perfection1640: Operation not supported
On Tue, Oct 05, 2021 at 03:26:22PM +0200, Wolfram Sang wrote: > > > I tried this but I still have xsane Version: 0.999-12 so there was no > > change. I couldn't find a newer version of xsane, even in Ubuntu. > > Indeed in the Ubuntu pool that I checked, the xsane directory was empty. > > You need a newer version of libsane than debian testing. Probably > packages "libsane-common" and friends. The xsane version can stay the > same. But a quick look tells me that Ubuntu repos won't be useful for > you because they also don't have the patch you need. Maybe your best bet > is to push Debian maintainers to include the patch I mentioned. They > should have it anyhow. Fedora already includes it. Well, I have been copying most of this thread to a debian bug, so I trust the Debian maintainer will pick it up soon. I once knew a little about packaging and built a few deb packages for my own purposes, so I could probably manage to get this working with enough time. Needless to say, I don't have that time now :-) As I needed a working scanner immediately, I have now scanned my documents using an older version of xsane which was already installed on devuan live image. Thanks for the help. I will keep watching this thread. ael
Bug#993350: [sane-devel] Epson Perfection1640: Operation not supported
On Tue, Oct 05, 2021 at 10:27:58AM +0100, ael via sane-devel wrote: > On Mon, Oct 04, 2021 at 08:39:58PM +0100, ael via sane-devel wrote: > > On Mon, Oct 04, 2021 at 05:32:29PM +0200, Wolfram Sang wrote: > > > There is a PPA with the latest development version here if you want to > > > test right away: > > > > > > https://launchpad.net/~sane-project/+archive/ubuntu/sane-git > > Meanwhile, I will get my scanner out and retest: despite the broken > packages, I think there is a chance that it might now work. > I tried this but I still have xsane Version: 0.999-12 so there was no change. I couldn't find a newer version of xsane, even in Ubuntu. Indeed in the Ubuntu pool that I checked, the xsane directory was empty. xscanimage also seg faulted as before. ael
Bug#993350: [sane-devel] Epson Perfection1640: Operation not supported
On Mon, Oct 04, 2021 at 08:39:58PM +0100, ael via sane-devel wrote: > On Mon, Oct 04, 2021 at 05:32:29PM +0200, Wolfram Sang wrote: > > There is a PPA with the latest development version here if you want to > > test right away: > > > > https://launchpad.net/~sane-project/+archive/ubuntu/sane-git > > > > I have tried using the ubuntu debs, but hit > dpkg: dependency problems prevent configuration of sane-utils: > sane-utils depends on libjpeg8 (>= 8c); however: > Package libjpeg8 is not installed. Just to report further: I tried to install the ubuntu libjpeg8 libjpeg8_8c-2ubuntu8_amd64.deb, but then hit further problems: libjpeg8:amd64 depends on libjpeg-turbo8 I then added libjpeg-turbo8_2.0.6-0ubuntu2_amd64.deb but then: error processing archive libjpeg-turbo8_2.0.6-0ubuntu2_amd64.deb (--install): conflicting packages - not installing libjpeg-turbo8:amd64 It seems that debian has instead: libturbojpeg0 So Ubuntu and debian seem to be using different package names. I could probably sort all this out if I had the time to refresh my memory about packaging. But is does not seem to be straight forward to use the Ubuntu packages in Debian. Meanwhile, I will get my scanner out and retest: despite the broken packages, I think there is a chance that it might now work. ael
Bug#993350: [sane-devel] Epson Perfection1640: Operation not supported
On Mon, Oct 04, 2021 at 05:32:29PM +0200, Wolfram Sang wrote: > There is a PPA with the latest development version here if you want to > test right away: > > https://launchpad.net/~sane-project/+archive/ubuntu/sane-git > I have tried using the ubuntu debs, but hit dpkg: dependency problems prevent configuration of sane-utils: sane-utils depends on libjpeg8 (>= 8c); however: Package libjpeg8 is not installed. libjpeg8 doesn't seem to be in debian... ael
Bug#993350: The new 1.0.33 version is needed
I have have contacted upstream and it seems that debian is not upto date with the latest version. Wolfram Sang said that ... "the new 1.0.33 version which is already in code-freeze state. Or the current version needs to include this patch from upstream: https://gitlab.com/sane-project/backends/-/commit/580c278dcafe4159213406b4307ee8598fe08f e7 " This is on the sane-devel list: sane-de...@alioth-lists.debian.net ael
Bug#993350: Also broken on Perfection 1640
I too am seeing this problem on my Perfection 1640SU. Pressing the acquire preview gives the message "Failed to start scanner: Operation not supported". This on Debian testing. Now on the Advanced Options window, there is an Autofocus button. I have deactivated it. I am pretty certain that this model has no autofocus mechanism. There is also a Focus position bar. Again, I don't think this model has any way to implement that. So I suspect that the "Operation not supported" is to adjust the focus. The old xsane (I probably mean the epson backend) just showed two settings: "Focus on glass" or "Focus on film". That is from memory, but something close to that. SO perhaps this old model had just a binary switch for two focus positions, and the epson backend has been broken by assuming that this model has more focus facilities. So far this is pure speculation on my part. ael
Bug#994719: linux-image-5.10.0-8-amd64: Kernel oops
Package: src:linux Version: 5.10.46-4 Severity: important Kernal oops: [ 4895.690309] FAT-fs (sdd1): Directory bread(block 23326848) failed [ 4895.690312] FAT-fs (sdd1): Directory bread(block 23326849) failed [ 4895.690314] FAT-fs (sdd1): Directory bread(block 23326850) failed [ 4895.690315] FAT-fs (sdd1): Directory bread(block 23326851) failed [ 4895.690317] FAT-fs (sdd1): Directory bread(block 23326852) failed [ 4895.690319] FAT-fs (sdd1): Directory bread(block 23326853) failed [ 4895.690320] FAT-fs (sdd1): Directory bread(block 23326854) failed [ 4895.690322] FAT-fs (sdd1): Directory bread(block 23326855) failed [ 4895.690324] FAT-fs (sdd1): Directory bread(block 23326856) failed [ 4895.690325] FAT-fs (sdd1): Directory bread(block 23326857) failed [ 4895.690530] FAT-fs (sdd1): FAT read failed (blocknr 4243) [ 4895.690532] [ cut here ] [ 4895.690533] bdi-(unknown) not registered [ 4895.690544] WARNING: CPU: 5 PID: 9048 at fs/fs-writeback.c:2326 __mark_inode_dirty+0 x17a/0x340 [ 4895.690545] Modules linked in: nls_ascii nls_cp437 vfat fat xt_recent ipt_REJECT nf_ reject_ipv4 xt_comment xt_hashlimit xt_addrtype xt_mark xt_CT nfnetlink_log xt_NFLOG nf _log_ipv4 nf_log_common xt_LOG nf_nat_tftp nf_nat_snmp_basic nf_conntrack_snmp nf_nat_s ip nf_nat_pptp nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat_amanda ts_kmp nf_conntrack_aman da nf_conntrack_sane nf_conntrack_tftp nf_conntrack_sip nf_conntrack_pptp nf_conntrack_ netlink nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_irc nf_conntrack_h3 23 nf_conntrack_ftp nft_counter xt_tcpudp xt_conntrack nft_compat nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables libcrc32c nfnetlink essiv authenc dm_crypt dm_mod uas usb_storage uinput binfmt_misc btusb btrtl btbcm btintel bluetooth uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 jitterentropy_rng videobuf2_ common drbg videodev ansi_cprng mc ecdh_generic ecc intel_rapl_msr intel_rapl_common x8 6_pkg_temp_thermal cpufreq_ondemand [ 4895.690601] intel_powerclamp coretemp snd_hda_codec_realtek kvm_intel snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi iwlmvm pktcdvd kvm snd_hda_intel snd_intel_dspcfg irqbypass crc32_pclmul soundwire_intel soundwire_generic_allocation ghash_clmulni_intel mac80211 snd_soc_core aesni_intel snd_compress soundwire_cadence libaes iTCO_wdt intel_pmc_bxt crypto_simd libarc4 snd_hda_codec iTCO_vendor_support rtsx_pci_sdmmc cryptd iwlwifi watchdog glue_helper mmc_core snd_hda_core mei_hdcp at24 xhci_pci snd_hwdep rapl ehci_pci xhci_hcd soundwire_bus r8169 ehci_hcd intel_cstate snd_pcm cfg80211 realtek sr_mod mdio_devres snd_timer intel_uncore cdrom joydev mei_me pcspkr usbcore libphy sg i2c_i801 snd rtsx_pci mei rfkill lpc_ich soundcore i2c_smbus usb_common wmi battery ac button msr parport_pc nfsd ppdev lp parport auth_rpcgss nfs_acl lockd fuse grace configfs sunrpc ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic sd_mod t10_pi crc_t10dif crct10dif_generic i915 [ 4895.690676] i2c_algo_bit ahci drm_kms_helper libahci libata cec drm scsi_mod psmouse crct10dif_pclmul crct10dif_common crc32c_intel evdev serio_raw video [ 4895.690697] CPU: 5 PID: 9048 Comm: AWT-EventQueue- Not tainted 5.10.0-8-amd64 #1 Debian 5.10.46-4 [ 4895.690699] Hardware name: Notebook W54_55SU1,SUW/W54_55SU1,SUW, BIOS 4.6.5 05/29/2014 [ 4895.690704] RIP: 0010:__mark_inode_dirty+0x17a/0x340 [ 4895.690707] Code: ff ff 48 8b 38 48 89 c5 f6 47 44 01 74 1e 48 8b 40 08 a8 01 75 16 e8 55 90 f3 ff 48 c7 c7 b8 8b 0f a4 48 89 c6 e8 29 3b 58 00 <0f> 0b 48 8b 05 1d 14 31 01 49 89 86 c8 00 00 00 45 85 ff 74 0e 48 [ 4895.690709] RSP: 0018:a672830a78a0 EFLAGS: 00010286 [ 4895.690712] RAX: RBX: 0001 RCX: 96ed0fb58a08 [ 4895.690713] RDX: ffd8 RSI: 0027 RDI: 96ed0fb58a00 [ 4895.690714] RBP: 96eae2f5c460 R08: R09: a672830a76c0 [ 4895.690715] R10: a672830a76b8 R11: a46cb3e8 R12: 96ea874c66d8 [ 4895.690716] R13: R14: 96ea874c6650 R15: [ 4895.690718] FS: 7fe7da562700() GS:96ed0fb4() knlGS: [ 4895.690719] CS: 0010 DS: ES: CR0: 80050033 [ 4895.690720] CR2: 55790a2de0f8 CR3: 00015ccec006 CR4: 001706e0 [ 4895.690722] Call Trace: [ 4895.690732] fat_alloc_clusters+0x487/0x4e0 [fat] [ 4895.690737] ? xas_load+0x5/0x70 [ 4895.690740] ? submit_bio_noacct+0x2c/0x420 [ 4895.690744] fat_add_new_entries+0x92/0x2f0 [fat] [ 4895.690748] ? _cond_resched+0x16/0x40 [ 4895.690750] ? ___ratelimit+0x90/0xe0 [ 4895.690753] ? fat__get_entry+0x8d/0x230 [fat] [ 4895.690757] fat_add_entries+0x49d/0x570 [fat] [ 4895.690760] ? vfat_add_entry+0x9c2/0xdf0 [vfat] [ 4895.690762] vfat_add_entry+0x9dd/0xdf0 [vfat] [ 4895.690768] ? __d_lookup_done+0x76/0xe0 [ 4895.690770] vfat_create+0x6c/0x170 [vfat] [ 4895.69077
Bug#991559: geeqie: Cannot select zoom-to-fit as default
Package: geeqie Version: 1:1.6-9 Severity: normal The current geeqie no longer seems to default to "zoom-to-fit" which is rather inconvenient. I have looked through the "Preferences" and could find no way to modify this. Perhaps I missed it? However, I could edit ~/.config/geeqie/geeqierc.xml directly: I changed image.zoom_mode from "0" to "1" (guess) and that worked. So at the least, the Preferences dialogue needs correcting. Not sure this package is still maintained gevin the ago of outstanding bugs? --- -- System Information: Debian Release: 11.0 APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-8-amd64 (SMP w/8 CPU threads) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages geeqie depends on: ii geeqie-common1:1.6-9 ii libc62.31-13 ii libcairo21.16.0-5 ii libchamplain-0.12-0 0.12.20-1 ii libchamplain-gtk-0.12-0 0.12.20-1 ii libclutter-1.0-0 1.26.4+dfsg-2 ii libclutter-gtk-1.0-0 1.8.4-4 ii libcogl201.22.8-2 ii libdjvulibre21 3.5.28-2 ii libexiv2-27 0.27.3-3 ii libffmpegthumbnailer4v5 2.1.1-0.2+b1 ii libgcc-s110.2.1-6 ii libgdk-pixbuf-2.0-0 2.42.2+dfsg-1 ii libglib2.0-0 2.66.8-1 ii libgtk-3-0 3.24.24-4 ii libheif1 1.11.0-1 ii libjpeg62-turbo 1:2.0.6-4 ii liblcms2-2 2.12~rc1-2 ii liblirc-client0 0.10.1-6.3 ii liblua5.1-0 5.1.5-8.1+b3 ii libopenjp2-7 2.4.0-3 ii libpango-1.0-0 1.46.2-3 ii libpangocairo-1.0-0 1.46.2-3 ii libpoppler-glib8 20.09.0-3.1 ii libstdc++6 10.2.1-6 ii libtiff5 4.2.0-1 ii libwebp6 0.6.1-2.1 ii sensible-utils 0.0.14 Versions of packages geeqie recommends: ii cups-bsd [lpr] 2.3.3op2-3+deb11u1 ii exiftran 2.10-4 ii exiv20.27.3-3 ii imagemagick 8:6.9.11.60+dfsg-1.3 ii imagemagick-6.q16 [imagemagick] 8:6.9.11.60+dfsg-1.3 ii librsvg2-common 2.50.3+dfsg-1 ii zenity 3.32.0-6 Versions of packages geeqie suggests: pn geeqie-dbg ii gimp 2.10.22-4 ii libjpeg-turbo-progs [libjpeg-progs] 1:2.0.6-4 pn xpaint -- no debconf information
Bug#904098: Timidity is blocking alsa plughw
After a little further investigation, I found that timidity was being started by systemd by falling back to /etc/rc*.d/ SYSV files. Note that I had removed timidity-daemon, but I did not purge the package. As a result, it seems that timidity was being started: # systemctl list-units "timidity*" UNIT LOAD ACTIVE SUB DESCRIPTION timidity.service loaded active running LSB: start and stop timidity So if you have had timidity-daemon installed at some point, then be sure to purge the package. I see that timidity "Suggests" timidity-daemon, although it is not needed in desktop installations. I imagine that it how it got installed here some years ago. The other issue is why timidity is locking out other sound applications from using plughw:. Perhaps that would be reasonable when timidity is actively playing sound, although I think most sound aplications are not so antisocial. I have not looked at that aspect so far.
Bug#979180: Timidity is the cause
After further investigation, it appears that the root cause is timidity blocking access on plughw: . The timidity package is known to cause such problems: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904098 I was completely unaware that timidity was running on my system, but then I am still running systemd :-( I continue to investigate...
Bug#904098: Timidity is blocking alsa plughw
I have also found that timidity is blocking access to the alsa plughw device. This may perhaps be the underlying problem with pulseaudio although as I only use alsa I cannot comment on that. Trying to open the alsa device returns a "Device or resource busy" error. It is possible that an asoundrc configuration https://www.alsa-project.org/wiki/Asoundrc might help.
Bug#979139: Answering calls
After my last post there was a reply on the linphone list. I tried again in a completely new session, and this time a small window popped up in the bottom right hand side of the screen. I find it hard to believe that I missed that before, but perhaps I was concentrating on the main linphone window and somehow escaped my notice. ael
Bug#979139: linphone-desktop: Icons not shown
I have just returned to testing linphone (after getting twinkle to work as well), and I have hit another problem. I can make outgoing calls, but I cannot answer incoming calls. Could that be another missing icon? When I make an incoming test tool, linphone plays the ringtone, but I can't see any change in the GUI, nor any way to answer the call. I have just posted a message to the linphone mailing list linphone-us...@nongnu.org
Bug#979180: ALSA now working
I now have twinkle working again with ALSA.
A quick-and-dirty patch is to change "plughw:0,0" to "default:" in
audio_device.cpp:-
$ diff -u audio_device.cpp audio_device.cpp_original
--- audio_device.cpp2021-01-07 22:35:15.862448988 +
+++ audio_device.cpp_original 2021-01-07 21:57:51.119873744 +
@@ -887,12 +887,9 @@
if ((err = snd_ctl_pcm_info(handle, pcminfo)) <
0) continue;
t_audio_device dev;
- /*dev.device = string("plughw:") +
int2str(card) +
-*/
- dev.device = string("default:");
- /* + int2str(card) +
+ //dev.device = string("plughw:") +
int2str(card) +
+ dev.device = string("default:") + int2str(card)
+
string(",") + int2str(device);
- */
dev.name = string(card_name) + " (";
dev.name += snd_pcm_info_get_name(pcminfo);
dev.name += ")";
The previous audio device is also stored in ~/.twinkle/twinkle.sys, so
it is very likely that will need editing as well. No doubt that can
be done from the twinkle gui as well, but I have not explored that as
well.
Bug#979180: AlSA problems remain
Sadly the new twinkle still has ALSA problems. I will try to investigate.
Bug#979180: Adding ZRTP
Although the rtp library is missing from testing, https://github.com/wernerd/ZRTPCPP provides the file(s). So cmake .. -DWITH_ALSA=On -DWITH_SPEEX=On -DWITH_ILBC=Off -DWITH_ZRTP=On -DWITH_G729=Off -DWITH_QT5=On now works.
Bug#979180: Git twinkle compiles
I have managed to compile the latest git version of twinkle by omitting a few codecs. I used cmake .. -DWITH_ALSA=On -DWITH_SPEEX=On -DWITH_ILBC=Off -DWITH_ZRTP=Off -DWITH_G729=Off -DWITH_QT5=On This seems to have produced a working twinkle and so far there have been no problems with ALSA. But I have done very little testing so far. So it looks as if it should be possible to get a working version in Debian.
Bug#979180: Twinkle
I have attempted to compile a newer version of twinkle, but libzrtpccp has been removed from testing which is needed. I hope that I can find or compile a version of that which will enable further progress.
Bug#979348: kalarm: Kalarm requires pulseaudio - no direct ALSA support
Package: kalarm Version: 4:20.08.3-1 Severity: wishlist I could not get kalarm to play audio with pulse audio absent. Even with apulse, it did not work, except, perhaps on one occasion which I have not been able to reproduce. It needs proper ALSA support. -- System Information: Debian Release: bullseye/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.0-5-amd64 (SMP w/8 CPU threads) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages kalarm depends on: ii akonadi-server4:20.08.3-1 ii kdepim-runtime4:20.08.3-1 ii kio 5.77.0-3 ii libc6 2.31-6 ii libgcc-s1 10.2.1-3 ii libkf5akonadicontact5 [libkf5akonadicontact5-20.08] 4:20.08.3-1 ii libkf5akonadicore5abi2 [libkf5akonadicore5-20.08] 4:20.08.3-1 ii libkf5akonadimime5 [libkf5akonadimime5-20.08] 4:20.08.3-1 ii libkf5akonadiwidgets5abi1 [libkf5akonadiwidgets5-20.08] 4:20.08.3-1 ii libkf5alarmcalendar5abi1 [libkf5alarmcalendar5-20.08] 4:20.08.3-1 ii libkf5authcore5 5.77.0-3 ii libkf5calendarcore5abi2 5:5.77.0-2 ii libkf5calendarutils5 [libkf5calendarutils5-20.08] 4:20.08.3-1 ii libkf5codecs5 5.77.0-2 ii libkf5completion5 5.77.0-4 ii libkf5configcore5 5.77.0-2 ii libkf5configgui5 5.77.0-2 ii libkf5configwidgets5 5.77.0-2 ii libkf5contacts5 5:5.77.0-2 ii libkf5coreaddons5 5.77.0-2 ii libkf5crash5 5.77.0-2 ii libkf5dbusaddons5 5.77.0-2 ii libkf5globalaccel-bin 5.77.0-3 ii libkf5globalaccel55.77.0-3 ii libkf5guiaddons5 5.77.0-4 ii libkf5holidays5 1:5.77.0-2 ii libkf5i18n5 5.77.0-2 ii libkf5identitymanagement5 [libkf5identitymanagement5-20.08] 20.08.3-1 ii libkf5itemmodels5 5.77.0-2 ii libkf5jobwidgets5 5.77.0-2 ii libkf5kiocore55.77.0-3 ii libkf5kiofilewidgets5 5.77.0-3 ii libkf5kiowidgets5 5.77.0-3 ii libkf5mailtransport5 [libkf5mailtransport5-20.08] 20.08.3-1 ii libkf5mailtransportakonadi5 [libkf5mailtransportakonadi5-20. 20.08.3-1 ii libkf5mime5abi1 [libkf5mime5-20.08] 20.08.3-1 ii libkf5notifications5 5.77.0-2 ii libkf5pimcommon5abi2 [libkf5pimcommon5-20.08] 4:20.08.3-1 ii libkf5pimtextedit5abi2 [libkf5pimtextedit5-20.08] 20.08.3-1 ii libkf5textwidgets55.77.0-2 ii libkf5widgetsaddons5 5.77.0-4 ii libkf5windowsystem5 5.77.0-2 ii libkf5xmlgui5 5.77.0-2 ii libphonon4qt5-4 4:4.11.1-3 ii libqt5core5a 5.15.2+dfsg-2 ii libqt5dbus5 5.15.2+dfsg-2 ii libqt5gui55.15.2+dfsg-2 ii libqt5network55.15.2+dfsg-2 ii libqt5widgets55.15.2+dfsg-2 ii libqt5x11extras5 5.15.2-2 ii libstdc++610.2.1-3 ii perl 5.32.0-6 ii phonon4qt54:4.11.1-3 kalarm recommends no packages. kalarm suggests no packages. -- no debconf information
Bug#979139: linphone-desktop: Icons not shown
On Mon, Jan 04, 2021 at 10:23:14PM +0100, Bernhard Schmidt wrote: > Am 04.01.21 um 22:16 schrieb ael: > > Hi, > > > > When I run linphone > > > > QSGTextureAtlas: texture atlas allocation failed, code=501 > > > > is one of the messages sent to stdout. Not sure whether this is relevant > > as yet. > > > > A quick search gave a few hits like > > https://etbe.coker.com.au/2020/12/04/kde-icons-disappearing-unstable/ > > which also mentions disappearing icons, so perhaps promising. > > that sounds promising. Did you try the workaround? Yes. Already posted. It worked. > Update 2 > > Carsten provided the REAL solution to this, run “apt remove > libqt5quick5-gles” which will automatically install “libqt5quick5” which > makes things work. Another workstation I run that tracks Testing had > libqt5quick5 installed which was why it didn’t have the problem. Yes, that seems to have worked. Excellent. I need to do a bit more testing tomorrow... ael
Bug#979139: Missing icons restored
As suggested in one of those posts, export MESA_EXTENSION_OVERRIDE="-GL_EXT_bgra -GL_EXT_texture_format_BGRA" before running linphone restores the icons! I need to test further tomorrow, but it looks very promissing ...
Bug#979139: linphone-desktop: Icons not shown
When I run linphone QSGTextureAtlas: texture atlas allocation failed, code=501 is one of the messages sent to stdout. Not sure whether this is relevant as yet. A quick search gave a few hits like https://etbe.coker.com.au/2020/12/04/kde-icons-disappearing-unstable/ which also mentions disappearing icons, so perhaps promising.
Bug#979139: Missing icons in linphone-desktop XFCE
I have done a quick check on linphone_filtered.log and as far as I can see I have packages installed which provide all of the files and libraries except those ending so.avx2. That is surprising because I am runing on a Haswell processor and have libmkl-avx2, libmkl-vml-avx2 and all the other lib*avx* packages installed. But none of them seem obviously connected with the black rectabgles replacing all the icons. So probably I have filtered out the relevant parts of linphone.log. I will try to look there maybe tomorrow.
Bug#979139: /usr/bin/linphonec: Missing documentation: access to linphone-friends.db.
On Mon, Jan 04, 2021 at 05:47:38PM +0100, Bernhard Schmidt wrote: > Am 04.01.21 um 17:32 schrieb ael via Pkg-voip-maintainers: > > > > > However there is something amiss with the redering of icons. > > Screenshot attached (I have cut out some contact details to protect > > privacy). Perhaps a missing dependency? > > Quite possible, but I'm a bit unsure which one. It works fine for me. > > Are you using the KDE Plasma desktop or something else? xfce4. > days. If you want to beat me to it, you could check with strace for > unsuccessful file accesses. I was looking for some debug switches, but the only thing was -V which produced very little, and nothing of interest. I will have a look with strace, but I am usually overwhelmed with the huge volume irrelevant data :-) I suppose that I could install the -dbgsym package and try with gdb, but I suspect I won't know where to look. I did look to see whether I could see a plasma-theme package that I could install as a test, but that wanted to pull in too much other stuff :-(
Bug#979139: /usr/bin/linphonec: Missing documentation: access to linphone-friends.db.
> gone upstream and will not come back. > > However, linphonec is not the successor. The successor is a Qt based GUI > client which unfortunately will only migrate to testing in a few days. > > https://tracker.debian.org/pkg/linphone-desktop > > Please try this one instead. It is still a very different beast than the > Gtk client, but I hope it will be more usable as a SIP client than > linphonec. I have installed linphone-desktop from the unstable distribution. As you say, very different! It has read the linphone_friend.db which is good. However there is something amiss with the redering of icons. Screenshot attached (I have cut out some contact details to protect privacy). Perhaps a missing dependency? I may report more when I have collected information.
Bug#979139: /usr/bin/linphonec: Missing documentation: access to linphone-friends.db.
On Mon, Jan 04, 2021 at 02:21:24PM +0100, Bernhard Schmidt wrote: > https://tracker.debian.org/pkg/linphone-desktop > > Please try this one instead. It is still a very different beast than the > Gtk client, but I hope it will be more usable as a SIP client than > linphonec. OK. I will try that. Thanks.
Bug#979180: twinkle: Cannot open ALSA driver ...
Package: twinkle Version: 1:1.10.2+dfsg-1 Severity: normal When twinkle starts it is unable to access the ALSA devices: - Critical: Cannot open ALSA driver for PCM playback: Device or resource busy Sun 21:07:45 Critical: Cannot open ALSA driver for PCM playback: Device or resource busy Sun 21:07:45 Critical: Cannot open ALSA driver for PCM playback: Device or resource busy --- Linphone and other sound applications have no such problem. And no, I was not running linphone at the same time. I am very rusty on ALSA, so have not done any diagnostics so far. alsa-info did not seem to include anything useful. aplay -l gave: List of PLAYBACK Hardware Devices card 0: PCH_1 [HDA Intel PCH], device 0: ALC269VB Analog [ALC269VB Analog] Subdevices: 0/1 Subdevice #0: subdevice #0 card 1: PCH [HDA Intel HDMI], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: PCH [HDA Intel HDMI], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: PCH [HDA Intel HDMI], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: PCH [HDA Intel HDMI], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: PCH [HDA Intel HDMI], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 And it is card 0: that I am using. The twinkle audio settings take the form: Alsa: plughw: 0,0: HDA Intel PCH (ALC269VB Analog... (I did leave a very brief comment on the twinkle github.) -- System Information: Debian Release: bullseye/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.0-5-amd64 (SMP w/8 CPU threads) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages twinkle depends on: ii libasound2 1.2.4-1 ii libc62.31-6 ii libccrtp2v5 2.0.9-2.3 ii libgcc-s110.2.1-3 ii libgsm1 1.0.18-2 ii libmagic11:5.39-3 ii libqt5core5a 5.15.2+dfsg-2 ii libqt5gui5 5.15.2+dfsg-2 ii libqt5qml5 5.15.2+dfsg-2 ii libqt5quick5-gles5.15.2+dfsg-2 ii libqt5widgets5 5.15.2+dfsg-2 ii libreadline8 8.1-1 ii libsndfile1 1.0.28-8 ii libspeex11.2~rc1.2-1.1 ii libspeexdsp1 1.2~rc1.2-1.1 ii libstdc++6 10.2.1-3 ii libucommon8 7.0.0-16 ii libxml2 2.9.10+dfsg-6.3+b1 ii qml-module-qtquick2 5.15.2+dfsg-2 ii twinkle-common 1:1.10.2+dfsg-1 twinkle recommends no packages. twinkle suggests no packages. -- no debconf information
Bug#979139: /usr/bin/linphonec: Missing documentation: access to linphone-friends.db.
Package: linphone-nogtk Severity: normal File: /usr/bin/linphonec Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I did an upgrade and lost a excellent working linphone installation :-( I realise that this is probably an upstream problem, but removing an excellent working linphone and replacing it with a barely documented substitute which appears to only have 5% of the old functionality without warning is really poor. Removing the GUI completely is pretty dire. I am very comfortable with the cli, but it is completely unclear how it is intended to be used. To be a bit more specific: 1) Starting linphonec gives a series of error messages: belle-sip-error-Cannot connect to [UDP://sipgate.co.uk:5060] 2021-01-03 13:10:21:607 belle-sip-error-belle_sip_get_src_addr_for: bctbx_connect() failed: Network is unreachable [..snip 5 repeats ] These do not seem to prevent outgoing calls, so perhaps as just informative, although it is unclear what is happening. 2) There seems to be no acccess to ~/.linphone-friends.db linphonec> friend list gives no results. Checking ~./linphone-friends.db with sqlite3 ~/.linphone-friends.db shows that all the contacts are still there. How is linphonec usable without access to the "directory". 3) How is linphonec supposed to answer calls? Yes there is an "answer" command, but is a copy of linphonec supposed to be running perhaps in a terminal to accept calls? >From the linphonecsh man page and inspection with htop, it seems that linphonec has an undocumented --pipe option, which presumably is the answer to the question above. It is unclear how an incoming call is signalled. I am sorry to be so negative, and perhaps need to do more reading, but such a sudden downgrade without warning is upsetting. Thank you for all the working in maintaining the package. -- System Information: Debian Release: bullseye/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.0-5-amd64 (SMP w/8 CPU threads) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#976284: linux-image-5.9.0-4-amd64: kernel oops when handling small 32GB usb drives
Package: src:linux Version: 5.9.11-1 Severity: normal Dear Maintainer, I checked dmesg after mounting a couple of new usb sticks and found a few oops apparently associated with task sync. I will attach the dmesg (gzipped) if reportbug does not do that automatially. -- Package-specific info: ** Version: Linux version 5.9.0-4-amd64 (debian-ker...@lists.debian.org) (gcc-10 (Debian 10.2.0-19) 10.2.0, GNU ld (GNU Binutils for Debian) 2.35.1) #1 SMP Debian 5.9.11-1 (2020-11-27) ** Command line: BOOT_IMAGE=/boot/vmlinuz-5.9.0-4-amd64 root=UUID=5b8060f7-f126-4534-a051-db5d205bd315 ro elevator=deadline ** Not tainted ** Kernel log: Unable to read kernel log; any relevant messages should be attached ** Model information sys_vendor: Notebook product_name: W54_55SU1,SUW product_version: Not Applicable chassis_vendor: Notebook chassis_version: N/A bios_vendor: American Megatrends Inc. bios_version: 4.6.5 board_vendor: Notebook board_name: W54_55SU1,SUW board_version: Not Applicable ** Loaded modules: nls_ascii nls_cp437 vfat fat essiv authenc dm_crypt dm_mod uas usb_storage snd_hrtimer snd_seq snd_seq_device cmac algif_hash algif_skcipher af_alg bnep uinput binfmt_misc btusb btrtl btbcm btintel bluetooth uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common jitterentropy_rng videodev drbg mc ansi_cprng ecdh_generic ecc intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel pktcdvd kvm irqbypass crc32_pclmul snd_hda_codec_realtek iwlmvm ghash_clmulni_intel snd_hda_codec_generic aesni_intel ledtrig_audio snd_hda_codec_hdmi libaes cpufreq_ondemand snd_hda_intel crypto_simd snd_intel_dspcfg mac80211 cryptd glue_helper libarc4 rtsx_pci_sdmmc snd_hda_codec xhci_pci iTCO_wdt intel_pmc_bxt rapl mmc_core iTCO_vendor_support iwlwifi xhci_hcd snd_hda_core r8169 ehci_pci watchdog at24 ehci_hcd intel_cstate snd_hwdep realtek snd_pcm mdio_devres sr_mod cfg80211 intel_uncore mei_me cdrom snd_timer i2c_i801 usbcore rtsx_pci libphy sg mei snd rfkill pcspkr soundcore lpc_ich joydev usb_common i2c_smbus wmi battery button ac nfsd msr parport_pc ppdev lp parport auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic sd_mod t10_pi crc_t10dif crct10dif_generic i915 i2c_algo_bit drm_kms_helper ahci libahci cec libata crct10dif_pclmul drm crct10dif_common scsi_mod psmouse crc32c_intel evdev serio_raw video ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller [8086:0c04] (rev 06) Subsystem: CLEVO/KAPOK Computer Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller [1558:5455] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel modules: ie31200_edac 00:02.0 VGA compatible controller [0300]: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer 4th Gen Core Processor Integrated Graphics Controller [1558:5455] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: i915 Kernel modules: i915 00:03.0 Audio device [0403]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller [8086:0c0c] (rev 06) Subsystem: CLEVO/KAPOK Computer Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller [1558:5455] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:14.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI [8086:8c31] (rev 05) (prog-if 30 [XHCI]) Subsystem: CLEVO/KAPOK Computer 8 Series/C220 Series Chipset Family USB xHCI [1558:5455] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: xhci_hcd Kernel modules: xhci_pci 00:16.0 Communication controller [0780]: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 [8086:8c3a] (rev 04) Subsystem: CLEVO/KAPOK Computer 8 Series/C220 Series Chipset Family MEI Controller [1558:5455] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAb
Bug#968215: Chromium crash
+1 Similar behaviour here with Linux elf 5.7.0-3-686-pae #1 SMP Debian 5.7.17-1 (2020-08-23) i686 on i386 box. Calling _exit(1). Core file will not be generated. ../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403 Received signal 11 SEGV_ACCERR 06c01193 #0 0x04f3c77f (/usr/lib/chromium/chromium+0x4b1177e) #1 0x04e8da12 (/usr/lib/chromium/chromium+0x4a62a11) #2 0x04f3c3ee (/usr/lib/chromium/chromium+0x4b113ed) #3 0xb7eec1e4 ([vdso]+0x11e3) #4 0x06115d28 (/usr/lib/chromium/chromium+0x5cead27) #5 0x0611ccf4 (/usr/lib/chromium/chromium+0x5cf1cf3) #6 0x0611ca4a (/usr/lib/chromium/chromium+0x5cf1a49) #7 0xb7eec1e4 ([vdso]+0x11e3) #8 0xb7eec1cd ([vdso]+0x11cc) #9 0xb7eec12a ([vdso]+0x1129) #10 0xb386cf69 (/lib/i386-linux-gnu/libc-2.31.so+0xc3f68) gs: 0033 fs: es: 007b ds: 007b edi: 0193 esi: bfd7ed88 ebp: bfd7ed58 esp: bfd7ed40 ebx: 09b63d38 edx: 0080 ecx: 06c01193 eax: 1000 trp: 000e err: 0007 ip: 06115d28 cs: 0073 efl: 00210206 usp: bfd7ed40 ss: 007b [end of stack trace] is one of many such error messages on the terminal. Running with -g wasn't very helpful, but among the errors reported was: ERROR :GL_INVALID_OPERATION : glDrawElements: buffer format and fragment output variable type incompatible This was on first installetion. Seems to be completely broken :-)
Bug#966283: calibre: Literal "<>" characters in text file not converted properly
On Mon, 27 Jul 2020 06:22:20 +0900 yokota wrote: > > Converting a text file (to epub) which included many lines like > > " > > = > > " > > resulted in just the character "=". > > When converts from TXT format, Calibre tries to detect format type. > Your text file "/usr/share/doc/exim4-base/spec.txt.gz" seems to be > Markdown format, > so Calibre treats your text file as Markdown format. > > If you want to disable these format detection and treat your file as > plain text file, use file converter from Calibre GUI. [snip] Yes that seems to have worked. Thankyou. I completely missed that sub menu for TXT input. It had not occurred to me that txt would not mean plain text. I already knew about Markdown and friends, but would have expected to need to specify Markdown or whatever if needed. After all, html files are also just (plain) text that just happen usually to have special filenames. But thanks again. I guess this "bug" needs to be closed.
Bug#964775: falkon: not thread-safe: livelock?
Package: falkon Version: 3.1.0+dfsg1-7 Severity: normal Dear Maintainer, falkon has repeatedly "hung": fails to respond. htop shows near 100% usage of QtWebEngineProcess. I normally kill that process to get back control, but on one occasion falkon eventually loaded the target page and returned to normal, so I don't know whether the other cases were true livelock or not. However, falkon is itself issuing this message: Please register the custom scheme 'extension' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. Use of deprecated not thread-safe setter, use setUrlRequestInterceptor instead. So that makes a livelock explanation more likely. -- -- System Information: Debian Release: bullseye/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 5.7.0-1-686-pae (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages falkon depends on: ii kio 5.70.1-1 ii libc62.30-8 ii libgcc-s110.1.0-4 ii libkf5coreaddons55.70.0-1 ii libkf5crash5 5.70.0-1 ii libkf5kiocore5 5.70.1-1 ii libkf5kiowidgets55.70.1-1 ii libkf5purpose-bin5.70.0-1 ii libkf5purpose5 5.70.0-1 ii libkf5wallet-bin 5.70.0-1 ii libkf5wallet55.70.0-1 ii libqt5core5a 5.14.2+dfsg-4 ii libqt5dbus5 5.14.2+dfsg-4 ii libqt5gui5 5.14.2+dfsg-4 ii libqt5network5 5.14.2+dfsg-4 ii libqt5printsupport5 5.14.2+dfsg-4 ii libqt5qml5 5.14.2+dfsg-2 ii libqt5quickwidgets5 5.14.2+dfsg-2 ii libqt5sql5 5.14.2+dfsg-4 ii libqt5sql5-sqlite5.14.2+dfsg-4 ii libqt5webchannel55.14.2-2 ii libqt5webenginecore5 5.14.2+dfsg1-2 ii libqt5webenginewidgets5 5.14.2+dfsg1-2 ii libqt5widgets5 5.14.2+dfsg-4 ii libqt5x11extras5 5.14.2-2 ii libssl1.11.1.1g-1 ii libstdc++6 10.1.0-4 ii libxcb1 1.14-2 ii qml-module-qtwebengine 5.14.2+dfsg1-2 Versions of packages falkon recommends: ii falkon-plugin-wallet 3.1.0+dfsg1-7 Versions of packages falkon suggests: pn qtwebengine5-dev-tools -- no debconf information
Bug#963560: UNIQ still present
On Thu, Jul 02, 2020 at 09:44:51PM +0200, Dirk Hünniger wrote: > Hi, > > I looked at the print version of the Haskell wikibook which is located at > the url > > https://en.wikibooks.org/wiki/Haskell/Print_version > > I looked into the chapter Getting set up > > and found the following paragraph. > > > These operators match most other programming languages: |+| is addition, > > |*| is multiplication, and |^| is exponentiation (raising to the power > > of, or '"`UNIQ--postMath-0001-QINU`"'). As shown in the second > > example, Haskell follows standard order of math operations (e.g. > > multiplication before addition). > So the problem is in MediaWiki not in mediawiki2latex OK. I guess my previous post with the link to https://www.mediawiki.org/wiki/QINU_fix and https://phabricator.wikimedia.org/T19329 is the same problem. Thanks for all the work and replies. ael
Bug#963560: UNIQ still present
On Thu, Jul 02, 2020 at 07:43:57PM +0100, ael wrote: > > > I just had a look at the mediawiki2latex source code and found that the > > > formular for epub documents are prepared using the latex2png command which > > > is part of the latex2rtf package. So please make sure the latex2rtf > > > package > > > is installed on your system. > > > > :-) That looks as if it has fixed the problem. I even mentioned > > latex2rtf myself earlier, but forgot to try this. > > > > I will try the full book as well just to make sure, but that will take > > a little longer. > > Sadly, the problem seems to still be present when I use > > mediawiki2latex -u https://en.wikibooks.org/wiki/Haskell/Print_version > -b -o /tmp/Haskell.epub Just to make sure that I wasn't viewing an old copy in calibre's library, I repeated and checked. Problem still present. Screen shot from calibre's viewer in the first instance that I noticed. ael
Bug#963560: main.pdf: openBinaryFile: does not exist
On Thu, Jul 02, 2020 at 07:22:40PM +0100, ael wrote: > On Thu, Jul 02, 2020 at 07:53:45PM +0200, Dirk Hünniger wrote: > > Hi, > > > > I just had a look at the mediawiki2latex source code and found that the > > formular for epub documents are prepared using the latex2png command which > > is part of the latex2rtf package. So please make sure the latex2rtf package > > is installed on your system. > > :-) That looks as if it has fixed the problem. I even mentioned > latex2rtf myself earlier, but forgot to try this. > > I will try the full book as well just to make sure, but that will take > a little longer. Sadly, the problem seems to still be present when I use mediawiki2latex -u https://en.wikibooks.org/wiki/Haskell/Print_version -b -o /tmp/Haskell.epub ael
Bug#963560: main.pdf: openBinaryFile: does not exist
On Thu, Jul 02, 2020 at 07:53:45PM +0200, Dirk Hünniger wrote: > Hi, > > I just had a look at the mediawiki2latex source code and found that the > formular for epub documents are prepared using the latex2png command which > is part of the latex2rtf package. So please make sure the latex2rtf package > is installed on your system. :-) That looks as if it has fixed the problem. I even mentioned latex2rtf myself earlier, but forgot to try this. I will try the full book as well just to make sure, but that will take a little longer. Again, an entry in the man page, I suggest... It is looking very promising ael
Bug#963560: main.pdf: openBinaryFile: does not exist
On Thu, Jul 02, 2020 at 07:36:54PM +0200, Dirk Hünniger wrote: > Hi, > > the problem does not appear on my ubuntu 20.04 running mediawiki2latex 7.40 $ dpkg -s mediawiki2latex|head Package: mediawiki2latex Status: install ok installed Priority: optional Section: misc Installed-Size: 33384 Maintainer: Dirk Huenniger Architecture: amd64 Version: 7.40-1 [..snip..]
Bug#963560: ? QINU fix
On Thu, Jul 02, 2020 at 07:36:54PM +0200, Dirk Hünniger wrote: > > see attached epub file > > command line > > mediawiki2latex -u https://en.wikibooks.org/wiki/Haskell/Truth_values -o > dirk.epub -b > > Yours Dirk > > On 7/2/20 3:14 PM, ael wrote: > > On Wed, Jul 01, 2020 at 05:55:23PM +0200, Dirk Hünniger wrote: > > > Hi, > > > > > > I got an epub that looks Ok using the following command line > > > > > > mediawiki2latex -u https://en.wikibooks.org/wiki/Haskell/Print_version -b > > > -o > > > Haskell.epub > > I still see the sort of problems that I have encountered before with > > that. Apart from no working links, there are things like > > "`UNIQ--postMath-0017-QINU`"' I found https://www.mediawiki.org/wiki/QINU_fix via https://github.com/Mediawiki-wysiwyg/WYSIWYG-CKeditor/issues/105 but I am not sure whether that explains the diffence between Debian and Ubuntu. But perhaps that gives something to go on? ael
Bug#963560: main.pdf: openBinaryFile: does not exist
On Thu, Jul 02, 2020 at 07:36:54PM +0200, Dirk Hünniger wrote: > > > Hi, > > > > > > I got an epub that looks Ok using the following command line > > > > > > mediawiki2latex -u https://en.wikibooks.org/wiki/Haskell/Print_version -b > > > -o > > > Haskell.epub > > I still see the sort of problems that I have encountered before with > > that. Apart from no working links, there are things like > > "`UNIQ--postMath-0017-QINU`"' > > in many places. I attach a couple of screen shots from the calibre viewer. > > I suspect that there are other problems that I haven't yet noticed. Interestingly, when I view https://www.wikidoc.org/index.php/Logarithm in my browser, I see similar strings like UNIQ--postMath-0001-QINU which suggest that there is some package missing on my system. Presumably it needs to be added as a dependency... ael
Bug#963560: main.pdf: openBinaryFile: does not exist
On Thu, Jul 02, 2020 at 07:36:54PM +0200, Dirk Hünniger wrote: > Hi, > > the problem does not appear on my ubuntu 20.04 running mediawiki2latex 7.40 > > see attached epub file > > command line > > mediawiki2latex -u https://en.wikibooks.org/wiki/Haskell/Truth_values -o > dirk.epub -b I tried that here and got: preparing images for LaTeX document mediawiki2latex: /tmp/MediaWiki2LaTeXImages-8b5d44e8857c3d3b/002D003600380034003300350032003500340035003000390032003100340035003500350030.png: openBinaryFile: does not exist (No such file or directory) I am running an up to date Debian testing system. Maybe there is some package that I am missing? I run it under strace and got write(2, "mediawiki2latex: ", 17mediawiki2latex: ) = 17 write(2, "/tmp/MediaWiki2LaTeXImages-e70f5"..., 260/tmp/MediaWiki2LaTeXImages-e70f592f6b041222/002D003600380034003300350032003500340035003000390032003100340035003500350030.png: openBinaryFile: does not exist (No such file or directory)) = 260 but I did not enable multithreading, so maybe missed something. But I doubt that helps much anyway as it seems to add liitle to the message above. I will have to find time to install source and see if I can get some idea of what is wrong. But I won't have time immmediately. ael
Bug#963560: main.pdf: openBinaryFile: does not exist
On Wed, Jul 01, 2020 at 05:30:12PM +0200, Georges Khaznadar wrote: > Dear Dirk, > > promoting packages from Recommended to straigt dependencies deserves > always some discussion. > > I suppose that the excerpt: > > .BR -b ", " --epub > Output epub file. > > Can be enhanced by mentioning calibre, for instance: > > .BR -b ", " --epub > Output epub file. This feature relies on the recommended package calibre. > > Also, when options -b or --epub are triggered, and calibre is not found, > mediawiki2latex might issue some warning, or some "rtfm" stance. I was going to suggest something very similar. Dirk has been very generous with his time suggesting various ways to achieve what I need, but I don't think that the current man page gives any clue about how to select and configure the options in fairly sophisticated ways if one is not already familiar with Wikipedia & wikibooks internals. I am still being lazy, well busy with other things really, so haven't yet looked at the source or tried to follow the Wiki mechanisms. ael
Bug#963560: main.pdf: openBinaryFile: does not exist
On Wed, Jul 01, 2020 at 08:52:51AM +0200, Dirk Hünniger wrote:
> Hi,
>
> thats strange. I got an epub with
>
> mediawiki2latex -u https://en.wikibooks.org/wiki/Haskell/Type_basics -o
> Haskell.epub -b
>
> what command line did you use.
I tried again with -i and this time the error was
Error downloading the lemma "zh:Haskell" form the url "Just (URL {url_type =
Absolute (Host {protocol = HTTP True, host = "en.wikibooks.org", port =
Nothing}), url_path = "wiki/Haskell", url_params = []},[URL {url_type =
Absolute (Host {protocol = HTTP True, host = "en.wikibooks.org", port =
Nothing}), url_path = "wiki", url_params = []},URL {url_type = Absolute (Host
{protocol = HTTP True, host = "en.wikibooks.org", port = Nothing}), url_path =
"", url_params = []},URL {url_type = Absolute (Host {protocol = HTTP True, host
= "commons.wikimedia.org", port = Nothing}), url_path = "wiki", url_params =
[]}])"
But it ran for a substantial time before hitting that error.
So that was with a command line of:
mediawiki2latex -u https://en.wikibooks.org/wiki/Haskell -o /tmp/Haskell.epub
-b -k -i
ael
