Package: live-build
Severity: normal
X-Debbugs-Cc: safinas...@gmail.com
Current Live image (
https://cdimage.debian.org/cdimage/weekly-live-builds/amd64/iso-hybrid/debian-live-testing-amd64-kde.iso
)
contains file /EFI/boot/grubx64.efi , which is binary identical to the file
/usr/lib/grub/x86_6
Package: kwin-wayland
Version: 4:5.27.10-1
Severity: normal
This is X11-to-Wayland regression.
Steps to reproduce:
- Start KDE in Wayland mode
- Open konsole window
- Open chromium window
- Copy to clipboard some text from chromium
- Close chromium
- Try to paste the text to konsole
This will no
has all
needed machinery. We just need to make aptitude to treat
"Build-Depends" in similar way to "Depends"
--
Askar Safin
Package: aptitude
Version: 0.8.13-5+b1
Severity: normal
Steps to reproduce:
- Create fresh sid system
- Type "aptitude install debhelper-compat"
The command will fail with the following absolutely absurd message:
# aptitude install debhelper-compat
"debhelper-compat" is a virtual package provide
aptitude, it has advanced resolution
algorithm"
--
Askar Safin
Package: git-email
Version: 1:2.43.0-1
Followup-For: Bug #895874
X-Debbugs-Cc: jrnie...@gmail.com, safinas...@gmail.com
The bug is still present in modern versions of git-email.
I. e. after 6 years it is still not fixed.
I did some experiments and I figured that the following 3
packages should be
email.
-- Package-specific info:
** Environment settings:
INTERFACE="text"
** /root/.reportbugrc:
reportbug_version "12.0.0"
mode advanced
ui text
realname "Askar Safin"
email "safinas...@gmail.com"
no-check-uid
list-cc-me
smtphost reportbug.debian.org
-- Sy
nfigured on this computer to send mail to the Internet [y|N|q|?]?
-- Package-specific info:
** Environment settings:
INTERFACE="text"
** /root/.reportbugrc:
reportbug_version "12.0.0"
mode advanced
ui text
realname "Askar Safin"
email "safinas...@gmail.c
Package: less
Version: 590-2
Severity: normal
Fixed upstream!
Steps to reproduce:
- Execute command "echo axb | grep --color=always x | less -R"
- When less spawns, press "/", then "x", then "Enter"
"x" will disappear. This is a bug.
Fortunately, the bug is not present in latest upstream releas
Package: apt
Followup-For: Bug #229775
X-Debbugs-Cc: Johannes Schauer Marin Rodrigues , David
Kalnischkies
Johannes Schauer Marin Rodrigues:
> It feels to me like what you are describing as a bug is like saying that dash
> is buggy because it does not support arrays
David Kalnischkies:
> All th
le
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
dependent : Depends: dependency (>= 2) but 1 is to be installed
E: Unable to correct problems, you have held broken packages.
===
So, I reproduced the very same bug, but this time with fully
artifactual packages. Note that "build-dep" is not involved. Bug is
reproducible with the usual "apt-get install".
> Support for stretch ended nearly a decade ago
You mixed up stretch and squeeze. According to Wikipedia,
support for stretch ended in 2020.
--
Askar Safin
Package: apt
Version: 2.7.7
Followup-For: Bug #229775
This bug (#229775) is still reproducible with current apt version (apt 2.7.7).
The bug
can be summarized so: "apt-get build-dep" fails to install a package from a repo
if its priority is slightly less than priority of installed release. In mor
I did some experiments and wrote a patch!
Okay, so, I spend some more time thinking about this. And I think the
bug is in apt's completion scripts. Because that *.bin files are
simply cache. And lack of caches should not break program! This
follows from my interpretation of FHS 3.0 5.5 (
https://r
On Fri, May 5, 2023 at 8:53 PM Tianon Gravi wrote:
> To be clear, there was nothing _certain_ in my response, merely that
> my first impression matched Cyril's for the very similar issue on d-i.
Okay, sorry for misunderstanding.
--
Askar Safin
nd in official docker image) to "working slowly".
Also, "working slowly" is just minor annoyance. But "not working"
means that the user doesn't know how to fix. Yes, merely calling
"apt-get install apt" will regenerate caches (in d-i case, not in
docker case), but how the user should know this? The solution is not
discoverable
--
Askar Safin
Current apt behavior also breaks official debian docker images, I
reported this here:
https://github.com/debuerreotype/debuerreotype/pull/153 . The images'
developer said this is apt completion scripts' problem
--
Askar Safin
Четверг, 20 апреля 2023, 23:33 +03:00 от "Cyril Brulebois" :
> Clearly one of these.
It seems apt completion is located in
/usr/share/bash-completion/completions/apt, which belongs to apt package.
So, anyway this belongs to apt package, so I reassigned
==
Askar Safin
Package: debian-installer
Severity: normal
Tags: d-i
Steps to reproduce:
- Install debian using recently published debian-bookworm-DI-
rc1-amd64-netinst.iso
- At first boot as a very first thing to do type "apt-get install a" (as
root, in normal root login shell)
- You will see that bash-completio
/root/.bashrc . I can write a
patch, if you want.
--
Askar Safin
-completion there, which CC
you: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=275623#58 .
--
Askar Safin
This will fix other possible "user vs root" bugs.
Currently /root/.bashrc doesn't have any non-comment lines, i. e. it
doesn't contain anything useful anyway.)
(Also this time I got your email properly.)
--
Askar Safin
ry to report this to bugs.debian.org bug tracker
--
Askar Safin
Package: bash-completion
Version: 1:2.11-6
Severity: normal
X-Debbugs-Cc: safinas...@gmail.com
bash-completion (for example, "apt-get inst") doesn't work for root in
non-login shell on default settings. Completion works for normal users.
And completion works in login shells.
-- System Informati
Package: debbugs
Severity: normal
I just reported bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034563 .
After some minutes I got confirmation e-mail titled "Bug#1034563:
Acknowledgement (login: "su" doesn't put /sbin and /usr/sbin to PATH)"
This e-mail contained a link " https://bugs.d
Package: login
Version: 1:4.13+dfsg1-1
Severity: normal
X-Debbugs-Cc: safinas...@gmail.com
Steps to reproduce:
user@92fe0070d0e9:~$ echo $PATH
/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
user@92fe0070d0e9:~$ su
Password:
root@92fe0070d0e9:/home/user# echo $PATH
/usr/local/bin:/
I just tested this bug using packages from https://apt.llvm.org/ . I see
that the bug reproduces with lldb-15, but doesn't reproduce with
lldb-16. So let's just wait when lldb 16 enters debian, and the bug
will be hopefully fixed
--
Askar Safin
Package: lldb-15
Version: 1:15.0.7-1
Severity: normal
X-Debbugs-Cc: safinas...@gmail.com
Consider this fragment from "man lldb-15":
Passing one of the attach options causes lldb to immediately
attach to the given process.
lldb -p lldb -n
Passing
Package: lldb-15
Version: 1:15.0.7-1
Severity: normal
X-Debbugs-Cc: safinas...@gmail.com
Here are steps to reproduce (in form of Dockerfile):
FROM debian:sid
ENV LC_ALL C.UTF-8
RUN apt-get update && apt-get install -y whiptail apt-utils
RUN apt-get update && apt-get install -y clang-15 lldb-15
RU
list-cc-me is set
>
> Closes: #1023786
>
>
> (this message was generated automatically)
> --
> Greetings
>
> https://bugs.debian.org/1023786
--
Askar Safin
fic info:
** Environment settings:
INTERFACE="text"
** /root/.reportbugrc:
reportbug_version "11.5.1"
mode expert
ui text
realname "Askar Safin"
email "safinas...@gmail.com"
no-check-uid
no-cc
list-cc-me
smtphost reportbug.debian.org
-- System Information:
Debian
:
reportbug_version "11.5.1"
mode advanced
ui text
realname "Askar Safin"
email "safinas...@gmail.com"
no-check-uid
no-cc
list-cc-me
smtphost reportbug.debian.org
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (500, 'testing'
introduced in this commit:
https://salsa.debian.org/reportbug-team/reportbug/-/commit/9df3e4c7096d9cc3222359a7ec582bf40bc37186
-- Package-specific info:
** Environment settings:
INTERFACE="text"
** /root/.reportbugrc:
reportbug_version "7.10.3+deb11u1"
mode advanced
ui text
realname "Askar Safin"
emai
ument it.
Reopening bug.
> Holger
--
Askar Safin
Package: debian-installer
Severity: normal
Tags: d-i
X-Debbugs-Cc: safinas...@gmail.com
I'm trying to install bullseye fully automatically using netboot with
pressed.cfg embedded in initramfs.
I wonder how to make taskel to install default set of packages. If I don't
mention tasksel in preseed
a
some editor.
-- Package-specific info:
** Environment settings:
INTERFACE="text"
** /root/.reportbugrc:
reportbug_version "7.10.3+deb11u1"
mode standard
ui text
realname "Askar Safin"
email "safinas...@gmail.com"
no-check-uid
no-cc
list-cc-me
smtphost reportbug.de
Package: apt-cacher-ng
Version: 3.7.4-1+b2
Severity: normal
X-Debbugs-Cc: safinas...@mail.ru
Steps to reproduce:
1. Install apt-cacher-ng in its default configuration
2. Make sure d-i.debian.org is not present in wget's HSTS database by running
'rm -f "$HOME/.wget-hsts"'
3. Run "http_proxy=http:/
Package: debian-installer
Severity: normal
Tags: d-i
I just downloaded this file:
http://deb.debian.org/debian/dists/sid/main/installer-
amd64/current/images/netboot/debian-installer/amd64/initrd.gz
Its /etc/udebs-source is bookworm (this is current testing) instead of sid, but
I downloaded this
should add aptitude to extract list, i. e. aptitude
should be extracted at extract stage. --foreign runs extract stage, so
--foreign should extract aptitude. But it doesn't. So man page (or debootstrap
output or debootstrap itself) is wrong.
So, we anyway have a bug either in debootstrap imp
to USB storage device).
Please, fix this bug. Fix is simple, benefits for many users are big. (So I
change severity.)
I think eatmydata mode should be enabled by default in debootstrap. Both inside
of d-i and outside of it.
==
Askar Safin
https://github.com/safinaskar
ch file or
directory
I will state again that this bug can be fixed either by changing code, either
by changing documentation.
I can explain problem another way, if you still don't understand.
==
Askar Safin
https://github.com/safinaskar
Oops, s/eproxy/epoxy/. And it is already packaged
Package: xdg-desktop-portal-kde
Version: 5.14.5-1
Severity: normal
This package is build with SCREENCAST_ENABLED as false. Thus screencast
functionality is currently disabled. Please,
fix this. It seems this would require packaging libeproxy for debian
-- System Information:
Debian Release: bull
Package: debootstrap
Version: 1.0.115
Severity: normal
It is known that debootstrap first extracts packages without writting to dpkg
database
using "dpkg-deb" or "ar" and then unpacks and configures packages using more
high-level
methods.
I will refer to that low-level stage (when we extract pa
Package: bison-doc
Version: 1:3.2.2-1
Severity: normal
/usr/share/doc/bison-doc/examples doesn't contain Makefiles, READMEs and other
such information, which may be of interest for user. It should contain all
info, which is installed by upstream package by "make install". Relevant thread
starts
Package: chromium
Version: 67.0.3396.87-1~deb9u1
Followup-For: Bug #900533
My system is Debian Stretch amd64. My sources.list is this:
===
deb http://mirror.yandex.ru/debian stretch main non-free contrib
deb-src http://mirror.yandex.ru/debian stretch main non-free contrib
deb http://secur
, please fix the bug immediately!!! And make it install to usual Stretch
installations (with stable and stable-security repos enables) in next upgrade.
This is very important, so I sent this widespread mail.
==
Askar Safin
http://vk.com/safinaskar
Package: fakeroot
Version: 1.21-3.1
Severity: important
Tags: upstream
fakeroot and fakechroot are very unreliable. Just look at other bug reports.
Even simple "env -i" (such commands are likely in building utils) unexpectedly
turn off fakeroot.
Other thing incompatible with fakeroot is static li
Package: debian-live
Severity: important
THIS BUG FORCED me to reinstall my system!!!
I got Debian Live Stretch KDE using this link:
https://cdimage.debian.org/images/unofficial/non-free/images-including-firmware/current-live/amd64/iso-hybrid/debian-live-9.3.0-amd64-kde+nonfree.iso
MD5 sum starts
Package: unzip
Version: 6.0-21
Severity: normal
There are two kinds of shell utils. Some understand "--" and threat all
arguments after it as non-options (this utils are good).
Some don't understand "--" and try to threat it as normal option or as normal
operand (this utils are bad, but they exi
rmed untrusted Debian packages may still cause leaked files?
==
Askar Safin
http://vk.com/safinaskar
Also, FreeBSD's tar has option "--chroot". And (if I remember correctly) it is
used in installation process. (Also, please see my previous letter in this bug
report if you missed it.)
==
Askar Safin
http://vk.com/safinaskar
/lib64/ld-linux-x86-64.so.2 is symlink and it points to file
/lib/x86_64-linux-gnu/ld-2.13.so , which is non-existent on host. So, now
host's dynamic linker name ( /lib64/ld-linux-x86-64.so.2 , hardcoded into
nearly all dynamic binaries) is symlink to non-exist file.
==
Askar Safin
http://vk.com/safinaskar
Same for buster. I. e. if I replace sid virtual machine with buster virtual
machine, I got the same bug. I mean that I created buster from the same alpha 1
installer, but this time I didn't upgrade it to sid.
==
Askar Safin
http://vk.com/safinaskar
Package: src:linux
Version: 4.13.10-1
Severity: important
Current (2017-11-14 - 2017-11-15) sid with up-to-date kernel (4.13.0) cannot
"chroot" into squeeze chroot environment.
What I did?
* I started qemu-system-x86_64 (debian package qemu-system-x86
1:2.8+dfsg-6+deb9u3) from my host system (
Package: base-files
Version: 9.9+deb9u1
Severity: normal
It seems public SCM for base-files is not available. When I type "apt-get
source base-files" I don't see something like "'base-files' packaging is
maintained in the ... version control system". Please provide some public SCM.
For example,
Thanks, but https://www.kernel.org/doc/Documentation/filesystems/ext4.txt seems
still to contain bug. If you want, I will send separate bug report to kernel
bugzilla
Package: apt
Version: 1.4.7
Severity: normal
I just wrote this to sources.list:
deb https://deb.debian.org/debian stretch main
deb https://deb.debian.org/debian-security stretch/updates main
And then I run "apt-get update". I saw:
# apt-get update
0% [Working]
I waited, and waited and waited.
Package: dash
Version: 0.5.8-2.4
Severity: normal
Tags: upstream
dash$ type -- ls
--: not found
ls is /bin/ls
"type" doesn't threat "--" specially. But POSIX 2016 edition says it should.
Also, all your builtins mentioned in POSIX (be it "special built-in utility" or
normal utility) should threa
Package: bash
Version: 4.4-5
Severity: normal
Tags: upstream
https://www.gnu.org/software/bash/manual/bash.html says this: "Unless otherwise
noted, each builtin command documented as accepting options preceded by ‘-’
accepts ‘--’ to signify the end of the options. The :, true, false, and test
b
Package: bash
Version: 4.4-5
Severity: normal
Tags: upstream
Type this to bash:
cat <(printf '%s' $'\177ELF') > file-1
and this:
printf '%s' $'\177ELF' > file-2
Resulting files will be different. file-1 will contain 5 bytes (as opposed to
expected 4)
-- System Information:
Debian Release: 9.
Package: dash
Version: 0.5.8-2.4
Severity: normal
man dash describe dash builtins wrong. In particular it doesn't describe
"false". Please, double-check that man's builtin list correspond to actual.
-- System Information:
Debian Release: 9.0
APT prefers stable
APT policy: (500, 'stable')
Arc
Documentation/filesystems/ext4.txt contains this:
commit=nrsec(*) Ext4 can be told to sync all its data and metadata
every 'nrsec' seconds. The default value is 5 seconds.
This means that if you lose your power, you will lose
It seems https://www.kernel.org/doc/Documentation/filesystems/ext4.txt has the
same issue?!
Package: e2fsprogs
Version: 1.43.4-2
Severity: normal
Tags: upstream
Hi. Currently "commit" for ext3 documented so:
.BI commit= nrsec
Sync all data and metadata every
.I nrsec
seconds. The default value is 5 seconds. Zero means default.
And in the beginning of ext4:
The options
.B journal_dev
>For 4.0, it is in NEW:
>https://ftp-master.debian.org/new/llvm-toolchain-snapshot_1:4.0~svn291432-1.html
Where can I download it? And why it is still not in sid? Why you just uploaded
fix to lldb-3.9 and it fastly went to sid and I still cannot download this
lldb-4.0?
==
Askar Safi
Same for this more complicated example:
#include
std::string
f (void)
{
printf ("a\n");
return "";
}
int
main (void)
{
printf ("%s\n", f ().c_str ());
}
==
Askar Safin
http://vk.com/safinaskar
Package: gdb
Version: 7.12-4
Severity: grave
Justification: renders package unusable
Steps to reproduce:
* Create this file /h.cpp:
#include
std::string
f (void)
{
return "";
}
int
main (void)
{
f ();
}
* Then:
root@ideal-os:/# g++ -g -o h h.cpp
root@ideal-os:/# gdb ./h
GNU gdb (Debian
reassign 846612 lldb-3.8 1:3.8.1-16
fixed 846612 1:3.8.1-17
thanks
Okey, I created separate bug. (But it seems it can be solved just by adding
that python-lldb-xx dependency.)
==
Askar Safin
http://vk.com/safinaskar
Package: lldb-3.9
Version: 1:3.9.1-2
Severity: normal
Steps to reproduce:
* Create fresh minimal debian sid
* Create apt.conf with APT::Install-Recommends "false";
* Install lldb-3.9 and clang-3.9
* Then:
root@ideal-os:/# cat o.cpp
#include
int
main (void)
{
std::vector a;
a.push_back (0);
cent call last):
File "", line 1, in
NameError: name 'run_one_line' is not defined
Traceback (most recent call last):
File "", line 1, in
NameError: name 'run_one_line' is not defined
(std::vector >) $0 = size=1 {
std::_Vector_base > = {
_M_impl = {
_M_start = 0x00615c20
_M_finish = 0x00615c24
_M_end_of_storage = 0x00615c24
}
}
}
(lldb)
==
Askar Safin
http://vk.com/safinaskar
reassign 846616 lldb-3.7 1:3.7.1-3
thanks
Thanks for fixing. The bug is still present in lldb-3.7 1:3.7.1-3 and in
lldb-4.0 1:4.0~svn290810-1 in sid
==
Askar Safin
http://vk.com/safinaskar
following arguments, so use it as the last option.
And still my version of konsole has this bug.
==
Askar Safin
Package: tar
Version: 1.29b-1.1
Severity: normal
I wanted to create archive. I typed:
$ sudo tar --one-file-system --same-owner --numeric-owner -cpf /tmp/x.tar .
And I saw:
tar: /tmp/x.tar: Wrote only 8192 of 10240 bytes
tar: Error is not recoverable: exiting now
Then I discovered that tar fil
Package: tar
Version: 1.29b-1.1
Severity: normal
"man tar" says:
--preserve
Same as both -p and -s.
But "tar" itself doesn't support this option:
$ tar --preserve -cf /tmp/a.tar /etc/fstab
tar: option '--preserve' is ambiguous; possibilities: '--preserve-permissions'
'--preserve-
Package: lldb-3.8
Version: 1:3.8.1-16
Severity: grave
Justification: renders package unusable
lldb 3.8 freezes after "run". Same for lldb 3.9 in stretch. Details:
http://bugs.debian.org/846531
Package: lldb-3.8
Version: 1:3.8.1-16
Severity: important
(lldb) r
error: process launch failed: unable to locate lldb-server
Details: http://bugs.debian.org/846531. Same for lldb 3.9 and maybe lldb 3.7.
Package: lldb-3.8
Version: 1:3.8.1-16
Severity: normal
debian:~# lldb-3.8 ./a
Traceback (most recent call last):
File "", line 1, in
ImportError: No module named lldb.embedded_interpreter
(lldb) target create "./a"
Current executable set to './a' (x86_64).
(lldb)
See http://bugs.debian.org/846
>Please report a bug per issue. It is too hard to track otherwise.
Is this okey if I create several bugs which differ in title and all point to
this bug?
==
Askar Safin
http://vk.com/safinaskar
Package: lldb-3.8
Version: 1:3.8.1-16
Severity: grave
Justification: renders package unusable
lldb 3.8 is unusable is Stretch. Here is list of bugs. Most of them apply to
lldb 3.9, too. Some of them apply
to lldb 3.7, too, but lldb 3.7 is somewhat usable unlike lldb 3.8 and lldb 3.9.
Steps to re
Package: apt
Version: 1.0.9.8.3
Followup-For: Bug #435069
The bug still exists in my version of apt. If there is no space on device,
apt-get update prints:
Ign http://192.168.1.64:3142 jessie InRelease
Hit http://192.168.1.64:3142 jessie Release.gpg
Hit http://192.168.1.64:3142 jessie Release
Hi
Package: rsync
Version: 3.1.1-3
Severity: normal
The following command does not autocomplete:
rsync root@host:'dat' /
bash-completion is installed. The following is uncommented in /etc/bash.bashrc:
if ! shopt -oq posix; then
if [ -f /usr/share/bash-completion/bash_completion ]; then
. /usr/
Package: coreutils
Version: 8.23-4
Severity: normal
Type the following:
du --exclude='*.jpg' /
You will see that doesn't autocomplete. "du /" works normally.
bash-completion is installed. The following is uncommented in /etc/bash.bashrc:
# enable bash completion in interactive shells
if ! shopt
Package: iputils-ping
Version: 3:20121221-5+b2
Severity: normal
I downloaded Debian Live from this link:
http://cdimage.debian.org/debian-cd/current-live/amd64/iso-hybrid/debian-live-8.5.0-amd64-kde-desktop.iso
I booted into this KDE live system, opened Konsole terminal emulator, typed
"ping debi
Package: systemd-container
Version: 230-5
Severity: normal
Steps to reproduce:
Download stretch alpha 7 installer, install it using qemu, then in this fresh
scretch system install debootstrap and
systemd-container.
Then run:
# debootstrap stretch /str http://10.0.2.2:3142/debian
(URL here is just
you want some more info, then just ask. I can easily create small debian
system and run it using chroot or systemd-nspawn or qemu and perform some
experiments on it.
==
Askar Safin
Package: apt-cacher-ng
Version: 0.9.3.1-1
Severity: important
Default behavior of CacheDir on Debian is really weird and annoying.
Steps to reproduce:
* Install apt-cacher-ng typical way ("apt-get install apt-cacher-ng") on sid.
You will notice that no interactive debconf will be run during this
any more.
Also, please, make whole /etc/skel be copied into /root at installation time.
This will merge /etc/skel/.bashrc with /root/.bashrc and same for .profile etc.
==
Askar Safin
Package: python-lldb-3.9
Version: 1:3.9~svn262954-1
Severity: normal
I just created fresh Debian sid chroot environment using my tool similar to
debootstrap. I installed clang-3.9 and lldb-3.9 and started lldb. It showed me
error message about missing python module "six". So, please, mention
"p
What option I should use to install some package to chroot environment? RootDir
or Dir?
==
Askar Safin
http://vk.com/safinaskar
>Thanks for the patch, but you haven't really told us about your usecase
>with c++ in a d-i context.
Any C library should allow including from C++. My usecase is following: I wrote
my own analogue of debootstrap/cdebootstrap called asdebootstrap ("as" for
Askar Safin, of c
Patch for source package libdebian-installer 0.99+deb8u1.
==
Askar Safin
http://vk.com/safinaskar
diff -Naur libdebian-installer-0.99+deb8u1/include/debian-installer/exec.h
new/include/debian-installer/exec.h
--- libdebian-installer-0.99+deb8u1/include/debian-installer/exec.h
2014-11-05 01
Package: libdebian-installer4-dev
Version: 0.98
Severity: normal
I cannot build C++ programs using this library. G++ shows a lot of errors and
warnings.
/usr/include/debian-installer/package.h:32:14: error: use of enum
‘di_package_dependency_type’ without previous declaration
typedef enum di_p
> do you experience the same behavior when running nano by itself (i.e.
> not spawn by reportbug) in konsole?
No
nano becomes corrupted.
ii nano 2.2.6-1+b1 amd64
ii konsole 4:4.8.4-2 amd64
-- Package-specific info:
** Environment settings:
INTERFACE="text"
** /root/.reportbugrc:
reportbug_version "6.4.4"
mode advanced
ui t
Package: okular
Version: 4:4.8.4-3+b1
Severity: normal
Tags: l10n
Steps to reproduce:
* Create the following file tex.tex:
\documentclass[a4paper]{article}
\usepackage[russian]{babel}
\begin{document}
Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed ...
\end{document}
* pdflatex tex.t
bison suggests:
pn bison-doc
-- no debconf information
==
Askar Safin
http://vk.com/safinaskar
Kazan, Russia
ion will be uploaded to Debian. So, I will not close the bug (right?).
==
Askar Safin
http://vk.com/safinaskar
Kazan, Russia
>> Please stop mischaracterizing the issue. It's not a bug: it's a case of
>> konsole's mismatched expectations. Since the mechanism it uses is not
>> documented, and relies on something in readline that is not documented, it
>> can't fairly be called a bug.
>Should long text line move when user
> Please stop mischaracterizing the issue. It's not a bug: it's a case of
> konsole's mismatched expectations. Since the mechanism it uses is not
> documented, and relies on something in readline that is not documented, it
> can't fairly be called a bug.
Should long text line move when user chang
rminal + bash 4.2 | bad | good
gnome-terminal + bash 4.3 | bad | bad
konsole + bash 4.2| good | good
konsole + bash 4.3| bad | bad
(And this gnome-terminal may be too old, i. e. Pádraig Brady just reported his
gnome-terminal works, he probably uses newer version.)
==
Askar Safin
http://vk.com/safinaskar
Kazan, Russia
1 - 100 of 130 matches
Mail list logo
