Re: Non-responsive maintainer: joost

2018-02-03 Thread Mattia Verga

Il 03/02/2018 01:05, Artur Iwicki ha scritto:

Hi, Richard.

What's the status on trying to reach joost? I use Pascal for some of my 
personal projects, so it's important to me that the Pascal stack in Fedora is 
operational.

Have you began the procedure to take over the packages from joost? I'd be 
willing to join as a co-maintainer. Alternatively, if you don't feel like 
taking over the maintainer responsibilities, I would be willing to become the 
new maintainer for FPC and Lazarus.

Thanks for your work.
A.I.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
I also had many problems in the past to get any response from joost, it 
seems he replies very rarely to bugs and updates.
And also take notice of fpc-srpm-macros package, which defines a macro 
to specify on what architectures pascal packages can be built.


I think whoever takes maintainer responsibilities for fpc should also 
take them for lazarus, because they interact closely.


Mattia
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org


Re: Non-responsive maintainer: joost

2018-02-03 Thread Christopher Meng
Richard Shaw 于2018年1月26日 周五上午12:57写道:

> Per the policy I am asking here if anyone knows how to get in touch with
> joost (jo...@cnoc.nl).
>
> I have bug reports for both fpc and lazarus that have gone for weeks
> without any response and it's preventing me from building cqrlog on armv7hl
> in rawhide due to lazbuild and hedgewars has a segmentation fault due to a
> bug in fpc.
>
> I have tried direct emails with no response.
>

In the past I also had trouble contacting joost, I remember that he spent 3
weeks replying to one of my several emails to him.

> --
Yours sincerely,
Christopher Meng
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org


Re: Non-responsive maintainer: joost

2018-02-03 Thread Richard Shaw
Well I could not find any activity for 2018 so we're well past 3 weeks at
this point. I have filed a ticket here:

https://pagure.io/fesco/issue/1838

But I don't want to maintain the packages, I can barely keep up with the
ones I already have on here and RPM Fusion.

Thanks,
Richard
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org


gobject-introspection broken requires

2018-02-03 Thread Richard Shaw
DEPRECATION WARNING: python2 invoked with /usr/bin/python.
Use /usr/bin/python3 or /usr/bin/python2
/usr/bin/python will be removed or switched to Python 3 in the future.
If you cannot make the switch now, please follow instructions at
https://fedoraproject.org/wiki/Changes/Avoid_usr_bin_python_in_RPM_Build#Quick_Opt-Out
DEPRECATION WARNING: python2 invoked with /usr/bin/python.
Use /usr/bin/python3 or /usr/bin/python2
/usr/bin/python will be removed or switched to Python 3 in the future.
If you cannot make the switch now, please follow instructions at
https://fedoraproject.org/wiki/Changes/Avoid_usr_bin_python_in_RPM_Build#Quick_Opt-Out
+ /usr/lib/rpm/brp-python-hardlink
+ /usr/lib/rpm/redhat/brp-mangle-shebangs
*** WARNING: mangling shebang in ./usr/bin/g-ir-scanner from #!/usr/bin/env
/usr/bin/python to #!/usr/bin//usr/bin/python2. This will become an ERROR,
fix it manually!
*** WARNING: mangling shebang in ./usr/bin/g-ir-annotation-tool from
#!/usr/bin/env /usr/bin/python to #!/usr/bin//usr/bin/python2. This will
become an ERROR, fix it manually!
*** WARNING: mangling shebang in ./usr/bin/g-ir-doc-tool from
#!/usr/bin/env /usr/bin/python to #!/usr/bin//usr/bin/python2. This will
become an ERROR, fix it manually!
Processing files: gobject-introspection-1.54.1-3.fc28.x86_64

Looks like brp-mangle-shebangs incorrectly updated the python invocation.
Since this requirement cannot be met it's breaking any package from
building that depends on it.


Thanks,
Richard
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org


Re: gobject-introspection broken requires

2018-02-03 Thread Richard Shaw
* Sat Feb 03 2018 Richard Shaw  - 1.54.1-4
- Add python2 to configure so shebangs are properly updated by
  brp-mangle-shebangs.

Fixed and rebuilt.

Thanks,
Richard
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org


COPR + pagure + rpkg HOWTO?

2018-02-03 Thread Richard Shaw
I would like to manage a COPR via SCM (in this case pagure)

I'm assuming using rpkg would be a good way to do this? Or should I forget
that and just use plain git+copr-cli?

