On 8/19/19 4:54 AM, Gianluca Cecchi wrote:
If you point me on how to get related log lines in journal in both
working and not working configurations, I can get more info.
Seen on several threads that with Xwayland and gnome-shell not so easy
to see startup log files...
Shouldn't make any diffe
Stefan Schulze Frielinghaus wrote:
> On Mon, Aug 19, 2019 at 12:47:20PM -0400, Todd Zullinger wrote:
>> If you enable the '-source' repositories, you'll be able to
>> do this with `dnf repoquery`. Something like this, I
>> believe:
>>
>> dnf repoquery --disablerepo '*' --enablerepo '*-source'
On Mon, Aug 19, 2019 at 12:47:20PM -0400, Todd Zullinger wrote:
> Hi,
>
> Stefan Schulze Frielinghaus wrote:
> > How can I list all packages which have a *build* requirement on package
> > foo? AFAIK build requirements are not stored as meta data in RPM files.
> > Thus, repoquery won't help. The o
On Mon, 2019-08-19 at 20:12 +0800, Ed Greshko wrote:
> On 8/19/19 6:54 PM, Patrick O'Callaghan wrote:
> > Did that and the problem has magically disappeared. No AVCs were
> > reported, though I did relabel after turning SElinux back on.
> >
> > Curiously, I now see:
> >
> > $ virsh net-list --all
Hi,
Stefan Schulze Frielinghaus wrote:
> How can I list all packages which have a *build* requirement on package
> foo? AFAIK build requirements are not stored as meta data in RPM files.
> Thus, repoquery won't help. The only option I am aware of would be to
> download all SPEC files and search fo
Hi all,
How can I list all packages which have a *build* requirement on package
foo? AFAIK build requirements are not stored as meta data in RPM files.
Thus, repoquery won't help. The only option I am aware of would be to
download all SPEC files and search for build requirements manually. Any
othe
On 8/19/19 6:54 PM, Patrick O'Callaghan wrote:
> Did that and the problem has magically disappeared. No AVCs were
> reported, though I did relabel after turning SElinux back on.
>
> Curiously, I now see:
>
> $ virsh net-list --all
> Name State Autostart Persistent
> --
Hello,
executed "dnf update" after about 15 days of inactivity.
Updates has brought in kernel 5.2.8-200.fc30.x86_64
But after reboot the system is not able to detect (in the sense of no
monitor connection at all seen) when connecting a 24" Dell monitor using an
usb-c to hdmi adapter on my laptop an
On Sun, 2019-08-18 at 10:30 +0800, Ed Greshko wrote:
> On 8/18/19 1:23 AM, Patrick O'Callaghan wrote:
> > The above only happens when SElinux is Enabled. When Disabled,
> > everything works. The same happens on both my VMs (Fedora and Windows).
> >
> > Looking at https://wiki.libvirt.org/page/Netw
On 8/18/19 2:36 AM, Michael D. Setzer II via users wrote:
On 8/17/19 5:38 PM, Michael D. Setzer II via users wrote:
I use syslinux in the g4l project I've maintained since 2004, and
noticed that
Fedora 30 includes the later 6.04 version versus the latest full
released 6.03
version. Did a test, a
10 matches
Mail list logo
