Ubuntu
evolution package

unsure of nature xubuntu ISSUE

Bug #209468 reported by subliminalfix on 2008-03-31

Affects		Status	Importance	Assigned to	Milestone
	evolution (Ubuntu)	Invalid	Medium	Ubuntu Desktop Bugs

Bug Description

Memory status: size: 26521600 vsize: 0 resident: 26521600 share: 0 rss: 9269248 rss_rlim: 0
CPU usage: start_time: 1206922973 rtime: 0 utime: 33 stime: 0 cutime:26 cstime: 0 timeout: 7 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/libexec/evolution-alarm-notify'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1233135952 (LWP 5951)]
[New Thread -1234420832 (LWP 5970)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb72876cb in waitpid () from /lib/tls/i686/cmov/libc.so.6
#2 0xb7dab1b6 in gnome_gtk_module_info_get () from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 0xffffe410 in __kernel_vsyscall ()
#5 0xb7222770 in raise () from /lib/tls/i686/cmov/libc.so.6
#6 0xb7223ef3 in abort () from /lib/tls/i686/cmov/libc.so.6
#7 0xb73f4122 in g_logv () from /usr/lib/libglib-2.0.so.0
#8 0xb73f4159 in g_log () from /usr/lib/libglib-2.0.so.0
#9 0x0805d500 in main ()

Thread 2 (Thread -1234420832 (LWP 5970)):
#0 0xffffe410 in __kernel_vsyscall ()
No symbol table info available.
#1 0xb72bc803 in poll () from /lib/tls/i686/cmov/libc.so.6
No symbol table info available.
#2 0xb73ee813 in g_main_context_check () from /usr/lib/libglib-2.0.so.0
No symbol table info available.
#3 0xb73eeb89 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
No symbol table info available.
#4 0xb79887e0 in link_set_io_thread () from /usr/lib/libORBit-2.so.0
No symbol table info available.
#5 0xb740938f in g_thread_create_full () from /usr/lib/libglib-2.0.so.0
No symbol table info available.
#6 0xb7030504 in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
No symbol table info available.
#7 0xb72c651e in clone () from /lib/tls/i686/cmov/libc.so.6
No symbol table info available.

Thread 1 (Thread -1233135952 (LWP 5951)):
#0 0xffffe410 in __kernel_vsyscall ()
No symbol table info available.
#1 0xb72876cb in waitpid () from /lib/tls/i686/cmov/libc.so.6
No symbol table info available.
#2 0xb7dab1b6 in gnome_gtk_module_info_get () from /usr/lib/libgnomeui-2.so.0
No symbol table info available.
#3 <signal handler called>
No symbol table info available.
#4 0xffffe410 in __kernel_vsyscall ()
No symbol table info available.
#5 0xb7222770 in raise () from /lib/tls/i686/cmov/libc.so.6
No symbol table info available.
#6 0xb7223ef3 in abort () from /lib/tls/i686/cmov/libc.so.6
No symbol table info available.
#7 0xb73f4122 in g_logv () from /usr/lib/libglib-2.0.so.0
No symbol table info available.
#8 0xb73f4159 in g_log () from /usr/lib/libglib-2.0.so.0
No symbol table info available.
#9 0x0805d500 in main ()
No symbol table info available.
#0 0xffffe410 in __kernel_vsyscall ()

Revision history for this message

Daniel Morales (danielmorales) wrote on 2008-04-12:

Thanks for the report. Seems to be a evolution-alarm-notify problem. Can you reproduce what are you doing when you get that backtrace, and when it happens. So we can confirm it and assign it to the right team.

Revision history for this message

subliminalfix (na1tr2lp-deactivatedaccount) wrote on 2008-04-12: Re: [Bug 209468] Re: unsure of nature xubuntu ISSUE

unnamed Edit (8.1 KiB, text/html; charset="utf-8")

Revision history for this message

subliminalfix (na1tr2lp-deactivatedaccount) wrote on 2008-04-13:

in second thought i have uploaded ubuntu probably 80+ times in the past two - three months without being able to keep a stable knode until

recently.that said i wish i could recall the configuration i was trying. i had added pure xubuntu from the alternate x iso. i had added audacity ,the x

movie player and x-roast or a x-cd player. this was my daughters computer .which i had set three user accounts to.admin, and 2 users.

and the report generated to the bug tracker was linked in direct protocol with launchpad .which does not usually happen

in other words in xubuntu when something goes

wrong the system automatically starts a trace route. ) which is cool ( in gnome you must physically go to help>help online for this to activate.

as i havent had a major gliche yet in kde im not sure how to even begin a trace and hopefully wont have to.

when this crash started or was incured in the libraries listed which are Thread 1 (Thread -1233135952 (LWP 5951)): in direct proportion to

the gnome or libgnomeui libraries so unless linked into this kernel and needed at the specific time which i dont follow seems odd

as well the out put following that down through the report shows an error in libc as well as libglib which are all common thread source libraries

beyound that i am unsure how to reproduce the exact conflict

additionally What I'm confused about it how this from /lib/tls/i686/cmov/libc.so.6 differs to

and going back to the initial thread error you will find something closly related to firefox [New Thread -1233135952 (LWP 5951)]

as well i will change the nature of this base in the bug report
peace

Revision history for this message

subliminalfix (na1tr2lp-deactivatedaccount) wrote on 2008-04-13:

reconfirmining in opening statement that this issue occured in xubuntu

Revision history for this message

subliminalfix (na1tr2lp-deactivatedaccount) wrote on 2008-04-13:

hi
this is the command line binary string that is reference to in the bug gen-report as 5951

67 69 73 74 65 72 36 34 5F 74 68 72 65 61 64 5F 61 gister64_thread_a

this is what i can gather from the log

# 0 kernel system call - enter stack -leaving user mode and entering kernel process

# 1 waitpid call is inconclusive as to the function error such as

The waitpid function suspends execution of the current
       process until a child as specified by the pid argument has
       exited, or until a signal is delivered whose action is to
       terminate the current process or to call a signal handling
       function. If a child as requested by pid has already
       exited by the time of the call (a so-called "zombie" pro-
       cess), the function returns immediately. Any system
       resources used by the child are freed.

The value of pid can be one of:

< -1 which means to wait for any child process whose
process group ID is equal to the absolute value of

       -1 which means to wait for any child process whose
              process group ID is equal to the absolute value of
              pid.

-1 which means to wait for any child process; this is
the same behaviour which wait exhibits.

       0 which means to wait for any child process whose
              process group ID is equal to that of the calling
              process.

> 0 which means to wait for the child whose process ID
is equal to the value of pid.

The value of options is an exclusive OR of zero or more of
the following constants:

as well

0xb72876cb is not found in the binary source using bless

# 3 Here is a minimal example program. It uses the alarm() function to limit the time spent waiting to open a file; this is useful if the file is for a serial device that may not be turned on, which would normally cause the os.open() to hang indefinitely. The solution is to set a 5-second alarm before opening the file; if the operation takes too long, the alarm signal will be sent, and the handler raises an exception.

import signal, os

def handler(signum, frame):
print 'Signal handler called with signal', signum
raise IOError, "Couldn't open device!"

# Set the signal handler and a 5-second alarm
signal.signal(signal.SIGALRM, handler)
signal.alarm(5)

# This open() may hang indefinitely
fd = os.open('/dev/ttyS0', os.O_RDWR)

signal.alarm(0) # Disable the alarm

im really unsure if its system related because of the cpu interface or if its more toward these lines

It means that GDB thinks that a signal handler has been invoked, and
that the frames above it are in the signal handler context. If that's
incorrect, you've found a bug in GDB.

this may all be a waste of space as i am a noob and ever yet unlearned at this code but thats all i have time to do today

peace =]