There is OK documentation for the independent tools but I can't seem to
find a HOWTO that ties it all together.

I want to use my pagure project: https://pagure.io/NBEMS

To tie into my COPR project:
https://copr.fedorainfracloud.org/coprs/hobbes1069/NBEMS/

so I can stop uploading package to my fedorapeople public_html site and
build via URLs.

Second question. My plan is to use this to mainly build packages for EL7 of
all the most useful applications from http://w1hkj.com for emergency
communications on a stable and LTS platform.

Some of them are already in EPEL but need newer versions of dependent
libraries than are available to build the latest versions.

I was thinking of using a git branch per application but that's not a
typical workflow, but seems better than just using master and a bunch of
subdirectories.

Thoughts?
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org


ghc 8.2 now in Rawhide

2018-02-03 Thread Jens-Ulrik Petersen
The Haskell SIG is pleased to announce that the ghc Haskell compiler has
been updated from 8.0.2 to 8.2.2 in Fedora Rawhide (for more information
see http://fedoraproject.org/wiki/Changes/GHC_8.2).

Most Haskell packages have already been updated and/or rebuilt.


A few remaining excepts are:

darcs (needs a patch)

ghc-gi-ggit
ghc-gi-gio  (these needs an upstream patch to ghc)
ghc-gi-ostree
ghc-ltk

haskell-platform (pending)

ghc-listsafe (new package)

hedgewars (statically linked and should rebuild fine)


Cheers, Jens
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org


Re: [Fedora-packaging] Re: Proposed Fedora packaging guideline: More Go packaging

2018-02-03 Thread nicolas . mailhot

De: "Jakub Cajka" 

Hi Jakub

> I'm strongly against general unrestricted practice of compat packages as 
> proposed. If you need compat package you
> need to work with usptreams on stabilizing the API/project, fork it, or just 
> use COPR as your projects(or its
> dependencies) are not yet mature enough for Fedora.

I appreciate the sentiment, and I quite hate compat packages, but the 
restrictions you want did not work in practice for Fedora.

Making compat package creation hard does not result in faster fixing to use new 
code. What it actually does is to block the packaging of all the projects that 
need a more recent package state, because packagers that need the old state for 
one of their packages, will drag their feet on updating common dependencies 
till the code of their packages is fixed upstream, or they have the time to fix 
it themselves.

And blocking packaging of new part means you do not get the new packagers that 
would join because they're interested in the new parts, and would contribute to 
the maintenance of common deps (not all of which need compat-ing), and would 
relieve part of the pressure on the existing packagers, that prevents them from 
working as much a they'd like to on updating their packages. It's a death 
spiral. It results in a massively obsolete Go package baselines, full of holes, 
because all the energy is poured in making existing stuff work, at the expense 
of onboarding new packages and packagers. 

Regards,

-- 
Nicolas Mailhot
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org


Re: COPR + pagure + rpkg HOWTO?

2018-02-03 Thread Michal Novotny
Hello Richard,

On Sat, Feb 3, 2018 at 3:45 PM, Richard Shaw  wrote:

> I would like to manage a COPR via SCM (in this case pagure)
>
> I'm assuming using rpkg would be a good way to do this? Or should I forget
> that and just use plain git+copr-cli?
>
> There is OK documentation for the independent tools but I can't seem to
> find a HOWTO that ties it all together.
>
> I want to use my pagure project: https://pagure.io/NBEMS
>
> To tie into my COPR project: https://copr.fedorainfracloud.org/coprs/
> hobbes1069/NBEMS/
>
> so I can stop uploading package to my fedorapeople public_html site and
> build via URLs.
>

So you need to first go to "Packages" in your project, click on each
package that you want to integrate with Pagure, then at "Default Build
Source" panel, click "Edit". And pick "SCM" tab. After that
you need to insert correct values (especially for Clone URL), enable
"Webhook rebuild" and click Submit. Afterwards in your Pagure project, you
need to enable Sending Fedmsgs (in the _Hooks_ panel)
down the Setting screen. And that should be it. This is assuming that you
have the packages that you want to rebuild automatically already created by
previous srpm builds. If not, you can just create them
manually from scratch.


>
> Second question. My plan is to use this to mainly build packages for EL7
> of all the most useful applications from http://w1hkj.com for emergency
> communications on a stable and LTS platform.
>
> Some of them are already in EPEL but need newer versions of dependent
> libraries than are available to build the latest versions.
>
> I was thinking of using a git branch per application but that's not a
> typical workflow, but seems better than just using master and a bunch of
> subdirectories.
>

Yes, typically, it's just master (optionally with some other dev branches)
and bunch of subdirectories in the main repo for each subpackage. Git
branch per application will technically work as well so it's a matter of
preference.

clime


>
> Thoughts?
>
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
>
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org


Re: Proposed Fedora packaging guideline: More Go packaging

2018-02-03 Thread Nicolas Mailhot
Hi Robert André

That's an interesting request

I guess you can't figure if the example is for building binaries or Go libs, 
because there is no hard frontier between both cases in the proposed guidelines

In Go, everything is effectively a code library that can be reused elsewhere. 
So the approach taken in the proposed guidelines, is that everything is a code 
library, some of which happen to build binaries, or setup compatibility 
symlinks, or need bootstrapping

It's a bit of a Lego guideline, you assemble the spec blocs you need, and 
ignore those you don't need. The example was chosen to include as many blocks 
as possible, with the walkthrough explaining their respective functions. All 
the blocks are very short and succinct, don't search for long runs of shell 
code like in the old guidelines
-- 
Envoyé de mon appareil Android avec Courriel K-9 Mail. Veuillez excuser ma 
brièveté.___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org


[Test-Announce] Proposal to CANCEL: 2018-02-05 Fedora QA Meeting

2018-02-03 Thread Adam Williamson
Hi folks! I'm proposing we cancel the QA meeting on Monday. I'll be
traveling again, and I don't think there are any urgent topics at this
time.

If anyone would like to have a meeting, and is willing to run it in my
place, please just go ahead and send an announcement mail (and, of
course, show up to run the meeting on Monday). Thanks!
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net
___
test-announce mailing list -- test-annou...@lists.fedoraproject.org
To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org


[Test-Announce] Proposal to CANCEL: 2018-02-05 blocker review meeting

2018-02-03 Thread Adam Williamson
Hi folks! I'm proposing we cancel the blocker review meeting for
Monday. There are no proposed blockers for Beta or Final at this
time, so nothing to talk about. Thanks!
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net
___
test-announce mailing list -- test-annou...@lists.fedoraproject.org
To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org


Re: [Test-Announce] Proposal to CANCEL: 2018-02-05 blocker review meeting

2018-02-03 Thread Silvia Sánchez
Hi,

I actually have an issue that could be a Beta blocker but I didn't file the
bug because I don't know where to do so, and there were no meetings so far,
so I hadn't the chance to discuss it.

Regards,
Silvia
FAS: Lailah



On 3 February 2018 at 18:14, Adam Williamson 
wrote:

> Hi folks! I'm proposing we cancel the blocker review meeting for
> Monday. There are no proposed blockers for Beta or Final at this
> time, so nothing to talk about. Thanks!
> --
> Adam Williamson
> Fedora QA Community Monkey
> IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
> http://www.happyassassin.net
> ___
> test-announce mailing list -- test-annou...@lists.fedoraproject.org
> To unsubscribe send an email to test-announce-leave@lists.
> fedoraproject.org
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org


Re: gnome crashes after today upgrade

2018-02-03 Thread Richard Shaw
Any news on the cause? I'm waiting to update until this is figured out...

Thanks,
Richard
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org


Re: [Test-Announce] Proposal to CANCEL: 2018-02-05 blocker review meeting

2018-02-03 Thread Adam Williamson
On Sat, 2018-02-03 at 19:17 +, Silvia Sánchez wrote:
> Hi,
> 
> I actually have an issue that could be a Beta blocker but I didn't file the
> bug because I don't know where to do so, and there were no meetings so far,
> so I hadn't the chance to discuss it.

Hi Silvia! Please just file the bug against something and set the
Blocks: field to 'BetaBlocker' - this should mark it as a proposed
blocker (you will see it show up in the blockerbugs app an hour or so
later). It's also be fine to bring this sort of thing up during the QA
meeting in the Open Floor section :)

