This was reported upstream as https://github.com/ar-/incron/issues/52
** Bug watch added: github.com/ar-/incron/issues #52
https://github.com/ar-/incron/issues/52
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is probably solved in all supported releases, as bionic uses
0.5.10-3build1, and 0.5.10 is apparently not affected.
That being said, I am experiencing a similar bug with bionic in a Docker
container, where incrond itself becomes a zombie process (and therefore
stops working).
--
You
Assuming this is about Debian #930526, this is reportedly fixed in
0.5.12-2, and therefore in all releases except bionic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823490
Title:
Incron causes
Public bug reported:
This package uses the name "docker.io", which apparently refers to docker-io,
an obsolete executable it previously contained:
https://stackoverflow.com/questions/45023363/what-is-docker-io-in-relation-to-docker-ce-and-docker-ee
Docker - whatever that means - is a mysterious
Can you clarify in what way this package is obsolete?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1753329
Title:
deprecate and stop packaging?
To manage notifications about this bug go to:
** Description changed:
After switching from Debian 9 to Kubuntu 19.04 (KOrganizer 5.10.3), I
noticed that event edition had broken with regards to times. No matter
what start and end times would be entered, saving would store these as
midnight. This would also affect existing events;
If you are experiencing this, start by checking Gmail's Forwarding and
POP/IMAP settings (at the misleading URL
https://mail.google.com/mail/u/0/#settings/fwdandpop ). In the IMAP
access area, check the second preference ("When I mark a message in IMAP
as deleted") and - if that one is set to
Which version of Qt WebEngine do you use? A similar issue was blamed on
it: https://bugs.kde.org/show_bug.cgi?id=405852
** Bug watch added: KDE Bug Tracking System #405852
https://bugs.kde.org/show_bug.cgi?id=405852
--
You received this bug notification because you are a member of Ubuntu
THIS CAN BE WORKED AROUND with Settings -> Date and time..., by going to
the Formats panel, setting Time to "France - français (fr_FR)" and
restarting a session.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I see that Launchpad allows to mark another package as affected.
Unfortunately, I cannot change the package. If someone can reassign this
to libkf5incidenceeditor, I will mark korganizer as also affected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
After switching from Debian 9 to Kubuntu 19.04 (KOrganizer 5.10.3), I
noticed that event edition had broken with regards to times. No matter
what start and end times would be entered, saving would store these as
midnight. This would also affect existing events; editing these
Public bug reported:
KOrganizer has a strange option allowing to disable reminders. When one
gives a secondary button click on the KOrganizer reminder daemon's
system tray icon, one of the menu items is an "Enable Reminders"
checkbox.
What is much more strange is that, apparently, this option is
I have had 2 Thunderbird 45 instances for the same Gmail account open in
the last weeks, viewing the All Mail folder while I was deleting mails
from that folder. On several occasions, I noticed after deleting and/or
tagging mails from one instance that the other instance wasn't updated.
The
This appears to be fixed. I cannot reproduce with the same camera (Canon
PowerShot SX200 iS) on Debian 9, using Digikam 5.3.0 and libkf5solid
5.28.0-3.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm sorry to report that this is not merely "cosmetic". I just noticed
there is also a behavioral impact; when such a warning is triggered
while running - for example - quilt pop 5, if the first de-application
causes the warning, only 1 patch will be popped.
--
You received this bug notification
** Description changed:
The push and pop quilt subcommands call touch for each patched file. The
way it is called, touch can generate an error due to insufficient
permissions, and that error is sent straight to the terminal.
The touch call intends to set file modification times. As
Public bug reported:
The push and pop quilt subcommands call touch for each patched file. The
way it is called, touch can generate an error due to insufficient
permissions, and that error is sent straight to the terminal.
The touch call intends to set file modification times. As explained in
Dotan, I do not think of someone who considers an issue solved as
working on that issue. And if the solution is deprecating X11, this will
involve more than a single developer. Besides, as I wrote, bugs are not
fixed because people decide they are - they are fixed when the software
is changed.
--
This is certainly fixable with X11. Even if it was not going to be
fixed, there would be a point in keeping the ticket open, i.e. allowing
users to find it.
Indeed, tickets are marked as resolved when there is code which fixes,
not when we find a context where the bug does not appear.
--
You
Martin,
It may remain forever the case that global shortcuts don't work when any popup
is active in X11. But that stops being a bug when users stop being deceived,
for example thanks to documentation.
I do not consider you or anyone as the developer working on this issue, but
in any case,
Thank you for these good news Martin, but users will not stop using X11 because
this doesn't affect it.
That Wayland is not affected does not resolve the bug.
Unless this is not considered a KDE bug (in which case this should be
marked INVALID), this should be retitled to specify X11
I am getting this message when opening Digikam from Device Notifier with
my mainstream Canon PowerShot SX200 iS, which has been supported for
years. Digikam appears to work fine though.
I am getting this on the same Debian testing install as the one I used 2
months ago, when I didn't get this
22 matches
Mail list logo