** Changed in: gdm
Status: Invalid => Expired
** Changed in: gdm
Importance: Unknown => High
--
[hardy] gdmsetup cause intensive disk activity and take a very long time to open
https://bugs.launchpad.net/bugs/204770
You received this bug notification because you are a member of Ubuntu
** Changed in: gdm
Status: In Progress => Invalid
--
[hardy] gdmsetup cause intensive disk activity and take a very long time to open
https://bugs.launchpad.net/bugs/204770
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubunt
** Branch linked: lp:ubuntu/tracker
--
[hardy] gdmsetup cause intensive disk activity and take a very long time to open
https://bugs.launchpad.net/bugs/204770
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
u
** Branch linked: lp:ubuntu/hardy-proposed/tracker
** Branch linked: lp:ubuntu/intrepid-updates/tracker
--
[hardy] gdmsetup cause intensive disk activity and take a very long time to open
https://bugs.launchpad.net/bugs/204770
You received this bug notification because you are a member of Ubuntu
This bug was fixed in the package tracker - 0.6.6-1ubuntu5.1
---
tracker (0.6.6-1ubuntu5.1) intrepid-proposed; urgency=low
* debian/tracker.install:
- don't install the dbus service so tracker is not automatically started
when other software try to see if it's already runn
** Tags added: verification-done
** Tags removed: verification-needed
--
[hardy] gdmsetup cause intensive disk activity and take a very long time to open
https://bugs.launchpad.net/bugs/204770
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
I tested tracker 0.6.6-1ubuntu5.1 from proposed and I can confirm that
it fixes this bug. It is no longer activated by gdmsetup. Directories
like /root/.cache/tracker, /root/.local/share/tracker and
/root/.config/tracker are no longer created when launching gdmsetup,
unlike version 0.6.6-1ubuntu5.
Accepted into intrepid-proposed, please test and give feedback here.
Please see https://wiki.ubuntu.com/Testing/EnableProposed for
documentation how to enable and use -proposed. Thank you in advance!
** Changed in: tracker (Ubuntu Intrepid)
Status: In Progress => Fix Committed
Target
This bug was fixed in the package tracker - 0.6.6-2ubuntu1
---
tracker (0.6.6-2ubuntu1) jaunty; urgency=low
* Merge from debian unstable, remaining changes:
- debian/sysctl.d/30-tracker.conf:
+ add sysctl for increased inotify limits (broken out from procps).
- debian/
I just confirmed that this is still an issue in intrepid.
** Changed in: tracker (Ubuntu Intrepid)
Status: Fix Committed => In Progress
Target: intrepid-alpha-2 => intrepid-updates
--
[hardy] gdmsetup cause intensive disk activity and take a very long time to open
https://bugs.laun
To the best of my recall, I do not remember seeing this bug on version
8.04.1 of Hardy the last time I did a test installation of it. However,
that HAS been quite a while back.
I do not yet use Hardy because, I still believe Gutsy is the most
reliable release.
Thanks.
--
[hardy] gdmsetup cause
> Is there any progress on this?
Ok a fresh install of Intrepid alpha5, I didn't encountered the trouble.
--
[hardy] gdmsetup cause intensive disk activity and take a very long time to open
https://bugs.launchpad.net/bugs/204770
You received this bug notification because you are a member of Ubu
Is there any progress on this?
--
[hardy] gdmsetup cause intensive disk activity and take a very long time to open
https://bugs.launchpad.net/bugs/204770
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu
I don't necessarily think that it is a good idea to autostart an
indexer. I am just pointing out that some apps rely on it. I say again
"DBus activation
is indeed a double edged sword" :-)
--
[hardy] gdmsetup cause intensive disk activity and take a very long time to open
https://bugs.launchpad.n
why do you think that applications starting tracker over dbus is a good
idea? users don't expect to get their system to start doing lot of io
for the day just because they used deskbar-applet or nautilus search,
especially when they disabled the tracker autostart to avoid that.
autostarting tracker
I see. So either use dbus directly without libtracker, add a
peek_tracker_running() method to libtracker, or disable dbus activation.
The simple solution is of course understandable for Hardy, but may break
other apps (the deskbar handler relies on the activation file for
instance). For intrepid a
the issue is that checking if tracker is running using libtracker will
active the index, that's creating issue for users who desactivated the
service because they don't use it and that's not giving any useful
informations anyway because the indexer starts
--
[hardy] gdmsetup cause intensive disk
This feels as the wrong solution to me. Many apps may assume that
Tracker will start by dbus activation. The 'right' fix is to make the
Tracker backend of the filechooser not launch Tracker, merely see if it
is installed (check if it is dbus activatable)[1]. Then if the user
enters a query then Tra
Needs to be fixed in Intrepid ASAP.
** Changed in: tracker (Ubuntu)
Target: None => intrepid-alpha-2
** Changed in: tracker (Ubuntu)
Status: Confirmed => Fix Committed
--
[hardy] gdmsetup cause intensive disk activity and take a very long time to open
https://bugs.launchpad.net/bu
Copied to hardy-updates.
** Changed in: tracker (Ubuntu Hardy)
Status: Fix Committed => Fix Released
--
[hardy] gdmsetup cause intensive disk activity and take a very long time to open
https://bugs.launchpad.net/bugs/204770
You received this bug notification because you are a member of Ub
I tested it on a vanilla install of 8.04, then enabled hardy-proposed,
updated, and the fix worked okay.
** Attachment added: "unnamed"
http://launchpadlibrarian.net/15172981/unnamed
--
[hardy] gdmsetup cause intensive disk activity and take a very long time to open
https://bugs.launchpad.ne
** Tags added: verification-done
** Tags removed: verification-needed
--
[hardy] gdmsetup cause intensive disk activity and take a very long time to open
https://bugs.launchpad.net/bugs/204770
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
Tested on a clean Hardy installation and on a old Hardy installation and
it seems to work perfectly. I don't really use tracker so I don't know
if there is side effects caused by this patch in tracker.
--
[hardy] gdmsetup cause intensive disk activity and take a very long time to open
https://bug
there is an autostart installed which run it when the session starts,
there is no reason the autoactivation should be required
--
[hardy] gdmsetup cause intensive disk activity and take a very long time to open
https://bugs.launchpad.net/bugs/204770
You received this bug notification because you
Sebastien's proposed patch works for me, though I'm not sure whether it
sacrifices any functionality of tracker in any way, i.e. whether tracker
needs this "autostart" feature under any circumstances.
--
[hardy] gdmsetup cause intensive disk activity and take a very long time to open
https://bugs
Accepted into -proposed, please test and give feedback here
** Changed in: tracker (Ubuntu Hardy)
Status: Confirmed => Fix Committed
Target: ubuntu-8.04.1 => None
** Tags added: verification-needed
--
[hardy] gdmsetup cause intensive disk activity and take a very long time to open
trivial change is to not install the dbus service so tracker will not
been automatically started when not required
** Attachment added: "the debdiff for the stable update"
http://launchpadlibrarian.net/15139212/tracker.debdifff
--
[hardy] gdmsetup cause intensive disk activity and take a very
Sebastien, is a proposed solution available for this bug? I think this
is very worthwhile to have fixed in hardy, though I doubt that 8.04.1 is
a realistic target here; maybe we should be targeting 8.04.2?
** Changed in: tracker (Ubuntu Hardy)
Target: None => ubuntu-8.04.1
--
[hardy] gdm
** Changed in: tracker (Ubuntu)
Target: ubuntu-8.04.1 => None
--
[hardy] gdmsetup cause intensive disk activity and take a very long time to open
https://bugs.launchpad.net/bugs/204770
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
libracker-gtk0 is needed for Tracker, which *is* installed by default. It's
just a bug that needs to be fixed in it, I guess.
However not everyone also has this problem either. I've asked about, and
others don't have it.
** Attachment added: "unnamed"
http://launchpadlibrarian.net/14613368/un
Does this mean that every time I do an installation of Hardy on a new
computer that this is just 1 more thing that I have to put on my either
mental or written listing to change in order to get this to work
correctly or will this libtracker-gtk0 package be fixed so that it
willNOT install during th
Confirmed the bug... and removing libtracker-gtk0 fixed it. Thanks
--
[hardy] gdmsetup cause intensive disk activity and take a very long time to open
https://bugs.launchpad.net/bugs/204770
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Yes, I also get this on the Final release/production version of Hardy.
Seems to me that whatever is causing this should be fixed or at a
minimum something should be put in place to tell the user what is going
on when they initially click on the login window function and it takes
several minutes to
I get this same bug in the release version.
--
[hardy] gdmsetup cause intensive disk activity and take a very long time to open
https://bugs.launchpad.net/bugs/204770
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailin
** Changed in: gdm (Ubuntu Hardy)
Importance: Undecided => Low
Status: New => Invalid
--
[hardy] gdmsetup cause intensive disk activity and take a very long time to open
https://bugs.launchpad.net/bugs/204770
You received this bug notification because you are a member of Ubuntu
Bugs, wh
that's not a gdm bug
** Changed in: tracker (Ubuntu Hardy)
Importance: Undecided => Medium
Assignee: (unassigned) => Ubuntu Desktop Bugs (desktop-bugs)
Status: New => Confirmed
** Changed in: gdm (Ubuntu)
Importance: Undecided => Low
Status: New => Invalid
--
[hardy] gd
We agreed to just disable the automagic tracker activation over dbus by
not installing the .service file any more.
** Changed in: tracker (Ubuntu)
Assignee: (unassigned) => Sebastien Bacher (seb128)
--
[hardy] gdmsetup cause intensive disk activity and take a very long time to open
https://
that's something several users complained about and why we stopped
building nautilus using it, the api to query if tracker is running
should not be using dbus which trigger the autoactivation then but
rather using a lock file on the disk or something which indicates if
tracker is running or not
do
calling a single method in libtracker will trigger launch of trackerd
via dbus activation.
This cannot be fixed at the tracker end as there is no way to turn off
said activation - its an intrinsic property of all dbus services
In this particular case the best we can do is prevent indexing by
tra
gdm doesn't use tracker directory, the dialog uses gtk fileselector
widgets which have a search files entry in the sidebar, that feature is
using tracker when available, now when the dialog is create the widgets
are initialized, gtk uses libtracker to know if tracker is available and
somewhat it ge
I just upgrade from 7.10 to 8.04 LTS yesterday.
The gdmsetup runs normally yesterday before I disable the indexing.
When I run the gdmetup, it shows no error message, but Sebastien says, it
triggers a trackerd up to search for something (I don't know).
So, if I run the indexing, then gdmsetup runs
I really have to ask now (out of genuine curiosity), wtf does tracker
have to do with gdm (or even, gdmsetup for that matter)? isn't it a
user-level app anyway? what is there to index over there? (I guess we
are talking about the tracker indexing/search tool)
--
[hardy] gdmsetup cause intensive d
the issue seems to be due to libtracker, it's trying to use tracker but
should not autostart it if it's not running
--
[hardy] gdmsetup cause intensive disk activity and take a very long time to open
https://bugs.launchpad.net/bugs/204770
You received this bug notification because you are a membe
Saïvann Carignan wrote:
> Thanks for your participation but please don't confirm a bug more than
> once, one confirmation is enough. We should keep bug reports as short
> and relevant as possible to help developers.
I thought it would help to have information that the problem is not a
quirl of a
Thanks for your participation but please don't confirm a bug more than
once, one confirmation is enough. We should keep bug reports as short
and relevant as possible to help developers.
--
[hardy] gdmsetup cause intensive disk activity and take a very long time to open
https://bugs.launchpad.net/
Confirmed again on a clean installation of Hardy final.
As an extra twist, "Login Window" is not displayed on the
"Administration" menu, although according to the menu editor it is
there.
--
[hardy] gdmsetup cause intensive disk activity and take a very long time to open
https://bugs.launchpad.n
Confirmed on a cleanly installed Hardy AMD64.
--
[hardy] gdmsetup cause intensive disk activity and take a very long time to open
https://bugs.launchpad.net/bugs/204770
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mail
Confirmed for a clean installation of Hardy final. Can this be fixed in
8.04.1?
--
[hardy] gdmsetup cause intensive disk activity and take a very long time to open
https://bugs.launchpad.net/bugs/204770
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
Also confirm this with a clean install of Hardy final release. It takes
a long time to load gdmsetup and the intensive ticking of the hard drive
while loading.
--
[hardy] gdmsetup cause intensive disk activity and take a very long time to open
https://bugs.launchpad.net/bugs/204770
You received t
Thanks for all your work. Could tracker be disabled by default for the
root user?
--
[hardy] gdmsetup cause intensive disk activity and take a very long time to open
https://bugs.launchpad.net/bugs/204770
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
** Changed in: gdm
Status: Unknown => In Progress
--
[hardy] gdmsetup cause intensive disk activity and take a very long time to open
https://bugs.launchpad.net/bugs/204770
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubunt
** Also affects: gdm via
http://bugzilla.gnome.org/show_bug.cgi?id=164786
Importance: Unknown
Status: Unknown
--
[hardy] gdmsetup cause intensive disk activity and take a very long time to open
https://bugs.launchpad.net/bugs/204770
You received this bug notification because you are
This bug is a consequence of a longstanding upstream bug:
http://bugzilla.gnome.org/show_bug.cgi?id=164786 (gdm frontend runs
entirely as root)
Notice that this upstream bug was opened in 2005, currently shows an
assigned status, a priority=high and a severity=major.
This bug has been the source
Also confirmed with a clean installation of Hardy Release Candidate.
I hope this will be fixed in time for the final release.
--
[hardy] gdmsetup cause intensive disk activity and take a very long time to open
https://bugs.launchpad.net/bugs/204770
You received this bug notification because you
Confirmed with a clean Hardy RC install.
--
[hardy] gdmsetup cause intensive disk activity and take a very long time to open
https://bugs.launchpad.net/bugs/204770
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing l
55 matches
Mail list logo
