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
-
** 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
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
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
*** 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
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 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
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
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
*** 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:
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)
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
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
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
101 - 131 of 131 matches
Mail list logo
