This version is expired
** Changed in: libproxy (Ubuntu)
Status: Triaged => Invalid
** Changed in: gnome-panel
Importance: Unknown => Undecided
** Changed in: gnome-panel
Status: Unknown => New
** Changed in: gnome-panel
Remote watch: code.google.com/p/libproxy/issues #153 =>
Hello? Why is this being ignored as yet another release (O) marches towards being yet another broken release?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/660455
Title:
clock-applet continually cr
On 11-09-20 02:54 AM, Aurius Bendikas wrote:
> Hi, I also recently started using proxy auto configuration (PAC) script
> to configure my proxy setting in the new project environment. The
> crashing keeps happening until I connect to internet. After I am
> connected the reload button successfully re
Hi, I also recently started using proxy auto configuration (PAC) script
to configure my proxy setting in the new project environment. The
crashing keeps happening until I connect to internet. After I am
connected the reload button successfully restores clock and it works
rock solid all day long.
-
This is still affecting Natty and presumably Ocelot (or whatever Natty+1
is) since libproxy 0.3.1 is simply broken.
This package badly needs updating to 0.4.7 to fix all of the crashing
that's going on with it and PAC proxy configurations.
--
You received this bug notification because you are a
The problem just randomly started occurring for me yesterday, though the
time between crashes seems to be random, not every 52 seconds as
mentioned earlier. I'm running on a relatively new install of Natty
(perhaps six weeks old max) with libproxy version 0.3.1-2. Is there any
supported way to upgr
** Changed in: libproxy (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/660455
Title:
clock-applet continually crashing
To manage notifications about this
Per the upstream libproxy bug, I have confirmed that upgrading libproxy
to 0.4.7 has fixed this problem.
Can we get an SRU (IIR-the-acronym-C) to update libproxy to 0.4.7 for
Natty please?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
This was a bug in libproxy, not webkit.
** Bug watch added: code.google.com/p/libproxy/issues #153
http://code.google.com/p/libproxy/issues/detail?id=153
** Changed in: gnome-panel
Importance: Critical => Unknown
** Changed in: gnome-panel
Status: Invalid => Unknown
** Changed in:
This bug seems to have survived and made it into Natty now.
Will there be any effort at solving it at all?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/660455
Title:
clock-applet continually crash
** Changed in: gnome-panel
Importance: Unknown => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/660455
Title:
clock-applet continually crashing
--
ubuntu-bugs mailing list
ubuntu-bugs@
** Changed in: gnome-panel
Status: Unknown => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/660455
Title:
clock-applet continually crashing
--
ubuntu-bugs mailing list
ubuntu-bugs@l
Upstream seems to be ignoring the bug report.
I think you need to either look into using a different JS engine for
libproxy or abandon using libproxy. Either way, having applications
continuing to crash due to the reliance on buggy and unmaintained
software is not a workable situation.
--
You r
** Changed in: gnome-panel (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/660455
Title:
clock-applet continually crashing
--
ubuntu-bugs mailing list
Pedro,
NM. I've pushed and am working this bug upstream anyway since nothing
is happening with it here. Hopefully it will be fixed there.
** Bug watch added: bugs.webkit.org/ #48908
https://bugs.webkit.org/show_bug.cgi?id=48908
** Also affects: gnome-panel via
https://bugs.webkit.org/sho
Pedro, you said in comment #2:
> thanks for the report, waiting for the stacktrace then and setting the
bug to incomplete.
Not only did I attach the stacktrace, I also brought it to your
attention subsequently. I did as I was asked. Now please do as you
committed to doing. AFAIC, we had a verb
Sorry for the above text being put as a comment rather then an attachment; this
is indeed the output of the command:
cat /var/log/messages | grep clock-applet
--
clock-applet continually crashing
https://bugs.launchpad.net/bugs/660455
You received this bug notification because you are a member o
Nov 2 16:35:47 SEMTEST-DEV-0005 kernel: [ 54.263621] clock-applet[1637]:
segfault at 0 ip 009094ab sp b2594fdc error 4 in libc-2.12.1.so[7ed000+157000]
Nov 2 16:36:44 SEMTEST-DEV-0005 kernel: [ 111.669188] clock-applet[1664]:
segfault at 0 ip 0102a4ab sp b3bfdfdc error 4 in libc-2.12.1.so[f0
I'm also affected by this bug, which I already noticed in Ubuntu 10.04
and is still present in 10.10.
When located behind a firewall and having an automatic proxy script defined in
System --> Preferences --> Network proxy, the bug is 100% reproductible by
following this simple procedure:
- add a
** Attachment added: "Stacktrace.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/660455/+attachment/1723055/+files/Stacktrace
--
clock-applet continually crashing
https://bugs.launchpad.net/bugs/660455
You received this bug notification because you are a member of Ubuntu
Bugs
** Attachment added: "ThreadStacktrace.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/660455/+attachment/1723054/+files/ThreadStacktrace
--
clock-applet continually crashing
https://bugs.launchpad.net/bugs/660455
You received this bug notification because you are a member of
Pedro,
I supplied the stack trace as promised. Can you please update this
ticket?
--
clock-applet continually crashing
https://bugs.launchpad.net/bugs/660455
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
The stack trace:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb2fbeb70 (LWP 12057)]
__strcmp_ia32 () at ../sysdeps/i386/i686/multiarch/../strcmp.S:39
39 ../sysdeps/i386/i686/multiarch/../strcmp.S: No such file or directory.
in ../sysdeps/i386/i686/multia
thanks for the report, waiting for the stacktrace then and setting the
bug to incomplete.
** Changed in: gnome-panel (Ubuntu)
Importance: Undecided => Medium
** Changed in: gnome-panel (Ubuntu)
Status: New => Incomplete
--
clock-applet continually crashing
https://bugs.launchpad.net/b
--
clock-applet continually crashing
https://bugs.launchpad.net/bugs/660455
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.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
25 matches
Mail list logo