hi
 this is the command line binary string that is reference to in the bug gen-report as 5951

67 69 73 74 65 72 36 34 5F 74 68 72 65 61 64 5F 61 gister64_thread_a

this is what i can gather from the log

# 0  kernel system call - enter stack -leaving user mode and entering kernel process

# 1  waitpid call is inconclusive as to the function error such as

The  waitpid  function  suspends  execution of the current
       process until a child as specified by the pid argument has
       exited,  or until a signal is delivered whose action is to
       terminate the current process or to call a signal handling
       function.   If  a  child  as  requested by pid has already
       exited by the time of the call (a so-called "zombie"  pro-
       cess),  the  function  returns  immediately.   Any  system
       resources used by the child are freed.

The value of pid can be one of:

< -1   which means to wait for  any  child  process  whose
              process group ID is equal to the absolute value of

-1     which  means  to  wait  for any child process whose
              process group ID is equal to the absolute value  of
              pid.

-1     which  means to wait for any child process; this is
              the same behaviour which wait exhibits.

0      which means to wait for  any  child  process  whose
              process  group  ID  is equal to that of the calling
              process.

> 0    which means to wait for the child whose process  ID
              is equal to the value of pid.

The value of options is an exclusive OR of zero or more of
       the following constants:

as well

0xb72876cb is not found in the binary source using bless

