Public bug reported:
When running:
$ pdfimages -list grayscale-document.pdf
the output is:
```
page num type width height color comp bpc enc interp object ID x-ppi
y-ppi size ratio
These findings are with Getmail version 5.13 (the Debian Buster
distribution).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908557
Title:
getmail's "delete_after" does not delete msgs from Yahoo
Since it's unclear whether getmail is failing in the decision logic or
whether server deletes are generally a problem, a test run was done with
SimpleIMAPSSLRetriever and "delete = true". In this case, the error
results:
'No mailbox exists with name "~/mail/yahoo_deleted.mbox"'
It's lying. "ls
I tried the same test with:
delete_dup_msgids = true
type=BrokenUIDLPOP3SSLRetriever
move_on_delete=~/mail/yahoo_deleted.mbox
and then with IMAP:
type=SimpleIMAPSSLRetriever
and it made no difference. In both cases it still failed to send a DELE
command to the server. It fetches the same
Public bug reported:
Getmail is expected to delete messages older than 90 days under this
configuration:
---8<
[options]
verbose = 0
message_log = ~/logs/getmail.log
message_log_verbose = true
delete_after = 90
max_messages_per_session=10
[retriever]
I noticed that cURL gives a "wrong ssl version" type of error when the scheme
of an URL is "smtps://"; fixed by removing the 2nd "s", giving "smtp://" (even
though it's still an SSL connection). It's bizarre.
And in case anyone finds "port=110" suspicious, well, it's not a typo.
The mail server strangely expects port 110 to be used and also mandates
use of SSL (which is not theoretically necessary on Tor but that's their
deal). It works in fetchmail.
--
You received this bug notification because you
I should also mention that I'm using a debian-based OS but not Ubuntu.
I'm posting this report here because there seems to be no upstream bug
tracker and Charles Cazabon has concealed the email address for use on
the getmail project well.
--
You received this bug notification because you are a
Public bug reported:
In attempt to retrieve messages from onionmail.info using Getmail 5.13,
this output results:
getmailrc: socket error ([SSL: WRONG_VERSION_NUMBER] wrong version
number (_ssl.c:727))
The CLI command is "torsocks getmail" and this is the relevant stanza in
getmailrc:
It locked up again. This time I let it sit there in the frozen state
for ~5 minutes before powering off. It was so frozen that it did not
respond to attempts to SSH in. This time the logs show more systemd-
udevd logs at the end. The new logs are attached.
** Attachment added: "journalctl -b
Immediately after a crash and forced poweroff, I ran "journalctl -b -1",
which I've pasted below (minus the huge amount of systemd-udevd logs
which are likely irrelevant). The freeze always happens in VLC, and
indeed the logs show VLC failures at the end of the logs.
I should also note that I'm
Same problem for me. I have an old parallel-only printer. It has been
working with a dedicated printer server, but the printer server died and
the PC has no parallel port. So I connected a USB-to-LPT cable. As I
attach the cable /var/log/syslog shows:
parport0: fix this legacy no-device port
Public bug reported:
I wrote a udev rule that would not trigger when expected. I spent 2
days working on it, trying to understand what the problem was. I
finally figured it out -- it was a matching problem:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1890836
The most verbose output
Bug report to improve debugging output:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1890890
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890836
Title:
udev rule read but "RUN" command
PEBKAC
** Changed in: systemd (Ubuntu)
Status: Incomplete => Invalid
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Bill Yikes (yik3s)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
It turns out the problem arises out of cargo cult programming on my
part. The bang in KERNEL=="sd*[!0-9]" is what I copied out of
stackexchange, and it's exactly what prevents the mount from matching.
I suspected that early on, but ruled it out because when the device
first connects it must
It fails for me on two different systems:
* Ubuntu 20.04 (Focal)
* Linux Mint 19.2 (Tina, which is based on Bionic)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890836
Title:
udev rule read but
The apport-collect command does not seem to give a way to save to a
file, so there's no way for users to inspect the data before sending.
The man page for apport-collect says "Bug reports can be written to a
file by using the --save option or by using apport-cli."
The --save option is not part
Public bug reported:
The following was introduced as
"/etc/udev/rules.d/99-harvest_camera.rules":
ACTION=="add", KERNEL=="sd*[!0-9]", ENV{ID_FS_UUID_ENC}=="C355-A42D",
RUN+="/usr/bin/sudo -u bill /home/bill/scripts/harvest_camera.sh"
When the device is attached, it gets mounted but the
** Package changed: ubuntu => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889992
Title:
Ubuntu Focal Fossa freezes spontaneously -- must power off when this
happens
To manage
Notice also there is a serious transparency problem. The output only
shows files for which removal failed. This acutely heightens the
destruction because it potentially destroyed *thousands* of files as I
sat there and let it run. The tool gives no idea how what's being
destroyed. The admin
Public bug reported:
The man page for udevadm neglects to mention options which seem to only
be documented in stackexchange. E.g.
udevadm monitor --environment
udevadm control --reload-rules
>From the man page, it's unclear what the difference is between /udevadm
trigger/ and /udevadm test/.
Sorry, i mean to say /var/log/syslog (not /var/log/system) shows the
device was attached.
The verbosity in /var/log/syslog increases when udev_log=debug, but
still no /var/log/udev.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
By default udev is supposed to log to /var/log. In Ubuntu 20 it is not
logging. Logging was then explicitly enabled by uncommenting this line
in /etc/udev/udev.conf:
"udev_log=info"
After running "systemctl restart udev" and plugging in a USB drive,
there is still no udev
Still a problem in 42.2. No color-theme-* (thus no color-theme-modern
that was proposed as a replacement).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1817480
Title:
Emacs color-theme package is
Public bug reported:
I installed rygel and created a specific rygel user to run it with (as
directed by the docs). I then realized a specific user was not needed.
To reverse my steps, I ran deluser which proceeded to delete lots of
files that have nothing to do with the rygel user:
root@host:~#
I've installed Mythbuntu, which was pre-packaged with `libmythtv-perl`
-- which supports nuvexport, but apparently doesn't include all of
nuvexport. `sudo aptitude search ~dnuvexport` only finds `libmythtv-
perl`.
I wouldn't call nuvexport absolutely "essential", but it's probably the
most
Public bug reported:
I just did a fresh first-time install of Ubuntu on a Dell Inspirion 14
with no modifications apart from installing Canon printer drivers and no
3rd party peripherals. The desktop freezes spontaneously. When it
freezes, the display freezes including the mouse pointer, and
Public bug reported:
The following command results in "host not found":
$ torsocks links2 https://dev.lemmy.ml/communities/page/1
Perhaps the ".ml" suffix is not being recognized as a TLD.
** Affects: links2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
Public bug reported:
This anomaly concerns interoperability between wodim and audacity. The
Audacity side of this has been reported here:
https://bugs.launchpad.net/ubuntu/+source/audacity/+bug/1852936
Wodim needs better documentation. To say "MSB left, LSB left, MSB
right, LSB right, MSB
Public bug reported:
The 16-bit WAV files that Audacity exports are unsuitable for simply
creating a redbook CD. After exporting in format "WAV (Microsoft)
signed 16-bit PCM", the files are fed to "cdrecord", which then states
that the encoding is unusable.
If the files are non-compliant with
101 - 131 of 131 matches
Mail list logo
