Bug#1090803: linux-image-6.11.10-amd64: Longstanding bug in usb disk mounting.

2024-12-19 Thread ael
Package: src:linux Version: 6.11.10-1 Severity: important Dear Maintainer, * What led up to the situation? Inserting usb thumb drive expecting hotplugging. Hotplugging usb thumb drives has long led to segfaults in multiple cores. This has been happening over multiple kernel versions for perh

Bug#1080459: Cannot probe codecs...

2024-09-25 Thread ael
One more data point: On a failure, dmesg shows: 0.741723] snd_hda_intel :00:1b.0: Cannot probe codecs, giving up (on a fail) But on an older working kernel, there is no such message, but dmesg includes:- == 5.155954] snd_hda_intel

Bug#1080459: Changes to /proc/modules after reisnatllinh snd_hda_intel

2024-09-24 Thread ael
Just in case this is useful I recorded the changes in /proc/modules after the usual "correction" # modprobe -r snd_hda_intel # modprobe snd_hda_intel I just used cat /proc/modules |grep snd_hda_intel > ~/after.txt before and after the above commands and then diff before.txt after.txt >compare.d

Bug#1080459: Adding snd_hda_intel to /etc/initramfs-tools/modules did not help

2024-09-22 Thread ael
Just to record that adding snd_hda_intel to /etc/initramfs-tools/modules did not help. This is not surprising since snd_hda_intel is already being loaded, but without the parameter options being correctly obeyed.

Bug#1080459: Problem remains with 6.10.9-amd64

2024-09-14 Thread ael
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

Bug#1080459: Comparing initramfs versions

2024-09-12 Thread ael
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

Bug#1080459: update initramfs did not help. REverting to 6.10.4-amd64 worked

2024-09-11 Thread ael
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 compare

Bug#1080459: update initramfs did not help. REverting to 6.10.4-amd64 worked

2024-09-11 Thread ael
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 hav

Bug#1080459: Possible clues

2024-09-09 Thread ael
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

Bug#1080459: Correction: probably not systemd after all.

2024-09-09 Thread ael
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,

Bug#1080459: systemd after all? Failed to find module 'options snd_hda_intel...

2024-09-09 Thread ael
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

Bug#1080459: Why are module parameters under /etc/modprobe.d not respected?

2024-09-07 Thread ael
ore 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?

2024-09-07 Thread ael
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

2024-09-04 Thread ael
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 li

Bug#1080459: kmod: Option parameters under /etc/modprobe.d are not obeyed on system initialization

2024-09-04 Thread ael
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 ob

Bug#1080459: kmod: Option parameters under /etc/modprobe.d are not obeyed on system initialization

2024-09-04 Thread ael
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 modpro

Bug#1080459: kmod: Option parameters under /etc/modprobe.d are not obeyed on system initialization

2024-09-04 Thread ael
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

Bug#1080459: kmod: Option parameters under /etc/modprobe.d are not obeyed on system initialization

2024-09-04 Thread ael
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 ther

Bug#1080459: kmod: Option parameters under /etc/modprobe.d are not obeyed on system initialization

2024-09-04 Thread ael
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 so

Bug#1080458: kmod: Option parameters under /etc/modprobe.d are not obeyed on system initialization

2024-09-04 Thread ael
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 soun

Bug#1080388: linux-image-6.10.6-amd64: Module parameters in /etc/modprobe.d/ are not configured

2024-09-03 Thread ael
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

Bug#1075981: offlineimap3: invalid escape sequence

2024-07-08 Thread ael
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/imapl

Bug#1068018: Perhaps resolved

2024-04-07 Thread ael
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

2024-03-29 Thread ael
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 man

Bug#1064855: xfce4-power-manager: Display is shutdown despite activity

2024-02-26 Thread ael
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 brok

Bug#1054130: It probably was trivial

2024-01-29 Thread ael
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

2024-01-01 Thread ael
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

Bug#1054345: usbcore call trace

2023-11-10 Thread ael
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] t

Bug#1055463: Removal of sysvinit

2023-11-08 Thread ael
if this ridiculous proposal goes through. ael

Bug#1054345: Bug presebt on all recent kernel versions

2023-10-22 Thread ael
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

2023-10-22 Thread ael
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 me

Bug#1054346: linux-image-6.5.0-2-amd64: Segfault with USB Mass storage

2023-10-22 Thread ael
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 me

Bug#1054132: podget: line 2532: ITEM_TITLE: unbound variable

2023-10-17 Thread ael
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/nak

Bug#1054131: podget: line 2532: ITEM_TITLE: unbound variable

2023-10-17 Thread ael
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/nake

Bug#1054130: podget: line 2532: ITEM_TITLE: unbound variable

2023-10-17 Thread ael
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/nake

Bug#1051134: AttributeError: 'str' object has no attribute '__suppress_context__'

2023-09-03 Thread ael
^ 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__' ==

Bug#1041508: tex-common: Installation fails if system is missing the set locale

2023-09-03 Thread ael
mp/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

2023-08-07 Thread ael
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

2023-08-07 Thread ael
ed. 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, '

Bug#1039008: M365-IMAP

2023-06-25 Thread ael
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

2023-06-24 Thread ael
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

2023-06-24 Thread ael
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

Bug#1034145: htop: Sort does not work?

2023-04-10 Thread ael
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. &

Bug#1034145: htop: Sort does not work?

2023-04-10 Thread ael
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. &

