On Mon, Oct 16, 2017 at 05:41:13PM -0700, Adam Williamson wrote:
> As we have decided to release F27 Server on a different cycle from the
> rest of F27, I thought it would make sense to have separate blocker/FE
> tracker bugs for Server. I have now created them and moved appropriate
>
As we have decided to release F27 Server on a different cycle from the
rest of F27, I thought it would make sense to have separate blocker/FE
tracker bugs for Server. I have now created them and moved appropriate
bugs to them, and updated blockerbugs to include the Server milestones:
https
On Mon, 09 Oct 2017 10:27:10 -0400, Matthias Clasen wrote:
> > Toggling various Search options in control center did _not_ stop the
> > four
> > tracker processes and did _not_ purge large files and databases from
> > user's home directory either. Not good.
> >
&
t;a problem", remains to be seen. It's ugly and not
> human-readable. Serialization is for machines, not for human beings.
Fwiw, it only displays the type annotation when it is necessary to
avoid ambiguity. If the array is not empty, it does not show up.
> > >
> Toggling var
ion. So much about making desktop user
> > friendly. It's not even possible to uninstall it because of
> > dependency
> > hell and libs usage:
> >
>
> Feel free to maintain it if you prefer it over the configuration that
> is available via control-center or gsetting
On Thu, 2017-10-05 at 15:51 +0200, Michael Schwendt wrote:
> On Wed, 04 Oct 2017 16:14:22 +0300, Yanko Kaneti wrote:
>
> > > $ gsettings list-recursively | grep -i org.freedesktop.Tracker
>
> While digging, I've come that far, too. Can't say I'm happy, because
> tracker-p
On Wed, 04 Oct 2017 16:14:22 +0300, Yanko Kaneti wrote:
> > $ gsettings list-recursively | grep -i org.freedesktop.Tracker
While digging, I've come that far, too. Can't say I'm happy, because
tracker-preferences at least made it quick and convenient to remove the
index directories.
$ gse
On Wed, Oct 4, 2017 at 3:14 PM, Yanko Kaneti <yan...@declera.com> wrote:
> Upstream decision.
> From the release notes of 1.99.0 - 2017-07-06:
> " * Deleted tracker-preferences. Tracker has been using GSettings for
> years,
> so doesn't specifically require an UI
On Wed, 2017-10-04 at 15:01 +0200, Kamil Paral wrote:
> On Mon, Sep 18, 2017 at 12:41 AM, Michael Schwendt <mschwendt@gmail.c
> om> wrote:
> > Package is absent from F27.
> > How to turn off tracker now?
> >
> > Tracker miners running like mad as one of the
On Mon, Sep 18, 2017 at 12:41 AM, Michael Schwendt <mschwe...@gmail.com>
wrote:
> Package is absent from F27.
> How to turn off tracker now?
>
> Tracker miners running like mad as one of the first things when
> demonstrating
> a fresh install of Fedora to someone, is real
- maybe a hardcore way-
in F26 I do:
- in rc.local: /usr/bin/chmod -x /usr/libexec/tracker*;
- rm -rf /usr/share/dbus-1/services/*Track*;
- reboot
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le
Package is absent from F27.
How to turn off tracker now?
Tracker miners running like mad as one of the first things when demonstrating
a fresh install of Fedora to someone, is really bad.
___
test mailing list -- test@lists.fedoraproject.org
#455: Add blocker bug tracker creation and blocker bug webapp update to QA
schedule
--+--
Reporter: adamwill | Owner:
Type: task | Status: new
Priority: minor | Milestone: Undetermined Future
Component: Wiki
Well, I am sure it is not a show stopper but tracker is going to be a
royal PITA for some users.
In Fedora 20 we have tracker-0.16.5-1.fc20.x86_64 and in Fedora 21 it is
tracker-1.2.4-3.fc21.x86_64. That difference in version/release means
that the tracker developer has been very busy adding
On Wed, 2014-11-19 at 07:37 -0500, Gene Czarcinski wrote:
Well, I am sure it is not a show stopper but tracker is going to be a
royal PITA for some users.
In Fedora 20 we have tracker-0.16.5-1.fc20.x86_64 and in Fedora 21 it
is tracker-1.2.4-3.fc21.x86_64. That difference in version/release
On Tue, 15 Oct 2013 15:44:12 -0600
Chris Murphy li...@colorremedies.com wrote:
A bug is set to block final but isn't listed in the tracker. Should I
file an infrastructure bug, and if so against what component?
Thanks,
Chris Murphy
File it in the qa trac [1] against the blocker bug
Forgot to mention this at the time, but I put up the F20 blocker and
freeze exception tracker bugs a couple of days back.
The old-style aliases (F20Alpha, F20Beta, F20Blocker etc) are no longer
in use: I only created the new-style aliases. All the bug numbers and
aliases are listed at
https
Greetings.
I'd like to propose we create a rawhide tracker bug.
Probibly name it: RawhideBlocker
(But I don't care what colour the bikeshed is)
This bug would be used for the following types of bugs against the
'rawhide' version:
- bugs that prevent the daily rawhide compose from completing
or systemd
issues
that cause most rawhide installs to fail to boot.
What about broken gdm, does it fall into the category? Should critical path
packages be also covered by this tracker bug? (Firefox broken, pulseaudio
broken, gnome-terminal broken, yum broken, ...)
The idea is that folks
On 11/03/13 09:41 AM, Kevin Fenzi wrote:
Greetings.
I'd like to propose we create a rawhide tracker bug.
Probibly name it: RawhideBlocker
(But I don't care what colour the bikeshed is)
This bug would be used for the following types of bugs against the
'rawhide' version:
- bugs that prevent
On Tue, 2013-01-22 at 19:30 -0800, Adam Williamson wrote:
The 'new style' tracker bug aliases are as follows:
AlphaBlocker
AlphaFreezeException
BetaBlocker
BetaFreezeException
FinalBlocker
FinalFreezeException
Versioned aliases will still be applied to all the tracker bugs, so that
we
into 'production' today. I have adjusted the tracker bugs
themselves,
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Trackers ,
https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process ,
https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting , and
renamed
https://fedoraproject.org/wiki
On Mon, Jan 21, 2013 at 11:57:12 -0600,
Adam Williamson awill...@redhat.com wrote:
Proposing a small refinement: we apply the release specific alias
names
to the old trackers after each release. So right now the F19 bugs
would
be AlphaBlocker, AlphaFreezeException etc: when F19 goes
On Jan 22, 2013, at 2:21 AM, Kamil Paral kpa...@redhat.com wrote:
As for the whiteboard labels, to keep things consistent, we can use:
AcceptedBlocker
RejectedBlocker
AcceptedFreezeException
RejectedFreezeException
The latter is a bit long though, any other proposals?
I would drop
On Tue, Jan 22, 2013 at 09:42:22 -0700,
Chris Murphy li...@colorremedies.com wrote:
ProposedBlocker
Blocker
RejectedBlocker
ProposedFreezeException
FreezeException
RejectedFreezeException
And I assume it's still the case each of those has three modifiers: Alpha,
Beta, Final.
I think we
process. We need to indicate
three states:
Proposed
Accepted
Rejected
We cannot do this with only the Blocks: field, which is why the
whiteboard labels exist. In theory you could tell whether a bug which
blocks the tracker is 'proposed' or 'accepted' by checking the comments,
but that's a big
On Tue, Jan 22, 2013 at 12:02:09 -0800,
Adam Williamson awill...@redhat.com wrote:
On Tue, 2013-01-22 at 11:09 -0600, Bruno Wolff III wrote:
2. (bwolff) I think we can live without prefixes for the whiteboard.
There could be cases where a bug is freezeexception for alpha and
blocker for beta,
On Tue, 2013-01-22 at 14:19 -0600, Bruno Wolff III wrote:
On Tue, Jan 22, 2013 at 12:02:09 -0800,
Adam Williamson awill...@redhat.com wrote:
On Tue, 2013-01-22 at 11:09 -0600, Bruno Wolff III wrote:
2. (bwolff) I think we can live without prefixes for the whiteboard.
There could be cases
for the
tracker bugs were inconsistent.
We developed a proposal to rename the aliases and the 'nice to have'
process. This was refined over the period of a few days' discussion on
the test@ mailing list: see
https://lists.fedoraproject.org/pipermail/test/2013-January/113363.html
for the thread
On Tue, 2013-01-22 at 19:30 -0800, Adam Williamson wrote:
I can think of a couple of potential issues with the 'dynamic' tracker
names (I'm not sure whether nominations will 'transfer' from one release
to the next when we change where the alias points, and if so, whether we
want
archives). So I decided to go ahead and Just Do It, putting the
proposal into 'production' today. I have adjusted the tracker bugs
themselves,
Thanks for doing this!
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
to blocker / freeze exception tracker aliases
Hey folks!
At FUDCon Lawrence, Tim Flink presented on the Fedora blocker bug and
'NTH' processes, and we got some interesting and useful feedback. People
felt that the 'nice to have' / 'accepted' name used in that process was
confusing and difficult
The proposal is this:
fXXalpha
fXXalpha-freezebreak
fXXbeta
fXXbeta-freezebreak
fXXfinal
fXXfinal-freezebreak
acceptedblocker
acceptedfb
Big thumbs up. A few things for consideration:
1. Do we need numbers in the alias? We always release just a single Fedora at a
time.
2. Do we
On 01/21/2013 09:48 AM, Kamil Paral wrote:
The proposal is this:
fXXalpha
fXXalpha-freezebreak
fXXbeta
fXXbeta-freezebreak
fXXfinal
fXXfinal-freezebreak
acceptedblocker
acceptedfb
Big thumbs up. A few things for consideration:
1. Do we need numbers in the alias? We always release just a
On Po, 2013-01-21 at 04:48 -0500, Kamil Paral wrote:
The proposal is this:
fXXalpha
fXXalpha-freezebreak
fXXbeta
fXXbeta-freezebreak
fXXfinal
fXXfinal-freezebreak
acceptedblocker
acceptedfb
Big thumbs up. A few things for consideration:
1. Do we need numbers in the
On Mon, Jan 21, 2013 at 04:48:56AM -0500, Kamil Paral wrote:
Big thumbs up. A few things for consideration:
1. Do we need numbers in the alias? We always release just a single Fedora at
a time.
If they're _not_ per release, all of the old dependencies will need to be
removed from the alias
talking
about the *alias*. Not the bug ID. The alias is transferrable. It's not
one tracker bug for all Alpha blockers ever, but one alias which
transfers from bug to bug: we create a new set of bugs for each cycle,
but we just transfer the alias from the old to the new. We can keep
track
On Mon, Jan 21, 2013 at 11:57:12 -0600,
Adam Williamson awill...@redhat.com wrote:
Proposing a small refinement: we apply the release specific alias names
to the old trackers after each release. So right now the F19 bugs would
be AlphaBlocker, AlphaFreezeException etc: when F19 goes out, we
Hi folks! We're running a FUDCon NA workshop session today to try and
actually knock out some QA 'low-hanging fruit', and the one we tried to
deal with this morning is the blocker tracker bug names. We had some
grand ideas for making this even better in the glorious future, which
involve more good
On 01/20/2013 06:49 PM, Adam Williamson wrote:
This is an issue that's come up repeatedly in the past and was also came
up during the talk Tim gave on the blocker process on Friday: the
feedback from everyone at the meeting (QA people and non-QA people) was
that the current names were really bad
On Sun, 2013-01-20 at 19:05 +, Jóhann B. Guðmundsson wrote:
On 01/20/2013 06:49 PM, Adam Williamson wrote:
This is an issue that's come up repeatedly in the past and was also came
up during the talk Tim gave on the blocker process on Friday: the
feedback from everyone at the meeting (QA
On Sun, 2013-01-20 at 13:27 -0600, Adam Williamson wrote:
and can you point me
to any talk where this has come up?
There've been multiple threads and meeting discussions, I don't have
references handy, but I thought you'd remember that too...
On Sun, Jan 20, 2013 at 12:49 PM, Adam Williamson awill...@redhat.com wrote:
Hi folks! We're running a FUDCon NA workshop session today to try and
actually knock out some QA 'low-hanging fruit', and the one we tried to
deal with this morning is the blocker tracker bug names. We had some
grand
#306: Blockers that move to 'CLOSED' are not removed from the tracker page
---+---
Reporter: tflink| Owner: tflink
Type: defect| Status: closed
Priority: major
Hi there,
if you find any bugs in Xfce or the Xfce spin, please let them block the
'F18Xfce' tracker bug [1] so we can look into them ASAP.
Kind regards,
Christoph
[1] https://bugzilla.redhat.com/show_bug.cgi?id=863722
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https
Am Sonntag, den 07.10.2012, 02:10 +0200 schrieb Christoph Wickert:
Hi there,
if you find any bugs in Xfce or the Xfce spin, please let them block the
'F18Xfce' tracker bug [1] so we can look into them ASAP.
Sorry, I forgot to mention that this bug is *only* for Xfce on F18 or
F19, maybe even
#311: Bug #847644 does not show up as a proposed blocker in the new blocker
tracker
---+---
Reporter: adamwill | Owner: tflink
Type: defect| Status: closed
Priority: critical
#311: Bug #847644 does not show up as a proposed blocker in the new blocker
tracker
---+---
Reporter: adamwill | Owner: tflink
Type: defect| Status: new
Priority: critical
#311: Bug #847644 does not show up as a proposed blocker in the new blocker
tracker
--+
Reporter: adamwill | Owner: tflink
Type: defect| Status: new
Priority: critical
#311: Bug #847644 does not show up as a proposed blocker in the new blocker
tracker
---+---
Reporter: adamwill | Owner: tflink
Type: defect| Status: new
Priority: critical
#311: Bug #847644 does not show up as a proposed blocker in the new blocker
tracker
---+---
Reporter: adamwill | Owner: tflink
Type: defect| Status: new
Priority: critical
#311: Bug #847644 does not show up as a proposed blocker in the new blocker
tracker
---+---
Reporter: adamwill | Owner: tflink
Type: defect| Status: new
Priority: critical
#296: Fix blocker bug tracker page and replace it with a static HTML page
-+---
Reporter: adamwill| Owner: tflink
Type: task| Status: new
Priority: major
#306: Blockers that move to 'CLOSED' are not removed from the tracker page
--+
Reporter: tflink| Owner: tflink
Type: defect| Status: new
Priority: major
#296: Fix blocker bug tracker page and replace it with a static HTML page
---+---
Reporter: adamwill | Owner: tflink
Type: task | Status: new
Priority: major | Milestone: Fedora 18
Component: Wiki |Version
#296: Fix blocker bug tracker page and replace it with a static HTML page
---+---
Reporter: adamwill | Owner: tflink
Type: task | Status: new
Priority: major | Milestone: Fedora 18
Component: Wiki |Version
#296: Fix blocker bug tracker page and replace it with a static HTML page
---+---
Reporter: adamwill | Owner: tflink
Type: task | Status: new
Priority: major | Milestone: Fedora 18
Component: Wiki |Version
#296: Fix blocker bug tracker page and replace it with a static HTML page
---+---
Reporter: adamwill | Owner: tflink
Type: task | Status: new
Priority: major | Milestone: Fedora 18
Component: Wiki |Version
#296: Fix blocker bug tracker page and replace it with a static HTML page
--+
Reporter: adamwill | Owner: tflink
Type: task | Status: new
Priority: major | Milestone: Fedora 18
Component: Wiki | Version
#296: Fix blocker bug tracker page and replace it with a static HTML page
---+---
Reporter: adamwill | Owner: tflink
Type: task | Status: new
Priority: major | Milestone: Fedora 18
Component: Wiki |Version
#296: Fix blocker bug tracker page and replace it with a static HTML page
---+---
Reporter: adamwill | Owner: tflink
Type: task | Status: new
Priority: major | Milestone: Fedora 18
Component: Wiki |Version
#296: Fix blocker bug tracker page and replace it with a static HTML page
---+---
Reporter: adamwill | Owner: tflink
Type: task | Status: new
Priority: major | Milestone: Fedora 18
Component: Wiki |Version
On Sat, 2012-04-21 at 18:34 -0400, Braden McDaniel wrote:
I've noticed several tracker-extract processes hanging around,
sleeping; 8 at the moment. Is this normal?
doesn't seem terribly unusual if you have tracker running, though if
they hang around for very long it might be. May be better
#154: Tracker: critical path test case creation
--+-
Reporter: adamwill | Owner: adamwill
Type: enhancement | Status: closed
Priority: major| Milestone: Fedora 15
Component: Wiki
Hey, folks. Just a note that I've created the blocker and NTH tracker
bugs for F17 and F18, as per the process documented at
http://fedoraproject.org/wiki/BugZappers/HouseKeeping/Trackers :
https://bugzilla.redhat.com/show_bug.cgi?id=F17Alpha
https://bugzilla.redhat.com/show_bug.cgi?id=F17Beta
On Wed, Oct 12, 2011 at 2:27 AM, Adam Williamson awill...@redhat.com wrote:
On Sat, 2011-10-08 at 22:27 -0400, Jonathan Kamens wrote:
Anybody else seeing anything like this? Known issue? Open bug?
I'd say it's a 'known issue' in the sense that every freaking 'desktop
search' mechanism I've
On Sat, 08 Oct 2011 22:27:17 -0400, JK (Jonathan) wrote:
I don't know whether Tracker is new or just updated in F16. I certainly
never noticed it running on my system before upgrading recently to F16.
What I'm noticing now is that it's tacking up a huge amount of CPU. Not
disk I/O, mind
On 10/09/2011 05:41 AM, Michael Schwendt wrote:
Last month's New bugs in updates thread contained a subthread on
tracker search tool. There are a couple of issues with tracker.
* It indexes removable devices by default.
Doesn't appear to be the case with my F16 beta install. I didn't turn
On Sun, 09 Oct 2011 07:48:41 -0400, JK (Jonathan) wrote:
On 10/09/2011 05:41 AM, Michael Schwendt wrote:
Last month's New bugs in updates thread contained a subthread on
tracker search tool. There are a couple of issues with tracker.
* It indexes removable devices by default
On Sat, 2011-09-10 at 15:20 +0200, Michael Schwendt wrote:
On Sat, 10 Sep 2011 13:12:50 +, JBG (Jóhann) wrote:
Tracker can be disabled in gnome-session-properties I myself did that
sometime during alpha since it caused excessive load on my laptop...
Which is the tool I've been
On Fri, 09 Sep 2011 20:38:21 -0600, DJG (Dariusz) wrote:
Yet, I get tracker, where I didn't ask for it. It would have been OK if it
was disabled by default
but not only it wasn't but it created problems for me (not to mention what is
the point of scanning
removable media by default
On Fri, Sep 9, 2011 at 10:22 PM, Adam Williamson awill...@redhat.com wrote:
On Fri, 2011-09-09 at 19:31 +0200, Michael Schwendt wrote:
On Fri, 9 Sep 2011 17:39:32 +0100, PR (Peter) wrote:
6) Tracker (apart from having crashed) started to appear at the top of
top
with heavy CPU usage
On 09/10/2011 12:13 PM, Peter Robinson wrote:
Actually its only grilo-plugins that depends on it, totem then depends
on grilo-plugins and shotwell on totem.
The tracker support in grilo-plugins can easily be split into a
grilo-plugins-tracker subpackage so that would be the easy way to lose
On Fri, 9 Sep 2011 13:13:25 +0200, me wrote:
6) Tracker (apart from having crashed) started to appear at the top of top
with heavy CPU usage. I hope that won't go on like that.
To fight that, I've stopped the mining, then used
yum -y install tracker-search-tool
to install two more tracker
On Fri, Sep 9, 2011 at 5:29 PM, Michael Schwendt mschwe...@gmail.com wrote:
On Fri, 9 Sep 2011 13:13:25 +0200, me wrote:
6) Tracker (apart from having crashed) started to appear at the top of top
with heavy CPU usage. I hope that won't go on like that.
To fight that, I've stopped the mining
On Fri, 9 Sep 2011 17:39:32 +0100, PR (Peter) wrote:
6) Tracker (apart from having crashed) started to appear at the top of
top
with heavy CPU usage. I hope that won't go on like that.
To fight that, I've stopped the mining, then used
yum -y install tracker-search-tool
On Fri, 2011-09-09 at 19:31 +0200, Michael Schwendt wrote:
On Fri, 9 Sep 2011 17:39:32 +0100, PR (Peter) wrote:
6) Tracker (apart from having crashed) started to appear at the top of
top
with heavy CPU usage. I hope that won't go on like that.
To fight that, I've stopped
On 09/09/11 10:29 AM, Michael Schwendt wrote:
On Fri, 9 Sep 2011 13:13:25 +0200, me wrote:
6) Tracker (apart from having crashed) started to appear at the top of top
with heavy CPU usage. I hope that won't go on like that.
To fight that, I've stopped the mining, then used
yum -y
On Fri, 2011-09-09 at 18:54 -0600, Dariusz J. Garbowski wrote:
Sadly, tracker affected my interest in Solang... Why do I need another search
tool on my system?
Already have locate. KDE comes with it's own stuff (which I disable by
default). Now another one
sneaks in...
tracker
On 09/09/11 08:22 PM, Adam Williamson wrote:
On Fri, 2011-09-09 at 18:54 -0600, Dariusz J. Garbowski wrote:
Sadly, tracker affected my interest in Solang... Why do I need another
search tool on my system?
Already have locate. KDE comes with it's own stuff (which I disable by
default). Now
#154: Tracker: critical path test case creation
--+-
Reporter: adamwill | Owner: adamwill
Type: enhancement | Status: new
Priority: major| Milestone: Fedora 15
Component: Wiki
#154: Tracker: critical path test case creation
--+-
Reporter: adamwill | Owner: adamwill
Type: enhancement | Status: new
Priority: major| Milestone: Fedora 15
Component: Wiki
#154: Tracker: critical path test case creation
--+-
Reporter: adamwill | Owner: adamwill
Type: enhancement | Status: new
Priority: major| Milestone: Fedora 15
Component: Wiki
#154: Tracker: critical path test case creation
--+-
Reporter: adamwill | Owner: adamwill
Type: enhancement | Status: new
Priority: major| Milestone: Fedora 15
Component: Wiki
#154: Tracker: critical path test case creation
--+-
Reporter: adamwill | Owner: adamwill
Type: enhancement | Status: new
Priority: major| Milestone: Fedora 15
Component: Wiki
#154: Tracker: critical path test case creation
--+-
Reporter: adamwill | Owner: adamwill
Type: enhancement | Status: new
Priority: major| Milestone: Fedora 15
Component: Wiki
#154: Tracker: critical path test case creation
--+-
Reporter: adamwill | Owner: adamwill
Type: enhancement | Status: new
Priority: major| Milestone: Fedora 15
Component: Wiki
#154: Tracker: critical path test case creation
--+-
Reporter: adamwill | Owner: adamwill
Type: enhancement | Status: new
Priority: major| Milestone: Fedora 15
Component: Wiki
#154: Tracker: critical path test case creation
--+-
Reporter: adamwill | Owner: adamwill
Type: enhancement | Status: new
Priority: major| Milestone: Fedora 15
Component: Wiki
#154: Tracker: critical path test case creation
--+-
Reporter: adamwill | Owner: adamwill
Type: enhancement | Status: new
Priority: major| Milestone: Fedora 15
Component: Wiki
#154: Tracker: critical path test case creation
--+-
Reporter: adamwill | Owner: adamwill
Type: enhancement | Status: new
Priority: major| Milestone: Fedora 15
Component: Wiki
#154: Tracker: critical path test case creation
--+-
Reporter: adamwill | Owner: adamwill
Type: enhancement | Status: new
Priority: major| Milestone: Fedora 15
Component: Wiki
#154: Tracker: critical path test case creation
--+-
Reporter: adamwill | Owner: adamwill
Type: enhancement | Status: new
Priority: major| Milestone: Fedora 15
Component: Wiki
#154: Tracker: critical path test case creation
--+-
Reporter: adamwill | Owner: adamwill
Type: enhancement | Status: new
Priority: major| Milestone: Fedora 15
Component: Wiki
2011/2/16 Adam Williamson:
Hey, everyone. I've created a tracker bug to try and collect all cases
where GNOME Shell initialization fails and fallback mode doesn't work
Current nightly spins (not always, never (?)) enable the GNOME shell
on systems for which gnome-shell --replace launches
On Fri, 2011-02-18 at 20:47 +0100, Christoph Frieben wrote:
2011/2/16 Adam Williamson:
Hey, everyone. I've created a tracker bug to try and collect all cases
where GNOME Shell initialization fails and fallback mode doesn't work
Current nightly spins (not always, never (?)) enable the GNOME
On Fri, 2011-02-18 at 11:56 -0800, Adam Williamson wrote:
On Fri, 2011-02-18 at 20:47 +0100, Christoph Frieben wrote:
2011/2/16 Adam Williamson:
Hey, everyone. I've created a tracker bug to try and collect all cases
where GNOME Shell initialization fails and fallback mode doesn't work
Hey, everyone. I've created a tracker bug to try and collect all cases
where GNOME Shell initialization fails and fallback mode doesn't work -
i.e. where trying to enter GNOME results in a complete failure (but you
can get into a non-accelerated desktop, like Xfce). If your bug report
meets
#154: Tracker: critical path test case creation
--+-
Reporter: adamwill | Owner: adamwill
Type: enhancement | Status: new
Priority: major| Milestone: Fedora 15
Component: Wiki
#154: Tracker: critical path test case creation
--+-
Reporter: adamwill | Owner: adamwill
Type: enhancement | Status: new
Priority: major| Milestone: Fedora 15
Component: Wiki
1 - 100 of 132 matches
Mail list logo
