Re: F38 and new GDM behavior
Jeffrey Walton wrote: >After 15 minutes of cleanup GDM suspended the machine with an active >SSH connection. I was bitten by this too. Left my system logged in to a GNOME desktop carrying out some backups, went out for a walk, came back to find the machine unresponsive. As you say, this is new in F38, though apparently pristine GNOME has had this misfeature for a while. There's a write up here: https://discussion.fedoraproject.org/t/gnome-suspends-after-15-minutes-of-user-inactivity-even-on-ac-power/79801 "User inactivity" is a poor criterion for suspending a machine. Ron ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Fedora 37: libvirt/qemu/kvm not work property with kernel 6.1.8-200.fc37.x86_64
Dario Lesca wrote: >When I try to install a new VM with virt-manager, (es Rocky Linux 9 or >Fedora 37 WS) from a verified ISO file, the live setup do not start and >the installation procedure is blocked before displaying the graphical >environment. ... >Is this a know issue? There is an issue which seems to match your description. See this bug report: https://bugzilla.suse.com/show_bug.cgi?id=1206848 As you've found, going back to a 6.0 kernel avoids the problem. There's a workaround for 6.1 kernels in one of the comments on the bug report: echo never > /sys/kernel/mm/transparent_hugepage/enabled The bug has been fixed in the 6.1.9 stable update, though that only came out yesterday so it may be a few days before it becomes available for Fedora. Cheers, Ron ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: kvm vs firefox issue?
Eyal Lebedinsky wrote: >This started only recently (kernel 6.0.18 or 6.1, or another update?) > >Is there a known problem. There is. It's in the 6.1 kernel and it isn't yet fixed in Fedora. (Not even in the 6.1.8 kernel currently in testing.) Here's a SuSE bug report: https://bugzilla.suse.com/show_bug.cgi?id=1206848 which suggests: echo never > /sys/kernel/mm/transparent_hugepage/enabled as a workaround until new kernels are available. I've confirmed that this seems to work with a Fedora 6.1 kernel. Cheers, Ron ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Launching Nautilus makes F37 'hard crash'
Frederic Muller wrote: >This is happening with the latest 2 kernel versions (just updated and >the same is happening). I thought I wouldn't be the only one and the bug >would magically disappear... well it seems not. It's probably this: https://bugzilla.kernel.org/show_bug.cgi?id=216895 The latest word is that it should be fixed in the 6.0.18 kernel: https://bodhi.fedoraproject.org/updates/FEDORA-2023-39b55235fc Ron ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: OpenVPN breakage
There's a bug report: https://bugzilla.redhat.com/show_bug.cgi?id=2093069 which includes a link to a test build of OpenVPN which fixes the problem I was having. Ron ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
OpenVPN breakage
Today OpenVPN was updated from 2.5.6-1 to 2.5.7-1 and my VPN connection broke. The log says: nm-openvpn[8655]: --cipher is not set. Previous OpenVPN version defaulted to BF-CBC as fallback when cipher negotiation failed in this case. If you need this fallback please add '--data-ciphers-fallback BF-CBC' to your configuration and/or add BF-CBC to --data-ciphers. nm-openvpn[8655]: OpenVPN 2.5.7 x86_64-redhat-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on May 31 2022 nm-openvpn[8655]: library versions: OpenSSL 3.0.2 15 Mar 2022, LZO 2.10 nm-openvpn[8655]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts nm-openvpn[8655]: Cipher BF-CBC not supported nm-openvpn[8655]: Exiting due to fatal error 2.5.6-1 says almost exactly the same, apart from the last two lines, and doesn't break. Adding 'cipher=AES-256-GCM' to the NetworkManager keyfile for the VPN got it working again. The advice about 'data-ciphers-fallback' and 'data-ciphers' is bogus because NetworkManager doesn't know about those options. Not happy, Ron ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: resurrecting old laptops
jim wrote: >I would welcome other distro suggestions for tired old hardware I'm using CentOS 7 on an Asus Eee PC 701. RHEL 7 doesn't have an i686 version but CentOS supports it as an altarch. Advantages: - it has all that familiar Red Hat goodness; - unlike CentOS 8 it'll be supported until RHEL 7 EOL, so another two years. Ron ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: wifi connection problem.
François Patte wrote: >Is it a known bug and what causes this dysfonction? I understand it's a problem with the kernel. If you still have kernel-5.16.14-200.fc35 installed booting with that should avoid the issue. The forthcoming kernel-5.16.18-200.fc35 might have the fix. Cheers, Ron ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
The restorecon problem is coming back
On 6th May an update to selinux-policy for Fedora 32 (3.14.5-38.fc32) caused all filesystems to be relabelled. In my case this took over twelve hours. I was not happy. It appears the developers have a workaround for the problem but the update that applies it will cause all filesystems to be relabelled if you already have the borked 3.14.5-38.fc32 update. The new update is currently in updates-testing and will no doubt be making its way onto our systems soon enough. The developers say[1]: Please note updating from the previous package version selinux-policy-3.14.5-38.fc32 will have all filesystems relabeling as a result which cannot be prevented. If relabeling takes a lot of time, consider unmounting some filesystems, updating manually, postponing the update to later. You have been warned. Ron [1] https://bodhi.fedoraproject.org/updates/FEDORA-2020-886cc9af08 ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: night light mode
Alessio Ciregia wrote: >I don't know, but I've noted that if geolocalization is disabled in privacy >settings, automatic (sunset to sunrise) night light doesn't work. And it >sounds like a bug, or at least I don't remember such behavior on F28 There have been interactions between night light and geolocation since it was introduced. Because sunrise/sunset times depend on location it's sort of inevitable. To have night light use sunrise/sunset when geolocation is disabled you can configure it by hand: gsettings set org.gnome.settings-daemon.plugins.color night-light-last-coordinates '(40.0, 10.0)' gsettings set org.gnome.settings-daemon.plugins.color night-light-enabled true gsettings set org.gnome.settings-daemon.plugins.color night-light-schedule-automatic true The coordinates are decimal latitude/longitude. The third setting is just for completeness, it's on by default. Ron ___ 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: what is wrong with dnf?
Matthew Miller wrote: >If you can find a reproducer, a bug report for this would be helpful. I think this one covers the issue: https://bugzilla.redhat.com/show_bug.cgi?id=1648274 As noted there, there's no need to muck about with the cache or the --refresh option. Simply running 'dnf update' twice makes things work as they should. Ron ___ 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: Debian vs Fedora
Matthew Miller wrote: >While I can't disagree with the general sentiment, I certainly hope Fedora >isn't being pigeonholed into "bleeding edge". Fedora also certainly "just >works". Except when it doesn't. In the week since F29 was released I've been bitten by cron not working (1639381) and web pages not rendering (1646150). There's a tension between "bleeding edge" and "just works". I think it's fair comment that Fedora tends towards the "bleeding edge". Ron ___ 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: GnuCash's new reconciliation behavior
Sam Varshavchik wrote: >Ron Yorston writes: >> On my system with gnucash-3.1-3 transactions in the reconciliation dialog >> appear in some order which defies logical anaylsis. > >This is nothing more than change for the sake of change, No, I think it's just a bug. I couldn't see anything in GNOME Bugzilla related to the sort order of the reconciliation dialog. After rummaging through their git repo, though, I did find this commit: https://github.com/Gnucash/gnucash/commit/836705f98087ec7bf9418cef71af939fcff6a393 which refers to the not-obviously-related bug 795101 'Scroll Bar in Reconcile Window Floats in and covers the check boxes': https://bugzilla.gnome.org/show_bug.cgi?id=795101 It seems they changed the order of the columns in the dialog but not the number of the column that was being sorted by default. So transactions are being sorted by their reconciliation status instead of date. The dates are probably just being ordered by however they come out of the database. The fix should be in 3.2. Ron ___ 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/HMMUNGVDYJ22VYUGY3BY6IMEKVDLOKGU/
Re: GnuCash's new reconciliation behavior
Sam Varshavchik wrote: >It seems that after clicking a transaction, to mark it as reconciled, what >happens now is that not only does the little checkbox next to the >transaction gets set, but the entire transaction gets shuffled to the bottom >of the transaction list, so that all reconciled transactions always appear >after the unreconciled ones. Were the transactions originally sorted in date order, as they used to be? On my system with gnucash-3.1-3 transactions in the reconciliation dialog appear in some order which defies logical anaylsis. Ron ___ 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/IDRKAQMSDX635V36K5TB6H3R5S55YBYB/
Re: Scroll Bars with Arrows Wanted
Jonathan Ryshpan wrote: >On Wed, 2018-01-24 at 12:13 -0800, Joe Zeff wrote: >> I've always found that clicking in the scroll bar area will move it >> in >> the direction of the mouse arrow. Doesn't that work for you? > >Only too well! Clicking on the scroll bar area can move the window >many columns. For a window with 29 columns this is too much; I want to >scroll one column. Just some additional information, in case it's of use to anyone: It used to be that clicking in the trough of a scrollbar would move by a page. GTK3 defaults to moving the slider to the point of the click. To get the old behaviour back create or edit this file: ~/.config/gtk-3.0/settings.ini so it contains: [Settings] gtk-primary-button-warps-slider=0 Ron ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Delta RPMs -
I've subscribed to the infrastructure mailing list and have asked there. Ron ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Delta RPMs -
Gordon Messmer wrote: >I don't see a "drpms" directory in the fedora 26 "updates" directory. >It's still present for f25 and f27. I haven't seen any notices about >that, so it might be a failure. I'm asking in the #fedora IRC >channel. I'll file a bug later if needed. Did you get any response? I've just updated two F26 machines and not a single DRPM was used. Ron ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Hundreds of kernel crash messages after Fedora 26 upgrade. We're sorry, it looks like BOOT_IMAGE=/boot/vmlinuz-4.11.9-300.fc26.x86_64 crashed.
Sudhir Khanger wrote: >I restarted the system. And also tried restarting abrtd. In that case I'm out of ideas. Sorry, Ron ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Hundreds of kernel crash messages after Fedora 26 upgrade. We're sorry, it looks like BOOT_IMAGE=/boot/vmlinuz-4.11.9-300.fc26.x86_64 crashed.
Sudhir Khanger wrote: >That didn't help. I am continuing to see the abrt notification. Did you restart abrtd? systemctl restart abrtd Ron ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Hundreds of kernel crash messages after Fedora 26 upgrade. We're sorry, it looks like BOOT_IMAGE=/boot/vmlinuz-4.11.9-300.fc26.x86_64 crashed.
Sudhir Khanger wrote: >Jul 15 10:35:05 workstation abrt-dump-journal-oops[1256]: Reported 2 kernel >oopses to Abrt >Jul 15 10:35:06 workstation abrt-server[5959]: Can't find a meaningful >backtrace for hashing in '.' >Jul 15 10:35:06 workstation abrt-server[5959]: Option >'DropNotReportableOopses' is not configured >Jul 15 10:35:06 workstation abrt-server[5959]: Preserving oops '.' because >DropNotReportableOopses is 'no' I had a similar problem. You can, at least, make abrt shut up by adding the line DropNotReportableOopses = yes to the file /etc/abrt/abrt.conf. That doesn't tackle the underlying problem, though. In my case the issue seems to be the one in this bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1408858 which is about the accelerometer on some Acer laptops. Disabling the related service stopped the oopses: systemctl stop iio-sensor-proxy.service systemctl mask iio-sensor-proxy.service Your problem may be different, though. Ron ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Umount USB
Chris Murphy wrote: On Tue, Aug 11, 2015 at 9:24 AM, Patrick Dupre wrote: F22 gnome, this option is just missing, it was here in F20. It's in Fedora 22 Gnome also. I'd say you either have something broken in the installation/upgrade, or the removable isn't actually mounted, or you've found a bug related to the specific partitioning/volume format of the removable. I think you're talking about different things. Chris's screenshot shows that Nautilus still has the ability to unmount removable devices. Patrick is referring to the icon that used to appear in the notification area when a removable device was mounted and which let you unmount it. In GNOME Shell 3.16 notifications have moved to the top of the screen and no longer include persistent icons for mounted devices. The old scheme provided a pointy-clicky way to unmount a device without having to start Nautilus. Ron -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: dnf update vs Software Udpates
Gordon Messmer wrote: Use dnf repolist -v to find out, in the future. It will print the date from the metadata you have, and the URL of the mirror from which it was retrieved. OK, today 'dnf repolist -v' tells me: fedora: using metadata from Wed Jul 22 08:38:59 2015. rmy: using metadata from Wed Jul 22 08:38:59 2015. updates: using metadata from Wed Jul 22 08:54:38 2015. Last metadata expiration check performed 21:22:45 ago on Wed Jul 22 08:54:38 2015. Repo-id : fedora Repo-updated : Sat May 23 11:23:20 2015 Repo-expire : 172,800 second(s) (last: Wed Jul 22 08:38:59 2015) Repo-id : rmy Repo-updated : Sat Jun 20 19:40:40 2015 Repo-expire : 172,800 second(s) (last: Wed Jul 22 08:38:59 2015) Repo-id : updates Repo-updated : Tue Jul 21 06:47:56 2015 Repo-expire : 21,600 second(s) (last: Wed Jul 22 08:54:38 2015) The fedora and rmy repos both have the default metadata_expire of 48 hours; updates has 6 hours, as configured in fedora-updates.repo. fedora and rmy are still within their metadata_expire timeout; updates has expired. Running the same commands as yesterday: [root@vulcan rmyf22]# dnf check-update Last metadata expiration check performed 0:00:00 ago on Thu Jul 23 06:19:10 2015. [root@vulcan rmyf22]# dnf --refresh check-update Fedora 22 - x86_64 - RMY repository 78 kB/s | 6.0 kB 00:00 Last metadata expiration check performed 0:00:00 ago on Thu Jul 23 06:20:06 2015. [root@vulcan rmyf22]# rm -rf /var/cache/dnf/x86_64/22/updates* [root@vulcan rmyf22]# dnf check-update Fedora 22 - x86_64 - Updates946 kB/s | 12 MB 00:13 Last metadata expiration check performed 0:00:11 ago on Thu Jul 23 06:23:32 2015. [root@vulcan rmyf22]# What immediately seems odd is that 'dnf --refresh check-update' pulled in a new version of the rmy metadata (which hasn't expired) but not the updates metadata (which has). Forcibly removing the updates metadata causes a download but I get the same version as yesterday (the one from Jul 21 06:47:56 2015) so there are no new updates. Actually, every time I run 'dnf --refresh check-update' the metadata for the rmy repo is downloaded. Maybe that's because the rmy repo has an 'ftp://' URL so dnf can't use an 'if-modified-since' request to see if it's changed. I wonder if that's confusing 'dnf --refresh'? Ron -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: dnf update vs Software Udpates
Ron Yorston wrote: What immediately seems odd is that 'dnf --refresh check-update' pulled in a new version of the rmy metadata (which hasn't expired) but not the updates metadata (which has). Of course, today it didn't need to download new updates metadata because it hadn't changed. That wasn't the case yesterday, though. Ron -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: dnf update vs Software Udpates
Suvayu Ali wrote: That said, I sometimes do not understand what's the harm in getting updates few hours later. dnf already tells you how old the metadata is when it starts, you can choose to get the latest metadata if it is too old. So what's the big deal? I certainly get the impression that dnf tells me about updates less frequently than yum did. It also seems to pull in metadata less frequently. In fedora-updates.repo I have: metadata_expire=6h. I also have the dnf-makecache.timer 'masked'. It's more than 6 hours since I last ran dnf but: [root@vulcan rmyf22]# dnf check-update Fedora 22 - x86_64 - RMY repository 131 kB/s | 6.0 kB 00:00 Last metadata expiration check performed 0:00:00 ago on Wed Jul 22 08:38:32 2015. [root@vulcan rmyf22]# No updates. It pulled in metadata for my private repo but not fedora-updates. So is it really telling me how old the metadata is? The message just refers to the last time an expiration check was performed. Does that mean the metadata was up to date as of 0:00:00 ago? Because, as we shall see, it clearly wasn't. Let's try the --refresh option: [root@vulcan rmyf22]# dnf --refresh check-update Fedora 22 - x86_64 - RMY repository 113 kB/s | 6.0 kB 00:00 Last metadata expiration check performed 0:00:00 ago on Wed Jul 22 08:39:01 2015. [root@vulcan rmyf22]# Still no updates. Time for a bigger hammer (don't try this at home or offer it as advice to newbies): [root@vulcan rmyf22]# rm -rf /var/cache/dnf/x86_64/22/updates* [root@vulcan rmyf22]# dnf check-update Fedora 22 - x86_64 - Updates774 kB/s | 12 MB 00:16 Last metadata expiration check performed 0:00:16 ago on Wed Jul 22 08:40:02 2015. environment-modules.x86_64 3.2.10-16.fc22updates ... Plus 55 other updates. What's going on? Ron -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: dnf update vs Software Udpates
Matthew Miller mat...@fedoraproject.org wrote: On Wed, Jul 22, 2015 at 07:20:11PM +0100, Ron Yorston wrote: I certainly get the impression that dnf tells me about updates less frequently than yum did. It also seems to pull in metadata less frequently. Keep in mind that we only push updates once per day *anyway*. OK, but that's independent of the client being used. Both yum and dnf see the same updates, but dnf doesn't seem to be as quick to pass them on. Of course, if you're mixing in private repos or other rpm providers, there may be different policies. Sure, different repos have different policies but why would that affect Fedora updates? The commands I quoted clearly show that there was newer metadata that dnf ignored until I blew away the old cache. Ron -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Firefox 34 bookmark sidebar scrolling has changed
Tony Nelson wrote:
Thank you. Do you know of any settings for other Gnome3 changes I
might wish to undo?
Well, I don't know what *you* might want to undo, but here's the script
I run after installing F20. Some of the settings can be modified in
gnome-tweak-tool but I find it more convenient to gather them all into
one place.
Ron
gsettings set org.gnome.shell.overrides edge-tiling false
gsettings set org.gnome.shell.overrides dynamic-workspaces false
gsettings set org.gnome.shell.overrides attach-modal-dialogs false
gsettings set org.gnome.shell always-show-log-out true
gsettings set org.gnome.shell.overrides button-layout :minimize,maximize,close
gsettings set org.gnome.settings-daemon.plugins.updates auto-download-updates
false
gsettings set org.gnome.settings-daemon.plugins.updates active false
gsettings set org.gnome.desktop.wm.preferences mouse-button-modifier 'Alt'
gsettings set org.gnome.mutter auto-maximize false
gsettings set org.gnome.settings-daemon.plugins.xsettings overrides
{'Gtk/ShellShowsAppMenu': 0}
gsettings set org.gnome.desktop.interface clock-show-date true
gsettings set org.gnome.desktop.wm.preferences focus-mode sloppy
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
Re: Firefox 34 bookmark sidebar scrolling has changed
Fred Smith wrote: I've just done a Centos-7 install on one of my netbooks, and then I installed the Mate desktop so I wouldn't have to fume and curse Gnome. Mate is much more friendly. but I noticed that some few programs even in Mate still use the silly new scrollbar behavior, and adding that entry (in fact, creating the file 'cause it wasn't there) doesn't help. I've had a quick look at Mate in F20 but didn't spot anything with the new scrollbar behaviour. Can you point to any examples? Ron -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Firefox 34 bookmark sidebar scrolling has changed
Tim ignored_mail...@yahoo.com.au wrote: I noticed the same thing with Evolution, long ago, that I can't simply page up and down by clicking above or below the scroll bar, any more. It jumps to what's essentially a random spot, since you have no way to actually pick a specific part of the message list that you want to see. You're pretty screwed if you don't have a mouse wheel and you want to page through things. It's due to a change in GTK+3. Maybe Firefox has inherited this. I preferred the old behaviour. To get the old behaviour back edit ~/.config/gtk-3.0/settings.ini and add this: [Settings] gtk-primary-button-warps-slider = 0 Ron -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: frippery extension in fedora 20
Patrick Dupre wrote: I cannot update frippery extensions (application menu, etc..) in fedora 20 I cannot remove them either. The Frippery extensions are available for F20, as a tar file or RPM from my website[1] or via the GNOME Shell Extensions website[2]. How did you originally install them? Because how you update or remove them depends on how you first got them. Ron [1] http://intgat.tigress.co.uk/rmy/extensions/index.html [2] https://extensions.gnome.org/ -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: gnome-classic-session
Robert Moskowitz wrote: I am looking through what extensions are available for gnome via yumex, and I find gnome-classic-session. I haven't tried gnome-classic-session in F20 yet though I have looked at it in F19. The one feature I missed is the ability to put application launchers in the top panel. Happily my Frippery Panel Favorites extension[1] works in classic mode as well as full-on GNOME 3 mode. You might also want to look at the other Frippery exensions[2]. I've been maintaining them since GNOME 3.0 to provide something like what classic mode now does. Ron [1] https://extensions.gnome.org/extension/4/panel-favorites/ [2] http://intgat.tigress.co.uk/rmy/extensions/index.html -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Systemd Freezing on NetworkManager or Display Manager
Rex Dieter rdie...@math.unl.edu wrote: Mark Bidewell wrote: I am using Fedora 19 on older hardware, and about half the time systemd freezes on boot. Typically the console messaging is pointing at Network Manager but occasionally kdm or gdm. I can switch to another console and log in and network is up and I can enter X. Any ideas how to debug this? You might be hitting this, https://bugzilla.redhat.com/show_bug.cgi?id=967521 Or possibly this: https://bugzilla.redhat.com/show_bug.cgi?id=1013867 Ron -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: GNOME Classic Extensions
Jorge Fábregas wrote: Thanks for the reminder Tim. It helps but I stll can't find it. It seems the Frippery Bottom Panel extension would do it but it doesn't work with GNOME 3.8. I'm the author of the Frippery extensions. The Bottom Panel should work with GNOME 3.8, though not in Classic mode. If it's not working for you I'd like to find out why. Ron -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Install Updates Restart on a laptop
Rahul Sundaram wrote: It isn't. This feature works by downloading all the updates beforehand I prefer to control when the download happens. This turns off the automatic download: dconf write /org/gnome/settings-daemon/plugins/updates/auto-download-updates false and then offering you the option in the menu to restart and install the updates in a special environment The new option is positioned at the bottom of the menu, where the shutdown option normally lives. I prefer to avoid the possibility of inadvertantly causing an update when I just meant to shut down: dconf write /org/gnome/settings-daemon/plugins/updates/active false Ron -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: F17 Gnome3 workspace names
Greg Woods wrote: Poked around a little, gsettings list-schema shows that the schema maybe should be org.gnome.desktop.wm.preferences, so I tried that: [greg@diamondage greg]$ gsettings set org.gnome.desktop.wm.preferences workspace-names ['Local','E-mail','Web','Virtual','Systems',Misc'] 44-45:unknown keyword There's a typo in the command: a missing single quote before Misc. It does work, and just last week I updated my Bottom Panel[1] Shell extension to display workspace names as tooltips. Ron [1] https://extensions.gnome.org/extension/3/bottom-panel/ -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: fedora 16 64 bits gnome shutdown button
Leonardo Silveira wrote: how do i add the shutdown button on gnome menu? My GNOME Shell Frippery[1] has an extension that makes shutting down the system work more like GNOME 2. In fact, it has a number of extensions to make things work more like they do in GNOME 2. Ron [1] http://intgat.tigress.co.uk/rmy/extensions/index.html -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Four Tweaks for Gnome 3
Lars E. Pettersson wrote: Sadly the things mentioned in the links earlier in the thread does not solve my issues fully. Have you tried my GNOME Shell frippery extensions? http://intgat.tigress.co.uk/rmy/extensions/index.html While you lot have been chattering here I've been busy releasing version 0.2.0: Jumping the shark. This includes a bottom panel approximating to the one in GNOME 2. If you're quick you can be the first to download it! Ron -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: RPM signing problems on Fedora 15?
Julian C. Dunn wrote: I just upgraded to F15 and now I'm having problems signing my custom RPMs. Am I losing my mind here: demeter:~/rpm/SPECS$ rpmbuild --sign twirssi.spec rpm: --addsign: No such file or directory ?? and demeter:~/rpm/SPECS$ file /home/staff/jdunn/rpm/RPMS/noarch/twirssi-2.5.0-1.fc15.noarch.rpm /home/staff/jdunn/rpm/RPMS/noarch/twirssi-2.5.0-1.fc15.noarch.rpm: RPM v3.0 bin i386/x86_64 demeter:~/rpm/SPECS$ rpm --addsign /home/staff/jdunn/rpm/RPMS/noarch/twirssi-2.5.0-1.fc15.noarch.rpm rpm: /home/staff/jdunn/rpm/RPMS/noarch/twirssi-2.5.0-1.fc15.noarch.rpm: No such file or directory WTF? Been there, done that. You need to install rpm-sign. Bugzilla #697435 Ron -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Comparison of Desktop Environments in F15?
Tim wrote: On Sun, 2011-05-15 at 12:28 -0400, Genes MailLists wrote: you're much better off throwing resources into an existing active project (whether its Gnome 3/shell, KDE, unity, lxde, etc etc). And so the attempt to pervert XFCE into Gnome 2 will begin... ;-p My plan is to pervert GNOME 3 into GNOME 2. http://intgat.tigress.co.uk/rmy/extensions/index.html Ron -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: OOo and delta RPM
Jonathan Dieter wrote: There's a bug in the push scripts where it only generates deltas against GA and not updates. So if you downgrade to GA OOo and then update you'd get deltas. Obviously *not* a good solution. We thought we'd fixed the bug, but obviously have missed something. We're investigating now. I've just installed another update to OOo and it still downloaded everything, not deltas. OOo is now excluded from update in my yum.conf. If this can't be fixed the maintainer should be a lot more cautious about pushing out updates to OOo. I'm sure I'm not alone in thinking that 100MB of updates about once a week is unacceptable. Think of the bandwidth. Ron -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
OOo and delta RPM
Is there a problem with openoffice.org and delta RPMs? I've just done a yum update on F14 and all the OOo packages were downloaded in their entirety, whereas about 30 others came in as deltas. And it's not like OOo is small. And this is the second update in a week. If it's going to carry on like this I'll exclude OOo from updates: I only use it once in a blue moon to examine documents in proprietary formats. Ron -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Recompiling VirtualBox kernel module [FAILED]
Greg Woods wrote: On Thu, 2010-04-08 at 15:34 -0500, Dennis Gilmore wrote: Im curious why you use virtualbox and not kvm/libvirt/virt-manager that are included by default in fedora? Im just trying to work out what is lacking in the default offerings that you go to a third party. I can't speak for the original poster, but for me, KVM is buggy, and doesn't work at all without hardware virtualization. On my Pentium 4 dual core desktop, KVM is so slow that it's useless. VirtualBox performs quite well. Likewise not presuming to speak for the OP. I don't use KVM because none of the machines I own supports hardware virtualisation. Excluding the stuff in the attic that would be two desktops, a laptop and three netbooks. On one of the desktops I use VMware Server and on one of the netbooks I use QEMU. I note that the OP is running an x86_64 kernel, but even that doesn't guarantee that they can use KVM. One of the machines I use here at work is an early Opteron. We have VMware Server on that. What's lacking from the default offerings is support for processors without hardware virtualisation. Ron -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