Bug#1034145: htop: Sort does not work?

2023-04-10 Thread ael
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 see

Bug#961508: ifupdown: RTNETLINK answers: File exists

2023-02-03 Thread ael
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

2023-01-31 Thread ael
bian.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

2022-10-23 Thread ael
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

2022-10-19 Thread ael
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

2022-10-17 Thread ael
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 i

Bug#1021938: kalarm: .local/share/kalarm/expired.ics is not a valid iCalendar file

2022-10-17 Thread ael
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

Bug#1021884: korganizer segfaults when adding new event

2022-10-16 Thread ael
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

Bug#1021576: linphone documentation

2022-10-13 Thread ael
action 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

2022-10-13 Thread ael
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

Bug#1021576: can't have both LIME and LIME X3DH enabled at the same time

2022-10-13 Thread ael
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

Bug#1021576: Interim gdb log

2022-10-12 Thread ael
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

Bug#1021576: Small update

2022-10-12 Thread ael
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.

2022-10-11 Thread ael
> > 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

Bug#1021561: Twinkle problem resolved

2022-10-11 Thread ael
. I will attempt to close this bug. ael

Bug#1021576: linphone-desktop: Core dumped: Program terminated with signal SIGABRT, Aborted.

2022-10-10 Thread ael
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-

Bug#1021561: twinkle: Cannot mix incompatible Qt library (5.15.6) with this library (5.15.4)

2022-10-10 Thread ael
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

Bug#997933: offlineimap3: 'int' object is not subscriptable when connecting to outlook.office365.com

2021-10-27 Thread ael
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 l

Bug#993350: [sane-devel] Epson Perfection1640: Operation not supported

2021-10-05 Thread ael
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

2021-10-05 Thread ael
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 t

Bug#993350: [sane-devel] Epson Perfection1640: Operation not supported

2021-10-05 Thread ael
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-proje

Bug#993350: [sane-devel] Epson Perfection1640: Operation not supported

2021-10-04 Thread ael
ndency 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

2021-10-04 Thread ael
kends/-/commit/580c278dcafe4159213406b4307ee8598fe08f e7 " This is on the sane-devel list: sane-de...@alioth-lists.debian.net ael

Bug#993350: Also broken on Perfection 1640

2021-10-04 Thread ael
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

2021-09-19 Thread ael
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-f

Bug#991559: geeqie: Cannot select zoom-to-fit as default

2021-07-27 Thread ael
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 dir

Bug#904098: Timidity is blocking alsa plughw

2021-01-25 Thread ael
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*"

Bug#979180: Timidity is the cause

2021-01-25 Thread ael
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 stil

Bug#904098: Timidity is blocking alsa plughw

2021-01-24 Thread ael
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

Bug#979139: Answering calls

2021-01-08 Thread ael
window and somehow escaped my notice. ael

Bug#979139: linphone-desktop: Icons not shown

2021-01-08 Thread ael
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

Bug#979180: ALSA now working

2021-01-07 Thread ael
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.1

Bug#979180: AlSA problems remain

2021-01-07 Thread ael
Sadly the new twinkle still has ALSA problems. I will try to investigate.

Bug#979180: Adding ZRTP

2021-01-07 Thread ael
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

2021-01-06 Thread ael
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

Bug#979180: Twinkle

2021-01-06 Thread ael
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

2021-01-05 Thread ael
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:

Bug#979139: linphone-desktop: Icons not shown

2021-01-04 Thread ael
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 std

Bug#979139: Missing icons restored

2021-01-04 Thread ael
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

2021-01-04 Thread ael
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 disappeari

Bug#979139: Missing icons in linphone-desktop XFCE

2021-01-04 Thread ael
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*av

Bug#979139: /usr/bin/linphonec: Missing documentation: access to linphone-friends.db.

2021-01-04 Thread ael
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

Bug#979139: /usr/bin/linphonec: Missing documentation: access to linphone-friends.db.

2021-01-04 Thread ael
> 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 di

Bug#979139: /usr/bin/linphonec: Missing documentation: access to linphone-friends.db.

2021-01-04 Thread ael
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.

Bug#979180: twinkle: Cannot open ALSA driver ...

2021-01-03 Thread ael
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: Can

Bug#979139: /usr/bin/linphonec: Missing documentation: access to linphone-friends.db.

2021-01-03 Thread ael
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 pr

Bug#976284: linux-image-5.9.0-4-amd64: kernel oops when handling small 32GB usb drives

2020-12-02 Thread ael
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: *

Bug#968215: Chromium crash

2020-09-13 Thread ael
+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_AC

Bug#966283: calibre: Literal "<>" characters in text file not converted properly

2020-07-27 Thread ael
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

Bug#964775: falkon: not thread-safe: livelock?

2020-07-10 Thread ael
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

Bug#963560: UNIQ still present

2020-07-02 Thread ael
ond > > 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

2020-07-02 Thread ael
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 ple

Bug#963560: main.pdf: openBinaryFile: does not exist

2020-07-02 Thread ael
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 latex2pn

Bug#963560: main.pdf: openBinaryFile: does not exist

2020-07-02 Thread ael
... It is looking very promising ael

Bug#963560: main.pdf: openBinaryFile: does not exist

2020-07-02 Thread ael
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 Maintain

Bug#963560: ? QINU fix

2020-07-02 Thread ael
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: > > O

  1   2   3   4   5   6   >