F27 my problem with brasero-3.12.2-2.fc27
Hi, try to burn a 1.2GB mp4 film onto a DVD or as iso to a foulder. Result only about 200MB a burned (readable) to the DVD and the source file of 1.2GB is cut also to about 200MB (same size as shown on DVD), the size of the burned 1.2GB film varied in 2 trials from about 80MB to about 200MB. To check wether it's my system or not, I made a new installation of F27, same error. F26 does not show this error ( brasero-3.12.1-5.fc26 ) - brasero-3.12.2-2.fc27 - Name : kernel Version : 4.15.4 Release : 300.fc27 Arch : x86_64 First Time I see this in Brasero Kind regards ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
My Data Tranfer Problem seems to be solved in F27
Hi, in the previous Fedora versions up to F26 there I had a problem transferring film files (1GB to 2GB) from the Laptop internal disk (Win 8.1) to an external ntfs formatted disk, transfer speed up to 40MB/sec. The problem was in the first minutes of the data transfer about 3 films couldn't be transferred, data error, the following transfers of the same session ok . Total data transfer was about 40 - 60GB. It was also not possible to copy these about 3 films later on i.e. with F26,there seemed to be something corrupted, but in Win 8.1 also for these 3 films there were no copying problem. In F27 this phenomenon did so far not appear. My configuration, always the same: Acer Laptop E5-571G, 8GB Ram, internal disk Win 8.1, Fedora on USB 3.0 stick, external disk: internal disk SATA 1TB bought from Ebay, connected to the system via cheap SATA to USB 2.0 adapter. I am happy now. Kind regards ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
DevedeNG F27
Hi, I didn't find DevedeNG for F27, is this App still in the development phase? Kind regards ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Re: Security problem with firefox-57.0-0.8.fc26.x86_64
Hi Joachim, get the same with firefox-56.0-5.fc26.x86_64 kind regards joerg -Ursprüngliche Mitteilung- Von: Joachim Backes An: Fedora Test Verschickt: Di, 31. Okt 2017 10:18 Betreff: Security problem with firefox-57.0-0.8.fc26.x86_64 I'm having a problem with thw wikipedia.de website: If I try to open it, I get some warning issue: - Your connection is not secure The website tried to negotiate an inadequate level of security. wiki2.wikimedia.de uses security technology that is outdated and vulnerable to attack. An attacker could easily reveal information which you thought to be safe. The website administrator will need to fix the server first before you can visit the site. Error code: NS_ERROR_NET_INADEQUATE_SECURITY - Anybody sees this too for the German wikipedia website wikipedia.de? Kind regards Joachim Backes Fedora release 26 (Twenty Six) Kernel-4.13.10-200.fc26.x86_64 Joachim Backes https://www-user.rhrk.uni-kl.de/~backes/___test mailing list -- test@lists.fedoraproject.orgTo unsubscribe send an email to test-le...@lists.fedoraproject.org ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
question to the move process (moving files from Windows directory to an external disk via Fedora)
Hi, my system is a laptop (Acer Aspire E15 E5-571G, 1.7 GB, 8GB Ram) with Win 8.1 on the internal disk, Fedora 25/26/27 on an USB 3.0 Flash medium, an used internal SATA disk bought from Ebay (disk is OK) connected via an USB Adapter to an USB 2.0 port. Data volume to be transferred about 30GB, transferrate between 20 to 40 MB/sec. The data are TV films size about 1 - 2 GB. Problem with F25/26 by moving from Win 8.1 to the external disk about 10% of the films are not moved because of an move error, afterwards there it is not possible to copy the films anymore, possibly some leading bytes may be destroyed. I want to try this with F27 Beta. My question how error save are the packages concerned with the moving process from Win 8.1 to an external disk in this stage of F27 development, I don't want to corrupt my Win 8.1 system? Kind regards ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Re: F26, system blocked about 30 secs while looking for updates
Hi, Acer Laptop E5-571G, 1.7 GHZ, 8GB RAM. Kind regards -Ursprüngliche Mitteilung- Von: Nathan An: test Verschickt: Mo, 16. Okt 2017 15:29 Betreff: Re: F26, system blocked about 30 secs while looking for updates No do not be the same, anyway what computer do you have?___test mailing list -- test@lists.fedoraproject.orgTo unsubscribe send an email to test-le...@lists.fedoraproject.org ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
F26, system blocked about 30 secs while looking for updates
Hi, I boot my system (F26, Desktop version), then after some minutes the system is automaticly looking for updates. During the time of updates search, the system is blocked, i.e. no move of cursor possible etc. Move of cursor is possible again, when the information like "there are updates to install" (German version, I don't know the exact translation) appears in the top of the screen. Is this wanted to happen, will this be the same in F27? Kind regards ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Selinux alarm F25, important?? possibly out of topic because F25
Hi, since several weeks I get a Selinux warning. I translate from German (German Version of F25 Desktop) "the source process abrtd tried with dac_read_search to access capability. Unknown." Is it worthwhile to investigate, or can I forget it, because F27 is comming? Kind regards ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Re: question to file copy to external media
Hi, My desktop is the "Workstation Edition" and I use the files menu with copy and paste. In the case of interest (F26) the first 1.5 GB are copied very quickly (about 100MB/sec) then the copying process slows down to about 11MB/sec. After signalling completion I have to wait about 4 minutes untill I am allowed to eject. If this is normal, then OK, if not, possibly I should file a bug. Kind regards -Ursprüngliche Mitteilung- Von: Samuel Sieb An: test Verschickt: Mi, 26. Jul 2017 23:45 Betreff: Re: question to file copy to external media On 07/26/2017 01:35 PM, Adam Williamson wrote: > On Wed, 2017-07-26 at 11:50 -0700, Samuel Sieb wrote: >> This is standard behaviour on all current operating systems. That is >> why they all have the "eject" button for unmounting external media. The >> reason is that the operating system buffers the data in memory and then >> writes it to the device as fast as the device can accept it. This lets >> whatever process is doing the writing to get on with other things >> instead of having to wait for slow media. The unmount command waits for >> all the cached data to be written to the device before unmounting. Then >> you get a notification saying that you can remove it. > > I don't think it's "standard behaviour", no. I think quite a lot of > file managers only copy synchronously, to avoid exactly this confusion. > It would help if Joerg specified which desktop / file manager he's > using? Ok, then it used to be standard behaviour and I haven't paid attention to it since then. :-) I will have to try it out, but I thought I saw this with nautilus recently.___test mailing list -- test@lists.fedoraproject.orgTo unsubscribe send an email to test-le...@lists.fedoraproject.org ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
question to file copy to external media
Hi, I frequently copy files (Size about 2GB, sometimes 50 files of this size in one copying process) from my internal laptop disk (Win8.1) to an external media, usb flash drive or external disk. The copying progress is schown in the right upper corner of the display. When the display shows "copying is finished", the copying process is not really finished, it takes some additional minutes, before I can eject the external media. This appears in F24/F25/F26. This is confusing. Kind regards ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Re: F26 Final boot on 64GB USB flash medium unsuccessful
Hi, sorry a second and third boot with the same configuration was ok. sorry kind regards -Ursprüngliche Mitteilung- Von: Joerg Lechner An: test Verschickt: Mi, 12. Jul 2017 14:33 Betreff: Re: F26 Final boot on 64GB USB flash medium unsuccessful Hi, boot of F26 RC 1.4 was ok Kind regards -Ursprüngliche Mitteilung- Von: Joerg Lechner An: test Verschickt: Mi, 12. Jul 2017 14:32 Betreff: F26 Final boot on 64GB USB flash medium unsuccessful Hi, just I downloaded F26 RC 1.5 from the official download site. Tried to boot the installed (on a 64GB USB stick), dracut error. I have had the same error previously on one of the prereleases of F25, there it was a timer, which was adjusted badly for my system. Acer Laptop with Win 8.1, Fedora on an USB flash medium. Possibly the USB flash medium is at the end of it's life, I will try this on a new 32GB USB flash medium. But anyway I want to inform You as quickly as possible about what has happened. See screen shot attached. Kind regards ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Re: F26 Final boot on 64GB USB flash medium unsuccessful
Hi, boot of F26 RC 1.4 was ok Kind regards -Ursprüngliche Mitteilung- Von: Joerg Lechner An: test Verschickt: Mi, 12. Jul 2017 14:32 Betreff: F26 Final boot on 64GB USB flash medium unsuccessful Hi, just I downloaded F26 RC 1.5 from the official download site. Tried to boot the installed (on a 64GB USB stick), dracut error. I have had the same error previously on one of the prereleases of F25, there it was a timer, which was adjusted badly for my system. Acer Laptop with Win 8.1, Fedora on an USB flash medium. Possibly the USB flash medium is at the end of it's life, I will try this on a new 32GB USB flash medium. But anyway I want to inform You as quickly as possible about what has happened. See screen shot attached. Kind regards ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Re: F26 Beta 1.3, my error or Anaconda?
Hi, I retested this question with F26 Beta 1.4. Result: If I give in reclaim space first delete all and then preserve a special partition, it's ok. If I give in reclaim space only a delete to i.e. 2 linux partitions and preserve to all others, the memory configuration error occurs. Kind regards -Ursprüngliche Mitteilung- Von: Adam Williamson An: For testing and quality assurance of Fedora releases Verschickt: Do, 1. Jun 2017 7:54 Betreff: Re: F26 Beta 1.3, my error or Anaconda? On Thu, 2017-06-01 at 01:16 -0400, Joerg Lechner wrote: > Hi, > beginning of the story, F26 Beta 1.3 Workstation iso on usb stick, > produced in Legacy mode (originally made to make a test in legacy, > but should work like in EFI mode made), laptop in EFI mode. Want to > install F26 on a 64GB usb stick with 2 partitions, ca. 40GB F26, > about 20GB Data. For installation I chose the branch reclaim space, > but I wanted to delete only the Fedora partitions on the stick and > leave the Data partition as it was. The result is an error, no > installation possible. See the 2 screen shots attached. Worthwhile > for a bug or my handling error? > Kind regards The screenshots don't help non German speakers much :) Could you translate, please - especially the error message under INSTALLATION DESTINATION on the hub in the second screenshot? Thanks. Also, there *is* a known bug in 26 and Rawhide currently where the INSTALLATION DESTINATION spoke sometimes shows an error condition for no real reason, and just going through it again will sort things out. openQA runs into it every so often, I haven't yet been able to figure out what the trigger is. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net___test mailing list -- test@lists.fedoraproject.orgTo unsubscribe send an email to test-le...@lists.fedoraproject.org ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Re: F26 Beta 1.3, my error or Anaconda?
Hi Adam, the error message means " error in checking the memory configuration", I am not keen on writing a bug, I only want to report for me unexpected behaviour. Kind regards -Ursprüngliche Mitteilung- Von: Adam Williamson An: For testing and quality assurance of Fedora releases Verschickt: Do, 1. Jun 2017 7:54 Betreff: Re: F26 Beta 1.3, my error or Anaconda? On Thu, 2017-06-01 at 01:16 -0400, Joerg Lechner wrote: > Hi, > beginning of the story, F26 Beta 1.3 Workstation iso on usb stick, > produced in Legacy mode (originally made to make a test in legacy, > but should work like in EFI mode made), laptop in EFI mode. Want to > install F26 on a 64GB usb stick with 2 partitions, ca. 40GB F26, > about 20GB Data. For installation I chose the branch reclaim space, > but I wanted to delete only the Fedora partitions on the stick and > leave the Data partition as it was. The result is an error, no > installation possible. See the 2 screen shots attached. Worthwhile > for a bug or my handling error? > Kind regards The screenshots don't help non German speakers much :) Could you translate, please - especially the error message under INSTALLATION DESTINATION on the hub in the second screenshot? Thanks. Also, there *is* a known bug in 26 and Rawhide currently where the INSTALLATION DESTINATION spoke sometimes shows an error condition for no real reason, and just going through it again will sort things out. openQA runs into it every so often, I haven't yet been able to figure out what the trigger is. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net___test mailing list -- test@lists.fedoraproject.orgTo unsubscribe send an email to test-le...@lists.fedoraproject.org ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Re: Fedora-Workstation-Live-x86_64-26_Beta-1.3.iso doesn't boot from usb stick
Hi Joachim, did now the full installation chain in legacy mode (mediawriter - iso - F26 Beta 1.3 build) all worked fine. If You think it's the usb stick, test with F3. If I get problems with one of my usb sticks, I make a new partition table on the stick with gparted, if gparted can not delete a fedora partition, I try a new Fedora install on this stick and interrupt this process, before the new data are written, by doing this afterwards gparted always "repaired" an usb stick which had only a SW corruption and no hardware defect. Kind regards Joerg -Ursprüngliche Mitteilung- Von: Chris Murphy An: joachim.backes ; For testing and quality assurance of Fedora releases Cc: Joerg Lechner Verschickt: Mi, 31. Mai 2017 19:06 Betreff: Re: Fedora-Workstation-Live-x86_64-26_Beta-1.3.iso doesn't boot from usb stick On Wed, May 31, 2017 at 8:28 AM, Joachim Backes wrote: > On 05/31/17 13:54, Joerg Lechner wrote: >> >> Hi Joachim, >> I have prepared iso s on USB sticks, both 2GB and 64GB each, the iso s - >> F26 Beta 1.3 - prepared with fedora mediawriter on F24 in UEFI mode, the iso >> s boot correctly in EFI mode as well as in Legacy mode. But so far I could >> not prepare a F26 iso running in Legacy mode, can there be a difference >> producing the iso boot medium in Legacy compared to EFI? >> Kind regards > > > Hi Joerg, > > I wrote the iso with mediawriter-4.1.0-1.fc25.x86_64 in F25 onto the USB > stick, but if booted, it hangs up during "loading initrd.img". This is before media check runs. Bootloader > load kernel, load initramfs > execute kernel > unpack initramfs > systemd runs > dracut pics up the boot param to check media > checkiso executes and checks the media So your failure is happening at the 2nd step, you're still in the bootloader. This is almost certainly a USB stick problem. I'd just write the image again and maybe it'll fix itself as a transient failure. If not, the try another stick. -- Chris Murphy ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Re: Fedora-Workstation-Live-x86_64-26_Beta-1.3.iso doesn't boot from usb stick
Hi Joachim, I wanted to prepare a bootable iso, when my laptop runs in legacy mode, to see if there is a different behaviour of the iso on usb stick prepared on a system in uefi mode versus prepared on a system running in legacy mode, but currently a have no Fedora running in legacy mode, therefore I can currently not test this behaviour. I booted successfully F26 Beta 1.3 from usb stick with the laptop running in legacy mode (iso prepared with F24 in EFI Mode with mediawriter, x86_64, 4.0.7, fc24), I could install F26 mediawriter on this iso, but so far I can not read the F26 Beta 1.3 located on an other partition of the same stick, to make an installation of F26 - today lack of knowledge - I will solve this (mounting 2nd partition with the F26 file on it to get access with mediawriter to this file) possibly tomorrow. What I have seen in running the F26 beta 1.3 iso in legacy mode, is after giving access to WIFI and doing one, two, or three other small jobs successfully, the system is blocked and I have to reboot and start again, in my feeling it's not blocked because of lack on memory. Kind regards Joerg -Ursprüngliche Mitteilung- Von: Joachim Backes An: Joerg Lechner ; test Verschickt: Mi, 31. Mai 2017 16:29 Betreff: Re: Fedora-Workstation-Live-x86_64-26_Beta-1.3.iso doesn't boot from usb stick On 05/31/17 13:54, Joerg Lechner wrote: > Hi Joachim, > I have prepared iso s on USB sticks, both 2GB and 64GB each, the iso s - > F26 Beta 1.3 - prepared with fedora mediawriter on F24 in UEFI mode, the > iso s boot correctly in EFI mode as well as in Legacy mode. But so far I > could not prepare a F26 iso running in Legacy mode, can there be a > difference producing the iso boot medium in Legacy compared to EFI? > Kind regards Hi Joerg, I wrote the iso with mediawriter-4.1.0-1.fc25.x86_64 in F25 onto the USB stick, but if booted, it hangs up during "loading initrd.img". What do you mean by "I could not prepare a F26 iso running in Legacy mode"? So, I have no explanation why the boot fails. Perhaps an USB problem? No problems if I write the iso with K3b to a DVD. This DVD boots completely without failure and without hanging up. Thank you for all your replies. Kind regards Joachim Backes > > > -Ursprüngliche Mitteilung- > Von: Joachim Backes > An: Joerg Lechner ; test > Verschickt: Mi, 31. Mai 2017 11:30 > Betreff: Re: Fedora-Workstation-Live-x86_64-26_Beta-1.3.iso doesn't boot > from usb stick > > On 05/31/17 11:24, Joerg Lechner wrote: > > HiJoachim, > > You tried to install the iso on an 64GB usb stick? > > I have just installed the beta 1.3 iso on an 2GB stick, as I do always > > since F22. The Desktop installation on an 64GB usb stick (sandisk) was > > ok, I am just on F26 Beta 1.3. > > If it's worthwhile to test an iso on an 64GB stick, I can try this, > > please let me know. > > Kind regards Joerg > > Hi Joerg, > > the described boot issue is independent from the media size, the booting > fails too with a 16GB sized usb stick. There was no special reason for > me to use a 64GB stick (It was the only one which was available for me). > > Joachim > > > > > > > > > -Ursprüngliche Mitteilung- > > Von: Joachim Backes <mailto:joachim.bac...@rhrk.uni>-kl.de> > > An: Martin Bříza mailto:mbr...@redhat.com>>; For > testing and quality assurance > > of Fedora releases <mailto:test@lists.fedoraproject.org>> > > Verschickt: Mi, 31. Mai 2017 10:26 > > Betreff: Re: Fedora-Workstation-Live-x86_64-26_Beta-1.3.iso doesn't boot > > from usb stick > > > > On 05/31/17 10:20, Martin Bříza wrote: > > > On Wed, 31 May 2017 10:11:55 +0200, Joachim Backes > > > mailto:joachim.bac...@rhrk.uni> > <mailto:joachim.bac...@rhrk.uni>-kl.de > <mailto:joachim.bac...@rhrk.uni>-kl.de?>> wrote: > > > > > >> Hi all, > > >> > > >> writing the iso to a 64gb sized usb stick with mediawriter and then > > >> trying to boot, it hangs during "loading initrd.img" > > >> > > >> On the other hand, if writing the image to a DVD, f26 will boot. > > >> > > >> Anybody sees this too? > > >> > > >> Kind regards > > >> > > >> Joachim Backes > > > > > > Hi > > > Did the media check after writing and on bootup pass or fail? > > > > 1. The mediacheck passed after writing the image to the usb stick. > > 2. Booting the usb stick first presents, as expected, a menu for > > selection of some F26 variants or memory te
Re: Fedora-Workstation-Live-x86_64-26_Beta-1.3.iso doesn't boot from usb stick
Hi Joachim, I have prepared iso s on USB sticks, both 2GB and 64GB each, the iso s - F26 Beta 1.3 - prepared with fedora mediawriter on F24 in UEFI mode, the iso s boot correctly in EFI mode as well as in Legacy mode. But so far I could not prepare a F26 iso running in Legacy mode, can there be a difference producing the iso boot medium in Legacy compared to EFI? Kind regards -Ursprüngliche Mitteilung- Von: Joachim Backes An: Joerg Lechner ; test Verschickt: Mi, 31. Mai 2017 11:30 Betreff: Re: Fedora-Workstation-Live-x86_64-26_Beta-1.3.iso doesn't boot from usb stick On 05/31/17 11:24, Joerg Lechner wrote: > HiJoachim, > You tried to install the iso on an 64GB usb stick? > I have just installed the beta 1.3 iso on an 2GB stick, as I do always > since F22. The Desktop installation on an 64GB usb stick (sandisk) was > ok, I am just on F26 Beta 1.3. > If it's worthwhile to test an iso on an 64GB stick, I can try this, > please let me know. > Kind regards Joerg Hi Joerg, the described boot issue is independent from the media size, the booting fails too with a 16GB sized usb stick. There was no special reason for me to use a 64GB stick (It was the only one which was available for me). Joachim > > > > -Ursprüngliche Mitteilung- > Von: Joachim Backes > An: Martin Bříza ; For testing and quality assurance > of Fedora releases > Verschickt: Mi, 31. Mai 2017 10:26 > Betreff: Re: Fedora-Workstation-Live-x86_64-26_Beta-1.3.iso doesn't boot > from usb stick > > On 05/31/17 10:20, Martin Bříza wrote: > > On Wed, 31 May 2017 10:11:55 +0200, Joachim Backes > > mailto:joachim.bac...@rhrk.uni>-kl.de> wrote: > > > >> Hi all, > >> > >> writing the iso to a 64gb sized usb stick with mediawriter and then > >> trying to boot, it hangs during "loading initrd.img" > >> > >> On the other hand, if writing the image to a DVD, f26 will boot. > >> > >> Anybody sees this too? > >> > >> Kind regards > >> > >> Joachim Backes > > > > Hi > > Did the media check after writing and on bootup pass or fail? > > 1. The mediacheck passed after writing the image to the usb stick. > 2. Booting the usb stick first presents, as expected, a menu for > selection of some F26 variants or memory test. > > If selecting the memory test, it will run properly, but not F26. > > Kind regards > > Joachim Backes > -- > > Fedora release 25 (Twenty Five) > Kernel-4.11.3-200.fc25.x86_64 > > > Joachim Backes <mailto:joachim.bac...@rhrk.uni>-kl.de> > https://www-user.rhrk.uni-kl.de/~backes/ > ___ test mailing list -- > test@lists.fedoraproject.org <mailto:test@lists.fedoraproject.org> To > unsubscribe send an email to test-le...@lists.fedoraproject.org > <mailto:le...@lists.fedoraproject.org> -- Fedora release 25 (Twenty Five) Kernel-4.11.3-200.fc25.x86_64 Joachim Backes https://www-user.rhrk.uni-kl.de/~backes/ ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Re: Fedora-Workstation-Live-x86_64-26_Beta-1.3.iso doesn't boot from usb stick
Hi Joachim, You tried to install the iso on an 64GB usb stick? I have just installed the beta 1.3 iso on an 2GB stick, as I do always since F22. The Desktop installation on an 64GB usb stick (sandisk) was ok, I am just on F26 Beta 1.3. If it's worthwhile to test an iso on an 64GB stick, I can try this, please let me know. Kind regards Joerg -Ursprüngliche Mitteilung- Von: Joachim Backes An: Martin Bříza ; For testing and quality assurance of Fedora releases Verschickt: Mi, 31. Mai 2017 10:26 Betreff: Re: Fedora-Workstation-Live-x86_64-26_Beta-1.3.iso doesn't boot from usb stick On 05/31/17 10:20, Martin Bříza wrote: > On Wed, 31 May 2017 10:11:55 +0200, Joachim Backes > wrote: > >> Hi all, >> >> writing the iso to a 64gb sized usb stick with mediawriter and then >> trying to boot, it hangs during "loading initrd.img" >> >> On the other hand, if writing the image to a DVD, f26 will boot. >> >> Anybody sees this too? >> >> Kind regards >> >> Joachim Backes > > Hi > Did the media check after writing and on bootup pass or fail? 1. The mediacheck passed after writing the image to the usb stick. 2. Booting the usb stick first presents, as expected, a menu for selection of some F26 variants or memory test. If selecting the memory test, it will run properly, but not F26. Kind regards Joachim Backes -- Fedora release 25 (Twenty Five) Kernel-4.11.3-200.fc25.x86_64 Joachim Backes https://www-user.rhrk.uni-kl.de/~backes/___test mailing list -- test@lists.fedoraproject.orgTo unsubscribe send an email to test-le...@lists.fedoraproject.org ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Re: tried to install F26 Alpha 1.1 Workstation - no success
Hi, some further tests showed: pata 2,5" disk connected via an usb 2.0 adapter connected to the laptop on usb 2.0 and usb 3.0 --> installation ok. Installation on a 32GB usb 3.0 flash medium connected to the same laptop via usb 2.0 or usb 3.0 doesn't work. The partition table seem to be made (automatic partitioning) correctly. But sometimes the installation process is very slow, and before reaching the 100%, when a step takes too long time, there seem to be a timeout, with breakdown of the running live os, and falling back to the screen, where there is a choice to click to "live user". Therefore I think this timeout can happen in the running live user os, or in the F26 installation process. I tend to think it`s a timeout in the running "live user os" and not in anaconda, which I think is responsible for the installation. An anaconda error can be some "slowing downs", or "interruptive processing" of the installation on an usb flash medium, which may cause the possible timeout in the live user os. Worthwhile to file a bug or is it enough to mention this behaviour in this list? Kind regards -Ursprüngliche Mitteilung- Von: Joerg Lechner An: test Verschickt: Fr, 17. Mrz 2017 17:43 Betreff: tried to install F26 Alpha 1.1 Workstation - no success Hi, install live medium ok, install trial of F26 on an USB 3.0 32GB flash medium, install with reclaim space, install stops at 29% completion, afterwards break down of running live session, falls back to "live system user", tried 2 times, always the same behaviour. Kind regards ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
tried to install F26 Alpha 1.1 Workstation - no success
Hi, install live medium ok, install trial of F26 on an USB 3.0 32GB flash medium, install with reclaim space, install stops at 29% completion, afterwards break down of running live session, falls back to "live system user", tried 2 times, always the same behaviour. Kind regards ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
out of topic: speed of USB flash media as Fedora boot medium
Hi, there might not be many Fedora users having Fedora on an USB flash medium as boot device. I use a 32GB USB3.0 and 64GB USB 3.0 (in my case Sandisk Ultra). My 64GB stick is in reading much slower, then the 32GB stick - this I have recognised by very slow dnf updates in F25. I talked to Sandisk, they will replace the 64GB stick. Test results with F3: READ-WRITE Test with F3 64GB Stick und 32GB Stick on USB 3.0 64GB Average writing speed: 44.74 MB/s Average reading speed: 96.86 MB/s 32GB Average writing speed: 46.52 MB/s Average reading speed: 142.83 MB/s [joerg@linux ~]$ cd /run/media/joerg [joerg@linux joerg]$ ls 746E-2094 [joerg@linux joerg]$ f3write 74* Removing old file 1.h2w ... Removing old file 2.h2w ... ... .. Removing old file 49.h2w ... Removing old file 50.h2w ... Removing old file 51.h2w ... Removing old file 52.h2w ... Removing old file 53.h2w ... Removing old file 54.h2w ... Removing old file 55.h2w ... Removing old file 56.h2w ... Removing old file 57.h2w ... Removing old file 58.h2w ... Removing old file 59.h2w ... Free space: 58.88 GB Creating file 1.h2w ... OK! Creating file 2.h2w ... OK! Creating file 3.h2w ... OK! Creating file 4.h2w ... OK! Creating file 5.h2w ... OK! Creating file 6.h2w ... OK! Creating file 7.h2w ... OK! Creating file 8.h2w ... OK! Creating file 9.h2w ... OK! Creating file 10.h2w ... OK! ... Creating file 54.h2w ... OK! Creating file 55.h2w ... OK! Creating file 56.h2w ... OK! Creating file 57.h2w ... OK! Creating file 58.h2w ... OK! Creating file 59.h2w ... OK! Free space: 0.00 Byte Average writing speed: 44.74 MB/s [joerg@linux joerg]$ f3read 74* SECTORS ok/corrupted/changed/overwritten Validating file 1.h2w ... 2097152/ 0/ 0/ 0 Validating file 2.h2w ... 2097152/ 0/ 0/ 0 Validating file 3.h2w ... 2097152/ 0/ 0/ 0 Validating file 4.h2w ... 2097152/ 0/ 0/ 0 Validating file 5.h2w ... 2097152/ 0/ 0/ 0 Validating file 6.h2w ... 2097152/ 0/ 0/ 0 Validating file 7.h2w ... 2097152/ 0/ 0/ 0 Validating file 8.h2w ... 2097152/ 0/ 0/ 0 Validating file 9.h2w ... 2097152/ 0/ 0/ 0 Validating file 10.h2w ... 2097152/ 0/ 0/ 0 Validating file 11.h2w ... 2097152/ 0/ 0/ 0 Validating file 12.h2w ... 2097152/ 0/ 0/ 0 ... Validating file 53.h2w ... 2097152/ 0/ 0/ 0 Validating file 54.h2w ... 2097152/ 0/ 0/ 0 Validating file 55.h2w ... 2097152/ 0/ 0/ 0 Validating file 56.h2w ... 2097152/ 0/ 0/ 0 Validating file 57.h2w ... 2097152/ 0/ 0/ 0 Validating file 58.h2w ... 2097152/ 0/ 0/ 0 Validating file 59.h2w ... 1835456/ 0/ 0/ 0 Data OK: 58.88 GB (123470272 sectors) Data LOST: 0.00 Byte (0 sectors) Corrupted: 0.00 Byte (0 sectors) Slightly changed: 0.00 Byte (0 sectors) Overwritten: 0.00 Byte (0 sectors) Average reading speed: 96.86 MB/s [joerg@linux joerg]$ f3write F1* Removing old file 1.h2w ... Removing old file 2.h2w ... Removing old file 3.h2w ... Removing old file 4.h2w ... Removing old file 5.h2w ... . . Removing old file 24.h2w ... Removing old file 25.h2w ... Removing old file 26.h2w ... Removing old file 27.h2w ... Removing old file 28.h2w ... Removing old file 29.h2w ... Free space: 28.62 GB Creating file 1.h2w ... OK! Creating file 2.h2w ... OK! Creating file 3.h2w ... OK! Creating file 4.h2w ... OK! .. ... Creating file 22.h2w ... OK! Creating file 23.h2w ... OK! Creating file 24.h2w ... OK! Creating file 25.h2w ... OK! Creating file 26.h2w ... OK! Creating file 27.h2w ... OK! Creating file 28.h2w ... OK! Creating file 29.h2w ... OK! Free space: 0.00 Byte Average writing speed: 46.52 MB/s [joerg@linux joerg]$ f3read F1* SECTORS ok/corrupted/changed/overwritten Validating file 1.h2w ... 2097152/ 0/ 0/ 0 Validating file 2.h2w ... 2097152/ 0/ 0/ 0 Validating file 3.h2w ... 2097152/ 0/ 0/ 0 .. Validating file 24.h2w ... 2097152/ 0/ 0/ 0 Validating file 25.h2w ... 2097152/ 0/ 0/ 0 Validating file 26.h2w ... 2097152/ 0/ 0/ 0 Validating file 27.h2w ... 2097152/ 0/ 0/ 0 Validating file 28.h2w ... 2097152/ 0/ 0/ 0 Validating file 29.h2w ... 1310016/ 0/ 0/ 0 Data OK: 28.62 GB (60030272 sectors) Data LOST: 0.00 Byte (0 sectors) Corrupted: 0.00 Byte (0 sectors) Slightly changed: 0.00 Byte (0 sectors) Overwritten: 0.00 Byte (0 sectors) Average reading speed: 142.83 MB/s [joerg@linux joerg Kind regards ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Re: F25 much more worse then F24, I hope F26 will be better
Hi Adam, I made a new F25 installation on an USB 3.0 flash medium, so far not all Packets, which are on the previous installation. The First update (dnf update about 900 files) was very quick, so there is a problem in my old F25 installation, I will remove the old installation and forget this update problem. Kind regards -Ursprüngliche Mitteilung- Von: Joerg Lechner An: test Verschickt: Do, 2. Mrz 2017 15:21 Betreff: Re: F25 much more worse then F24, I hope F26 will be better Hi Adam, my configuration is F25 on an USB 3.0 Flash medium, 64GB, connected to the Laptop via USB 3.0. I use a 32GB USB 3.0 Flash medium for the F24 installation, which quick, as it would have been installed on the internal harddisk, my Laptop has 8GB Ram. So it's possible that I have made a "bad" F25 installation, and if not then the USB 3.0 "connection" is in F25 worse then in F24. I will keep this "bad" installation for eventually needed later investigation, and make a new install of F25 on an other 32GB USB 3.0 medium, then I can say If that, what I currently have is only a bad installation, or F25 is slow in an installation on an USB 3.0 flash medium. I need a little bit of time, to make a new installation. Kind regards -Ursprüngliche Mitteilung- Von: Adam Pribyl An: For testing and quality assurance of Fedora releases Verschickt: Do, 2. Mrz 2017 13:40 Betreff: Re: F25 much more worse then F24, I hope F26 will be better If this is a wall clock, then the update took 49minutes right? This is really weired. Download speed indicated the download took 2.4 minutes. This looks to me like some extremely slow access to hard drive to resolve all dependencies, rebuild delta RPM and then install them. Do you use SSD or HDD? What does the hdparm -tT /dev/sda (if sda is your primary disk) says? smartctl output may also be interesting. On Thu, 2 Mar 2017, Joerg Lechner wrote: > Hi, > investigation of the first action point: "dnf update" takes too much time in > F25. > I made timestamps by my watch not by the system. > . .. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Re: F25 much more worse then F24, I hope F26 will be better
Hi Adam, my configuration is F25 on an USB 3.0 Flash medium, 64GB, connected to the Laptop via USB 3.0. I use a 32GB USB 3.0 Flash medium for the F24 installation, which quick, as it would have been installed on the internal harddisk, my Laptop has 8GB Ram. So it's possible that I have made a "bad" F25 installation, and if not then the USB 3.0 "connection" is in F25 worse then in F24. I will keep this "bad" installation for eventually needed later investigation, and make a new install of F25 on an other 32GB USB 3.0 medium, then I can say If that, what I currently have is only a bad installation, or F25 is slow in an installation on an USB 3.0 flash medium. I need a little bit of time, to make a new installation. Kind regards -Ursprüngliche Mitteilung- Von: Adam Pribyl An: For testing and quality assurance of Fedora releases Verschickt: Do, 2. Mrz 2017 13:40 Betreff: Re: F25 much more worse then F24, I hope F26 will be better If this is a wall clock, then the update took 49minutes right? This is really weired. Download speed indicated the download took 2.4 minutes. This looks to me like some extremely slow access to hard drive to resolve all dependencies, rebuild delta RPM and then install them. Do you use SSD or HDD? What does the hdparm -tT /dev/sda (if sda is your primary disk) says? smartctl output may also be interesting. On Thu, 2 Mar 2017, Joerg Lechner wrote: > Hi, > investigation of the first action point: "dnf update" takes too much time in > F25. > I made timestamps by my watch not by the system. > > start of dnf update 09:48 > > [joerg@linux ~]$ su > Passwort: > [root@linux joerg]# dnf update > Letzte Prüfung auf abgelaufene Metadaten: vor 0:06:22 am Thu Mar 2 09:41:58 > 2017. > Abhängigkeiten sind aufgelöst. > > PackageArch Version Paketquelle > Größe > > Installieren: > kernel x86_64 4.9.12-200.fc25 updates 96 k > kernel-corex86_64 4.9.12-200.fc25 updates 20 M > kernel-modules x86_64 4.9.12-200.fc25 updates 22 M > kernel-modules-extra x86_64 4.9.12-200.fc25 updates 2.2 M > libglvnd x86_64 1:0.2.999-10.gitdc16f8c.fc25 updates 89 k > libglvnd-egl x86_64 1:0.2.999-10.gitdc16f8c.fc25 updates 43 k > libglvnd-gles x86_64 1:0.2.999-10.gitdc16f8c.fc25 updates 31 k > libglvnd-glx x86_64 1:0.2.999-10.gitdc16f8c.fc25 updates 124 k > Aktualisieren: > NetworkManager-openvpn x86_64 1:1.2.8-2.fc25updates 237 k > NetworkManager-openvpn-gnome > x86_64 1:1.2.8-2.fc25updates 91 k > audit x86_64 2.7.3-1.fc25 updates 243 k > audit-libsx86_64 2.7.3-1.fc25 updates 106 k > audit-libs-python x86_64 2.7.3-1.fc25 updates 77 k > audit-libs-python3x86_64 2.7.3-1.fc25 updates 76 k > breeze-icon-theme noarch 5.31.0-1.fc25 updates 8.3 M > copy-jdk-configs noarch 2.2-2.fc25updates 19 k > fedora-repos noarch 25-2 updates 88 k > gnome-autoar x86_64 0.2.0-1.fc25 updates 49 k > gnome-terminalx86_64 3.22.1-5.fc25 updates 1.2 M > gspellx86_64 1.2.3-1.fc25 updates 81 k > gstreamer1x86_64 1.10.4-1.fc25 updates 1.2 M > gstreamer1-plugins-bad-free >x86_64 1.10.4-1.fc25 updates 1.8 M > gstreamer1-plugins-bad-free-gtk >x86_64 1.10.4-1.fc25 updates 32 k > gstreamer1-plugins-base x86_64 1.10.4-1.fc25 updates 1.5 M > gstreamer1-plugins-good x86_64 1.10.4-1.fc25 updates 2.0 M > ibus-typing-booster noarch 1.5.22-1.fc25 updates 3.8 M > kde-style-breeze x86_64 5.8.6-1.fc25 updates 179 k > kernel-headersx86_64 4.9.12-200.fc25 updates 1.1 M > kf5-filesystemx86_64 5.31.0-1.fc25 updates 15 k > libblockdev x86_64 1.9-9.fc25updates 85 k > libblockdev-btrfs x86_64 1.9-9.fc25updates 41 k > libblockdev-cryptox86_64 1.9-9.fc25updates 43 k > libblockdev-dmx86_64 1.9-9.fc25updates
Re: F25 much more worse then F24, I hope F26 will be better
and report. Kind regards -Ursprüngliche Mitteilung- Von: Matthew Miller An: For testing and quality assurance of Fedora releases Verschickt: Mi, 1. Mrz 2017 14:45 Betreff: Re: F25 much more worse then F24, I hope F26 will be better On Mon, Feb 27, 2017 at 06:19:18AM -0500, Joerg Lechner wrote:> - last dnf update took far too much time> - shutdown process not tolerable, takes too much time.> - usb connection erroneous. i.e. after copying to flash medium or> external disk connected by an usb adapter in most trials, when I try> to eject the usb connected medium, there - after a copying process is> finished a long time ago - comes the message "usb medium in use",> this for ever. Also after shutdown of F25 in some cases I had to> repair the usb connected medium with a new partition table. Things> like that are not nice.These things seem unlikely to actually be very version dependent andprobably are more to do with the specific configuration. The first twocomplaints are not actionable — the dnf problem might just be yournetwork, and without any detail, we don't know what is holding up yoursystem's shutdown.The third is likely a kernel issue, and may be something you can tune.Are you *sure* you don't have anything from the externel disk in use?The /sbin/lsof command can tell you.Have you tried typing "sync" at the command line before attempting toeject the disk?-- Matthew MillerFedora Project Leader___test mailing list -- test@lists.fedoraproject.orgTo unsubscribe send an email to test-le...@lists.fedoraproject.org ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Re: F25 much more worse then F24, I hope F26 will be better
Hi, thank You Matthiew, I will investigate and give more details. Kind regards -Ursprüngliche Mitteilung- Von: Matthew Miller An: For testing and quality assurance of Fedora releases Verschickt: Mi, 1. Mrz 2017 14:45 Betreff: Re: F25 much more worse then F24, I hope F26 will be better On Mon, Feb 27, 2017 at 06:19:18AM -0500, Joerg Lechner wrote:> - last dnf update took far too much time> - shutdown process not tolerable, takes too much time.> - usb connection erroneous. i.e. after copying to flash medium or> external disk connected by an usb adapter in most trials, when I try> to eject the usb connected medium, there - after a copying process is> finished a long time ago - comes the message "usb medium in use",> this for ever. Also after shutdown of F25 in some cases I had to> repair the usb connected medium with a new partition table. Things> like that are not nice.These things seem unlikely to actually be very version dependent andprobably are more to do with the specific configuration. The first twocomplaints are not actionable — the dnf problem might just be yournetwork, and without any detail, we don't know what is holding up yoursystem's shutdown.The third is likely a kernel issue, and may be something you can tune.Are you *sure* you don't have anything from the externel disk in use?The /sbin/lsof command can tell you.Have you tried typing "sync" at the command line before attempting toeject the disk?-- Matthew MillerFedora Project Leader___test mailing list -- test@lists.fedoraproject.orgTo unsubscribe send an email to test-le...@lists.fedoraproject.org ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
F25 much more worse then F24, I hope F26 will be better
Hi, - last dnf update took far too much time - shutdown process not tolerable, takes too much time. - usb connection erroneous. i.e. after copying to flash medium or external disk connected by an usb adapter in most trials, when I try to eject the usb connected medium, there - after a copying process is finished a long time ago - comes the message "usb medium in use", this for ever. Also after shutdown of F25 in some cases I had to repair the usb connected medium with a new partition table. Things like that are not nice. Conclusion: I use F24 and if F26 will be better switch to F26 and omit F25. Kind regards ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Re: problem in F25 shutdown process
Hi, i would like to compare the shutdown logs F24 and F25. Assume I can find it in /var/logs. Which log is to view, to see the possible error in the F25 shutdown in comparison to F24? Kind regards -Ursprüngliche Mitteilung- Von: Joerg Lechner An: test Verschickt: Do, 19. Jan 2017 19:00 Betreff: Re: problem in F25 shutdown process Hi Stan, I have already filed Bug 1414809 - problem in F25 shutdown process to Kernel. In my eyes its a major bug. I have just done the same on F24 with another disk - no problem. Also if You don't have a USB-disk, if You compare shutting down in F24 and F25, You should see the -only viewing shut down in F25 desktop version, no logging - lines of code displayed and the the time needed for shutting down, and You can compare this this with the shut down procedure in F24. Kind regards -Ursprüngliche Mitteilung- Von: stan An: test Verschickt: Do, 19 Jan 2017 5:52 pm Betreff: Re: problem in F25 shutdown process On Thu, 19 Jan 2017 01:04:39 -0500Joerg Lechner wrote:> Hi> is use external disks (USB) to collect TV films and TV shows.> Yesterday I forgot to eject the external disk before shutting down> F25. Result ratarata.. of the external disk during the shut down> process. Currently I have no access to this disk (sata, 1TB) via F25,> F24 and Windows I did not try so far. The shut down process of F25> takes a lot more time, then the shut down process of F24/F23.> Shutting down F25 a lot of code is displayed. I didn't make any> modification, the system is as originally installed, with the last> updates. This very long lasting shut down process seems to have been> the same since Alpha. With F24/F23 I could shutting down the PC> without destroying an external disk. My system Acer Laptop> E5-571G-50K9, F25 Desktop Version 64bit, the external disk is> connected with an USB adapter, it's a used internal disk. I don't> know whether the disk has had an error previously or not, but I could> save on it about 100GB films before shutting down without of the> "ticking" of a moribund disk. Kind regardsI don't have a usb disk, so I'm not familiar with this. But, are yousaying that shutting down F25 with a usb disk attached destroyed theusb disk? I think that at shutdown, all buffers are flushed to disk,so that the disk is left in the correct state. I can't see how thatwould trash a disk. If it did, that's a major bug, and you should opena bugzilla documenting your experience as above. I'm not sure whichcomponent does that, unfortunately. Probably the kernel, but systemdis in charge of shutdown, so you could choose either kernel or systemd.https://bugzilla.redhat.com/___test mailing list -- test@lists.fedoraproject.orgTo unsubscribe send an email to test-le...@lists.fedoraproject.org ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Re: problem in F25 shutdown process
Hi Stan, I have already filed Bug 1414809 - problem in F25 shutdown process to Kernel. In my eyes its a major bug. I have just done the same on F24 with another disk - no problem. Also if You don't have a USB-disk, if You compare shutting down in F24 and F25, You should see the -only viewing shut down in F25 desktop version, no logging - lines of code displayed and the the time needed for shutting down, and You can compare this this with the shut down procedure in F24. Kind regards -Ursprüngliche Mitteilung- Von: stan An: test Verschickt: Do, 19 Jan 2017 5:52 pm Betreff: Re: problem in F25 shutdown process On Thu, 19 Jan 2017 01:04:39 -0500Joerg Lechner wrote:> Hi> is use external disks (USB) to collect TV films and TV shows.> Yesterday I forgot to eject the external disk before shutting down> F25. Result ratarata.. of the external disk during the shut down> process. Currently I have no access to this disk (sata, 1TB) via F25,> F24 and Windows I did not try so far. The shut down process of F25> takes a lot more time, then the shut down process of F24/F23.> Shutting down F25 a lot of code is displayed. I didn't make any> modification, the system is as originally installed, with the last> updates. This very long lasting shut down process seems to have been> the same since Alpha. With F24/F23 I could shutting down the PC> without destroying an external disk. My system Acer Laptop> E5-571G-50K9, F25 Desktop Version 64bit, the external disk is> connected with an USB adapter, it's a used internal disk. I don't> know whether the disk has had an error previously or not, but I could> save on it about 100GB films before shutting down without of the> "ticking" of a moribund disk. Kind regardsI don't have a usb disk, so I'm not familiar with this. But, are yousaying that shutting down F25 with a usb disk attached destroyed theusb disk? I think that at shutdown, all buffers are flushed to disk,so that the disk is left in the correct state. I can't see how thatwould trash a disk. If it did, that's a major bug, and you should opena bugzilla documenting your experience as above. I'm not sure whichcomponent does that, unfortunately. Probably the kernel, but systemdis in charge of shutdown, so you could choose either kernel or systemd.https://bugzilla.redhat.com/___test mailing list -- test@lists.fedoraproject.orgTo unsubscribe send an email to test-le...@lists.fedoraproject.org ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
problem in F25 shutdown process
Hi is use external disks (USB) to collect TV films and TV shows. Yesterday I forgot to eject the external disk before shutting down F25. Result ratarata.. of the external disk during the shut down process. Currently I have no access to this disk (sata, 1TB) via F25, F24 and Windows I did not try so far. The shut down process of F25 takes a lot more time, then the shut down process of F24/F23. Shutting down F25 a lot of code is displayed. I didn't make any modification, the system is as originally installed, with the last updates. This very long lasting shut down process seems to have been the same since Alpha. With F24/F23 I could shutting down the PC without destroying an external disk. My system Acer Laptop E5-571G-50K9, F25 Desktop Version 64bit, the external disk is connected with an USB adapter, it's a used internal disk. I don't know whether the disk has had an error previously or not, but I could save on it about 100GB films before shutting down without of the "ticking" of a moribund disk. Kind regards ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Re: K3B in F25 blocks after burning a CD
Hi, thank You Stan. I filed bug 1413400 . I could show the processes in a virtual console, kill them and return to the gui interface. Kind regards -Ursprüngliche Mitteilung- Von: stan An: test Verschickt: So, 15 Jan 2017 5:40 pm Betreff: Re: K3B in F25 blocks after burning a CD On Sun, 15 Jan 2017 01:39:12 -0500Joerg Lechner wrote:> Hi,> I like to use K3B instead of Brasero. But I recognized that after> successful burning of a CD, the CD is successfully ejected, but> afterwards my system is blocked, I cannot shut down K3B, have to> restart the system. Where is to put the question? KDE oe Fedora? My> system is always updated to the newest SW. Kind regardsI suggest you open a bugzilla against package k3b. You can do so here:https://bugzilla.redhat.com/Can you reach a virtual console? Ctrl-Alt-F2 - F6If you can, can you then do a ps alx | grep -i k3bto find the process id?If you can, what happens if you dokill [process id]or kill -9 [process id]if that doesn't work? Can you then return to the gui interfacesuccessfully? Ctrl-Alt-F1___test mailing list -- test@lists.fedoraproject.orgTo unsubscribe send an email to test-le...@lists.fedoraproject.org ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
K3B in F25 blocks after burning a CD
Hi, I like to use K3B instead of Brasero. But I recognized that after successful burning of a CD, the CD is successfully ejected, but afterwards my system is blocked, I cannot shut down K3B, have to restart the system. Where is to put the question? KDE oe Fedora? My system is always updated to the newest SW. Kind regards ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
F25, transfer of files to external disk not stable enough
Hi, I am frequently transferring files (mp4 films) from the internal laptop disk to an usb connected external disk. F24 - stable file transferring (about 80GB in about 1 hour), Win 8.1 worse then F24, F25 worse then Win 8.1, F25 and Windows 8.1 frequently break down of the "connection", stable only for transferring of 10 - 15 GB, then break down of the connection, had to reboot the system, to get the cut and copy process again to run, that's my last experience. My system Fedora on an usb 3.0 flash medium, Win 8.1 on the internal laptop disk, external disk (sata 200GB) usb 2.0 connected, with usb-sata/pata adapter. File transfer is made from the laptop internal disk to the external usb 2.0 connected disk (ntfs formatted). Is this worthwhile to investigate? If yes, please tell me, which logs I should do. Kind regards ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
O.T. F25 Brasero displays burn error, K3B does the job
Hi, try to copy a VCD or a picture CD with jpgs. Error see log appending. K3B does this job without error. If anyone of the Brasero developpers sees this thread, possibly he would be interested in the investigation of this problem. The error occurs at the "end" of the copy process. The copy should be done from a VCD into a CD in the same burning utility. The CD was made with a Windows program. Kind regards, log appending Log: Checking session consistency (brasero_burn_check_session_consistency brasero-burn.c:1739) BraseroCdrdao called brasero_job_get_action BraseroCdrdao getting varg BraseroCdrdao called brasero_job_get_action BraseroCdrdao called brasero_job_get_current_track BraseroCdrdao called brasero_job_set_output_size_for_current_track BraseroCdrdao got varg: BraseroCdrdao stopping BraseroCdrdao called brasero_job_get_action BraseroCdrdao called brasero_job_get_session_output_size BraseroCdrdao output set (IMAGE) image = /home/joerg/muttiAlbum-.toc.bin toc = /home/joerg/muttiAlbum-.toc BraseroCdrdao called brasero_job_get_session_output_size BraseroCdrdao getting varg BraseroCdrdao called brasero_job_get_action BraseroCdrdao called brasero_job_get_current_track BraseroCdrdao called brasero_job_get_output_type BraseroCdrdao called brasero_job_get_image_output BraseroCdrdao called brasero_job_get_action BraseroCdrdao called brasero_job_set_use_average_rate BraseroCdrdao got varg: cdrdao read-cd --device /dev/sr0 --read-raw --datafile /home/joerg/muttiAlbum-.toc.bin -v 2 /home/joerg/muttiAlbum-.toc BraseroCdrdao Launching command BraseroCdrdao called brasero_job_get_fd_in BraseroCdrdao called brasero_job_get_fd_out BraseroCdrdao stderr: WARNING: Environment variable 'HOME' not defined- cannot read .cdrdao. BraseroCdrdao called brasero_job_get_action BraseroCdrdao stderr: Cdrdao version 1.2.3 - (C) Andreas Mueller BraseroCdrdao called brasero_job_get_action BraseroCdrdao stderr: /dev/sr0: HL-DT-ST DVDRAM GUA0NRev: 1.00 BraseroCdrdao called brasero_job_get_action BraseroCdrdao stderr: Using driver: Generic SCSI-3/MMC - Version 2.0 (options 0x) BraseroCdrdao called brasero_job_get_action BraseroCdrdao stderr: BraseroCdrdao stderr: Reading toc and track data... BraseroCdrdao called brasero_job_get_action BraseroCdrdao stderr: BraseroCdrdao stderr: Track ModeFlags StartLength BraseroCdrdao called brasero_job_get_action BraseroCdrdao stderr: BraseroCdrdao called brasero_job_get_action BraseroCdrdao stderr: 1 DATA4 00:00:00( 0) 35:40:29(160529) BraseroCdrdao called brasero_job_get_action BraseroCdrdao stderr: Leadout DATA4 35:40:29(160529) BraseroCdrdao called brasero_job_get_action BraseroCdrdao called brasero_job_get_action BraseroCdrdao stderr: BraseroCdrdao stderr: PQ sub-channel reading (data track) is supported, data format is BCD. BraseroCdrdao called brasero_job_get_action BraseroCdrdao stderr: Raw P-W sub-channel reading (data track) is supported. BraseroCdrdao called brasero_job_get_action BraseroCdrdao stderr: Cooked R-W sub-channel reading (data track) is supported. BraseroCdrdao called brasero_job_get_action BraseroCdrdao stderr: Copying data track 1 (MODE2_RAW): start 00:00:00, length 35:40:29 to "/home/joerg/muttiAlbum-.toc.bin"... BraseroCdrdao called brasero_job_get_action BraseroCdrdao called brasero_job_set_current_action BraseroCdrdao stderr: 00:01:00 BraseroCdrdao called brasero_job_get_action BraseroCdrdao stderr: 00:02:00 BraseroCdrdao called brasero_job_get_action BraseroCdrdao stderr: 00:03:00 BraseroCdrdao called brasero_job_get_action BraseroCdrdao stderr: 00:04:00 BraseroCdrdao called brasero_job_get_action BraseroCdrdao stderr: 00:05:00 BraseroCdrdao called brasero_job_get_action BraseroCdrdao stderr: 00:06:00 BraseroCdrdao called brasero_job_get_action BraseroCdrdao stderr: 00:07:00 BraseroCdrdao called brasero_job_get_action BraseroCdrdao stderr: 00:08:00 BraseroCdrdao called brasero_job_get_action BraseroCdrdao stderr: 00:09:00 BraseroCdrdao called brasero_job_get_action BraseroCdrdao stderr: 00:10:00 BraseroCdrdao called brasero_job_get_action BraseroCdrdao stderr: 00:11:00 BraseroCdrdao called brasero_job_get_action BraseroCdrdao stderr: 00:12:00 BraseroCdrdao called brasero_job_get_action BraseroCdrdao stderr: 00:13:00 BraseroCdrdao called brasero_job_get_action BraseroCdrdao stderr: 00:14:00 BraseroCdrdao called . . . . . BraseroCdrdao called brasero_job_get_action BraseroCdrdao stderr: 35:34:00 BraseroCdrdao called brasero_job_get_action BraseroCdrdao stderr: 35:35:00 BraseroCdrdao called brasero_job_get_action BraseroCdrdao stderr: 35:36:00 BraseroCdrdao called brasero_job_get_action BraseroCdrdao stderr: 35:37:00 BraseroCdrdao called brasero_job_get_action BraseroCdrdao stderr: 35:38:00 BraseroCdrdao called brasero_job_get_action BraseroCdrdao stderr: 35:39:00 BraseroCdrdao called brasero_jo
Re: F25 Workstation - Problem gparted
Hi, tried to start gparted out of an xterm with su and pw no success. Logged in as root, xterm, gparted started. What's in this case the difference in giving as user su and pw and beeing logged in as root? see log copied from xterm: [joerg@linux ~]$ su Passwort: [root@linux joerg]# gparted Created symlink /run/systemd/system/-.mount → /dev/null. Created symlink /run/systemd/system/boot-efi.mount → /dev/null. Created symlink /run/systemd/system/boot.mount → /dev/null. Created symlink /run/systemd/system/home.mount → /dev/null. Created symlink /run/systemd/system/proc-fs-nfsd.mount → /dev/null. Created symlink /run/systemd/system/run-user-0.mount → /dev/null. Created symlink /run/systemd/system/run-user-1000.mount → /dev/null. Created symlink /run/systemd/system/run-user-42.mount → /dev/null. Created symlink /run/systemd/system/tmp.mount → /dev/null. Created symlink /run/systemd/system/var-lib-machines.mount → /dev/null. Created symlink /run/systemd/system/var-lib-nfs-rpc_pipefs.mount → /dev/null. No protocol specified (gpartedbin:4086): Gtk-WARNING **: cannot open display: :0 Removed /run/systemd/system/-.mount. Removed /run/systemd/system/boot-efi.mount. Removed /run/systemd/system/boot.mount. Removed /run/systemd/system/home.mount. Removed /run/systemd/system/proc-fs-nfsd.mount. Removed /run/systemd/system/run-user-0.mount. Removed /run/systemd/system/run-user-1000.mount. Removed /run/systemd/system/run-user-42.mount. Removed /run/systemd/system/tmp.mount. Removed /run/systemd/system/var-lib-machines.mount. Removed /run/systemd/system/var-lib-nfs-rpc_pipefs.mount. [root@linux joerg]# Kind regards -Ursprüngliche Mitteilung- Von: Adam Williamson An: For testing and quality assurance of Fedora releases Verschickt: Mo, 28 Nov 2016 5:19 pm Betreff: Re: F25 Workstation - Problem gparted On Mon, 2016-11-28 at 20:41 +0800, Ed Greshko wrote:> > On 11/28/16 20:33, Joerg Lechner wrote:> > can not start gparted see protocol from terminal. Does anyone know, whats to do?> > gparted will not run in a GNOME-Wayland session.> > Run GNOME in X11 to run gparted.This is because it tries to run with root privileges, right?-- Adam WilliamsonFedora QA Community MonkeyIRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . nethttp://www.happyassassin.net___test mailing list -- test@lists.fedoraproject.orgTo unsubscribe send an email to test-le...@lists.fedoraproject.org ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
F25 Workstation - Problem gparted
Hi, can not start gparted see protocol from terminal. Does anyone know, whats to do? [root@linux joerg]# gparted Created symlink /run/systemd/system/-.mount → /dev/null. Created symlink /run/systemd/system/boot-efi.mount → /dev/null. Created symlink /run/systemd/system/boot.mount → /dev/null. Created symlink /run/systemd/system/home.mount → /dev/null. Created symlink /run/systemd/system/proc-fs-nfsd.mount → /dev/null. Created symlink /run/systemd/system/run-user-1000.mount → /dev/null. Created symlink /run/systemd/system/run-user-42.mount → /dev/null. Created symlink /run/systemd/system/tmp.mount → /dev/null. Created symlink /run/systemd/system/var-lib-machines.mount → /dev/null. Created symlink /run/systemd/system/var-lib-nfs-rpc_pipefs.mount → /dev/null. No protocol specified (gpartedbin:2671): Gtk-WARNING **: cannot open display: :0 Removed /run/systemd/system/-.mount. Removed /run/systemd/system/boot-efi.mount. Removed /run/systemd/system/boot.mount. Removed /run/systemd/system/home.mount. Removed /run/systemd/system/proc-fs-nfsd.mount. Removed /run/systemd/system/run-user-1000.mount. Removed /run/systemd/system/run-user-42.mount. Removed /run/systemd/system/tmp.mount. Removed /run/systemd/system/var-lib-machines.mount. Removed /run/systemd/system/var-lib-nfs-rpc_pipefs.mount. [root@linux joerg]# Kind regards ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
F25 i386 LXDE Anaconda - reclaim space doesn't work
Hi, Old HP Pavilion Laptop, I think 64bit. Tried to install from DVD iso to install F25 i386 LXDE. Reaching in Anaconda the step "Speicherplatz Freigeben (reclaim space in English)" the button "reclaim space" is not lightened, therefore no action on hitting on it. Worthwhile for a bug report? Kind regards ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Re: Kernel x86_64 4.5.5- 300.fc24 - no shutdown possible
Hi, this shutdown problem does not appear in F25 with Kernels 4.8.6-300.fc25 and 4.8.0-0.rc7.git0.1.fc25 Kind regards -Ursprüngliche Mitteilung- Von: Joerg Lechner An: test Verschickt: Fr, 11 Nov 2016 9:39 am Betreff: Kernel x86_64 4.5.5- 300.fc24 - no shutdown possible Hi, shutting down remains in the Fedora screen blue with the stars, the curser is disappeared, only possible to shutdown totally by power off. This is a new installation of F24 after the problem described in in the thread " It's F24, but possibly concerns more Fxx, Kernel dnf update -> grub> ". This shutdown problem i had also with Kernel 4.8.6-201.fc24 before the error "grub>" appeared, no display of grub boot menue. Question: How to make a downgrade of Kernel, when there is only one Kernel in the system? I would like to downgrade untill this error disappears to help finding the reason for this error. Kind regards ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Kernel x86_64 4.5.5- 300.fc24 - no shutdown possible
Hi, shutting down remains in the Fedora screen blue with the stars, the curser is disappeared, only possible to shutdown totally by power off. This is a new installation of F24 after the problem described in in the thread " It's F24, but possibly concerns more Fxx, Kernel dnf update -> grub> ". This shutdown problem i had also with Kernel 4.8.6-201.fc24 before the error "grub>" appeared, no display of grub boot menue. Question: How to make a downgrade of Kernel, when there is only one Kernel in the system? I would like to downgrade untill this error disappears to help finding the reason for this error. Kind regards ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Re: It's F24, but possibly concerns more Fxx, Kernel dnf update -> grub>
Hi Samuel, thank You for helping! Kind regards Joerg -Ursprüngliche Mitteilung- Von: Samuel Sieb An: For testing and quality assurance of Fedora releases Verschickt: Do, 10 Nov 2016 8:27 pm Betreff: Re: It's F24, but possibly concerns more Fxx, Kernel dnf update -> grub> On 11/10/2016 10:27 AM, Joerg Lechner wrote:> Hi,> did a new install, I am not so good in repairing broken systems, the> reason for this damage, I don't know, is it possible, that bad clicking> in emails and websites can cause to stop the next booting at "grub>" and> not displaying the Grub menue? Did anyone see things like that, which> are not caused by a hidden software error, or by a bad combination of apps?The only thing I can think of is that something went wrong during the kernel install and the grub config didn't get updated properly.___test mailing list -- test@lists.fedoraproject.orgTo unsubscribe send an email to test-le...@lists.fedoraproject.org ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Re: It's F24, but possibly concerns more Fxx, Kernel dnf update -> grub>
Hi, did a new install, I am not so good in repairing broken systems, the reason for this damage, I don't know, is it possible, that bad clicking in emails and websites can cause to stop the next booting at "grub>" and not displaying the Grub menue? Did anyone see things like that, which are not caused by a hidden software error, or by a bad combination of apps? Kind regards -Ursprüngliche Mitteilung- Von: Samuel Sieb An: For testing and quality assurance of Fedora releases Verschickt: Mi, 9 Nov 2016 3:04 am Betreff: Re: It's F24, but possibly concerns more Fxx, Kernel dnf update -> grub> On 11/08/2016 10:33 AM, Joerg Lechner wrote:> I can only look with F23(F25) into the config file of F24, because since> my update today the boot stops with "grub>". The config file says:> # Automatically generated file; DO NOT EDIT.> # Linux/x86_64 4.8.6-201.fc24.x86_64 Kernel Configuration>> It's the same as You have. In this case I don't understand this> behaviour of my installation. If it's not of general interest, I will do> a new installation of F24, which causes no problem for me.Am I understanding correctly that you don't get the grub menu at all? At first I was thinking it was just not booting the latest kernel. If that's the case, then you will most likely need to boot a live image or better an installer with the rescue mode (net installer works), chroot to the system and run grub2-mkconfig with the appropriate options or redirect.___test mailing list -- test@lists.fedoraproject.orgTo unsubscribe send an email to test-le...@lists.fedoraproject.org ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Re: It's F24, but possibly concerns more Fxx, Kernel dnf update -> grub>
Hi, I can only look with F23(F25) into the config file of F24, because since my update today the boot stops with "grub>". The config file says: # Automatically generated file; DO NOT EDIT. # Linux/x86_64 4.8.6-201.fc24.x86_64 Kernel Configuration It's the same as You have. In this case I don't understand this behaviour of my installation. If it's not of general interest, I will do a new installation of F24, which causes no problem for me. Kind regards -Ursprüngliche Mitteilung- Von: Samuel Sieb An: For testing and quality assurance of Fedora releases Verschickt: Di, 8 Nov 2016 6:25 pm Betreff: Re: It's F24, but possibly concerns more Fxx, Kernel dnf update -> grub> On 11/08/2016 06:23 AM, Joerg Lechner wrote:> dnf update today in F24 results in a bad Kernel, should be the last> Kernel for F24 distributed.> boot ends up with GRUB>>Which kernel? I updated to 4.8.6-201.fc24 last night with no problems.___test mailing list -- test@lists.fedoraproject.orgTo unsubscribe send an email to test-le...@lists.fedoraproject.org ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
It's F24, but possibly concerns more Fxx, Kernel dnf update -> grub>
Hi, dnf update today in F24 results in a bad Kernel, should be the last Kernel for F24 distributed. boot ends up with GRUB> Kind regards ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Re: again F25 on USB Flash medium - with legacy ok - only problem with EFI -Anaconda
Hi, I want to tell, that with the new 65GB Sandisk Ultra stick sent just from Sandisk, the F25 Beta installation is ok. From the talks with Sandisk, I feel that Sandisk knew the reason, why the installation failed with the previous stick, my idea the firmware of the stick has changed before the production of the current one, but who knows except Sandisk. Kind regards -Ursprüngliche Mitteilung- Von: Joerg Lechner An: test Verschickt: Mo, 24 Okt 2016 5:16 pm Betreff: Re: again F25 on USB Flash medium - with legacy ok - only problem with EFI -Anaconda Hi, have told Sandisk the story, they said they don't make sticks to do OS installations and they said i should return the stick, they will send another one, which will work. So we will see, what happens when the stick is replaced. Kind regards -Ursprüngliche Mitteilung- Von: Joerg Lechner An: test Verschickt: So, 23 Okt 2016 10:58 am Betreff: Re: again F25 on USB Flash medium - with legacy ok - only problem with EFI -Anaconda Hi, I have just made a f3 test, the stick is ok, I attach the result. If it's an interference of Acer Laptop, Sandisk USB 65GB stick and Fedora, I have started discussions with Acer and Sandisk, Sandisks first answer will come in a few working days. Acer said that the Bios manufacterer is Inside H2O, if anyone knows Bioses like that. [joerg@linux media]$ su Passwort: [root@linux media]# f3write --start-at=1 --end-at=65 /run/media/joerg/sandiskTest Free space: 57.19 GB Creating file 1.h2w ... OK! Creating file 2.h2w ... OK! , Data OK: 57.17 GB (119900264 sectors) Data LOST: 0.00 Byte (0 sectors) Corrupted: 0.00 Byte (0 sectors) Slightly changed: 0.00 Byte (0 sectors) Overwritten: 0.00 Byte (0 sectors) Average reading speed: 40.26 MB/s [root@linux media]# Kind regards , ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Re: again F25 on USB Flash medium - with legacy ok - only problem with EFI -Anaconda
Hi, have told Sandisk the story, they said they don't make sticks to do OS installations and they said i should return the stick, they will send another one, which will work. So we will see, what happens when the stick is replaced. Kind regards -Ursprüngliche Mitteilung- Von: Joerg Lechner An: test Verschickt: So, 23 Okt 2016 10:58 am Betreff: Re: again F25 on USB Flash medium - with legacy ok - only problem with EFI -Anaconda Hi, I have just made a f3 test, the stick is ok, I attach the result. If it's an interference of Acer Laptop, Sandisk USB 65GB stick and Fedora, I have started discussions with Acer and Sandisk, Sandisks first answer will come in a few working days. Acer said that the Bios manufacterer is Inside H2O, if anyone knows Bioses like that. [joerg@linux media]$ su Passwort: [root@linux media]# f3write --start-at=1 --end-at=65 /run/media/joerg/sandiskTest Free space: 57.19 GB Creating file 1.h2w ... OK! Creating file 2.h2w ... OK! , Data OK: 57.17 GB (119900264 sectors) Data LOST: 0.00 Byte (0 sectors) Corrupted: 0.00 Byte (0 sectors) Slightly changed: 0.00 Byte (0 sectors) Overwritten: 0.00 Byte (0 sectors) Average reading speed: 40.26 MB/s [root@linux media]# Kind regards , ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Re: Taking a screenshot in GNOME (or other) desktop during a app menu is open. How to?
Hi, did You Try "Aktivitaeten" - "Hilfsprogramme" - "Bildschirmfoto" and set the time to take the screenshot to some seconds, or longer. I don't know if this is helpful and working in Your situation, or a silly idea. If this screenshot is not blocked by the behaviour You described. Kind regards -Ursprüngliche Mitteilung- Von: Joachim Backes An: Fedora Test Verschickt: So, 23 Okt 2016 11:52 am Betreff: Re: Taking a screenshot in GNOME (or other) desktop during a app menu is open. How to? On 10/23/16 11:41, Joachim Backes wrote:> Hi all,>> having a problem in F25: I need to take a screenshot on a gnome (or> other) desktop (no wayland!) with alt+print or shift+print keys, during> some application menu of some window is open, but nothing happens. How> can I achive this?> The menu should be included in the screenshot. The screenshot is> performed flawlessly if the menu is closed.>> It seems that this is a X11 problem.>> All comments are welcome.>> Kind regards>> Joachim Backes>Could solve the problem with gnome-screenshot and a delay value > 0Joachim Backes-- Fedora release 25 (Twenty Five)Kernel-4.8.3-300.fc25.x86_64Joachim Backes http://www-user.rhrk.uni-kl.de/~backes/___test mailing list -- test@lists.fedoraproject.orgTo unsubscribe send an email to test-le...@lists.fedoraproject.org ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Re: again F25 on USB Flash medium - with legacy ok - only problem with EFI -Anaconda
0 Validating file 20.h2w ... 2097152/0/ 0/ 0 Validating file 21.h2w ... 2097152/0/ 0/ 0 Validating file 22.h2w ... 2097152/0/ 0/ 0 Validating file 23.h2w ... 2097152/0/ 0/ 0 Validating file 24.h2w ... 2097152/0/ 0/ 0 Validating file 25.h2w ... 2097152/0/ 0/ 0 Validating file 26.h2w ... 2097152/0/ 0/ 0 Validating file 27.h2w ... 2097152/0/ 0/ 0 Validating file 28.h2w ... 2097152/0/ 0/ 0 Validating file 29.h2w ... 2097152/0/ 0/ 0 Validating file 30.h2w ... 2097152/0/ 0/ 0 Validating file 31.h2w ... 2097152/0/ 0/ 0 Validating file 32.h2w ... 2097152/0/ 0/ 0 Validating file 33.h2w ... 2097152/0/ 0/ 0 Validating file 34.h2w ... 2097152/0/ 0/ 0 Validating file 35.h2w ... 2097152/0/ 0/ 0 Validating file 36.h2w ... 2097152/0/ 0/ 0 Validating file 37.h2w ... 2097152/0/ 0/ 0 Validating file 38.h2w ... 2097152/0/ 0/ 0 Validating file 39.h2w ... 2097152/0/ 0/ 0 Validating file 40.h2w ... 2097152/0/ 0/ 0 Validating file 41.h2w ... 2097152/0/ 0/ 0 Validating file 42.h2w ... 2097152/0/ 0/ 0 Validating file 43.h2w ... 2097152/0/ 0/ 0 Validating file 44.h2w ... 2097152/0/ 0/ 0 Validating file 45.h2w ... 2097152/0/ 0/ 0 Validating file 46.h2w ... 2097152/0/ 0/ 0 Validating file 47.h2w ... 2097152/0/ 0/ 0 Validating file 48.h2w ... 2097152/0/ 0/ 0 Validating file 49.h2w ... 2097152/0/ 0/ 0 Validating file 50.h2w ... 2097152/0/ 0/ 0 Validating file 51.h2w ... 2097152/0/ 0/ 0 Validating file 52.h2w ... 2097152/0/ 0/ 0 Validating file 53.h2w ... 2097152/0/ 0/ 0 Validating file 54.h2w ... 2097152/0/ 0/ 0 Validating file 55.h2w ... 2097152/0/ 0/ 0 Validating file 56.h2w ... 2097152/0/ 0/ 0 Validating file 57.h2w ... 2097152/0/ 0/ 0 Validating file 58.h2w ... 362600/0/ 0/ 0 Data OK: 57.17 GB (119900264 sectors) Data LOST: 0.00 Byte (0 sectors) Corrupted: 0.00 Byte (0 sectors) Slightly changed: 0.00 Byte (0 sectors) Overwritten: 0.00 Byte (0 sectors) Average reading speed: 40.26 MB/s [root@linux media]# Kind regards -Ursprüngliche Mitteilung- Von: Chris Murphy An: For testing and quality assurance of Fedora releases Verschickt: Sa, 22 Okt 2016 10:03 pm Betreff: Re: again F25 on USB Flash medium - with legacy ok - only problem with EFI -Anaconda On Sat, Oct 22, 2016 at 12:50 AM, Pavlo Rudyi wrote:> On Fri, 2016-10-21 at 23:30 -0400, Joerg Lechner wrote:>> Hi,>> need advice. Problem installing F25 on an Sandisk Ultra USB 3.0 65GB>> stick in UEFI mode. Works for a 32GB Sandisk Ultra, but not for the>> 65GB stick.>> PC is an Acer Laptop, 2 years old, Win 8.1.>> Tried now netinstall with the 65GB stick for 2 times instead of>> Workstation Live. In the first trial the installation stopped at>> file 1114 of 1413, in the second trial it stopped at 1089 of 1413.>> Try to install minimum OS only, then boot, run `dnf groupinstall> "what_you_want"` and see your problem packages.Without logs there's no way of knowing why something "doesn't work".I've seen quite a lot of SD card reader flip out with anything above32GiB cards, and just plain do weird shit. I have no idea if that's afactor in this case or not. Another thing is there's a lot of fakeflash out in the world. No matter what the brand supposedly is, orwhere you got it, it's worth using f3 on it, or Gnome Multiwriter alsohas a test for fake flash - the manifestation of which is corruptionas the flash loops over itself. So long as only data is being written,this spoofing of the flash can last quite a while only destroyingpreviously written data silently. But as fs metadata gets stepped on,eventually the fs will face plant. Some file systems tolerate this farlonger than others.-- Chris Murphy___test mailing list -- test@lists.fedoraproject.orgTo unsubscribe send an email to test-le...@lists.fedoraproject.org ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Re: again F25 on USB Flash medium - with legacy ok - only problem with EFI -Anaconda
Hi, now I have installed F25 successfully on an external 1TB sata disk, PC always a 2 years old Acer Laptop. There remains only the problem of installing F24 or F25 on a Sandisk Ultra 65GB usb stick. It is not understandable that the F25 installation is ok on a 32GB Sandisk Ultra and not ok on a 65GB Sandisk Ultra. For this I will ask Sandisk. In addition I have tried to do F25 netinstall on the 65GB stick and on the 1TB external disk, didn't work, I think for some reason -I don't know why- connection cut by the server timeout. This was for the 65GB stick the first try at file 1114 from 1413 files, second try at file 1089 from 1413 files, with the 1TB disk it was at selinux-policy-targeted.noarch this was file 1291 of 1413 files. A F24 netinstall installation on the 1TB external disk was successful and F24 bootable. Kind regards -Ursprüngliche Mitteilung- Von: Pavlo Rudyi An: test Verschickt: Sa, 22 Okt 2016 8:50 am Betreff: Re: again F25 on USB Flash medium - with legacy ok - only problem with EFI -Anaconda On Fri, 2016-10-21 at 23:30 -0400, Joerg Lechner wrote:> Hi,> need advice. Problem installing F25 on an Sandisk Ultra USB 3.0 65GB> stick in UEFI mode. Works for a 32GB Sandisk Ultra, but not for the> 65GB stick.> PC is an Acer Laptop, 2 years old, Win 8.1.> Tried now netinstall with the 65GB stick for 2 times instead of> Workstation Live. In the first trial the installation stopped at> file 1114 of 1413, in the second trial it stopped at 1089 of 1413. Try to install minimum OS only, then boot, run `dnf groupinstall"what_you_want"` and see your problem packages.-- ___test mailing list -- test@lists.fedoraproject.orgTo unsubscribe send an email to test-le...@lists.fedoraproject.org ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Re: again F25 on USB Flash medium - with legacy ok - only problem with EFI -Anaconda
Hi, need advice. Problem installing F25 on an Sandisk Ultra USB 3.0 65GB stick in UEFI mode. Works for a 32GB Sandisk Ultra, but not for the 65GB stick. PC is an Acer Laptop, 2 years old, Win 8.1. Tried now netinstall with the 65GB stick for 2 times instead of Workstation Live. In the first trial the installation stopped at file 1114 of 1413, in the second trial it stopped at 1089 of 1413. Is it normal, that the connection breaks down sometimes, or is this more my connection (My internet provuder is a cable TV company), normally I don't see line interruptions. As a further trial I will try to clone my working F25 installation from the 32GB stick to the 65GB stick with Clonezilla, but so far I think I don't use Clonezilla correctly. Did anyone successfully Clone Fedora (F25) with Clonezilla, or another clone program? Reason I get now a 1 TB used internal sata disk, which I want to use as an external drive (USB 2.0 adapter), but previously I have tried an external pata disk (some hundred MB) and got the same error as I get so far with the 65GB USB flash medium in EFI. Legacy is ok. Kind regards -Ursprüngliche Mitteilung- Von: Pavlo Rudyi An: test Verschickt: Fr, 21 Okt 2016 3:02 pm Betreff: Re: again F25 on USB Flash medium - with legacy ok - only problem with EFI -Anaconda > Installation on an Sandisk Ultra 65GB -- Dracut Error, as I have> tested > now, the same error occurs for F22 to F25> Installation in legacy mode on > 32Gb and 65GB for F24 and F25 ok. AFAIR Sandisk Flashes always had some > "strange" problems like a 2xplaying speed in car receivers. Try to check all > packages in chroot via"rpm -Va".> Now I had a live Chat with Acer Support > (Acer says always we make> Windows PCs, linux is not our beer),F** Acer, the > standard of horrible hardware. > Is it possible to transfer a Lecacy > installation to EFI? In the Acer> language by "changing", adding or patching > drivers?> Kind regards> Yep, you need the EFI partition, grub2-efi, shim and > efibootmgr:https://fedoraproject.org/wiki/GRUB_2#Updating_GRUB_2_configuration_on_UEFI_systemsIMHO > this is not UEFI problem.___test > mailing list -- test@lists.fedoraproject.orgTo unsubscribe send an email to > test-le...@lists.fedoraproject.org ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Re: again F25 on USB Flash medium - with legacy ok - only problem with EFI -Anaconda
Hi, currently this problem seems to be only mine. PC: Acer Laptop, 2 years old, Aspire E15 E5-571G Installation of F25 Beta workstation EFI mode on a Sandisk Ultra USB 3.0 32GB flash medium ok (as it was for F22 - F24) Installation on an Sandisk Ultra 65GB -- Dracut Error, as I have tested now, the same error occurs for F22 to F25 Installation in legacy mode on 32Gb and 65GB for F24 and F25 ok. Now I had a live Chat with Acer Support (Acer says always we make Windows PCs, linux is not our beer), but in the Chat today I got: "Grundsätzlich ist nur zu beachten, dass Legacy bei derInstallation von Linux aktiviert ist und nach der Installation jenach Linux Version auf UEFI umgestellt wird." I try to translate: Legacy is in the installing process of Linux activated. And will be repositioned depending on the Linux version to UEFI. "Es gibt Linux Version, die lassen sich nur im Legacy installieren,nach der Installation hat Linux aber grafische Fehler, weswegen manauf UEFI umstellen muss. Das hat an sich mit der Treiberanbindung zutun." Translation: There are Linux versions, which can only be installed in Legacy mode, after installation Linux has grafical errors, therefore it has to transferred to UEFI. The reason is driver connection. So far what I got from Acer. Therefore this problem seems to be at least partly in the interworking of Acer Bios (EFI) and F25 ?Anaconda? So far that's all what I currently know about. Is it possible to transfer a Lecacy installation to EFI? In the Acer language by "changing", adding or patching drivers? Kind regards ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Re: again F25 on USB Flash medium - with legacy ok - only problem with EFI -Anaconda
Hi Richard, it's disappointing, when this problem will be solved after the final release of F25. In this case I will skip F25 and take part again in F26/F27 as soon as this problem will be solved. My Acer laptop is 2 years old, Bios updated (V1.32 published in 2016/04/07). Kind regards -Ursprüngliche Mitteilung- Von: Richard Ryniker An: For testing and quality assurance of Fedora releases Verschickt: Di, 18 Okt 2016 3:37 pm Betreff: Re: again F25 on USB Flash medium - with legacy ok - only problem with EFI -Anaconda >install F25 Beta in legacy mode on an 64GB flash medium. And surprise >it>works.I think this suggests there is some configuration or BIOS problem >withEFI and USB in your machine. Both Chris Murphy and I performedsuccessful >EFI installations, he with Apple and I with Samsung hardware.It may be >impossible to accurately gauge the prevalence of this problemwith the limited >hardware coverage available for pre-release tests. Onthe positive side, you >have discovered a way to avoid the issue that mayhelp other users who >experience similar >difficulty.___test mailing list -- >test@lists.fedoraproject.orgTo unsubscribe send an email to >test-le...@lists.fedoraproject.org ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
again F25 on USB Flash medium - with legacy ok - only problem with EFI -Anaconda
Hi, by case I tried to install F25 Beta in legacy mode on an 64GB flash medium. And surprise it works. This means Anaconda problem when installing F25 on an USB flash medium in EFI mode, but in Legacy mode ok. I run an Acer laptop with Win 8.1 on the internal disk. I think this is good news to find a way to solve this EFI - Anaconda problem. Kind regards ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Re: F25 Beta - still not possible to install on usb connected media
Hi Chris, My system is an Acer laptop, bought 2 years ago with Windows 8.1, also EFI. I use AOL since 1995, at this time I had the choice between Compuserve (more for experts) and AOL (more for non experts). I will think about Your proposal. Kind regards -Ursprüngliche Mitteilung- Von: Chris Murphy An: For testing and quality assurance of Fedora releases Verschickt: Mi, 12 Okt 2016 3:34 am Betreff: Re: F25 Beta - still not possible to install on usb connected media On Tue, Oct 11, 2016 at 10:37 AM, Joerg Lechner wrote:> Hi,> there is still the Anaconda problem of F25 Alpha in F25 Beta. Still not> possible to install on usb connected media.> Same Dracut error message as previously. Will it be possible to use usb> connected media in F25 Final?> Now my problem is only, that I can not take part in the testing of Beta,> except saying there is an Anaconda problem.I can't reproduce this withFedora-Workstation-Live-x86_64-25-20161008.n.0.iso and installing to ablank USB stick (wiped MBR and GPT signatures). I suppose anadditional test is to try installing over this using Reclaim Space.But maybe the problem is fixed or it's a local problem. My system isan EFI Mac, so that could also slightly change the outcome perhaps.Also, I think you should consider a different email service for lists.The header aol is inserting is telling any mail server than honorsdmarc to refuse to relay your emails, so they always end up as spamfor such services. dmarc=fail (p=REJECT dis=NONE) header.from=aol.comhttp://postmaster-blog.aol.com/2014/04/22/aol-mail-updates-dmarc-policy-to-reject/-- Chris Murphy___test mailing list -- test@lists.fedoraproject.orgTo unsubscribe send an email to test-le...@lists.fedoraproject.org ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
F25 Beta - still not possible to install on usb connected media
Hi, there is still the Anaconda problem of F25 Alpha in F25 Beta. Still not possible to install on usb connected media. Same Dracut error message as previously. Will it be possible to use usb connected media in F25 Final? Now my problem is only, that I can not take part in the testing of Beta, except saying there is an Anaconda problem. Kind regards ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Re: F25, how to reclaim space - manually partitioning
Hi Chris, manual partitioning with reclaim space I could do -according to Your help. The installation result on an USB connected medium (in this case USB 3.0 flash medium) is the same as with automatic partitioning and reclaim space, and also when I "clean" the USB flash medium with media writer and following gparted and try installation without reclaiming space-> installation does not work on usb connected media - dracut error report is always the same. Kind regards -Ursprüngliche Mitteilung- Von: Chris Murphy An: For testing and quality assurance of Fedora releases Verschickt: Mo, 3 Okt 2016 10:28 pm Betreff: Re: F25, how to reclaim space - manually partitioning On Mon, Oct 3, 2016 at 6:51 AM, Joerg Lechner wrote:> Hi,> problems in reclaiming space in manual partitioning for F25 Alpha> Workstation installation.> Does anyone know, how to do this? If error and so far not solved,> worthwhile to file a bug?Click on Fedora Linux 25... and it will reveal the mount points forthat installation. Click one and then click the '-' button to deleteit.-- Chris Murphy___test mailing list -- test@lists.fedoraproject.orgTo unsubscribe send an email to test-le...@lists.fedoraproject.org ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fwd: Fedora on usb connected media
Hi, I should note, that the installation with manual partitioning installed showed after installation the same partitions as was, when I had chosen automatic partitioning with reclaim space. My wanted partitioning was ignored. Kind regards -Ursprüngliche Mitteilung- Von: Joerg Lechner An: test Verschickt: So, 2 Okt 2016 8:57 am Betreff: Re: Fedora on usb connected media Hi, tried now wether my installation way causes the error: automatic partitioning with reclaim space. But it isn't, made the installation medium "clean" and used manual partitioning -> same result shown in the dracut error reporting. Kind regards -Ursprüngliche Mitteilung- Von: Richard Ryniker An: For testing and quality assurance of Fedora releases Verschickt: Sa, 1 Okt 2016 8:46 pm Betreff: Re: Fedora on usb connected media Might this be a clue (from your anaconda log)? 13:10:26,938 INFO anaconda: Running post-installation scripts 13:10:26,938 INFO anaconda: Running kickstart %%post script(s) 13:10:29,210 ERR anaconda: Error code 1 running the kickstart script at line 33 13:10:29,210 INFO anaconda: All kickstart %%post script(s) have been runI checked my installation, and have no "Error code 1" message.___test mailing list -- test@lists.fedoraproject.orgTo unsubscribe send an email to test-le...@lists.fedoraproject.org ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Re: Fedora on usb connected media
Hi, tried now wether my installation way causes the error: automatic partitioning with reclaim space. But it isn't, made the installation medium "clean" and used manual partitioning -> same result shown in the dracut error reporting. Kind regards -Ursprüngliche Mitteilung- Von: Richard Ryniker An: For testing and quality assurance of Fedora releases Verschickt: Sa, 1 Okt 2016 8:46 pm Betreff: Re: Fedora on usb connected media Might this be a clue (from your anaconda log)? 13:10:26,938 INFO anaconda: Running post-installation scripts 13:10:26,938 INFO anaconda: Running kickstart %%post script(s) 13:10:29,210 ERR anaconda: Error code 1 running the kickstart script at line 33 13:10:29,210 INFO anaconda: All kickstart %%post script(s) have been runI checked my installation, and have no "Error code 1" message.___test mailing list -- test@lists.fedoraproject.orgTo unsubscribe send an email to test-le...@lists.fedoraproject.org ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Re: Fedora on usb connected media
Hi, installed again with the original F25 Alpha public delivery live Workstation. Here the anaconda.log from liveuser, if You need more logs, no problem, please tell me. Kind regards -Ursprüngliche Mitteilung- Von: Chris Murphy An: For testing and quality assurance of Fedora releases Verschickt: Fr, 30 Sept 2016 10:36 pm Betreff: Re: Fedora on usb connected media On Fri, Sep 30, 2016 at 1:43 PM, Joerg Lechner wrote:> Hi,> tested again.> Acer laptop Aspire E15 E5-571G EFI system> 64GB USB 3.0 flash medium>> Loaded F25 Alpha release Workstation> dnf update kernel -> got Kernel x86_64 4.8.0-0 rc8.git.0.1.fc25> made -according to the production process- a successful F25 build on the> 64GB flash medium> Tried to boot -> again Dracut error with the warnings:> - dev/fedora/root does not exist> - dev/fedora/swap does not exist> - dev/mapper/fedora-root does not exist>> When I looked with F24 onto the F25 build, most partitions did not exist,> i.e. EFI partition was empty, also GRUB2 was nearly empty,> the size of the F25 build was was about 1,1GB.> Kind regardsYou're doing a default autopartition installtaion to the USB media?And it doesn't have an LVM partition for fedora-root and fedora-swapLV's? That's an installer bug, although without logs from theinstaller there's no way to figure out what's going on.-- Chris Murphy___test mailing list -- test@lists.fedoraproject.orgTo unsubscribe send an email to test-le...@lists.fedoraproject.org 00:53:28,680 INFO anaconda: /sbin/anaconda 25.20-1 00:53:28,946 INFO anaconda: 8194716 kB (8002 MB) are available 00:53:28,959 INFO anaconda: check_memory(): total:8002, needed:320, graphical:410 00:53:28,968 INFO anaconda: Not doing 'early exception handler' in live installation 00:53:28,968 INFO anaconda: Not doing 'start audit daemon' in live installation 00:53:28,969 INFO anaconda: anaconda called with cmdline = ['/sbin/anaconda', '--liveinst', '--method=livecd:///dev/mapper/live-base'] 00:53:28,970 INFO anaconda: Default encoding = utf-8 00:53:28,997 WARN anaconda: /usr/lib64/python3.5/optparse.py:999: PendingDeprecationWarning: The KSOption class is deprecated and will be removed in pykickstart-3. Use the argparse module instead. option = self.option_class(*args, **kwargs) 00:53:29,016 WARN anaconda: /usr/lib64/python3.5/site-packages/pyanaconda/pwpolicy.py:101: PendingDeprecationWarning: add_option is deprecated and will be removed in pykickstart-3. Use add_argument instead. op.add_option("--minlen", type="int") 00:53:29,017 INFO anaconda: Parsing kickstart: /usr/share/anaconda/interactive-defaults.ks 00:53:30,071 WARN anaconda: /usr/lib64/python3.5/site-packages/pyanaconda/pwpolicy.py:117: PendingDeprecationWarning: _setToObj has been renamed to set_to_obj. The old name will be removed in a future release. self._setToObj(self.op, opts, pd) 00:53:30,074 WARN anaconda: /usr/lib64/python3.5/optparse.py:999: PendingDeprecationWarning: The KSOption class is deprecated and will be removed in pykickstart-3. Use the argparse module instead. option = self.option_class(*args, **kwargs) 00:53:30,075 DEBUG anaconda: setting locale to: en_US.UTF-8 00:53:30,092 DEBUG anaconda: network: devices found ['enp1s0f1', 'wlp2s0'] 00:53:30,238 DEBUG anaconda: network: ifcfg file for enp1s0f1 not found 00:53:30,290 DEBUG anaconda: network: dumping ifcfg file for default autoconnection on enp1s0f1 00:53:30,301 DEBUG anaconda: network: missing ifcfgs created for devices ['enp1s0f1'] 00:53:30,312 DEBUG anaconda: updating host name localhost.localdomain 00:53:30,332 WARN anaconda: /usr/lib64/python3.5/site-packages/pyanaconda/pwpolicy.py:101: PendingDeprecationWarning: add_option is deprecated and will be removed in pykickstart-3. Use add_argument instead. op.add_option("--minlen", type="int") 00:53:30,333 INFO anaconda: Running Thread: AnaWaitForConnectingNMThread (140476717840128) 00:53:30,347 INFO anaconda: Display mode = g 00:53:30,349 INFO anaconda: 8194716 kB (8002 MB) are available 00:53:30,365 INFO anaconda: check_memory(): total:8002, needed:320, graphical:410 00:53:30,369 INFO anaconda: got 1 NTP servers from DHCP 00:53:30,390 INFO anaconda: Thread Done: AnaWaitForConnectingNMThread (140476717840128) 00:53:30,744 INFO anaconda: Fedora Workstation is the highest priority installclass, using it 00:53:30,835 INFO anaconda: bootloader EFIGRUB on EFI platform 00:53:30,836 INFO anaconda: Detected 7.82 GiB of memory 00:53:30,837 INFO anaconda: Suggested swap size (7.82 GiB) exceeds 10 % of disk space, using 10 % of disk space (0.0) instead. 00:53:30,837 INFO anaconda: Swap attempt of 0.0 00:53:30,838 INFO anaconda: bootloader EFIGRUB on EFI platform 00:53:30,839 INFO anaconda: Running T
Re: Fedora on usb connected media
Hi, tested again. Acer laptop Aspire E15 E5-571G EFI system 64GB USB 3.0 flash medium Loaded F25 Alpha release Workstation dnf update kernel -> got Kernel x86_64 4.8.0-0 rc8.git.0.1.fc25 made -according to the production process- a successful F25 build on the 64GB flash medium Tried to boot -> again Dracut error with the warnings: - dev/fedora/root does not exist - dev/fedora/swap does not exist - dev/mapper/fedora-root does not exist When I looked with F24 onto the F25 build, most partitions did not exist, i.e. EFI partition was empty, also GRUB2 was nearly empty, the size of the F25 build was was about 1,1GB. Kind regards -Ursprüngliche Mitteilung- Von: Chris Murphy An: For testing and quality assurance of Fedora releases Verschickt: Fr, 30 Sept 2016 8:35 pm Betreff: Re: Fedora on usb connected media On Fri, Sep 30, 2016 at 11:07 AM, Richard Ryniker wrote:> Works for me. I used a Samsung 940X laptop and a Sandisk 80GB USB3> external SSD.>> This is a UEFI machine, and I installed using manual partitioning to> re-use partitions on the external device, which contained an old Fedora> 23 system. My purpose here was to preserve an encrypted /home partition.> /boot, /boot/efi, /root and a swap partition were reformatted by the> installer for the F25 system.>> In order to boot from the external drive, I must use the EFI boot loader> - press F10 during start to display a list of boot devices, then select> the SanDisk USB drive.Just a guess, but I think that when the USB stick isn't present, thefirmware is removing what it considers to be a stale NVRAM boot entry.Or it's reordering the boot priority. Otherwise the stick would bebooted by default, if present.> The internal drive for this machine dual boots Fedora 24 and Windows.> Only the external drive was used by Anaconda for the F25 installation.> It might be possible to update GRUB on the internal drive so it can boot> F25 from the external drive, but I rather like the present state where no> change was made to the internal storage medium.The boot manager aspects of GRUB are weak, it still depends on staticconfiguration rather than dynamic discovery. Discovery is difficult asos-prober's existence and history shows. There's a proposed standardto help, but there's no meaningful agreement on it among any of thestake holders.But yes, it's possible to statically get a boot entry into GRUB butthen it appears as if it's a valid option even when the stick isn'tpresent. If the stick has to be recreated/replaced, then that bootentry won't work.-- Chris Murphy___test mailing list -- test@lists.fedoraproject.orgTo unsubscribe send an email to test-le...@lists.fedoraproject.org ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora on usb connected media
Hi, I am using Fedora since a very long time privately, I have started with Redhat, when Fedora came up I switched to Fedora. I use always two systems Windows and Fedora quasi paralell. This means if in a function Windows is better Windows, if Fedora is better Fedora. Partly I had 2 disks in the system one for Windows, one for Fedora. But since I work with laptops I use Fedora on USB connected media, currently Fedora on a 64GB usb 3.0 connected flash medium. Fedora is in this configuration -as I feel- quite quick, as it would be on the internal disk. As mass storage I use the laptop internal Windows disk. I saw that data transfering from the Laptop internal disk to an external disk and vice versa is much more quicker, when it's controlled from Fedora on usb flash medium, then it is, when controlled from the laptop internal disk, there are many examples where fedora is comparable ( or better) as the Apps of Windows. Since development of F24 I have problems with testing in my small corner "Fedora paralell to Windows on usb connected media". In F24 there was no dual boot Windows - Fedora possible - requirement for Final, this had worked always in the previous "editions" of Fedora. Now in F25 it is not possible to install F25 Alpha on an usb connected medium - not on an usb flash medium, not on an external disk. I filed a bug against dracut - dracut showed the error, possibly I should have filed against Anaconda - nearly no reaction on this bug - was not worth the invested work. It might be, that Fedora is mainly used on bigger systems, and not so important for smaller systems, but also on smaller systems there are people, who could learn to love Fedora, if there is more promotion for this part of the computer community. Especially Windows oriented users. Kind regards ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Bug 1371661 - no boot possible from 64GB usb 3.0 flash medium
Hi Adam, this bug I should possibly have routed to Anaconda and not to Dracut. Because so far it's not possible to make a F25 build an an USB connected medium, in my opinion this bug is blocking for Beta Final. Kind regards ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Re: Karma request (F25): anaconda-25.20.1-1.fc25 and NetworkManager-1.4.0-3.fc25
Hi, updated anaconda as proposed: No working production of F25 on USB connected media (flash medium or ext. disk), if again needed I can send the sos-report.txt, but anyway I think there is no change to th previous situation. Kind regards -Ursprüngliche Mitteilung- Von: Adam Williamson An: For testing and quality assurance of Fedora releases Verschickt: Do, 8 Sept 2016 9:56 pm Betreff: Karma request (F25): anaconda-25.20.1-1.fc25 and NetworkManager-1.4.0-3.fc25 Hi folks! There's a couple of significant updates for F25 that it'd benice to get tested and pushed:https://bodhi.fedoraproject.org/updates/FEDORA-2016-ca1b48f89e -NetworkManager-1.4.0-3.fc25https://bodhi.fedoraproject.org/updates/FEDORA-2016-aa89721b07 - anaconda-25.20.1-1.fc25I've confirmed the bug fix for the first one, so if folks can just testtheir network continues working with it as before, that'd be great. Andfor anaconda, I've run the openQA tests on it and they work, so I'mpretty sure it's OK. To test it yourself you can grab a recent nightlylive image - see https://www.happyassassin.net/nightlies.html - bootit, and before running the installer, update the anaconda packages withdnf - you can grab them fromhttp://koji.fedoraproject.org/koji/buildinfo?buildID=799029 . Then runa live install as normal and if it works, you can +1 the update.thanks folks!-- Adam WilliamsonFedora QA Community MonkeyIRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . nethttp://www.happyassassin.net--test mailing listtest@lists.fedoraproject.orgTo unsubscribe:https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
F25 Alpha, not possible to produce an installation on external disk/usb flash medium
Hi, has anyone produced successfully an F25 bootable installation on an USB connected medium? Some days ago I filed a bug: https://bugzilla.redhat.com/show_bug.cgi?id=1371661 Tried to install F25 on an USB flash medium and on an usb connected external pata disk. Production said ok, but no complete data on the external medium. Did anyone except me try this so far? Kind regards -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Kernel 4.7.2 printing problem ... F24
Hi, tried to print from Libreoffice a letter, the print job was in the printer queue, but stopped. Went back to Kernel 4.6.7, the print was ok. My system: Acer E15 E5-571G, Printer Canon Pixma MP540. Kind regards -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: Testing idea: kernel 4.7 for Fedora 23 / Fedora 24
Hi just loaded Kernel 4.7.2 in F24, boot ok, so far no further problems. Acer Laptop E15 E5-571G, F24 on an usb 3.0 flash medium. Kind regards -Ursprüngliche Mitteilung- Von: Adam Williamson An: For testing and quality assurance of Fedora releases Verschickt: Mi, 31 Aug 2016 8:19 am Betreff: Testing idea: kernel 4.7 for Fedora 23 / Fedora 24 Hi folks! Just thought I'd send out a testing idea for anyone who'slooking for something they can do.We currently have kernel 4.7 in updates-testing for Fedora 23 andFedora 24:23 - https://bodhi.fedoraproject.org/updates/FEDORA-2016-f1adaaadc624 - https://bodhi.fedoraproject.org/updates/FEDORA-2016-2e5ebfed6dit's always good to get new kernel releases tested on as much hardwareas possible, so if you haven't done it yet, please try updating thekernel on any machines you have running Fedora 23 or 24. This commandshould do it:dnf --enablerepo=updates-testing update kernel*then you can reboot, and check if all your hardware and your normal useof the system works OK with the new kernel. If it does, give positivefeedback for the update; if not, file a bug and give negative feedbackfor the update, with a link to your bug report. Testing kernel updatesis nice and safe, because even if it doesn't work well, you can justreboot and pick an older kernel from the boot menu - Fedora will alwayskeep three kernels installed, so you have a fallback if the newest onedoesn't work right.Thanks everyone! :)Just as a quick note on other testing topics: for Fedora 25 validation,we'll start getting nightly composes 'nominated' for testing againsoon, working towards the Beta release; Beta freeze is 2016-09-27, so amonth or so to go before we start thinking about Beta RCs. The Fedora25 Test Days should also be starting up soon - Sumantro is away rightnow, but I expect we'll start seeing announcements soon, so look outfor those! And of course, we can always test updates (not just thekernel updates) for 23, 24 and 25. Happy testing :)--test mailing listtest@lists.fedoraproject.orgTo unsubscribe:https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: Testing idea: kernel 4.7 for Fedora 23 / Fedora 24
Hi, have updated the F23 Kernel to 4.7.2 -> so far no problems, an update of F24 is still not possible Kernel 4.7.2 seem so far not to be in updates-testing. Kind regards -Ursprüngliche Mitteilung- Von: Adam Williamson An: For testing and quality assurance of Fedora releases Verschickt: Mi, 31 Aug 2016 8:19 am Betreff: Testing idea: kernel 4.7 for Fedora 23 / Fedora 24 Hi folks! Just thought I'd send out a testing idea for anyone who'slooking for something they can do.We currently have kernel 4.7 in updates-testing for Fedora 23 andFedora 24:23 - https://bodhi.fedoraproject.org/updates/FEDORA-2016-f1adaaadc624 - https://bodhi.fedoraproject.org/updates/FEDORA-2016-2e5ebfed6dit's always good to get new kernel releases tested on as much hardwareas possible, so if you haven't done it yet, please try updating thekernel on any machines you have running Fedora 23 or 24. This commandshould do it:dnf --enablerepo=updates-testing update kernel*then you can reboot, and check if all your hardware and your normal useof the system works OK with the new kernel. If it does, give positivefeedback for the update; if not, file a bug and give negative feedbackfor the update, with a link to your bug report. Testing kernel updatesis nice and safe, because even if it doesn't work well, you can justreboot and pick an older kernel from the boot menu - Fedora will alwayskeep three kernels installed, so you have a fallback if the newest onedoesn't work right.Thanks everyone! :)Just as a quick note on other testing topics: for Fedora 25 validation,we'll start getting nightly composes 'nominated' for testing againsoon, working towards the Beta release; Beta freeze is 2016-09-27, so amonth or so to go before we start thinking about Beta RCs. The Fedora25 Test Days should also be starting up soon - Sumantro is away rightnow, but I expect we'll start seeing announcements soon, so look outfor those! And of course, we can always test updates (not just thekernel updates) for 23, 24 and 25. Happy testing :)--test mailing listtest@lists.fedoraproject.orgTo unsubscribe:https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: Testing idea: kernel 4.7 for Fedora 23 / Fedora 24
Hi, tried F23, no kernel 4.7. see: [root@linux joerg]# dnf --enablerepo=updates-testing update kernel* Fedora 23 - x86_64 - Test Updates 5.2 MB/s | 2.4 MB 00:00 Abhängigkeiten sind aufgelöst. Nichts zu tun. Komplett! [root@linux joerg]# dnf info kernel Letzte Prüfung auf abgelaufene Metadaten: vor 0:02:00 am Wed Aug 31 08:55:44 2016. Installierte Pakete Name: kernel Arch: x86_64 Epoch : 0 Version : 4.6.4 Release : 201.fc23 Größe : 0.0 Paketquelle : @System Aus Paketqu : updates Zusammenfas : The Linux kernel URL : http://www.kernel.org/ Lizenz : GPLv2 and Redistributable, no modification permitted Beschreibun : The kernel meta package Name: kernel Arch: x86_64 Epoch : 0 Version : 4.6.5 Release : 200.fc23 Größe : 0.0 Paketquelle : @System Aus Paketqu : updates Zusammenfas : The Linux kernel URL : http://www.kernel.org/ Lizenz : GPLv2 and Redistributable, no modification permitted Beschreibun : The kernel meta package Name: kernel Arch: x86_64 Epoch : 0 Version : 4.6.7 Release : 200.fc23 Größe : 0.0 Paketquelle : @System Aus Paketqu : updates Zusammenfas : The Linux kernel URL : http://www.kernel.org/ Lizenz : GPLv2 and Redistributable, no modification permitted Beschreibun : The kernel meta package [root@linux joerg]# Kind regards -Ursprüngliche Mitteilung- Von: Adam Williamson An: For testing and quality assurance of Fedora releases Verschickt: Mi, 31 Aug 2016 8:19 am Betreff: Testing idea: kernel 4.7 for Fedora 23 / Fedora 24 Hi folks! Just thought I'd send out a testing idea for anyone who'slooking for something they can do.We currently have kernel 4.7 in updates-testing for Fedora 23 andFedora 24:23 - https://bodhi.fedoraproject.org/updates/FEDORA-2016-f1adaaadc624 - https://bodhi.fedoraproject.org/updates/FEDORA-2016-2e5ebfed6dit's always good to get new kernel releases tested on as much hardwareas possible, so if you haven't done it yet, please try updating thekernel on any machines you have running Fedora 23 or 24. This commandshould do it:dnf --enablerepo=updates-testing update kernel*then you can reboot, and check if all your hardware and your normal useof the system works OK with the new kernel. If it does, give positivefeedback for the update; if not, file a bug and give negative feedbackfor the update, with a link to your bug report. Testing kernel updatesis nice and safe, because even if it doesn't work well, you can justreboot and pick an older kernel from the boot menu - Fedora will alwayskeep three kernels installed, so you have a fallback if the newest onedoesn't work right.Thanks everyone! :)Just as a quick note on other testing topics: for Fedora 25 validation,we'll start getting nightly composes 'nominated' for testing againsoon, working towards the Beta release; Beta freeze is 2016-09-27, so amonth or so to go before we start thinking about Beta RCs. The Fedora25 Test Days should also be starting up soon - Sumantro is away rightnow, but I expect we'll start seeing announcements soon, so look outfor those! And of course, we can always test updates (not just thekernel updates) for 23, 24 and 25. Happy testing :)--test mailing listtest@lists.fedoraproject.orgTo unsubscribe:https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: Testing idea: kernel 4.7 for Fedora 23 / Fedora 24
Hi, tried dnf --enablerepo=updates-testing update kernel* for F24, did't get kernel 4.7. Have I to enable too something with Bodhi? Kind regards -Original Message- From: Adam Williamson To: For testing and quality assurance of Fedora releases Sent: Wed, Aug 31, 2016 8:19 am Subject: Testing idea: kernel 4.7 for Fedora 23 / Fedora 24 Hi folks! Just thought I'd send out a testing idea for anyone who'slooking for something they can do.We currently have kernel 4.7 in updates-testing for Fedora 23 andFedora 24:23 - https://bodhi.fedoraproject.org/updates/FEDORA-2016-f1adaaadc624 - https://bodhi.fedoraproject.org/updates/FEDORA-2016-2e5ebfed6dit's always good to get new kernel releases tested on as much hardwareas possible, so if you haven't done it yet, please try updating thekernel on any machines you have running Fedora 23 or 24. This commandshould do it:dnf --enablerepo=updates-testing update kernel*then you can reboot, and check if all your hardware and your normal useof the system works OK with the new kernel. If it does, give positivefeedback for the update; if not, file a bug and give negative feedbackfor the update, with a link to your bug report. Testing kernel updatesis nice and safe, because even if it doesn't work well, you can justreboot and pick an older kernel from the boot menu - Fedora will alwayskeep three kernels installed, so you have a fallback if the newest onedoesn't work right.Thanks everyone! :)Just as a quick note on other testing topics: for Fedora 25 validation,we'll start getting nightly composes 'nominated' for testing againsoon, working towards the Beta release; Beta freeze is 2016-09-27, so amonth or so to go before we start thinking about Beta RCs. The Fedora25 Test Days should also be starting up soon - Sumantro is away rightnow, but I expect we'll start seeing announcements soon, so look outfor those! And of course, we can always test updates (not just thekernel updates) for 23, 24 and 25. Happy testing :)--test mailing listtest@lists.fedoraproject.orgTo unsubscribe:https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: Announcing the release of Fedora 25 Alpha!
Hi, filed bug: https://bugzilla.redhat.com//show_bug.cgi?id=1371661 wanted to add rdsosreport.txt, but is 1,9MB in size, this will not work, sorry Kind regards -Ursprüngliche Mitteilung- Von: Joerg Lechner An: users ; test ; awilliam Verschickt: Di, 30 Aug 2016 5:42 pm Betreff: Re: Announcing the release of Fedora 25 Alpha! Hi, as desribed in thread: Re: [Test-Announce] Fedora 25 Candidate Alpha-1.2 Available Now! No boot with USB flash medium possible --> dracut I will collect a log and file a bug. Kind regards -Ursprüngliche Mitteilung- Von: Dennis Gilmore An: test-announce Cc: announce ; devel-announce Verschickt: Di, 30 Aug 2016 4:15 pm Betreff: Announcing the release of Fedora 25 Alpha! The Fedora Project is pleased to announce the immediate availability of the Fedora 25 Alpha, an important milestone on the road to our Fedora 25 release in November. Download the prerelease from our Get Fedora site: * https://getfedora.org/en/workstation/prerelease/ * https://getfedora.org/en/server/prerelease/ * https://getfedora.org/en/cloud/prerelease/ Or, check out one of our popular variants: * https://spins.fedoraproject.org/prerelease * https://labs.fedoraproject.org/prerelease * https://arm.fedoraproject.org/prerelease == Alternative Architectures == We are also simultaneously releasing the F25 Alpha for Power64 and 64-bit ARM (AArch64). These are available from: https://download.fedoraproject.org/pub/fedora-secondary/releases/test/ 25_Alpha/ == What is the Alpha release? == The Alpha release contains all the features of Fedora 25's editions in a form that anyone can help test. This testing, guided by the Fedora QA team, helps us target and identify bugs. When these bugs are fixed, we make a Beta release available. A Beta release is code-complete and bears a very strong resemblance to the third and final release. The final release of Fedora 25 is expected in November. If you take the time to download and try out the Alpha, you can check and make sure the things that are important to YOU are working. Every bug you find and report doesn't just help you, it improves the experience of millions of Fedora users worldwide! Together, we can make Fedora rock-solid. We have a culture of coordinating new features and pushing fixes upstream as much as we can, and your feedback improves not only Fedora, but Linux and Free software as a whole. * https://fedoraproject.org/wiki/Releases/25/Schedule == Issues and Details == Since this is an alpha release, we expect that you may encounter bugs or missing features. To report issues encountered during testing, contact the Fedora QA team via the mailing list or in #fedora-qa on Freenode. As testing progresses, common issues are tracked on the Common F25 Bugs page. * https://fedoraproject.org/wiki/Common_F25_bugs For tips on reporting a bug effectively, read "how to file a bug report". * https://fedoraproject.org/wiki/How_to_file_a_bug_report == Release Schedule == The full release schedule is available on the Fedora wiki: * https://fedoraproject.org/wiki/Releases/25/Schedule The current schedule calls for a beta release towards the middle of October, and the final release in November. Be aware that these dates are development targets. Some projects release on a set date regardless of feature completeness or bugs; others wait until certain thresholds for functionality or testing are met. Fedora uses a hybrid model, with milestones subject to adjustment. This allows us to make releases with new features and newly- integrated and updated upstream software while also retaining high quality. Enjoy Fedora Release Engineering (Dennis, Peter, Kevin, Mohan, Adam, Randy)--announce mailing listannounce@lists.fedoraproject.orghttps://lists.fedoraproject.org/admin/lists/annou...@lists.fedoraproject.org -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: Announcing the release of Fedora 25 Alpha!
Hi, as desribed in thread: Re: [Test-Announce] Fedora 25 Candidate Alpha-1.2 Available Now! No boot with USB flash medium possible --> dracut I will collect a log and file a bug. Kind regards -Ursprüngliche Mitteilung- Von: Dennis Gilmore An: test-announce Cc: announce ; devel-announce Verschickt: Di, 30 Aug 2016 4:15 pm Betreff: Announcing the release of Fedora 25 Alpha! The Fedora Project is pleased to announce the immediate availability of the Fedora 25 Alpha, an important milestone on the road to our Fedora 25 release in November. Download the prerelease from our Get Fedora site: * https://getfedora.org/en/workstation/prerelease/ * https://getfedora.org/en/server/prerelease/ * https://getfedora.org/en/cloud/prerelease/ Or, check out one of our popular variants: * https://spins.fedoraproject.org/prerelease * https://labs.fedoraproject.org/prerelease * https://arm.fedoraproject.org/prerelease == Alternative Architectures == We are also simultaneously releasing the F25 Alpha for Power64 and 64-bit ARM (AArch64). These are available from: https://download.fedoraproject.org/pub/fedora-secondary/releases/test/ 25_Alpha/ == What is the Alpha release? == The Alpha release contains all the features of Fedora 25's editions in a form that anyone can help test. This testing, guided by the Fedora QA team, helps us target and identify bugs. When these bugs are fixed, we make a Beta release available. A Beta release is code-complete and bears a very strong resemblance to the third and final release. The final release of Fedora 25 is expected in November. If you take the time to download and try out the Alpha, you can check and make sure the things that are important to YOU are working. Every bug you find and report doesn't just help you, it improves the experience of millions of Fedora users worldwide! Together, we can make Fedora rock-solid. We have a culture of coordinating new features and pushing fixes upstream as much as we can, and your feedback improves not only Fedora, but Linux and Free software as a whole. * https://fedoraproject.org/wiki/Releases/25/Schedule == Issues and Details == Since this is an alpha release, we expect that you may encounter bugs or missing features. To report issues encountered during testing, contact the Fedora QA team via the mailing list or in #fedora-qa on Freenode. As testing progresses, common issues are tracked on the Common F25 Bugs page. * https://fedoraproject.org/wiki/Common_F25_bugs For tips on reporting a bug effectively, read "how to file a bug report". * https://fedoraproject.org/wiki/How_to_file_a_bug_report == Release Schedule == The full release schedule is available on the Fedora wiki: * https://fedoraproject.org/wiki/Releases/25/Schedule The current schedule calls for a beta release towards the middle of October, and the final release in November. Be aware that these dates are development targets. Some projects release on a set date regardless of feature completeness or bugs; others wait until certain thresholds for functionality or testing are met. Fedora uses a hybrid model, with milestones subject to adjustment. This allows us to make releases with new features and newly- integrated and updated upstream software while also retaining high quality. Enjoy Fedora Release Engineering (Dennis, Peter, Kevin, Mohan, Adam, Randy)--announce mailing listannounce@lists.fedoraproject.orghttps://lists.fedoraproject.org/admin/lists/annou...@lists.fedoraproject.org -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: [Test-Announce] Fedora 25 Candidate Alpha-1.2 Available Now!
Hi Adam, problem F25 Alpha no boot after installation to usb 3.0 flash medium. As attachment rdsosreport.txt. I hope it's helpful. If needed I can do further testing in this problem, if it's a general problem and not only mine problem. Kind regards -Ursprüngliche Mitteilung- Von: Adam Williamson An: Joerg Lechner ; test Verschickt: Fr, 26 Aug 2016 8:18 am Betreff: Re: [Test-Announce] Fedora 25 Candidate Alpha-1.2 Available Now! On Fri, 2016-08-26 at 02:12 -0400, Joerg Lechner wrote: > Hi Adam, > is it still useful to investigate this boot problem with usb flash > medium? I have tried to copy rdsosreport.txt to an usb flash medium > from dracut emergency state (cp /rdsosreport.txt dev/sdb1, sdb1 > formatted in ext4 and as second trial in fat32) unsuccessfully, there > was something doing with sdb1, but afterwards I could not read sdb1, > gparted showed unknown system on sdb1, no fat32, no ext4. The only > thing which I could do is taking screenshots with the smartphone. Is > this worthwhile to or did You see the same problem on Your system? > Kind regards I didn't try it yet. The easiest thing is probably to copy it to another USB stick. Or if you have a network cable connected, the network should come up and you should be able to copy the file off that way. + cat /lib/dracut/dracut-044-76.fc25 dracut-044-76.fc25 + cat /proc/cmdline BOOT_IMAGE=/vmlinuz-4.8.0-0.rc2.git3.1.fc25.x86_64 root=/dev/mapper/fedora-root ro rd.lvm.lv=fedora/root rd.lvm.lv=fedora/swap rhgb quiet LANG=de_DE.UTF-8 + '[' -f /etc/cmdline ']' + for _i in '/etc/cmdline.d/*.conf' + '[' -f '/etc/cmdline.d/*.conf' ']' + break + cat /proc/self/mountinfo 0 0 0:1 / / rw shared:1 - rootfs rootfs rw 18 0 0:18 / /sys rw,nosuid,nodev,noexec,relatime shared:2 - sysfs sysfs rw 19 0 0:4 / /proc rw,nosuid,nodev,noexec,relatime shared:8 - proc proc rw 20 0 0:6 / /dev rw,nosuid shared:9 - devtmpfs devtmpfs rw,size=4018900k,nr_inodes=1004725,mode=755 21 18 0:19 / /sys/kernel/security rw,nosuid,nodev,noexec,relatime shared:3 - securityfs securityfs rw 22 20 0:20 / /dev/shm rw,nosuid,nodev shared:10 - tmpfs tmpfs rw 23 20 0:21 / /dev/pts rw,nosuid,noexec,relatime shared:11 - devpts devpts rw,gid=5,mode=620,ptmxmode=000 24 0 0:22 / /run rw,nosuid,nodev shared:12 - tmpfs tmpfs rw,mode=755 25 18 0:23 / /sys/fs/cgroup ro,nosuid,nodev,noexec shared:4 - tmpfs tmpfs ro,mode=755 26 25 0:24 / /sys/fs/cgroup/systemd rw,nosuid,nodev,noexec,relatime shared:5 - cgroup cgroup rw,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd 27 18 0:25 / /sys/fs/pstore rw,nosuid,nodev,noexec,relatime shared:6 - pstore pstore rw 28 18 0:26 / /sys/firmware/efi/efivars rw,nosuid,nodev,noexec,relatime shared:7 - efivarfs efivarfs rw 29 25 0:27 / /sys/fs/cgroup/blkio rw,nosuid,nodev,noexec,relatime shared:13 - cgroup cgroup rw,blkio 30 25 0:28 / /sys/fs/cgroup/cpuset rw,nosuid,nodev,noexec,relatime shared:14 - cgroup cgroup rw,cpuset 31 25 0:29 / /sys/fs/cgroup/hugetlb rw,nosuid,nodev,noexec,relatime shared:15 - cgroup cgroup rw,hugetlb 32 25 0:30 / /sys/fs/cgroup/pids rw,nosuid,nodev,noexec,relatime shared:16 - cgroup cgroup rw,pids 33 25 0:31 / /sys/fs/cgroup/cpu,cpuacct rw,nosuid,nodev,noexec,relatime shared:17 - cgroup cgroup rw,cpu,cpuacct 34 25 0:32 / /sys/fs/cgroup/net_cls,net_prio rw,nosuid,nodev,noexec,relatime shared:18 - cgroup cgroup rw,net_cls,net_prio 35 25 0:33 / /sys/fs/cgroup/devices rw,nosuid,nodev,noexec,relatime shared:19 - cgroup cgroup rw,devices 36 25 0:34 / /sys/fs/cgroup/perf_event rw,nosuid,nodev,noexec,relatime shared:20 - cgroup cgroup rw,perf_event 37 25 0:35 / /sys/fs/cgroup/freezer rw,nosuid,nodev,noexec,relatime shared:21 - cgroup cgroup rw,freezer 38 25 0:36 / /sys/fs/cgroup/memory rw,nosuid,nodev,noexec,relatime shared:22 - cgroup cgroup rw,memory 61 18 0:37 / /sys/kernel/config rw,relatime shared:23 - configfs configfs rw + cat /proc/mounts rootfs / rootfs rw 0 0 sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0 proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0 devtmpfs /dev devtmpfs rw,nosuid,size=4018900k,nr_inodes=1004725,mode=755 0 0 securityfs /sys/kernel/security securityfs rw,nosuid,nodev,noexec,relatime 0 0 tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0 devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0 tmpfs /run tmpfs rw,nosuid,nodev,mode=755 0 0 tmpfs /sys/fs/cgroup tmpfs ro,nosuid,nodev,noexec,mode=755 0 0 cgroup /sys/fs/cgroup/systemd cgroup rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd 0 0 pstore /sys/fs/pstore pstore rw,nosuid,nodev,noexec,relatime 0 0 efivarfs /sys/firmware/efi/efivars efivarfs rw,nosuid,nodev,noexec,relatime 0 0 cgroup /sys/fs/cgroup/blkio cgroup rw,nosuid,nodev,noexec,relatime,blkio 0 0 cgroup /sys/fs/cgroup/cpuset cgroup rw,nosuid,nodev,noexec,relatime,cpuset 0
Re: [Test-Announce] Fedora 25 Candidate Alpha-1.2 Available Now!
Hi Adam, is it still useful to investigate this boot problem with usb flash medium? I have tried to copy rdsosreport.txt to an usb flash medium from dracut emergency state (cp /rdsosreport.txt dev/sdb1, sdb1 formatted in ext4 and as second trial in fat32) unsuccessfully, there was something doing with sdb1, but afterwards I could not read sdb1, gparted showed unknown system on sdb1, no fat32, no ext4. The only thing which I could do is taking screenshots with the smartphone. Is this worthwhile to or did You see the same problem on Your system? Kind regards -Ursprüngliche Mitteilung- Von: Adam Williamson An: For testing and quality assurance of Fedora releases Verschickt: Do, 25 Aug 2016 5:21 pm Betreff: Re: [Test-Announce] Fedora 25 Candidate Alpha-1.2 Available Now! On Thu, 2016-08-25 at 09:28 -0400, Joerg Lechner wrote:> Hi,> installed F25 Alpha-1.2 on an 64GB USB 3.0 flash medium (Laptop Acer> E15 E5-571G, 8GB Ram). Tried to boot twice. Got a Dracut timeout. See> screenshot attached. The production process seemed to be ok. I will> produce again and tell if this is ok. In the installation process I> seemed to have problems in deleting the windows data of the flash> medium. but this can also have been my typing error in the> installation process.> In my opinion the production process was ok, as with F24. Does anyone> see similar things?> Kind regardsAll that tells us is it can't find the install, basically. We'd needmore information (the journal, the contents of the installed system'sfstab, at least) to figure out why. Installing to a USB stick is kindof a corner case, I'm not sure how many people test it. I might try itlater today, though, so if I do I'll see if the same happens here.--test mailing listtest@lists.fedoraproject.orgTo unsubscribe:https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: [Test-Announce] Fedora 25 Candidate Alpha-1.2 Available Now!
Hi, in etc I can only find a file named fstab.empty, which is really empty. There is a file /run/initramfs/rdsosreport.txt, I will look tomorrow how to prepare it as a mail-attachment. Kind regards -Ursprüngliche Mitteilung- Von: Adam Williamson An: For testing and quality assurance of Fedora releases Verschickt: Do, 25 Aug 2016 5:21 pm Betreff: Re: [Test-Announce] Fedora 25 Candidate Alpha-1.2 Available Now! On Thu, 2016-08-25 at 09:28 -0400, Joerg Lechner wrote:> Hi,> installed F25 Alpha-1.2 on an 64GB USB 3.0 flash medium (Laptop Acer> E15 E5-571G, 8GB Ram). Tried to boot twice. Got a Dracut timeout. See> screenshot attached. The production process seemed to be ok. I will> produce again and tell if this is ok. In the installation process I> seemed to have problems in deleting the windows data of the flash> medium. but this can also have been my typing error in the> installation process.> In my opinion the production process was ok, as with F24. Does anyone> see similar things?> Kind regardsAll that tells us is it can't find the install, basically. We'd needmore information (the journal, the contents of the installed system'sfstab, at least) to figure out why. Installing to a USB stick is kindof a corner case, I'm not sure how many people test it. I might try itlater today, though, so if I do I'll see if the same happens here.--test mailing listtest@lists.fedoraproject.orgTo unsubscribe:https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: devedeng problem F24 -> could this also happen to F25 ?
Hi, I attach the journalctl for the Gnome session, when the error occured, possibly it's a hint for someone who can understand this, the erroneous session is logged at 8:45:59 -- Logs begin at Di 2016-06-21 20:25:45 CEST, end at Sa 2016-08-20 13:06:05 CEST. -- Aug 20 08:45:59 linux.fritz.box org.gnome.Shell.desktop[1145]: (gnome-shell:1145): Clutter-WARNING **: Could not open device /dev/input/event14: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Operation not permitted Aug 20 08:45:59 linux.fritz.box org.gnome.Shell.desktop[1145]: glamor: EGL version 1.4 (DRI2): Aug 20 08:46:03 linux.fritz.box org.gnome.Shell.desktop[1145]: (gnome-shell:1145): Gjs-WARNING **: JS ERROR: could not get remote objects for service org.gnome.SettingsDaemon.Smartcard path /org/gnome/SettingsDaemon/Smartcard: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SettingsDaemon.Smartcard was not provided by any .service files Aug 20 08:46:03 linux.fritz.box org.gnome.Shell.desktop[1145]: _proxyInvoker/asyncCallback@resource:///org/gnome/gjs/modules/overrides/Gio.js:83 Aug 20 08:46:10 linux.fritz.box org.gnome.Shell.desktop[1615]: (gnome-shell:1615): Gjs-WARNING **: JS ERROR: could not get remote objects for service org.gnome.SettingsDaemon.Smartcard path /org/gnome/SettingsDaemon/Smartcard: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SettingsDaemon.Smartcard was not provided by any .service files Aug 20 08:46:10 linux.fritz.box org.gnome.Shell.desktop[1615]: _proxyInvoker/asyncCallback@resource:///org/gnome/gjs/modules/overrides/Gio.js:83 Aug 20 08:46:11 linux.fritz.box gnome-shell[1615]: GNOME Shell started at Sat Aug 20 2016 08:46:09 GMT+0200 (CEST) Aug 20 08:46:11 linux.fritz.box org.gnome.Shell.desktop[1615]: (gnome-shell:1615): mutter-WARNING **: STACK_OP_ADD: window 0x121 already in stack Aug 20 08:46:11 linux.fritz.box org.gnome.Shell.desktop[1615]: (gnome-shell:1615): mutter-WARNING **: STACK_OP_ADD: window 0x121 already in stack Aug 20 08:46:13 linux.fritz.box org.gnome.Shell.desktop[1615]: Gjs-Message: JS LOG: The property brightness doesn't seem to be a normal object property of [0x559d0ae30840 StWidget] or a registered special property Aug 20 08:46:13 linux.fritz.box org.gnome.Shell.desktop[1615]: Gjs-Message: JS LOG: The property vignette_sharpness doesn't seem to be a normal object property of [0x559d0ae30840 StWidget] or a registered special property Aug 20 10:04:21 linux.fritz.box org.gnome.Shell.desktop[1615]: Gjs-Message: JS LOG: The property brightness doesn't seem to be a normal object property of [0x559d096f6ce0 StWidget] or a registered special property Aug 20 10:04:21 linux.fritz.box org.gnome.Shell.desktop[1615]: Gjs-Message: JS LOG: The property vignette_sharpness doesn't seem to be a normal object property of [0x559d096f6ce0 StWidget] or a registered special property Aug 20 10:28:48 linux.fritz.box org.gnome.Shell.desktop[1615]: Gjs-Message: JS LOG: The property brightness doesn't seem to be a normal object property of [0x559d0cc841f0 StWidget] or a registered special property Aug 20 10:28:48 linux.fritz.box org.gnome.Shell.desktop[1615]: Gjs-Message: JS LOG: The property vignette_sharpness doesn't seem to be a normal object property of [0x559d0cc841f0 StWidget] or a registered special property ~ ~ ~ ~ ~ ~ ~ lines 1-16/16 (END) Kind regards , -Ursprüngliche Mitteilung- Von: Joerg Lechner An: test Verschickt: Sa, 20 Aug 2016 11:39 am Betreff: Re: devedeng problem F24 -> could this also happen to F25 ? Hi, repeated the same procedure, which led to the Gnome (GDM?) break down, I did totally the same as in the erroneous production. This time the production was ok. As I mentioned, when Gnome (GDM?) breaks down the movie.iso is produced totally ok, I could burn it with Brasero, the iso is ok untill the end of the film. So this error seems to appear statstically, estimated approximately, 1 in 10 runs is nok, How can I "catch" this error? Do I have a sufficient logfile after the breakdown and reboot? When the screen is black and the "system lamp" says the system is running, how can I try to return to GDM? Kind regards -Ursprüngliche Mitteilung- Von: Joerg Lechner An: test Verschickt: Sa, 20 Aug 2016 9:16 am Betreff: Re: devedeng problem F24 -> could this also happen to F25 ? Hi, the "black screen" in converting a mp4 film to iso with devedeNG happened again, after it had previously ok. Size of flash medium seems to be ok, here df -h after booting the system again after the crash (system was running, but black screen, possibly GDM problem?). The size of the flash medium is 32GB. I add 2 screenshots to show the size of the movie directory and the movie.iso. How can I investigate a situation, where GDM? has crashed? [root@linux joerg]# df -h Dateisys
Re: devedeng problem F24 -> could this also happen to F25 ?
Hi, repeated the same procedure, which led to the Gnome (GDM?) break down, I did totally the same as in the erroneous production. This time the production was ok. As I mentioned, when Gnome (GDM?) breaks down the movie.iso is produced totally ok, I could burn it with Brasero, the iso is ok untill the end of the film. So this error seems to appear statstically, estimated approximately, 1 in 10 runs is nok, How can I "catch" this error? Do I have a sufficient logfile after the breakdown and reboot? When the screen is black and the "system lamp" says the system is running, how can I try to return to GDM? Kind regards -Ursprüngliche Mitteilung- Von: Joerg Lechner An: test Verschickt: Sa, 20 Aug 2016 9:16 am Betreff: Re: devedeng problem F24 -> could this also happen to F25 ? Hi, the "black screen" in converting a mp4 film to iso with devedeNG happened again, after it had previously ok. Size of flash medium seems to be ok, here df -h after booting the system again after the crash (system was running, but black screen, possibly GDM problem?). The size of the flash medium is 32GB. I add 2 screenshots to show the size of the movie directory and the movie.iso. How can I investigate a situation, where GDM? has crashed? [root@linux joerg]# df -h Dateisystem Größe Benutzt Verf. Verw% Eingehängt auf devtmpfs 3,9G 0 3,9G0% /dev tmpfs 3,9G412K 3,9G1% /dev/shm tmpfs 3,9G1,7M 3,9G1% /run tmpfs 3,9G 0 3,9G0% /sys/fs/cgroup /dev/mapper/fedora_linux-root 25G 16G 7,8G 67% / tmpfs 3,9G124K 3,9G1% /tmp /dev/sdb2 477M157M 291M 36% /boot /dev/sdb1 200M8,4M 192M5% /boot/efi tmpfs 791M 16K 791M1% /run/user/42 tmpfs 791M 20K 791M1% /run/user/1000 /dev/sr0 2,2G2,2G 0 100% /run/media/joerg/DVDVIDEO [root@linux joerg]# Kind regards -Ursprüngliche Mitteilung- Von: Sérgio Basto An: test Verschickt: Mi, 17 Aug 2016 5:52 pm Betreff: Re: devedeng problem F24 -> could this also happen to F25 ? On Qua, 2016-08-17 at 08:25 -0400, Joerg Lechner wrote:> Hi, > after production of DVD iso out of MP4 file, F24 breaks down, no> shutdown, the screen is dark and the blue lamp, which signals the> system is on, is still on? The produced iso is complete and can be> burned successfully with Brasero. Is this Gnome? GDM?> This is new since the last 2 Kernels or updates (modules?). How can I> read a log about this breakdown?The only thing that devedeng can do to break down your computer , isfull the disk ... what is output of df -h ? to check kernel: dmesg and journalctl -p err -b anyway try boot with one kernel 4.5 , instead 4.6 ... see if helps > My system: Acer Laptop, 6GB Ram> SW:> [joerg@linux ~]$ dnf info devedeng> Letzte Prüfung auf abgelaufene Metadaten: vor 0:01:49 am Wed Aug 17> 14:11:07 2016.> Installierte Pakete> Name: devedeng> Arch: noarch> Epoch : 0> Version : 4.7.1> Release : 1.fc24> Größe : 3.2 M> Paketquelle : @System> Aus Paketqu : rpmfusion-free-updates> Zusammenfas : A program to create video DVDs and CDs (VCD, sVCD or> CVD)> URL : http://www.rastersoft.com/programas/devede.html> Lizenz : GPLv3+> Beschreibun : DevedeNG is a program to create video DVDs and CDs> (VCD, sVCD or> : CVD), suitable for home players, from any number of> video files,> : in any of the formats supported by FFMpeg.> : > : The suffix NG is because it is a rewrite from scratch> of the old> : Devede, to work with Python3 and Gtk3, and with a new> internal> : architecture that allows to expand it and easily add> new features.> > [joerg@linux ~]$ dnf info kernel> Letzte Prüfung auf abgelaufene Metadaten: vor 0:02:12 am Wed Aug 17> 14:11:07 2016.> Installierte Pakete> Name: kernel> Arch: x86_64> Epoch : 0> Version : 4.6.4> Release : 301.fc24> Größe : 0.0 > Paketquelle : @System> Aus Paketqu : updates> Zusammenfas : The Linux kernel> URL : http://www.kernel.org/> Lizenz : GPLv2 and Redistributable, no modification permitted> Beschreibun : The kernel meta package> > Name: kernel> Arch: x86_64> Epoch : 0> Version : 4.6.5> Release : 300.fc24> Größe : 0.0 > Paketquelle : @System> Aus Paketqu : updates> Zusammenfas : The Linux kernel> URL : http://www.kernel.org/> Lizenz : GPLv2 and Re
Re: something curious Media Writer -- Gparted
Hi, that's what I see with Gparted (screenshot), trying several menues of Gparted I can draw it back to 29,5GB, but after new iso with Fedora Media Writer this impossible size over 100GB is shown again. It's a Hama flash medium 32GB. Is this caused by Media Writer? Or is something hidden (i.e chip originally planned for 128GB but because of bad quality only sold for 32GB)? Kind regards -Ursprüngliche Mitteilung----- Von: Joerg Lechner An: test Verschickt: Do, 18 Aug 2016 9:00 am Betreff: something curious Media Writer -- Gparted Hi, could not delete a full F24 installation on an 32GB USB flash drive with Gparted, therefore I used a workaround with building an iso with the Fedora Media Writer on this flash drive. Afterwards I deleted this iso with Gparted. Delete was successful, but Gparted showed now a flash drive with 117GB and it was not possible to get a working partition. Using the restore to factory settings with Media Writer repaired the flash drive again to 32GB. Normally Gparted -as I have seen so far- works correctly. Is there an error in setting the "correct end" of the flash drive (in my case 32GB) in the production of an Fedora iso? Kind regards -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
something curious Media Writer -- Gparted
Hi, could not delete a full F24 installation on an 32GB USB flash drive with Gparted, therefore I used a workaround with building an iso with the Fedora Media Writer on this flash drive. Afterwards I deleted this iso with Gparted. Delete was successful, but Gparted showed now a flash drive with 117GB and it was not possible to get a working partition. Using the restore to factory settings with Media Writer repaired the flash drive again to 32GB. Normally Gparted -as I have seen so far- works correctly. Is there an error in setting the "correct end" of the flash drive (in my case 32GB) in the production of an Fedora iso? Kind regards -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: devedeng problem F24 -> could this also happen to F25 ?
Hi, Thank You very much for your help. It was disk space. I use F24 and Windows alternatively on a laptop, so for varying Fedora distributions it's the easiest for me to have F24 on an 32GB USB 3.0 flash medium, there were about 8GB free for production of films on DVD, this was enough for Devede but not for Devede_NG. So I will transfer F24 to a 64GB USB 3.0 flash medium. Kind regards -Ursprüngliche Mitteilung- Von: Sérgio Basto An: test Verschickt: Mi, 17 Aug 2016 5:52 pm Betreff: Re: devedeng problem F24 -> could this also happen to F25 ? On Qua, 2016-08-17 at 08:25 -0400, Joerg Lechner wrote:> Hi, > after production of DVD iso out of MP4 file, F24 breaks down, no> shutdown, the screen is dark and the blue lamp, which signals the> system is on, is still on? The produced iso is complete and can be> burned successfully with Brasero. Is this Gnome? GDM?> This is new since the last 2 Kernels or updates (modules?). How can I> read a log about this breakdown?The only thing that devedeng can do to break down your computer , isfull the disk ... what is output of df -h ? to check kernel: dmesg and journalctl -p err -b anyway try boot with one kernel 4.5 , instead 4.6 ... see if helps > My system: Acer Laptop, 6GB Ram> SW:> [joerg@linux ~]$ dnf info devedeng> Letzte Prüfung auf abgelaufene Metadaten: vor 0:01:49 am Wed Aug 17> 14:11:07 2016.> Installierte Pakete> Name: devedeng> Arch: noarch> Epoch : 0> Version : 4.7.1> Release : 1.fc24> Größe : 3.2 M> Paketquelle : @System> Aus Paketqu : rpmfusion-free-updates> Zusammenfas : A program to create video DVDs and CDs (VCD, sVCD or> CVD)> URL : http://www.rastersoft.com/programas/devede.html> Lizenz : GPLv3+> Beschreibun : DevedeNG is a program to create video DVDs and CDs> (VCD, sVCD or> : CVD), suitable for home players, from any number of> video files,> : in any of the formats supported by FFMpeg.> : > : The suffix NG is because it is a rewrite from scratch> of the old> : Devede, to work with Python3 and Gtk3, and with a new> internal> : architecture that allows to expand it and easily add> new features.> > [joerg@linux ~]$ dnf info kernel> Letzte Prüfung auf abgelaufene Metadaten: vor 0:02:12 am Wed Aug 17> 14:11:07 2016.> Installierte Pakete> Name: kernel> Arch: x86_64> Epoch : 0> Version : 4.6.4> Release : 301.fc24> Größe : 0.0 > Paketquelle : @System> Aus Paketqu : updates> Zusammenfas : The Linux kernel> URL : http://www.kernel.org/> Lizenz : GPLv2 and Redistributable, no modification permitted> Beschreibun : The kernel meta package> > Name: kernel> Arch: x86_64> Epoch : 0> Version : 4.6.5> Release : 300.fc24> Größe : 0.0 > Paketquelle : @System> Aus Paketqu : updates> Zusammenfas : The Linux kernel> URL : http://www.kernel.org/> Lizenz : GPLv2 and Redistributable, no modification permitted> Beschreibun : The kernel meta package> > Name: kernel> Arch: x86_64> Epoch : 0> Version : 4.6.6> Release : 300.fc24> Größe : 0.0 > Paketquelle : @System> Aus Paketqu : updates> Zusammenfas : The Linux kernel> URL : http://www.kernel.org/> Lizenz : GPLv2 and Redistributable, no modification permitted> Beschreibun : The kernel meta package> > Kind Regards> --> test mailing list> test@lists.fedoraproject.org> To unsubscribe:> https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.> org-- Sérgio M. B.--test mailing listtest@lists.fedoraproject.orgTo unsubscribe:https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
devedeng problem F24 -> could this also happen to F25 ?
Hi, after production of DVD iso out of MP4 file, F24 breaks down, no shutdown, the screen is dark and the blue lamp, which signals the system is on, is still on? The produced iso is complete and can be burned successfully with Brasero. Is this Gnome? GDM? This is new since the last 2 Kernels or updates (modules?). How can I read a log about this breakdown? My system: Acer Laptop, 6GB Ram SW: [joerg@linux ~]$ dnf info devedeng Letzte Prüfung auf abgelaufene Metadaten: vor 0:01:49 am Wed Aug 17 14:11:07 2016. Installierte Pakete Name: devedeng Arch: noarch Epoch : 0 Version : 4.7.1 Release : 1.fc24 Größe : 3.2 M Paketquelle : @System Aus Paketqu : rpmfusion-free-updates Zusammenfas : A program to create video DVDs and CDs (VCD, sVCD or CVD) URL : http://www.rastersoft.com/programas/devede.html Lizenz : GPLv3+ Beschreibun : DevedeNG is a program to create video DVDs and CDs (VCD, sVCD or : CVD), suitable for home players, from any number of video files, : in any of the formats supported by FFMpeg. : : The suffix NG is because it is a rewrite from scratch of the old : Devede, to work with Python3 and Gtk3, and with a new internal : architecture that allows to expand it and easily add new features. [joerg@linux ~]$ dnf info kernel Letzte Prüfung auf abgelaufene Metadaten: vor 0:02:12 am Wed Aug 17 14:11:07 2016. Installierte Pakete Name: kernel Arch: x86_64 Epoch : 0 Version : 4.6.4 Release : 301.fc24 Größe : 0.0 Paketquelle : @System Aus Paketqu : updates Zusammenfas : The Linux kernel URL : http://www.kernel.org/ Lizenz : GPLv2 and Redistributable, no modification permitted Beschreibun : The kernel meta package Name: kernel Arch: x86_64 Epoch : 0 Version : 4.6.5 Release : 300.fc24 Größe : 0.0 Paketquelle : @System Aus Paketqu : updates Zusammenfas : The Linux kernel URL : http://www.kernel.org/ Lizenz : GPLv2 and Redistributable, no modification permitted Beschreibun : The kernel meta package Name: kernel Arch: x86_64 Epoch : 0 Version : 4.6.6 Release : 300.fc24 Größe : 0.0 Paketquelle : @System Aus Paketqu : updates Zusammenfas : The Linux kernel URL : http://www.kernel.org/ Lizenz : GPLv2 and Redistributable, no modification permitted Beschreibun : The kernel meta package Kind Regards -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: automaticly reduced screen brightness, now also in F24, will this also be a problem for F25?
Hi, question to Richard Hughes and Chris Murphy. I have now installed colorhug-client-backlight-0.2.8-2.fc24.x86_64.rpm, as you proposed in the previous thread concerning F23. The ambient light shows still 0 Lux. Is colorhug-client-backlight-0.2.8-2.fc24.x86_64.rpm already ok for F24? Kind regards -Ursprüngliche Mitteilung- Von: Joerg Lechner An: test Verschickt: Mi, 3 Aug 2016 6:39 pm Betreff: automaticly reduced screen brightness, now also in F24, will this also be a problem for F25? Hi, the story: Acer Laptop Aspire E15 E5-571G, running on storage-battery for about an hour (I forgot to plug in the power), screen lightning normal, about 60%, during plug in to the power, suddenly lightning is reduced to 30%. I looked at the power management to see the current value of lightning. I saw similar things previously in F23, and had opened a thread about this problem during F24 development time, it seems that there is still no working solution, is there something planned for F25? I will try to reproduce this problem. Kind regards -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
automaticly reduced screen brightness, now also in F24, will this also be a problem for F25?
Hi, the story: Acer Laptop Aspire E15 E5-571G, running on storage-battery for about an hour (I forgot to plug in the power), screen lightning normal, about 60%, during plug in to the power, suddenly lightning is reduced to 30%. I looked at the power management to see the current value of lightning. I saw similar things previously in F23, and had opened a thread about this problem during F24 development time, it seems that there is still no working solution, is there something planned for F25? I will try to reproduce this problem. Kind regards -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
boot F24 in special condition (additional USB disk connected) very slow
Hi, I saw this sometimes, now I ask this silly question. F24 on USB flash media, addiional external Harddisk connected via a separate USB connection to the laptop. At boot this embleme, first white, afterwards blue and the Fedora F in it, is very slow. This white embleme takes very long, some minutes before it completes, it took so long that I interrupted the boot. The disk is a used one just buyed from Ebay, 1TB sata, nothing on it, which could cause the boot to slow down so much. Disconnecting the external disk, the boot is fast as usual. Connecting the ext. disk again after boot, all behaves as usual. Is this behaviour at boot ok? Kind regards -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: devede beta1 nok
Hi, thank You very much for this advice "rm ~/.devede". Now Devede Beta1 works as user and as root. Kind regards -Ursprüngliche Mitteilung- Von: Sérgio Basto An: test Verschickt: Sa, 23 Jul 2016 5:54 am Betreff: Re: devede beta1 nok On Sex, 2016-07-22 at 23:47 -0400, Joerg Lechner wrote:> Hi,> not possible to run, the result of a "run trial" I had included,> after successful dnf update, where devede beta1 is in. Thank You for> Your advice, I will investigate a little bit and file a bug. After> downgrade the previous version of devede "runs" again.> Kind regards> devede-3.23.0-7.20151018git.fc23.noarch works for me please try:rm ~/.devede-- Sérgio M. B.--test mailing listtest@lists.fedoraproject.orgTo unsubscribe:https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: devede beta1 nok
Hi, not possible to run, the result of a "run trial" I had included, after successful dnf update, where devede beta1 is in. Thank You for Your advice, I will investigate a little bit and file a bug. After downgrade the previous version of devede "runs" again. Kind regards -Ursprüngliche Mitteilung- Von: Sérgio Basto An: test Verschickt: Fr, 22 Jul 2016 9:46 pm Betreff: Re: devede beta1 nok On Sex, 2016-07-22 at 14:17 -0400, Joerg Lechner wrote:> Hi,> just saw in F23 - this might also be valid for the F23 followers:> > Aktualisiert:> audit.x86_64 2.6.5-> 1.fc23 > audit-libs.x86_64 2.6.5-> 1.fc23 > audit-libs-python3.x86_64 2.6.5-> 1.fc23 > devede.noarch 3.23.0-7.20151018git.fc23 > doesn't work,> also as user nok - not only as root nok > what is not ok ? , devede.noarch 3.23.0-7.20151018git.fc23 is fromRPMFusion , not Fedora, please report it on RPMFusion channels .(Mailing list or bugzilla or irc) > > gnome-calculator.x86_64 3.18.3-> 1.fc23 > > Komplett!> [root@linux joerg]# devede> DeVeDe 3.23.0 beta1> Locale: de_DE.UTF-8> Using package-installed files> /root/> Cores: 2 Virtual cores: 4> Entro en fonts> Salgo de fonts> /root/> Temp Directory is: /var/tmp> home load: /root/.devede> linea: video_format:pal> > linea: temp_folder:/var/tmp/> > linea: multicore:1> > linea: hyperthreading:1> > Traceback (most recent call last):> File "/usr/bin/devede", line 303, in > devede_other.load_config(global_vars) # load configuration> File "/usr/lib/python2.7/site-packages/devede/devede_other.py",> line 484, in load_config> value=to_bool(value)> File "/usr/lib/python2.7/site-packages/devede/devede_other.py",> line 422, in to_bool> raise Exception('Invalid value for boolean conversion: ' +> str(value))> Exception: Invalid value for boolean conversion: 1> [root@linux joerg]#> > Kind regards > > --> test mailing list> test@lists.fedoraproject.org> To unsubscribe:> https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.> org-- Sérgio M. B.--test mailing listtest@lists.fedoraproject.orgTo unsubscribe:https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
devede beta1 nok
Hi, just saw in F23 - this might also be valid for the F23 followers: Aktualisiert: audit.x86_64 2.6.5-1.fc23 audit-libs.x86_64 2.6.5-1.fc23 audit-libs-python3.x86_64 2.6.5-1.fc23 devede.noarch 3.23.0-7.20151018git.fc23 > doesn't work, also as user nok - not only as root nok gnome-calculator.x86_64 3.18.3-1.fc23 Komplett! [root@linux joerg]# devede DeVeDe 3.23.0 beta1 Locale: de_DE.UTF-8 Using package-installed files /root/ Cores: 2 Virtual cores: 4 Entro en fonts Salgo de fonts /root/ Temp Directory is: /var/tmp home load: /root/.devede linea: video_format:pal linea: temp_folder:/var/tmp/ linea: multicore:1 linea: hyperthreading:1 Traceback (most recent call last): File "/usr/bin/devede", line 303, in devede_other.load_config(global_vars) # load configuration File "/usr/lib/python2.7/site-packages/devede/devede_other.py", line 484, in load_config value=to_bool(value) File "/usr/lib/python2.7/site-packages/devede/devede_other.py", line 422, in to_bool raise Exception('Invalid value for boolean conversion: ' + str(value)) Exception: Invalid value for boolean conversion: 1 [root@linux joerg]# Kind regards -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
F24 Gnome, frequently used apps
Hi, I know questions to F24 should be now in the user area and not in this list. But I saw the following in Gnome. Just used the terminal to do an dnf update. When I go in the gnome display for apps, and there in the display for frequently used apps, i expected to find the icon for the terminal there, as it is in F23, but there is a no icon for any used app before. Kind regards -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
only installing F24 release sets sytem time to USA eastern time
Hi, there is an -I think- open bug " [Bug 1018162] only testing LIVE CD, changes system time in BIOS ", in this error system time was set to UTC. Just installed the release version Workstation (6.2) after a fresh download according to the release link. I installed F24, shut down the Live Media on usb and started immediately Windows 8.1. My system time in UEFI or BIOS is now set 6 hours back, in my case from MEZ (middle European Time) to eastern North American Time. This effect is new. Shall I file another bug, or comment Bug 1018162? What's best? Kind regards -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: still not possible to activate WIFI during installation of F24 Final
Hi Adam, if necessary I can give a more detailed explanation, via screenshots, that's a better way of explanation, then my bad technical English. But anyway I have loaded today in the morning F24 Final 1.2 workstation, all the problems I mentioned (dual boot, memory error while recover space in installation, WIFI) previously are solved now, including " the WIFI initial setup problem". But anyway I can make screenshots to explain what I want to say, if still needed. Kind Regards -Ursprüngliche Mitteilung- Von: Adam Williamson An: For testing and quality assurance of Fedora releases Verschickt: Mi, 15 Jun 2016 7:42 am Betreff: Re: still not possible to activate WIFI during installation of F24 Final On Tue, 2016-06-14 at 22:41 -0700, Adam Williamson wrote:> On Tue, 2016-06-14 at 15:48 -0400, Joerg Lechner wrote:> > Hi Adam,> > to say explicitly, what is not working, I have made a screenshot of> > the not working feature. Via network it's possible to activate, but> > the method of activation in the initial set up - which I could> > previously find there, and did also not work in network feature, as> > it didn't in the initial set up - has disappeared there.> > Kind regards> > Are you saying that you don't see the network configuration step in the> initial setup wizard, and the screenshot you attached is a screenshot> of the thing you used to see that you don't see any more?Oh, never mind, saw the BZ link. It's odd that you say it's fixed inRC2, though, because I don't think we changed anything related to thisin RC2.-- Adam WilliamsonFedora QA Community MonkeyIRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . nethttp://www.happyassassin.net--test mailing listtest@lists.fedoraproject.orgTo unsubscribe:https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: still not possible to activate WIFI during installation of F24 Final
Hi, the bug is "Bug 1331922 - can not connect to wifi in the Gnome initial set up" https://bugzilla.redhat.com/show_bug.cgi?id=1331922 Kind regards -Ursprüngliche Mitteilung- Von: Adam Williamson An: For testing and quality assurance of Fedora releases Verschickt: Di, 14 Jun 2016 8:24 pm Betreff: Re: still not possible to activate WIFI during installation of F24 Final On Tue, 2016-06-14 at 12:20 -0400, Joerg Lechner wrote:> Hi,> today I have updated from updates-testing F24 Final 1.1. I assume> these updates will make 1.1 to 1.2.No, not at all. Most of the stuff in updates-testing will not beincluded in the final media.> 2 of mine problems are solved (anaconda, dual boot). But during> installation i can not activate WIFI, there is still this problem> valid, there is an open bug.> Kind regardsWell, it's hard to say anything since you left out all the usefuldetails...could you link to the bug report?-- Adam WilliamsonFedora QA Community MonkeyIRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . nethttp://www.happyassassin.net--test mailing listtest@lists.fedoraproject.orgTo unsubscribe:https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
still not possible to activate WIFI during installation of F24 Final
Hi, today I have updated from updates-testing F24 Final 1.1. I assume these updates will make 1.1 to 1.2. 2 of mine problems are solved (anaconda, dual boot). But during installation i can not activate WIFI, there is still this problem valid, there is an open bug. Kind regards -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
after update (updates-testing) dual boot (Win 8.1 -F24) ok
Hi, after it's now possible (anaconda updated) to install F24 Desktop Final 1.1, I updated according to protocol: [joerg@linux ~]$ su Passwort: [root@linux joerg]#dnf config-manager --set-enabled updates-testing [root@linux joerg]#dnf update Fedora 24 - x86_64 5.8 MB/s | 47 MB 00:08 Fedora 24 - x86_64 -Updates1.8 kB/s | 257 B 00:00 Fedora 24 - x86_64 -Test Updates 5.3 MB/s | 5.1 MB 00:00 Letzte Prüfung aufabgelaufene Metadaten: vor 0:00:02 am Tue Jun 14 14:36:59 2016. Abhängigkeiten sindaufgelöst. Package Arch Version Paketquelle Größe Installieren: kernel x86_64 4.5.7-300.fc24 updates-testing 70 k kernel-core x86_64 4.5.7-300.fc24 updates-testing 19 M kernel-modules x86_64 4.5.7-300.fc24 updates-testing 21 M kernel-modules-extra x86_64 4.5.7-300.fc24 updates-testing 2.2 M libblockdev-fs x86_64 1.6-1.fc24 updates-testing 40 k libblockdev-part x86_64 1.6-1.fc24 updates-testing 44 k libbytesize x86_64 0.7-1.fc24 fedora 51 k Aktualisieren: NetworkManager x86_64 1:1.2.2-2.fc24 updates-testing 2.6 M NetworkManager-adsl x86_64 1:1.2.2-2.fc24 updates-testing 239 k NetworkManager-bluetooth x86_64 1:1.2.2-2.fc24 updates-testing 259 k NetworkManager-config-connectivity-fedora x86_64 1:1.2.2-2.fc24 updates-testing 104 k NetworkManager-glib x86_64 1:1.2.2-2.fc24 updates-testing 369 k NetworkManager-libnm x86_64 1:1.2.2-2.fc24 updates-testing 538 k NetworkManager-team x86_64 1:1.2.2-2.fc24 updates-testing 239 k NetworkManager-wifi x86_64 1:1.2.2-2.fc24 updates-testing 265 k NetworkManager-wwan x86_64 1:1.2.2-2.fc24 updates-testing 363 k accountsservice x86_64 0.6.40-4.fc24 updates-testing 95 k accountsservice-libs x86_64 0.6.40-4.fc24 updates-testing 81 k autocorr-en noarch 1:5.1.4.1-2.fc24updates-testing 203 k bluezx86_64 5.40-1.fc24 updates-testing 1.1 M bluez-cups x86_64 5.40-1.fc24 updates-testing 86 k bluez-libs x86_64 5.40-1.fc24 updates-testing 83 k bluez-obexd x86_64 5.40-1.fc24 updates-testing 192 k chrony x86_64 2.4-1.fc24 updates-testing 225 k cryptsetup x86_64 1.7.2-1.fc24updates-testing 130 k cryptsetup-libs x86_64 1.7.2-1.fc24updates-testing 220 k cups-filters x86_64 1.9.0-1.fc24updates-testing 688 k cups-filters-libsx86_64 1.9.0-1.fc24updates-testing 100 k curl x86_64 7.47.1-5.fc24 updates-testing 293 k dmidecodex86_64 1:3.0-3.fc24updates-testing 89 k evolutionx86_64 3.20.3-1.fc24 updates-testing 8.6 M evolution-data-server x86_64 3.20.3-1.fc24 updates-testing 3.1 M evolution-ewsx86_64 3.20.3-1.fc24 updates-testing 503 k evolution-help noarch 3.20.3-1.fc24 updates-testing 2.1 M findutilsx86_64 1:4.6.0-5.fc24 updates-testing 521 k gdb x86_64 7.11.1-75.fc24 updates-testing 3.3 M gettext x86_64 0.19.8.1-1.fc24 updates-testing 1.0 M gettext-libs x86_64 0.19.8.1-1.fc24 updates-testing 506 k glibcx86_64 2.23.1-8.fc24 updates-testing 3.6 M glibc-all-langpacks x86_64 2.23.1-8.fc24 updates-testing 6.9 M glibc-common x86_64 2.23.1-8.fc24 updates-testing 861 k glibc-devel x86_64 2.23.1-8.fc24 updates-testing 935 k glibc-headersx86_64 2.23.1-8.fc24 updates-testing 500 k glibc-langpack-enx86_64 2.23.1-8.fc24 updates-testing 275 k gnome-abrt x86_64 1.2.4-1.fc24updates-testing 247 k gnome-terminal x86_64 3.20.2-2.fc24 updates-testing 1.2 M gnutls x86_64 3.4.13-1.fc24 updates-testing 659 k gnutls-dane x86_64 3.4.13-1.fc24 updates-testing 38 k gnutls-utils x86_64 3.4.13-1.fc24 updates-testing 262 k gspell x86_64 1.0.2-1.fc24updates-testing 77 k gssproxy x86_64 0.5.0-5.fc24updates-testing 96 k gstreamer1 x86_6
Re: [Test-Announce] Fedora 24 Candidate RC-1.1 Available Now!
Hi, Here the bug created by the system related to the problem with F24 RC 1.1 Workstation: Bug 1344856 - AttributeError: 'Iso9660FS' object has no attribute 'partitions' Kind regards -Ursprüngliche Mitteilung- Von: Joerg Lechner An: test Verschickt: Sa, 11 Jun 2016 8:52 pm Betreff: Re: [Test-Announce] Fedora 24 Candidate RC-1.1 Available Now! Hi, tried to install Workstation RC 1.1 x86_64 -> "unknown error occured" on install to harddrive after I tried to get again space on the harddrive ( option delete all partitions), the system has sent a bug report. My system Acer laptop E15, tried to install F24 on a 32GB usb flash medium. Error occurs always. Kind regards -Ursprüngliche Mitteilung- Von: Peter Robinson An: test ; Development discussions related to Fedora Cc: test-announce Verschickt: Sa, 11 Jun 2016 6:43 pm Betreff: Re: [Test-Announce] Fedora 24 Candidate RC-1.1 Available Now! On Sat, Jun 11, 2016 at 4:59 PM, wrote:> According to the schedule [1], Fedora 24 Candidate RC-1.1 is now> available for testing. Please help us complete all the validation> testing! For more information on release validation testing, see:> https://fedoraproject.org/wiki/QA:Release_validation_test_planAren't they named incorrectly? Looking at spins [1] and isos [2]they're using the nightly naming scheme (24-20160611.n.0) rather than24-1.1 like I'd expect.[1] http://dl.fedoraproject.org/pub/fedora/linux/development/24/Spins/x86_64/iso/[2] http://dl.fedoraproject.org/pub/fedora/linux/development/24/Server/x86_64/iso/> Test coverage information for the current release can be seen at:> https://www.happyassassin.net/testcase_stats/24>> You can see all results, find testing instructions and image download> locations, and enter results on the Summary page:>> https://fedoraproject.org/wiki/Test_Results:Fedora_24_RC_1.1_Summary>> The individual test result pages are:>> https://fedoraproject.org/wiki/Test_Results:Fedora_24_RC_1.1_Installation> https://fedoraproject.org/wiki/Test_Results:Fedora_24_RC_1.1_Base> https://fedoraproject.org/wiki/Test_Results:Fedora_24_RC_1.1_Server> https://fedoraproject.org/wiki/Test_Results:Fedora_24_RC_1.1_Cloud> https://fedoraproject.org/wiki/Test_Results:Fedora_24_RC_1.1_Desktop> https://fedoraproject.org/wiki/Test_Results:Fedora_24_RC_1.1_Security_Lab>> All RC priority test cases for each of these test pages [2] must> pass in order to meet the RC Release Criteria [3].>> Help is available on #fedora-qa on irc.freenode.net [4], or on the> test list [5].>> Current Blocker and Freeze Exception bugs:> http://qa.fedoraproject.org/blockerbugs/current>> [1] http://fedorapeople.org/groups/schedule/f-24/f-24-quality-tasks.html> [2] https://fedoraproject.org/wiki/QA:Release_validation_test_plan> [3] https://fedoraproject.org/wiki/Fedora_24_RC_Release_Criteria> [4] irc://irc.freenode.net/fedora-qa> [5] https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/> ___> test-announce mailing list> test-annou...@lists.fedoraproject.org> https://lists.fedoraproject.org/admin/lists/test-annou...@lists.fedoraproject.org> --> devel mailing list> de...@lists.fedoraproject.org> https://lists.fedoraproject.org/admin/lists/de...@lists.fedoraproject.org--test mailing listtest@lists.fedoraproject.orgTo unsubscribe:https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: [Test-Announce] Fedora 24 Candidate RC-1.1 Available Now!
Hi, tried to install Workstation RC 1.1 x86_64 -> "unknown error occured" on install to harddrive after I tried to get again space on the harddrive ( option delete all partitions), the system has sent a bug report. My system Acer laptop E15, tried to install F24 on a 32GB usb flash medium. Error occurs always. Kind regards -Ursprüngliche Mitteilung- Von: Peter Robinson An: test ; Development discussions related to Fedora Cc: test-announce Verschickt: Sa, 11 Jun 2016 6:43 pm Betreff: Re: [Test-Announce] Fedora 24 Candidate RC-1.1 Available Now! On Sat, Jun 11, 2016 at 4:59 PM, wrote:> According to the schedule [1], Fedora 24 Candidate RC-1.1 is now> available for testing. Please help us complete all the validation> testing! For more information on release validation testing, see:> https://fedoraproject.org/wiki/QA:Release_validation_test_planAren't they named incorrectly? Looking at spins [1] and isos [2]they're using the nightly naming scheme (24-20160611.n.0) rather than24-1.1 like I'd expect.[1] http://dl.fedoraproject.org/pub/fedora/linux/development/24/Spins/x86_64/iso/[2] http://dl.fedoraproject.org/pub/fedora/linux/development/24/Server/x86_64/iso/> Test coverage information for the current release can be seen at:> https://www.happyassassin.net/testcase_stats/24>> You can see all results, find testing instructions and image download> locations, and enter results on the Summary page:>> https://fedoraproject.org/wiki/Test_Results:Fedora_24_RC_1.1_Summary>> The individual test result pages are:>> https://fedoraproject.org/wiki/Test_Results:Fedora_24_RC_1.1_Installation> https://fedoraproject.org/wiki/Test_Results:Fedora_24_RC_1.1_Base> https://fedoraproject.org/wiki/Test_Results:Fedora_24_RC_1.1_Server> https://fedoraproject.org/wiki/Test_Results:Fedora_24_RC_1.1_Cloud> https://fedoraproject.org/wiki/Test_Results:Fedora_24_RC_1.1_Desktop> https://fedoraproject.org/wiki/Test_Results:Fedora_24_RC_1.1_Security_Lab>> All RC priority test cases for each of these test pages [2] must> pass in order to meet the RC Release Criteria [3].>> Help is available on #fedora-qa on irc.freenode.net [4], or on the> test list [5].>> Current Blocker and Freeze Exception bugs:> http://qa.fedoraproject.org/blockerbugs/current>> [1] http://fedorapeople.org/groups/schedule/f-24/f-24-quality-tasks.html> [2] https://fedoraproject.org/wiki/QA:Release_validation_test_plan> [3] https://fedoraproject.org/wiki/Fedora_24_RC_Release_Criteria> [4] irc://irc.freenode.net/fedora-qa> [5] https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/> ___> test-announce mailing list> test-annou...@lists.fedoraproject.org> https://lists.fedoraproject.org/admin/lists/test-annou...@lists.fedoraproject.org> --> devel mailing list> de...@lists.fedoraproject.org> https://lists.fedoraproject.org/admin/lists/de...@lists.fedoraproject.org--test mailing listtest@lists.fedoraproject.orgTo unsubscribe:https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: TPM prevents grub menu, scratch build request
Hi, as I said, I can try. Test PCs could be an old 386 Laptop with 524MB Ram (only LXDE), or a fast 64bit Laptop, I think there also should run an i686 workstation. Kind regards -Ursprüngliche Mitteilung- Von: Chris Murphy An: For testing and quality assurance of Fedora releases Verschickt: Fr, 20 Mai 2016 10:05 pm Betreff: TPM prevents grub menu, scratch build request [Bug 1334075] TPM prevents grub menu, drops to grub rescue; BIOSsettings no helphttps://bugzilla.redhat.com/show_bug.cgi?id=1334075This is not a blocker since it's i686, but there is a willing testerwith affected hardware who can test the recent patch submitted forthis bug.Is anyone able/willing to put up a scratch build? And if that goeswell get it into u-t before freeze?I can do it locally but I know diddly squat about how to package stuffwithin the Fedora build system.-- Chris Murphy--test mailing listtest@lists.fedoraproject.orgTo unsubscribe:http://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org -- test mailing list test@lists.fedoraproject.org To unsubscribe: http://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: TPM prevents grub menu, scratch build request
Hi, I can try, but I need instructions, what's to do. Kind regards -Ursprüngliche Mitteilung- Von: Chris Murphy An: For testing and quality assurance of Fedora releases Verschickt: Fr, 20 Mai 2016 10:05 pm Betreff: TPM prevents grub menu, scratch build request [Bug 1334075] TPM prevents grub menu, drops to grub rescue; BIOSsettings no helphttps://bugzilla.redhat.com/show_bug.cgi?id=1334075This is not a blocker since it's i686, but there is a willing testerwith affected hardware who can test the recent patch submitted forthis bug.Is anyone able/willing to put up a scratch build? And if that goeswell get it into u-t before freeze?I can do it locally but I know diddly squat about how to package stuffwithin the Fedora build system.-- Chris Murphy--test mailing listtest@lists.fedoraproject.orgTo unsubscribe:http://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org -- test mailing list test@lists.fedoraproject.org To unsubscribe: http://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: release criteria for final - bug 1320967
Hi, there is somewhere proposed (when I remember correctly in an elder bug report concerning the same problem) to use the dual boot system of the other OS, in my case this would be Win 8.1, or a workaround. I disagree with these proposals. I would like to use a downgrade of Grub, if this downgrade works. Kind regards -Ursprüngliche Mitteilung- Von: Chris Murphy An: For testing and quality assurance of Fedora releases Verschickt: Fr, 20 Mai 2016 5:56 pm Betreff: Re: release criteria for final - bug 1320967 On Fri, May 20, 2016 at 8:42 AM, Adam Williamson wrote:> On Fri, 2016-05-20 at 10:08 -0400, Joerg Lechner wrote:>> Hi,>> question to Adam Williamson:>> Is it possible to file a bug to have a problem shifted from blocking>> for final i.e. to blocking for Alpha or Beta?>> This is a question for F25 and followers.>> Kind regards>> We can discuss changing the criterion, sure. This is usually done just> with a thread on the mailing list (exactly like this one) - there is no> need for a bug report or ticket.>> I don't think I'd support the change, though, personally. I think Final> is the appropriate place for dual-boot criteria.I don't think it'd affect development at all. What it does do isremove the most obvious big dual boot bugs from broader community betatesting, so that hopefully if there are more obscure bugs, they getfound. Showstopper bugs tend to inhibit that testing. On some systemsit's necessary to do a grub downgrade to do any post-install testingof a dual boot UEFI system right now.-- Chris Murphy--test mailing listtest@lists.fedoraproject.orgTo unsubscribe:http://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org -- test mailing list test@lists.fedoraproject.org To unsubscribe: http://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: release criteria for final - bug 1320967
Hi, I would like to do a Grub downgrade, this would be a way for me to take part easily in testing with my dual boot system (F24 - Win 8.1). So far I have no success in a F24 Grub downgrade, possibly I do something wrong, so far I have tried the simple way of downgrading: [root@linux joerg]# [root@linux joerg]# dnf downgrade grub2-efi-modules Letzte Prüfung auf abgelaufene Metadaten: vor 2:16:13 am Fri May 20 16:26:30 2016. Keine Übereinstimmungen für verfügbares Paket: grub2-efi-modules-1:2.02-0.30.fc24.x86_64 Fehler: Nichts zu tun. [root@linux joerg]# Kind regards -Ursprüngliche Mitteilung- Von: Chris Murphy An: For testing and quality assurance of Fedora releases Verschickt: Fr, 20 Mai 2016 5:56 pm Betreff: Re: release criteria for final - bug 1320967 On Fri, May 20, 2016 at 8:42 AM, Adam Williamson wrote:> On Fri, 2016-05-20 at 10:08 -0400, Joerg Lechner wrote:>> Hi,>> question to Adam Williamson:>> Is it possible to file a bug to have a problem shifted from blocking>> for final i.e. to blocking for Alpha or Beta?>> This is a question for F25 and followers.>> Kind regards>> We can discuss changing the criterion, sure. This is usually done just> with a thread on the mailing list (exactly like this one) - there is no> need for a bug report or ticket.>> I don't think I'd support the change, though, personally. I think Final> is the appropriate place for dual-boot criteria.I don't think it'd affect development at all. What it does do isremove the most obvious big dual boot bugs from broader community betatesting, so that hopefully if there are more obscure bugs, they getfound. Showstopper bugs tend to inhibit that testing. On some systemsit's necessary to do a grub downgrade to do any post-install testingof a dual boot UEFI system right now.-- Chris Murphy--test mailing listtest@lists.fedoraproject.orgTo unsubscribe:http://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org -- test mailing list test@lists.fedoraproject.org To unsubscribe: http://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: release criteria for final - bug 1320967
Hi, question to Adam Williamson: Is it possible to file a bug to have a problem shifted from blocking for final i.e. to blocking for Alpha or Beta? This is a question for F25 and followers. Kind regards -Ursprüngliche Mitteilung- Von: Ahmad Samir An: For testing and quality assurance of Fedora releases Verschickt: Mi, 18 Mai 2016 4:14 pm Betreff: Re: release criteria for final - bug 1320967 On 18 May 2016 at 14:41, Joerg Lechner wrote: Hi, my question and suggestion is not to have an important issue like this -for having one computer as test machine for a new release and in parallell for another OS - as a blocker for Final but earlier as a blocker for Alpha or Beta, then at least for me it's easier to help testing in a new release. I misunderstood then, sorry about the noise :|. This is a suggestion for F25, currently for my use I can still run F23 || Win 8.1, but I can not so easily contribute to F24 testing. Is there a bug report helpful? Kind regards I am not sure about the process/procedure to change the criteria, but posting to this list is a logical first step, I think. --test mailing listtest@lists.fedoraproject.orgTo unsubscribe:http://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org -- test mailing list test@lists.fedoraproject.org To unsubscribe: http://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: F23 Brightness reduces itself, this problem also in F24?
Hi Chris, I am just starting to understand. "You turn off the support in g-c-c" I don't understand, whats to be done?. I have installed Colorhug Backlight Utility, a screenshot shows the first display of this app after installation, so far I did not make any adjustments. Can You tell me, how I can get, what You need, please explain for a none expert. If there is Lux 0, does this mean, that in my Laptop there is no sensor? kind regards -Ursprüngliche Mitteilung- Von: Chris Murphy Verschickt: Mi, 18 Mai 2016 7:30 pm Betreff: Re: F23 Brightness reduces itself, this problem also in F24? On Wed, May 18, 2016 at 11:15 AM, Chris Murphy wrote:> Daytime: Ambient reports either 61 Lux - 43 Lux the whole day. At 58> Lux, backlight looks like 75% according to the graph. There's no raw> value visible. And I'm not inclined to change the brightness. But even> if it went up or down, chasing this narrow ambient range, I wouldn't> notice it.58 Lux and 75%, turned automatic back to On, and 2 minutes later thebrightness is automatically bumped to 85 in one event (two notches),even though ambient hasn't changed. So that's unexpected. It's notthat noticeable visually. I probably would not make a change had I notbeen looking right at CBU when it happened.I've changed it back to 75% and after 5 minutes, still at 57 Lux and75%, so it hasn't changed again yet.-- Chris Murphy--test mailing listtest@lists.fedoraproject.orgTo unsubscribe:http://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org -- test mailing list test@lists.fedoraproject.org To unsubscribe: http://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: release criteria for final - bug 1320967
Hi, my question and suggestion is not to have an important issue like this -for having one computer as test machine for a new release and in parallell for another OS - as a blocker for Final but earlier as a blocker for Alpha or Beta, then at least for me it's easier to help testing in a new release. This is a suggestion for F25, currently for my use I can still run F23 || Win 8.1, but I can not so easily contribute to F24 testing. Is there a bug report helpful? Kind regards -Ursprüngliche Mitteilung- Von: Ahmad Samir An: For testing and quality assurance of Fedora releases Verschickt: Mi, 18 Mai 2016 1:36 pm Betreff: Re: release criteria for final - bug 1320967 On 18 May 2016 at 07:39, Joerg Lechner wrote: Hi, I use an about one year old Acer laptop, internal disk Win 8.1, F23/F24 on usb flash media, for F20/21/22/23 I tested as user, using the Fedora version in development. Because of " F24 Alpha 1.7 Desktop - Grub boot menue, not possible to start Win 8.1" - Bug 1320967, in F24 I don't test very frequently, because unplugging/plugging (in my case neccessary for F24) the usb media very often I forget, when I switch from Win to Fedora and vice versa. This problem of Grub is a release criteria for final. Is it possible to have it for F25 as a release criteria for Beta or Alpha? Kind Regards It's a known issue https://fedoraproject.org/wiki/Common_F24_bugs#uefi-chainloading-error -- Ahmad Samir --test mailing listtest@lists.fedoraproject.orgTo unsubscribe:http://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org -- test mailing list test@lists.fedoraproject.org To unsubscribe: http://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
release criteria for final - bug 1320967
Hi, I use an about one year old Acer laptop, internal disk Win 8.1, F23/F24 on usb flash media, for F20/21/22/23 I tested as user, using the Fedora version in development. Because of " F24 Alpha 1.7 Desktop - Grub boot menue, not possible to start Win 8.1" - Bug 1320967, in F24 I don't test very frequently, because unplugging/plugging (in my case neccessary for F24) the usb media very often I forget, when I switch from Win to Fedora and vice versa. This problem of Grub is a release criteria for final. Is it possible to have it for F25 as a release criteria for Beta or Alpha? Kind Regards -- test mailing list test@lists.fedoraproject.org To unsubscribe: http://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org