Re: battery discharging whilelaptop powered off?
On 05/21/2018 09:06 AM, Wolfgang Pfeiffer wrote: I'd try retraining the battery for longer run-time until empty: Depleting the battery fully does not extend the run-time of the battery. It will sometimes re-calibrate the battery controller and improve its estimates, but it does reduce the battery's ability to hold a charge. https://arstechnica.com/gadgets/2014/04/ask-ars-the-best-way-to-use-a-lithium-ion-battery-redux/ ___ 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/message/OU2GRNDH5TX5QUX7J6AQRPYRGPAX74AT/
Re: Could LightDM be bad?? (LONG)
Tim: >> There are programs that just don't terminate every time when I log >> out. Various system/desktop daemons, sometimes web browsers. Patrick O'Callaghan: > Possibly unrelated, but I sometimes - not always - find that after > updating (using dnf with the tracer plugin) I'm advised to restart my > session, then on logging out and in I'm suddenly forced out again > after a short time, usually less than a minute. Software updates aren't part of my problem's situation. It can do it when I haven't done any updates since the last reboot. -- [tim@localhost ~]$ uname -rsvp Linux 4.16.7-100.fc26.x86_64 #1 SMP Wed May 2 21:45:56 UTC 2018 x86_64 Boilerplate: All mail to my mailbox is automatically deleted. There is no point trying to privately email me, I only get to see the messages posted to the mailing list. You can't have equality AND special treatment. ___ 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/message/ARMTLN7TEALV5OXZBUDVBRE5CVJR2I7G/
Re: Enable mDNS name (.local) resolution on Fedora 28
On Mon, 21 May 2018 20:11:56 +0200 Marek Howard wrote: > I don't know what authselect is (yet). I don't really know either, but I tend to suspect it is only run once when you install, or later if the sysadmin explicitly invokes it. It is apparently a replacement for "authconfig" which I also never heard about (or needed to know about because it must have worked much better). I had to replace a couple of pam config files to get NIS login working: https://bugzilla.redhat.com/show_bug.cgi?id=1575297 ___ 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/message/7BN4DWSBJC37ED6Q4DIYEJESYABCQE3S/
Enable mDNS name (.local) resolution on Fedora 28
Hi, I've just installed Fedora 28 and I wanted to make it discoverable on my local network via mDNS. I'm using Avahi to resolve .local names of my ArchLinux and Ubuntu boxes. To make it work, I've installed and started avahi daemon on both boxes and slightly modified 'host:' line in /etc/nsswitch.conf (with the help of ArchWiki) to hosts: files mymachines mdns_minimal [NOTFOUND=return] resolve [!UNAVAIL=return] dns myhostname However, on Fedora 28, the header of the aforementioned file has the following at the top # Generated by authselect on Tue May 21 10:25:11 2018 # Do not modify this file manually. So I guess my changes would be overwritten at some future time when authselect will be run by some daemon. I started avahi-daemon.service but name resolution of .local hostnames, current machine hostname to be precise (pluto.local), doesn't work. # hostname pluto # ping pluto.local ping: pluto.local: Name or service not known I've also tried # systemctl disable firewalld before running commands above. I don't know what authselect is (yet). I tried to Google it, ended up at SSSD documentation and now I'm more confused than when I started. It seems these tools/services are intended for enterprise environments, not for my home, but I don't dismiss it, partly because I want to keep my Fedora as it was designed. How can I enable mDNS name resolution? I want to be able to resolve mDNS names of other machines on local network as well as being able to connect from these machines via Fedora's host mDNS name. Thank you. ___ 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/message/7FJYUPCMQLAGCSLLPXNEUOHAHP67NM2B/
Re: battery discharging whilelaptop powered off?
On Fri, May 18, 2018 at 04:14:44PM -0600, Chris Murphy wrote: > state: fully-charged > warning-level: none > energy: 27.7816 Wh > energy-empty:0 Wh > energy-full: 27.7816 Wh > energy-full-design: 38.115 Wh > energy-rate: 0 W > voltage: 8.648 V > percentage: 100% > capacity:72.8889% > technology: lithium-ion > > > energy-full did bounce back ~0.5, but basically in one day the > energy-full/capacity% dropped nearly 10%. Sounds like a sick battery > or something. I'd try retraining the battery for longer run-time until empty: I described the procedure to do that a few weeks ago: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/Y5IBA2N3KVBJKOJ3ORY2BENQKR2K4B7D/ HTH, and good luck! Wolfgang ___ 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/message/PUVR5GB5ECSNQ4Q4GZXBWPMELUZSTVQJ/
Re: portable (really) Fedora on stick
Hi and thanks for all replies. The `dracut-config-generic` package did the job with Fedora 28. I'm actually building this for a non-technical person. What I did was: * install on stick with netinst fedora image (BIOS mode) * choose XFCE desktop * choose basic layout (without LVM) with ~20GB root partition ** remove flash partition ** create VFAT partition for sharing files with windows (make it first partition [*]) * install dracut-config-generic, codecs and VLC * rebuild initramfs * set uid= in fstab for the VFAT partition * link Documents, Pictures, etc. to the VFAT partition ** disable Firefox disk cache (about:config -> browser.cache.disk) [**] ** make locked memory for target user unlimited in limits.d/memlock.conf (default fedora limit might be reasonable for a server but not for a workstation) It looks and works pretty descent. Presently installing on a 32GB USB 3.0 stick. If said user likes the setup I'll recommend switching to an external SSD/NVMe. Thanks again and have fun! [**] Without removing FF disk cache youtube videos have been cutting out like crazy and data constantly being written to the stick. [*] I had only one issue. When I put stick into windows 7 it shows "disk f:" and asks me to format it. It didn't show the VFAT partition because it is third partition in the MBR. I had to use fdisk to just change partition numbers. Then boot with install CD in rescue mode to chroot into the system, then `grub2-mkconfig > /etc/grub2.cfg` and `grub2-install /dev/sdX`. [1] https://superuser.com/questions/400560/windows-7-doesnt-recognize-second-partition-on-removable-disk ja wrote on 04/24/18 11:30: On Mon, 2018-04-23 at 23:52 +0300, Aleksandar Kostadinov wrote: ja wrote on 04/23/18 20:28: On Mon, 2018-04-23 at 17:20 +0300, Aleksandar Kostadinov wrote: Hi, I'm reading documentation [1] for Fedora on a USB stick. The only option to have a portable fedora on a stick seems to be by creating an overlay FS and this certainly leads to getting out of disk space at some point. I would really like to create Fedora on USB that I can plug anywhere and work off it. I was thinking that perhaps I can just install regular fedora on a USB stick like I would do on a hard drive. Then it can be updated and used just like any other Fedora machine. Perhaps disable persistent logging and swap so that flash memory doesn't wear out. One issue I presently know about is dracut. It creates by default images that only support a specific hardware. i.e. if I install kernel on a machine with an nforce disk controller, it will put in intird only that module thus Fedora will not boot on a machine with AHCI controller. Maybe this wouldn't matter when all things are on the USB drive but then can there be a problem with different USB controller modules? I was wondering if anybody tried that and has tips for greated portability. Thank you, Aleksandar I have been doing this for several years, currently F27, but only as a recovery Stick. I just do a standard install but use a custom disk layout using ext4 / partition - no LMV. gdisk -l /dev/sda Number Start (sector)End (sector) Size Code Name 12048 1026047 500.0 MiB EF00 EFI System 2 1026048 1028095 1024.0 KiB EF02 BIOS boot partition 3 1028096 3125247 1024.0 MiB 8300 Linux filesystem 4 312524819902463 8.0 GiB 8200 Linux swap 51990246461800414 20.0 GiB8300 Linux filesystem I have recently been using a Corsair GT 32GB stick Thanks a lot for the tip! I am also planning to start with a 32GB USB 3.0 stick. It looks like though that you are having EFI and BIOS mode both supported. Would you share how did you achieve it? I usually pre-format SSD's, sticks with a "standard" partition layout using gdisk before installing Fedora. This was it for this stick - "BIOS" & "EFI" boot partitions. All my machines have compatibility mode for booting. F27 was installed on this stick on a machine with EFI but "BIOS" mode was selected/forced during installation. I have just re-tested the stick It will boot on a 10 year old laptop with dual AMD Althon & only USB2. Also on Intel i7-6700K machine using "BIOS" mode. John ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org ___ 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/message/6TDLMFYWDAKN332ZHU2VEUZQAMQOWHWR/
Re: Gnome keyring and ssh passphrase
On 05/21/2018 06:37 AM, Gianluca Cecchi wrote: I was in Mate up to some days ago and the ssh passphrase was in need to be inserted only once in mater-terminal, because I had this in my .bashrc (I think) export SSH_ASKPASS="/usr/bin/ksshaskpass" Not exactly. The "askpass" setting only controls which UI will be used to prompt you for your passphrase when adding a key to the agent. It doesn't determine whether or not an agent is running. In GNOME, you should see a process named gnome-keyring-daemon, and a child process named ssh-agent. The agent process is the one that holds your keys in memory temporarily and handles public key authentication. Now I see that my gnome-terminal continues to ask my passhprase without giving chance to save it into its keyring. It seems there is a bug in the current release of gnome-keyring which will cause you to be unable to use any ssh keys if you have one or more "bad" public keys in ~/.ssh. Check that directory for any file whose name ends in ".pub". If you find any that don't have a matching private key, or any in the old RSA1 format, move them to a different directory or delete them. If you don't see any bad public keys, check the output of the "echo $SSH_AUTH_SOCK" command in a terminal, as well as the output of "ssh-add -l". ___ 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/message/ZCZ5YNCWJW3UUGG635GWG5DIUGC6RFEC/
Re: Could LightDM be bad?? (LONG)
On Mon, 2018-05-21 at 16:09 +0100, Patrick O'Callaghan wrote: > On Mon, 2018-05-21 at 10:06 +0930, Tim via users wrote: > > There are > > programs that just don't terminate every time when I log out. Various > > system/desktop daemons, sometimes web browsers. > > Possibly unrelated, but I sometimes - not always - find that after > updating (using dnf with the tracer plugin) I'm advised to restart my > session, then on logging out and in I'm suddenly forced out again after > a short time, usually less than a minute. > > (Also, and only in this specific situation, Firefox forgets all the > windows it had open except one, but I had the same problem with > Chrome). > > On logging in *again*, everything is fine. It's as if the session > manager isn't waiting long enough for things to terminate gracefully > before presenting the login screen, then when they do terminate it > panics. I haven't managed to narrow it down yet. Forgot to mention that this is with KDE and SDDM. 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/message/KIZNMCL6733ZO664VSQM67X2YRI7IBD5/
Re: Could LightDM be bad?? (LONG)
On Mon, 2018-05-21 at 10:06 +0930, Tim via users wrote: > There are > programs that just don't terminate every time when I log out. Various > system/desktop daemons, sometimes web browsers. Possibly unrelated, but I sometimes - not always - find that after updating (using dnf with the tracer plugin) I'm advised to restart my session, then on logging out and in I'm suddenly forced out again after a short time, usually less than a minute. (Also, and only in this specific situation, Firefox forgets all the windows it had open except one, but I had the same problem with Chrome). On logging in *again*, everything is fine. It's as if the session manager isn't waiting long enough for things to terminate gracefully before presenting the login screen, then when they do terminate it panics. I haven't managed to narrow it down yet. 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/message/TXFRJUBQA4LJ6SPRLGIRV5EBLVQM7E3I/
Re: F27 problems with pam?
On Mon, May 21, 2018 at 3:36 PM, wrote: > > Hi. > > On Thu, 17 May 2018 10:19:52 -0700 stan wrote: > > > On Thu, 17 May 2018 10:54:57 +0200 > > Gianluca Cecchi wrote: > > >> Now (I'm in F28) it is simply sufficient to re-enable gdm and > >> connectusing Gnome as DE to see that all is ok: > >> - logout/shutdown buttons without problems (previously a logout > >> originated an automatic relogin...) > >> - switch wifi on/off and other components (such as external usb disks) > >> without getting authorization errors > >> - audio adapter is seen ok with its analog and hdmi settings (and it > >> works too... ;-) > > >> Possibly gdm in its start enables some permission for normal users > >> that lightdm (at least in latest updates) doesn't provide? > > I don't think it's that. See below. > > We are using lightdm and noticed also this problem. > So I'm not alone... Perhaps I didn't express clear enough. With lightdm I had the problem (as you confirmed you had too) With gdm I don't have the problem at all I found that the culprit is the RPM pam-kwallet-5.12.5-3.fc27: if you > erase it this problem disappear. You indicated this RPM in your initial post. > I can try and verify if it is the same for my environment In the mean time I took the occasion to switch back again to gdm as DM and gnome-session as DE I have to say that it seems more usable and less cpu consuming as in the time when I abandoned it (especially gnome-shell process that often became mad...) Also, after disabling tracker related things (see the other thread), it seems to me that all in all this configuration in F28 on my laptop (Asus U36SD) consumes less (battery lasts more) than the previous F27+lightdm+Mate DE I will continue to test and eventually switch again if not satisfied. The important is to preserve the power of choice and ability to change if needed ;-) > > It is safe to suppress the pam_kwallet RPM since it fails anyway to > spawn kwalletd and no other RPM depends ont it. > > Nice side effect for an optional module :-( > > Indeed! Thanks for your comments and help Gianluca ___ 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/message/4YJSDVXBFH4X3E3ZLI2CM5EXG6D2PJ2I/
Gnome keyring and ssh passphrase
Hello, I'm starting here in F28 to use gnome session again, after some Fedora versions... I was in Mate up to some days ago and the ssh passphrase was in need to be inserted only once in mater-terminal, because I had this in my .bashrc (I think) export SSH_ASKPASS="/usr/bin/ksshaskpass" Now I see that my gnome-terminal continues to ask my passhprase without giving chance to save it into its keyring. I read this https://wiki.gnome.org/Projects/GnomeKeyring/Ssh but I haven't completely understood it (if it is current) It seems gnome-keyring-daemon is running [g.cecchi@ope46 ~]$ ps -ef|grep keyr g.cecchi 1972 1 0 08:44 ?00:00:13 /usr/bin/gnome-keyring-daemon --daemonize --login g.cecchi 16480 14954 0 15:11 pts/800:00:00 grep --color=auto keyr [g.cecchi@ope46 ~]$ but is there any other setting to do not to insert every time my passhrase? Thanks, Gianluca ___ 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/message/HYFN3ZTMJI6QQ6JLXKXL6RXFIDO5OFBE/
Re: F27 problems with pam?
Hi. On Thu, 17 May 2018 10:19:52 -0700 stan wrote: > On Thu, 17 May 2018 10:54:57 +0200 > Gianluca Cecchi wrote: >> Now (I'm in F28) it is simply sufficient to re-enable gdm and >> connectusing Gnome as DE to see that all is ok: >> - logout/shutdown buttons without problems (previously a logout >> originated an automatic relogin...) >> - switch wifi on/off and other components (such as external usb disks) >> without getting authorization errors >> - audio adapter is seen ok with its analog and hdmi settings (and it >> works too... ;-) >> Possibly gdm in its start enables some permission for normal users >> that lightdm (at least in latest updates) doesn't provide? I don't think it's that. See below. We are using lightdm and noticed also this problem. > It's strange that a desktop manager would affect this, since it is > the desktop that performs the actions that are having problems. This is normal since those actions rely on having a proper session/seat defined to be authorized by polkit and that is the desktop manager that setup that. I found that the culprit is the RPM pam-kwallet-5.12.5-3.fc27: if you erase it this problem disappear. You indicated this RPM in your initial post. With pam-kwallet installed, the journal shows: lightdm[10869]: pam_kwallet5(lightdm:session): pam_kwallet5: final socket path: /tmp/kwallet5_fm.socket lightdm[10869]: pam_kwallet5(lightdm:session): pam_kwallet5-kwalletd: Couldn't listen in socket lightdm[10869]: pam_kwallet5(lightdm:session): pam_kwallet5: Impossible to write walletKey to walletPipe lightdm[10869]: pam_kwallet(lightdm:session): pam_kwallet: pam_sm_open_session lightdm[10870]: pam_kwallet(lightdm:session): pam_kwallet: final socket path: /tmp/kwallet_fm.socket lightdm[10870]: pam_kwallet(lightdm:session): pam_kwallet-kwalletd: Couldn't listen in socket lightdm[10870]: pam_kwallet(lightdm:session): pam_kwallet: Impossible to write walletKey to walletPipe ### Fail to create session: lightdm[10870]: pam_systemd(lightdm:session): Failed to create session: Access denied lightdm[10870]: pam_unix(lightdm:session): session opened for user fm by (uid=1005) ### Fail to register in lastlog and btmp lightdm[10870]: pam_lastlog(lightdm:session): unable to open /var/log/lastlog: Permission denied lightdm[10870]: pam_lastlog(lightdm:session): unable to open /var/log/btmp: Permission denied It works with gdm since it doesn't include pam_kwallet in its pam configuration files (of course :-) ), unlike lightdm: /etc/pam.d/lightdm: auth substacksystem-auth -auth optionalpam_gnome_keyring.so -auth optionalpam_kwallet5.so -auth optionalpam_kwallet.so .. -sessionoptionalpam_gnome_keyring.so auto_start -sessionoptionalpam_kwallet5.so -sessionoptionalpam_kwallet.so sessioninclude system-auth I tried to put system-auth before the pam_kwallet* in the session part: nmcli works, but logout no. In this case the socket is put under /run/user/$UID that is created before, but still "Couldn't listen insocket" I haven't tried to put the pam_kwallet* last in the session part. sddm is perhaps subject to this bug since it includes also the pam_kwallet* modules. I haven't tested it. It is safe to suppress the pam_kwallet RPM since it fails anyway to spawn kwalletd and no other RPM depends ont it. Nice side effect for an optional module :-( -- francis ___ 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/message/IV24MZCXW4PIMKHSEBI75VRZKFM2HVL7/
Re: Updated info about disabling tracker related processes?
Il giorno lun, 21/05/2018 alle 10.57 +0200, Gianluca Cecchi ha scritto: > Just a confirmation: the last command is needed only to purge old > generated files/databases for that connected user, correct? Yes So in case of multiple users you need to run it for every one who has logged in before to purge all? Yes Thank! -- 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/message/PEIQ27QVWNDH4P4KVAKRKTYB2PSCY6Z2/
Re: Updated info about disabling tracker related processes?
On Sat, May 19, 2018 at 7:57 PM, Dario Lesca wrote: > Il giorno ven, 18/05/2018 alle 09.03 +0200, Gianluca Cecchi ha scritto: > > Any pointer about configuring and/or disabling it? > > > # Disable tracker... > > sudo -E dnf -y -C remove tracker-miners > > > sudo sed -i 's/X-GNOME-Autostart-enabled=.*/X-GNOME-Autostart-enabled=false/' > /etc/xdg/autostart/tracker-store.desktop > > > yes|LANG=C tracker reset --hard > > > Hope this help > > Thanks! This way seems to work good in F28. Just a confirmation: the last command is needed only to purge old generated files/databases for that connected user, correct? So in case of multiple users you need to run it for every one who has logged in before to purge all? Gianluca ___ 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/message/BOY5OCKVBCJ5JD3DIEBEZYMHI3UANUO3/
