** Changed in: xchat-gnome
Importance: Unknown => Medium
--
When running xchat-gnome I'm flooded by crash message
https://bugs.launchpad.net/bugs/56362
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
de
Fixed in 1:0.13-0ubuntu5
** Changed in: xchat-gnome (Ubuntu)
Status: Confirmed => Fix Released
--
When running xchat-gnome I'm flooded by crash message
https://bugs.launchpad.net/bugs/56362
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug
** Bug 57703 has been marked a duplicate of this bug
--
When running xchat-gnome I'm flooded by crash message
https://launchpad.net/bugs/56362
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
** Changed in: xchat-gnome (upstream)
Status: Unknown => Fix Released
--
When running xchat-gnome I'm flooded by crash message
https://launchpad.net/bugs/56362
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Patch applied to the edgy package:
xchat-gnome (1:0.13-0ubuntu5) edgy; urgency=low
.
* debian/patches/97_from_svn_gnome_screensaver_new_method.patch:
- patch from SVN, makes the gnome-screensaver plugin work with the
new dbus method used by it
--
When running xchat-gnome I'm flo
** Bug watch added: GNOME Bug Tracker #354306
http://bugzilla.gnome.org/show_bug.cgi?id=354306
** Also affects: xchat-gnome (upstream) via
http://bugzilla.gnome.org/show_bug.cgi?id=354306
Importance: Unknown
Status: Unknown
--
When running xchat-gnome I'm flooded by crash message
I fixed the upstream bug about the wrong backend used.
It should use gnome-screensaver instead of X11 now.
Testing welcome.
But there is still the problem in the X11 backend.
--
When running xchat-gnome I'm flooded by crash message
https://launchpad.net/bugs/56362
--
desktop-bugs mailing list
I open a upstream bug about the bad backend used bug.
Please let's continue the discussion there to try to fix that problem.
http://bugzilla.gnome.org/show_bug.cgi?id=354306
--
When running xchat-gnome I'm flooded by crash message
https://launchpad.net/bugs/56362
--
desktop-bugs mailing list
de
I suppose (hope?) there is a better way to do that with gnome-screensaver and
some dbus magic.
IMHO we should drop xscreensaver backend and give some love to the plugin to
improve that.
--
When running xchat-gnome I'm flooded by crash message
https://launchpad.net/bugs/56362
--
desktop-bugs m
crash from xprop:
"Starting program: /usr/bin/xprop -f _SCREENSAVER_STATUS 32ac
_SCREENSAVER_STATUS -root
_SCREENSAVER_STATUS
Program received signal SIGABRT, Aborted.
0xe410 in __kernel_vsyscall ()
(gdb) bt
#0 0xe410 in __kernel_vsyscall ()
#1 0xb7d8e760 in *__GI_raise () from /lib/tls
from the crash report log: "Core was generated by `xprop -f
_SCREENSAVER_STATUS 32ac -root _SCREENSAVER_STATUS'."
--
When running xchat-gnome I'm flooded by crash message
https://launchpad.net/bugs/56362
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman
I use gnome-screensaver, nothing on the command line from where I start
xchat-gnome
--
When running xchat-gnome I'm flooded by crash message
https://launchpad.net/bugs/56362
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
It's strange because it's in the xscreensaver backend but i suppose
you're using gnome-screensaver. Don't you?
Do you have any error message in the console when the plugin is loaded?
--
When running xchat-gnome I'm flooded by crash message
https://launchpad.net/bugs/56362
--
desktop-bugs maili
The issue is due to the autoaway plugin. It's not happening at the
moment, bug I workaround the "xprop crashing every second" by unloading
that plugin when it was happening
--
When running xchat-gnome I'm flooded by crash message
https://launchpad.net/bugs/56362
--
desktop-bugs mailing list
des
So, let's fix xchat-gnome's bug now.
Baptiste i suppose it's a problem in the autoaway plugin. Could you test
without this plugin loaded please?
--
When running xchat-gnome I'm flooded by crash message
https://launchpad.net/bugs/56362
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
apport (0.12) edgy; urgency=low
.
* apport-gtk: Make bug report window resizable when the details are
expanded. Closes: LP#56672
* apport_utils.py: Add get_recent_crashes() and a test suite check for it.
* apport: If the same binary produced more than 5 crashes in the last 24
h
IRC discussion for the records:
maybe stop creating bugs if the process loop crash
the loop is probably easy to determine
like >3 crashes in a min
creating bugs for that binary I mean
sure, I can define an inhibition period, but how long should that be?
the problem is right now, as soon as y
The real bug is in xprop, of course, but we need to handle this case
more gracefully in apport.
** Changed in: apport (Ubuntu)
Importance: Untriaged => Medium
Assignee: (unassigned) => Martin Pitt
Status: Unconfirmed => Confirmed
--
When running xchat-gnome I'm flooded by crash me
** Changed in: xchat-gnome (Ubuntu)
Importance: Untriaged => Medium
--
When running xchat-gnome I'm flooded by crash message
https://launchpad.net/bugs/56362
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
that's due to the absence notifier plugin and the crash notifications
come from apport
** Changed in: xchat-gnome (Ubuntu)
Assignee: (unassigned) => Ubuntu Desktop Bugs
Status: Unconfirmed => Confirmed
--
When running xchat-gnome I'm flooded by crash message
https://launchpad.net/bug
Does xchat-gnome crash?
** Also affects: apport (Ubuntu)
Importance: Untriaged
Status: Unconfirmed
--
When running xchat-gnome I'm flooded by crash message
https://launchpad.net/bugs/56362
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/lis
21 matches
Mail list logo
