Daniel, yes, this is the same crash as in bug 1787512.
It's not a duplicate IMO, since I'd researched the exact repro steps.
Any developer can trigger the crash now, by following the repro steps.
That's why I didn't use ubuntu-bug either; just follow the repro steps
and trigger the crash
Please NOTE: the report is against gnome-shell, NOT indicator-multiload!
It's not so important to fix the indicator app. Rather, gnome-shell
needs to become sturdier.
There's a change to be made to gnome-shell so that it perseveres
assertion failures and keeps running.
Lurking around, I've seen
Hey Daniel! I hope you'll take a look here:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844354
TL;DR: I'd distilled the issue and worked out a gnome-shell crasher to
reproduce this in clean VM.
Hope that helps.
--
You received this bug notification because you are a member of
Repro steps have been verified in clean VM and now refined to include
the crasher.
** Description changed:
## Steps to reproduce ##
- 1. On bionic, apt install -y indicator-multiload
- 2. Run indicator-multiload
+ 1. On bionic, apt install -y indicator-multiload dconf-editor
+ 2. dconf load
The repro steps aren't as exact as I'd like, since I found this on a
live machine with long history of rough usage (including wiping /var by
accident, and restoring from there), so the steps are a bit difficult to
isolate.
I'll try refining the steps as needed in a VM.
--
You received this bug
Public bug reported:
## Steps to reproduce ##
1. On bionic, apt install -y indicator-multiload
2. Run indicator-multiload
lsb_release -d: Ubuntu 18.04.3 LTS
gnome-shell version: 3.28.4-0ubuntu18.04.1
indicator-multiload version: 0.4-0ubuntu5
## Actual result ##
Whole desktop crashes.
Also, I'd like to see feedback from @vanvugt (as he has triaged a lot of
gnome-shell crash reports), and Michael Hofmann as the
original maintainer of indicator-multiload.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in
Found it.
In my case, this crash was triggered by .config/autostart/indicator-
multiload.desktop
If I rm the autostart file, gnome-shell logs in and works fine.
If run directly, indicator-multiload crashes gnome-shell. Package
version 0.4-0ubuntu5.
--
You received this bug notification
Nope, it didn't work.
Neither did this, the same failed assertion crash persisted:
gsettings set org.gnome.desktop.search-providers disabled
"['org.gnome.Nautilus.desktop']"
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
@vanvugt hi! Nice triage, appreciated.
Confirming I now have had this on 18.04, gnome-shell version
3.28.4-0ubuntu18.04.1.
*Removing or renaming $HOME/.config*, as a universal workaround, also
works in this case.
I'm going to test if disabling search-providers (as mentioned in
#1722599) helps,
Public bug reported:
The Linux kernel has a knob, vm.overcommit_memory, which switches how
memory allocation requests are handled. What I'm reporting is that
Chromium is basically unusable with a non-standard setting of that knob
(which makes sense as a better default to me on my system).
So,
** Changed in: xdg-utils (Ubuntu)
Status: Invalid = Opinion
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-utils in Ubuntu.
https://bugs.launchpad.net/bugs/619913
Title:
open should be an alias to xdg-open
Status in
I have to bump this again.
Personallly, I've been using bash alias open=xdg-open for years. It's
EXTREMELY useful and convenient. And I do really want to stress that:
even though I generally avoid non-standard aliases for the command line
(just so that my habits won't depend too much on a widely
Sorry, I also forgot to mention that the Brainstorm idea link given
above no longer works.
So the discussion needs to happen (at least) here.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-utils in Ubuntu.
Public bug reported:
Totem reliably crashes when using remote control feauture. To
reproduce:
1) Start totem with a video. Wait until in opens up and starts playing.
2) Switch to another terminal and issue totem --pause.
The second instance outputs:
% totem --pause
** Attachment added: example core dump of a crashed totem instance
https://bugs.launchpad.net/bugs/917241/+attachment/2677481/+files/core.gz
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to totem in Ubuntu.
I am experiencing the same issue.
I have a Gmail account set up in Evolution, IMAP and SMTP access worked
just fine for a long time. Today I discovered that I can't send email
anymore: an error window appears with a message Input/output error.
How to get more debug information?
** Changed in:
17 matches
Mail list logo