Thanks for testing!
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org


Re: gnome crashes after today upgrade

2018-02-03 Thread Tomasz Kłoczko
On 3 February 2018 at 22:55, Richard Shaw  wrote:

> Any news on the cause? I'm waiting to update until this is figured out...
>

Still don't see any update about the issue.
It is really pain in the a*s that Linux still has no good support to handle
such cases like it is on for example on Solaris where is possible to
generate using zfs snapshots and cloning separated BEs (boot environments)
on each upgrade or even new package install which adds to grub menu new
boot entry which allows preserve 100% state from before any packages
operations.
Just checked a bit dnf documentation and seems that dnf supports rollback
operation. However as long as Fedora repo holds only latest versions of the
each package I'm only curious how it is handled as rpm no longer supports
repackage and rollback operations (?).

Can someone share some details how to use dnf rollback and/or is it now
supported by Fedora rawhide?
Issues like this one with crashing gnome may happen always an no one should
be bashing anyone for such faults as rawhide is devel by definition however
details about how system needs to be prepared to handle rollback using dnf
are quite important.

kloczek
-- 
Tomasz Kłoczko | LinkedIn: *http://lnkd.in/FXPWxH *
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org


Fedora Rawhide-20180203.n.0 compose check report

2018-02-03 Thread Fedora compose checker
Missing expected images:

