On Mon Aug 22, 2022 at 14:53:57 -0700, Russ Allbery wrote:
> Control: severity -1 important
>
> Adam Lackorzynski writes:
>
> > I had the same issue. Turned out my personal .emacs.d/eln-cache
> > directory and its folders belonged to root:
>
> > $ ls -la $HOM
On Fri Aug 19, 2022 at 11:42:30 -0700, Russ Allbery wrote:
> Package: emacs-lucid
> Version: 1:28.1+1-1
> Severity: grave
> X-Debbugs-Cc: r...@debian.org
>
> The 28.1 version of emacs-lucid fails on startup with a cryptic error
> message:
>
> % emacs
> Cannot find suitable directory for output
Source: qemu
Version: 1:6.2+dfsg-1
Severity: normal
Hi,
QEMU 6.2 ships with a new multiboot blob, please include it as it is used by
default when launching a multiboot-capable guest:
Could not open option rom 'multiboot_dma.bin': No such file or directory
--- optionrom.mak.old 2022-01-17
On Mon Jun 14, 2021 at 10:19:13 +0100, Mike Crowe wrote:
> Hi Adam,
>
> On Monday 14 June 2021 at 09:16:51 +0200, Adam Lackorzynski wrote:
> > Ok, thanks. Meantime I changed all of this static memory handling to be
> > more dynamic, also addressing this case I believe.
Hi Mike,
On Mon Jun 14, 2021 at 08:12:18 +0100, Mike Crowe wrote:
> On Sunday 13 June 2021 at 21:22:32 +0200, Adam Lackorzynski wrote:
> > thanks again. I wonder why it did not reproduce for me earlier.
> > Could you try attached patch and report back?
>
> Hi Adam,
>
ac
> Intra object redzone:bb
> ASan internal: fe
> Left alloca redzone: ca
> Right alloca redzone:cb
> Shadow gap: cc
> ==56567==ABORTING
>
> I hope this is meaningful to you. If not, I'll see if I can work out
> anything mor
Hi,
thanks for the report. The issue has always been there and had to do
with the width of minicom's window (over 256 columns). I have addressed
this.
Martin, I have pushed this on the 2.8.x branch (8deebed). Please
pick both changes there for the next upload.
Thanks, Adam
On Fri Jun 11, 2021
Hi Björn,
On Fri Jan 29, 2021 at 09:35:45 +, Björn Wiberg wrote:
> Hello Adam!
>
> Thank you for your reply!
>
> On Sun, 24 Jan 2021 20:44:23 +0100 Adam Lackorzynski
> wrote:
> > I improved the handling in minicom upstream to consider this case.
>
> Thank
Hi,
I improved the handling in minicom upstream to consider this case.
Still, minicom creates the lockfile such that it is readable by
everyone. In your case, has the lockfile been created by minicom or
someone else?
Adam
Hi,
On Wed Jul 26, 2017 at 08:24:48 +0200, Heinrich Schuchardt wrote:
> calling
> minicom -R UTF8
> displays utf-8 characters in the accessed utf-8 system correctly.
>
> Environment variable
> export MINICOM="-R UTF8"
> does not have this effect. Utf-8 characters are output as two (or more)
>
://alioth.debian.org/anonscm/hg/minicom/
Thanks, Adam
On Tue Apr 26, 2016 at 20:45:09 -0400, Mingye Wang (Arthur2e5) wrote:
> On 4/26/2016 18:23, Adam Lackorzynski wrote:
> > Hi,
> >
> > thanks for letting me know of those issues!
> Thanks for responding to my report :)
>
Hi,
thanks for letting me know of those issues!
On Wed Apr 20, 2016 at 12:04:37 -0400, Mingye Wang (Arthur2e5) wrote:
> Package: minicom
> Version: 2.7-1
>
> A few months ago I was doing some minicom zh_CN l10n on
> TranslationProject.org. Since the work is has been assigned to someone
> else,
Hi,
On Mon Apr 11, 2016 at 23:11:24 +0200, Luca Corbatto wrote:
> I can confirm that minicom (still) has problems with utf-8.
> I opened minicom in the gnome-terminal.
>
> I implemented a small console program on an ATMega1284p that simply sends
> the exact same
> bytes it recieves back. I am
On Thu May 09, 2013 at 15:03:26 +0200, Sascha Silbe wrote:
I'm often using multiple minicom instances to work on multiple serial
ports (connected both to different devices and to different ports of
the same device) in parallel. Currently, it's hard to distinguish
these instances as they all
On Thu May 09, 2013 at 16:04:39 +0200, Sascha Silbe wrote:
Adam Lackorzynski a...@os.inf.tu-dresden.de writes:
Starting minicom with -T will show the device name instead of the online
time. I guess that's what you're looking for.
Thanks for the hint; I wouldn't have expected the option
Hi,
I was seeing the same issue on wheezy systems (x86 32 and 64 bit).
proftpd process segfaults on SIGHUP. After tracing this a bit the
segfault happens when processing restart events of the quotatab module.
Thus disabling quota modules in the config makes reload/SIGHUP work
again for me.
HTH,
On Thu Jan 17, 2013 at 23:56:39 -0500, Mattthew Gabeler-Lee wrote:
Package: minicom
Version: 2.6.1-2
Severity: normal
Apparently the maximum length of a device name for minicom is 80 chars.
This does not play well at all with the udev symlinks in /dev/serial/by-id,
which are very handy
Hi,
On Mon Jan 07, 2013 at 19:23:14 +, Sascha Silbe wrote:
Package: minicom
Version: 2.6.1-1
Severity: normal
Dear Maintainer,
123456789012345678901234567890123456789012345678901234567890123456789012
minicom cuts off the name of the serial device file at the first colon,
so by-path
Package: varnish
Version: 3.0.2-2
Severity: normal
Hi,
starting varnish with umask set to 077 fails:
$ /usr/sbin/varnishd -P /var/run/varnishd.pid -F -a :80 -T localhost:6082 ...
child (2484) Started
Pushing vcls failed:
dlopen(./vcl.B6xCZlYB.so): ./vcl.B6xCZlYB.so: cannot open shared object
Hi,
On Sun Feb 19, 2012 at 15:31:20 -0800, Basil Nutmeg wrote:
Minicom sends ASCII BS for the `--' key by default. This means
that this key does not delete the character to the left of the
cursor when minicom is connected to a policy-conforming remote
system.
What would be an example of such
Hi,
On Fri Feb 10, 2012 at 13:01:20 +, Mike Crowe wrote:
Package: minicom
Version: 2.4-3
Severity: normal
LANG=en_GB.utf8
Minicom parameters -m -c on -8 -R utf-8
If minicom receives an invalid UTF-8 sequence from the serial port it doesn't
display any more of the characters that
Package: wmnet
Version: 1.05-17
Severity: normal
Tags: patch
Hi,
this patch fixes wmnet to continue displaying when the numbers in
/proc/net/dev increase over 32bits.
diff -ur x/wmnet-1.05/drivers.c wmnet-1.05/drivers.c
--- x/wmnet-1.05/drivers.c 2011-09-01 09:24:15.526102621 +0200
+++
Package: libc6
Version: 2.13-2
Severity: normal
Tags: sid
Hi,
static binaries that trigger loading of shared objects (libnss) fail
with the following assertion.
/tmp cat a.c
#include pty.h
#include stdlib.h
int main()
{
int a, b;
openpty(a, b, 0, 0, 0);
return (int)malloc(123);
}
/tmp gcc
On Fri Apr 08, 2011 at 15:35:41 +0200, Florian Lohoff wrote:
Hi,
when entering a single ~ in the Modem and Dialing commands
e.g. Init String or Reset String the ~ gets expanded to
the users homedir on pressing return.
For obvious reasons this is broken as the ~ is the delay character
and
On Sat Apr 02, 2011 at 21:32:34 -0700, Eugene Stemple wrote:
When minicom is invoked for a RS-232 serial port, ttyS0, it creates a lockfile
/var/lock/LCK..ttyS0 as expected. However, when a file transfer is initiated
that lockfile is removed! For example, when an ASCII upload is started an
Package: lists.debian.org
Severity: normal
Hi,
debian-user-german has a footer in every list mail that refers to
http://www.de.debian.org/debian-user-german-FAQ/. As it is not available
anymore and has been outdated anyway, please remove this FAQ footer.
Thanks,
Adam
--
Adam
tags 610511 fixed-upstream
thanks
On Wed Jan 19, 2011 at 11:27:42 +0100, Roland Stigge wrote:
Package: minicom
Version: 2.4-4
Severity: normal
Hi,
there seems to be a limit on (quoted) words to send in scripts:
sth. like:
send set xxx
tags 610512 fixed-upstream
thanks
On Wed Jan 19, 2011 at 11:17:53 +0100, Roland Stigge wrote:
Package: minicom
Version: 2.4-4
Severity: normal
Hi,
when a minicom script is run and exits, one still needs to press Ctrl-C. See
also
Hi,
On Fri Jul 30, 2010 at 01:52:39 +0200, Peter De Wachter wrote:
I've tried configuring minicom to start with local echo enabled (pu localecho
Yes in the config file), but this doesn't work. Minicom's upper layer
recognizes this setting, but it isn't passed on to the vt100 layer. The
On Thu Apr 15, 2010 at 23:47:07 +0100, David Wilson Clarke wrote:
When starting 'minicom' contents of lock file is not to Filesystem Hierarchy
Standard. FHS 2.3 states:
Thanks, I've changed it accordingly (in upstream repo).
Adam
--
Adam a...@os.inf.tu-dresden.de
On Sun Oct 11, 2009 at 16:27:52 +0200, Adam Lackorzynski wrote:
korganizer always crashes for me when I create a new calender entry by
double-clicking e.g. in the week view, add a title and klicking 'Apply'.
The crash-report reads as follows:
Application: KOrganizer (korganizer), signal
On Wed Oct 28, 2009 at 11:34:21 +0100, Lucas Nussbaum wrote:
During a rebuild of all packages in sid, your package failed to build on
amd64.
In eglibc = 2.9, getline was only defined if _GNU_SOURCE was defined.
In eglibc 2.10, getline is always defined (since it became a standard in
Package: korganizer
Version: 4:4.3.2-1
Severity: important
Hi,
korganizer always crashes for me when I create a new calender entry by
double-clicking e.g. in the week view, add a title and klicking 'Apply'.
The crash-report reads as follows:
Application: KOrganizer (korganizer), signal:
Hi,
On Tue Apr 22, 2008 at 12:29:49 +0200, Lothar Wassmann wrote:
If a script is being run after logging has been enabled and
subsequently disabled minicom crashes.
I.e:
- Enable logging to a file
- Disable logging
- Start any minicom script
= crash
I can confirm this for the etch
Package: hpoj
Version: 0.91-13.2
Severity: normal
Hi,
the ptal-init script uses 'killall' which is in package psmisc but is
not listed in the dependencies of hpoj. A missing killall makes
'ptal-init setup' fail in a strange way when trying to detect USB
devices.
Adam
--
Adam
On Fri Feb 22, 2008 at 14:14:45 +0900, Rene Pavlik wrote:
The implicit history buffer size is 2000 lines. This cannot be changed in the
menu to a bigger value than 999, since I can type 3 digits only.
Thanks, fixed in repo.
Adam
--
Adam [EMAIL PROTECTED]
Lackorzynski
On Sun Jan 13, 2008 at 06:46:57 +0300, Yuri Kozlov wrote:
char some_string[32];
but it is too small for utf8 translated Russian text (and not only Russian, I
think)
Could it be to increase up to 64 or allocated dynamically?
I increased the string in the upstream repo.
Adam
--
Adam
On Sun Jan 13, 2008 at 11:07:24 +0300, Yuri Kozlov wrote:
Patch:
--- src/config.c2007-05-12 13:12:24.0 +0400
+++ /home/yuray/tmp/minicom-2.3~rc1/src/config.c2008-01-13
08:15:31.0 +0300
@@ -847,8 +844,8 @@
mc_wprintf(w, %s %s\n, macros_enabled,
On Mon Nov 12, 2007 at 15:41:36 +0100, Petr Salinger wrote:
the current version fails to build on GNU/kFreeBSD.
It is due to usage of non-posix TCGETS.
Please use portable tcgetattr() instead.
It would also be nice if you can ask upstream
to include this changes.
Thanks, committed
merge 413934 423017
thanks
On Wed May 09, 2007 at 15:23:29 +0200, David Weinehall wrote:
Package: minicom
Version: 2.2-5
Severity: normal
Minicom crashed on me today, with the following error message:
minicom: ../iconv/loop.c:425: internal_utf8_loop_single: Assertion
`inptr - bytebuf
Hi Yasushi,
On Fri Apr 20, 2007 at 20:46:30 +0900, Yasushi SHOJI wrote:
The reason was simple. We played with variable work_dir when we draw
the screen and left along. Then, in the next iteration, realloc() was
upset because we gave the changed wrong address as the first argument.
Thanks for
On Sun Apr 15, 2007 at 08:10:07 +0200, Martin Godisch wrote:
On Sat, Mar 10, 2007 at 17:41:19 +0100, Adam Lackorzynski wrote:
If minicom is started with LANG=de_DE.UTF-8 and serial port is set
wrong (wrong Bps/Par/Bits), it crashes with the following error
message
Hallo,
On Sat Mar 24, 2007 at 15:28:17 +0100, Ludovic Rousseau wrote:
When I ask to upload a file a dialog listing the files is displayed.
Some files are missing from the listing.
I found the bug. minicom assumes that '.' and '..' files are the first
and second answers from readdir(). This
On Mon Feb 26, 2007 at 23:35:02 +0100, Adam Lackorzynski wrote:
On Mon Feb 26, 2007 at 11:41:34 -0800, Alan Ianson wrote:
Package: minicom
Version: 2.2-5
Severity: minor
Minicom on amd64 can't read a .dialdir created by minicom on i386 or
vice-versa. Some 32 - 64 bit thing?
Yes
On Thu Mar 08, 2007 at 14:04:09 +0100, Markus Meier wrote:
Am Donnerstag, 8. März 2007 10:33 schrieb Adam Lackorzynski:
On Thu Mar 08, 2007 at 00:14:07 +0100, Markus Meier wrote:
If minicom is started with LANG=de_DE.UTF-8 and serial port is set
wrong (wrong Bps/Par/Bits), it crashes
Hi,
On Thu Mar 08, 2007 at 00:14:07 +0100, Markus Meier wrote:
If minicom is started with LANG=de_DE.UTF-8 and serial port is set wrong
(wrong Bps/Par/Bits), it crashes with the following error message:
xminicom: ../iconv/loop.c:425: internal_utf8_loop_single: Zusicherung
»inptr - bytebuf
Package: powerpc-utils
Severity: important
Tags: patch
Hi,
on recent kernels like 2.6.19 nvsetenv does work anymore:
$ nvsetenv
Error reading /dev/nvram: No such file or directory
This is caused by the fact that nvsetenv tries to read from /dev/nvram
with a single read call whereas Linux only
On Mon Feb 26, 2007 at 11:41:34 -0800, Alan Ianson wrote:
Package: minicom
Version: 2.2-5
Severity: minor
Minicom on amd64 can't read a .dialdir created by minicom on i386 or
vice-versa. Some 32 - 64 bit thing?
Yes, confirmed. Alignment issue in some structures. Will see how a fix
could
tags 405219 patch
thanks
Hi,
On Tue Jan 02, 2007 at 00:01:54 +0100, Samuel Thibault wrote:
Package: minicom
Version: 2.2-4
Severity: minor
Tags: l10n
Hi,
Though they are available as mo files, french messages are not used
instead of english messages.
Indeed. I just committed the
Package: moreutils
Version: 0.10
Severity: normal
Tags: patch
Hi,
here are some more fixes to the code, esp. return checks for lib calls
as well as the removal of all macros and code duplication, thus reducing
the code size by nearly 5k (~40%).
Adam
--
Adam [EMAIL
Package: moreutils
Version: 0.9
Severity: normal
Tags: patch
$ ifdata -ph foo
ioctl: No such device
00:00:00:00:00:00
The attached patch changes the behaviour to
$ ifdata -ph foo
ioctl: No such device
without printing the bogus hwaddr.
Adam
--
Adam [EMAIL PROTECTED]
Package: moreutils
Version: 0.7
Severity: normal
Tags: patch
ifdata crashes if /proc is not mounted due to following
NULL pointer derefs. Possible patch attached, against 0.8.
I also added a check for malloc I spotted.
Adam
--
Adam [EMAIL PROTECTED]
Lackorzynski
Package: glibc
Severity: normal
Hi,
when a program is linked with the --gc-sections linker option,
the __libc_atexit section in the final binary disappears. As a
consequence the flushing on exit does not work.
$ cat x.c
#include stdlib.h
#include stdio.h
int main(void) { printf(blah\n);
Package: bins
Version: 1.1.29-1
Severity: grave
Justification: renders package unusable
Hi,
the bins script file contains paths from the build process making it
unusable because it cannot find its styles etc and therefore does not work:
~# grep tbm /usr/bin/bins
my $localePath =
Package: svnmailer
Version: 1.0.3-2
Severity: normal
Hi,
/usr/share/doc/svnmailer/README.Debian states that there's a
example configuration file in /usr/share/doc/svnmailer/examples/ but
that examples directory does not exist. Where is it?
Adam
--
Adam [EMAIL PROTECTED]
Package: unison
Version: 2.10.2-1
Severity: normal
unison fails to install with the following message because of a wrong
entry in the postinst:
Setting up unison (2.10.2-1) ...
/usr/share/doc-base/[EMAIL PROTECTED]@-manual: cannot open control file for
reading: No such file or directory
dpkg:
56 matches
Mail list logo
