Re: OT: bash parameter substitutions
On 11/4/18 10:00 PM, Mike Wright wrote: There is such a thing as too terse. Can somebody explain what this cryptic snippet means? I get the "substitute part; it's the "error,exit" part that has me confounded. My assumption is that it will print an error and abort the script. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: hibernate stops working after upgrade to F29 from F28
On 11/4/18 7:09 PM, Ranjan Maitra wrote:
On Sun, 4 Nov 2018 18:46:28 -0800 Samuel Sieb wrote:
On 11/4/18 5:21 PM, Ranjan Maitra wrote:
Nov 04 19:12:41 machine.name kernel: audit: type=1400 audit(1541380361.892:226): avc: denied { read } for
pid=805 comm="systemd-logind" name="nvme0n1p1" dev="devtmpfs" ino=17833
scontext=system_u:system_r:systemd_logind_t:s0 tcontext=system_u:object_r:nvme_device_t:s0 tclass=blk_file
permissive=0
There are a couple of these and it appears that it is the disk device
that it is trying to open. Run "ls -li /dev/nvme0n1*" to verify that.
17666 brw-rw. 1 root disk 259, 0 Nov 4 19:43 /dev/nvme0n1
17667 brw-rw. 1 root disk 259, 1 Nov 4 19:43 /dev/nvme0n1p1
17668 brw-rw. 1 root disk 259, 2 Nov 4 19:43 /dev/nvme0n1p2
17669 brw-rw. 1 root disk 259, 3 Nov 4 19:44 /dev/nvme0n1p3
17670 brw-rw. 1 root disk 259, 4 Nov 4 19:43 /dev/nvme0n1p4
17671 brw-rw. 1 root disk 259, 5 Nov 4 19:43 /dev/nvme0n1p5
17672 brw-rw. 1 root disk 259, 6 Nov 4 19:43 /dev/nvme0n1p6
The numbers don't match, but I just realized why. The inode numbers on
a tmpfs are temporary. I would need to see the log line and the inode
numbers from the same boot. I'm now wondering if it's an selinux issue.
Try running "sudo setenforce off" and then try "systemctl hibernate".
See if that works.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Xfce 4.13 took it on the chin in FC29
On 11/3/18 11:33 AM, ToddAndMargo via users wrote: Hi All, Four machines upgraded to Fedora 29, two to go. The last two are servers, so they are going to wait a bit. :-) Xfce 4.13 sure took it on the chin. I just open up launcher panels no longer scale https://bugzilla.xfce.org/show_bug.cgi?id=14828 xfce4-about 4.13 thinks it is 4.12 https://bugzilla.xfce.org/show_bug.cgi?id=14827 xfce4-about 4.13 is missing from settings https://bugzilla.xfce.org/show_bug.cgi?id=14829 panel icon size ignored on pop up https://bugzilla.xfce.org/show_bug.cgi?id=14830 mailing list is down https://bugzilla.xfce.org/show_bug.cgi?id=14831 And one more: black background on panel icons https://bugzilla.xfce.org/show_bug.cgi?id=14842 ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
OT: bash parameter substitutions
Hi bash fans,
There is such a thing as too terse. Can somebody explain what this
cryptic snippet means? I get the "substitute part; it's the
"error,exit" part that has me confounded.
+--++---+--+
| | parameter | parameter | parameter|
| | Set and Not Null | Set But Null | Unset|
+--++---+--+
|${parameter:?word}|substitute parameter|error,exit |error,exit|
|${parameter?word} |substitute parameter|substitute null|error,exit|
+--++---+--+
TIA,
Mike Wright
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: hibernate stops working after upgrade to F29 from F28
On Sun, 4 Nov 2018 18:46:28 -0800 Samuel Sieb wrote:
> On 11/4/18 5:21 PM, Ranjan Maitra wrote:
> > Nov 04 19:12:41 machine.name systemd-logind[805]: Enough swap for
> > hibernation, Active(anon)=234032 kB, size=20967420 kB, used=0 kB,
> > threshold=98%
>
> Your swap is fine.
>
> > Nov 04 19:12:41 machine.name audit[805]: AVC avc: denied { read } for
> > pid=805 comm="systemd-logind" name="nvme0n1p1" dev="devtmpfs" ino=17833
> > scontext=system_u:system_r:systemd_logind_t:s0
> > tcontext=system_u:object_r:nvme_device_t:s0 tclass=blk_file permissive=0
> > Nov 04 19:12:41 machine.name audit[805]: SYSCALL arch=c03e syscall=257
> > success=no exit=-13 a0=ff9c a1=7fffb9486130 a2=8 a3=0 items=0
> > ppid=1 pid=805 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0
> > sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="systemd-logind"
> > exe="/usr/lib/systemd/systemd-logind"
> > subj=system_u:system_r:systemd_logind_t:s0 key=(null)
> > Nov 04 19:12:41 machine.name audit: PROCTITLE
> > proctitle="/usr/lib/systemd/systemd-logind"
> > Nov 04 19:12:41 machine.name systemd-logind[805]: Failed to open file
> > system "/boot/efi": Permission denied
> > Nov 04 19:12:41 machine.name systemd-logind[805]: Cannot read boot
> > configuration from ESP, assuming hibernation is not possible.
>
> This is clearly the problem. I don't have any idea why it can't open
> the file system. And from the code, my understanding is that it should
> fall back to reading /proc/cmdline anyway.
I see. I filed earlier this morning on bugzilla as well as on github. But no
one has asked for any information yet. I guess that I should add this info in
case someone looks into.
The important thing to note is that it worked in F28 (with systemd 238-9) and
not in F29 (with systemd 239-6). And it was not a fresh install but an upgrade
to F29 from F28.
> > Nov 04 19:12:41 machine.name kernel: audit: type=1400
> > audit(1541380361.892:226): avc: denied { read } for pid=805
> > comm="systemd-logind" name="nvme0n1p1" dev="devtmpfs" ino=17833
> > scontext=system_u:system_r:systemd_logind_t:s0
> > tcontext=system_u:object_r:nvme_device_t:s0 tclass=blk_file permissive=0
> > Nov 04 19:12:41 machine.name kernel: audit: type=1300
> > audit(1541380361.892:226): arch=c03e syscall=257 success=no exit=-13
> > a0=ff9c a1=7fffb9486130 a2=8 a3=0 items=0 ppid=1 pid=805
> > auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0
> > tty=(none) ses=4294967295 comm="systemd-logind"
> > exe="/usr/lib/systemd/systemd-logind"
> > subj=system_u:system_r:systemd_logind_t:s0 key=(null)
>
> There are a couple of these and it appears that it is the disk device
> that it is trying to open. Run "ls -li /dev/nvme0n1*" to verify that.
17666 brw-rw. 1 root disk 259, 0 Nov 4 19:43 /dev/nvme0n1
17667 brw-rw. 1 root disk 259, 1 Nov 4 19:43 /dev/nvme0n1p1
17668 brw-rw. 1 root disk 259, 2 Nov 4 19:43 /dev/nvme0n1p2
17669 brw-rw. 1 root disk 259, 3 Nov 4 19:44 /dev/nvme0n1p3
17670 brw-rw. 1 root disk 259, 4 Nov 4 19:43 /dev/nvme0n1p4
17671 brw-rw. 1 root disk 259, 5 Nov 4 19:43 /dev/nvme0n1p5
17672 brw-rw. 1 root disk 259, 6 Nov 4 19:43 /dev/nvme0n1p6
>
> > Sorry, it works, and flawlessly. I am wondering if I should just upgrade
> > the source rpm and then forget about this mess of systemd.
>
> You don't need to update it. It works fine as it is and it won't go away.
The only irritating thing is that it requires a password. And can not be mapped
to a button, therefore: I am an openbox user.
> > I see. I am using a text console.
>
> Oh, that's surprising.
Thanks again!
Ranjan
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: hibernate stops working after upgrade to F29 from F28
On 11/4/18 5:21 PM, Ranjan Maitra wrote:
Nov 04 19:12:41 machine.name systemd-logind[805]: Enough swap for hibernation,
Active(anon)=234032 kB, size=20967420 kB, used=0 kB, threshold=98%
Your swap is fine.
Nov 04 19:12:41 machine.name audit[805]: AVC avc: denied { read } for pid=805
comm="systemd-logind" name="nvme0n1p1" dev="devtmpfs" ino=17833
scontext=system_u:system_r:systemd_logind_t:s0 tcontext=system_u:object_r:nvme_device_t:s0 tclass=blk_file
permissive=0
Nov 04 19:12:41 machine.name audit[805]: SYSCALL arch=c03e syscall=257 success=no exit=-13
a0=ff9c a1=7fffb9486130 a2=8 a3=0 items=0 ppid=1 pid=805 auid=4294967295 uid=0 gid=0 euid=0
suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="systemd-logind"
exe="/usr/lib/systemd/systemd-logind" subj=system_u:system_r:systemd_logind_t:s0
key=(null)
Nov 04 19:12:41 machine.name audit: PROCTITLE
proctitle="/usr/lib/systemd/systemd-logind"
Nov 04 19:12:41 machine.name systemd-logind[805]: Failed to open file system
"/boot/efi": Permission denied
Nov 04 19:12:41 machine.name systemd-logind[805]: Cannot read boot
configuration from ESP, assuming hibernation is not possible.
This is clearly the problem. I don't have any idea why it can't open
the file system. And from the code, my understanding is that it should
fall back to reading /proc/cmdline anyway.
Nov 04 19:12:41 machine.name kernel: audit: type=1400 audit(1541380361.892:226): avc: denied { read } for
pid=805 comm="systemd-logind" name="nvme0n1p1" dev="devtmpfs" ino=17833
scontext=system_u:system_r:systemd_logind_t:s0 tcontext=system_u:object_r:nvme_device_t:s0 tclass=blk_file
permissive=0
Nov 04 19:12:41 machine.name kernel: audit: type=1300 audit(1541380361.892:226): arch=c03e
syscall=257 success=no exit=-13 a0=ff9c a1=7fffb9486130 a2=8 a3=0 items=0 ppid=1 pid=805
auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295
comm="systemd-logind" exe="/usr/lib/systemd/systemd-logind"
subj=system_u:system_r:systemd_logind_t:s0 key=(null)
There are a couple of these and it appears that it is the disk device
that it is trying to open. Run "ls -li /dev/nvme0n1*" to verify that.
Sorry, it works, and flawlessly. I am wondering if I should just upgrade the
source rpm and then forget about this mess of systemd.
You don't need to update it. It works fine as it is and it won't go away.
I see. I am using a text console.
Oh, that's surprising.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Clean Install of F29 problems
On 11/4/18 7:18 AM, stan wrote: On Sun, 04 Nov 2018 14:29:08 + ja wrote: warning: %post(tex-fonts-hebrew-0.1-28.fc29.noarch) scriptlet failed, exit status 255 Error in POSTIN scriptlet in rpm package tex-fonts-hebrew Installed: tex-fonts-hebrew-0.1-28.fc29.noarch This is strange, since it is the same package as f28, just rebuilt in the f29 environment. You could try installing the f28 package from here https://koji.fedoraproject.org/koji/buildinfo?buildID=1042001 to see if it has the same issue. It's a known issue. Fixes should be in testing now. https://bugzilla.redhat.com/show_bug.cgi?id=1555931 ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: hibernate stops working after upgrade to F29 from F28
Hi Sam,
Thanks very much again!
On Sun, 4 Nov 2018 16:52:13 -0800 Samuel Sieb wrote:
> On 11/4/18 3:08 PM, Ranjan Maitra wrote:
> > On Sun, 4 Nov 2018 13:25:47 -0800 Samuel Sieb wrote:
> >> These definitely seem relevant. You said it's an EFI system. Is
> >> /boot/efi mounted correctly?
> >
> > Thanks! I would guess so, given that it worked as expected with F28
> > (systemd 238-9).
> >
> > df -h
> > /dev/nvme0n1p1 vfat 952M 18M 934M 2% /boot/efi
>
> The error opening /boot/efi is curious. Can you follow the instructions
> in
> https://lists.freedesktop.org/archives/systemd-devel/2013-March/010004.html
> to enable debug logging for logind (the second part written by Lennart,
> not the quoted part). Reboot after those changes and try my
> instructions again with running journalctl before trying to hibernate.
Here is the output:
Nov 04 19:12:41 machine.name systemd-logind[805]: Got message type=method_call
sender=:1.129 destination=org.freedesktop.login1 path=/org/freedesktop/login1
interface=org.freedesktop.login1.Manager member=ListInhibitors cookie=2
reply_cookie=0 signature=n/a error-name=n/a error-message=n/a
Nov 04 19:12:41 machine.name systemd-logind[805]: Sent message
type=method_return sender=n/a destination=:1.129 path=n/a interface=n/a
member=n/a cookie=40 reply_cookie=2 signature=a(uu) error-name=n/a
error-message=n/a
Nov 04 19:12:41 machine.name polkitd[776]: Registered Authentication Agent for
unix-process:1606:17251 (system bus name :1.130 [/usr/bin/pkttyagent
--notify-fd 5 --fallback], object path
/org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
Nov 04 19:12:41 machine.name systemd-logind[805]: Got message type=method_call
sender=:1.129 destination=org.freedesktop.login1 path=/org/freedesktop/login1
interface=org.freedesktop.login1.Manager member=SetWallMessage cookie=3
reply_cookie=0 signature=sb error-name=n/a error-message=n/a
Nov 04 19:12:41 machine.name systemd-logind[805]: Sent message type=method_call
sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus
interface=org.freedesktop.DBus member=GetConnectionUnixUser cookie=41
reply_cookie=0 signature=s error-name=n/a error-message=n/a
Nov 04 19:12:41 machine.name systemd-logind[805]: Got message
type=method_return sender=org.freedesktop.DBus destination=:1.14 path=n/a
interface=n/a member=n/a cookie=20 reply_cookie=41 signature=u error-name=n/a
error-message=n/a
Nov 04 19:12:41 machine.name systemd-logind[805]: Sent message type=method_call
sender=n/a destination=org.freedesktop.PolicyKit1
path=/org/freedesktop/PolicyKit1/Authority
interface=org.freedesktop.PolicyKit1.Authority member=CheckAuthorization
cookie=42 reply_cookie=0 signature=(sa{sv})sa{ss}us error-name=n/a
error-message=n/a
Nov 04 19:12:41 machine.name systemd-logind[805]: Got message
type=method_return sender=:1.10 destination=:1.14 path=n/a interface=n/a
member=n/a cookie=175 reply_cookie=42 signature=(bba{ss}) error-name=n/a
error-message=n/a
Nov 04 19:12:41 machine.name systemd-logind[805]: Sent message
type=method_return sender=n/a destination=:1.129 path=n/a interface=n/a
member=n/a cookie=43 reply_cookie=3 signature=n/a error-name=n/a
error-message=n/a
Nov 04 19:12:41 machine.name systemd-logind[805]: Got message type=method_call
sender=:1.129 destination=org.freedesktop.login1 path=/org/freedesktop/login1
interface=org.freedesktop.login1.Manager member=Hibernate cookie=4
reply_cookie=0 signature=b error-name=n/a error-message=n/a
Nov 04 19:12:41 machine.name systemd-logind[805]: Failed to open configuration
file '/etc/systemd/sleep.conf': No such file or directory
Nov 04 19:12:41 machine.name systemd-logind[805]: Enough swap for hibernation,
Active(anon)=234032 kB, size=20967420 kB, used=0 kB, threshold=98%
Nov 04 19:12:41 machine.name audit[805]: AVC avc: denied { read } for
pid=805 comm="systemd-logind" name="nvme0n1p1" dev="devtmpfs" ino=17833
scontext=system_u:system_r:systemd_logind_t:s0
tcontext=system_u:object_r:nvme_device_t:s0 tclass=blk_file permissive=0
Nov 04 19:12:41 machine.name audit[805]: SYSCALL arch=c03e syscall=257
success=no exit=-13 a0=ff9c a1=7fffb9486130 a2=8 a3=0 items=0 ppid=1
pid=805 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0
tty=(none) ses=4294967295 comm="systemd-logind"
exe="/usr/lib/systemd/systemd-logind"
subj=system_u:system_r:systemd_logind_t:s0 key=(null)
Nov 04 19:12:41 machine.name audit: PROCTITLE
proctitle="/usr/lib/systemd/systemd-logind"
Nov 04 19:12:41 machine.name systemd-logind[805]: Failed to open file system
"/boot/efi": Permission denied
Nov 04 19:12:41 machine.name systemd-logind[805]: Cannot read boot
configuration from ESP, assuming hibernation is not possible.
Nov 04 19:12:41 machine.name kernel: audit: type=1400
audit(1541380361.892:226): avc: denied { read } for pid=805
comm="systemd-logind" name="nvme0n1p1" dev="devtmpfs" ino=17833
scontext=system_u:syst
Re: Will RedHat deprecate KDE on Fedora?
Once upon a time, Tom Horsley said: > On Sun, 4 Nov 2018 15:26:51 -0500 > Digimer wrote: > > SysV Init had to be replaced, it was terrible. > > Where "terrible" is a linux developer code word for "old" :-). No, really, while SysV init was better than what came before, it was really pretty terrible at anything more complicated than starting a few independent services. Anything beyond "run this one executable" made init scripts that were non-portable and hard to follow/debug. Services that had dependencies that couldn't easily be expressed by simple lexical ordering had all kinds of cobbled bits in the init scripts that was just terrible. And it really didn't handle any kind of dynamic system, where things might come and go. Having a bunch of independent layers crammed on to handle that didn't really mesh well either. systemd-the-project that seems to have continual scope creep may not be the best (IMHO), but systemd-the-init-system is a vast improvement on what came before. "Old" isn't inherently bad, but then neither is "new". -- Chris Adams ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: gnome-control-center coredumps
On 11/4/18 10:02 AM, Patrick O'Callaghan wrote: I always assumed that the only reason for g-c-c to exist was so that users of other DEs could access Gnome settings. If it can only run under Gnome that rather defeats the purpose I would think. I'm pretty sure its primary purpose is to control the settings in Gnome. Most of the settings are not relevant if you're using a different DE. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: hibernate stops working after upgrade to F29 from F28
On 11/4/18 3:08 PM, Ranjan Maitra wrote: On Sun, 4 Nov 2018 13:25:47 -0800 Samuel Sieb wrote: These definitely seem relevant. You said it's an EFI system. Is /boot/efi mounted correctly? Thanks! I would guess so, given that it worked as expected with F28 (systemd 238-9). df -h /dev/nvme0n1p1 vfat 952M 18M 934M 2% /boot/efi The error opening /boot/efi is curious. Can you follow the instructions in https://lists.freedesktop.org/archives/systemd-devel/2013-March/010004.html to enable debug logging for logind (the second part written by Lennart, not the quoted part). Reboot after those changes and try my instructions again with running journalctl before trying to hibernate. What user are you running systemctl as? mortal user. Does it work if you do "sudo systemctl hibernate"? Did you try installing the pm-utils package I linked you to from koji? See if "pm-hibernate" works. Where are you running it? From a console or from a graphical terminal window? From a CLI terminal. What is a console? If you press CTRL-ALT-F3, you should get a text console. Pressing ALT-F2 should get you back to your graphical session. If that doesn't work, try ALT-F1 (I'm not sure if gdm always starts a new console now). ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Will RedHat deprecate KDE on Fedora?
Digimer writes: SysV Init had to be replaced, it was terrible. Canonical didn't make a viable alternative, and no other projects were out there with any real viability. So they funded the creation and development of systemd and enough people liked it that it got picked up and hit critical mass. Unfortunately, if systemd was just a sysvinit replacement, I don't think most people would mind. They never forced it on anyone. Until Gnome acquired a dependency on systemd. At that point, if you wished to ship Gnome, without hacking it, you'd have to ship systemd. pgpU2iSZyHsI3.pgp Description: PGP signature ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Will RedHat deprecate KDE on Fedora?
Patrick O'Callaghan writes: On Sun, 2018-11-04 at 07:24 -0500, Sam Varshavchik wrote: > That would only be true if Fedora incurs no expense to Red Hat. Perhaps some > minimal expense on the account of KDE will be tolerable. But I don't think > it would take a lot for KDE to leave via the same door where systemd came in. Without wishing to get into yet another discussion about the merits or otherwise of systemd, I'd just point out that it's now used by every major Linux distro. Those that don't can be found here: $ rpm -q --requires gnome-session | grep systemd libsystemd.so.0()(64bit) libsystemd.so.0(LIBSYSTEMD_209)(64bit) systemd is being forced onto the Linux distributions mostly because Gnome requires it. pgp0r91O89wS1.pgp Description: PGP signature ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: hibernate stops working after upgrade to F29 from F28
On Sun, 4 Nov 2018 13:25:47 -0800 Samuel Sieb wrote:
> On 11/4/18 5:25 AM, Ranjan Maitra wrote:
> > On Sat, 3 Nov 2018 22:34:00 -0700 Samuel Sieb wrote:
> >
> >> On 11/3/18 9:48 PM, Ranjan Maitra wrote:
> >>> On Sat, 3 Nov 2018 21:39:41 -0700 Samuel Sieb wrote:
> That is a likely cause. Are there any other lines from logind in the
> journal? What is in /proc/cmdline?
> >>>
> >>> I don't know hoe to look in the journal. With regard to /proc/cmdline:
> >>
> >> In one terminal window, run "sudo journalctl -fa". In another one, try
> >> to hibernate. See what lines get printed in the first terminal.
> >
> > Nov 04 07:19:29 machine.name audit[827]: AVC avc: denied { read } for
> > pid=827 comm="systemd-logind" name="nvme0n1p1" dev="devtmpfs" ino=17625
> > scontext=system_u:system_r:systemd_logind_t:s0
> > tcontext=system_u:object_r:nvme_device_t:s0 tclass=blk_file permissive=0
> > Nov 04 07:19:29 machine.name audit[827]: SYSCALL arch=c03e syscall=257
> > success=no exit=-13 a0=ff9c a1=7ffe3533e050 a2=8 a3=0 items=0
> > ppid=1 pid=827 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0
> > sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="systemd-logind"
> > exe="/usr/lib/systemd/systemd-logind"
> > subj=system_u:system_r:systemd_logind_t:s0 key=(null)
> > Nov 04 07:19:29 machine.name audit: PROCTITLE
> > proctitle="/usr/lib/systemd/systemd-logind"
> > Nov 04 07:19:29 machine.name systemd-logind[827]: Failed to open file
> > system "/boot/efi": Permission denied
> > Nov 04 07:19:29 machine.name kernel: audit: type=1400
> > audit(1541337569.994:258): avc: denied { read } for pid=827
> > comm="systemd-logind" name="nvme0n1p1" dev="devtmpfs" ino=17625
> > scontext=system_u:system_r:systemd_logind_t:s0
> > tcontext=system_u:object_r:nvme_device_t:s0 tclass=blk_file permissive=0
> > Nov 04 07:19:29 machine.name kernel: audit: type=1300
> > audit(1541337569.994:258): arch=c03e syscall=257 success=no exit=-13
> > a0=ff9c a1=7ffe3533e050 a2=8 a3=0 items=0 ppid=1 pid=827
> > auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0
> > tty=(none) ses=4294967295 comm="systemd-logind"
> > exe="/usr/lib/systemd/systemd-logind"
> > subj=system_u:system_r:systemd_logind_t:s0 key=(null)
>
> These definitely seem relevant. You said it's an EFI system. Is
> /boot/efi mounted correctly?
Thanks! I would guess so, given that it worked as expected with F28 (systemd
238-9).
df -h
/dev/nvme0n1p1 vfat 952M 18M 934M 2% /boot/efi
> What user are you running systemctl as?
mortal user.
> Where are you running it? From a console or from a graphical terminal
> window?
From a CLI terminal. What is a console?
Many thanks,
Ranjan
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
--
Important Notice: This mailbox is ignored: e-mails are set to be deleted on
receipt. Please respond to the mailing list if appropriate. For those needing
to send personal or professional e-mail, please use appropriate addresses.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Why this activity on mounted but unused fs?
On 4/11/18 4:19 pm, Eyal Lebedinsky wrote: While configuring a new raid I ran iostat to see that it is idle. It was, and there was no io showing at all. I then mounted it on a new mount point which I have no process using. I started hearing knocks from the PC case, and touching the disks revealed that they all had activity 1-2 times a second, concurrently, leading to the louder than usual noise. Here is what "iostat 60" is now showing on a totally idle system (this is a very typical entry): avg-cpu: %user %nice %system %iowait %steal %idle 0.21 0.00 0.19 1.36 0.00 98.24 Device tps kB_read/s kB_wrtn/s kB_read kB_wrtn sda 0.73 0.93 4.07 56 244 sdb 5.87 8.53 20.78 512 1247 sdd 6.67 10.93 23.18 656 1391 sdf 8.50 40.27 52.52 2416 3151 sde 6.20 4.40 16.65 264 999 sdh 5.97 10.13 22.38 608 1343 sdg 7.77 38.00 50.25 2280 3015 sdc 5.87 8.53 20.78 512 1247 md127 1.80 0.00 40.27 0 2416 sda is the root fs (ext4). md127 (ext4) is a RAID6 of 7 disks sd[b-h]1. What is this io, and can it be stopped? I want to allow the disks to enter low power mode (not spin down) when idle. This is up-to-date recent install of f28 (this is a test system, so not customized). TIA A summary of what I learnt so far: I was pointed at the lazy init feature of ext4 as the culprit (read the thread). I was not aware of this feature so there is a silver lining to this cloudy issue. After some searching I now see in mkfs.ext4 man page these two options lazy_itable_init, lazy_journal_init Furthermore, I read about it here https://ext4.wiki.kernel.org/index.php/Ext4_Disk_Layout#Lazy_Block_Group_Initialization One can see the activity using iotop: $ iotop -oP Total DISK READ : 0.00 B/s | Total DISK WRITE : 0.00 B/s Actual DISK READ: 0.00 B/s | Actual DISK WRITE: 103.76 K/s PID PRIO USER DISK READ DISK WRITE SWAPIN IO>COMMAND 1872 be/3 root0.00 B/s0.00 B/s 0.00 % 3.50 % [jbd2/md127-8] 1874 be/4 root0.00 B/s0.00 B/s 0.00 % 1.11 % [ext4lazyinit] However it seems that there is no way to see how far the lazy init progressed or how much data needs to be written. My other observation is that the RAID6 write amplification probably has a large effect if the init process is writing non sequential single blocks. HTH -- Eyal at Home (fed...@eyal.emu.id.au) ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Will RedHat deprecate KDE on Fedora?
On 2018-11-04 4:33 p.m., Tom Horsley wrote: > On Sun, 4 Nov 2018 15:26:51 -0500 > Digimer wrote: > >> SysV Init had to be replaced, it was terrible. > > Where "terrible" is a linux developer code word for "old" :-). I'm still running our production clusters on cman + rgmanager, an old and deprecated cluster stack. I'm doing it on purpose because old is stable. I have no problem at all with "old" as a general concept. As just one example, try setting up sysvinit with proper shutdown ordering. As another, try having complex start up requirements. You'll need basically a program, not a script. No, sysvinit was seriously limited and cludgey. I'm still struggling to adapt to systemd, it's been a painful process, but the more I learn, the more I understand why a replacement was long over due. -- Digimer Papers and Projects: https://alteeve.com/w/ "I am, somehow, less interested in the weight and convolutions of Einstein’s brain than in the near certainty that people of equal talent have lived and died in cotton fields and sweatshops." - Stephen Jay Gould ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Will RedHat deprecate KDE on Fedora?
On Sun, 4 Nov 2018 15:26:51 -0500 Digimer wrote: > SysV Init had to be replaced, it was terrible. Where "terrible" is a linux developer code word for "old" :-). ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: hibernate stops working after upgrade to F29 from F28
On 11/4/18 5:25 AM, Ranjan Maitra wrote:
On Sat, 3 Nov 2018 22:34:00 -0700 Samuel Sieb wrote:
On 11/3/18 9:48 PM, Ranjan Maitra wrote:
On Sat, 3 Nov 2018 21:39:41 -0700 Samuel Sieb wrote:
That is a likely cause. Are there any other lines from logind in the
journal? What is in /proc/cmdline?
I don't know hoe to look in the journal. With regard to /proc/cmdline:
In one terminal window, run "sudo journalctl -fa". In another one, try
to hibernate. See what lines get printed in the first terminal.
Nov 04 07:19:29 machine.name audit[827]: AVC avc: denied { read } for pid=827
comm="systemd-logind" name="nvme0n1p1" dev="devtmpfs" ino=17625
scontext=system_u:system_r:systemd_logind_t:s0 tcontext=system_u:object_r:nvme_device_t:s0 tclass=blk_file
permissive=0
Nov 04 07:19:29 machine.name audit[827]: SYSCALL arch=c03e syscall=257 success=no exit=-13
a0=ff9c a1=7ffe3533e050 a2=8 a3=0 items=0 ppid=1 pid=827 auid=4294967295 uid=0 gid=0 euid=0
suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="systemd-logind"
exe="/usr/lib/systemd/systemd-logind" subj=system_u:system_r:systemd_logind_t:s0
key=(null)
Nov 04 07:19:29 machine.name audit: PROCTITLE
proctitle="/usr/lib/systemd/systemd-logind"
Nov 04 07:19:29 machine.name systemd-logind[827]: Failed to open file system
"/boot/efi": Permission denied
Nov 04 07:19:29 machine.name kernel: audit: type=1400 audit(1541337569.994:258): avc: denied { read } for
pid=827 comm="systemd-logind" name="nvme0n1p1" dev="devtmpfs" ino=17625
scontext=system_u:system_r:systemd_logind_t:s0 tcontext=system_u:object_r:nvme_device_t:s0 tclass=blk_file
permissive=0
Nov 04 07:19:29 machine.name kernel: audit: type=1300 audit(1541337569.994:258): arch=c03e
syscall=257 success=no exit=-13 a0=ff9c a1=7ffe3533e050 a2=8 a3=0 items=0 ppid=1 pid=827
auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295
comm="systemd-logind" exe="/usr/lib/systemd/systemd-logind"
subj=system_u:system_r:systemd_logind_t:s0 key=(null)
These definitely seem relevant. You said it's an EFI system. Is
/boot/efi mounted correctly? What user are you running systemctl as?
Where are you running it? From a console or from a graphical terminal
window?
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Will RedHat deprecate KDE on Fedora?
On 2018-11-04 7:24 a.m., Sam Varshavchik wrote: > Digimer writes: > >> On 2018-11-03 10:49 a.m., Wolfgang Pfeiffer wrote: >> > Legally that may be correct. But who's the main sponsor for Fedora? [1] >> > And usually the guy who pays for the orchestra decides for the tunes >> > that are played. Correct? >> >> No, not correct. Red Hat funds a lot of projects, simply to ensure they >> survive and thrive but then stays hands-off. Fedora, Centos and >> countless other projects included. They know they can't make decisions >> as well as the people at the front of a project, so they leave them be >> and simply pick off the parts that help them. > > So tell me, how exactly did we wind up with systemd, that landed with a > thud years ago, without anyone being able to point their fingers, > exactly, at the big community demand for it? > > If Red Hat truly stayed "hands off", the systemd garbage would've > withered and died a long time ago. There was a lot of handwaving about > all the big and useful features it had, but that's about it, but the > actual details were curiously scant. Without rehashing the systemd debate, I will point this out; Red Hat said they would have been fine with upstart, if Canonical had released it under a less restrictive license. SysV Init had to be replaced, it was terrible. Canonical didn't make a viable alternative, and no other projects were out there with any real viability. So they funded the creation and development of systemd and enough people liked it that it got picked up and hit critical mass. They never forced it on anyone. They sure as heck didn't force it on Debian anb Ubuntu, yet even they adopted it. So as much as you might not like it, it has some value to enough other people, including Fedora. >> > The people "working on it", you write. I note the difference to people >> > "working with it" ... ;) >> >> Most Fedora developers are users as well. Example; I live in the HA >> cluster world, mostly dominated by Red Hat (with an honourable mention > > Right. Now, I have better things to do on a day to day basis, so I could > be wrong on the following, but it's my impression that Red Hat has a > healthy percentage of Gnome developers on their payroll, if not an > outright majority of them. Tell me that I'm wrong, and Red Hat does not > have more say than anyone else, insofar as Gnome development goes. > > Which is why KDE is getting the boot. > >> > Plus: >> > As Fedora is more or less directly linked to RHEL [2] - what financial >> > sense does it make for Redhat to support the work on KDE if even now >> > already RHEL deprecates KDE? >> >> Fedora is arm's length and independent. RH sees the value / ROI on >> knowing they have a reliable place to build RHEL from, nothing more. >> Every RHEL release takes some version (or two) off of Fedora as a base. >> Once they have that base, they start heavily modifying it. > > There's certainty some value in having an army of unpaid volunteers > doing QA for you. And the longer they continue to believe that they have > any say in the larger roadmap, the better. > >> One of the top concerns, since RHEL 6, has been to streamline what RH >> support is liable for. If there are two projects that provide >> effectively the same thing, one will be dropped. This is purely for >> reducing support liability. We say this with Xen being dropped in EL6 in >> favour of KVM/qemu, for example. > > Right. And since Red Hat has more control over Gnome than KDE, is there > any mystery as to which one got the boot? > >> I suspect that is the same motivation for dropping KDE. Gnome is more >> popular and provides a GUI, > > Last time I checked, so did KDE. It's called Qt. > >> so why pay developers and support staff to >> support KDE in RHEL as well? > > Right, makes no sense. > >> The majority of GUI users on RHEL are >> "Workstation" systems, which don't generate them much money (compared to >> full RHEL) and are largely corporate, where standard builds are the norm. >> >> This is not a conspiracy again KDE, it's simply business. > > Right. And one very desirable thing that every business with an > established customer base looks for is vendor lock-in. systemd is vendor > lock-in, with Red Hat owning pretty much all technical knowledge of that > hairball. Gnome is being groomed to the same end result. At some point > it'll have the same cozy relationship with Red Hat that systemd does now. > >> Fedora, not >> being a source of income for them and being arm's length, will be left >> free to do and support whatever they want. > > That would only be true if Fedora incurs no expense to Red Hat. Perhaps > some minimal expense on the account of KDE will be tolerable. But I > don't think it would take a lot for KDE to leave via the same door where > systemd came in. > >> Who knows, maybe someday it >> will make sense to swap out Gnome for KDE as the official GUI? Leave it >> to the community and let time tell. > > Never going to happen. Of t
Re: dnf : Failed to set locale, defaulting to C
On Sun, 4 Nov 2018 19:51:40 +0200 Adrian Sevcenco wrote: > Hi! I just upgraded fron f28 and when using dnf i get : > Failed to set locale, defaulting to C > > but i have : > [root@t420 ~]# rpm -qa | grep glibc-langpack > glibc-langpack-en-2.28-9.fc29.x86_64 > > Does anyone have any idea what's going on? No idea, you should be good to go. Some things to try. What's in /etc/locale.conf? If it isn't defined properly, you should set it to the locale you desire. e.g. LANG="en_US.UTF-8" What shows for LANG when you type locale at a prompt? There should be a UTF-8 on the end of that. I saw that some people were able to fix this by reinstalling glibc-langpack-en. You could also try rebuilding the locale def as UTF-8 with localedef -f UTF-8 -i en_US en_US.UTF-8 if your desired locale is en_US. Adjust for your locale accordingly. You could try forcing it with echo "export LANG=en_US.UTF-8" >> $HOME/.bashrc so that your shell environment always has lang set to en_US.UTF-8 ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Is tracer working?
On Sun, 2018-11-04 at 17:40 +0100, Dario Lesca wrote: > Il giorno dom, 04/11/2018 alle 14.32 +, Patrick O'Callaghan ha > scritto: > > Has anyone else seen strange behaviour from tracer? > Yes, there is something strange. > I have update some packages this morning and do not have reboot. If I > run "sudo tracer" none is show. > If I run "sudo lsof|grep delete" I found many system's binary apps > update but running old version (deleted), > [root@dodo:~]# lsof 2>/dev/null|grep deleted|wc -l3620 > for example NetworkManager: > [root@dodo:~]# grep NetworkManager-1 /var/log/dnf.log NetworkManager- > 1:1.12.4-2.fc29.x86_64NetworkManager-adsl-1:1.12.4- > 2.fc29.x86_64 2018-11-04T10:21:13Z DDEBUG > /var/cache/dnf/updates-0b4cc238d1aa4ffe/packages/NetworkManager-1.12.4- > 2.fc29.x86_64.rpm eliminato[root@dodo:~]# lsof|grep > NetworkMa.*deletedlsof: WARNING: can't stat() fuse.gvfsd-fuse file > system /run/user/1000/gvfs Output information may be > incomplete.NetworkMa 1077root txt REG > 253,2 3095264 446801 /usr/sbin/NetworkManager > (deleted)NetworkMa 1077 1081 > gmainroot txt REG 253,2 3095264 44680 > 1 /usr/sbin/NetworkManager (deleted)NetworkMa 1077 1083 > gdbusroot txt REG 253,2 3095264 44680 > 1 /usr/sbin/NetworkManager (deleted)[root@dodo:~]# ll -i > /usr/sbin/NetworkManager446800 -rwxr-xr-x 1 root root 3095264 29 ott > 18.41 /usr/sbin/NetworkManager > The I-Node of binary is changed because the binari it was update. > If I restart my NB I do not see anymore deleted flag for system appls > and I-node, for example of NM, match > Seem tracer not work anymore ... It has a BZ entry. Seems it has been around since Rawhide: https://bugzilla.redhat.com/show_bug.cgi?id=1607754 poc ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Clean Install of F29 problems
On Sun, 2018-11-04 at 09:48 -0500, Tom Horsley wrote: > On Sun, 04 Nov 2018 13:34:29 + > Patrick O'Callaghan wrote: > > > Unless you explicitly deleted the cache (e.g. with 'dnf clean') it > > should not have been necessary to repeat the download. > > I noticed the same thing, I found the keepcache parameter > in the dnf.conf man page that says the default is False (I > change it to True, but only after I had to re-download 3GB > of packages). Apparently the default has changed. However according to dnf.conf(5): Even if it is set to False and packages have not been installed they will still persist until next successful transaction. poc ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: gnome-control-center coredumps
On Sun, 2018-11-04 at 08:39 -0500, Tom Horsley wrote: > On Sun, 04 Nov 2018 12:11:08 + > Patrick O'Callaghan wrote: > > > I tried to run gnome-control-center under KDE to look at some Gnome- > > related settings, and got this: > > > > $ gnome-control-center > > > > ERROR:../shell/cc-shell-model.c:458:cc_shell_model_set_panel_visibility: > > assertion failed: (valid) > > Aborted (core dumped) > > > > Reported as https://bugzilla.redhat.com/show_bug.cgi?id=1645855 > > I get the same thing. Apparently they've arranged for it > to only be runnable under gnome? > > https://bugzilla.redhat.com/show_bug.cgi?id=1645664 I always assumed that the only reason for g-c-c to exist was so that users of other DEs could access Gnome settings. If it can only run under Gnome that rather defeats the purpose I would think. poc ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
dnf : Failed to set locale, defaulting to C
Hi! I just upgraded fron f28 and when using dnf i get : Failed to set locale, defaulting to C but i have : [root@t420 ~]# rpm -qa | grep glibc-langpack glibc-langpack-en-2.28-9.fc29.x86_64 Does anyone have any idea what's going on? Thank you!! Adrian ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Problem AdobeReader after upgrade F28 to F29.
On Fri, 2 Nov 2018, Ranjan Maitra wrote: On Fri, 2 Nov 2018 19:17:27 +0100 Markus Schönhaber wrote: Ger Van Dijck, Fri, 02 Nov 2018 14:32:43 +0100: The Acrobat Reader does not funktionate anymore : So I tried to reinstall it with AdbeRdr9.5.5-1_i486linux_enu.rpm . I get the message "build transaction failure , conflicting requests ; nothing provides libidn.so.11 needed by AcrobatReader_enu-9.5.5-1.i486 . How can I solve this problem ? _ You can solve this problem by not using this ancient, unsupported piece of software which contains a lot of unpatched security bugs. There are quite a few PDF readers available in the Fedora repositories (Okular, Evince, MuPDF, …) you can choose from. Very likely there's already one installed that came with your DE. Otherwise, pick the one that suits you best. Hi, I agree that choosing an OSS pdf viewer is the best. However is there a viewer that can handle animation? This is the only reason I sometimes use acroread. An example of what I am talking about is in this file (created by LaTeX): there is a file in there called stadoc.pdf which has the animation on Page 5, Movie 1. https://wol-prod-cdn.literatumonline.com/pb-assets/assets/20491573/Stat_AutClass_v4_rev-1508937938000.zip When I try to read it in evince or okular, in the first case, nothing happens with the animation. In the case of okular, I get a blank gray square where the animation is. (All this with F28: I do not know if upgrading F29 will fix that in the sense that if there is an upgrade to evince or okular.) Joining the chorus of those who use AdobeReader, two benefits: - Adobe has tabs rather than individual windows in order to view several documents at once; - Adobe's save-as-text function sometimes works better than pdftotext; since there is no standardization of pdf files, sometimes one tool renders the text better than the other (YMMV) Thanks, Max Thanks, Ranjan ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Is tracer working?
Il giorno dom, 04/11/2018 alle 14.32 +, Patrick O'Callaghan ha scritto: > Has anyone else seen strange behaviour from tracer? Yes, there is something strange. I have update some packages this morning and do not have reboot. If I run "sudo tracer" none is show. If I run "sudo lsof|grep delete" I found many system's binary apps update but running old version (deleted), [root@dodo:~]# lsof 2>/dev/null|grep deleted|wc -l3620 for example NetworkManager: [root@dodo:~]# grep NetworkManager-1 /var/log/dnf.log NetworkManager- 1:1.12.4-2.fc29.x86_64NetworkManager-adsl-1:1.12.4- 2.fc29.x86_64 2018-11-04T10:21:13Z DDEBUG /var/cache/dnf/updates-0b4cc238d1aa4ffe/packages/NetworkManager-1.12.4- 2.fc29.x86_64.rpm eliminato[root@dodo:~]# lsof|grep NetworkMa.*deletedlsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs Output information may be incomplete.NetworkMa 1077root txt REG 253,2 3095264 446801 /usr/sbin/NetworkManager (deleted)NetworkMa 1077 1081 gmainroot txt REG 253,2 3095264 44680 1 /usr/sbin/NetworkManager (deleted)NetworkMa 1077 1083 gdbusroot txt REG 253,2 3095264 44680 1 /usr/sbin/NetworkManager (deleted)[root@dodo:~]# ll -i /usr/sbin/NetworkManager446800 -rwxr-xr-x 1 root root 3095264 29 ott 18.41 /usr/sbin/NetworkManager The I-Node of binary is changed because the binari it was update. If I restart my NB I do not see anymore deleted flag for system appls and I-node, for example of NM, match Seem tracer not work anymore ... -- Dario Lesca (inviato dal mio Linux Fedora 28 Workstation) ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Will a T42 thinkpad run F29?
On Sun, 04 Nov 2018 06:31:52 -0500, Ted Roche wrote: > Hi, Beartooth: > > IIRC when discussed in January, people pointed you to the 32-bit distro, > as the T42 runs a 32-bit Pentium-M processor. > > That's what I'd try. You mean I was here before? Milles Pardons! And I'll go download the 32-bit now. Thanks again! -- Beartooth Staffwright, Not Quite Clueless Power User Remember I know little (precious little!) of where up is. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Clean Install of F29 problems
On Sun, 04 Nov 2018 14:29:08 + ja wrote: > There is a bug in the tex-fonts-hebrew rpm as trying to install > it on a working machine fails. > root@paxos:~]$ dnf install tex-fonts-hebrew > ... > Installed: tex-fonts-hebrew-0.1-28.fc29.noarch > > Installing : tex-fonts-hebrew-0.1-28.fc29.noarch > Running scriptlet: tex-fonts-hebrew-0.1-28.fc29.noarch > /usr/bin/texconfig-sys: line 33: exec: texconfig: not found > Option cnffile requires an argument > Try "updmap --help" for more information. > warning: %post(tex-fonts-hebrew-0.1-28.fc29.noarch) scriptlet failed, > exit status 255 Error in POSTIN scriptlet in rpm package > tex-fonts-hebrew Installed: tex-fonts-hebrew-0.1-28.fc29.noarch This is strange, since it is the same package as f28, just rebuilt in the f29 environment. You could try installing the f28 package from here https://koji.fedoraproject.org/koji/buildinfo?buildID=1042001 to see if it has the same issue. When I do a net install, I always do a minimal install first, and then use dnf to do the updates while running the new install, pulling from the repositories. It seems to work fine, and errors like you encountered aren't as painful. And, as Patrick said, if cache removal is turned off, the downloaded files remain locally so there is only the one download. At the end a dnf clean packages will remove them. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Will RedHat deprecate KDE on Fedora?
On Sun, 2018-11-04 at 07:07 -0600, Rex Dieter wrote: > Matthew Miller wrote: > > > snip > > > > That said: also, no, there is no such plan. As long as people are > > interested in working on it, there will be a KDE desktop option in > > Fedora. > > As a long-time contributor to fedora kde-sig, I emphatically echo > what > Matthew just said. > > -- Rex > That's good to hear. I'm a fan of both Fedora and KDE... though I'm not running Fedora now. Unfortunately, Fedora 29 won't install on my laptop. This seems to happen once every two or three versions, and then gets fixed. It's easier for me to move to a different distro (right now I'm using KDE Neon) than try to deal with odd grub/efi/hardware/bios/dual boot issues, and it almost always seems to go away with the next version. billo ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Clean Install of F29 problems
On Sun, 04 Nov 2018 13:34:29 + Patrick O'Callaghan wrote: > Unless you explicitly deleted the cache (e.g. with 'dnf clean') it > should not have been necessary to repeat the download. I noticed the same thing, I found the keepcache parameter in the dnf.conf man page that says the default is False (I change it to True, but only after I had to re-download 3GB of packages). Apparently the default has changed. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Is tracer working?
Since upgrading to F29 a couple of days ago I've continued my usual routine of running 'dnf update' every morning. However in contrast to what always happened with F28 (and earlier), I never get any feedback about restarting services or running apps, even when I know that something that is currently running has been changed. I have the dnf.plugin.tracer package installed. I've also run 'sudo tracer' directly, with no result. Has anyone else seen strange behaviour from tracer? poc ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Clean Install of F29 problems
On Sun, 2018-11-04 at 13:34 +, Patrick O'Callaghan wrote: > On Sun, 2018-11-04 at 09:17 +, ja wrote: > > 2. A fatal dnf error during installation of tex-fonts-hebrew rpm > > required a complete start from scratch avoiding this particular rpm. > > (Another 2.5GB download) > > Unless you explicitly deleted the cache (e.g. with 'dnf clean') it > should not have been necessary to repeat the download. > As far as I could tell my only choice was to re-boot the USB Net Install stick and go through everything again - the cache being destroyed?? I had a go at using Cont/Alt/Fn but there was no obvious info on how to continue The graphical display just had a pop up that said something like "Fatal dnf error" No option to continue or skip There is a bug in the tex-fonts-hebrew rpm as trying to install it on a working machine fails. root@paxos:~]$ dnf install tex-fonts-hebrew ... Installed: tex-fonts-hebrew-0.1-28.fc29.noarch Installing : tex-fonts-hebrew-0.1-28.fc29.noarch Running scriptlet: tex-fonts-hebrew-0.1-28.fc29.noarch /usr/bin/texconfig-sys: line 33: exec: texconfig: not found Option cnffile requires an argument Try "updmap --help" for more information. warning: %post(tex-fonts-hebrew-0.1-28.fc29.noarch) scriptlet failed, exit status 255 Error in POSTIN scriptlet in rpm package tex-fonts-hebrew Installed: tex-fonts-hebrew-0.1-28.fc29.noarch ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Will RedHat deprecate KDE on Fedora?
On Sun, 2018-11-04 at 07:24 -0500, Sam Varshavchik wrote: > That would only be true if Fedora incurs no expense to Red Hat. Perhaps some > minimal expense on the account of KDE will be tolerable. But I don't think > it would take a lot for KDE to leave via the same door where systemd came in. Without wishing to get into yet another discussion about the merits or otherwise of systemd, I'd just point out that it's now used by every major Linux distro. Those that don't can be found here: http://without-systemd.org/wiki/index.php/Linux_distributions_without_systemd poc ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Why this activity on mounted but unused fs?
On Mon, 5 Nov 2018 00:04:00 +1100 Eyal Lebedinsky wrote: > Interesting. The array was mounted for many hours, but maybe not long enough. At the low rate it does background activity, I'd guess days to get through 55TB. It took about a day to get through with my 8TB raid. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: gnome-control-center coredumps
On Sun, 04 Nov 2018 12:11:08 + Patrick O'Callaghan wrote: > I tried to run gnome-control-center under KDE to look at some Gnome- > related settings, and got this: > > $ gnome-control-center > > ERROR:../shell/cc-shell-model.c:458:cc_shell_model_set_panel_visibility: > assertion failed: (valid) > Aborted (core dumped) > > Reported as https://bugzilla.redhat.com/show_bug.cgi?id=1645855 I get the same thing. Apparently they've arranged for it to only be runnable under gnome? https://bugzilla.redhat.com/show_bug.cgi?id=1645664 ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Clean Install of F29 problems
On Sun, 2018-11-04 at 09:17 +, ja wrote: > 2. A fatal dnf error during installation of tex-fonts-hebrew rpm > required a complete start from scratch avoiding this particular rpm. > (Another 2.5GB download) Unless you explicitly deleted the cache (e.g. with 'dnf clean') it should not have been necessary to repeat the download. poc ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: hibernate stops working after upgrade to F29 from F28
On Sat, 3 Nov 2018 22:34:00 -0700 Samuel Sieb wrote:
> On 11/3/18 9:48 PM, Ranjan Maitra wrote:
> > On Sat, 3 Nov 2018 21:39:41 -0700 Samuel Sieb wrote:
> >> That is a likely cause. Are there any other lines from logind in the
> >> journal? What is in /proc/cmdline?
> >
> > I don't know hoe to look in the journal. With regard to /proc/cmdline:
>
> In one terminal window, run "sudo journalctl -fa". In another one, try
> to hibernate. See what lines get printed in the first terminal.
Nov 04 07:19:29 machine.name polkitd[800]: Registered Authentication Agent for
unix-process:2334:95259 (system bus name :1.175 [/usr/bin/pkttyagent
--notify-fd 5 --fallback], object path
/org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
Nov 04 07:19:29 machine.name audit[827]: AVC avc: denied { read } for
pid=827 comm="systemd-logind" name="nvme0n1p1" dev="devtmpfs" ino=17625
scontext=system_u:system_r:systemd_logind_t:s0
tcontext=system_u:object_r:nvme_device_t:s0 tclass=blk_file permissive=0
Nov 04 07:19:29 machine.name audit[827]: SYSCALL arch=c03e syscall=257
success=no exit=-13 a0=ff9c a1=7ffe3533e050 a2=8 a3=0 items=0 ppid=1
pid=827 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0
tty=(none) ses=4294967295 comm="systemd-logind"
exe="/usr/lib/systemd/systemd-logind"
subj=system_u:system_r:systemd_logind_t:s0 key=(null)
Nov 04 07:19:29 machine.name audit: PROCTITLE
proctitle="/usr/lib/systemd/systemd-logind"
Nov 04 07:19:29 machine.name systemd-logind[827]: Failed to open file system
"/boot/efi": Permission denied
Nov 04 07:19:29 machine.name polkitd[800]: Unregistered Authentication Agent
for unix-process:2334:95259 (system bus name :1.175, object path
/org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
(disconnected from bus)
Nov 04 07:19:29 machine.name kernel: audit: type=1400
audit(1541337569.994:258): avc: denied { read } for pid=827
comm="systemd-logind" name="nvme0n1p1" dev="devtmpfs" ino=17625
scontext=system_u:system_r:systemd_logind_t:s0
tcontext=system_u:object_r:nvme_device_t:s0 tclass=blk_file permissive=0
Nov 04 07:19:29 machine.name kernel: audit: type=1300
audit(1541337569.994:258): arch=c03e syscall=257 success=no exit=-13
a0=ff9c a1=7ffe3533e050 a2=8 a3=0 items=0 ppid=1 pid=827
auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0
tty=(none) ses=4294967295 comm="systemd-logind"
exe="/usr/lib/systemd/systemd-logind"
subj=system_u:system_r:systemd_logind_t:s0 key=(null)
Nov 04 07:19:29 machine.name kernel: audit: type=1327
audit(1541337569.994:258): proctitle="/usr/lib/systemd/systemd-logind"
Is it time for a BZ report? However, this is probably a systemd bug upstream
given the information that I think you dug out here:
https://github.com/systemd/systemd/issues/10613
But it might help to know that Fedora like Arch also reports this problem.
I was thinking of downgrading systemd, but then I am not sure what all
components need to be downgrading, since there are many.
> > $ m /proc/cmdline
> > BOOT_IMAGE=/boot/vmlinuz-4.18.16-300.fc29.x86_64
> > root=UUID=bfae51c6-7f8c-4b0b-8b3b-af6af9ae5446 ro
> > resume=UUID=a83ac239-cc10-43a6-be54-de4ce7050605 rhgb quiet LANG=en_US.UTF-8
> >
> > and:
> >
> > This is the relevant part from sudo blkid:
> >
> > /dev/nvme0n1p4: UUID="a83ac239-cc10-43a6-be54-de4ce7050605" TYPE="swap"
> > PARTUUID="1b80fbac-938f-41f1-82bc-3e0dee5ffef1"
>
> Those look fine.
>
> You could try installing pm-utils from:
> https://koji.fedoraproject.org/koji/buildinfo?buildID=691608
>
> See if "pm-hibernate" works.
Thanks, does this work with efi systems?
Many thanks,
Ranjan
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Will RedHat deprecate KDE on Fedora?
Matthew Miller wrote: > On Fri, Nov 02, 2018 at 09:00:17PM -0400, William Oliver wrote: >> I just read this in The Register -- that RH is deprecating KDE in >> RHEL. As a long time fan of KDE, I'm a bit saddened. Is this planned >> for Fedora as well? > > Red Hat doesn't make decisions for Fedora. > > That said: also, no, there is no such plan. As long as people are > interested in working on it, there will be a KDE desktop option in Fedora. As a long-time contributor to fedora kde-sig, I emphatically echo what Matthew just said. -- Rex ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Why this activity on mounted but unused fs?
On 4/11/18 11:49 pm, Tom Horsley wrote: On Sun, 4 Nov 2018 16:19:45 +1100 Eyal Lebedinsky wrote: I then mounted it on a new mount point which I have no process using. I started hearing knocks from the PC case, and touching the disks revealed that they all had activity 1-2 times a second, concurrently, leading to the louder than usual noise. If it is an ext4 filesystem, then a newly formatted ext4 gets background activity building some sort of internal data structures. It eventually stops doing it if makes it all the way through. Possibly other filesystems do something similar, but I know ext4 does. Interesting. The array was mounted for many hours, but maybe not long enough. Filesystem Size Used Avail Use% Mounted on /dev/md127 55T 17T 38T 32% /new-raid Seeing only 'write's suggests that it may be busy initializing some internal tables? I will leave it mounted overnight (or longer). Naturally, once commissioned it will stay mounted for years. -- Eyal at Home (fed...@eyal.emu.id.au) ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Why this activity on mounted but unused fs?
On 4/11/18 11:11 pm, Berend De Schouwer wrote: On Sun, 2018-11-04 at 18:57 +1100, Eyal Lebedinsky wrote: On 4/11/18 6:39 pm, Berend De Schouwer wrote: On Sun, 2018-11-04 at 17:32 +1100, Eyal Lebedinsky wrote: On 4/11/18 4:44 pm, Samuel Sieb wrote: On 11/3/18 10:19 PM, Eyal Lebedinsky wrote: What is this io, and can it be stopped? I want to allow the disks to enter low power mode (not spin down) when idle. I'm assuming since it's a new RAID that you haven't created files on it yet, or at least not many. Try running "lsof +D /mnt/point" to see if there is any process looking at it. Then try running "inotifywait -rm /mnt/point" and let it run for a little while to see if you can catch some process accessing the fs. You will need to install "inotify-tools" to get that program. Sure, should have said a bit more: The array was resync'ed, then (much) data was copied in. This was a few days ago. Did the sync finish? What is the kernel status of the array? cat /proc/mdstat Yes, as I mentioned, the sync finished (28/Oct), then the copy finished (30/Oct). Acquired a new case and installed the array there (using an old mobo) testing how the case ventilation performs. Waiting for a new mobo/CPU/mem. It is during this quiet period that I noticed the io issue which got me wondering. Since this happens only when the array is mounted, and I do not see any files being touched, I wondered if this is some ext4 internal housekeeping. Can this be related to the size of the fs? Maybe. Maybe the journal. Maybe a runaway sync(). The machine was reboot numerous times, same thing. You can play with mount options like 'noatime.' Note that some mount options might cause data corruption. Look in /proc/mounts for the currently used options. See if there's something different to /. Same options: /dev/sda2 on / type ext4 (rw,relatime) /dev/md127 on /new-raid type ext4 (rw,relatime,stripe=640) 'noatime' showa similar activity to 'realtime'. read-only mount stops this activity. Your original mail showed more activity on /dev/sdb .. sdh than on /dev/md127, so it might be raid housekeeping, or a ext4/raid barrier. This is OK. Looking at one entry in 'iostat 100': avg-cpu: %user %nice %system %iowait %steal %idle 0.010.000.120.640.00 99.24 Device tpskB_read/skB_wrtn/skB_readkB_wrtn sda 0.01 0.08 0.00 8 0 sdc 5.14 5.1216.23512 1623 sdg 6.5026.3637.47 2636 3747 sdh 5.86 7.8018.91780 1891 sdf 7.6435.7646.87 3576 4687 sde 6.6419.7630.87 1976 3087 sdd 5.14 5.1216.23512 1623 sdb 5.28 7.3618.47736 1847 md127 1.59 0.0035.76 0 3576 For RAID6 'write' generates more activity than for a plain device. Even a small 'write' leads to whole stripes read/modify/write. Note that there are no 'read' operations on the array. What I see is a periodic 'write' of about 20KB to md127, probably to the fs, This rate is very constant. If I have to guess I would say this is some ext4 internal activity to a control area (not to a file in the fs). /dev/md127 showed only write access. Is that typical too? The shortest way to know if it's ext4 is to re-format as xfs or btrfs. I don't suggest you do that lightly. -- Eyal at Home (fed...@eyal.emu.id.au) ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Why this activity on mounted but unused fs?
On Sun, 4 Nov 2018 16:19:45 +1100 Eyal Lebedinsky wrote: > I then mounted it on a new mount point which I have no process using. I > started hearing > knocks from the PC case, and touching the disks revealed that they all had > activity 1-2 > times a second, concurrently, leading to the louder than usual noise. If it is an ext4 filesystem, then a newly formatted ext4 gets background activity building some sort of internal data structures. It eventually stops doing it if makes it all the way through. Possibly other filesystems do something similar, but I know ext4 does. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Will RedHat deprecate KDE on Fedora?
Digimer writes: On 2018-11-03 10:49 a.m., Wolfgang Pfeiffer wrote: > Legally that may be correct. But who's the main sponsor for Fedora? [1] > And usually the guy who pays for the orchestra decides for the tunes > that are played. Correct? No, not correct. Red Hat funds a lot of projects, simply to ensure they survive and thrive but then stays hands-off. Fedora, Centos and countless other projects included. They know they can't make decisions as well as the people at the front of a project, so they leave them be and simply pick off the parts that help them. So tell me, how exactly did we wind up with systemd, that landed with a thud years ago, without anyone being able to point their fingers, exactly, at the big community demand for it? If Red Hat truly stayed "hands off", the systemd garbage would've withered and died a long time ago. There was a lot of handwaving about all the big and useful features it had, but that's about it, but the actual details were curiously scant. > The people "working on it", you write. I note the difference to people > "working with it" ... ;) Most Fedora developers are users as well. Example; I live in the HA cluster world, mostly dominated by Red Hat (with an honourable mention Right. Now, I have better things to do on a day to day basis, so I could be wrong on the following, but it's my impression that Red Hat has a healthy percentage of Gnome developers on their payroll, if not an outright majority of them. Tell me that I'm wrong, and Red Hat does not have more say than anyone else, insofar as Gnome development goes. Which is why KDE is getting the boot. > Plus: > As Fedora is more or less directly linked to RHEL [2] - what financial > sense does it make for Redhat to support the work on KDE if even now > already RHEL deprecates KDE? Fedora is arm's length and independent. RH sees the value / ROI on knowing they have a reliable place to build RHEL from, nothing more. Every RHEL release takes some version (or two) off of Fedora as a base. Once they have that base, they start heavily modifying it. There's certainty some value in having an army of unpaid volunteers doing QA for you. And the longer they continue to believe that they have any say in the larger roadmap, the better. One of the top concerns, since RHEL 6, has been to streamline what RH support is liable for. If there are two projects that provide effectively the same thing, one will be dropped. This is purely for reducing support liability. We say this with Xen being dropped in EL6 in favour of KVM/qemu, for example. Right. And since Red Hat has more control over Gnome than KDE, is there any mystery as to which one got the boot? I suspect that is the same motivation for dropping KDE. Gnome is more popular and provides a GUI, Last time I checked, so did KDE. It's called Qt. so why pay developers and support staff to support KDE in RHEL as well? Right, makes no sense. The majority of GUI users on RHEL are "Workstation" systems, which don't generate them much money (compared to full RHEL) and are largely corporate, where standard builds are the norm. This is not a conspiracy again KDE, it's simply business. Right. And one very desirable thing that every business with an established customer base looks for is vendor lock-in. systemd is vendor lock-in, with Red Hat owning pretty much all technical knowledge of that hairball. Gnome is being groomed to the same end result. At some point it'll have the same cozy relationship with Red Hat that systemd does now. Fedora, not being a source of income for them and being arm's length, will be left free to do and support whatever they want. That would only be true if Fedora incurs no expense to Red Hat. Perhaps some minimal expense on the account of KDE will be tolerable. But I don't think it would take a lot for KDE to leave via the same door where systemd came in. Who knows, maybe someday it will make sense to swap out Gnome for KDE as the official GUI? Leave it to the community and let time tell. Never going to happen. Of that, I'm certain. pgpAGmKoNuNvY.pgp Description: PGP signature ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
gnome-control-center coredumps
I tried to run gnome-control-center under KDE to look at some Gnome- related settings, and got this: $ gnome-control-center (gnome-control-center:12420): dbind-WARNING **: 12:02:42.073: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. failed to open /usr/lib64/dri/hybrid_drv_video.so Not using hybrid_drv_video.so failed to open /usr/lib64/dri/hybrid_drv_video.so Not using hybrid_drv_video.so ** ERROR:../shell/cc-shell-model.c:458:cc_shell_model_set_panel_visibility: assertion failed: (valid) Aborted (core dumped) Reported as https://bugzilla.redhat.com/show_bug.cgi?id=1645855 poc ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Why this activity on mounted but unused fs?
On Sun, 2018-11-04 at 18:57 +1100, Eyal Lebedinsky wrote: > On 4/11/18 6:39 pm, Berend De Schouwer wrote: > > On Sun, 2018-11-04 at 17:32 +1100, Eyal Lebedinsky wrote: > > > On 4/11/18 4:44 pm, Samuel Sieb wrote: > > > > On 11/3/18 10:19 PM, Eyal Lebedinsky wrote: > > > > > What is this io, and can it be stopped? I want to allow the > > > > > disks > > > > > to enter > > > > > low power mode (not spin down) when idle. > > > > > > > > I'm assuming since it's a new RAID that you haven't created > > > > files > > > > on it yet, or at least not many. Try running "lsof +D > > > > /mnt/point" > > > > to see if there is any process looking at it. Then try running > > > > "inotifywait -rm /mnt/point" and let it run for a little while > > > > to > > > > see if you can catch some process accessing the fs. You will > > > > need > > > > to install "inotify-tools" to get that program. > > > > > > Sure, should have said a bit more: The array was resync'ed, then > > > (much) data was copied in. This was a few days ago. > > > > Did the sync finish? What is the kernel status of the array? > > cat /proc/mdstat > > Yes, as I mentioned, the sync finished (28/Oct), then the copy > finished (30/Oct). > Acquired a new case and installed the array there (using an old mobo) > testing how > the case ventilation performs. Waiting for a new mobo/CPU/mem. > > It is during this quiet period that I noticed the io issue which got > me wondering. > > Since this happens only when the array is mounted, and I do not see > any files being > touched, I wondered if this is some ext4 internal housekeeping. Can > this be related > to the size of the fs? Maybe. Maybe the journal. Maybe a runaway sync(). You can play with mount options like 'noatime.' Note that some mount options might cause data corruption. Look in /proc/mounts for the currently used options. See if there's something different to /. Your original mail showed more activity on /dev/sdb .. sdh than on /dev/md127, so it might be raid housekeeping, or a ext4/raid barrier. /dev/md127 showed only write access. Is that typical too? The shortest way to know if it's ext4 is to re-format as xfs or btrfs. I don't suggest you do that lightly. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Will a T42 thinkpad run F29?
Hi, Beartooth: IIRC when discussed in January, people pointed you to the 32-bit distro, as the T42 runs a 32-bit Pentium-M processor. That's what I'd try. On Sat, Nov 3, 2018 at 5:59 PM Beartooth wrote: > > Background: F28 has been the first Fedora release that has given > troubles on a couple of old PCs (built for me by friends who speak > hardware; so I don't have specs) -- troubles which other friends > attribute to those PCs lacking hardware that F28 requires. I'm in process > of burning a live DVD (with MATE - Compiz) of F29 which I'll try with > them; if it seems to run, I'll try installing it. So far, I think I know > at least roughly what I'm doing. > > But, to get to the real point, I also have an old T42 Thinkpad > which has been gathering dust. I'd like to do the same with it as with > the PCs. But, if there is anyone anywhere who can say at sight whether > there's any hope, that may save me considerable frustration. How about it? > -- > Beartooth Staffwright, Not Quite Clueless Power User > Remember I know little (precious little!) of where up is. > ___ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org > -- Ted Roche Ted Roche & Associates, LLC http://www.tedroche.com ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Systemd update
Sun, 4 Nov 2018 17:52:11 +0800 Ed Greshko kirjoitti: > No, I meant when you get the boot screen to select which kernel to > start that you type "e" and edit the linux16 line to add that to the > end. Sri, not good morning :) didn't think that... Now works, was my stupid editing selinux config file. Now it's ok and disabled... Let's ride to sun set... Jarmo ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Systemd update
On 11/4/18 4:26 PM, jarmo wrote: > Sun, 4 Nov 2018 15:58:07 +0800 > Ed Greshko kirjoitti: > > >> You can probably get it to boot by adding "selinux=0" to the boot >> params. > Other words live media and edit via that. As quessed.. > No, I meant when you get the boot screen to select which kernel to start that you type "e" and edit the linux16 line to add that to the end. -- Fedora Users - The place to go to beat OT dead horses :-) :-) ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Systemd update
Sun, 4 Nov 2018 15:58:07 +0800 Ed Greshko kirjoitti: > You can probably get it to boot by adding "selinux=0" to the boot > params. Other words live media and edit via that. As quessed.. Tnx, Jarmo ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Clean Install of F29 problems
I have made a clean installed of F29 onto a small SSD and had a few problems which may be of interest. 1. It was necessary to separately dd and recreate the required partitions using gdisk to get the installer to accept a custom layout. The installer would not let me use the existing partitions. 2. A fatal dnf error during installation of tex-fonts-hebrew rpm required a complete start from scratch avoiding this particular rpm. (Another 2.5GB download) 3. I have been using _dnf_local and a local F29 repo for several releases Having set things up as previously the two repos give these errors. Any hints as to what I have missed with the repos would be very useful. [root@paxos:~]$ dnf install nedit Local ja Fedora 29 x86_64 Updates _dnf_local Fedora Modular 29 - x86_64 google-chrome google-earth-pro RPM Fusion for Fedora 29 - Free - Updates RPM Fusion for Fedora 29 - Nonfree - Updates Failed to synchronize cache for repo 'local-29-update', ignoring this repo. Failed to synchronize cache for repo '_dnf_local', ignoring this repo. Package nedit-5.7-5.fc29.x86_64 is already installed. Dependencies resolved. Nothing to do. Complete! Thanks ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Systemd update
On 11/4/18 3:41 PM, jarmo wrote: > Brought nasty surprise. I have selinux disabled has been in F28 > and upgraded F29. Now, I can't get laptop (HP) running. Stops > to: Can't find selinux policy freezing! > Upgrade itself went smoothly, but this last systemd upgrade > made it. > > Shortest way to repair system. Laptop is for testing, so no > important is going to loose, if install again. You can probably get it to boot by adding "selinux=0" to the boot params. Then fix up whatever you need to. -- Fedora Users - The place to go to beat OT dead horses :-) :-) ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Why this activity on mounted but unused fs?
On 4/11/18 6:39 pm, Berend De Schouwer wrote: On Sun, 2018-11-04 at 17:32 +1100, Eyal Lebedinsky wrote: On 4/11/18 4:44 pm, Samuel Sieb wrote: On 11/3/18 10:19 PM, Eyal Lebedinsky wrote: What is this io, and can it be stopped? I want to allow the disks to enter low power mode (not spin down) when idle. I'm assuming since it's a new RAID that you haven't created files on it yet, or at least not many. Try running "lsof +D /mnt/point" to see if there is any process looking at it. Then try running "inotifywait -rm /mnt/point" and let it run for a little while to see if you can catch some process accessing the fs. You will need to install "inotify-tools" to get that program. Sure, should have said a bit more: The array was resync'ed, then (much) data was copied in. This was a few days ago. Did the sync finish? What is the kernel status of the array? cat /proc/mdstat Yes, as I mentioned, the sync finished (28/Oct), then the copy finished (30/Oct). Acquired a new case and installed the array there (using an old mobo) testing how the case ventilation performs. Waiting for a new mobo/CPU/mem. It is during this quiet period that I noticed the io issue which got me wondering. Since this happens only when the array is mounted, and I do not see any files being touched, I wondered if this is some ext4 internal housekeeping. Can this be related to the size of the fs? Filesystem Size Used Avail Use% Mounted on /dev/md127 55T 17T 38T 32% /new-raid $ cat /proc/mdstat Personalities : [raid6] [raid5] [raid4] md127 : active raid6 sdc1[1] sdb1[0] sdf1[4] sdh1[6] sde1[3] sdd1[2] sdg1[5] 58593761280 blocks super 1.2 level 6, 512k chunk, algorithm 2 [7/7] [UUU] bitmap: 1/88 pages [4KB], 65536KB chunk unused devices: -- Eyal at Home (fed...@eyal.emu.id.au) ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Systemd update
Brought nasty surprise. I have selinux disabled has been in F28 and upgraded F29. Now, I can't get laptop (HP) running. Stops to: Can't find selinux policy freezing! Upgrade itself went smoothly, but this last systemd upgrade made it. Shortest way to repair system. Laptop is for testing, so no important is going to loose, if install again. Jarmo ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Why this activity on mounted but unused fs?
On Sun, 2018-11-04 at 17:32 +1100, Eyal Lebedinsky wrote: > On 4/11/18 4:44 pm, Samuel Sieb wrote: > > On 11/3/18 10:19 PM, Eyal Lebedinsky wrote: > > > What is this io, and can it be stopped? I want to allow the disks > > > to enter > > > low power mode (not spin down) when idle. > > > > I'm assuming since it's a new RAID that you haven't created files > > on it yet, or at least not many. Try running "lsof +D /mnt/point" > > to see if there is any process looking at it. Then try running > > "inotifywait -rm /mnt/point" and let it run for a little while to > > see if you can catch some process accessing the fs. You will need > > to install "inotify-tools" to get that program. > > Sure, should have said a bit more: The array was resync'ed, then > (much) data was copied in. This was a few days ago. Did the sync finish? What is the kernel status of the array? cat /proc/mdstat ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