Workstation live i386
Kde live i386

Failed openQA tests: 9/129 (x86_64), 4/22 (i386), 1/2 (arm)

ID: 190546  Test: x86_64 Server-dvd-iso server_role_deploy_domain_controller
URL: https://openqa.fedoraproject.org/tests/190546
ID: 190576  Test: i386 Workstation-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/190576
ID: 190577  Test: i386 Workstation-boot-iso memory_check
URL: https://openqa.fedoraproject.org/tests/190577
ID: 190578  Test: x86_64 KDE-live-iso desktop_notifications_live
URL: https://openqa.fedoraproject.org/tests/190578
ID: 190579  Test: x86_64 KDE-live-iso install_default_upload
URL: https://openqa.fedoraproject.org/tests/190579
ID: 190580  Test: x86_64 KDE-live-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/190580
ID: 190581  Test: x86_64 KDE-live-iso install_no_user
URL: https://openqa.fedoraproject.org/tests/190581
ID: 190591  Test: arm Minimal-raw_xz-raw.xz 
install_arm_image_deployment_upload
URL: https://openqa.fedoraproject.org/tests/190591
ID: 190593  Test: x86_64 Atomic-dvd_ostree-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/190593
ID: 190594  Test: x86_64 Atomic-dvd_ostree-iso install_default
URL: https://openqa.fedoraproject.org/tests/190594
ID: 190614  Test: x86_64 universal upgrade_server_domain_controller
URL: https://openqa.fedoraproject.org/tests/190614
ID: 190620  Test: x86_64 universal install_package_set_kde
URL: https://openqa.fedoraproject.org/tests/190620
ID: 190669  Test: i386 universal install_package_set_kde
URL: https://openqa.fedoraproject.org/tests/190669
ID: 190675  Test: i386 universal upgrade_2_desktop_32bit
URL: https://openqa.fedoraproject.org/tests/190675

Soft failed openQA tests: 19/129 (x86_64), 3/22 (i386)
(Tests completed, but using a workaround for a known bug)

ID: 190554  Test: i386 Server-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/190554
ID: 190555  Test: i386 Server-dvd-iso install_default
URL: https://openqa.fedoraproject.org/tests/190555
ID: 190559  Test: x86_64 Workstation-live-iso install_default_upload
URL: https://openqa.fedoraproject.org/tests/190559
ID: 190561  Test: x86_64 Workstation-live-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/190561
ID: 190562  Test: x86_64 Workstation-live-iso install_no_user
URL: https://openqa.fedoraproject.org/tests/190562
ID: 190572  Test: x86_64 Workstation-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/190572
ID: 190575  Test: x86_64 Workstation-boot-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/190575
ID: 190602  Test: x86_64 universal upgrade_minimal_64bit
URL: https://openqa.fedoraproject.org/tests/190602
ID: 190603  Test: x86_64 universal upgrade_desktop_encrypted_64bit
URL: https://openqa.fedoraproject.org/tests/190603
ID: 190615  Test: x86_64 universal upgrade_kde_64bit
URL: https://openqa.fedoraproject.org/tests/190615
ID: 190617  Test: x86_64 universal upgrade_2_desktop_64bit
URL: https://openqa.fedoraproject.org/tests/190617
ID: 190626  Test: x86_64 universal upgrade_desktop_64bit
URL: https://openqa.fedoraproject.org/tests/190626
ID: 190627  Test: x86_64 universal upgrade_server_64bit
URL: https://openqa.fedoraproject.org/tests/190627
ID: 190629  Test: x86_64 universal upgrade_2_minimal_64bit
URL: https://openqa.fedoraproject.org/tests/190629
ID: 190631  Test: x86_64 universal upgrade_2_kde_64bit
URL: https://openqa.fedoraproject.org/tests/190631
ID: 190639  Test: x86_64 universal install_iscsi
URL: https://openqa.fedoraproject.org/tests/190639
ID: 190657  Test: x86_64 universal upgrade_2_server_64bit
URL: https://openqa.fedoraproject.org/tests/190657
ID: 190659  Test: x86_64 universal upgrade_2_desktop_encrypted_64bit
URL: https://openqa.fedoraproject.org/tests/190659
ID: 190662  Test: x86_64 universal install_european_language
URL: https://openqa.fedoraproject.org/tests/190662
ID: 190663  Test: x86_64 universal install_cyrillic_language
URL: https://openqa.fedoraproject.org/tests/190663
ID: 190664  Test: x86_64 universal install_asian_language
URL: https://openqa.fedoraproject.org/tests/190664
ID: 190667  Test: i386 universal upgrade_desktop_32bit
URL: https://openqa.fedoraproject.org/tests/190667

