Package: reportbug
Version: 7.10.3+deb11u1
Followup-For: Bug #1016009
X-Debbugs-Cc: debbug.report...@sideload.33mail.com
Control: tags 1016009 + a11y
You have misunderstood the purpose of the --paranoid option. The
purpose of this option is to enable users to mitigate data leaks by
checking the in
Package: reportbug
Version: 7.10.3+deb11u1
Severity: normal
X-Debbugs-Cc: debbug.report...@sideload.33mail.com
When a bug is archived, reportbug still accepts user input for that
bug, then falls over when the SMTP server blocks the message. There
are a few bugs in this scenario.
(bug 1)
The doc
Package: gnucash
Version: 1:4.4-1
Severity: normal
X-Debbugs-Cc: debbug.gnuc...@sideload.33mail.com
Upstream devs have requested a stack trace from me, which is
documented here:
https://wiki.gnucash.org/wiki/Stack_Trace
Running “aptitude search gnucash” indicates that there are no packages
nam
Package: ghostscript
Version: 9.53.3~dfsg-7+deb11u2
Followup-For: Bug #1016424
X-Debbugs-Cc: debbug.1016...@sideload.33mail.com
> Therefore please report the issue upstream.
I just happened to have an account on the upstream bug tracker that
still works, so I reported here:
https://bugs.ghosts
Package: ghostscript
Version: 9.53.3~dfsg-7+deb11u2
Severity: normal
X-Debbugs-Cc: debbug.ghostscr...@sideload.33mail.com
Ghostscript fails to convert PBM files to PDF. Attempts were made with
3 different PBM files:
1) scanner-made PDF → (pdfimages -all) → (unpaper) → PBM →
(ghostscript/pdfwri
Package: rsync
Version: 3.2.3-4+deb11u1
Severity: critical
Justification: causes serious data loss
X-Debbugs-Cc: debbug.rs...@sideload.33mail.com
I accidentally ran:
$ rsync -va --progress --remove-source-files "$dir_with_many_files"
"$dir_with_many_files"
Due to a typo when using bash histor
Package: tootle
Followup-For: Bug #1014374
X-Debbugs-Cc: debbug.1014...@sideload.33mail.com
I should also mention that it’s important that tootle uses the
XDG_CONFIG_HOME variable when referencing the config file. If not, and
the config file path is hardcoded to include a directory that the user
h
Package: tootle
Followup-For: Bug #1014374
X-Debbugs-Cc: debbug.1014...@sideload.33mail.com
Control: block 1014374 by 1016015
Control: severity 1014374 minor
Control: retitle 1014374 Accounts cannot be added when running in Firejail
Control: summary 1014374 This is possibly not a bug in tootle. It
Package: firejail
Version: 0.9.64.4-2
Severity: important
X-Debbugs-Cc: debbug.firej...@sideload.33mail.com
Control: affects 1014374 + tootle
The command tootle was first executed outside firejail to establish a
working config file. This was motivated to work around bug
1015816. After tootle prove
Package: firejail
Version: 0.9.64.4-2
Followup-For: Bug #1015816
X-Debbugs-Cc: debbug.1015...@sideload.33mail.com
To cover all bases, I also tried enabling the read-write perms,
effectively running:
$ firejail --env=XDG_CONFIG_HOME="$HOME"/my_config_files\
--whitelist="$(readlink $
Package: firejail
Version: 0.9.64.4-2
Followup-For: Bug #1015816
X-Debbugs-Cc: debbug.1015...@sideload.33mail.com
It was an interesting suggestion but in the end it made no
difference. And in fact the test inspires a feature request.
I created /tmp/toot.profile as follows:
===8<-
Package: reportbug
Version: 7.10.3+deb11u1
Severity: wishlist
Tags: a11y
X-Debbugs-Cc: debbug.report...@sideload.33mail.com
Using the --paranoid option shows the text of the bug report before
transmission. In my case, the body is usually base64 encoded, which
means only the headers are readible to
.3"
mode advanced
ui text
realname "anonymous coward"
email "tripr@a5dkbvgakon2lxmauleiizkv6i3s36wp6w3i32a3buc4xmtdnbttmryd.onion"
no-cc
list-cc-me
smtphost reportbug.debian.org
-- System Information:
Debian Release: 11.4
APT prefers stable-updates
APT policy: (990,
Package: reportbug
Version: 7.10.3+deb11u1
Followup-For: Bug #880877
X-Debbugs-Cc: debbug.880...@sideload.33mail.com
>> When reportbug is used as a direct SMTP client , reporting user
>> hostname , ip and username are leaked to the BTS.
>
> well, that's how mail transport systems work
Different
ge your locale if this is incorrect.
Using 'anonymous coward
' as your
from address.
Will send report to Debian (per lsb_release).
Spawning emacs...
1658731267 WARNING torsocks[21486]: [syscall] Unsupported syscall number 315.
Denying the call (in tsocks_syscall() at syscall.c:604)
Package: firejail
Followup-For: Bug #1015151
X-Debbugs-Cc: debbug.1015...@sideload.33mail.com
I did another test, this time ensuring that the profile was read:
$ firejail --net=vnet0 --dns="$(ip address show dev vnet0 | awk
'/inet\>/{gsub(/[/].*/,""); print $2 }')"\
--profile=<(pr
Package: firejail
Version: 0.9.64.4-2
Severity: normal
X-Debbugs-Cc: debbug.firej...@sideload.33mail.com
The app “toot” generally needs to create and access this config file:
~/.config/toot/config.json
For organizational and backup reasons, I’ve taken these steps
(in effect):
$ mv ~/.config
Package: toot
Version: 0.27.0-1
Severity: minor
X-Debbugs-Cc: debbug.t...@sideload.33mail.com
The default config file is apparently ~/.config/toot/config.json, but
this is not mentioned in the man page. The man page should also
mention how to change which config file is used, if possible. It
shou
Package: firejail
Followup-For: Bug #1015151
X-Debbugs-Cc: debbug.1015...@sideload.33mail.com
I tried the suggestion and it made no difference, but I suspect I have
a separate problem with local profiles. I first looked through the
man page for a commandline equivalent to “ignore noroot” and foun
Package: firejail
Followup-For: Bug #1015151
X-Debbugs-Cc: debbug.1015...@sideload.33mail.com
When doing this upgrade:
0.9.64.4-2 → 0.9.64.4-2+deb11u1
~50+ or so other packages were upgraded at the same time which could
have theoretically changed the Tor middlebox. So more testing was
needed t
Package: firejail
Version: 0.9.64.4-2+deb11u1
Severity: important
X-Debbugs-Cc: debbug.firej...@sideload.33mail.com, t...@security.debian.org
This upgrade introduced a segmentation fault:
firejail:amd64 0.9.64.4-2 → 0.9.64.4-2+deb11u1
This is a sample command where it fails:
$ firejail --ne
Package: tootle
Version: 1.0-alpha2-1
Severity: normal
X-Debbugs-Cc: debbug.too...@sideload.33mail.com
When a status/toot is composed, the user is given no control over what
populates the “application” field. This adds to users’
fingerprints.
I’ve been doxxed and it was revealed that the user age
Package: tootle
Version: 1.0-alpha2-1
Severity: normal
X-Debbugs-Cc: debbug.too...@sideload.33mail.com
Everytime I added a new account, tootle failed to launch a browser for
the Oauth URL. Most normal users would be totally stumped at this
point because the GUI gives no indication that there was a
Package: tootle
Version: 1.0-alpha2-1
Severity: normal
X-Debbugs-Cc: debbug.too...@sideload.33mail.com
I have been able to add 4 accounts, shutdown the app, relaunch, and
the 4 accounts are remembered just fine. But when a 5th account is
added, it is accepted and it functions just for the session
Package: tootle
Version: 1.0-alpha2-1
Severity: normal
X-Debbugs-Cc: debbug.too...@sideload.33mail.com
Steps to reproduce:
1. Click the search icon and manually enter your own pseudonym by hand (since
there is no other way to view one’s own timeline)
2. Click the /more/ icon (stacked dots) & cho
t know
what package the bug is in, please contact debian-u...@lists.debian.org for
assistance.
> firejail
*** Welcome to reportbug. Use ? for help at prompts. ***
Note: bug reports are publicly archived (including the email address of the
submitter).
Detected character set: UTF-8
Please change your locale
Package: reportbug
Version: 7.10.3
Followup-For: Bug #810933
X-Debbugs-Cc: bug810...@sideload.33mail.com
I concur that SMTP proxying would be useful.
I also have a workaround using firejail. Firejail makes it possible to
restrict an app to a network namespace. So if you can configure your
proxy t
t sure if the impact
is significant.
-- Package-specific info:
** Environment settings:
EDITOR="emacs"
INTERFACE="text"
** /home/blee/.reportbugrc:
reportbug_version "7.10.3"
mode advanced
ui text
realname "anonymous coward"
no-cc
list-cc-me
smtphost reportbug.d
Package: wvdial
Version: 1.61-5
Severity: normal
X-Debbugs-Cc: debbug.wvd...@sideload.33mail.com
Connecting using a GSM mobile broadband USB modem succeeds but there
are errors during the PPP handshake. When the “debug” option is
uncommented in /etc/ppp/options as well as the “-detach” option, th
Package: wvdial
Version: 1.61-5
Followup-For: Bug #444714
X-Debbugs-Cc: bug639...@sideload.33mail.com
Indeed the README still shows semicolons to designate comments. So the
README still needs to be updated. I find that the hash symbol works
for comments so that’s the workaround.
-- System Inform
Package: ppp
Version: 2.4.9-1+1
Followup-For: Bug #639368
X-Debbugs-Cc: bug639...@sideload.33mail.com
When the following options are supplied in /etc/ppp/options prior to
running wvdial:
* debug
* -detach
* nodetach
output is normal (non-verbose). It’s unclear if this is the same bug
as the 11 y
ackage-specific info:
** Environment settings:
EDITOR="emacs"
INTERFACE="text"
** $HOME/.reportbugrc:
reportbug_version "4.12.6"
mode novice
ui text
realname "anonymous coward"
email "marc.carter-ceqo...@cool.fr.nf"
-- System Information:
Debian Releas
Package: slrn
Version: 1.0.0~pre18-1.1
Severity: normal
Launching after previously sending a SIGQUIT reports the following:
Connected to host. Posting ok.
Checking news ...
* The autosave file of /home/user/.jnewsrc is newer than the file itself.
Do you want to restore your newsrc fro
Package: mutt
Version: 1.5.20-9+squeeze2
Severity: normal
This version of mutt now reports new mail on mbox files where mail was
already read. The "N" marker is cleared upon opening a file and
returning to the pager, but the marker does not stick. Entering
another file marked with NEW messages
Package: mutt
Version: 1.5.20-9+squeeze2
Severity: wishlist
When the shutdown scripts run as part of a shutdown by the
administrator, users lose their changes. There is currently nothing
that can be added to the shutdown scripts in /etc/init.d/ to initiate
a graceful shutdown of users mutt insta
Package: bash
Version: 4.1-3
Severity: normal
This command works:
duplicity full -vinfo --dry-run --no-encryption --include /etc/resolv.conf
--exclude '**' /etc/ file:///tmp/
but when quoting is used to store the exclude option inside a
variable, the variable does not render properly. There
Package: slrn
Version: 1.0.0~pre18-1.1
Severity: minor
If the configuration file has this option:
server "nntp.aioe.org" ".jnewsrc-aioe"
it should use the .jnewsrc-aioe file whenever that server is accessed.
However, if the server is set as:
export NNTPSERVER="snews://nntp.aioe.org:563";
s
Package: texlive-full
Version: 2009-11
Severity: normal
When graphicx.sty and invoice.sty are both used by the same document, this
error results:
> ...
> (/usr/share/texmf-texlive/tex/latex/invoice/invoice.def))
> (/usr/share/texmf-texlive/tex/latex/graphics/graphicx.sty
>
> ! LaTeX Error: Missi
Package: texlive-full
Version: 2009-11
Severity: normal
The invoice package is supposed to be included in texlive according to
this documentation:
http://www.math.washington.edu/tex-archive/help/Catalogue/entries/invoice.html
It has been included in the past, but suddenly it is missing. This
Package: boinc-client
Version: 7.0.24+dfsg-1
Followup-For: Bug #669208
Hello,
I'm not familiar with Debian's policies and goals but I think the main problem
is not the point at which boinc-client starts automatically but that this point
is not configurable by the user.
How about simply picking
Package: iceweasel
Version: 3.5.16-14
Severity: normal
When visiting https://www.linuxquestions.org, the padlock icon is (rightly)
closed, with a bang and a warning about some content being unauthenticated (as
it should). However, when clicking the favicon, the statement "Your connection
to th
Package: rtorrent
Version: 0.8.6-1
Severity: minor
Sometimes rtorrent loses the ratio across restarts. Seems random. After a
shutdown and restart, the ratio will be 0.0 on some torrents that had a higher
ratio. This ratio reset does not impact all torrents at once -- the ratio is
preserved
Package: boinc-client
Version: 7.0.24+dfsg-1
Severity: normal
Dear Maintainer,
update-rc.d refuses to make boinc-client start automatically at boot and I can
see no way to bypass those warnings:
~# update-rc.d boinc-client defaults
update-rc.d: using dependency based boot sequencing
update-rc.d
Package: gnome-desktop-environment
Version: 1:2.30+7
Severity: wishlist
There is already an icon in the tray showing power level. Even when the power
level is evident in that icon, there is still a disurbing popup nag to give
redundant information. The preferences give no way to disable this a
Package: mutt
Version: 1.5.20-9+squeeze2
Severity: normal
Sending messages from the commandline has been recently broken (this worked in
previous versions). Example:
mutt -a $HOME/.bashrc -s "trying to send a file" mym...@email.com <<< "simply
sending a file"
No recipients specified.
In t
Package: multitail
Version: 5.2.2-2
Severity: normal
The documentation states that width of one column can be omitted, as
one would expect, to assign whatever width is available to that
column. Documented examples suggest that syntax like the following
would work:
$ multitail -sw 100, -R 15 -l
Package: multitail
Version: 5.2.2-2
Severity: normal
The following multitail command worked previously on debian etch, but occured
after installing debian squeeze along with the corresponding multitail version.
multitail -sw 120,80 -i file.txt -R 45 -l 'ls -1tr $(ls -d1tr $HOME|tail -n
1)/*|tai
47 matches
Mail list logo
