** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
+ boot-testi
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1826354 (xenial/li
** Changed in: ubuntu-report (Ubuntu)
Assignee: (unassigned) => Didier Roche (didrocks)
** Changed in: ubuntu-report (Ubuntu Bionic)
Assignee: (unassigned) => Didier Roche (didrocks)
** Changed in: ubuntu-report (Ubuntu Disco)
Assignee: (unassigned) => Didier Roche (didrocks)
** C
** Summary changed:
- linux: 4.15.0-49.52 -proposed tracker
+ linux: 4.15.0-49.53 -proposed tracker
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826358
Title:
linux: 4.15.0-49.53 -proposed tracke
this issue is fixed in ubuntu 19.04 desktop
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790427
Title:
Automatically install open-vm-tools when installer running in a VMware
VM
To manage notifi
"This is new to me, so hopefully it's correct."
We are just wandering together the road of "hopefully getting ideas here
to actually look for", your active help on this is great!
Ok, so we see that PREEMPTION_TIMER and PENDING_INTERRUPT are high.
This almost seems as if a IRQ shall be delivered b
** Description changed:
[Impact]
- * Any new report after an installation in a Virtualbox machine won't
- show up CPU informations.
+ * Any new report after an installation in a Virtualbox machine won't show up
CPU informations.
+ * Note that we don't fix Cosmic: it's almost EOL and ubunt
Please run that as yourself in a regular desktop terminal window:
xrandr --verbose > xrandr.txt
** Summary changed:
- two monitor setup - resolution not properly recognized
+ [amdgpu] two 4K monitor setup - resolution not properly recognized
** Tags added: amdgpu
** Also affects: xserver-xor
And ideally run it in a Xorg session.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826316
Title:
[amdgpu] two 4K monitor setup - resolution not properly recognized
To manage notifications about t
Thanks.
1. Please run:
ubuntu-bug /var/crash/_sbin_plymouthd.0.crash
to create a bug report about that crash.
2. I can't check that whoopsie-id right now because one of our internal
servers is not responding today :(
--
You received this bug notification because you are a member of Ubun
Public bug reported:
Nach dem Start erscheint die Meldung: "Fehler in einer System Anwendung
festgestellt"
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
Uname: Linux 4.15.0-48-generic x86_64
.tmp.unity_suppor
I wondering if it makes sense to cherrypick also for lsreipl, since both tools
are almost used every time in combination, hence I think it would be good if
they are on a similar level.
Not totally sure if it is used here, but could be, for example for verification
purposes ...
--
You received
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
derivatives: bug 1826356 (linux-h
OK ... this is the second attempt ... note I had mis-typed my password in the
first attempt.
lyn@lyn-HP-Compaq-8200-Elite-CMT-PC:~$ ls /var/crash
_sbin_plymouthd.0.crash
lyn@lyn-HP-Compaq-8200-Elite-CMT-PC:~$ 2DatCat2
2DatCat2: command not found
lyn@lyn-HP-Compaq-8200-Elite-CMT-PC:~$ sudo cat /var
Doing this fixes it:
ln -s /sbin/iptables /usr/sbin/
ln -s /sbin/iptables-restore /usr/sbin/
ln -s /sbin/ip6tables /usr/sbin/
ln -s /sbin/ip6tables-restore /usr/sbin/
Apparently firewalld looks for these binaries in the wrong path, doesn't
use $PATH, and assumes a merged /usr system.
** Summary
*** This bug is a duplicate of bug 1365509 ***
https://bugs.launchpad.net/bugs/1365509
Patch for "master" branch: https://reviews.mahara.org/9877
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1365
Is there even anyone out there with disco dingo AND a functioning kernel
with an nvidia driver? But of course if someone did, they wouldn't be
here.
"I've tried nothing and I'm all out of ideas, man!"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
As I said on [this][1] probable upstream issue this bug seems to be
reduced just to have by default 'ask' or 'launch' as the default value
for key `executable-text-activation` (on
org.gnome.nautilus.preferences), or I'm missing something?
[1]: https://gitlab.gnome.org/GNOME/nautilus/issues/443#
Thanks Simon,
as discussed this will be added (or if accepted by then picked up) at the
strongswan merge for Eoan. But that has a few things it has to wait on first so
this will take a while.
Fortunately you added the great apparmor override help in comment #4 which
should help people affected u
lspci.txt
** Attachment added: "lspcik.txt"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1826316/+attachment/5259190/+files/lspcik.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/182631
about xrandr.txt... this happens with wayland session (the bug is tagged
properly i think)
honestly, i didnt try the xorg session... so the file is empty
root@r7:/home/mspehar# xrandr --verbose > xrandr.txt
No protocol specified
Can't open display :0
--
You received this bug notification becaus
edids.txt
** Attachment added: "edids.txt"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1826316/+attachment/5259188/+files/edids.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826316
journal.txt
** Attachment added: "journal.txt"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1826316/+attachment/5259189/+files/journal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/18
dmesg.txt
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1826316/+attachment/5259187/+files/dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826316
The link to that image appears to be broken. But rather than replacing
the image, please try to copy the text in the window and only send us
the text. Not an image.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
** Changed in: openssl (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797386
Title:
[SRU] OpenSSL 1.1.1 to 18.04 LTS
To manage notifications abou
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-signed-hwe (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825924
Ti
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1826346 (xenial/li
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
kernel-sta
** Changed in: ceph (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822872
Title:
Bionic: Luminous radosgw incompatible with libssl1.1
To manage notificatio
** Summary changed:
- linux-oracle: -proposed tracker
+ linux-oracle: 4.15.0-1012.14 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team (canonical-ke
[Expired for bro (Ubuntu) because there has been no activity for 60
days.]
** Changed in: bro (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1812557
Title
** Summary changed:
- linux-hwe: -proposed tracker
+ linux-hwe: 4.18.0-19.20~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team (canonical-ke
Hi Daniel ...
Attached is a screen shot of what appeared on the terminal after I copied the
script in Step 1 into the terminal.
Does that tell you anything ?
Do I assume that Step 1 did not work and go onto Step 2 ?
-Original Message-
From: Daniel van Vugt
To: RoseAngelLyn
Sent: Tu
Public bug reported:
Asterisk was working fine in 18.10, during upgrade to 19.04 it crashed
with segfault and no longer starts. This bug report is based on me
purging all asterisk files and doing a clean install.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: asterisk 1:16.2.1~dfsg-1
Proc
** No longer affects: apt (Ubuntu Artful)
** No longer affects: apt (Ubuntu Xenial)
** No longer affects: apt (Ubuntu Trusty)
** No longer affects: apt (Ubuntu)
** Changed in: unattended-upgrades (Ubuntu Trusty)
Status: New => Won't Fix
--
You received this bug notification because you
** Changed in: oem-priority
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1817817
Title:
To add power setting bin file for SAR support (QCA6174)
To mana
** No longer affects: snapd (Ubuntu Bionic)
** No longer affects: snapd (Ubuntu Xenial)
** No longer affects: snapd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778219
Title:
unattended
** No longer affects: python-apt (Ubuntu Bionic)
** No longer affects: python-apt (Ubuntu Xenial)
** No longer affects: python-apt (Ubuntu)
** This bug is no longer a duplicate of bug 1260041
Unattended-Upgrades crashes with a dpkg error
--
You received this bug notification because you are
*** This bug is a duplicate of bug 1365509 ***
https://bugs.launchpad.net/bugs/1365509
Patch for "master" branch: https://reviews.mahara.org/9874
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1365
A better fix for this issue is available in Bionic and later and also
backported to Xenial with bug 1675079.
unattended-upgrades and update-manager will now remove unused kernel
packages when there are other updates to be installed.
I'm closing this initramfs-tools task since a fix specifically f
** Project changed: initramfs-tools => ubuntu
** No longer affects: ubuntu
** Project changed: software-center => ubuntu
** No longer affects: ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/79
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/798414
Title:
update-initra
per test in bionic, turn on proposed channel, do a 'apt install
modemmanager'. it will upgrade to version 1.10.0-1~ubuntu18.04.1 and
also upgrade related libmbim and libqmi library.
I do that separate on two machine, that have DW5820e and DW5821e
separately with a sim card inside.
I confim I can
I am still seeing this issue on ARM64 nodes for the SRU triggered
yesterday:
The following packages have unmet dependencies:
linux-generic-hwe-18.04-edge : Depends: linux-image-generic-hwe-18.04-edge (=
5.0.0.13.69) but it is not going to be installed
E: Unable to correct problems, you have held
I have reclaimed /var/lib with chown to root:root and now everything is
working.
Thank you so much for your help in chasing it down! I couldn't figure
it out since it didn't point me all those levels up. Thank you!
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Please:
1. Run: lspci -k > lspcik.txt
and send us the file 'lspcik.txt'.
2. Run: strings -f /sys/class/drm/*/edid > edids.txt
and send us the file 'edids.txt'.
3. Run: dmesg > dmesg.txt
and send us the file 'dmesg.txt'.
4. Run: journalctl -b0 > journal.txt
and send us the file '
Please also:
5. Run: xrandr > xrandr.txt
and send us the file 'xrandr.txt'.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826316
Title:
two monitor setup - resolution not properly recognized
Please also:
5. Run: xrandr --verbose > xrandr.txt
and send us the file 'xrandr.txt'.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826316
Title:
two monitor setup - resolution not properly re
oh it was my mistake, i was not using the native cp & mv binary, i have
solved it now. I will close the report now. Thanks for you support
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826429
Title:
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs
Also, it appears you are using the old graphics driver ("intel"). The
newer driver which should work better is called "modesetting".
If you have made a custom xorg.conf that enables the Intel driver then
please remove it. Please also try uninstalling the driver since you
shouldn't need it:
sudo
** Changed in: inkscape
Importance: High => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/170049
Title:
Inverted ruler co-ordinate system
To manage notifications about this bug go to:
htt
The log messages you mention seem to be describing symptoms of the
problem but not the cause.
In order to find the cause of the problem, first please try uninstalling
the 'gsconnect' extension and then reboot. Then tell us if the problem
still happens.
Please also run these commands and send us t
The bluez version hasn't changed (in any meaningful way) between cosmic
and disco. So I don't think that's the cause. Also, those log messages
are from the kernel.
Can you please try downgrading your kernel to something more like cosmic
(4.18) and tell us which versions do or don't have the bug?
krisbee@mythserver2018:~$ sudo ls -la /
total 120
drwxr-xr-x 25 root root 4096 Apr 11 18:41 .
drwxr-xr-x 25 root root 4096 Apr 11 18:41 ..
drwxr-xr-x 2 root root 4096 Apr 20 15:34 bin
drwxr-xr-x 3 root root 4096 Apr 20 15:37 boot
drwxrwxr-x 2 root root 4096 Jul 8 2018 cdrom
drwxr-xr-
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-disco
** Tags added: block-proposed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
Fo
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-disco
** Tags added: block-proposed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
Fo
I am using 18.10 and I have not yet experienced this issue.
For me, in 18.04, something that consistently triggered this bug was
whenever I accidentally touched the touch-screen on my laptop while
adjusting it.
In 19.04, I am able to interact with the touch-screen using my fingers,
and this issue
** No longer affects: amd
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: amd
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
I suspect the Xorg modesetting driver's atomic logic might have
something to do with this. Can someone experiencing the problem please
try logging into 'Ubuntu on Wayland' and tell us if that avoids the
issue?
** Also affects: xorg-server (Ubuntu)
Importance: Undecided
Status: New
** Ch
** Tags added: regression
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825378
Title:
systemd-networkd doesn't set wireguard peer endpoint
To manage notifications about this bug go to:
https://bug
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826488
Title:
package snapd 2.38~14.04 failed to install/upgrade: subprocess
installed post-installation script
** Changed in: gnome-shell
Status: Unknown => Fix Released
** Changed in: mutter
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826176
Title:
Applicati
Looks like there is a similar open bug, so I will add a comment to it
with additional info
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826311
Title:
Cannot Login to Google with Advanced Protectio
I would like to find out if this is a general VAAPI problem or is indeed
specific to gstreamer.
1. Please run 'vainfo' and send us the output.
2. Please run 'lspci -k' and send us the output.
3. Please try playing the video with 'mpv'. Tell us if that works and
also send us the output it prints
*** This bug is a duplicate of bug 1550779 ***
https://bugs.launchpad.net/bugs/1550779
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1550779, so it is being marked as such. Please look
Public bug reported:
package snapd 2.38~14.04 failed to install/upgrade
subprocess installed post-installation script returned error exit status 1
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: snapd 2.38~14.04
ProcVersionSignature: Ubuntu 4.4.0-146.172~14.04.1-generic 4.4.177
Uname: L
** Changed in: mutter
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826182
Title:
[DisplayLink][fixed upstream] GNOME libmutter crash on hotplugging a
dock
Thanks Pekka.
Since I know you're the upstream developer of the fix there's no need
for us to ask any further questions.
** Tags added: fixed-in-3.32.1 fixed-upstream
** Changed in: mutter (Ubuntu)
Importance: Undecided => High
** Changed in: mutter (Ubuntu)
Status: New => Triaged
**
This sounds a little like bug 1716232. But mostly the issue here seems
to be that your touchpad doesn't support scrolling(?).
Have you tried configuring the various scrolling methods available in:
Settings > Devices > Mouse & Touchpad > ...
?
** Changed in: gnome-shell-extension-ubuntu-dock (
** No longer affects: mysql-5.5 (Ubuntu)
** Also affects: unattended-upgrades (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: unattended-upgrades (Ubuntu Xenial)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubunt
No, no progress on this. The package ftbfs in release in both bionic and
cosmic, in ways that are not obviously the same. I'm not very inclined
to fix cosmic but I guess fixing bionic should be slightly higher
priority.
--
You received this bug notification because you are a member of Ubuntu
Bugs
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
+ boot-testi
Thanks.
I wonder if this comes under the "send info to canonical" option chosen
on first login. Maybe if you choose "No" then that also means crash
reports don't get sent...? :(
We'll need to find out how to flip that option to test it.
--
You received this bug notification because you are a me
*** This bug is a duplicate of bug 1798790 ***
https://bugs.launchpad.net/bugs/1798790
Great!
That makes this a duplicate of bug 1798790.
** This bug has been marked a duplicate of bug 1798790
Ubuntu login screen never appears when using the Nvidia driver (and setting
WaylandEnable=false
@Sebastien Bacher
verdre responded:
This is caused by x11 not sending a device-changed event if no
interaction happened with the OSK before using the physical keyboard.
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1185
--
You received this bug notification because you are a member of Ubun
** Tags removed: verification-needed-cosmic
** Tags added: verification-done-cosmic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825058
Title:
mac80211_hwsim unable to handle kernel NULL pointer d
Just in case, please try uninstalling your extensions:
b'org.gnome.shell' b'enabled-extensions' b"['workspace-
g...@mathematical.coffee.gmail.com', 'nohotcor...@azuri.free.fr',
'gnomeGlobalAppMenu@lestcape', 'static_workspa...@rmy.pobox.com', 'user-
th...@gnome-shell-extensions.gcampax.github.com'
Also verified in February in comment #9.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779615
Title:
Shell text and some icons have sharp edges during zoom
To manage notifications about this bug g
I was using 3.28.3+git20190124-0ubuntu18.04.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779615
Title:
Shell text and some icons have sharp edges during zoom
To manage notifications about this
This bug is closed because:
(a) The original reporter can't reproduce it any more; and
(b) The developer can't reproduce it any more.
If there are any remaining issues then please open a new bug by running:
ubuntu-bug gnome-shell
--
You received this bug notification because you are a memb
(In reply to Tristan Miller from comment #202)
> Is this problem still reproducible in the latest version of KMail? There
> haven't been any comments on this bug in over a year; I'm wondering if
> that's because the problem has been fixed or because it has driven most of
> the user base away.
Dri
> Please consider that it is very hard for maintainers
> to fix a bug that is not reproducible on their setup.
True, but there's nothing to stop them from enlisting help from
knowledgeable users (at least a few have offered, including me). They
won't do it though; I can only speculate as to why no
(In reply to Tristan Miller from comment #207)
> (In reply to Árpi from comment #206)
> > I did get numerous duplicates when I installed kmail 5.7.x (I think, x=3),
> > that came with Ubuntu 18.04. Then I started using the workaround from
> > comment #118.
>
> Lucky you; that workaround did nothin
But is one of the developers actually looking at this? The duplication
of the messages, combined with the akonadi hanging itself out to dry
when deleting messages (resulting in the famous "retrieving folder
content" screen) makes KMail basically unusable. I'm really baffled how
such a crucial piece
I've been using IMAP for some years now, and I don't get duplicates
anymore when filtering. In the case my filters ever do filter, which is
roughly the case in 80 % of the mails they should work on (otherwise,
nothing happens).
After almost eight years and more than 200 comments, I think one shoul
(In reply to Eric Depagne from comment #203)
> It has been fixed I believe, since it disappeared from my kmail in
2015.
And yet there are plenty of comments here from 2015 to 2018 claiming the
problem still exists. I would prefer to hear from someone who was
experiencing the problem more recentl
Excellent! Good to know there is some progress.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/883459
Title:
KMail duplicates emails
To manage notifications about this bug go to:
https://bugs.launch
With a working link: bug #388869
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/883459
Title:
KMail duplicates emails
To manage notifications about this bug go to:
https://bugs.launchpad.net/kdepim/
Just hit the same. I noted that the duplicated messages, were messages
never fully moved in the first place. They ghosted in the original
folder, and the ghosts were copied.
The folders this happens to also does not have working folder
properties. Nothing you change in folder properties have ANY e
Kmail version 5.2.3 (in Debian Stable) is definitely showing this bug
(see the attached screenshot).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/883459
Title:
KMail duplicates emails
To manage no
(In reply to Tristan Miller from comment #202)
> Is this problem still reproducible in the latest version of KMail? There
> haven't been any comments on this bug in over a year; I'm wondering if
> that's because the problem has been fixed or because it has driven most of
> the user base away. I'd
(In reply to Tristan Miller from comment #202)
> Is this problem still reproducible in the latest version of KMail? There
> haven't been any comments on this bug in over a year; I'm wondering if
> that's because the problem has been fixed or because it has driven most of
> the user base away. I'd
(In reply to graham from comment #216)
> Was a KMail for what seems like forever (~2000?) (I've been a KDE user since
> it first came out in '96), but after dealing with workarounds and hacks for
> two+ years I eventually gave in and abandoned KMail back in mid-2017.
There was a commit in 2017-05-
(In reply to Tristan Miller from comment #202)
> [...] because the problem has been fixed or because it has driven most of
> the user base away. I'd love to return to using KMail [...]
I didn't stop using KMail. I stopped using filters.
If I find time to explore alternatives and find something s
(In reply to Martin Koller from comment #182)
Martin... if that's the case, then this "duplicates" issue would _only_
happen for messages being auto-filtered, correct? Instead, if messages
were first picked up and dropped into a folder and then _manually_
filtered, the events would reorder such t
(In reply to Eric Depagne from comment #203)
> (In reply to Tristan Miller from comment #202)
> > Is this problem still reproducible in the latest version of KMail? There
> > haven't been any comments on this bug in over a year; I'm wondering if
> > that's because the problem has been fixed or bec
I haven't seen the problem for a while, maybe two years. I use POP3
only, not IMAP. I run Kubuntu; currently I'm on 19.04.
Sometimes kmail crashes, and I wonder if the way I clean up is related
to my not seeing duplicate filtered messages. When kmail crashes, I stop
akonadi ("akonadictl stop") and
I can confirm this bug with both an IMAP and a POP account. Mails are sometimes
(not always, filters don't always work well) transferred from the inbox to the
correct folder and a little bit later the mails are also back in the inbox.
This can go on forever.
When I delete them from the inbox it
1 - 100 of 815 matches
Mail list logo
