** Changed in: nautilus
Importance: Unknown => Critical
--
Permissions of symlinked source file/folder set to 777 if symlink is copied via
nautilus
https://bugs.launchpad.net/bugs/418135
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subs
** Changed in: glib2.0 (Ubuntu Dapper)
Status: Fix Committed => Invalid
--
Permissions of symlinked source file/folder set to 777 if symlink is copied via
nautilus
https://bugs.launchpad.net/bugs/418135
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, wh
** Changed in: glib2.0 (Ubuntu Dapper)
Status: Invalid => Fix Committed
--
Permissions of symlinked source file/folder set to 777 if symlink is copied via
nautilus
https://bugs.launchpad.net/bugs/418135
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, wh
** Visibility changed to: Public
--
Permissions of symlinked source file/folder set to 777 if symlink is copied via
nautilus
https://bugs.launchpad.net/bugs/418135
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
--
desktop-bugs
** Visibility changed to: Private
--
Permissions of symlinked source file/folder set to 777 if symlink is copied via
nautilus
https://bugs.launchpad.net/bugs/418135
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
--
desktop-bugs
This bug was fixed in the package glib2.0 - 2.16.6-0ubuntu1.2
---
glib2.0 (2.16.6-0ubuntu1.2) hardy-security; urgency=low
* Backported patch from Karmic: fix permissions being overwritten when
copying symlinks (LP: #418135).
- Add debian/patches/61_skip-perms-on-symlinks.pat
This bug was fixed in the package glib2.0 - 2.18.2-0ubuntu2.2
---
glib2.0 (2.18.2-0ubuntu2.2) intrepid-security; urgency=low
* Backported patch from Karmic: fix permissions being overwritten when
copying symlinks (LP: #418135).
- Add debian/patches/62_skip-perms-on-symlinks.
This bug was fixed in the package glib2.0 - 2.20.1-0ubuntu2.1
---
glib2.0 (2.20.1-0ubuntu2.1) jaunty-security; urgency=low
* Backported patch from Karmic: fix permissions being overwritten when
copying symlinks (LP: #418135).
- Add debian/patches/61_skip-perms-on-symlinks.pa
CVE-2009-3289
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2009-3289
--
Permissions of symlinked source file/folder set to 777 if symlink is copied via
nautilus
https://bugs.launchpad.net/bugs/418135
You received this bug notification because you are a member of Ubuntu
Deskt
These are building in the security queue now; thanks for all the work in
testing and building! I adjusted the changelogs to use the -security
pocket, but other than that, it looks great. Once they're built, I'll
get them tested again and published.
** Changed in: glib2.0 (Ubuntu Intrepid)
I just tested this on a VBox Dapper, seems like the issue is nonexistant there.
Invalidating for now.
** Changed in: glib2.0 (Ubuntu Dapper)
Status: Confirmed => Invalid
--
Permissions of symlinked source file/folder set to 777 if symlink is copied via
nautilus
https://bugs.launchpad.net
Arands update seems to fix everything for me now, thanks.
--
Permissions of symlinked source file/folder set to 777 if symlink is copied via
nautilus
https://bugs.launchpad.net/bugs/418135
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
I've edited the patch to use g_set_error instead of g_set_error_literal (simply
replacing the function since the arguments seems to already be in the right
format).
Since I have minimal knowledge about the actual code involved in this I can
only confirm that it works with no immediate regression
Getting the fix into hardy may be non-trivial, since the patch seems to
depend on the function g_set_error_literal, which is, i assume, not
implemented in pre-intrepid glib (attached build errors for hardy).
This function is implemented here:
http://mail.gnome.org/archives/svn-commits-list/2008-Ju
added new debdiff for intrepid, typo in changelog regarding patch
filename. (61_* is already in intrepid for another patch, I simply used
62_* instead)
** Attachment added: "backport_to_intrepid_debdiff"
http://launchpadlibrarian.net/31532869/backport_to_intrepid_debdiff
--
Permissions of sym
** Attachment removed: "backport_to_intrepid_debdiff"
http://launchpadlibrarian.net/31519411/backport_to_intrepid_debdiff
--
Permissions of symlinked source file/folder set to 777 if symlink is copied via
nautilus
https://bugs.launchpad.net/bugs/418135
You received this bug notification becau
** Description changed:
Binary package hint: nautilus
TEST CASE:
1. Create a symlink to a file or folder, on which you normally are able
change permissions. (touch ~/testfile && ln -s ~/testfile ~/testlink)
2. Copy the symlink to anywhere using Nautilus (ctrl+c && ctrl+v)
3. Check pe
I've put together a proposed update for intrepid as well which has been built
and tested locally in an i386 virtualbox instance (issue gone, no immediate
regressions).
This also uploaded to my ppa, testing welcome.
Attached debdiff of this proposed update.
** Attachment added: "backport_to_intre
** Also affects: glib2.0 (Ubuntu Dapper)
Importance: Undecided
Status: New
** Changed in: glib2.0 (Ubuntu Dapper)
Status: New => Confirmed
--
Permissions of symlinked source file/folder set to 777 if symlink is copied via
nautilus
https://bugs.launchpad.net/bugs/418135
You rece
I've uploaded the proposed jaunty updated version to my ppa:
https://launchpad.net/~arand/+archive/ppa
I've tested this on i386 & amd64, where I it seems to solve the issue,
with no noticable regressions so far, Bispop's issue included.
--
Permissions of symlinked source file/folder set to 777 i
Bispop, I cannot confirm that, for me viewing trash when it contains a
*.desktop file works absolutely fine. So it seems like there might be
more to that issue than just this update?
--
Permissions of symlinked source file/folder set to 777 if symlink is copied via
nautilus
https://bugs.launch
ill take the last one back, can anyone confirm that the update crashes
nautilus when trying to open the trash when it contains a *.desktop
file?
--
Permissions of symlinked source file/folder set to 777 if symlink is copied via
nautilus
https://bugs.launchpad.net/bugs/418135
You received this bu
2.21.5-0ubuntu3 seems to fix everything, thank you.
--
Permissions of symlinked source file/folder set to 777 if symlink is copied via
nautilus
https://bugs.launchpad.net/bugs/418135
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.
Quick testing in VBox confirms that 2.21.5-0ubuntu3 fixes the bug and
solves the regression.
I mixed together a proposition debdiff for the backport to Jaunty, if
that's of any use.
** Attachment added: "proposed backport to Jaunty debdiff"
http://launchpadlibrarian.net/31293950/backport_to_ja
Thanks for the report! I actually just updated the patch to use the
upstream patch, which should solve this regression. Once it builds,
please test 2.21.5-0ubuntu3 to validate it has been fixed.
--
Permissions of symlinked source file/folder set to 777 if symlink is copied via
nautilus
https:/
Hello, i noticed that if you install the updatet glib you cannot drag
shortcuts onto the desktop from the applications menu anymore, it
complainis about not being able to set permissions on symlinks,
downgrading fixes this.
--
Permissions of symlinked source file/folder set to 777 if symlink is c
Created a debdiff for Jaunty using the upstream patch, also added
(replaced) to PPA
** Attachment added: "upstream_patch_debdiff"
http://launchpadlibrarian.net/31119367/upstream_patch_debdiff
--
Permissions of symlinked source file/folder set to 777 if symlink is copied via
nautilus
https://
This bug has been fixed upstream using what seems like a completely
different method, we might have to consider whether we want that or
current karmic solution.
** Changed in: nautilus
Status: New => Fix Released
--
Permissions of symlinked source file/folder set to 777 if symlink is copi
** Attachment added: "rough_debdiff"
http://launchpadlibrarian.net/3974/rough_debdiff
--
Permissions of symlinked source file/folder set to 777 if symlink is copied via
nautilus
https://bugs.launchpad.net/bugs/418135
You received this bug notification because you are a member of Ubuntu
D
Tested on Jaunty by simply adding 61_skip-perms-on-symlinks.patch from karmic
source and inserting entry in series file (debian/patches).
This fixes the bug on current Jaunty.
I've created a _rough_ debdiff with my changes and added this package to my
ppa: https://launchpad.net/~arand/+archive/pp
** Also affects: glib2.0 (Ubuntu Hardy)
Importance: Undecided
Status: New
** Also affects: glib2.0 (Ubuntu Intrepid)
Importance: Undecided
Status: New
** Also affects: glib2.0 (Ubuntu Karmic)
Importance: Medium
Assignee: Ubuntu Desktop Bugs (desktop-bugs)
Status
This bug is also present (in virtualbox instances) on:
ubuntu 8.04 livecd & updated install
ubuntu 8.10 livecd & updated install
(fedora 11 updated install, GNOME Developer Kit 2.27.20090727 & updated)
There seems to be some SRUing to do...
--
Permissions of symlinked source file/folder set to 7
This bug was fixed in the package glib2.0 - 2.21.5-0ubuntu2
---
glib2.0 (2.21.5-0ubuntu2) karmic; urgency=low
* Add debian/patches/61_skip-perms-on-symlinks.patch, fix permissions
being overwritten when copying symlinks (LP: #418135).
-- Kees CookMon, 31 Aug 2009 18:49:12
** Package changed: nautilus (Ubuntu) => glib2.0 (Ubuntu)
** Changed in: glib2.0 (Ubuntu)
Status: Triaged => In Progress
--
Permissions of symlinked source file/folder set to 777 if symlink is copied via
nautilus
https://bugs.launchpad.net/bugs/418135
You received this bug notification b
This can cause really nasty side-effects for people using symlinks into
their encrypted Private directory. This needs to be fixed for Karmic
and SRU'd to Jaunty.
--
Permissions of symlinked source file/folder set to 777 if symlink is copied via
nautilus
https://bugs.launchpad.net/bugs/418135
Yo
** Changed in: nautilus (Ubuntu)
Milestone: None => karmic-alpha-6
--
Permissions of symlinked source file/folder set to 777 if symlink is copied via
nautilus
https://bugs.launchpad.net/bugs/418135
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a
the description cannot be updated without posting a new comment, saw you
subscribed there, could you add a comment? Thanks.
--
Permissions of symlinked source file/folder set to 777 if symlink is copied via
nautilus
https://bugs.launchpad.net/bugs/418135
You received this bug notification becaus
37 matches
Mail list logo
