I also have this annoying bug.
Gandalf resolve it in is compiz repo by patching gnome-session.
I attach the actual patch for the 2.16 version.
** Attachment added: gnome-session_patch
http://librarian.launchpad.net/4441152/19_logout_no_grab_server.patch
--
GNOME logout screen doesn't appear
This is actually the same patch, i didn't see that gandalf reported a bug.
I can't say for xcompmgr since i never use it, but you should try.
--
GNOME logout screen doesn't appear when the composite is enabled
https://launchpad.net/bugs/24221
--
desktop-bugs mailing list
Public bug reported:
Hi,
gok crash at startup with the following output :
/dev/js0: Aucun fichier ou répertoire de ce type
** (gok:536): WARNING **: Cannot open input device!
Erreur de segmentation (core dumped)
I'll attach the apport crash report
** Affects: gok (Ubuntu)
Importance:
** Attachment added: _usr_bin_gok.y0T3G0.crash
http://librarian.launchpad.net/4560729/_usr_bin_gok.y0T3G0.crash
--
[edgy] gok crash at startup
https://launchpad.net/bugs/63227
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
*** This bug is a duplicate of bug 58600 ***
This seams to be a duplicate of #58600 #61656.
Commented those three lines make it work :
# InputDevice stylus SendCoreEvents
# InputDevice cursor SendCoreEvents
# InputDevice eraser SendCoreEvents
** This bug has been marked a duplicate of bug
*** This bug is a duplicate of bug 58600 ***
Mark as Duplicate of 58600
--
[edgy] gok crash at startup
https://launchpad.net/bugs/63227
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
*** This bug is a duplicate of bug 58600 ***
I mark this bug as a duplicate of 58600. Feal free to change that if you
think this is not the same issue
** This bug has been marked a duplicate of bug 58600
wacom configuration kills gok
--
gok doesn't work
https://launchpad.net/bugs/61656
--
** Bug 61656 has been marked a duplicate of this bug
** Bug 63227 has been marked a duplicate of this bug
--
wacom configuration kills gok
https://launchpad.net/bugs/58600
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Public bug reported:
Hi,
Since the last update of nautilus (2.16.1) you can't no more create empty file
with right-clickcreate new documentempty file. Every time, you fall to a
permission error :
you do not have permissions to write to the destination
** Affects: nautilus (Ubuntu)
*** This bug is a duplicate of bug 63934 ***
From bug #63934
Was due to a distro patch, this upload fixes the issue:
nautilus (2.16.1-0ubuntu2) edgy; urgency=low
.
* debian/patches/02_umask.patch:
- dropped for now, it creates issues on file creation (Ubuntu: #63934)
** Changed in:
Public bug reported:
Binary package hint: hal
This is a little issue but still annoying.
Using a wrong argument or no argument to the hal init script,
give you the following argument :
* Usage: /etc/init.d/hald {start|stop|restart|force-reload}
which is wrong and should be :
* Usage:
This issue is due to :
hal-0.5.8.1/fdi/policy/10osvendor/20-storage-methods.fdi :
[...]
!-- Ignore fixed partitions which are automatically mounted from fstab --
match key=linux.fstab.mountpoint exists=true
merge key=volume.ignore type=boolfalse/merge
match
Sorry Nicolò Chieffo if i change to much your description of the bug,
but it was to make it more clear.
Regards,
Flo
** Description changed:
- I'm using feisty. In the drivemount applet and in the places menu, the
- only thing that appears is the cdrom. after restarting the dbus daemon
-
I don't see any reason why it should be update-notifier fault :
There is a real problem if hal is started after gnome, what seams to be the case
** Changed in: update-notifier (Ubuntu)
Status: Unconfirmed = Rejected
--
failed to initialize HAL with automated login
I think this bug is due to a problem in the init script priority :
- gdm start with S13
- dbus (and so hal) start with S20
In the majority of the case there is no problem. But if you use automated login
and if there a script between the 2 that take some time, it might fail.
I suggest that
RGilbert, this bug might be a duplicate of 81670.
Do you have the same problem when logout/login (no restart) ?
--
hal failed to initialize
https://launchpad.net/bugs/69160
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
** Summary changed:
- failed to initialize HAL with automated login
+ failed to initialize HAL : gdm init script priority should be at least equal
to dbus one
--
failed to initialize HAL : gdm init script priority should be at least equal to
dbus one
https://launchpad.net/bugs/81670
--
Hal is use by a lot different pieces in the desktop, so if it isn't
update-notifier that shows up this message, it will be show by something else.
So what is important is not to improve the update-notifier message, but to make
hal running properly before gnome start.
--
failed to initialize
It seams that this bug come back today with the new gnome-netstatus
** Changed in: gnome-netstatus (Ubuntu)
Status: Fix Released = Unconfirmed
--
Network Monitor icons are horizontally stretched
https://launchpad.net/bugs/57626
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
Ok, so it appears that the fix was dropped because it wasn't in a patch. enable
frank patch fix the issue.
I provide a debdiff in case :
** Attachment added: debdiff_ubuntu1-ubuntu2
http://librarian.launchpad.net/6424726/debdiff_ubuntu1-ubuntu2
--
Network Monitor icons are horizontally
Be sure that you have 2.12.1-0ubuntu2 it should fix it
--
Network Monitor icons are horizontally stretched
https://launchpad.net/bugs/57626
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Please give me the output of :
apt-cache madison gnome-netstatus-applet
remove and readd the applet and confirm that it works or not.
If it don't work, install
http://flomertens.keo.in/debian/gnome-netstatus-applet_false_i386.deb
remove and readd the applet and confirm that it works or not.
** Description changed:
In feisty, volumes that are mounted from fstab with the options
defaults and/or auto are ignored and in consequence don't show up in
place and in computer://
This is a different behavior from dapper or edgy, where all partitions,
mounted or not, where present
** Description changed:
In feisty, volumes that are mounted from fstab with the options
defaults and/or auto are ignored and in consequence don't show up in
place and in computer://
This is a different behavior from dapper or edgy, where all partitions,
mounted or not, where present
*** This bug is a duplicate of bug 73227 ***
** This bug has been marked a duplicate of bug 73227
[feisty] some partitions do not appear in Places menu
--
Disk-Mounter applet does not show all partitions
https://launchpad.net/bugs/83035
--
desktop-bugs mailing list
*** This bug is a duplicate of bug 73227 ***
** This bug has been marked a duplicate of bug 73227
[feisty] some partitions do not appear in Places menu
--
[Feisty] Fails to display some mounted local partitions
https://launchpad.net/bugs/76936
--
desktop-bugs mailing list
** Description changed:
In feisty, volumes that are mounted from fstab with the options
defaults and/or auto are ignored and in consequence don't show up in
place and in computer://
This is a different behavior from dapper or edgy, where all partitions,
mounted or not, where present
Hum, misread your comment, but anyway, sudo /etc/init.d/dbus restart
should be taken with caution. It's always better to restart gnome in
that case.
--
failed to initialize HAL : gdm init script priority should be at least equal to
dbus one
https://launchpad.net/bugs/81670
--
desktop-bugs
Restarting the all dbus init scripts during a gnome session, could stop support
for some working service (like avahi in your case).
The minimal should be to restart hal :
sudo /etc/dbus-1/events.d/20hal restart
The best is to simply restart gnome.
--
failed to initialize HAL : gdm init script
*** This bug is a duplicate of bug 73227 ***
I believe that this is an other duplicate of 73227.
Tell me if you think that this is an other problem.
Thanks
** This bug has been marked a duplicate of bug 73227
[feisty] some partitions do not appear in Places menu
--
ntfs drive not appearing
This bug might be https://launchpad.net/ubuntu/+source/update-
notifier/+bug/81670
Try to logout/login, and see if you still get the error.
Thanks.
--
Internal error failed to inialize HAL !
https://launchpad.net/bugs/85795
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
Hi,
I have the exact same problem.
In fact the segfault occur when track, album or artist field contain one of
those character ? :
It seams also to be a duplicate of #70147 even if the error message is
not the same (probably because it's not the same version of sound-
juicer)
The problem is
Thanks for the reply.
I use edgy, sound-juicer 2.16.1
With the same procedure than before but with libglib2.0-0-dbg
libgtk2.0-0-dbg, (i already had sound-juicer-dbgsym), i get this
backtrace.
** Attachment added: gdb_sound-juicer_with-all-dbg
Hi robert,
After reading your post, specially the fact that you rip your track on a fat32
fs, like me, i was thinking that it could be the problem.
So i try to extract a track name track 1 ? on an ext3 fs, and it works. So
this is the cause of the crash, but i don't know why it's happens.
I
Changing iocharset and codpage to default didn't change anything.
On a side not, i have no problem when extracting to my ntfs partition
(with utf8 locale).
No idea what's wrong here.
--
track name with a question mark in it causes a seg-fault
https://launchpad.net/bugs/72218
--
desktop-bugs
Wha, that's a shame, good work robert ;) .
So there is nothing to do about it.
However, i think that sound-juicer should provide a better error message
for this kind of error, and not crash.
Flo
--
track name with a question mark in it causes a seg-fault
https://launchpad.net/bugs/72218
--
** Bug watch added: GNOME Bug Tracker #321436
http://bugzilla.gnome.org/show_bug.cgi?id=321436
** Also affects: sound-juicer (upstream) via
http://bugzilla.gnome.org/show_bug.cgi?id=321436
Importance: Unknown
Status: Unknown
--
track name with a question mark in it causes a
Hi,
Do you try to extract on a FAT filesystem ?
If it's the case, this problem is due to the fact that FAT fs can't handle some
special character like ? :
More info there :
https://bugs.launchpad.net/distros/ubuntu/+source/sound-juicer/+bug/72218
So there is nothing you can do against it.
You
*** This bug is a duplicate of bug 72218 ***
** This bug has been marked a duplicate of bug 72218
track name with a question mark in it causes a seg-fault
--
Fails to handle a : in Title and Artist field
https://launchpad.net/bugs/70147
--
desktop-bugs mailing list
Hi,
You should choose your locale according to how your system is actually set.
To get all the configuration supported by your system, try 'locale -a' in a
terminal, and choose according to what is your default language.
I guess it should be pt_BR.utf8 or something.
Say me if it works.
Thanks.
I think it's because the hal patch that support fuse has been drop
(accidentally ?) in feisty hal during update.
Could you please attach the output of 'lshal', and post the output of 'mount'
to confirm this.
Thanks.
--
mounted devices shown as unmounted [feisty]
*** This bug is a duplicate of bug 35354 ***
Ok, that's what i expected :
mount :
/dev/disk/by-uuid/50F0A0A4F0A09230 on /media/sda1 type fuse
(rw,nosuid,nodev,noatime,allow_other)
lshal :
udi = '/org/freedesktop/Hal/devices/volume_uuid_50F0A0A4F0A09230'
[...]
volume.is_mounted = false (bool)
It's seems that the patch has been dropped during merge from edgy to feisty, so
i reopen this bug.
Also see duplicate here : https://launchpad.net/bugs/75796
Thanks.
** Changed in: hal (Ubuntu)
Status: Fix Released = Confirmed
--
hal does not recognize NTFS-FUSE mounted devices as
Public bug reported:
Binary package hint: hal
In feisty, we use the hal mount backend to mount locale removable device.
Ntfs partition device are mount with the utf8 option, but this option is not
allowed in hal since it is not in volume.mount.valid_options, and so mounting
ntfs device is
Public bug reported:
Binary package hint: hal
The locale= option is needed to set locale with ntfs-3g and ntfs-fuse.
This option should be add to volume.mount.valid_options for ntfs volume in
/usr/share/hal/fdi/policy/10osvendor/20-storage-methods.fdi
** Affects: hal (Ubuntu)
Importance:
** Tags added: ntfs-support
--
hal need to allowed utf8 option for ntfs fs
https://launchpad.net/bugs/78142
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
** Tags added: ntfs-support
--
hal does not recognize NTFS-FUSE mounted devices as mounted
https://launchpad.net/bugs/35354
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
** Tags added: ntfs-support
--
Incorrect permissions when accessing an auto-mounted NTFS partition in nautilus.
https://launchpad.net/bugs/41204
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
This is not a nautilus issue.
With only defaults for option, an ntfs partition is mount with :
ro,uid=0,gid=0,fmask=0177,dmask=077
making it unreadable by non-root user. So the permission error is normal.
The problem would be the way the installer set up the ntfs partition, but since
edgy, it is
Is it still an issue ?
--
Nautilus creating directory on NTFS partition
https://launchpad.net/bugs/72750
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Ok, so i reject this one, this is not an nautilus issue anyway.
Thanks.
** Changed in: nautilus (Ubuntu)
Status: Needs Info = Rejected
--
Nautilus creating directory on NTFS partition
https://launchpad.net/bugs/72750
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
*** This bug is a duplicate of bug 73227 ***
** This bug has been marked a duplicate of bug 73227
[feisty] some partitions do not appear in Places menu
--
Mounted Drives do not appear in Desktop or Disk Mounter
https://launchpad.net/bugs/92099
--
desktop-bugs mailing list
Martin, is there any plan to change that in feisty, or do you want to
keep the current behaviour ?
--
[feisty] some partitions do not appear in Places menu
https://launchpad.net/bugs/73227
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
Public bug reported:
Binary package hint: rhythmbox
When starting a CD extraction, there is no way to cancel it without
quitting rhthmbox.
Sugestions :
- A cancel button in the status bar, near the progress bar.
- A cancel button near the extract CD button
- An extract button which is keept
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/13960766/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/13960767/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://launchpadlibrarian.net/13960768/ProcStatus.txt
--
No way to
Public bug reported:
Binary package hint: rhythmbox
Clicking several time on the the exctract CD button queue again and again the
same
tracks for extraction. And since there is no way to cancel an exraction (bug
#223023)
this make the CD extraction experience not really user friendly.
It
** Bug watch added: GNOME Bug Tracker #530189
http://bugzilla.gnome.org/show_bug.cgi?id=530189
** Also affects: rhythmbox via
http://bugzilla.gnome.org/show_bug.cgi?id=530189
Importance: Unknown
Status: Unknown
--
Clicking by error 2 times on the Extract CD button make rhythmbox
** Bug watch added: GNOME Bug Tracker #365306
http://bugzilla.gnome.org/show_bug.cgi?id=365306
** Also affects: rhythmbox via
http://bugzilla.gnome.org/show_bug.cgi?id=365306
Importance: Unknown
Status: Unknown
--
No way to cancel a CD extraction
*** This bug is a duplicate of bug 207693 ***
https://bugs.launchpad.net/bugs/207693
** This bug is no longer a duplicate of bug 199380
gnome-panel crashed with SIGSEGV in g_object_get()
** This bug has been marked a duplicate of bug 207693
gnome-panel crashed with SIGSEGV
--
*** This bug is a duplicate of bug 207693 ***
https://bugs.launchpad.net/bugs/207693
** This bug is no longer a duplicate of bug 199380
gnome-panel crashed with SIGSEGV in g_object_get()
** This bug has been marked a duplicate of bug 207693
gnome-panel crashed with SIGSEGV
--
Panel
*** This bug is a duplicate of bug 207693 ***
https://bugs.launchpad.net/bugs/207693
** This bug has been marked a duplicate of bug 207693
gnome-panel crashed with SIGSEGV
--
gnome-panel crashed with SIGSEGV in g_object_get()
https://bugs.launchpad.net/bugs/199380
You received this bug
https://bugs.edge.launchpad.net/ubuntu/+source/libwnck/+bug/199380 is
the same bug and contains a valgrind showing the issue :
==27419== Invalid read of size 4
==27419==at 0x44B87D1: gtk_tooltip_start_delay (gtktooltip.c:1015)
==27419==by 0x44B93DF: _gtk_tooltip_handle_event
Hi bryce,
gd_randr12_revert_support.patch :
doesn't apply cleanly (as 104_gd_randr12_revert_support.patch)
cc_randr12_revert_dialog.patch :
fail to build. You probably should add at least (most obvious):
#define REVERT_COUNT 40
Also gettext is quite broken.
Another implementation idea
Ok, forget my previous implementation idea, i was confused by the big mess
of the upstream tree. There is of course no apply_configuration in g-s-d, it's a
running daemon (damn i'm stupid). So xrandr_capplet talk to it with Xevents.
So i have an other implementation idea. Why not create an
** Tags added: new-xrandr-capplet
--
Hardy beta: gnome-display-properties allows switching off the only monitor
https://bugs.launchpad.net/bugs/208535
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in ubuntu.
--
Bryce, do you think that the gtk.patch in the upstream source tree might help
one that ?
Anyway, affect to gnome-control-center for now, even if it has nothing to do
here...
** Changed in: gnome-control-center (Ubuntu)
Sourcepackagename: None = gnome-control-center
--
Dual monitor disconnect
** Tags added: new-xrandr-capplet
--
gnome-display-properties should revert change automatically if not acknowledged
https://bugs.launchpad.net/bugs/197673
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in ubuntu.
Is it only GDM that start with the wrong resolution or even gnome ?
If it's only GDM, gnome-display-properties will not help (at least for now)
as it only set the resolution for gnome.
** Tags added: new-xrandr-capplet
--
[Hardy] GDM starts with wrong display resolution
Finaly the gnome-control-center patch
that make use of the above.
** Attachment added: PATCH 3/3
http://launchpadlibrarian.net/13039184/110_cc-randr12-revert-dialog.patch
--
gnome-display-properties should revert change automatically if not acknowledged
https://bugs.launchpad.net/bugs/197673
Then the gnome-setting-daemon patch that make it react
to _GNOME_RANDR_TEST_ATOM xevent
by calling configuration_apply_test.
** Attachment added: PATCH 2/3
http://launchpadlibrarian.net/13039173/93_gsd-randr12-revert-dialog.patch
--
gnome-display-properties should revert change
Hi all,
Here we go.
First the gnome-desktop patch that implement :
configuration_save_test
configuration_apply_test
** Attachment added: Patch 1/3
http://launchpadlibrarian.net/13039165/104_gd-xrandr-revert-dialog.patch
--
gnome-display-properties should revert change automatically if not
Humm, why did it set mime-type to text/html ???
Anyway, this is a first shoot so some tests are required, but overall this
seams to works ok.
No gettext for now but that might be a futur patch. Not the most urgent.
Now i'll take some rest ;)
Cheers
--
gnome-display-properties should revert
Wrong resolution in gnome after restart was fixed by #191878.
Wrong resolution in GDM is not a bug because gnome-display-properties only set
resolution for gnome.
If you want to change it, you'll have to change it manually in xorg.conf.
** Changed in: libxrandr (Ubuntu)
Status: New =
Florent, cool, I'll take a look at your patch tomorrow.
Do as you want. With the actual code i don't see better way to do it.
For now you can't pass objects to g-s-d so you'll always need to store new
config in a test file.
BTW, i wonder why they call configuration_apply_stored() via g-s-d and
Attached is an updated patch for gnome-control-center
It re enable translation.
The *.pot file is correctly updated during build but not the *.po.
This need some `make update-po` magic, and i don't now
how to do that cleanly.
** Attachment added: PATCH 2/3
Please follow Martin Pitt comment if you really want to tackle down the problem.
Without proper debug information, we can't really now why hal failed to start.
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Leeuw a écrit :
In my case it's the, only recently surfaced, connection Philips Tv-card.
I read through this whole thread, noting down dif'rent fixes that didn't seem
to make much sense,
So these means that your bug is different than the original one.
This bug report is really old and was
Did it crash on exit ? If not please open a new bug. Thanks.
--
Tomboy.exe crashed with SIGSEGV in exit()
https://bugs.launchpad.net/bugs/199496
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
--
desktop-bugs mailing list
Some results with an intel 855 GM :
With gnome-settings-daemon 2.21.91-0ubuntu6 and gnome-desktop 2:21.92-ubuntu3
gnome-settings-daemon don't crash anymore at startup.
However, gnome-display-properties still crash with a sligthly different
backtrace :
#0 rw_output_by_id (info=0x1af28, id=77)
Public bug reported:
Binary package hint: gnome-control-center
Starting gnome-display-properties crash at startup.
I got this from standart output :
Resource Timestamp: 39771
Resource Configuration Timestamp: 39771
CRTC 49 Timestamp: 39771
CRTC 4a Timestamp: 39771
Output 4b Timestamp: 39771
I
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/12452737/CoreDump.gz
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/12452738/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/12452739/Disassembly.txt
** Attachment
Bryce Harrington a écrit :
@Florent and rbmorse: Thanks for confirming that the crash is gone on
855, that's a relief. So technically this bug is solved - system start
up is no longer prevented. I'm dropping the priority and milestone.
For the separate gnome-display-properties crash,
Hi Bryce,
X.Org X Server 1.4.0.90
Release Date: 5 September 2007
X Protocol Version 11, Revision 0
Build Operating System: Linux Ubuntu (xorg-server 2:1.4.1~git20080131-1ubuntu5~b
wh1)
Current Operating System: Linux flo-laptop 2.6.24-12-generic #1 SMP Mon Mar 10 1
5:32:00 UTC 2008 i686
Build
Sebastien you are my hero !
--
gnome-display-properties crashed with SIGSEGV in screen_info_new() - i855,
fglrx, radeonhd
https://bugs.launchpad.net/bugs/198951
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-desktop in ubuntu.
I think i can also reproduce this crash.
It's have to do with the new tooltip.
My way to reproduce it is :
1. enable compiz
2. move the mouse over the workspace switcher
3. as soon as the tooltip appears, click on a workspace (different than your
current one, of course)
4. repeat with
** Attachment added: A BIG backtrace of the crash
http://launchpadlibrarian.net/12755790/big_bactrace
--
gnome-panel crashed with SIGSEGV in g_object_get()
https://bugs.launchpad.net/bugs/199380
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a
** Attachment added: A valgrind log
http://launchpadlibrarian.net/12755792/valgrind.log
--
gnome-panel crashed with SIGSEGV in g_object_get()
https://bugs.launchpad.net/bugs/199380
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
*** This bug is a duplicate of bug 199380 ***
https://bugs.launchpad.net/bugs/199380
** This bug has been marked a duplicate of bug 199380
gnome-panel crashed with SIGSEGV in g_object_get()
--
gnome-panel workspace switcher segfaults when switching workspaces
It seams to not be a problem for me anymore.
Bernard, feel free to reopen it if it's still an issue for you.
** Changed in: yelp (Ubuntu)
Status: Incomplete = Fix Released
--
Yelp take a lot of ressource
https://bugs.launchpad.net/bugs/195153
You received this bug notification because
Longsleep, this is a different bug. please see Bug #199960
Thanks
--
gnome-settings-daemon crashed with SIGSEGV
https://bugs.launchpad.net/bugs/197153
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in ubuntu.
--
*** This bug is a duplicate of bug 199380 ***
https://bugs.launchpad.net/bugs/199380
** This bug has been marked a duplicate of bug 199380
gnome-panel crashed with SIGSEGV in g_object_get()
--
Panel crash when switching viewports
https://bugs.launchpad.net/bugs/200629
You received this
I can confirm this bug.
I also can confirm that 'gphoto2 -L' works, so this has nothing to do with the
sansa issue.
I also found that when mounting with right-click-mount it works. Can
somebody try that ?
** Changed in: gvfs (Ubuntu)
Status: Incomplete = Confirmed
--
gvfsd-gphoto2
*** This bug is a duplicate of bug 202304 ***
https://bugs.launchpad.net/bugs/202304
** Tags added: need-i386-retrace
** Tags removed: apport-failed-retrace
--
gvfsd-gphoto2 crashed with SIGSEGV in pthread_mutex_lock()
https://bugs.launchpad.net/bugs/207911
You received this bug
*** This bug is a duplicate of bug 215499 ***
https://bugs.launchpad.net/bugs/215499
** This bug is no longer a duplicate of bug 157396
Copyng a file to a NTFS drive change the date and the time of the file
** This bug has been marked a duplicate of bug 215499
Nautilus not preserving
*** This bug is a duplicate of bug 215499 ***
https://bugs.launchpad.net/bugs/215499
** Changed in: ntfs-config
Status: New = Invalid
** Changed in: ntfs-3g (Ubuntu)
Status: New = Invalid
** This bug has been marked a duplicate of bug 215499
Nautilus not preserving
Public bug reported:
Binary package hint: gnome-games
Just unplayable.
Step to reproduce :
- start any game at any level
- go into a wall.
=You'll lose all your points, while you should lose only one and restart
= You'll continue to play, and you'll be able to cross all walls and users as
you
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/11784278/Dependencies.txt
--
Nibbles is buggy
https://bugs.launchpad.net/bugs/189448
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for gnome-games in ubuntu.
--
I can't reproduce it myself.
I'll reopen it if i can't.
Thanks for your time.
** Changed in: gnome-games (Ubuntu)
Status: Incomplete = Invalid
--
Nibbles is buggy
https://bugs.launchpad.net/bugs/189448
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
Public bug reported:
Binary package hint: yelp
Yelp fail to format certain unix man page correctly, probably because
it fail to recognize certain nroff macros.
Step to reproduce (this is an exemple that require mplayer.) :
1. Open yelp
2. Manual page - application - mplayer
The
INTERACTIVE
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/12174561/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/12174562/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://launchpadlibrarian.net/12174563/ProcStatus.txt
--
Some nroff
1 - 100 of 131 matches
Mail list logo
