** Changed in: conky (Debian)
Status: Fix Committed => Fix Released
--
conky crashed with SIGSEGV in __libc_start_main()
https://bugs.launchpad.net/bugs/405188
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailin
** Changed in: conky (Debian)
Status: New => Fix Committed
--
conky crashed with SIGSEGV in __libc_start_main()
https://bugs.launchpad.net/bugs/405188
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ub
** Branch linked: lp:ubuntu/karmic/conky
--
conky crashed with SIGSEGV in __libc_start_main()
https://bugs.launchpad.net/bugs/405188
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.co
This bug was fixed in the package conky - 1.7.2-0ubuntu1
---
conky (1.7.2-0ubuntu1) karmic; urgency=low
* New upstream release:
- Improved Lua API (lua_read_parse has been removed in favour of the
conky_parse() Lua API call).
- Cairo and Imlib2 bindings for Lua.
-
Fixed upstream, will be in the next release.
** Changed in: conky (Ubuntu)
Status: Triaged => Fix Committed
--
conky crashed with SIGSEGV in __libc_start_main()
https://bugs.launchpad.net/bugs/405188
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
Yes, I can see where the problem is now, but to fix this is not trivial,
it would need a redesign of the whole module.
>I'm not sure if you follow the Answers section
Not on a daily basis, but your question is also linked to this problem.
For the time being I can only advise you to redirect stder
@Cesare Tirabassi :
I'm not sure if you follow the Answers section , just to bring to your
attention my question >
https://answers.launchpad.net/ubuntu/+source/conky/+question/80019
--
conky crashed with SIGSEGV in __libc_start_main()
https://bugs.launchpad.net/bugs/405188
You received this bug
Oops , i totally forgot about the downgrade ;)
I tested this with Conky1.7.1.1..& I correct myself... I can reproduce
this *very* consistently.
To reproduce:
1: Run conky from terminal
2: Mount any external drive/pendrive
3: As soon as an external drive is mounted , conky crashes with Segmentatio
I guess the problem with apport is that there are no debugging symbols
available for a ppa package. Anyhow, if you can trigger the crash
consistently you can at least tell us how you do that. If you downgrade
to 1.7.1.1 you can then also provide a backtrace (you can simply
downgrade using sudo apti
I think i'm able to reproduce this crash with fair consistency, i believe it
has something to do with my Western Digital USB Drive,
But however , since I'm running the ppa , apport is not collecting the info :(
I think i should be able to provide more info once 1.7.2 is pushed to
main repo.
--
** Changed in: conky (Debian)
Status: Unknown => New
--
conky crashed with SIGSEGV in __libc_start_main()
https://bugs.launchpad.net/bugs/405188
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b
The Debian bug is somewhat similar to this, even though the reporter
claims it wasn't seen on 1.7.0
** Changed in: conky (Ubuntu)
Status: In Progress => Incomplete
** Changed in: conky (Ubuntu)
Assignee: Cesare Tirabassi (norsetto) => (unassigned)
** Bug watch added: Debian Bug track
It shouldn't make any difference for your problem, but, just in case you
want to check it out, I just uploaded to my ppa
(https://edge.launchpad.net/%7Enorsetto/%2Barchive) the second release
candidate for 1.7.2.
--
conky crashed with SIGSEGV in __libc_start_main()
https://bugs.launchpad.net/bugs
If the crash happens during a mount/dismount than it is because the problem is
for one of the diskiograph which are if_mounted.
I would like you to try and trigger the crash with the least possible
configuration file, to be sure about exactly what is it that is causing it. I
can't reproduce it s
Oh... Ok... I thought it was the same since the crash happened during
the mount dismount, i thought this was related to the fonts...
"As a test, can you try to just use the diskiograph portions of your
configuration file and see if that alone will cause any crash?"
I dont understand ... you are a
The number of fonts you can use has already been raised in the version
you are using (was 64 is now 256). Exceeding the font limit will anyhow
not crash the program, the crash you reported through apport has nothing
to do with fonts.
--
conky crashed with SIGSEGV in __libc_start_main()
https://b
Also the crash doesnt occur when the conky is restarted, with the same number
of drives.
only occurs when the if_* refreshes the conky and conky tries to use more
$fonts.
My present .conkyrc has few $fonts , i dont have the old conkyrc[which had
different $fonts for diskI/O , size/free almost
I ran conky from the terminal, and when conky crashes it says , "You dont need
so many fonts sorry".
So i figured it was due to the fonts.
I have 3 partitions and if i attach another pendrive or external drive
,this happens,
This was worse when i had more $fonts in the harddrive section , which
I'm not able to reproduce this. I took your configuration file, adapted it to
my hardware, set up all the needed fonts, and even went as far as using an
external script to mount/dismount several times various drives and partitions
and never had any crash.
The backtrace indicates that the crash i
Separate bug reports issued for the two other problems as well, bug
#405701 and bug #405707, please lets keep discussing them there, if
needs be.
--
conky crashed with SIGSEGV in __libc_start_main()
https://bugs.launchpad.net/bugs/405188
You received this bug notification because you are a member
Don't worry, I already submitted the patch upstream, they are looking
into that. In the future, you may want to use their but tracker at
http://sourceforge.net/tracker/?group_id=143975&atid=757308.
--
conky crashed with SIGSEGV in __libc_start_main()
https://bugs.launchpad.net/bugs/405188
You rec
@Cesare Tirabassi :
I'v already opened a separate launchpad bug report for the grey background.
As for the updates, you are referring to the libgtk2.0 updates, right ? ok...
just applied them , will report back how it works on the other bug report
itself.
To report the user_times issue upstream
A very long shot in the dark, but re. the grey problem, I'm wondering if thats
because of your gtk version, since thats the one with the new client side
windows code. Event though conky doesn' t use gtk+, thats obviously used by
gnome.
There was a new upload a couple of hours ago, could you chec
This patch is a possible solution to the user_times problem.
Note that this also add seconds to the time, which might not be wished.
Perhaps, it could also be worth cleaning users.c using macros from readutmp.h
(from the gnu library collection).
** Attachment added: "utime.patch"
http://launch
Checking the source I see where the problem with user_times lies. The
call to localtime applied to the time difference is pretty bogus. I need
to discuss this with Brenden.
--
conky crashed with SIGSEGV in __libc_start_main()
https://bugs.launchpad.net/bugs/405188
You received this bug notificati
>Should i open a separate bug for this?
Yes pls., I expect there is no problem with compiz off?
>$user_times gives a wrong output
On my system there is a constant 1 hour offset, which I don' t yet know if it
is by design or a mistake (perhaps linked to some UTC or Summer Time offset),
this nee
@Cesare Tirabassi :
Thanx for picking this up...
On a different issue,
1> In karmic the background of the conky turns grey[random] , this does not
happen when i dual boot into jaunty and using the same .conkyrc
I ran conky from terminal ,but there is no error when this happens.
It returns to no
** Visibility changed to: Public
** Changed in: conky (Ubuntu)
Status: New => In Progress
** Changed in: conky (Ubuntu)
Assignee: (unassigned) => Cesare Tirabassi (norsetto)
--
conky crashed with SIGSEGV in __libc_start_main()
https://bugs.launchpad.net/bugs/405188
You received this
28 matches
Mail list logo
