dmesg shows:
[36663.761623] EXT3-fs error (device sda6): htree_dirblock_to_tree: bad entry
in directory #1156372: rec_len % 4 != 0 - offset=0, inode=5312000, rec_len=59,
name_len=16
[36663.761635] Aborting journal on device sda6.
[36663.763203] ext3_abort called.
[36663.763207] EXT3-fs error
Your /home filesystem is corrupt. Many of the other symptoms are
potentially fallout from this.
--
After upgrade to Jaunty Beta my machine shows different problems, , random high
load, no meta key, etc.
https://bugs.launchpad.net/bugs/352362
You received this bug notification because you are a
Attached fsck output for /home
** Attachment added: e2fsck -n /dev/sda6
http://launchpadlibrarian.net/24590045/fsck.txt.gz
--
After upgrade to Jaunty Beta my machine shows different problems, , random high
load, no meta key, etc.
https://bugs.launchpad.net/bugs/352362
You received this bug
r...@dm-lappy:~# grep 'EXT3.*error' /var/log/syslog{.0,}
/var/log/syslog.0:Mar 30 13:16:30 dm-lappy kernel: [ 133.531625] EXT3-fs error
(device sda6): ext3_free_blocks_sb: bit already cleared for block 10444818
/var/log/syslog.0:Mar 30 13:16:30 dm-lappy kernel: [ 133.533535] EXT3-fs error
** Summary changed:
- gnome-keyring-daemon eating 100% CPU at login in Jaunty
+ [arm] gnome-keyring-daemon eating 100% CPU at login in Jaunty
--
[arm] gnome-keyring-daemon eating 100% CPU at login in Jaunty
https://bugs.launchpad.net/bugs/328167
You received this bug notification because you
I am seeing different behavior on two different systems. On my system
at home, my font sizes are normal, but at work, my terminals are much
larger than they had previously been (and too large for the screen in my
opinion).
How can I go about diagnosing the problem?
--
Default font size too
Yes I do (attached).
I also get this prompt for Set system time the first time I use it in
the session. However, in that case as well, the dialog simply closes
and I don't get the chance to change the time.
** Attachment added: screenshot of PolicyKit prompt from FUSA
On Wed, Mar 11, 2009 at 03:04:37PM -, Sebastien Bacher wrote:
the dialog closing is normal (that's confusing but a known bug) it
should set the time though, do you have any error in .xsession-errors?
I think the problem is actually that I've completely misunderstood how the
dialog works.
On Wed, Mar 04, 2009 at 05:32:51PM -, Chris Coulson wrote:
Matt, could you please run dbus-monitor | tee ~/dbus.log, then try to
change the time and attach the file after you clicked the Set System
Time button.
The only output is at the very beginning:
signal sender=org.freedesktop.DBus -
On Tue, Mar 03, 2009 at 10:16:32PM -, Sebastien Bacher wrote:
thank you for your bug report, what gnome-panel is running, did you
restart recently? that's supposed to be fixed in the current version?
I have 1:2.25.91-0ubuntu3 installed and had rebooted earlier the same
day.
--
- mdz
--
perseus:[~] apt-cache policy policykit-gnome
policykit-gnome:
Installed: 0.9-1ubuntu2
Candidate: 0.9-1ubuntu3
Version table:
0.9-1ubuntu3 0
500 http://archive.ubuntu.com jaunty/main Packages
*** 0.9-1ubuntu2 0
100 /var/lib/dpkg/status
--
Unable to set system time:
Running polkit-gnome-manager does not change the behaviour.
--
Unable to set system time: helper refused
https://bugs.launchpad.net/bugs/337445
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
Works fine here, anyone still affected should file a new bug.
--
gnome-keyring-daemon returns Agent admitted failure to sign using the key.
https://bugs.launchpad.net/bugs/328127
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
Public bug reported:
Binary package hint: gnome-panel
Clicking the Set system time simply closes the dialog with no further
action. ~/.xsession-errors shows:
** (gnome-panel:4472): DEBUG: helper refused; returned
polkit_result='auth_self_keep_always -- (action, result)' and
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/23391296/Dependencies.txt
--
Unable to set system time: helper refused
https://bugs.launchpad.net/bugs/337445
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
I can reproduce a similar crash by opening the right-click menu on an
image and browsing through the View and Image menus. It's not 100%, but
trying this many times eventually triggers a crash.
Bug 330846 and bug 334076 are possible duplicates, particularly if this
is a GTK issue.
** Tags
On Sat, Feb 21, 2009 at 03:44:32PM -, Sam Liddicott wrote:
When will the patch hit jaunty?
It has been committed upstream, so it will be included with the next release
of totem, probably with the next update to the totem package.
--
- mdz
--
totem-xine crashed with SIGSEGV in strchr()
** Tags added: regression-potential
--
totem-xine crashed with SIGSEGV in strchr()
https://bugs.launchpad.net/bugs/328331
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
** Tags added: regression-potential
--
gnome-keyring-daemon returns Agent admitted failure to sign using the key.
https://bugs.launchpad.net/bugs/328127
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
** Tags added: regression-potential
** Tags removed: regression-potential
--
ssh Agent admitted failure to sign using the key on big endian machines
https://bugs.launchpad.net/bugs/201786
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug
It looks like this was probably fixed by removing the segv handler
from libgnomeui:
libgnomeui 2.19.1
* Fix crash in thumbnailing code (#452907, Felix Riemann)
* Use xdg-user-dirs to get Destkop directory shortcut (#459854, Luca Ferretti)
* Remove segv handler (Fernando Herrera)
* Add
** Tags added: regression-updates
--
python-gobject in hardy-updates on sparc misbuilt only for python2.5
https://bugs.launchpad.net/bugs/309674
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pygobject in ubuntu.
--
desktop-bugs
On Tue, Dec 02, 2008 at 09:34:29PM -, Loye Young wrote:
Daniel, unless you know of someone else to fix this, the maintainer of
the package is the right person. In this case, the maintainer is ubuntu-
core-dev.
I'm afraid that is not the right way to respond to this bug report. It is
On Tue, Dec 02, 2008 at 10:08:58PM -, ltrojan wrote:
I had a proble today loading one file: it seems the same kind of problem
(evince keeps loading and eat up all memory. I didn't wait untill it
actually run out of memory though). I'm uploading the file which caused
the problem (the
I agree with Martin's assessment in
https://bugs.edge.launchpad.net/ubuntu/+source/gnome-
panel/+bug/283278/comments/5. The final release freeze is not a good
time to experiment with this.
The fact that there is more than one way to exit the session is not new:
the panel has had two ways to do
On Mon, Oct 13, 2008 at 09:32:01AM -, Michael Vogt wrote:
What should gnome-app-install do about this? The description of the
gst-plugins-bad0.10 is:
Description: GStreamer plugins from the bad set
GStreamer is a streaming media framework, based on graphs of filters
...
So the short
I've confirmed the fix on my T61 with gnome-power-manager
2.24.0-0ubuntu4 in Intrepid.
--
ACPI brightness events no longer work on ThinkPad T61
https://bugs.launchpad.net/bugs/280646
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
I have filed bug 281669 about the sticky num lock key (Bryce's issue #2
in
https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/280646/comments/41)
--
ACPI brightness events no longer work on ThinkPad T61
https://bugs.launchpad.net/bugs/280646
You received this bug notification because you
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/18436346/Dependencies.txt
--
WARNING: Failed to parse default value `??? ??
;gtk-theme-selector.desktop, ???
???;default-applications.desktop,??? ;gnome-cups-manager.desktop]'
Closing out the linux task; this is not a kernel bug.
** Changed in: linux (Ubuntu)
Status: Triaged = Invalid
--
ACPI brightness events no longer work on ThinkPad T61
https://bugs.launchpad.net/bugs/280646
You received this bug notification because you are a member of Ubuntu
Desktop
Public bug reported:
Binary package hint: gnome-control-center
Seen when installing recent Intrepid updates:
Preparing to replace capplets-data 1:2.24.0.1-0ubuntu3 (using
.../capplets-data_1%3a2.24.0.1-0ubuntu4_all.deb) ...
WARNING: Failed to parse default value `??? ??
** Summary changed:
- warning during installation
+ warning during installation: WARNING: Failed to parse default value
--
warning during installation: WARNING: Failed to parse default value
https://bugs.launchpad.net/bugs/276272
You received this bug notification because you are a member of
** Attachment added: debdiff using AnyModifier
http://launchpadlibrarian.net/18390848/gnome-power-manager-280646.debdiff
** Changed in: gnome-power-manager (Ubuntu)
Importance: Undecided = Medium
Assignee: (unassigned) = Matt Zimmerman (mdz)
Status: New = Triaged
--
ACPI
On Fri, Oct 10, 2008 at 01:50:49AM -, Bryce Harrington wrote:
1. The problem with g-p-m not handling the brightness key when numlock
is set is in fact an issue local to gnome-power-manager. It's simply
neglects to grab the modifiers for the keys.
The first line of the attached patch
There is a package in my PPA with this patch:
https://edge.launchpad.net/~mdz/+archive
deb http://ppa.launchpad.net/mdz/ubuntu intrepid main
deb-src http://ppa.launchpad.net/mdz/ubuntu intrepid main
I haven't been able to test it on the T61 yet, but would appreciate
regression testing
** Changed in: gnome-power-manager (Ubuntu)
Target: None = ubuntu-8.10
--
ACPI brightness events no longer work on ThinkPad T61
https://bugs.launchpad.net/bugs/280646
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
On Fri, Oct 10, 2008 at 04:17:00PM -, Marc Jauvin wrote:
Hi Matt, since I did this upgrade, keyboard and mouse don't work after
I rebooted... not sure if this is caused by your updated package (or
one of their dependency like xinput).
I'm currently writing this from Hardy since my
perseus:[~] cat /proc/acpi/ibm/hotkey
status: enabled
mask: 0x008c7fff
commands: enable, disable, reset, mask
--
ACPI brightness events no longer work on ThinkPad T61
https://bugs.launchpad.net/bugs/280646
You received this bug notification because you are a member of
The gpm brightness applet does work, so gpm's logic for setting the
brightness (and whatever it calls out to...xrandr?) is working.
--
ACPI brightness events no longer work on ThinkPad T61
https://bugs.launchpad.net/bugs/280646
You received this bug notification because you are a member of
Starting to look like a hal issue, moving there...
** Changed in: hal (Ubuntu)
Sourcepackagename: gnome-power-manager = hal
--
ACPI brightness events no longer work on ThinkPad T61
https://bugs.launchpad.net/bugs/280646
You received this bug notification because you are a member of Ubuntu
I rebooted into 2.6.24 and the problem persists, so I don't think this
is strictly a kernel issue. Looking at g-p-m now.
** Changed in: gnome-power-manager (Ubuntu)
Sourcepackagename: linux = gnome-power-manager
--
ACPI brightness events no longer work on ThinkPad T61
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/18362355/Dependencies.txt
--
ACPI brightness events no longer work on ThinkPad T61
https://bugs.launchpad.net/bugs/280645
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Further investigation indicates that this is probably a kernel issue,
will file there
** Changed in: gnome-power-manager (Ubuntu)
Status: New = Invalid
--
ACPI brightness events no longer work on ThinkPad T61
https://bugs.launchpad.net/bugs/280645
You received this bug notification
Public bug reported:
Binary package hint: gnome-power-manager
[regression from 8.04]
I'm not sure about the root cause of this yet, but starting here.
Pressing the brightness up/down keys on my ThinkPad T61 no longer
changes the brightness of the LCD backlight. This worked fine in 8.04,
and
gnome-power-manager --verbose says that it is grabbing the right
keycodes:
TI:11:55:04 TH:0x650a00 FI:gpm-button.c FN:gpm_button_grab_keystring,152
- Grabbed modmask=0, keycode=233
TI:11:55:04 TH:0x650a00 FI:gpm-button.c FN:gpm_button_grab_keystring,152
- Grabbed modmask=0,
** Changed in: gnome-power-manager (Ubuntu)
Importance: Undecided = Medium
Status: Confirmed = Triaged
--
g-p-m does not honor its configuration for LCD brightness levels after multiple
unplug-replug from AC
https://bugs.launchpad.net/bugs/215484
You received this bug notification
** Also affects: module-init-tools (Ubuntu)
Importance: Undecided
Status: New
--
snd_pcsp: To blacklist or not to blacklist?
https://bugs.launchpad.net/bugs/276067
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
** Summary changed:
- No audiable system bell
+ snd_pcsp: To blacklist or not to blacklist?
** Description changed:
- Binary package hint: gnome-control-center
+ When snd_pcsp was introduced, there were some problems reported with it,
+ including:
- Using an up-to-date Intrepid with compiz
See also: https://tango.0pointer.de/pipermail/pulseaudio-
discuss/2008-September/002371.html where pulseaudio upstream seems to be
against shipping snd_pcsp
--
snd_pcsp: To blacklist or not to blacklist?
https://bugs.launchpad.net/bugs/276067
You received this bug notification because you are a
On Wed, Oct 01, 2008 at 04:38:44PM -0500, Ted Gould wrote:
On Wed, 2008-10-01 at 19:13 +0200, Martin Pitt wrote:
Matt Zimmerman [2008-10-01 14:19 +0100]:
That's correct. However, if the user doesn't get the deskbar applet
added,
they don't lose anything they had before
** Tags added: regression
** Tags removed: regression-potential
** Changed in: gnome-session (Ubuntu Intrepid)
Status: Confirmed = Triaged
--
usplash is not started on shutdown/reboot
https://bugs.launchpad.net/bugs/264696
You received this bug notification because you are a member of
When this bug is fixed, bug 277058 should be fixed at the same time.
--
usplash is not started on shutdown/reboot
https://bugs.launchpad.net/bugs/264696
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in ubuntu.
--
On Thu, Oct 02, 2008 at 12:30:46PM +0200, Sebastien Bacher wrote:
Le jeudi 02 octobre 2008 à 09:04 +0100, Matt Zimmerman a écrit :
This is not about how the dialog looks, but the end user functionality
in
it. The current upstream Shut Down dialog offers everything we need
*except
On Thu, Oct 02, 2008 at 10:38:15AM -, Martin Pitt wrote:
I played around with this a little bit. Adding the usplash_down call to
/etc/init.d/usplash stop fixes the bug to 80%, you still get some
seconds of a black text screen with a cursor, until usplash kicks in
(the time between killing
On Thu, Oct 02, 2008 at 02:30:44PM +0200, Sebastien Bacher wrote:
Le jeudi 02 octobre 2008 à 11:42 +0100, Matt Zimmerman a écrit :
Doing that would either require to change the upstream dialog to
list
all the option or to add a new dialog similar to the current
upstream
ones which
On Thu, Oct 02, 2008 at 04:28:48PM +0200, Sebastien Bacher wrote:
Le jeudi 02 octobre 2008 à 13:37 +0100, Matt Zimmerman a écrit :
I don't consider the redundant menu entries to be as much of a problem
as
having one of the most prominent buttons on the default desktop lose
most of
its
On Thu, Oct 02, 2008 at 06:09:58PM +0200, Sebastien Bacher wrote:
Le jeudi 02 octobre 2008 à 16:57 +0100, Matt Zimmerman a écrit :
On Thu, Oct 02, 2008 at 04:28:48PM +0200, Sebastien Bacher wrote:
* add an extra dialog similar to the 2 upstream ones which lists all the
options
On Wed, Oct 01, 2008 at 02:23:42PM +0200, Martin Pitt wrote:
Scott James Remnant [2008-10-01 10:07 +0100]:
On Wed, 2008-10-01 at 07:48 +0200, Martin Pitt wrote:
- if the old logout applet is configured in the panel, show the new
f-u-s-a instead
- if the old f-u-s-a applet is
On Wed, Oct 01, 2008 at 10:15:53AM -0500, Ted Gould wrote:
On Wed, 2008-10-01 at 14:19 +0100, Matt Zimmerman wrote:
Note that this, the most significant issue in my opinion, could be easily
addressed by restoring the lost functionality to the logout button.
Are you suggesting
The same thing happened to me on both of my Intrepid systems, one of
which was freshly installed from an earlier Intrepid alpha. I do have
gtk2-engines-murrine installed:
ii gtk2-engines-murrine
0.53.1+svn20080529-0ubuntu3 cairo-based gtk+-2.0 theme engine
** Changed in:
The kernel is reporting the battery status incorrectly, moving the bug
there. Was this working earlier in Intrepid as well, or only on gutsy
and hardy?
** Changed in: linux (Ubuntu)
Sourcepackagename: gnome-power-manager = linux
--
Battery status no longer shown
*** This bug is a duplicate of bug 260314 ***
https://bugs.launchpad.net/bugs/260314
** This bug is no longer a duplicate of bug 262935
gnome-power-manager crashed with SIGSEGV in gpm_cell_array_update()
** This bug has been marked a duplicate of bug 260314
gnome-power-manager
*** This bug is a duplicate of bug 260314 ***
https://bugs.launchpad.net/bugs/260314
** This bug is no longer a duplicate of bug 262935
gnome-power-manager crashed with SIGSEGV in gpm_cell_array_update()
** This bug has been marked a duplicate of bug 260314
gnome-power-manager
*** This bug is a duplicate of bug 260314 ***
https://bugs.launchpad.net/bugs/260314
** This bug has been marked a duplicate of bug 260314
gnome-power-manager frequently crashes with SIGSEGV in
IA__g_closure_invoke() or g_closure_invoke()
--
gnome-power-manager crashed with SIGSEGV in
*** This bug is a duplicate of bug 255008 ***
https://bugs.launchpad.net/bugs/255008
** This bug has been marked a duplicate of bug 255008
Up arrow key mapped to Print [screen]
--
arrow keys don't work intrepid
https://bugs.launchpad.net/bugs/255861
You received this bug notification
*** This bug is a duplicate of bug 159262 ***
https://bugs.launchpad.net/bugs/159262
** This bug has been marked a duplicate of bug 159262
gdm doesn't call usplash_down
--
usplash_down call missing in stop routine of /etc/init.d/gdm initscript
https://bugs.launchpad.net/bugs/225384
You
This sounds like gdm is not invoking usplash_down in all cases.
--
Usplash without progress bar on shutdown.
https://bugs.launchpad.net/bugs/216266
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
--
desktop-bugs mailing
usplash_down is meant to be invoked by gdm itself when it is shutting
down at the user's request, not from the init script (which will run
later).
--
gdm doesn't call usplash_down
https://bugs.launchpad.net/bugs/159262
You received this bug notification because you are a member of Ubuntu
Desktop
Public bug reported:
Binary package hint: gdm
usplash_down should be invoked by gdm when it is shutting down, so that
the progress bar is displayed for the shutdown sequence. It doesn't
seem to do this anymore (Intrepid), and the patch which implemented this
(debian/patches/15_usplash.patch) is
I think some of the comments from people who think /etc/init.d/gdm
should call usplash_down are actually about this bug (eg. bug 159262).
Also, the end result seems to be that something else starts usplash much
later in the init sequence, which results in an empty usplash progress
bar at the very
It's working fine here, and this bug report is already very long and
confused, so I think it would be better to take your issue to bug
257855. I've unmarked it as a duplicate as your issue may be slightly
different.
** Changed in: gnome-settings-daemon (Ubuntu Intrepid)
Status: Confirmed
** Description changed:
Binary package hint: gdm
usplash_down should be invoked by gdm when it is shutting down, so that
the progress bar is displayed for the shutdown sequence. It doesn't
- seem to do this anymore (Intrepid), and the patch which implemented this
-
*** This bug is a duplicate of bug 255008 ***
https://bugs.launchpad.net/bugs/255008
** This bug has been marked a duplicate of bug 255008
Up arrow key mapped to Print [screen]
--
[intrepid] Can't type @ during live cd session/arrow keys don't work
https://bugs.launchpad.net/bugs/257855
Scratch that, I've just confirmed the bug in a fresh installation using
intrepid-desktop-i386 20080903. This seems to have regressed.
** Changed in: gnome-settings-daemon (Ubuntu Intrepid)
Status: Fix Released = Triaged
** Changed in: gnome-settings-daemon (Ubuntu Intrepid)
My test was in KVM. Jan, were you testing on real hardware or in a VM?
--
Up arrow key mapped to Print [screen]
https://bugs.launchpad.net/bugs/255008
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
In fact, this only happens to me when I forget the -k switch to kvm.
Sorry about the noise, I think the original issue remains fixed, and kvm
is just broken.
** Changed in: gnome-settings-daemon (Ubuntu Intrepid)
Status: Triaged = Fix Released
--
Up arrow key mapped to Print [screen]
I instrumented /sbin/usplash_down and straced gdm, and it's simply never
invoked. Perhaps the code paths changed and the patch no longer has the
intended effect?
--
usplash is not started on shutdown/reboot
https://bugs.launchpad.net/bugs/264696
You received this bug notification because you
I think what's happened is that the actual shutdown process is now
invoked via consolekit rather than from gdm:
5489 ?S 0:00 /usr/lib/policykit/polkitd
5497 ?S 0:00 /bin/sh /usr/lib/ConsoleKit/scripts/ck-system-restart
5498 ?R 0:00 \_ /bin/sh
This ought to be fixed somewhere below gdm, either in gnome-session or
consolekit. gnome-session has:
static void
do_attempt_shutdown (GsmConsolekit *consolekit)
{
if (gsm_consolekit_can_stop (consolekit)) {
gdm_set_logout_action (GDM_LOGOUT_ACTION_NONE);
On Mon, Sep 01, 2008 at 10:16:51AM -, BUGabundo wrote:
I have not followed all Desktop meeting on this, so can you guys explain
to me (and others reading this) why having two very un-functional menus
to deal with a session a low priority?
The fact that the current menus don't work properly
On Mon, Sep 01, 2008 at 02:10:24PM -, Sebastien Bacher wrote:
upstream is going to change the dialog, that should land to intrepid
today or tomorrow when new tarballs are rolled
you can see screenshots of the new dialogs on
http://bugzilla.gnome.org/show_bug.cgi?id=507101
These are an
*** This bug is a duplicate of bug 260314 ***
https://bugs.launchpad.net/bugs/260314
** This bug has been marked a duplicate of bug 260314
gnome-power-manager crashed with SIGSEGV in IA__g_closure_invoke() or
g_closure_invoke()
--
gnome-power-manager crashed with SIGSEGV in
*** This bug is a duplicate of bug 260314 ***
https://bugs.launchpad.net/bugs/260314
** This bug is no longer a duplicate of bug 260597
gnome-power-manager crashed with SIGSEGV in g_closure_invoke()
** This bug has been marked a duplicate of bug 260314
gnome-power-manager crashed with
*** This bug is a duplicate of bug 260314 ***
https://bugs.launchpad.net/bugs/260314
** This bug has been marked a duplicate of bug 260314
gnome-power-manager crashed with SIGSEGV in IA__g_closure_invoke() or
g_closure_invoke()
--
gnome-power-manager crashed with SIGSEGV in
I see the same thing; gnome-power-manager segfaults after a few minutes
of runtime, even when the system is completely idle. I see the
following output with --no-daemon --verbose before the crash:
** (gnome-power-manager:26090): CRITICAL **: gpm_cell_array_get_cell:
assertion `GPM_IS_CELL_ARRAY
This may be a duplicate of bug 149746, but that bug is much older and
had no further reports until this big spike in reports in Intrepid, so I
suspect it's a different issue.
** Summary changed:
- gnome-power-manager crashed with SIGSEGV in IA__g_closure_invoke() or
g_closure_invoke()
+
** This bug is no longer a duplicate of bug 260597
gnome-power-manager crashed with SIGSEGV in g_closure_invoke()
--
gnome-power-manager crashed with SIGSEGV in g_closure_invoke()
https://bugs.launchpad.net/bugs/136540
You received this bug notification because you are a member of Ubuntu
** Changed in: gnome-power-manager (Ubuntu)
Sourcepackagename: None = gnome-power-manager
--
pressing the Power button shows a logout dialog
https://bugs.launchpad.net/bugs/252795
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Public bug reported:
Binary package hint: gnome-session
The unified Quit dialog, present in Ubuntu 8.04, is missing in Intrepid.
I understand this has regressed due to the new gnome-session and the
patch needs to be adapted for the new version.
debian/patches/11_session_dialog.patch has been
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/17154702/Dependencies.txt
--
Ubuntu quit/logout/shutdown dialog is gone
https://bugs.launchpad.net/bugs/262555
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
I got one of these shortly after attaching a removable USB drive. I'll
see if it happens the next time.
--
gvfs-hal-volume-monitor crashed with SIGSEGV in g_closure_invoke()
https://bugs.launchpad.net/bugs/255511
You received this bug notification because you are a member of Ubuntu
Desktop
On Thu, Aug 21, 2008 at 03:50:19PM -, Pedro Villavicencio wrote:
IS this still an issue with Intrepid? the vte has been changed a lot
during the 2.23 cycle and it would be nice to try to reproduce the same
with it. thanks.
I haven't seen this problem in a long time.
--
- mdz
--
On Sat, Aug 16, 2008 at 08:20:14AM -, Paul Weiss wrote:
This bug doesn't exist for me in Alpha 4 anymore...
Working fine for me as well now, on both affected systems. Thanks, all.
--
- mdz
--
Up arrow key mapped to Print [screen]
https://bugs.launchpad.net/bugs/255008
You received this
On Sat, Aug 16, 2008 at 06:45:25PM -, Luka Renko wrote:
Still a problem here: Kubuntu Intrepid, up-to-date as of today.
Workaround with setxkbmap -model evdev -layout us helps.
Not surprising, since the fix was in a GNOME component. Probably KDE needs
to do the same, but I don't know what
I think that's a distinct problem, as the one I've described here (which
I think matches the original report) appears to be specific to gnome-
power-manager.
--
Idle/inactive action/autosuspend results in a suspend AND a hibernate
https://bugs.launchpad.net/bugs/136871
You received this bug
Public bug reported:
Binary package hint: gnome-session
After installing a large batch of updates, gnome-session 2.23.6-0ubuntu1
crashes reproducibly for me on every login, after about 10 seconds or
so. I can see that nautilus has started successfully, and the log
indicates that compiz is
** Attachment added: .xsession-errors
http://launchpadlibrarian.net/16724201/failed-login-xsession-errors
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/16724202/Dependencies.txt
--
gnome-session segfault during login
https://bugs.launchpad.net/bugs/257250
You
Downgrading to version 2.22.1.1-0ubuntu2 (from 8.04) enabled me to login
as a workaround
--
gnome-session segfault during login
https://bugs.launchpad.net/bugs/257250
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in
On Tue, Aug 12, 2008 at 11:58:44AM -, Chris Coulson wrote:
Matt - I know this might sound like a silly question, but is Apport
enabled? You can check by typing the following in a terminal:
cat /proc/sys/kernel/core_pattern
...it should look something like |apport %p %s %c. If it reads
#0 0xb77c2263 in strlen () from /lib/tls/i686/cmov/libc.so.6
#1 0xb778e826 in vfprintf () from /lib/tls/i686/cmov/libc.so.6
#2 0xb7844f3a in __vasprintf_chk () from /lib/tls/i686/cmov/libc.so.6
#3 0xb79325df in IA__g_vasprintf (string=0xbf9c8194,
format=0x8067098 Unable to parse command
101 - 200 of 591 matches
Mail list logo
