Re: [gentoo-user] Re: replacement for ftp?

On Tue, 16 May 2017 04:58:44 +0200 Kai Krakow wrote: > If this is the underlying (and perfectly legitimate) problem, you need > to deploy a solution that's most easy for your users and not for you. > That may involve a custom transfer solution where they simply can drop >

[gentoo-user] Re: Wow, the GTK3 file browser is awful!

On 2017-05-22, Mick wrote: > On Monday 22 May 2017 18:33:47 Grant Edwards wrote: >> Having just recently allowed Firefox to upgrade from 45 to 52, I'm now >> hobbled with the GTK3 file browser dialog. >> >> It's horrible. >> >> First of all, it's freaking _huge_! It

Re: [gentoo-user] Wow, the GTK3 file browser is awful!

On Monday 22 May 2017 18:33:47 Grant Edwards wrote: > Having just recently allowed Firefox to upgrade from 45 to 52, I'm now > hobbled with the GTK3 file browser dialog. > > It's horrible. > > First of all, it's freaking _huge_! It wastes acres of display > real-estate. It was obviously

Re: [gentoo-user] Wow, the GTK3 file browser is awful!

On Mon, 22 May 2017 18:33:47 + (UTC) Grant Edwards wrote: > Having just recently allowed Firefox to upgrade from 45 to 52, I'm now > hobbled with the GTK3 file browser dialog. > > It's horrible. Indeed :/. You're not alone, but what can we do about it? Its not

[gentoo-user] Wow, the GTK3 file browser is awful!

Having just recently allowed Firefox to upgrade from 45 to 52, I'm now hobbled with the GTK3 file browser dialog. It's horrible. First of all, it's freaking _huge_! It wastes acres of display real-estate. It was obviously designed by a megalomaniac who thinks your computer belongs to him, and

[gentoo-user] Re: Qt-4.8.7 bug

Hello Kai, Kai Krakow wrote: > Am Mon, 22 May 2017 19:33:55 +0200 > schrieb Jörg Schaible : > >> Peter Humphrey wrote: [snip] >> > >> > I can only suggest you read bug report 618922 if you haven't >> > already, including following its reference to bug 595618. It makes

[gentoo-user] Re: Qt-4.8.7 bug

Am Mon, 22 May 2017 19:33:55 +0200 schrieb Jörg Schaible : > Peter Humphrey wrote: > > > On Monday 22 May 2017 09:49:01 Jörg Schaible wrote: > >> Hi Peter, > >> > >> Peter Humphrey wrote: > >> > >> [snip] > >> > [...] > >> > >> well, this does not seem to be the

[gentoo-user] Re: Re: Re: Qt-4.8.7 bug

Peter Humphrey wrote: > On Monday 22 May 2017 09:49:01 Jörg Schaible wrote: >> Hi Peter, >> >> Peter Humphrey wrote: >> >> [snip] >> >> > Have you seen https://bugs.gentoo.org/show_bug.cgi?id=595618 ? It says >> > that "Qt plugins compiled with gcc-4 are incompatible with >> > > > be >> >

Re: [gentoo-user] Re: Issues with AMD_IOMMU

Here's the grub command line I was using on my Phenom II on a 990FX board, I had only commented it out after upgrading to Ryzen #GRUB_CMDLINE_LINUX="check_enable_amd_mmconf amd_iommu=fullflush iommu=soft" -- Strange Game. The only winning move is not to play. Powers are not rights.

Re: [gentoo-user] gdm fails to start

Hello, Very simple question but did you have "pam" in your global USE flag or Systemd USE flag ? If this is on the first, did you compile systemd and may be dependencies after add it ? Did you try that: |systemctl reset-failed| |For a guy on github, that solve (without explanation) the

Re: [gentoo-user] Re: Issues with AMD_IOMMU

On 05/21/2017 06:12 PM, Adam Carter wrote: > > > > [0.991863] iommu: Adding device :06:00.0 to group 12 > > [0.991982] iommu: Adding device :07:04.0 to group 12 > > [1.063849] AMD-Vi: Found IOMMU at :00:00.2 cap 0x40 > > [1.063962] AMD-Vi: Interrupt

Re: [gentoo-user] gdm fails to start

On Mon, 2017-05-22 at 13:02 +0300, Alexander Kapshuk wrote: > On Mon, May 22, 2017 at 1:00 PM, Raffaele Belardi > wrote: > > On Mon, 2017-05-22 at 12:47 +0300, Alexander Kapshuk wrote: > > > > > > A Google search found this systemd issue: > > >

Re: [gentoo-user] Re: Re: Qt-4.8.7 bug

On Monday 22 May 2017 09:49:01 Jörg Schaible wrote: > Hi Peter, > > Peter Humphrey wrote: > > [snip] > > > Have you seen https://bugs.gentoo.org/show_bug.cgi?id=595618 ? It says > > that "Qt plugins compiled with gcc-4 are incompatible with > > > be > > expected to anticipate that. On the

Re: [gentoo-user] gdm fails to start

On Mon, May 22, 2017 at 1:00 PM, Raffaele Belardi wrote: > On Mon, 2017-05-22 at 12:47 +0300, Alexander Kapshuk wrote: >> >> A Google search found this systemd issue: >> https://github.com/systemd/systemd/issues/4342 >> Quote: >> @poettering I see I left no account

Re: [gentoo-user] gdm fails to start

On Mon, 2017-05-22 at 12:47 +0300, Alexander Kapshuk wrote: > > A Google search found this systemd issue: > https://github.com/systemd/systemd/issues/4342 > Quote: > @poettering I see I left no account modules in the bare-bones PAM > config. Maybe it is pam_acct_mgmt failing then? > > @yuwata

Re: [gentoo-user] gdm fails to start

On Mon, May 22, 2017 at 11:16 AM, Raffaele Belardi wrote: > I'm unable to start the gdm service on a recently installed gnome > desktop (~x86): the service continuously fails and restarts with the > errors below. If I disable the service and login into a text console, >

Re: [gentoo-user] Re: Issues with AMD_IOMMU

On Mon, May 22, 2017 at 7:15 PM, taii...@gmx.com wrote: > Worse, ideally you wouldn't be using SWIOTLB but I don't know how to > disable this without re-compiling the kernel. > Can you point to some definitive documentation on this? When i read

Re: [gentoo-user] Re: Issues with AMD_IOMMU

Worse, ideally you wouldn't be using SWIOTLB but I don't know how to disable this without re-compiling the kernel. On 05/21/2017 07:12 PM, Adam Carter wrote: [0.991863] iommu: Adding device :06:00.0 to group 12 [0.991982] iommu: Adding device :07:04.0 to group 12 [

[gentoo-user] gdm fails to start

I'm unable to start the gdm service on a recently installed gnome desktop (~x86): the service continuously fails and restarts with the errors below. If I disable the service and login into a text console, startx works fine but the Gnome session misses some features (e.g. screen lock). I enabled

[gentoo-user] Re: Re: Qt-4.8.7 bug

Hi Peter, Peter Humphrey wrote: [snip] > Have you seen https://bugs.gentoo.org/show_bug.cgi?id=595618 ? It says > that "Qt plugins compiled with gcc-4 are incompatible with > expected to anticipate that. On the other hand, some kind of notice could > be issued, and bug 618922 is pursuing that.