Hello!
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065034
This bug was filed with Debian a little over a month ago.
Unfortunately, the courier packages on Debian have long been poorly
maintained. Nobody seems to be willing to step up and help out. I know
Markus Wanner is/was doing
Go for it. It's been years since I filed that bug.
On 12/29/18 10:34 AM, Dmitry Bogatov wrote:
control: tags -1 +confirmed
[2016-04-26 03:52] J Mo
I am troubleshooting a problem with the courier package suite
(courier-imap as example).
I found that in /lib/init/init-d-script
Soren
The symptom of getting a "imapd-ssl: No supported cipher suites have been
found." message might be configuration related.
I have a business client that decided to upgrade their mail server on their own
this last weekend. It didn't go well for them and they had to call me.
They had this
Package: systemd
Version: 237-1
Severity: normal
Using tab-auto-completion with systemctl can cause /sbin/init to go to 100% CPU
utilization and lock up the terminal. This is probably due to the
implementation of it's bash-completion file.
This can be replicated by typing "systemctl start
I was working on this yesterday. First noticed it about a week ago. Here
are the upstream bugs:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889144
https://github.com/systemd/systemd/issues/8085
And the money quotes:
"looking at the bigger picture here: This change in systemd, while
Package: src:linux
Version: 4.14.13-1
Severity: normal
linux-image-4.14.0-3-amd64: general protection fault, SMP PTI, while running
hwinfo
I upgraded one of my desktop systems two days ago and noticed immediately that
it was freezing up every day at the same time. Total system lock. The
Package: cgroup-tools
Version: 0.41-8
Severity: normal
Multiple tools in cgroup-tools will exit 0 even on error.
Example below:
-->cgcreate -a foo:bar -t foo:bar -g cpus:whatever ; echo $?
cgcreate: can't find uid of user foo.
0
-- System Information:
Debian Release: buster/sid
APT prefers
Unwelcome comment from the peanut gallery: Ondrej closed a great many
bugs improperly, including some of mine. They were not fixed or
addressed and he didn't ask the reporters if they were still an issue.
He just closed them because he wanted to be able to put "Debian
maintainer" on his
Spectator here chiming in. Just upgraded and the module built okay for
me. Likely a local system issue. Good luck getting it figured out OP.
-->modinfo /lib/modules/4.9.0-3-amd64/updates/dkms/nvidia-current-drm.ko
filename: /lib/modules/4.9.0-3-amd64/updates/dkms/nvidia-current-drm.ko
version:
Here's the dbus messages being sent when I unplug/replug the power cable:
-->dbus-monitor
signal time=1498026097.362125 sender=:1.28 -> destination=(null
destination) serial=538 path=/org/kde/Solid/PowerManagement;
interface=org.kde.Solid.PowerManagement; member=batteryRemainingTimeChanged
Package: upower
Version: 0.99.4-4+b1
Severity: normal
upower is only checking for power state changes every two minutes on my Apple
Macbook Pro 5,1.
I suspect that upower is supposed to be getting some kind of dynamic
notification over dbus or something, but apparently it's not.
upower
Package: src:linux
Version: 4.9.30-1
Severity: normal
Lately I have been testing Linux on an Apple Macbook Pro 5,1. This model, along
with the rest of the 5-series, has two GPUs: A chipset/IGP NVidia 9400M and a
discrete NVidia 9600M GT.
In the pursuit of power savings, I've been looking into
Package: src:linux
Version: 4.9.30-1
Severity: normal
I recently installed Debian on an old Apple Macbook Pro 5,1 from 2009/2010.
The good news is that almost everything works by default. However, I've got a
weird chronic intermittent problem which I think is related to the kernel and
ACPI or
Package: macfanctld
Version: 0.6+repack1-1+b1
Severity: normal
I noticed sometimes that macfanctld was not running after boot.
The log file was ending with: "Error: Can't find a applesmc device".
-->journalctl | egrep "macfan|applesmc"
Jun 14 22:34:58.479716 fappy macfanctld[1239]: Starting
Package: grub-common
Version: 2.02~beta3-5
Severity: normal
->grub-mkrescue -o asdf asdf
[~]
->echo $?
0
asdf does not exist -- just random characters. grub-mkrescue seems to be
broken. I was trying to make a rescue .iso image using a real input directory
but that was failing. After awhile I
A compatible controller [0300]: NVIDIA Corporation C79
[GeForce 9400M] [10de:0863] (rev b1)
On 06/08/2017 03:24 AM, Luca Boccassi wrote:
Control: tags -1 moreinfo
On Wed, 2017-06-07 at 23:49 -0700, J Mo wrote:
Package: nvidia-legacy-check
Version: 375.66-1
Severity: normal
Package
Package: nvidia-legacy-check
Version: 375.66-1
Severity: normal
Package seems farked. Can't even unpack.
Selecting previously unselected package nvidia-legacy-check.
Preparing to unpack .../nvidia-legacy-check_375.66-1_amd64.deb ...
dpkg: error processing archive
Package: kmix
Version: 4:16.08.0-1+b1
Severity: normal
I just upgraded my KDE system today and discovered that kmix is no
longer adjusting the volume like it previously did when I used the mouse
wheel while hovering over the system tray icon.
When I first tested this, I got the impression that
Package: motion
Version: 4.0-1
Severity: normal
This is an bug for posterity. I've already fixed the issue myself.
After upgrading from binary version 3.4.1 to 4.0, I noticed that my
video capture was blocky and very poor quality. There was no change in
my configuration prior or during this
On 11/11/2016 10:48 AM, Guido Günther wrote:
As far as I understand your report you're disabling the feature you
want: having libvirt fixup permissions. If you disable it you have (or
virt-manager) to do that.
There might be a bug in virt-manager where it should take more care of
adjusting
On 11/11/2016 10:48 AM, Guido Günther wrote:
As far as I understand your report you're disabling the feature you
want: having libvirt fixup permissions. If you disable it you have (or
virt-manager) to do that.
There might be a bug in virt-manager where it should take more care of
adjusting
Package: libvirt-daemon
Version: 2.4.0-1+b1
Severity: important
I discovered today that setting "dynamic_ownership = 0" in
/etc/libvirt/qemu.conf seems to break the creation of new VMs.
I set dynamic_ownership=0 because libvirt was improperly seizing
ownership of read-only ISO images.
Package: syslog-ng
Version: 3.8.1-5
Severity: important
This build is obviously broken by default.
Please test new builds with the default config before shipping them out.
Nov 09 18:53:14.197521 testhost1 syslog-ng[3968]:
[2016-11-09T18:53:14.196635] WARNING: Configuration file format is too
Confirmed fixed as of 2:4.4.6+dfsg-2. If there is any release after
which, I have not teted.
On 10/14/2016 12:08 PM, Mathieu Parent wrote:
To the recipients:
Do you still have the problem when using latest packages from sid?
I cant' reproduce the problem anymore.
Thanks
Mathieu Parent
Did you close the wrong bug by accident, or is there some non obvious
connection here?
On 10/11/2016 12:39 AM, Debian Bug Tracking System wrote:
This is an automatic notification regarding your Bug report
which was filed against the samba package:
#840382: samba: After upgrade to
I just removed everything with apt-get remove --purge and reinstalled. A
fresh installation with very minimal config is crashing in the same way.
Package: samba
Version: 2:4.4.5+dfsg-3
Severity: normal
Upgraded from samba_2:4.4.3+dfsg-4 to 2:4.4.5+dfsg-3. Now samba just crashes on
start.
Notably I also saw this while installing:
Failed to preset unit: Unit file /etc/systemd/system/samba-ad-dc.service is
masked.
I had read similar statements out on the internet that gtk support was
bad previously, but that those issues have long been worked out. I'm
using it on an Arch system now and it feels really good to have.
There is also 3D acceleration features starting to go in, so you are
probably going to
Package: qemu
Version: 1:2.6+dfsg-3.1
Severity: wishlist
When attempting to use GTK features, such as -display gtk, the following error
is printed:
qemu-system-x86_64: -display gtk,gl=on: GTK support is disabled
Please begin building Debian qemu packages with GTK enabled. This is a very
Three years and two months later...
I am still doing hacky crap to get bcache installed on new systems.
Package: src:linux
Version: 4.6.2-1
Severity: normal
I have a Zotac ZBox Nano CI320 (Intel N2930), which has a built-in SD card
reader. However, it doesn't seem to be working.
I get the following dmesg errors when I insert a card:
Jul 07 17:21:06.417263 hostname kernel: mmc0: error -110 whilst
Package: e2fsprogs
Version: 1.43.1-1
Severity: normal
I have an ext4 filesystem where I wanted to remove the metadata_csum feature,
but tune2fs doesn't seem to support this, even though the man page seems to
indicate that it should.
The command I am using is: sudo tune2fs -O ^metadata_csum
Looking at my backups, my previous version was 4:15.08.3-1.
Package: dolphin
Version: 4:16.04.1-1
Severity: normal
Mouse wheel scrolling is now painfully slow in all view modes. It was working
fine as of a few weeks ago. I just upgraded today.
I found a number of upstream bugs with similar complaints but nothing that
stuck out as already being tracked.
Package: network-manager
Version: 1.2.2-1
Severity: normal
It is, apparently, not possible to specify the layer 2 MAC address which a
virtual bridge interface will use. It appears to randomly re-use a MAC address
of one of it's bridged ports (slaves).
I don't think wishlist is an appropriate
Sorry, ignore the above bugs.kde.org links. They were in reference to a
different bug.
This bridging problem still exists though. I have to put this in my
/etc/rc.local to get my bridge to come up on boot:
# Bring up br0 on boot because Debian bug:
I am sorry this is late. I missed this mail when it came in.
On 05/09/2016 10:16 AM, Marcus Wolschon wrote:
a)
0.75.0-20 doesn't fix ANYTHING.
It just adds a cryptic note to a NEWS file burried in /usr/share/doc .
The existing /etc/courier/maildroprc rule file is not moved (is
conversion
reopen 822429
This problem persists in plasma-nm 4:5.4.3-1.
Looks like this may be one or more of the following upstream bugs
https://bugs.kde.org/show_bug.cgi?id=345234
https://bugs.kde.org/show_bug.cgi?id=349673
Package: courier-base
Version: 0.75.0-18
Severity: normal
There are multiple bash scripts in the courier suite which explicitly call bash
as their interpreter, thus bash should probably be a dependency in the suite
somewhere.
Examples:
/usr/sbin/esmtpd
/usr/sbin/imapd
-- System
Package: courier-imap-ssl
Version: 4.16.2+0.75.0-18
Severity: normal
I noticed that /usr/sbin/imapd has a dependency on the config file
/etc/courier/imapd-ssl, and vice-versa for the imapd-ssl control script.
This seems to create a dependency problem.
Additionally, those control script have
Hi
Sorry I've been silent. My linux desktop motherboard died about a week
ago and I had to deal with issues surrounding that.
Here are the init scripts which I am currently using. These work for me:
http://jmomo.net/files/courier-init/
If you find any problems let me know and we can work
which has an Radeon HD 5770 in it
and I am not seeing any similar issues here.
Finally, I probably won't be able to test this again in the future as I
am planning on putting that ZBox to use and won't have access to it for
awhile.
On 04/25/2016 04:09 AM, J Mo wrote:
Thanks for the advice. I
Package: sysvinit-utils
Version: 2.88dsf-59.3
Severity: important
The last line of /lib/init/init-d-script is "exit 0".
That can't be right, can it? This overrides all other valid return codes which
could be provided by the script. In almost all cases, even errors, $? is going
to be 0.
--
Most of the problems that I've found so far are actually bugs in
init-d-script. The rest are between init-d-script and
init-d-script-courier _override() functions not replicating needed
functionality.
Before I started looking into this, I had never heard of
/lib/init/init-d-script
Ondrej, I have some questions
Why were the old courier init scripts discarded in favor of using the
init-d-script method/system? Were there some bugs related to them which
needed to get fixed? And, was there a particular reason why the
init-d-script method was used over writing stand-alone
Package: sysvinit-utils
Version: 2.88dsf-59.3
Severity: normal
I am troubleshooting a problem with the courier package suite (courier-imap as
example).
I found that in /lib/init/init-d-script, the do_status() function calls
status_of_proc() without the -p argument, leaving the PIDFILE to be
Package: sysvinit-utils
Version: 2.88dsf-59.3
Severity: minor
There are a huge number of spelling and terminology mistakes in this package.
One of them in particular which led me to expect incorrect behavior was from
the man page:
"PIDFILE (none means no PID file)"
In this case, the word
Note that a workaround is to use the ncurses "nmtui" command line tool,
or the Gnome Network Connections tool (apt-get install
network-manager-gnome).
It may be necessary to manually restart network manager after using
these tools (sudo systemctl restart NetworkManager.service), as I found
:
On Sun, Apr 24, 2016 at 21:55:12 -0700, J Mo wrote:
Package: xorg
Version: 1:7.7+15
Severity: normal
I have Zotac ZBox Nano CA320 which uses an AMD APU with a Radeon HD 8250. It's
an Intel NUC-like system, and this chip is commonly found on laptops.
I have X running KDE5 (sddm) successfully
Package: xorg
Version: 1:7.7+15
Severity: normal
I have Zotac ZBox Nano CA320 which uses an AMD APU with a Radeon HD 8250. It's
an Intel NUC-like system, and this chip is commonly found on laptops.
I have X running KDE5 (sddm) successfully but am troubleshooting another video
bug. I wanted to
Package: plasma-nm
Version: 4:5.4.3-1
Severity: normal
Already fixed upstream, this bug is a huge pain. It prevents most configuration
changes. Even non-configuration changes like changing one letter of the name of
a connection/entry.
https://bugs.kde.org/show_bug.cgi?id=362141
The user's
ile causes Xorg to fail. All other attempts at
modifying the config results in Xorg failing to start.
On 4/20/16 01:31, Michel Dänzer wrote:
On 19.04.2016 16:18, J Mo wrote:
The other system I put my drive into had a Nvidia GTX 970 and definitely
nouveau as it's newly installed Debian as of
Ondrej
You are misinterpreting the severity of the situation with a personal
attack or some hyperbolic raving on my part.
If an auto mechanic gives back an owner's car and it's on fire with the
engine and doors missing, it's not unreasonable for the mechanic to get
yelled at, no matter
Package: maildrop
Version: 2.8.3-0.1
Severity: grave
Justification: causes non-serious data loss
Recently I decided to upgrade courier (mta and imap) on one of my mail servers.
It was a disaster. The quality of these packages is abysmal and dangerous. This
is one of the many serious, grave, and
Package: courier-mta
Version: 0.75.0-18
Severity: grave
Justification: renders package unusable
Recently I decided to upgrade courier (mta and imap) on one of my mail servers.
It was a disaster. The quality of these packages is abysmal and dangerous. This
is one of the many serious, grave, and
Package: courier-mta
Version: 0.75.0-18
Severity: grave
Justification: renders package unusable
Recently I decided to upgrade courier (mta and imap) on one of my mail servers.
It was a disaster. The quality of these packages is abysmal and dangerous. This
is one of the many serious, grave, and
Package: courier-imap
Version: 4.16.2+0.75.0-18
Severity: grave
Justification: renders package unusable
Recently I decided to upgrade courier (mta and imap) on one of my mail servers.
It was a disaster. The quality of these packages is abysmal and dangerous. This
is one of the many serious,
Recently I decided to upgrade courier (mta and imap) on one of my mail
servers. It was a disaster. The quality of these packages is abysmal and
dangerous. This is one of the many serious, grave, and critical bugs I
ran into during that process.
Our problem is in postinst, line 30,
Package: courier-mta
Version: 0.75.0-18
Severity: grave
Justification: renders package unusable
Recently I decided to upgrade courier (mta and imap) on one of my mail servers.
It was a disaster. The quality of these packages is abysmal and dangerous. This
is one of the many serious, grave, and
Package: courier-mta
Version: 0.75.0-18
Severity: grave
Justification: renders package unusable
Recently I decided to upgrade courier (mta and imap) on one of my mail servers.
It was a disaster. The quality of these packages is abysmal and dangerous. This
is one of the many serious, grave, and
Package: courier-imap
Followup-For: Bug #815956
I just ran into this bug, so it's still an issue for upgrading. I'll go poking
around the control scripts in a bit and see WTF the issue is.
Like OP said:
Setting up courier-imap (4.16.2+0.75.0-18) ...
Usage: /usr/bin/makedat -src=src -file=file
Package: plasma-desktop
Version: 4:5.4.3-1
Severity: normal
The default Login Screen (SDDM), Breeze, hides login options, user accounts,
and can potentially put the user into a position where they can not log back in
without deviating from reasonable behavior.
Let's just call it thoughtlessly
:
On 19.04.2016 13:24, J Mo wrote:
Package: xserver-xorg-video-radeon
Version: 1:7.7.0-1
Severity: normal
Example image:
http://jmomo.net/files/snapshot_LibreOffice_fonts_broken-2.png
Notice the blocks under "Menu" in the middle-right where letters should be in
the UI.
The hardware
Package: xserver-xorg-video-radeon
Version: 1:7.7.0-1
Severity: normal
Example image:
http://jmomo.net/files/snapshot_LibreOffice_fonts_broken-2.png
Notice the blocks under "Menu" in the middle-right where letters should be in
the UI.
The hardware is a Zotac ZBox CA320 which has a AMD A6-1450
Package: plasma-desktop
Version: 4:5.4.3-1
Severity: minor
System Settings crashes very often, but not always, after being closed. As far
as I can tell, this does not affect the saving of settings.
Note that I am using the Classic Tree view.
The bug reporter says it's a segfault(11) and
Package: plasma-desktop
Version: 4:5.4.3-1
Severity: normal
In System Settings > Workspace > Window Management > Task Switcher.
All non-default Task Switchers installed via the star (Get Hot New Stuff) seem
to be broken and most result in an error message:
"The Window Switcher installation is
Package: plasma-desktop
Version: 4:5.4.3-1
Severity: minor
Sometimes window shadows are not being cleaned up properly.
Here is an example screenshot of the Application Launcher leaving a shadow
behind which doesn't go away until something covers it:
Package: plasma-desktop
Version: 4:5.4.3-1
Severity: normal
I am getting weird problems when trying to configure Login Screen (SDDM)
options under System Settings. Many times the entire UI will freeze up when
switching between the "Theme" and "Advanced" tabs, and switching between other
Package: plasma-desktop
Version: 4:5.4.3-1
Severity: normal
I am not able to delete or disable fonts.
System Settings > Appearance > Font > Font Management
Select multiple fonts
Delete them
"Error" "Backend died, but has been restarted. Please try again."
is gone. Not sure if it's because of the fresh reboot or the upgrade.
Thanks Ben
On 4/11/16 20:05, Ben Hutchings wrote:
Control: reassign -1 src:linux 4.3.3-7
Control: severity -1 normal
Control: tag -1 unreproducible moreinfo
On Mon, 2016-04-11 at 17:43 -0700, J Mo wrote:
Package: nfs-kernel
Package: nfs-kernel-server
Version: 1:1.2.8-9
Severity: grave
Justification: renders package unusable
Relatively new system and I'm trying to get nfsd working, but it fails.
After looking at journalctl, it seems that the nfsd module can not be loaded:
Apr 11 17:37:50.511723 myhost kernel:
Package: motion
Version: 3.2.12+git20140228-8
Severity: normal
Today I noticed that my motion daemon had shut down unexpectedly. I found the
following in my syslogs:
Mar 16 14:38:06 cine motion: [1] [NTC] [EVT] event_new_video FPS 9
Mar 16 14:38:06 cine motion: [1] [NTC] [EVT] event_newfile:
Package: syslog-ng
Version: 3.5.6-2.1
Followup-For: Bug #802888
I was finding this bug today on my system. Noticed that all of my kernel
messages were from five minutes in the future.
It looks like this bug has finally been fixed as of last month:
This is definitely still an issue, a serious one, and trivial to fix.
The problem is that the courier packages are basically orphaned. There
have been some new people trying to pick it up, but basically we need a
new maintainer.
On 3/6/16 12:11, Thomas Mayer wrote:
May be obsolete now,
Package: ifupdown
Version: 0.8.8
Severity: important
Hello
I have been having a problem where my network devices are not being configured
properly on boot. I suspect that my problems are caused in a fundamental
oversight
in the /etc/init.d/networking init script, though I'm not sure.
This bug is old and abandoned but I thought I might add that if the
author is using wpa_supplicant, this could be bug #815121.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815121
This is a way bigger/dumber bug than just bridge interfaces.
ifup is trying to bring up interfaces when udev hasn't even finished
creating devices; before drivers have even loaded.
This is probably one of ifup's many other bugs, though I'm not sure
which one. I'm still looking into this.
Occasionally my br0 interface will come up on boot, but usually not.
Seems to be a race.
My br0 interface has a eth0 (onboard 1000BASE-T) and a wlan0 (PCIE
iwlwifi card) on it.
I added a second bridge, br1, with no interfaces it in. It came up for
the two boot attempts I tested with.
This bug is still active.
This isn't an issue in the config file. The init system itself is
failing to bring up the interface.
80 matches
Mail list logo