# 3  Here is a minimal example program. It uses the alarm() function to limit the time spent waiting to open a file; this is useful if the file is for a serial device that may not be turned on, which would normally cause the os.open() to hang indefinitely. The solution is to set a 5-second alarm before opening the file; if the operation takes too long, the alarm signal will be sent, and the handler raises an exception.

import signal, os

def handler(signum, frame):
    print 'Signal handler called with signal', signum
    raise IOError, "Couldn't open device!"

# Set the signal handler and a 5-second alarm
signal.signal(signal.SIGALRM, handler)
signal.alarm(5)

# This open() may hang indefinitely
fd = os.open('/dev/ttyS0', os.O_RDWR)

signal.alarm(0)          # Disable the alarm

im really unsure if its system related because of the cpu interface or if its more toward these lines

It means that GDB thinks that a signal handler has been invoked, and
that the frames above it are in the signal handler context.  If that's
incorrect, you've found a bug in GDB.

this may all be a waste of space as i am a noob and ever yet unlearned at this code but thats all i have time to do today

peace  =]

Revision history for this message

Lionel Le Folgoc (mrpouit) wrote on 2008-04-14:

> Backtrace was generated from '/usr/libexec/evolution-alarm-notify'

Reassigning to evolution, but /usr/libexec doesn't really sound like a debian-fhs-compliant path.

Revision history for this message

C de-Avillez (hggdh2) wrote on 2008-04-14:

/usr/libexec/evolution-alarm-notify is not ours indeed. e-a-n lives under /usr/lib/evolution/<version>, like "/usr/lib/evolution/2.22/evolution-alarm-notify".

@R.JOEL-STAFFORD: can you please state your Ubuntu version, and Evolution and Evolution-Data-Server versions?

Changed in evolution:
assignee:	nobody → desktop-bugs
importance:	Undecided → Medium
status:	New → Incomplete

Revision history for this message

subliminalfix (na1tr2lp-deactivatedaccount) wrote on 2008-04-16:

SORRY ABOUT THAT i was using the 6.10 alt installer and if i had switched to evolution rather than

thunderbird it would have been similiar. also i have reloaded xubuntu to try to figure out what happened

im not sure if it will reaccure but ill hang in for a few days before going back to kde

i really like the development tools in kde and was unsure if bringing them into x would work

peace =]

ps
thomas edison invented ten thousand non working light bulbs.he did not discourage

he simply deduced that he did not have the

right configuration

Changed in evolution:
status:	Incomplete → New

Revision history for this message

subliminalfix (na1tr2lp-deactivatedaccount) wrote on 2008-04-16:

well i jinxed myself i am in serious trouble now

bug#218022

Revision history for this message

subliminalfix (na1tr2lp-deactivatedaccount) wrote on 2008-04-20:

#10

ALLO WAKER)(???

IMPORTANT XUBUNTU IF YOU CANT SUPPORT IT DONT INTAGRATE IT

Changed in evolution:
assignee:	desktop-bugs → nobody
status:	New → Confirmed

Revision history for this message

Pedro Villavicencio (pedro) wrote on 2008-04-21:

#11

please do not confirm your own bug reports.

Changed in evolution:
status:	Confirmed → Incomplete

Revision history for this message

C de-Avillez (hggdh2) wrote on 2008-04-25:

#12

Thank you for taking the time to report this issue and helping to make Ubuntu better. Examining the information you have given us, this does not appear to be a bug report so we are closing it. We appreciate the difficulties you are facing, but it would make more sense to raise problems you are having in the support tracker at [WWW] https://answers.launchpad.net/ubuntu if you are uncertain if they are bugs. For help on reporting bugs, see [WWW] https://help.ubuntu.com/community/ReportingBugs .

I tried to understand your problem, but I am not sure what it is now. Please open an updated question on the support tracker.