Public bug reported:
I can reproduce this bug in Ubuntu 12.10 using Evolution 3.5.5 by taking
the following steps:
Move a message to a different folder or sub-folder.
Immediately click on an unread message.
After doing this, you will still be able to interact with Evolution,
click on messages,
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs/1039256
Title:
Evolution stops functioning when moving a message followed by clicking
on an unread message.
Status in “evolution”
This has fixed the problem for me.
Thanks, rock star!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs/1039256
Title:
Evolution stops functioning when moving a message followed by
Oops, spoke too soon. This fixed the behavior I specified above in most
cases, but it still happens when I move an email with an attachment and
then view a new message. Unless the fix hasn't been released to the
repositories yet, in which case I haven't actually tested it.
Sorry!
** Changed in:
Public bug reported:
This bug is new so far as I can tell with Ubuntu 12.10.
I am using IMAP and IMAP+ for email accounts, and for all of them I see
the same issue. I have seen similar issues reported for POP email
accounts, but since I am not using POP I am unsure if it is a related
problem.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs/1049289
Title:
Evolution has errors with automatically moving emails.
Status in “evolution” package in Ubuntu:
New
Bug
Changed the status to New, because I think I incorrectly put it to In
Progress when it is still unassigned and so obviously not being worked
on. Sorry about that!
** Changed in: evolution (Ubuntu)
Status: In Progress = New
--
You received this bug notification because you are a member of
happened to me on a zip file which I was able to unzip without a problem
via the command line unzip program.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/850840
Title:
The pidgin-libnotify modifications in the PPA work for me. I haven't
done a lot of testing, but a very far cry from the horribly broken state
it is in on the main branch. For one, I can finally close pidgin and
have it running from the notification bar again.
Thank you very much for your work on
On the other hand, I still see nothing for evolution. I'm a bit confused
about the status.
I see up on the main bar that it is reported as triaged, but down in the
comments the best I can tell it has simply been removed entirely from
support. Does triaged in this context mean that there are no
Thanks for the update Sebastien! That's very good news for me to hear!
So, I have been using linux for a decade, but I have not been using
Ubuntu nearly so long. What is the correct way to test the package
from raring (I assume the next release name) in a mostly quantal system?
Or would I need to
Oh my gosh, thank you so much for this.
I've been experiencing this problem for six months, and removing
evolution-indicator finally fixed it!
It was randomly crashing every few minutes with no explanation, and no
where else have I seen any suggestion for a solution.
--
You received this bug
I previously had bug https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1724557 which causes the desktop to hard crash when the
monitor is turned on, related to gnome-shell and mutter.
That bug hasn't reported anything to /var/crash lately, but the behavior
has stayed the same for me. If
I have still been experiencing crashes of the desktop whenever my
monitor is turned back on. However, the /var/crash log is now reporting
against Xwayland.
I submitted a new bug report https://bugs.launchpad.net/ubuntu/+source
/xorg-server/+bug/1733893 against this crash log as I am not sure if
This bug is coming up every single time I turn on my monitor. I play
sound with the monitor off, and sound plays up until the moment I turn
on the monitor, after which libmutter causes gnome-shell to crash. dmesg
and crash log timing coincides exactly with monitor turn on time.
--
You received
This bug may still be impacting me, but since I'm not 100% sure if the
cause is the same I am not sure. It seems to have gotten better in some
but not all situations. I did reboot to apply the released fix so this
is the most recent versions hopefully.
Perhaps useful to note that it doesn't crash
I am not certain if my crash is the same as this bug, but this seems
most likely the same issue that I see when I attempt to lock my session.
Upon locking the session it immediately crashes gnome-shell. I am using
an Intel NUC.
My dmesg reports:
gnome-shell[17362]: segfault at 38 ip
I still have the exact same symptoms after the fix was released, but no
longer see crash logs. Any way to tell what is causing the crash? I
assume it's related but don't know how to track it down.
--
You received this bug notification because you are a member of Desktop
Packages, which is
This was fixed a while ago, just cleaning my backlog of reported bugs.
** Changed in: evolution (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evolution in Ubuntu.
Fixed in bionic as best I can test.
** Changed in: gnome-shell (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1755166
Title:
I'm not going to go so far as to say the bug itself is fixed, but upon
upgrading to Bionic it is no longer using Wayland by default so...
no longer a bug that affects me at least. I'd suggest others try
upgrading and switching to the new default window manager and backend.
--
You received this
After upgrading to Bionic (and no longer using Wayland), I also no
longer get this bug.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1724439
Title:
gnome-shell crashed with
I don't know how to tell if it's definitely the same, but for me the
crash occurs not when the monitor is turned off but rather when it is
turned back on. The actual time stamp of the crash isn't until after
turning it on.
--
You received this bug notification because you are a member of Desktop
What is a bugpattern? Happy to try to create this, but my web search for
the term is just showing the reports that have it rather than a
definition.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
It's been a month, is there a way to get the fixed release of mutter in
Ubuntu 17.10? I'm fine with installing an experimental package for it or
use a PPA. My mutter version is still 3.26.1.
Is this going to stay frozen until 18.04 is released? I'd really like to
not spend the next three months
Crash still occurs every time I turn my monitor back on, as has been the
case since October.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1731911
Title:
Xwayland crashed with
I'm still seeing crashes under the exact same conditions as since
October. When I do ubuntu-bug on the crash file it directs me here, so I
think this bug may still be getting triggered for me at least.
--
You received this bug notification because you are a member of Desktop
Packages, which is
The fix provided by chris-18 worked for me, same issue.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1715435
Title:
Can't lock screen with keyboard shortcuts when using lightdm
Can confirm that this exact thing happened to me as well, I believe
after upgrading to 19.10.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-disk-utility in Ubuntu.
https://bugs.launchpad.net/bugs/1832606
Title:
GNOME Disks
Fundamentally it's fair to blame nvidia's closed source drivers because
the open source one seems to do fractional scaling properly.
Other than that what's the point in assigning blame? I'm not sure
someone is even paying attention to this bug report, I probably would
turn off notifications if it
30 matches
Mail list logo
