Bug#1068018: Perhaps resolved

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

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

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

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

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]

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

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

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

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

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

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

2023-09-03 Thread ael
3.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 urllibpars

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, 'testi

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

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

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

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
, 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

Bug#1021576: linphone documentation

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

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

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

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

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

2021-10-05 Thread ael
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
ngs: "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]

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

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

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

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

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

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

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

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

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 prote

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

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:

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

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

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

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

Bug#963560: UNIQ still present

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

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

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

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

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

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

2020-07-01 Thread ael
te (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

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

2020-07-01 Thread ael
askell.epub -b -k with calibre installed expecting to get the whole book, but hit openBinaryFile: does not exist (No such file or directory) again. Should that have worked? ael

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

2020-07-01 Thread ael
On Wed, Jul 01, 2020 at 08:52:51AM +0200, Dirk Hünniger wrote: > > what command line did you use. mediawiki2latex -u https://en.wikibooks.org/wiki/Haskell/Print_version -b -o /tmp/Haskell.epub -i with calibre installed still fails as before. ael

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

2020-07-01 Thread ael
n to maintain software that perhaps you don't use regularly. ael

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

2020-07-01 Thread ael
On Wed, Jul 01, 2020 at 09:03:33AM +0200, Dirk Hünniger wrote: > oh and you you check if calibre is installed? No, it wasn't. I see that it is a "Recommends". I now wonder whether I might also need latex2rtf, although that isn't so obvious. ael

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

2020-06-30 Thread ael
sion adding the -b flag, and hit the "openBinaryFile: does not exist" problem again. I can probably live without an epub version, but as a Debian package, there are obviously problems. ael

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

2020-06-30 Thread ael
On Tue, Jun 30, 2020 at 08:41:17PM +0200, Dirk Hünniger wrote: > Hi, > > I got something that looks Ok to me using > > mediawiki2latex -u https://en.wikibooks.org/wiki/Haskell/Print_version -o > Haskell.pdf -i Indeed: that seems to give a good copy. Thanks. ael

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

2020-06-30 Thread ael
On Tue, Jun 30, 2020 at 01:07:13PM +0200, Dirk Hünniger wrote: > Hi, > > if you want to fetch recursively try option -k. As I said, that now fetches recursively OK, but there are now many errors. I attach main.tex and main.log (bzip2'ed). ael main.tex.bz2 Description: Bi

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

2020-06-30 Thread ael
o look a liitle further. ael

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

2020-06-30 Thread ael
”‘UNIQ--postMath-0001- QINU‘ on page 16 of the pdf. Should I re-open this bug, or open a new bug report? Thanks for the quick response to the first problem, by the way. ael

Bug#963560: main.log

2020-06-23 Thread ael
main.log attached. This is XeTeX, Version 3.14159265-2.6-0.92 (TeX Live 2020/Debian) (preloaded format=xelatex 2020.6.13) 23 JUN 2020 19:36 entering extended mode restricted \write18 enabled. %&-line parsing enabled. **main.tex (./main.tex LaTeX2e <2020-02-02> patch level 5 L3 programming

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

2020-06-23 Thread ael
Package: mediawiki2latex Version: 7.39-1+b1 Severity: normal Dear Maintainer, Program fails reporting main.pdf: openBinaryFile: does not exist It gets this far: FullConfig {headers = Nothing, resolution = 300, outputFilename = "/tmp/Haskell", inputUrl =

Bug#962622: qmapshack: Segmentation fault: no file found for translations

2020-06-11 Thread ael
> completed. Thanks. I saw the upstream duplicate bug. Menawhile I must look into code page generation. ael

Bug#962622: qmapshack: Segmentation fault: no file found for translations

2020-06-11 Thread ael
On Thu, Jun 11, 2020 at 06:28:58PM +0200, Sebastiaan Couwenberg wrote: > Control: tags -1 - moreinfo > Control: tags -1 upstream > Control: forwarded -1 https://github.com/Maproom/qmapshack/issues/209 > > On 6/11/20 4:55 PM, ael wrote: > > Small test.img (20M) attached. &g

Bug#962622: qmapshack: Segmentation fault: no file found for translations

2020-06-11 Thread ael
On Thu, Jun 11, 2020 at 05:52:04AM +0200, Sebastiaan Couwenberg wrote: > Control: tags -1 moreinfo > > On 6/10/20 10:08 PM, ael wrote: > > Trying to read a gmapsupp.img generated by mkgmap using mapnik.typ > > results in an immediate crash. > > Can you share this file

Bug#962622: qmapshack: Segmentation fault: no file found for translations

2020-06-10 Thread ael
Package: qmapshack Version: 1.14.1-1 Severity: normal Trying to read a gmapsupp.img generated by mkgmap using mapnik.typ results in an immediate crash. Running under gdb doesn't give much useful information, but: (gdb) run Starting program: /usr/bin/qmapshack [Thread debugging using

Bug#961508: ifupdown: RTNETLINK answers: File exists

2020-05-25 Thread ael
Package: ifupdown Version: 0.8.35 Severity: normal There seem to be so many open bugs for ifupdown that it is not clear whether there is any point in reporting this, but perhaps it may help others. I have encountered the unhelpful error message "RTNETLINK answers: File exists" on more than one

Bug#958732: linux-image-5.5.0-2-amd64: invalid opcode: 0000 [#1] SMP PTI kernel crash (stilll called an Oops?)

2020-04-24 Thread ael
Package: src:linux Version: 5.5.17-1 Severity: normal Kernel crash: Apr 24 12:58:24 shelf kernel: [ 8109.802668] [ cut here ] Apr 24 12:58:24 shelf kernel: [ 8109.802673] invalid opcode: [#1] SMP PTI Apr 24 12:58:24 shelf kernel: [ 8109.802676] CPU: 4 PID: 5665

Bug#949780: maptool: Maptool segfaults

2020-01-26 Thread ael
used the simplest defaults I think. In my history I just have cmake ../navit/ make maptool Does that tell you what you need to know? ael

  1   2   3   4   5   >