June 1, 2013, Ubuntu 13.04.
I have set up apport to notify every time Weather Indicator crashes - and it
still does, sometimes more than once a day.
With Doug's workaround, it re-starts immediately, so the only problem now is
the nuisance of having to check the crash report to verify it's
[Expired for Weather Indicator because there has been no activity for 60
days.]
** Changed in: weather-indicator
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
As promised, both my main rig and netbook were up continuously from Dec
25 through Jan 1. The main rig (wired) and the netbook (while wired)
both had 'indicator-weather' crashs the morning of the 26th. (crash
reports coming). Since the 26th the main rig (amd 64) has had numerous
Added attachment 2
** Attachment added: _usr_bin_indicator-weather.1000.crash
https://bugs.launchpad.net/weather-indicator/+bug/821832/+attachment/2655992/+files/_usr_bin_indicator-weather.1000.crash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Added attachment 3
** Attachment added: _usr_bin_indicator-weather.1000.crash
https://bugs.launchpad.net/weather-indicator/+bug/821832/+attachment/2656001/+files/_usr_bin_indicator-weather.1000.crash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thanks John. As I mentioned before, the problems seem to be something
amiss in libdbusmenu -- either the problem is there, or libdbusmenu is
not checking for a problem condition for which it should be checking.
It's quite likely that just a few lines of programming code need to be
changed -- it's
An apport trace and strace I caught trying to get something useful for this bug
made me wonder if this is related to the issue in
https://bugs.launchpad.net/weather-indicator/+bug/743541
Perhaps the underlying issue in dbusmenu is present in both situations.
--
You received this bug
Possible, but I know 'indicator-weather' runs fine in my Ubuntu 11:10
i386, as I stated above.
Jack
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/821832
Title:
indicator-weather disappears
Works fine, Doug!
I now have a crash in /var/crash and an 'indicator -weather' running. The
workaround may not be the perfect fix, but it sure suits me.
And it's entirely possible you've provided a hint which could lead to a
permanent fix - not a bad day's work!
Thank you!
Jack
--
You
Right, hard to say then. Crashes have been extremely rare for me and so
far I've only trapped once with enough detail and it looks much like
743541 though I originally thought I was looking at the situation
discussed here. I've only probably seen 4 crashes since October on 11.10
on an i386 laptop.
So, my confidence is now pretty high that this is due to a problem in
libdbusmenu, or some misuse of it by either Python itself or a Python
extension (but I tend to doubt it's the latter two).
So, not sure I can go much further with this right now. The next step I
would take would be download
@John: Of course, I did *ask* you to add as attachment what you had
already posted. :) Just goes to show how easy it is to overlook such
things. :) Be well. --Doug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Visibility changed to: Private
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/821832
Title:
indicator-weather disappears from panel randomly
To manage notifications about this bug go to:
Thank you, Doug. As you see, I have returned this file to private,
which it was originally until I was asked to make it public.
I have been hoping since Natty somehow the developers would hit on the
solution, but every update is a disappointment. I do note, however,
indicator-weather never
@John: Sounds good, and Merry Christmas to you as well!
I didn't really read through all the previous posts in this thread until
just now, so wasn't aware Eliah had already cautioned you re: crash
reports. I certainly will be more mindful of this issue in the future,
both in offering out my
Hi John,
Wow, lots of bug reports there, most of them segfaults from the looks of
it.
Your crash report could be helpful. Would you mind to post it as a a
file attachment? I can't really work with as it is. The email message
itself is, as it should be, has long lines wrapped, thereby
My apologies - old guys, when they get tired, tend to fall into old habits.
here's the crash report as an attachment.
John
** Attachment added: _usr_bin_indicator-weather.1000.crash
Thanks John.
Well, for your crash, it looks like your crash is related to passing a
menu message along dbus (see below). This isn't terribly diagnostic,
but my best guess would be that the problem is occurring when indicator-
weather is updating it appearance due to some change in weather
Yep, my crash was also was related to libdbusmenu, but further down in
the program stack, and apparently on the Fetcher thread (according to
IndicatorLog.txt).
--- apport-retrace ---
root@s3:/var/crash# apport-retrace -s -g _usr_bin_indicator-weather.1000.crash
Reading symbols from
I should have noted:
In the above comment (Comment #47), I believe the key lines of interest
from the stack backtrace are lines 9 and 14:
#9 0x7f39ef5557fc in ?? () from /usr/lib/libdbusmenu-glib.so.4
...
#14 0x7f39ef551254 in dbusmenu_menuitem_property_set_variant () from
Hi,
I recently started using indicator-weather and also would like to see
this bug resolved and am willing to help in any way I can. My
$HOME/.cache/indicator-weather.log file is attached.
Apparently, according to the log, I used indicator-weather a bit on
Sept. 14, 2011 (i.e., on Natty). I
Oops, forgot to attach the logfile. Apologies for the dup message.
** Attachment added: indicator-weather.log
https://bugs.launchpad.net/weather-indicator/+bug/821832/+attachment/2645383/+files/indicator-weather.log
--
You received this bug notification because you are a member of Ubuntu
Hey, Doug, welcome to this mess. I had long ago decided I was all alone with
this nuisance!
If you check for other bugs in indicator-weather you'll find it has had and
still has a lot of problems. It seems also we no longer have Eliah Kagan to
help, so I don't know where else to go.
Perhaps
I spoke too soon. After a week of solidarity, indicator-weather has
started shutting down unexpectedly in Ubuntu 11.10.
I activated apport and, although it did not give me a reporting window,
it gave me a crash report in /var/crash.
What now?
--
You received this bug notification because you
On 11-10-23 12:53 PM, Eliah Kagan wrote:
I apologize for taking so long without attending to this. Assuming you
still have the affected system, are you willing to continue working on
this problem? If so, others could benefit. But if not, I fully
understand.
Hey - no apologies necessary -
I apologize for taking so long without attending to this. Assuming you
still have the affected system, are you willing to continue working on
this problem? If so, others could benefit. But if not, I fully
understand.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
This report is now moot.
My computer now has 2 systems - Ubuntu 11.04 and Ubuntu 11.10, on different
drives.
Indicator-weather still disappears regularly from 11.04, but is steady in 11.10.
We'll probably never know what small quirk in my version of 11.04 caused the
problem, but 11.04 will be my
Sorry, I had forgotten that -S was added in the Oneiric version of
apport-retrace. What happens when you do this (which should *not* appear
as though it is doing nothing for hours)?
apport-retrace -g 822931
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
It takes me through a series of Launchpad pages, eventually leading me to this
page, which is bug 821832.
I saw no report for bug 822931, only 3 bugs, 2 of which are very old, and this
one.
By the way, Indicator-weather is still sometimes reporting crashes, so I took a
look at the details of
Just submitting a new report, with your system as it is, would probably
not help. But if you can install all the debug symbol packages relevant
to this crash, so that your new report contains a usable stack trace,
then submitting a new report might provide the necessary information for
a developer
OK, I get this far.
jack@jackpc:~$ apt-cache policy yelp
yelp:
Installed: 3.0.0-0ubuntu2
Candidate: 3.0.0-0ubuntu2
Version table:
*** 3.0.0-0ubuntu2 0
500 http://ca.archive.ubuntu.com/ubuntu/ natty/main amd64 Packages
100 /var/lib/dpkg/status
jack@jackpc:~$ sudo apt-get
The instructions on that page say:
NOTE: 'yelp' [which is the package name of Help and Support located under
the 'System' menu] is just an example and not a part of the command: 'yelp' is
only used to demonstrate the procedure. You must replace 'yelp' with the name
of the package you want to
And again the nooby is confused by the instructions! here are 1 to 4...
jack@jackpc:~$ echo deb http://ddebs.ubuntu.com $(lsb_release -cs) main
restricted universe multiverse | \
sudo tee -a /etc/apt/sources.list.d/ddebs.list
[sudo] password for jack:
deb http://ddebs.ubuntu.com natty main
The Apport retracing service has not produced a symbolic stack trace in
duplicate bug 822931, so can you try using apport-retrace -g to do so
manually, and attach the trace here? (Duplicate bug 822931 doesn't look
like it has or is going to automatically get enough information for a
developer to
jack@jackpc:~$ apport-retrace -g
The program 'apport-retrace' is currently not installed. You can install it by
typing:
sudo apt-get install apport-retrace
jack@jackpc:~$ sudo apt-get install apport-retrace
[sudo] password for jack:
Reading package lists... Done
Building dependency tree
Change directory to where your .crash files are stored:
cd /var/crash
Then list them:
ls
One of the .crash files listed is the crash reported for the weather
indicator. Invoke apport-retrace -g on this file. Depending on what this
.crash file is called, the command you use might be:
OK. What am I doing Wrong?
jack@jackpc:~$ cd /var/crash
jack@jackpc:/var/crash$ ls
_usr_bin_audacity.1000.crash _usr_bin_indicator-weather.1000.crash
jack@jackpc:/var/crash$ apport-retrace -g _user_bin_indicator-weather.1000.crash
ERROR: _user_bin_indicator-weather.1000.crash is neither an
You entered the filename incorrectly, typing user instead of usr.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/821832
Title:
indicator-weather disappears from panel randomly
To manage
You can really tell I'm a user, not an understander, of Linux! What now?
jack@jackpc:~$ cd /var/crash
jack@jackpc:/var/crash$ ls
_usr_bin_audacity.1000.crash _usr_bin_indicator-weather.1000.crash
jack@jackpc:/var/crash$ apport-retrace -g _usr_bin_indicator-weather.1000.crash
ERROR: report file
I don't know why entries would be missing from your .crash file. What
happens when you try having it retrace the crash as reported on
Launchpad rather than using your local copy? (While we're at it, let's
use a sandbox and automatically grab all the necessary debug symbols.)
apport-retrace -g -S
jack@jackpc:~$ apport-retrace -g -S system 822931
Usage: apport-retrace [options] apport problem report | crash ID
apport-retrace: error: no such option: -S
jack@jackpc:~$
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
A little something in addition to what has appeared here...
Recently,Indicator-weather now does not always load when I start the computer
and must be started individually, despite the fact it is listed in Startup
Applications.
Also, although Apport is installed and running, indicator-weather
Yes, as per my instructions above, you should use the Apport window that
has come up to report a new bug. Please read https://bugs.launchpad.net
/weather-indicator/+bug/821832/comments/6 very carefully, as I explained
in detail what to do in this situation (starting about the middle of the
third
@Mateusz Stachowski
Since John Hagerman's bug is a crash, your bug is almost certainly a different
one. (You could enable Apport as detailed in
https://bugs.launchpad.net/weather-indicator/+bug/821832/comments/6 to be sure,
but both your own observations and
A duplicate report has been submitted after indicator-weather closed
unexpectedly. The reporting of this bug only vaguely resembled the
instructions in Ubuntu Help. It seems the help page is out of date -
clicking Report in the original Report a Problem window took me
directly to Launchpad and an
A duplicate report has been submitted after indicator-weather closed
unexpectedly.
Are you willing to mark bug 822931 public (or subscribe me to it) so
that I can take a look at it and see if it contains the necessary
information? (See my discussion of visibility in
On 11-08-08 03:15 PM, Eliah Kagan wrote:
A duplicate report has been submitted after indicator-weather closed
unexpectedly.
Are you willing to mark bug 822931 public (or subscribe me to it) so
that I can take a look at it and see if it contains the necessary
information? (See my discussion
It appears to me that bug 822931 is private, and also that I am not
subscribed to it. Please let me know if that is incorrect; then I will
post a question for the Launchpad admins to investigate the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Sorry, I spoke too soon. Just after I said that, the change took effect.
While you have not made bug 822931 public, I am subscribed and do have
access.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On 11-08-08 04:17 PM, Eliah Kagan wrote:
Sorry, I spoke too soon. Just after I said that, the change took effect.
While you have not made bug 822931 public, I am subscribed and do have
access.
I have also gone back and made 822931 public - and I know more now about
Apport and Launchpad than I
** Also affects: indicator-weather (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/821832
Title:
indicator-weather disappears from panel randomly
It was a mistake for me to add indicator-weather in Ubuntu to this bug,
since so far this has only been produced with the version from the
weather-indicator-team PPA. The indicator-weather (Ubuntu) task can be
reopened if anyone experiences this bug with the officially packaged
Ubuntu version.
To provide the file ~/.cache/indicator-weather.log, please run this
command in a Terminal after indicator-weather disappears (while it is
still disappeared):
cp ~/.cache/indicator-weather.log ~/Desktop
Now that the file is on the Desktop, it's easy to locate using graphical
programs (such as
I also have these problems with your indicator. It mostly works good but
there are times that it doesn't show up on the panel. I can see that it
is running in system monitor but it just doesn't show up and killing the
process (and then starting it) doesn't solve problem.
** Attachment added:
@John Hagerman
By comparison to Mateusz Stachowski's log, I can see that the file
IndicatorLog.txt (automatically attached from your system by Apport) is a
complete log, and corresponds specifically to indicator-weather. Therefore, it
is not necessary for you to provide the information I
(Keep status Incomplete pending determination of whether or not this is
an Apport-reportable crash.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/821832
Title:
indicator-weather disappears from
@Mateusz Stachowski
It's possible that you're experiencing a different bug. In this (John
Hagerman's) bug, the indicator-weather process is actually terminating when
indicator-weather disappears. On your system, it does not terminate. Finding
out whether or not John Hagerman's bug is a crash
My apologies for being so far behind in answering queries. In my own defence, I
sometimes work nights and don't get up until noon my time, so we may be working
at cross purposes.
First - I have not seen any of the windows shown in
https://wiki.ubuntu.com/Apport. In fact, I have no idea how to
Do you know if you enabled Apport
(https://wiki.ubuntu.com/Apport#How_to_enable_apport)?
If you are not sure if it is really enabled, try opening a Terminal
window, running nano (type nano and press enter), then open a new tab
and run killall -SEGV nano (without the quotes). If Apport is enabled,
On 11-08-07 03:45 PM, Eliah Kagan wrote:
Do you know if you enabled Apport
(https://wiki.ubuntu.com/Apport#How_to_enable_apport)?
If you are not sure if it is really enabled, try opening a Terminal
window, running nano (type nano and press enter), then open a new tab
and run killall -SEGV
I now have a couple of shutdowns of indicator-weather and a crash report in
/var/crash.
I have held the Apport window that popped up but have not reported.
I await your instructions.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
61 matches
Mail list logo