Passed openQA tests: 88/129 (x86_64), 15/22 (i386)

Skipped openQA tests: 11 of 153
-- 
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org


Re: gnome crashes after today upgrade

2018-02-03 Thread Sam Varshavchik

Tomasz Kłoczko writes:

On 3 February 2018 at 22:55, Richard Shaw  
hobbes1...@gmail.com> wrote:


   Any news on the cause? I'm waiting to update until this is figured out...

Still don't see any update about the issue.
It is really pain in the a*s that Linux still has no good support to handle


One option that's available to you is to switch to another desktop. No  
issues here, whatsoever, on my XFCE desktop.


I replaced Gnome with XFCE on all my desktops a number of years ago, and  
haven't looked back.


pgpUl344AnHyE.pgp
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org


Re: Wyland is a disaster

2018-02-03 Thread Howard Howell
On Thu, 2018-02-01 at 09:08 -0800, Howard Howell wrote:
> On Wed, 2018-01-31 at 09:43 -0800, Howard Howell wrote:
> > On Wed, 2018-01-31 at 14:14 +0100, Olivier Fourdan wrote:
> > > Hi
> > > 
> > > On Wed, Jan 31, 2018 at 1:58 PM, Olivier Fourdan  > > .com> wrote:
> > > > Jan 31 01:14:08 school gnome-session[1715]: gnome-session-
> > > > binary[1715]: WARNING: App 'org.gnome.Shell.desktop' exited
> > > > with 
> > > > > Jan 31 01:14:08 school org.gnome.Shell.desktop[1785]: Window
> > > > > manager error: Could not find cursor. Perhaps set
> > > > > XCURSOR_PATH
> > > > 
> > > > Interesting, that could be the problem! gnome-shell is both a
> > > > Wayland compositor (thus the display server) and an X11 window
> > > > manager.
> > > > 
> > > 
> > > Are you using a custom cursor theme or the default “Adwaita”
> > > cursor theme? 
> > >  
> > > > I think we should keep those discussions, including these
> > > > important bits, in the issue you filed upstream (https://gitlab
> > > > gnome.org/GNOME/gnome-shell/issues/9) and not in a downstream
> > > > mailing list :)
> > > > 
> > > 
> > > And... I got confused by multiple issues being reported in the
> > > same mail thread, that issue was filed by Przemek, so probably
> > > different from yours...
> > > 
> > > Cheers,
> > > Olivier
> > > 
> > OK!  I did change the cursor theme.  According to gnome-tweak-tool, 
> > it is Gamma.Gold.  I have some vision problems and this looked good
> > to me.
> > 
> > Regards,
> > Les H
> > ___
> > devel mailing list -- devel@lists.fedoraproject.org
> > To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> I replied back to this message because the laters ones all are either
> mine or another thread within this topic...
> Olivier,
>   I left my system logged in, and several journal entries occured
> while I slept.  Then today there are lots of messages about
> evolution. And after being on the system for only 20 minutes, I got
> logged off again.
> 
>   I captured the messages to a file (744 lines)  and have
> attached it here.
> 
> Regards,
> Les H
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Latest finding...
running gpartd, which I wanted to use to reformat an SD card for use
with a raspberry PI, drops me out to login immediately.
attached is the latest journalctl after the third attempt.
I clicked on gpartd at 17:36:14, and ended up logging back in at
17:37:01

I don't know if this helps, but gpartd seems to fire the issue every
time.

