** Attachment removed: "5DA98279D76FCF11.jpg"
https://bugs.launchpad.net/ubuntu/hardy/+source/nautilus-actions/+bug/182345/+attachment/4920647/+files/5DA98279D76FCF11.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
Thank you for reporting this bug to Ubuntu. Hardy reached EOL on May 9, 2013.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
** Changed in: nautilus-actions (Ubuntu Hardy)
Status: New => Invalid
--
You received this bug notification because yo
** Changed in: nautilus
Importance: Unknown => Critical
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
https://bugs.launchpad.net/bugs/182345
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Branch linked: lp:ubuntu/nautilus-actions
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
https://bugs.launchpad.net/bugs/182345
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@li
Happens to me in Ibex when I switch between Compiz and Metacity
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
https://bugs.launchpad.net/bugs/182345
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
> Hopefully, next LTS is soon.
It was opened for Hardy, why is it ignored. Hardy is LTS - does that mean 'Long
Term Suffering'?
Do we have to open a new bug report to get that fixed?
** Changed in: nautilus-actions (Ubuntu Hardy)
Status: Won't Fix => New
--
nautilus crashed with SIGSEGV
The patch is not trivial enough to be ported to hardy/intrepid.
Hopefully, next LTS is soon.
FYI, it's already fixed in jaunty and karmic.
** Changed in: nautilus-actions (Ubuntu Hardy)
Status: In Progress => Won't Fix
** Changed in: nautilus-actions (Ubuntu Intrepid)
Status: In Pr
The package already has been fixed, just those who are using
[b]Hardy[/b] still have to wait for the backport - that's [b]Long
Term[/b] (Support)
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
https://bugs.launchpad.net/bugs/182345
You received this bug notification because you ar
Hello,
Removing the nautilus-actions package eliminates this crash on start up,
so the problem must reside within that package.
Later, Ray Parrish
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
https://bugs.launchpad.net/bugs/182345
You received this bug notification because you
I will give it a shot next week after Jaunty RC.
I think this is more an update that is needed than a backport. So I
closed the backport request and add targeted release there.
** Also affects: nautilus-actions (Ubuntu Intrepid)
Importance: Undecided
Status: New
** Changed in: nautilus
done, see here:
https://bugs.launchpad.net/hardy-backports/+bug/357634
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
https://bugs.launchpad.net/bugs/182345
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs m
Here's how to request a backport:
https://help.ubuntu.com/community/UbuntuBackports#How%20to%20request%20new%20packages
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
https://bugs.launchpad.net/bugs/182345
You received this bug notification because you are a member of Ubuntu
Bugs,
And when will the fix be available in Hardy repository?
Please consider that this bug was reported first for Hardy since 1 year.
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
https://bugs.launchpad.net/bugs/182345
You received this bug notification because you are a member of Ubu
This bug was fixed in the package nautilus-actions -
1.4.1+svn521-0ubuntu1
---
nautilus-actions (1.4.1+svn521-0ubuntu1) jaunty; urgency=low
* Take SVN version to fix SIGSEGV crash in
gconf_client_remove_dir and autilus_actions_config_gconf_reader_finalize
(LP: #182345, #2711
Hey there Tobias!
Sorry to pass a bad word, but I am having the problem with the fresh
install. I am not sure what caused it, and for me, it just pops up
occasionally.
On Tue, Apr 7, 2009 at 5:21 AM, Tobias Gross wrote:
> I just wanted to mention: I did a clean fresh install of 9.04 from the
I just wanted to mention: I did a clean fresh install of 9.04 from the
desktop CD and and I did not have any error since then. So it seems to
be related to upgrade's only - at least for me. Unfortunate, I am now
unable to reproduce...
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
I tried a lot now and it doesn't make a difference if I have a separeted
/home or not. Interesting thing is that for instance my mythfrontend
doesn't work either. It quits with a segmention fault as well.
https://bugs.launchpad.net/bugs/355220
--
nautilus crashed with SIGSEGV in gconf_client_remo
I also have the issue in Jaunty Beta with a separate /home partition (ext4) and
a / partition (ext4).
It doesn't happen all the time though, I don't know yet what causes it.
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
https://bugs.launchpad.net/bugs/182345
You received this bug
I didn't have this error before. What I did most recently:
I moved my /home directory to a new separated partition (ext4) from the
terminal (gdm stopped).
Afterwards I mounted the new /home, started gdm, logged into gnome and
finally got the crash-report "nautilus crashed with SIGSEGV in
gconf_cl
? Reinstalling the package doesn't help, removing it,
was very scary!
Taufik Hasan
--- On Sat, 3/28/09, Patrick Coutu wrote:
From: Patrick Coutu
Subject: [Bug 182345] Re: nautilus crashed with SIGSEGV in
gconf_client_remove_dir()
To: tfk252ha...@yahoo.com
Date: Saturday, March 28, 2009,
Same here... I get this problem on every start... Ubuntu 9.04 beta
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
https://bugs.launchpad.net/bugs/182345
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs maili
Upgraded to Jaunty, after reboot I get this message. all is working
fine.
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
https://bugs.launchpad.net/bugs/182345
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bug
In my case (reported as https://bugs.launchpad.net/bugs/336737) this
does not occur when Nautilus starts, but when I close a Nautilus which I
have started from the command line. Pedro Villavicencio thought it was
a duplicate of this bug (which it may very well be), so he closed my bug
report.
--
Same for me, crash at start.
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
https://bugs.launchpad.net/bugs/182345
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
h
I get this crash after logging into jaunty.. every time.
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
https://bugs.launchpad.net/bugs/182345
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ub
Once more. At the beginning of a Gnome session, two hours ago also.
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
https://bugs.launchpad.net/bugs/182345
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mail
Apport says: nautilus crashed with SIGSEGV in gconf_client_remove_dir()
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
https://bugs.launchpad.net/bugs/182345
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Jaunty, restart after an update just now. Got a message that Nautilus
crashed. Could open Nautilus normally.
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
https://bugs.launchpad.net/bugs/182345
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
The same problem to me, i'm using ubuntu hardy 64 with a machine core 2
duo and nvidia card.
Keep the good work ubuntu Team.
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
https://bugs.launchpad.net/bugs/182345
You received this bug notification because you are a member of Ubuntu
The same happens to me: I can keep using Nautilus normally.
It hasn't happened again since a long ago, so I thing it's solved.
Bye
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
https://bugs.launchpad.net/bugs/182345
You received this bug notification because you are a member of U
Hello,
This crash report happens often after closing Nautilus or on a new boot
up. I never have any problems running Nautilus, and it never shuts down
on me, I just keep getting crash reports periodically.
Later, Ray Parrish
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
https://
happening to me a lot..
** (nautilus:7115): WARNING **: Unable to add monitor: Operation not supported
SSSNautilus-Share-Messag
Thank you for your reply.
I just get a lot of crash reports from nautilus... sometimes up to six in a
row. mostly when closing nautilus.
sincerely,
adrian
On Fri, Nov 7, 2008 at 12:03 AM, matiuzalem <[EMAIL PROTECTED]>
wrote:
> Any problem since few weeks with nautilus, but I don't know why!
>
Any problem since few weeks with nautilus, but I don't know why!
Good luck ;)
matiuzalem
On 06/11/2008, Volnei <[EMAIL PROTECTED]> wrote:
>
> Happened to me after closing Nautilus that had been opened by right-
> clicking context menu and choosing "Open as administrator". Just a while
> after t
Happened to me after closing Nautilus that had been opened by right-
clicking context menu and choosing "Open as administrator". Just a while
after the window was closed, the "crash report" showed in. I'm using
Hardy fully up-to-date.
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
unsubscribe
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
https://bugs.launchpad.net/bugs/182345
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubun
@ingo: no, the issue is indeed in nautilus-actions. It was fixed in
upstream SVN, but not yet released. Since the package is currently
unmaintained, it may take a while for the fix to be made available. If
you follow the upstream bug you will see the original
maintainer/developer stating he does no
I confirm this bug on Intrepid.
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
https://bugs.launchpad.net/bugs/182345
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.co
if the problem had been fixed for some intermittend time as stated
above, does that not mean it is not caused by nautilus-achtins and
instead should be assigned to nautilus?
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
https://bugs.launchpad.net/bugs/182345
You received this bug
I mean currently (not correctly) orphaned (in other words,
unmaintained). Sorry.
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
https://bugs.launchpad.net/bugs/182345
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubu
hum. nautilus-actions is correctly orphaned upstream.
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
https://bugs.launchpad.net/bugs/182345
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubunt
I am taking this out of 'Fix Committed': upstream has not yet published
the fix. The problem has been identified, and it seems it was already
fixed in SVN quite a long time ago, but the updated code has not yet
been released. I am unsure why it was set upstream as 'RESOLVED/FIXED'
*before* the avai
I still get it on a dayly base and can easily predict when apport will
pop up and report it:
When after logging in the icon for a nfs-mount on my desktop is
displaced in a different position, it only takes minutes until apport
reports the crash.
Hardy with all available an proposed fixes.
--
na
I got this error today for the first time. Occurred after downloading
the latest updates for Ubuntu 8.10
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
https://bugs.launchpad.net/bugs/182345
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
On every login to the gnome-desktop I get the error. There appears another
error-messoge-box, telling me, that nautilus can't find the
bonobo-activation-server.
So everytime I have to kill bonobo manually and restart nautilus manually.
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir
Got this today while logged in via FreeNX, latest updates.
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
https://bugs.launchpad.net/bugs/182345
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I just got this error today latest updates/all updates running latest
intrepid
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
https://bugs.launchpad.net/bugs/182345
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubunt
Things are even worse:
when opening nautilus with 'gksudo' a device gets mounted, which is in
/etc/fstab, but with 'noauto option'!
(/dev/sdb1 /media/sdb1 ext2 defaults,noatime,noauto 0
2)
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
https://bugs.launchpad.net
I just repeated Daniel's procedure and got apport pop-up with the
information filed as Bug #278021
So, seems the fix is not (yet) applied to Hardy?
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
https://bugs.launchpad.net/bugs/182345
You received this bug notification because you
Atl + F2 > gksudo nautilus > works fine! > closing nautilus > everthing
is fine > crash report
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
https://bugs.launchpad.net/bugs/182345
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
Fixed in Upstream svn.
** Changed in: nautilus-actions (Ubuntu)
Status: Triaged => Fix Committed
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
https://bugs.launchpad.net/bugs/182345
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
** Changed in: nautilus
Status: Unknown => Fix Released
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
https://bugs.launchpad.net/bugs/182345
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing l
** Changed in: nautilus
Importance: Undecided => Unknown
Bugwatch: None => GNOME Bug Tracker #480179
Status: New => Unknown
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
https://bugs.launchpad.net/bugs/182345
You received this bug notification because you are a memb
** Changed in: nautilus
Importance: Unknown => Undecided
Bugwatch: GNOME Bug Tracker #480179 => None
Status: Fix Released => New
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
https://bugs.launchpad.net/bugs/182345
You received this bug notification because you are a
** Changed in: nautilus
Status: Confirmed => Fix Released
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
https://bugs.launchpad.net/bugs/182345
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
I don't understand that this bug is always assigned to nautilus-actions:
Ubuntu-Hardy uses version 1.4.1-1ubuntu1
The same version in the Debian repository has no open bugs assigned to it, see
here:
http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=nautilus-actions;dist=unstable
So it is either n
** This bug is no longer flagged as a security issue
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
https://bugs.launchpad.net/bugs/182345
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu
I am getting this one frequently,
It seems to be related somehow with gvsf-trash crash:
Reported by tdflanders 4 hours ago (Activity log) (undecided) Bug
268825:
gvfsd-trash crashed with SIGSEGV in IA__g_main_context_dispatch()
The wastebin opens for no reason wile I am working in Nautilu
[EMAIL PROTECTED]:~$ lsb_release -rd ; uname -a ; apt-cache policy
linux-headers-2.6.27-2-generic linux-image-2.6.27-2-generic linux
linux-source-2.6.27 linux-restricted-modules nautilus
Description:Ubuntu intrepid (development branch)
Release:8.10
Linux thomas-laptop 2.6.27-2-generi
this happens in intrepid as well when your root nautilus
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
https://bugs.launchpad.net/bugs/182345
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ub
Just got this on logging in.
Using up-to-date 8.10.
Nautilus ver: 1:2.23.6.1-0ubuntu1
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
https://bugs.launchpad.net/bugs/182345
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** This bug has been flagged as a security issue
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
https://bugs.launchpad.net/bugs/182345
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
Still happens after today's (2008-08-01) major 'proposed' GNOME-update on
Hardy 8.04.1
Please fix asap.
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
https://bugs.launchpad.net/bugs/182345
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
happen also here !!! please fix
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
https://bugs.launchpad.net/bugs/182345
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.co
It just happened to me today after a reboot.
Hardy 8.04
Nautilus 1:2.22.2-0ubuntu6
Linux 2.6.24-17-generic x86_64
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
https://bugs.launchpad.net/bugs/182345
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Changed in: nautilus
Status: Unknown => Confirmed
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
https://bugs.launchpad.net/bugs/182345
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Also experiencing.
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
https://bugs.launchpad.net/bugs/182345
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lis
confirming. i have the same issue.
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
https://bugs.launchpad.net/bugs/182345
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu
Occurs at right after boot and at random on up-to-date hardy beta
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
https://bugs.launchpad.net/bugs/182345
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailin
Occurs every boot on Hardy Beta
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
https://bugs.launchpad.net/bugs/182345
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.co
Confirmed here as well on up-to-date Hardy Beta...
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
https://bugs.launchpad.net/bugs/182345
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b
I confirm it. Here it occurred when upgrading language packs.
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
https://bugs.launchpad.net/bugs/182345
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing li
i have amd64
Just started a new session and had the crash report to do...Nothing seems to be
broken... also.
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
https://bugs.launchpad.net/bugs/182345
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
Occurred every time when I start nautilus with "gksudo nautilus" do what
I need to do, and close it. Then it happends.
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
https://bugs.launchpad.net/bugs/182345
You received this bug notification because you are a member of Ubuntu
Bugs, w
Same here, up-to-date hardy.
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
https://bugs.launchpad.net/bugs/182345
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
h
Using Hardy fully updated/upgraded
Same here...
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
https://bugs.launchpad.net/bugs/182345
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
Occurred while installing lots of software and then using sudo nautilus
at the same time
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
https://bugs.launchpad.net/bugs/182345
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: nautilus
Bugwatch: GNOME Bug Tracker #496332 => GNOME Bug Tracker #480179
Status: Invalid => Unknown
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
https://bugs.launchpad.net/bugs/182345
You received this bug notification because you are a member of Ubunt
** Changed in: nautilus
Status: New => Invalid
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
https://bugs.launchpad.net/bugs/182345
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubunt
** Changed in: nautilus
Status: Unknown => New
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
https://bugs.launchpad.net/bugs/182345
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
thanks for your report, that's more like a nautilus-actions issue, re
assigning. Also known upstream you can track it here:
http://bugzilla.gnome.org/show_bug.cgi?id=496332
** Changed in: nautilus-actions (Ubuntu)
Sourcepackagename: nautilus => nautilus-actions
Status: New => Triaged
** Vi
81 matches
Mail list logo
