Not likely to be a bug in the gnome-system-tools anyway. Somebody trying
to debug this should tell us what /etc/resolv.conf contains before and
after the bug is triggered, and whether running a 'ping' on the address
of the DNS server works.
--
[network-admin] wireless card will not associate if s
Public bug reported:
Binary package hint: gdm
Every time I boot my system, GDM starts, but crashes (along with X,
apparently) as soon as I press Enter (such as to select the user name).
The second time it start up, GDM behaves correctly and accepts input.
ProblemType: Bug
DistroRelease: Ubuntu
Attaching the /var/log/gdm/:0.log file as well, in case it offers any
additional data. X gets stopped with a SIGQUIT.
** Attachment added: ":0.log.1"
https://bugs.edge.launchpad.net/ubuntu/+source/gdm/+bug/638061/+attachment/1583053/+files/%3A0.log.1
--
gdm crashes once every boot
https://bu
** Attachment added: "First gdm startup with crash"
https://bugs.edge.launchpad.net/bugs/638061/+attachment/1583051/+files/%3A0-greeter.log.1
** Attachment added: "Dependencies.txt"
https://bugs.edge.launchpad.net/bugs/638061/+attachment/1583052/+files/Dependencies.txt
--
gdm crashes on
*** This bug is a duplicate of bug 623516 ***
https://bugs.launchpad.net/bugs/623516
** This bug has been marked a duplicate of bug 623516
empathy crashed because depend on package telepathy-logger
* You can subscribe to bug 623516 by following this link:
https://bugs.edge.launchpad.net/u
Public bug reported:
Binary package hint: gnome-volume-manager
In volume control applet it is possible to set volume only for
applications that are actually playing. This makes almost impossible to
control volume for applications that are playing only short sounds (like
IM client).
** Affects: g
Public bug reported:
Binary package hint: gnome-utils
Error while looking up definition
No definitions found for 'triathlon'
ProblemType: Bug
Architecture: i386
CheckboxSubmission: 9bdae1a29c58562209c7e38c30433273
CheckboxSystem: 798c9f1c7b96d673ca66694cf100eb91
Date: Tue Sep 14 06:33:34 2010
D
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/638074/+attachment/1583079/+files/Dependencies.txt
** Attachment added: "ProcMaps.txt"
https://bugs.launchpad.net/bugs/638074/+attachment/1583080/+files/ProcMaps.txt
** Attachment added: "ProcStatus.txt"
https://
same here:
(nautilus:21201): Unique-DBus-WARNING **: Error while sending message: No such
interface `org.gtk.UniqueApp' on object at path /Factory
Maverick, 64x
--
nautilus not starting
https://bugs.launchpad.net/bugs/637704
You received this bug notification because you are a member of Ubuntu
Hi!
Your issue is likely to be either bug 625239 or bug 626723 (although,
the latter one was fixed a few days ago)
--
gdm crashes once every boot
https://bugs.launchpad.net/bugs/638061
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm
Restarting the computer fixed the problem for me too.
--
nautilus not starting
https://bugs.launchpad.net/bugs/637704
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in ubuntu.
--
desktop-bugs mailing list
desktop-bugs@lists.ub
Yep. Keyboard Preferences → Layouts → Separate layout for each window.
--
100 percent cpu usage on gnome-settings-daemon
https://bugs.launchpad.net/bugs/629444
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in ubunt
*** This bug is a duplicate of bug 630884 ***
https://bugs.launchpad.net/bugs/630884
** Visibility changed to: Public
** This bug has been marked a duplicate of bug 630884
nautilus crashed with SIGSEGV in g_closure_invoke()
* You can subscribe to bug 630884 by following this link:
https:
Steve,
> Please show the contents of a plymouth:debug log, and /proc/fb, when
> booting with vga=799 (and without grub_gfxmode set).
Attaching /var/log/udev, /var/log/plymouth-debug.log and /proc/fb after boot
with no GRUB_GFXMODE set and:
GRUB_CMDLINE_LINUX_DEFAULT="vga=799 plymouth:debug"
GRUB
Steve,
> Seth, Jamie, can one of you also show the output of 'grep fb
> /var/log/kern.log' on a system showing this problem?
Attached, after boot with standard configuration (no workarounds or
related custom config at all).
** Attachment added: "kern.log-grep-fb.out"
https://bugs.launchpad.n
Thank you taking the time to report this bug and helping to make Ubuntu better.
However, processing the crash report to get detailed information for the
developers failed as the retracer did not generate a useful symbolic stack
trace.
Please try to obtain a backtrace manually following the ins
*** This bug is a duplicate of bug 634093 ***
https://bugs.launchpad.net/bugs/634093
** Visibility changed to: Public
** This bug has been marked a duplicate of bug 634093
nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__BOOLEAN()
* You can subscribe to bug 634093 by following th
Thank you taking the time to report this bug and helping to make Ubuntu better.
However, processing the crash report to get detailed information for the
developers failed as the retracer did not generate a useful symbolic stack
trace.
Please try to obtain a backtrace manually following the ins
** Branch linked: lp:~ubuntu-desktop/vino/ubuntu
--
vino crashes on desktop sharing with Empathy
https://bugs.launchpad.net/bugs/628967
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to empathy in ubuntu.
--
desktop-bugs mailing list
desk
Steve,
I meant to confirm that the boot that produced the output file attached to
comment #127 did indeed land me with X on vt2, and I did crash, as expected,
after a few minutes, when pressing enter in Terminal.
--
X starts on wrong tty because gdm starts before nvidia driver is ready
https://
Thank you taking the time to report this bug and helping to make Ubuntu better.
However, processing the crash report to get detailed information for the
developers failed as the retracer did not generate a useful symbolic stack
trace.
Please try to obtain a backtrace manually following the ins
*** This bug is a duplicate of bug 621710 ***
https://bugs.launchpad.net/bugs/621710
** Visibility changed to: Public
** This bug has been marked a duplicate of bug 621710
nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__BOOLEAN()
* You can subscribe to bug 621710 by following th
*** This bug is a duplicate of bug 599931 ***
https://bugs.launchpad.net/bugs/599931
** Visibility changed to: Public
** This bug has been marked a duplicate of bug 599931
rhythmbox crashed with SIGSEGV in g_closure_invoke()
* You can subscribe to bug 599931 by following this link:
https
** Changed in: vino (Ubuntu Maverick)
Assignee: Ken VanDine (ken-vandine) => Karl Lattimer (karl-qdh)
--
vino crashes on desktop sharing with Empathy
https://bugs.launchpad.net/bugs/628967
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
*** This bug is a duplicate of bug 630886 ***
https://bugs.launchpad.net/bugs/630886
** Visibility changed to: Public
** This bug has been marked a duplicate of bug 630886
nautilus crashes when browsing /var/log at
nautilus_icon_container_search_preedit_changed
* You can subscribe to bug
** Visibility changed to: Public
--
nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
https://bugs.launchpad.net/bugs/625874
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in ubuntu.
--
desktop-bugs mailing list
Public bug reported:
Binary package hint: gdm
Since upgrading gdm to 2.30.5-0ubuntu4 from the previous version, it
fails to set the correct resolution at bootup. This is the first time
it's ever done this. In the past it has always chosen my monitor's
correct native widescreen resolution of 1440x
** Visibility changed to: Public
--
rhythmbox crashed with SIGSEGV in gtk_tree_model_get_valist()
https://bugs.launchpad.net/bugs/635502
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to rhythmbox in ubuntu.
--
desktop-bugs mailing list
d
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/638103/+attachment/1583254/+files/Dependencies.txt
--
gdm 2.30.5-0ubuntu4 regression - wrong resolution
https://bugs.launchpad.net/bugs/638103
You received this bug notification because you are a member of Ubuntu
Desktop
*** This bug is a duplicate of bug 631958 ***
https://bugs.launchpad.net/bugs/631958
** This bug has been marked a duplicate of bug 631958
gnome-settings-daemon crashed with signal 5 in
gkbd_keyboard_drawing_new_dialog()
* You can subscribe to bug 631958 by following this link:
https://b
*** This bug is a duplicate of bug 551809 ***
https://bugs.launchpad.net/bugs/551809
Thank you for taking the time to report this crash and helping to make
Ubuntu better. This particular crash has already been reported and is a
duplicate of bug #637264, so is being marked as such. Please loo
this could be a duplicate of bug 630239
** Visibility changed to: Public
--
gnome-settings-daemon crashed with signal 5 in
gkbd_keyboard_drawing_new_dialog()
https://bugs.launchpad.net/bugs/631958
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subsc
*** This bug is a duplicate of bug 551809 ***
https://bugs.launchpad.net/bugs/551809
** This bug is no longer a duplicate of private bug 637264
** This bug has been marked a duplicate of bug 551809
gnome-settings-daemon crashed with SIGSEGV
* You can subscribe to bug 551809 by following th
*** This bug is a duplicate of bug 551809 ***
https://bugs.launchpad.net/bugs/551809
** This bug is no longer a duplicate of private bug 637264
** This bug has been marked a duplicate of bug 551809
gnome-settings-daemon crashed with SIGSEGV
* You can subscribe to bug 551809 by following th
*** This bug is a duplicate of bug 551809 ***
https://bugs.launchpad.net/bugs/551809
** This bug is no longer a duplicate of private bug 637264
** This bug has been marked a duplicate of bug 551809
gnome-settings-daemon crashed with SIGSEGV
* You can subscribe to bug 551809 by following th
*** This bug is a duplicate of bug 551809 ***
https://bugs.launchpad.net/bugs/551809
** This bug is no longer a duplicate of private bug 637264
** This bug has been marked a duplicate of bug 551809
gnome-settings-daemon crashed with SIGSEGV
* You can subscribe to bug 551809 by following th
** Also affects: gnome-bluetooth (Ubuntu Maverick)
Importance: High
Status: Triaged
** Also affects: nautilus-sendto (Ubuntu Maverick)
Importance: Undecided
Status: Invalid
** Changed in: gnome-bluetooth (Ubuntu Maverick)
Assignee: (unassigned) => Canonical Desktop Team (
*** This bug is a duplicate of bug 551809 ***
https://bugs.launchpad.net/bugs/551809
bug 551809 is also tracking that upstream report, traces are similar as
well, marking this as duplicate of bug 551809
--
bluetooth-applet crashed with SIGSEGV
https://bugs.launchpad.net/bugs/551831
You recei
upstream report was reassigned to gtk+, doing the same with this one.
** Package changed: gnome-settings-daemon (Ubuntu) => gtk+2.0 (Ubuntu)
--
gnome-settings-daemon crashed with SIGSEGV
https://bugs.launchpad.net/bugs/551809
You received this bug notification because you are a member of Ubuntu
** Branch linked: lp:~ken-vandine/gnome-bluetooth/ubuntu
--
bluetooth "devices" menu item not working in bluetooth indicator
https://bugs.launchpad.net/bugs/558841
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk+2.0 in ubuntu.
--
de
the bug is fixed since yesterday
** Changed in: gnome-bluetooth (Ubuntu Maverick)
Status: Triaged => Fix Released
--
nautilus-sendto crashed with SIGSEGV in _start() due to broken
libnstbluetooth.so plugin_info structure
https://bugs.launchpad.net/bugs/632358
You received this bug notifi
*** This bug is a duplicate of bug 551809 ***
https://bugs.launchpad.net/bugs/551809
** This bug has been marked a duplicate of bug 551809
gnome-settings-daemon crashed with SIGSEGV
* You can subscribe to bug 551809 by following this link:
https://bugs.edge.launchpad.net/ubuntu/+source/gt
I can confirm this bug. Also major issue with our ubuntu deployment.
** Changed in: nautilus (Ubuntu)
Status: Incomplete => Confirmed
--
cant browse/mount windows shares in nautilus 10.04
https://bugs.launchpad.net/bugs/544847
You received this bug notification because you are a member of
I am affected (Lucid, fresh install).
Steps to trigger bug:
1. Edit -> Preferences -> Plugins
2. Check "External Tools"
3. Click "Configure Plugin"
4. Select any configured tool
5. Click "All Languages" on the "Applicability" line
This will hang X every time. To recover:
1. CTRL+ALT+F2
2. Log
Thanks for checking this out. seems to working at the moment. if it
happens again i will let you know.
Kind Regards
mg_bob
--
rhythmbox crashed with SIGSEGV in pthread_mutex_lock()
https://bugs.launchpad.net/bugs/629429
You received this bug notification because you are a member of Ubuntu
Deskt
** Changed in: rhythmbox (Ubuntu)
Status: Invalid => New
--
Cannot edit Metadata in a WMA file
https://bugs.launchpad.net/bugs/278510
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@lis
Here is my complete kernel.log since last reboot, just after downgrading to the
regular gdm package for lucid (no workarounds).
You can do your own greps if you wish :)
---
Now if someone is ever interested in more detai
There's a samba bug here:
https://bugzilla.samba.org/show_bug.cgi?id=7250 that I'm not sure but
looks like it might resolve this issue.
Was fixed in samba 3.5.3 which ubuntu 10.04 has 3.4.7
** Bug watch added: Samba Bugzilla #7250
https://bugzilla.samba.org/show_bug.cgi?id=7250
--
Unable to
** Changed in: shared-mime-info
Status: Invalid => Won't Fix
** Changed in: shared-mime-info
Importance: Unknown => Medium
--
Folders have wrong default program and the association can't be changed
https://bugs.launchpad.net/bugs/35463
You received this bug notification because you are
Steve,
> You might also be able to confirm this is the problem by commenting out
> the "graphics-device-added fb0" part of the start condition.
Okay, testing with standard disto version of /etc/default/grub and the
following in my /etc/init/gdm.conf:
start on (filesystem
and started db
Just experienced this in Maverick.
First rename seems to work then the second does not (doing it quickly after).
All music is on an external drive.
rhythmbox-debug attached --hopefully it's okay, I don't know how to properly
close rhythmbox now with the sound menu.
** Attachment added: "rhythmb
On 09/14/2010 05:09 PM, Jamie Krug wrote:
> Steve,
>
>
>> You might also be able to confirm this is the problem by commenting out
>> the "graphics-device-added fb0" part of the start condition.
>>
> Okay, testing with standard disto version of /etc/default/grub and the
> following in my /et
Note: It might be that we need this kernel patch:
http://lkml.org/lkml/2010/5/3/76
--
nautilus not removing device after unmount
https://bugs.launchpad.net/bugs/548546
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in ubuntu.
-
Thank you for taking the time to make Ubuntu better. Since what you
submitted is a Feature Request to improve Ubuntu, you are invited to
post your idea in Ubuntu Brainstorm at https://brainstorm.ubuntu.com/
where it can be discussed, voted by the community and reviewed by
developers. Thanks for tak
** Branch linked: lp:ubuntu/vino
--
vino crashes on desktop sharing with Empathy
https://bugs.launchpad.net/bugs/628967
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to empathy in ubuntu.
--
desktop-bugs mailing list
desktop-bugs@lists.u
*** This bug is a duplicate of bug 43066 ***
https://bugs.launchpad.net/bugs/43066
** Also affects: gnome-panel
Importance: Undecided
Status: New
--
panel right vertical - windows on panel collapse and uncollapse periodically
https://bugs.launchpad.net/bugs/618303
You received this
*** This bug is a duplicate of bug 637260 ***
https://bugs.launchpad.net/bugs/637260
** This bug has been marked a duplicate of private bug 637260
--
gnome-settings-daemon crashed with signal 5 in xkl_process_error()
https://bugs.launchpad.net/bugs/636385
You received this bug notification b
** Visibility changed to: Public
--
empathy-av crashed with SIGSEGV in g_closure_invoke()
https://bugs.launchpad.net/bugs/635763
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to empathy in ubuntu.
--
desktop-bugs mailing list
desktop-bug
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Please answer these questions:
1. Is this reproducible?
2. If so, what specific steps should we take to recreate this bug? Be as
detailed as possible.
This will help us to find and resolve the problem.
Trace is g
Seth,
> So let me get this straight, you just removed the "graphics-device-added
> fb0 PRIMARY_DEVICE_FOR_DISPLAY=1" disjunction?
Yes, that is exactly what I did, and nothing else.
--
X starts on wrong tty because gdm starts before nvidia driver is ready
https://bugs.launchpad.net/bugs/625239
Y
.. which was accepted upstream here:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=c3473c63542d53740f175f3a515257ae159e998b
--
nautilus not removing device after unmount
https://bugs.launchpad.net/bugs/548546
You received this bug notification because you are a membe
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a valgrind log following the
instructions at https://wiki.ubuntu.com/Valgrind and attach the file to
the bug report. This will greatly help us in tracking down your problem.
** Changed in: evo
*** This bug is a duplicate of bug 627236 ***
https://bugs.launchpad.net/bugs/627236
Thank you for taking the time to report this crash and helping to make
Ubuntu better. This particular crash has already been reported and is a
duplicate of bug #627236, so is being marked as such. Please loo
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Please answer these questions:
1. Is this reproducible?
2. If so, what specific steps should we take to recreate this bug? Be as
detailed as possible.
This will help us to find and resolve the problem.
** Changed
I have just done an upgrade and so far Evolution has been
working, though I did notice a duplication of emails last
week: It appears to have cleared them up however and did
not crash - or not yet any way.
Thanks for your interest.
Aine
On Tue, 14 Sep 2010 12:15:54 -
Pedro Villavicencio
*** This bug is a duplicate of bug 507062 ***
https://bugs.launchpad.net/bugs/507062
** Visibility changed to: Public
** This bug has been marked a duplicate of bug 507062
synaptic assert failure: synaptic: ../../src/xcb_io.c:385: _XAllocID:
Assertion `ret != inval_id' failed.
* You can
*** This bug is a duplicate of bug 507062 ***
https://bugs.launchpad.net/bugs/507062
** This bug is no longer a duplicate of bug 630966
gnome-panel assert failure: gnome-panel: ../../src/xcb_io.c:385: _XAllocID:
Assertion `ret != inval_id' failed.
** This bug has been marked a duplicate of
*** This bug is a duplicate of bug 507062 ***
https://bugs.launchpad.net/bugs/507062
** This bug is no longer a duplicate of bug 630966
gnome-panel assert failure: gnome-panel: ../../src/xcb_io.c:385: _XAllocID:
Assertion `ret != inval_id' failed.
** This bug has been marked a duplicate of
*** This bug is a duplicate of bug 507062 ***
https://bugs.launchpad.net/bugs/507062
** This bug is no longer a duplicate of bug 630966
gnome-panel assert failure: gnome-panel: ../../src/xcb_io.c:385: _XAllocID:
Assertion `ret != inval_id' failed.
** This bug has been marked a duplicate of
*** This bug is a duplicate of bug 507062 ***
https://bugs.launchpad.net/bugs/507062
** This bug is no longer a duplicate of bug 630966
gnome-panel assert failure: gnome-panel: ../../src/xcb_io.c:385: _XAllocID:
Assertion `ret != inval_id' failed.
** This bug has been marked a duplicate of
*** This bug is a duplicate of bug 507062 ***
https://bugs.launchpad.net/bugs/507062
** This bug has been marked a duplicate of bug 507062
synaptic assert failure: synaptic: ../../src/xcb_io.c:385: _XAllocID:
Assertion `ret != inval_id' failed.
* You can subscribe to bug 507062 by followi
Can confirm on T410s, same issue
--
wrong battery status in power applet after resume from suspend
https://bugs.launchpad.net/bugs/606159
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu.
--
desktop-bugs mai
As per comments and bug status this is fixed. However, invalid upstream
bug still active in bug searches. Unlinking but if this problem persists
please re-link a valid bug.
** Changed in: gtk
Importance: Unknown => Undecided
** Changed in: gtk
Status: Incomplete => New
** Changed in: g
Hi Chris,
Seems like there is info missing on my bug :)
I don't think it's the same as 625239, since I don't have nvidia
hardware (unless I'm reading this wrong?). As for 626723, I have noticed
this text in the past. I will try to reproduce it later on.
** Changed in: gdm (Ubuntu)
Status:
*** This bug is a duplicate of bug 417583 ***
https://bugs.launchpad.net/bugs/417583
** Visibility changed to: Public
** This bug is no longer flagged as a security vulnerability
** This bug has been marked a duplicate of bug 417583
gnome-panel crashed with SIGSEGV in g_closure_invoke()
*** This bug is a duplicate of bug 507062 ***
https://bugs.launchpad.net/bugs/507062
** This bug has been marked a duplicate of bug 507062
synaptic assert failure: synaptic: ../../src/xcb_io.c:385: _XAllocID:
Assertion `ret != inval_id' failed.
* You can subscribe to bug 507062 by followi
Steve, Seth,
The "graphics-device-added fb0 PRIMARY_DEVICE_FOR_DISPLAY=1" removal
tweak is not a guaranteed workaround after all. I just booted up again
and crashed within a minute of use. I was just waiting for a Chrome tab
to open--no keyboard activity this time.
--
X starts on wrong tty becau
Thank you for posting this bug.
As per upstream this issue is Invalid and Launchpad notes Fixed
Released.
Unlinking upstream bug, but if this issue resurfaces, please relink with
Valid bug.
Marking this bug as Fixed Released.
** Changed in: totem
Importance: Unknown => Undecided
** Changed
** Changed in: totem
Status: Incomplete => Invalid
--
Controls are sluggish
https://bugs.launchpad.net/bugs/13415
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
h
on the window border we have "x" button(close), which close every application
instead of rhythmbox
i do not understand why i should use ctrl+q instead of "x" button(close)
to hide rhythmbox we have "_" button(minimize)
--
can't quit from rhythmbox with alt+f4
https://bugs.launchpad.net/bugs/6376
** Visibility changed to: Public
--
gnome-power-manager crashed with signal 5 in _XError()
https://bugs.launchpad.net/bugs/619615
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu.
--
desktop-bugs mailing lis
*** This bug is a duplicate of bug 619615 ***
https://bugs.launchpad.net/bugs/619615
** This bug has been marked a duplicate of private bug 619615
--
gnome-power-manager crashed with signal 5 in _XError()
https://bugs.launchpad.net/bugs/619044
You received this bug notification because you a
Foxit is not free software.
I can't see how Google Docs is relevant here...
--
Searching Hebrew text works in reverse order
https://bugs.launchpad.net/bugs/127732
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing
** Visibility changed to: Public
--
gnome-display-properties crashed with SIGSEGV in g_value_unset()
https://bugs.launchpad.net/bugs/633385
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in ubuntu.
--
desktop-bugs
*** This bug is a duplicate of bug 631001 ***
https://bugs.launchpad.net/bugs/631001
** Visibility changed to: Public
** This bug has been marked a duplicate of bug 631001
gnome-display-properties crashed with SIGSEGV in g_value_init()
* You can subscribe to bug 631001 by following this l
Attached is a cleaner version of the previous patch - instead of
checking whether conversion is NULL check the value of nitems early and
return if it's zero.
** Patch added: "92_return_if_nitems_is_0.patch"
https://bugs.edge.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/626379/+attac
Thank you taking the time to report this bug and helping to make Ubuntu better.
However, processing the crash report to get detailed information for the
developers failed as the retracer did not generate a useful symbolic stack
trace.
Please try to obtain a backtrace manually following the ins
Thank you for your bug report, could you try if that's still an issue
with the current version?
--
gnome-display-properties crashed with SIGSEGV in g_value_unset()
https://bugs.launchpad.net/bugs/633385
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is s
seems the bug fixed in 2.31.91-0ubuntu2, reopen if you still get the
issue though
** Changed in: gnome-control-center (Ubuntu)
Status: New => Fix Released
--
gnome-display-properties crashed with SIGSEGV in g_value_unset()
https://bugs.launchpad.net/bugs/633385
You received this bug notif
** Visibility changed to: Public
--
gcalctool crashed with signal 5 in g_object_newv()
https://bugs.launchpad.net/bugs/632105
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gcalctool in ubuntu.
--
desktop-bugs mailing list
desktop-bugs
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Please answer these questions:
1. Is this reproducible?
2. If so, what specific steps should we take to recreate this bug? Be as
detailed as possible.
This will help us to find and resolve the problem.
** Visibil
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Please answer these questions:
1. Is this reproducible?
2. If so, what specific steps should we take to recreate this bug? Be as
detailed as possible.
This will help us to find and resolve the problem.
** Visibil
Here's the valgrind. I tried to reproduce the steps as closely as i
could remember how the bug happened. Some important steps might differ.
No bug occured.
Let me know how i can help further.
** Attachment added: "Valgrind"
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/636982/+atta
I don't remember changing icon theme, so probably the default. How to find out
which one I am using?
Changing desktop themes do not change the situation.
--
icon incorrect for typing monitor
https://bugs.launchpad.net/bugs/635960
You received this bug notification because you are a member of Ubu
On Tue, Sep 14, 2010 at 07:58, Steve Langasek
wrote:
> has anyone reproduced this nvidia+gdm crash on maverick? Marking
> incomplete for maverick pending confirmation.
>
On my system, this bug was fixed.
--
X starts on wrong tty because gdm starts before nvidia driver is ready
https://bugs.laun
Public bug reported:
Binary package hint: evolution
I'm just starting to use Evolution. The default calendar is called
"Personal", and comes in a light blue color.
I tried to change the color of this calendar:
1. Open evolution.
2. Go to the calendar section.
3. Right click on Personal and click
** Attachment added: "Dependencies.txt"
https://bugs.edge.launchpad.net/bugs/638202/+attachment/1583742/+files/Dependencies.txt
--
can't change default calendar color
https://bugs.launchpad.net/bugs/638202
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, wh
** Visibility changed to: Public
--
yelp crashed with signal 5 in _XError()
https://bugs.launchpad.net/bugs/634268
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to yelp in ubuntu.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.co
*** This bug is a duplicate of bug 633708 ***
https://bugs.launchpad.net/bugs/633708
Thank you for taking the time to report this crash and helping to make
Ubuntu better. This particular crash has already been reported and is a
duplicate of bug #633708, so is being marked as such. Please loo
** Visibility changed to: Public
--
yelp crashed with signal 5 in __libc_start_main()
https://bugs.launchpad.net/bugs/625948
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to yelp in ubuntu.
--
desktop-bugs mailing list
desktop-bugs@lists
101 - 200 of 478 matches
Mail list logo