Regards,
Les HFeb 01 02:19:43 school gsd-housekeepin[2069]: Failed to enumerate children of 
/var/tmp/systemd-private-06b6f83
Feb 01 02:19:43 school gsd-housekeepin[2069]: Failed to enumerate children of 
/var/tmp/systemd-private-06b6f83
Feb 01 02:19:43 school gsd-housekeepin[2069]: Failed to enumerate children of 
/var/tmp/systemd-private-06b6f83
Feb 01 02:19:43 school gsd-housekeepin[2069]: Failed to enumerate children of 
/tmp/systemd-private-06b6f836b50
Feb 01 02:19:43 school gsd-housekeepin[2069]: Failed to enumerate children of 
/var/tmp/systemd-private-06b6f83
Feb 01 02:19:43 school gsd-housekeepin[2069]: Failed to enumerate children of 
/tmp/systemd-private-06b6f836b50
Feb 01 02:19:43 school gsd-housekeepin[2069]: Failed to enumerate children of 
/tmp/systemd-private-06b6f836b50
Feb 01 02:19:43 school gsd-housekeepin[2069]: Failed to enumerate children of 
/tmp/systemd-private-06b6f836b50
Feb 01 03:19:43 school gsd-housekeepin[2069]: Failed to enumerate children of 
/tmp/systemd-private-06b6f836b50
Feb 01 03:19:43 school gsd-housekeepin[2069]: Failed to enumerate children of 
/tmp/systemd-private-06b6f836b50
Feb 01 03:19:43 school gsd-housekeepin[2069]: Failed to enumerate children of 
/tmp/systemd-private-06b6f836b50
Feb 01 03:19:43 school gsd-housekeepin[2069]: Failed to enumerate children of 
/tmp/systemd-private-06b6f836b50
Feb 01 03:19:43 school gsd-housekeepin[2069]: Failed to enumerate children of 
/var/tmp/systemd-private-06b6f83
Feb 01 03:19:43 school gsd-housekeepin[2069]: Failed to enumerate children of 
/var/tmp/systemd-private-06b6f83
Feb 01 03:19:43 school gsd-housekeepin[2069]: Failed to enumerate children of 
/var/tmp/systemd-private-06b6f83
Feb 01 03:19:43 school gsd-housekeepin[2069]: Failed to enumerate children of 
/var/tmp/systemd-private-06b6f83
Feb 01 04:19:43 school gsd-housekeepin[2069]: Failed to enumerate children of 
/var/tmp/systemd-private-06b6f83
Feb 01 04:19:43 school gsd-housekeepin[2069]: Failed to enumerate children of 
/var/tmp/systemd-private-06b6f83
Feb 01 04:19:43 school gsd-housekeepin[2069]: Failed to enumerate children of 
/var/tmp/systemd-private-06b6f83
Feb 01 04:19:43 school gsd-housekeepin[2069]: Failed to enumerate children of 
/var/tmp/systemd-private-06b6f83
Feb 01 04:19:43 school gsd-housekeepin[2069]: Failed to enumerate children of 
/tmp/sys

Re: Wyland is a disaster

2018-02-03 Thread Samuel Sieb

On 02/03/2018 05:58 PM, Howard Howell wrote:

Latest finding...
running gpartd, which I wanted to use to reformat an SD card for use 
with a raspberry PI, drops me out to login immediately.

attached is the latest journalctl after the third attempt.
I clicked on gpartd at 17:36:14, and ended up logging back in at 17:37:01

I don't know if this helps, but gpartd seems to fire the issue every time.


Did you try switching the cursor theme back to the default to see if 
that makes a difference?  Also, be aware that there's an issue with the 
Places menu extension that gets triggered in various ways which might be 
relevant here.


https://bugzilla.redhat.com/show_bug.cgi?id=1538493
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org


Re: gnome crashes after today upgrade

2018-02-03 Thread Samuel Sieb

On 02/02/2018 12:55 PM, Chris Murphy wrote:

Yeah I'm getting a bunch of clutter messages as well as many lines of
gnome shell desktop related stack traces. But there is nothing listed
by coredumpctl, or abrt.


Feb 02 13:51:31 f27h.localdomain org.gnome.Shell.desktop[1612]: ==
Stack trace for context 0x557b7ae9d000 ==


The gnome shell related stack traces have been going for a while. 
They're really annoying, but not fatal.  However, there is an issue with 
the Places menu extension that cause gnome shell to crash when a USB 
device is plugged in and also other situations.


https://bugzilla.redhat.com/show_bug.cgi?id=1538493
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org