Re: Fedora-26: KDE Scrollbars no longer have arrows at their ends

On Sun, 2017-07-30 at 14:06 -0700, Samuel Sieb wrote: > On 07/30/2017 01:41 PM, Tom Horsley wrote: > > I really wonder why they don't just get rid of the scrollbar > > completely. If you are looking at a big file and you so much > > as touch the scrollbar thumb it jerks to some new position > >

Re: Fedora-26: KDE Scrollbars no longer have arrows at their ends

On 30 July 2017 at 22:16, Jonathan Ryshpan wrote: > Just upgraded from f25 to f26. Most programs run better, but scrollbars no > longer have arrows at their upper and lower ends. System Settings used to > have a function to control this, but it seems to be gone, both in

Re: Fedora-26: KDE Scrollbars no longer have arrows at their ends

On 07/30/2017 01:41 PM, Tom Horsley wrote: I really wonder why they don't just get rid of the scrollbar completely. If you are looking at a big file and you so much as touch the scrollbar thumb it jerks to some new position hundreds or thousands of lines away, so you have to use the keyboard for

Re: Fedora-26: KDE Scrollbars no longer have arrows at their ends

On Sun, 30 Jul 2017 13:16:32 -0700 Jonathan Ryshpan wrote: > but scrollbars no > longer have arrows at their upper and lower ends I guess KDE is copying GTK which also seems to think arrows are anathema. I used to be able to put this in ~/.config/gtk-3.0/gtk.css: .scrollbar {

Fedora-26: KDE Scrollbars no longer have arrows at their ends

Just upgraded from f25 to f26. Most programs run better, but scrollbars no longer have arrows at their upper and lower ends. System Settings used to have a function to control this, but it seems to be gone, both in native KDE and Gnome applications. How are scrollbars now controlled in KDE?

Fedora 26 (Live) on Dell XPS 15 9560

Hello there, I'm trying to boot from a F26 Live CD (on a flash drive) on a brand new Dell XS 15 9560, but it sticks after "Started Virtualization daemon", then no move. The media is verified OK. I tried w/ "quiet" boot option, it gets more verbose, with "norhgb" but no luck. How could I get

Fedora 26 small issues with Asus Zenbook UX306U

Hi, I run Fedora 26 maybe since Alpha release on my Zenbook and in between Alpha and Beta I lost backlight control from gnome shell and /sys/class/backlight/intel_backlight/brightness. Then after 4.11.3 kernel I wasn't able to boot anymore, I discovered that switching to CSM mode solved

Re: Upgrade to Fedora-26 vs gpg download verification

Jonathan Ryshpan: > > gpg: WARNING: This key is not certified with a trusted signature! > > gpg: There is no indication that the signature belongs to the > > owner. > > Primary key fingerprint: E641 850B 77DF 4353 78D1 D7E2 812A 6B4B 64DA B85D Todd Zullinger: > The warning here is

Re: Upgrade to Fedora-26 vs gpg download verification

On Thu, 2017-07-27 at 14:41 -0400, Todd Zullinger wrote: > The warning here is telling you that gpg can't say with any certainty > that the key which made the good signature is a key you trust, because > the fedora key isn't signed by you or someone you have told gpg you > trust. > > This

Re: Upgrade to Fedora-26 vs gpg download verification

of it. Please excuse my extreme ignorance. ... $ gpg --verify-files *-CHECKSUM gpg: Signature made Fri Jul 7 08:13:35 2017 PDT using RSA key ID 64DAB85D ... gpg: Good signature from "Fedora 26 Primary (26) <fedora-26-prim...@fedoraproject.org>" What gpg is

Upgrade to Fedora-26 vs gpg download verification

gpg: key E372E838: "Fedora 25 Secondary (25) < fedora-25-second...@fedoraproject.org>" not changed gpg: key 64DAB85D: "Fedora 26 Primary (26) < fedora-26-prim...@fedoraproject.org >" not changed gpg: key 3B921D09: "Fedora 26 Seco

Re: Fedora 26 update causes crash on boot

at 12:13 AM Ed Greshko <ed.gres...@greshko.com> > wrote: > >> On 07/21/17 12:57, Robert Washbourne wrote: >> > Fedora 26 worked for a while but after selecting "restart and update" >> the laptop >> > now has this behavior (google photos link with vid): &

Re: Fedora 26 update causes crash on boot

On 07/21/17 12:57, Robert Washbourne wrote: > Fedora 26 worked for a while but after selecting "restart and update" the > laptop > now has this behavior (google photos link with vid): > > https://photos.app.goo.gl/7lTzF5h09iRDZOzT2 > > Also, going to a new session w

Fedora 26 update causes crash on boot

Fedora 26 worked for a while but after selecting "restart and update" the laptop now has this behavior (google photos link with vid): https://photos.app.goo.gl/7lTzF5h09iRDZOzT2 Also, going to a new session with ctrl + alt + F2 and running startx starts budgie desktop (crashes with

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.

On Sun, 16 Jul 2017 03:46:17 - "Sudhir Khanger" wrote: > Hi, > > I installed Ubuntu LTS because I can't have my system breaking every > six months. I had already wasted 24 hours and I couldn't waste > anymore. Thank you so much for your help. Yeah, you're probably

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.

Hi, I installed Ubuntu LTS because I can't have my system breaking every six months. I had already wasted 24 hours and I couldn't waste anymore. Thank you so much for your help. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe

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.

On Sat, 15 Jul 2017 13:28:54 -0400 Tom Horsley wrote: > I'd almost wonder if there was only one actual crash, and > abrt keeps telling you about the same one over and over again > because it failed to record that it already told you. That > would explain why running a new

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.

On Sat, 15 Jul 2017 10:04:45 -0700 stan wrote: > I know little about abrt, and why it would be generating these oops, > and why it isn't paying attention to its configuration file settings. I'd almost wonder if there was only one actual crash, and abrt keeps telling you about the same one over

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.

On Sat, 15 Jul 2017 04:18:07 - "Sudhir Khanger" wrote: > I just installed 4.11.10-300.fc26.x86_64. And the problem continues. > > I am getting the following messages every second. > > We're sorry, it looks like > BOOT_IMAGE=/boot/vmlinuz-4.11.9-300.fc26.x86_64

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.

Hi Ron, I restarted the system. And also tried restarting abrtd. ___ 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

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.

Hi, >DropNotReportableOopses = yes That didn't help. I am continuing to see the abrt notification. I have so far 10,000 entries in the ABRT window. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to

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

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.

Hi, I have just rebuilt the boot images after running the following command. dracut --regenerate-all --force Let's see how long it works. I have 6000+ unreportable errors in the ABRT window. Still no luck. Jul 15 10:35:05 workstation abrt-dump-journal-oops[1256]: Reported 2 kernel oopses to

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.

On 07/14/2017 09:18 PM, Sudhir Khanger wrote: I am getting the following messages every second. We're sorry, it looks like BOOT_IMAGE=/boot/vmlinuz-4.11.9-300.fc26.x86_64 crashed. Please contact the developer if you want to report the issue. We're sorry, it looks like

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.

. We're sorry, it looks like BOOT_IMAGE=/boot/vmlinuz-4.11.10-300.fc26.x86_64 crashed. Please contact the developer if you want to report the issue. We're sorry, it looks like a problem occurred. If you'd like to help resolve the issue, please send a report. I am so regretting upgrading to Fedora

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.

On 07/14/2017 08:19 AM, Sudhir Khanger wrote: I have been getting these messages on my system every second after upgrading from Fedora 25 to Fedora 26 Plasma Desktop. We're sorry, it looks like BOOT_IMAGE=/boot/vmlinuz-4.11.9-300.fc26.x86_64 crashed. I already have 1000 of reports that I

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.

On Fri, 14 Jul 2017 15:19:41 - "Sudhir Khanger" <m...@sudhirkhanger.com> wrote: > I have been getting these messages on my system every second after > upgrading from Fedora 25 to Fedora 26 Plasma Desktop. > > We're sorry, it looks like > BOOT_IMAGE=/boot

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.

Hello, I have been getting these messages on my system every second after upgrading from Fedora 25 to Fedora 26 Plasma Desktop. We're sorry, it looks like BOOT_IMAGE=/boot/vmlinuz-4.11.9-300.fc26.x86_64 crashed. I already have 1000 of reports that I can't submit. How do I resolve

Re: Fedora 26 qemu breaks Win10 guests

On Wed, 2017-07-12 at 21:08 -0400, Sam Varshavchik wrote: > Well, I'm all out of Fedora hosts with Win10 guests, that I can upgrade, so > that pretty much sticks a fork in me. From this little experiment, I see two > separate qemu 2.9 issues: an update screws up the Spice display driver; and

Re: Fedora 26 qemu breaks Win10 guests

Patrick O'Callaghan writes: On Tue, 2017-07-11 at 18:08 -0400, Sam Varshavchik wrote: > > > But this is a bald-faced lie. But if I force off, and boot again, Windows 10 > comes up like there's nothing wrong. Normal boot. Just tried it and it worked perfectly. Did you shut down your Windows

Re: Fedora 26 qemu breaks Win10 guests

On Tue, 2017-07-11 at 18:08 -0400, Sam Varshavchik wrote: > Patrick O'Callaghan writes: > > > On Tue, 2017-07-11 at 13:21 -0400, Sam Varshavchik wrote: > > > Upgraded F25 that had a Win10 guest VM to F26. > > > > > > When the VM got started, the initial logo and the spinning circle came up, > >

Re: Fedora 26 qemu breaks Win10 guests

On Jul 11, 2017 4:09 PM, "Sam Varshavchik" wrote: Patrick O'Callaghan writes: On Tue, 2017-07-11 at 13:21 -0400, Sam Varshavchik wrote: > > Upgraded F25 that had a Win10 guest VM to F26. > > > > When the VM got started, the initial logo and the spinning circle came > up,

Re: Fedora 26 qemu breaks Win10 guests

Patrick O'Callaghan writes: On Tue, 2017-07-11 at 13:21 -0400, Sam Varshavchik wrote: > Upgraded F25 that had a Win10 guest VM to F26. > > When the VM got started, the initial logo and the spinning circle came up, > but then the display cleared to what appears to be the VGA 648x480 >

Re: Fedora 26 qemu breaks Win10 guests

On Tue, 2017-07-11 at 13:21 -0400, Sam Varshavchik wrote: > Upgraded F25 that had a Win10 guest VM to F26. > > When the VM got started, the initial logo and the spinning circle came up, > but then the display cleared to what appears to be the VGA 648x480 > resolution, with gray vertical lines

Fedora 26 qemu breaks Win10 guests

Upgraded F25 that had a Win10 guest VM to F26. When the VM got started, the initial logo and the spinning circle came up, but then the display cleared to what appears to be the VGA 648x480 resolution, with gray vertical lines and something else. After a few minutes of this I force-rebooted

Re: Setting umask in Fedora 26

On Sun, 2017-04-30 at 18:26 -0600, Peter Gueckel wrote: > In ~/.bash_profile, I have umask=002, since I want directories > (files) to have the permission 755 (644). > > Until Fedora 25, this worked perfectly. > > Now, in Fedora 26, directories (files) are created with the >

Re: Setting umask in Fedora 26

Peter Gueckel wrote: > In ~/.bash_profile, I have umask=002 I meant, I have it set to *022* ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org

Setting umask in Fedora 26

In ~/.bash_profile, I have umask=002, since I want directories (files) to have the permission 755 (644). Until Fedora 25, this worked perfectly. Now, in Fedora 26, directories (files) are created with the permission 775 (664). When I run umask, it returns 0002. For some reason, my setting

Participate in Fedora 26 translation sprint

With the great success of our collaboration during Fedora 24 and Fedora 25 to improve localization, this is the time to make it even better for Fedora 26. We’re having a virtual Fedora 26 translation sprint to finish translations prior to the next Beta release. We will be gathering online from

<    1   2