Re: Urgent F23 testing request: logout bugs
On wed, 21/10/2015 at 09.13 -0700, Adam Williamson wrote: > Hi folks! > > So we're building 23 Final RC2 now, but we have a couple of > outstanding > proposed blocker bugs, and we could use some more data to evaluate > them. > > The way to test is really simple: > > * Install F23 Final TC11 Workstation or KDE live[1] > * Create a user and log in > * Log out a bunch of times. Just keep logging in and out. > > Ideally try this both in a VM and on a real system, if you have a > spare > system to test on. > > There are two bugs that you might hit: > > 1. https://bugzilla.redhat.com/show_bug.cgi?id=1272737 > 2. https://bugzilla.redhat.com/show_bug.cgi?id=1273247 > > With the first one, the system gets stuck at a black screen after > logging out. You won't be able to switch to a TTY or anything, but if > you have another system, you'll find that ssh'ing in still works. So > far it seems this bug *only* affects Workstation (we believe it > involves Wayland, and Workstation has GDM-on-Wayland). It seems easy > to > reproduce in a KVM, harder to reproduce on a real system, but some > testers have reproduced it on a real system after several attempts. > We're particularly interested in whether you hit it on a real system, > and if so, how often. > > With the second bug, assuming you don't hit the first bug, the cursor > disappears on the login screen, possibly after you click somewhere > (e.g. the password text entry box). Roshi says he sees something like > this on Workstation but not KDE, kparal says he sees it on KDE but > not > Workstation, and I can't reproduce it on either. This one is probably > only reproducible in a KVM, but of course let us know if you manage > to > trigger it on a real system! > > If you could report back to the list what configuration you tested > on, > and whether and how often you managed to reproduce either bug, that > would be a great help. For virtual machine testing, please let us > know: > > * What virtualization system you used (KVM/virt-manager is preferred) > * For a KVM: > ** Whether your VM has a virtual 'tablet' input device (one > is often created by default, so check in virt-manager) > ** What video adapter and viewer you're using (e.g. qxl/SPICE or > std/VNC) > ** What OS and release is running on the host system > ** The graphics adapter and driver being used on the host system > > Thanks! > > [1] Downloads: > https://dl.fedoraproject.org/pub/alt/stage/23_TC11/Workstation/i3 > 86/iso/Fedora-Live-Workstation-i686-23-TC11.iso > https://dl.fedoraproject.org/pub/alt/stage/23_TC11/Workstation/x8 > 6_64/iso/Fedora-Live-Workstation-x86_64-23-TC11.iso > https://dl.fedoraproject.org/pub/alt/stage/23_TC11/Live/i386/Fedo > ra-Live-KDE-i686-23-TC11.iso > https://dl.fedoraproject.org/pub/alt/stage/23_TC11/Live/x86_64/Fe > dora-Live-KDE-x86_64-23-TC11.iso > -- > Adam Williamson > Fedora QA Community Monkey > IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . > net > http://www.happyassassin.net > > I've tested the "mouse cursor" bug (the one reported by Roshi) with ~15/20 attempts: I haven't been able to reproduce it. Here are some details: 1) qemu-kvm via virt-manager on a Fedora 22 host 2) Yes, my VM has got that virtual 'tablet', created by default. 3) The video adapter is QXL/SPICE here. 4) Two Amd GPUs (4250m+5650m) with radeon driver on the host. 5) KDE x86_64 TC11 on the guest. // Giulio (jpigface) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
I proposed a blocker, but I chose the wrong milestone
Greetings folks. I've just proposed https://bugzilla.redhat.com/show_bug.cgi?id=1250712 as blocker, but I'm afraid I chose "Beta" instead of "Final". Hmmm, I honestly don't know how to revert this. Should I re-propose it or will an admin move it to the correct milestone? Sorry for the mistake. // Giulio (jpigface) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Bug 1257131 (also proposed as blocker) needs testing
Hi folks. Sorry if I write this mail, but there is a bug which might potentially be serious enough to be a nasty blocker - at least in my opinion -. The link is this: https://bugzilla.redhat.com/show_bug.cgi?id=1257131 As I wrote with my comment, I don't hit the issue inside a vm. Unfortunately I haven't got available hardware to test this on bare metal, so I'm asking if anyone encounters this bug. We need to be sure that this doesn't affect a large class of laptops. Again... Please excuse me if I ping the ML, but I think that it's better to collect more data before the next blocker review in order to ease the decision regarding this bug. Have a nice week-end! Giulio -- Giulio 'juliuxpigface' Fedora QA FAS: juliuxpigface || IRC: jpigface || GITHUB: pigjuliux WEB: https://pigjuliux.wordpress.com -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Bug 1257131 (also proposed as blocker) needs testing
On 05/09/2015 at 21.38 +0200, Giulio 'juliuxpigface' wrote: > Hi folks. > > Sorry if I write this mail, but there is a bug which might > potentially > be serious enough to be a nasty blocker - at least in my opinion -. > > The link is this: https://bugzilla.redhat.com/show_bug.cgi?id=1257131 > > As I wrote with my comment, I don't hit the issue inside a vm. > Unfortunately I haven't got available hardware to test this on bare > metal, so I'm asking if anyone encounters this bug. We need to be > sure > that this doesn't affect a large class of laptops. One additional info: the reporter is able to reproduce the bug with a live too (Fedora 23, obviously). > > Again... Please excuse me if I ping the ML, but I think that it's > better to collect more data before the next blocker review in order > to > ease the decision regarding this bug. > > Have a nice week-end! > Giulio -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: 03/09/15 - Cinnamon Testday
04/Set/2015 09:01, "Adam Williamson" <adamw...@fedoraproject.org> wrote: > > On Fri, 2015-09-04 at 08:54 +0200, Giulio (juliuxpigface) wrote: > > Hi folks. > > > > Does anybody know what happened to the Cinnamon TestDay? > > > > The related page appears to be still blank, so I'm wondering if the > > date > > has changed or the event has been actually ran without announces. > > We didn't get around to setting it up or announcing it properly, so > it'll be delayed (again) and run another day. I'll try and set it up > and send an announce in a bit. Thanks for your interest! > -- Thank you for the info. Tonight I shall have some spare time, so let me know if you need help in setting it up (l've never done such kinds of things before, but I can learn...). -- Giulio 'juliuxpigface' Fedora QA FAS: juliuxpigface || IRC: jpigface || GITHUB: pigjuliux WEB: https://pigjuliux.wordpress.com -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
03/09/15 - Cinnamon Testday
Hi folks. Does anybody know what happened to the Cinnamon TestDay? The related page appears to be still blank, so I'm wondering if the date has changed or the event has been actually ran without announces. Thank you. Giulio -- Giulio 'juliuxpigface' Fedora QA FAS: juliuxpigface || IRC: jpigface || GITHUB: pigjuliux WEB: https://pigjuliux.wordpress.com -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Question related to NetworkManager Testday (20/08/2015)
juliux.pigf...@gmail.com wrote: Hi guys. Just a simple question: is it possible to test with KDE instead of Workstation? I'm asking this because I already have a guest with F23 KDE, but I haven't got enough time to set up a new one with Gnome. Otherwise, if Workstation is mandatory, it's not a problem. I'll play with a live. Thank you. -- Giulio 'juliuxpigface' Fedora QA FAS: juliuxpigface || IRC: jpigface || GITHUB: pigjuliux WEB: https://pigjuliux.wordpress.com I've just seen that the TestDay's page clearly states that various setups are welcome (including different desktop environments). That's great! Excuse me for my previous mail. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Question related to NetworkManager Testday (20/08/2015)
Hi guys. Just a simple question: is it possible to test with KDE instead of Workstation? I'm asking this because I already have a guest with F23 KDE, but I haven't got enough time to set up a new one with Gnome. Otherwise, if Workstation is mandatory, it's not a problem. I'll play with a live. Thank you. -- Giulio 'juliuxpigface' Fedora QA FAS: juliuxpigface || IRC: jpigface || GITHUB: pigjuliux WEB: https://pigjuliux.wordpress.com -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
LiveUsb creator and kernel panic.
Hi folks. Since the tool 'liveusb-creator' had got a low coverage, I tried to follow the appropriate case in order to test it. I encountered this issue: https://bugzilla.redhat.com/show_bug.cgi?id=1250712 I proposed the bug as freeze exception, but I think that more testing is welcome, in order to discover if that tool is entirely broken. I may be totally wrong, but l-u-c doesn't seem reliable to me. Thank you for your help. -- Giulio 'juliuxpigface' Fedora QA FAS: juliuxpigface || IRC: jpigface || GITHUB: pigjuliux WEB: https://pigjuliux.wordpress.com -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Bug 1246252: testing needed!
Il 24/Lug/2015 19:33, Robert Knight kni...@princeton.edu ha scritto: Hi folks. I've recently proposed a new blocker for F23 Final. The problem is Gnome doesn't notify for available updates. The link is here: https://bugzilla.redhat.com/show_bug.cgi?id=1246252 But, since my current network is not always stable, I'd like to receive sone feedback in order to have a confirm that the bug is actually present (and therefore it isn't a problem of mine). The steps are simple: just boot an installed F23 Workstation (I chose 20150717, but the new tc that will be announced shortly is fine) and follow this testcase: https://fedoraproject.org/wiki/QA:Testcase_desktop_update_notification Thank you! -- Giulio (juliuxpigface) Nothing here, either. I also used 20150717. There was a notification that a component had crashed and been automatically reported. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test Hi Robert. Many thanks for your test. May you please post this comment on Bugzilla too? Thank you -- Giulio ( juliuxpigface) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Bug 1246252: testing needed!
Hi folks. I've recently proposed a new blocker for F23 Final. The problem is Gnome doesn't notify for available updates. The link is here: https://bugzilla.redhat.com/show_bug.cgi?id=1246252 But, since my current network is not always stable, I'd like to receive sone feedback in order to have a confirm that the bug is actually present (and therefore it isn't a problem of mine). The steps are simple: just boot an installed F23 Workstation (I chose 20150717, but the new tc that will be announced shortly is fine) and follow this testcase: https://fedoraproject.org/wiki/QA:Testcase_desktop_update_notification Thank you! -- Giulio (juliuxpigface) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: [Fedora QA] #476: Proposed Test Day - Cinnamon Spin
Il 17/Lug/2015 01:11, Fedora QA t...@fedorahosted.org ha scritto: #476: Proposed Test Day - Cinnamon Spin --+ Reporter: grinnz| Owner: Type: task | Status: new Priority: major | Milestone: Fedora 23 Component: Test Day | Version: Keywords:| Blocked By: Blocking:| --+ It would be awesome if the QA team could setup a test day for the new Cinnamon spin. I don't have a preference on the date. https://fedoraproject.org/wiki/Changes/Cinnamon_Spin -- Ticket URL: https://fedorahosted.org/fedora-qa/ticket/476 Fedora QA http://fedorahosted.org/fedora-qa Fedora Quality Assurance -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test This was also dicussed in a recent meeting and, as said there, it will be a great chance to engage people for testing. We might also discuss about the modality: since the standard test cases will be tested by us during release validation, I'd rather write a call for a sort of exploratory testing. Increasing people's freedom with the flexibility of exploratory testing, we might receive a broader coverage. My idea is to include a reference to the standard testcases inside the wiki page, but not to flag them as mandatory during the TestDay, in order to get some exploratory efforts. What do other QA folks think about it? Have a nice day --- Giulio (juliuxpigface) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: [Test-Announce] Fedora 23 Rawhide 20150714 nightly compose nominated for testing
Il giorno mer, 15/07/2015 alle 12.03 -0400, Robert Knight ha scritto: [Sorry for the spotty quoting -- I usually only get digests and this is cut and paste from the archive web pages.] satellit reports the same, but I saw progress displayed as usual in my tests. How much RAM does your test box have? MemTotal:3905728 kB I *think* https://www.happyassassin.net/temp/updates.img should be an image with the fixes for all three bugs (typo crash, autopart fail, selinux fail) combined, right now (though note, as the name rather implies, I tend to overwrite that location frequently with a new test image). Will try it as soon as I've sent this. 3. Strong passwords are required during installation. IIRC this is more or less by design; I think the idea was that anaconda was only going to roll back to the 'old' policy for 22, and from 23 onwards flavors are supposed to override it if they want to. There's probably details in the relevant FESCo ticket. Fine by me. 4. A Workstation install only allowed a single login. The second login does nothing except return to the login screen after the password is entered. How do you mean exactly - console or graphical logins? Were you using the 'switch user' mechanism, or just flipping back to the GDM instance that keeps running on tty1 or something (because...Wayland, I think)? A second graphical login fails. An ssh from another host succeeds. I just selected the Gnome logout in the top menu bar, under my id with entry logout. The login screen reappeared, but, after a pause, just puts the login screen back up. 5. Only once, the Storage spoke garbled the screen (sufficient improperly rendered horizontal lines so that the screen was unreadable). Huh, that's interesting - it'd certainly be worth reporting if you can reproduce it. Could be a graphics driver bug. I've been trying since unsuccessfully. I'll make more of an effort to capture the complete situation if it does re-occur. Regards, Robert -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test Hi folks. I've just encountered https://bugzilla.redhat.com/show_bug.cgi?id=1243543 on Workstation's live. I'm wondering if it's related to the issue you described or it's a brand new thing. Any clues? Thank you. -- Giulio 'juliuxpigface' Fedora QA FAS: juliuxpigface || IRC: jpigface || GITHUB: pigjuliux WEB: https://pigjuliux.wordpress.com -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Introduction
On 25/05/2015 Kevin and Nancy wrote: Greetings, I was hoping to join the team of those doing pre-release testing of Fedora. I am Kevin Bach, computer/network engineer, with more that 20 years experience. I'm from southern Indiana in the United States. I have extensive experience with Unix and Linux. I learned Berkley Unix at Purdue in the mid-1980's. I first installed Redhat for the company I worked for at the time in the late-1990's. I've installed Fedora for profit and non-profit entities since Fedora Core 4 (maybe 3, don't remember), and I've continued to use Fedora all they way through 21. (Looking forward to 22.) I've used or experimented with various versions of Unix and Linux, including Solaris, AIX, Ubuntu, etc. I'd be very enthusiastic to help with Fedora, and grateful for the opportunity. I am likewise grateful for the hard work of those reading this, and those who've contributed so much in the past. I don't use IRC right now, but I can easily get back into it for the sake of Fedora teamwork. Kevin Bach -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test Hi Kevin. Welcome to QA! Don't worry; if you use a modern client, IRC is pretty straightforward. I like xchat very much, but it clearly isn't the only one available on Fedora's repos. Also, feel free to ask questions if you are stuck somewhere. Kind regards // Giulio (juliuxpigface) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: [Test-Announce] Fedora 22 Final Release Candidate 2 (RC2) Available Now!
Il giorno mer, 20/05/2015 alle 20.53 -0600, Mike Ruckman ha scritto: As per the Fedora 22 schedule [1], Fedora 22 Final Release Candidate 2 (RC2) is now available for testing. Content information, including changes, can be found at https://fedorahosted.org/rel-eng/ticket/6166#comment:12. Please see the following pages for download links and testing instructions. Normally dl.fedoraproject.org should provide the fastest download, but download-ib01.fedoraproject.org is available as a mirror (with an approximately 1 hour lag) in case of trouble. To use it, just replace dl with download-ib01 in the download URL. Hi Mike. I regret to have to inform that the RC2 pages don't seem to include the download links. Actually, the Image table is void. I hit 'Refresh' multiple times on Firefox, but the grid remains empty. Thank you in advance. Kind regards. //Giulio (juliuxpigface) Installation: https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test Base: https://fedoraproject.org/wiki/Test_Results:Current_Base_Test Workstation and Desktop: https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test Server: https://fedoraproject.org/wiki/Test_Results:Current_Server_Test Cloud: https://fedoraproject.org/wiki/Test_Results:Current_Cloud_Test Summary: https://fedoraproject.org/wiki/Test_Results:Current_Summary All Final priority test cases for each of these test pages [2] must pass in order to meet the Final Release Criteria [3]. Help is available on #fedora-qa on irc.freenode.net [4], or on the test list [5]. Create Fedora 22 Final test compose (TC) and release candidate (RC) https://fedorahosted.org/rel-eng/ticket/6166 Current Blocker and Freeze Exception bugs: http://qa.fedoraproject.org/blockerbugs/current [1] http://fedorapeople.org/groups/schedule/f-22/f-22-quality-tasks.html [2] https://fedoraproject.org/wiki/QA:Release_validation_test_plan [3] https://fedoraproject.org/wiki/Fedora_22_Final_Release_Criteria [4] irc://irc.freenode.net/fedora-qa [5] https://admin.fedoraproject.org/mailman/listinfo/test -- // Mike -- Fedora QA freenode: roshi http://roshi.fedorapeople.org ___ test-announce mailing list test-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/test-announce -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Fedora 22 TC3 KDE and KSplash
On 11/05/2015 Jaroslav Reznik wrote: - Original Message - Hi folks. I'm currently testing the KDE live TC3. While performing QA:Testcase_base_startup, I saw that there isn't a KSplash theme with artworks from Fedora. The standard 'breeze' is used instead. I would not call it a fail, but if I remember right, previous releases shipped with a customized theme. Is this an intended behavior or is something missing? As all theming in Plasma is new due to switch to Plasma 5 and changes from old themes to new QML based themes, some pieces are still missing. Filling bug is a good idea but I'd not block on this. Long time ago I was doing all theming work but in the end, we just changed wallpapers to one theme. It should not be difficult just to patch standard Breeze to use Fedora wp. There were also plans for second Fedora theme for lock screens but it's not yet ready. Jaroslav Thank you! // Giulio (juliuxpigface) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test Hi guys. I'm writing in reference to the mail I've attached. I opened the report ( https://bugzilla.redhat.com/show_bug.cgi?id=1220497 ) and the maintainers quickly developed a valid update. On KDE Live TC4, the new theme exists, but breeze is still used by default. I'd like to fill a new bug-report (with priority set to low) in order to be sure that we don't forget this little issue. What is (in your opinion) the correct component? Shall I choose releng or what else? Thank you! //Giulio (juliuxpigface) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Fedora 22 TC3 KDE and KSplash
Hi folks. I'm currently testing the KDE live TC3. While performing QA:Testcase_base_startup, I saw that there isn't a KSplash theme with artworks from Fedora. The standard 'breeze' is used instead. I would not call it a fail, but I think that previous versions had a customized theme. Is this an intended behavior or is something missing? Thank you! // Giulio (juliuxpigfave) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Fedora 22 TC3 KDE and KSplash
Hi folks. I'm currently testing the KDE live TC3. While performing QA:Testcase_base_startup, I saw that there isn't a KSplash theme with artworks from Fedora. The standard 'breeze' is used instead. I would not call it a fail, but if I remember right, previous releases shipped with a customized theme. Is this an intended behavior or is something missing? Thank you! // Giulio (juliuxpigface) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Anyone with two AMDs?
On Wed, 06/05/2015 at 15.06 -0700, Adam Williamson wrote: On Wed, 2015-05-06 at 19:33 +0200, Giulio 'juliuxpigface' wrote: On Mon, 2015-05-04 at 21:56 +0200, Giulio (juliuxpigface) wrote: Hi folks. Does anyone with a laptop equipped with two Amd experience this? https://bugzilla.redhat.com/show_bug.cgi?id=1218364 I'm sorry but this is currently affecting my activity for QA as I can't use Fedora at all. I promise I'll be back as soon as I figure out what's happening with that laptop (*). Cheers guys. Feel free to contact me if you have got suggestions! There's a couple of other radeon parameters you might try twiddling: radeon.aspm=0 radeon.bapm=0 dunno if they'll help, but it can't hurt to try... Hi guys. Even though I found a workaround, yesterday I filled an upstream bug for the issue. The link is this: https://bugs.freedesktop.org/show_bug.cgi?id=90321 As shown there, Alex Deucher proposed a patch. I'm wondering what I'm supposed to do now. In order to test it, I believe that recompiling the kernel is mandatory, but I'm not sure (this is one of my first upstream tickets, sorry). Should I try to get my hands on it (I don't really know how to, anyway, but I might learn...), or shall I ping Fedora's maintainer? The way I like to do this (there are others, like poma's) is to rebuild the kernel package. Clone it from git: fedpkg --anonymous clone kernel cd kernel You can stay on master branch, which is the rawhide package, and so right now will give you a 4.1rc2 kernel. Or you can do 'fedpkg - -anonymous switch-branch f22' to switch to the f22 branch. Copy the patch into the directory, then edit the kernel.spec file. Find the two big blocks where patches are defined and applied. There's a comment at the end of the patch definitions - # END OF FEDORA PATCH DEFINITIONS - so search for that. Add your patch right above it, with a number higher than the last patch. So right now, for instance, you'd wind up with this, on the master branch: #rhbz 1218662 Patch26199: libata-Blacklist-queued-TRIM-on-all-Samsung-800 -seri.patch Patch26200: 0001-drm-radeon-handle-audio-for-PX.patch # END OF PATCH DEFINITIONS There are similar comments around the patch application block, so you can find that similarly - look for # END OF FEDORA PATCH APPLICATIONS. Edit as appropriate again. You'll wind up with: #rhbz 1218662 ApplyPatch libata-Blacklist-queued-TRIM-on-all-Samsung-800-seri.patch ApplyPatch 0001-drm-radeon-handle-audio-for-PX.patch # END OF PATCH APPLICATIONS Now you want to bump the package version a bit so it'll be newer than the current kernel package. There's actually a handy macro for this purpose in the kernel spec, near the top: # % define buildid .local You can uncomment that and change it. So for e.g. you could do: %define buildid .1.juliux and then you'd wind up with a kernel based on '4.1.0-0.rc2.git2.1' whose version would be '4.1.0-0.rc2.git2.1.1.juliux' - makes it easy to notice when you're running your own modified kernel. If you like you can put a changelog entry in, following the format of the existing ones - it's not required, but it can be handy so you remember what the hell you did two weeks later. :) Then you can build a .src.rpm: fedpkg --anonymous srpm Then you just have to build it. If you're a packager you can do a Koji scratch build, but if not, you can use mock: mock -r fedora-22-x86_64 --rebuild kernel-4.1.0 -0.rc2.git2.1.1.juliux.src.rpm for e.g. Or of course you can just build it with 'rpm --rebuild', but I like to keep my package builds clean. To use mock you have to set it up if you never have - https://fedoraproject.org/wiki/Using_Mock_to_test_package_builds . You can fiddle about with 'make config-release' and the '%define debugbuildsenabled 0/1' line in kernel.spec - if you want a non-debug kernel and a faster build, you want to run 'make config-release' before creating the .src.rpm, and make sure it's '%define debugbuildsenabled 0' not '%define debugbuildsenabled 1' - but that's not compulsory. Good luck :) If you test and find the patch works it'll likely start working its way upstream, and you could poke the Fedora maintainers and see if they're willing to backport it to Rawhide and F22 kernels. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net Hi guys. Sorry if I bump this again. I've been trying Adam's suggestions, but my problem is that my / partition goes easily out of space while mocking (throwing 'OSError: [Errno 28] No space left on device' explicitly. 'df -h
Re: Anyone with two AMDs?
On 10/05/2015 12.44 +0200, poma wrote: On 10.05.2015 11:24, Giulio 'juliuxpigface' wrote: On Wed, 06/05/2015 at 15.06 -0700, Adam Williamson wrote: On Wed, 2015-05-06 at 19:33 +0200, Giulio 'juliuxpigface' wrote: On Mon, 2015-05-04 at 21:56 +0200, Giulio (juliuxpigface) wrote: Hi folks. Does anyone with a laptop equipped with two Amd experience this? https://bugzilla.redhat.com/show_bug.cgi?id=1218364 I'm sorry but this is currently affecting my activity for QA as I can't use Fedora at all. I promise I'll be back as soon as I figure out what's happening with that laptop (*). Cheers guys. Feel free to contact me if you have got suggestions! There's a couple of other radeon parameters you might try twiddling: radeon.aspm=0 radeon.bapm=0 dunno if they'll help, but it can't hurt to try... Hi guys. Even though I found a workaround, yesterday I filled an upstream bug for the issue. The link is this: https://bugs.freedesktop.org/show_bug.cgi?id=90321 As shown there, Alex Deucher proposed a patch. I'm wondering what I'm supposed to do now. In order to test it, I believe that recompiling the kernel is mandatory, but I'm not sure (this is one of my first upstream tickets, sorry). Should I try to get my hands on it (I don't really know how to, anyway, but I might learn...), or shall I ping Fedora's maintainer? The way I like to do this (there are others, like poma's) is to rebuild the kernel package. Clone it from git: fedpkg --anonymous clone kernel cd kernel You can stay on master branch, which is the rawhide package, and so right now will give you a 4.1rc2 kernel. Or you can do 'fedpkg - -anonymous switch-branch f22' to switch to the f22 branch. Copy the patch into the directory, then edit the kernel.spec file. Find the two big blocks where patches are defined and applied. There's a comment at the end of the patch definitions - # END OF FEDORA PATCH DEFINITIONS - so search for that. Add your patch right above it, with a number higher than the last patch. So right now, for instance, you'd wind up with this, on the master branch: #rhbz 1218662 Patch26199: libata-Blacklist-queued-TRIM-on-all-Samsung-800 -seri.patch Patch26200: 0001-drm-radeon-handle-audio-for-PX.patch # END OF PATCH DEFINITIONS There are similar comments around the patch application block, so you can find that similarly - look for # END OF FEDORA PATCH APPLICATIONS. Edit as appropriate again. You'll wind up with: #rhbz 1218662 ApplyPatch libata-Blacklist-queued-TRIM-on-all-Samsung-800 -seri.patch ApplyPatch 0001-drm-radeon-handle-audio-for-PX.patch # END OF PATCH APPLICATIONS Now you want to bump the package version a bit so it'll be newer than the current kernel package. There's actually a handy macro for this purpose in the kernel spec, near the top: # % define buildid .local You can uncomment that and change it. So for e.g. you could do: %define buildid .1.juliux and then you'd wind up with a kernel based on '4.1.0 -0.rc2.git2.1' whose version would be '4.1.0-0.rc2.git2.1.1.juliux' - makes it easy to notice when you're running your own modified kernel. If you like you can put a changelog entry in, following the format of the existing ones - it's not required, but it can be handy so you remember what the hell you did two weeks later. :) Then you can build a .src.rpm: fedpkg --anonymous srpm Then you just have to build it. If you're a packager you can do a Koji scratch build, but if not, you can use mock: mock -r fedora-22-x86_64 --rebuild kernel-4.1.0 -0.rc2.git2.1.1.juliux.src.rpm for e.g. Or of course you can just build it with 'rpm - -rebuild', but I like to keep my package builds clean. To use mock you have to set it up if you never have - https://fedoraproject.org/wiki/Using_Mock_to_test_package_builds . You can fiddle about with 'make config-release' and the '%define debugbuildsenabled 0/1' line in kernel.spec - if you want a non -debug kernel and a faster build, you want to run 'make config-release' before creating the .src.rpm, and make sure it's '%define debugbuildsenabled 0' not '%define debugbuildsenabled 1' - but that's not compulsory. Good luck :) If you test and find the patch works it'll likely start working its way upstream, and you
Anyone with two AMDs?
Hi folks. Does anyone with a laptop equipped with two Amd experience this? https://bugzilla.redhat.com/show_bug.cgi?id=1218364 I'm sorry but this is currently affecting my activity for QA as I can't use Fedora at all. I promise I'll be back as soon as I figure out what's happening with that laptop (*). Cheers guys. Feel free to contact me if you have got suggestions! // Giulio (juliuxpigface) (*) or maybe I'll be back on track with a new computer, because the unnecessary overhead caused by double-gpus is tiring me... -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: LXDE Final TC1 and 'abrt-cli ls'
02/05/2015 on 10.49 +0200, František Zatloukal wrote: Hi, the missing .service file (which is probably causing Segmentation fault) is provided by package abrt-dbus. Is that package installed? Hi! Thank you for the advice! That package wasn't installed. After obtaining it, 'abrt-cli ls' works. So... Now the question is... Since (in my opinion) it should be there by default, against what should I report this issue? Thank you! // Giulio (juliuxpigface) 2015-05-02 10:44 GMT+02:00 Giulio 'juliuxpigface' juliuxpigf...@fedoraproject.org: Hi folks. I'm testing LXDE spin and I found what seems like an incorrect behavior . [root@localhost ~]# abrt-cli ls Can't get problem list from abrt-dbus: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.problems was not provided by any .service files (process:2069): GLib-CRITICAL **: g_ptr_array_sort_with_data: assertion 'array != NULL' failed Segmentation fault (core dumped) Since LXDE doesn't offer a graphical fronted for abrt by default, I think that the impossibility to use at least abrt-cli is not a good thing. The problem is... I'd like to report it as a bug, but I don't know the right component I can choose. I think it's not an issue from abrt-cli itself, since it works flawlessly on other spins. Does anyone have suggestions? Kind regards. // Giulio (juliuxpigface) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test -- Best regards / S pozdravem, František Zatloukal Web: frantisek.zatloukalu.eu -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: [Test-Announce] 2015-04-30: Software Center / Apper Test Day!
On Fri, 01/05/2015 at 14.21 -0700, Adam Williamson wrote: On Fri, 2015-05-01 at 15:30 -0500, Abdel G. Martínez L. wrote: Hello Adam! Is this Test Day still available? I see updates on the wiki but no one have tested. When is going to be the real Test Day? Hum? I see results from four different testers: pschindl, lbrabec, juliuxpigface, and satellit. Indeed juliux even tested yumex too (I have to add a note of those results to the page). You can still run the tests and add results now, though - as it says at the top of the page: If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at Bugzilla, and add your results to the results section. Thanks! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net Hi Abdel. Try to refresh the page inside your browser. // Giulio (juliuxpigface) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
LXDE Final TC1 and 'abrt-cli ls'
Hi folks. I'm testing LXDE spin and I found what seems like an incorrect behavior . [root@localhost ~]# abrt-cli ls Can't get problem list from abrt-dbus: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.problems was not provided by any .service files (process:2069): GLib-CRITICAL **: g_ptr_array_sort_with_data: assertion 'array != NULL' failed Segmentation fault (core dumped) Since LXDE doesn't offer a graphical fronted for abrt by default, I think that the impossibility to use at least abrt-cli is not a good thing. The problem is... I'd like to report it as a bug, but I don't know the right component I can choose. I think it's not an issue from abrt-cli itself, since it works flawlessly on other spins. Does anyone have suggestions? Kind regards. // Giulio (juliuxpigface) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: LXDE Final TC1 and 'abrt-cli ls'
Il giorno sab, 02/05/2015 alle 08.26 -0700, Adam Williamson ha scritto: On Sat, 2015-05-02 at 13:42 +0200, František Zatloukal wrote: I believe it should be installed by default too. But I don't know against which component you should report it. Maybe somebody else will know. Well caught, guys! The obvious thing to do is to file a bug against abrt-cli. If A runs when B is installed, but A doesn't run when B isn't, and A doesn't have a dependency on B, it's a pretty safe bet that filing a bug A should depend on B is the right thing to do. Even if the fix turns out to be something less obvious, that's the right starting point. Thanks! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net Many thanks! https://bugzilla.redhat.com/show_bug.cgi?id=1217901 //Giulio (juliuxpigface) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Proposal: Split up QA:Testcase_desktop_updates into three separate test cases
Il giorno lun, 27/04/2015 alle 18.09 -0700, Adam Williamson ha scritto: Hey folks! So several people have commented in the past that https://fedoraproject.org/wiki/QA:Testcase_desktop_updates is kind of a mess, and I think that's correct. I think we were trying to make things 'efficient' at the time by exercising several different things in one test, but it really does result in a messy, hard-to-comprehend test case. So, I propose we split it into three separate test cases, and I've drafted them up: https://fedoraproject.org/wiki/User:Adamwill/Draft_QA_Testcase_base_u pd ate_cli https://fedoraproject.org/wiki/User:Adamwill/Draft_QA_Testcase_deskto p_ update_graphical https://fedoraproject.org/wiki/User:Adamwill/Draft_QA_Testcase_deskto p_ update_notification The first would be an Alpha test case in the Base (not desktop) results page, and just covers installing updates with yum/dnf. The second would be a Beta test case in the Desktop page, and covers installing updates from a graphical desktop. The third would be a Final test case in the Desktop page, and covers notification of available updates. I'm also planning to draft some additional test cases covering package installation and removal tomorrow - mainly for the test day we have coming up, but it would probably not be a bad idea to have them as release validation tests as well. What do folks think? Does this look like an improvement? Thanks! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net Hi Adam. When we see a single 'fail' on the current matrix, we can not be sure about what part of the process might be broken (dnf? apper? notifications? kde's applet?). So, in my opinion, the tests are much clearer as they appear in your drafts. They could improve the readability of our results. Indeed, I prefer little, 'monolithic' test-cases which are easier to follow and to track down. Have a nice day! // Giulio (juliuxpigface) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: grub -
On 24/04/2015 11.13 +0200, poma wrote: On 24.04.2015 07:50, Giulio 'juliuxpigface' wrote: Il giorno gio, 23/04/2015 alle 22.58 +0200, poma ha scritto: On 23.04.2015 21:20, Giulio 'juliuxpigface' wrote: On 23.04.2015 20:23, Bob Goodwin ~ Zuni, Virginia, USA wrote: Can I simply delete rhgb quiet in order to show what's happening Of course, this is my default everywhere. during the boot process, GRUB_CMDLINE_LINUX= ? I hesitate to make a change and find that I can't boot the computer ... [bobg@box10 ~]$ cat /etc/default/grub GRUB_TIMEOUT=15 GRUB_DISTRIBUTOR=$(sed 's, release .*$,,g' /etc/system -release) GRUB_DEFAULT=saved GRUB_DISABLE_SUBMENU=true GRUB_TERMINAL_OUTPUT=console GRUB_CMDLINE_LINUX=rhgb quiet GRUB_DISABLE_RECOVERY=true Bob If you don't want to touch the bootloader's configuration, there is another easy (and non-persistent) way. You could stop Grub's countdown, hit 'e', erase 'rhgb quiet' and then boot (Ctrl+X, if I remember right). //Giulio (juliuxpigface) Giulio, how can the same thing be done with the Extlinux? 1) Press a button in order to stop the countdown. This is a segment of my Extlinux configuration: ui menu.c32 menu title Extlinux timeout 10 label Fedora ... ... If I press e.g. an A key, it will only reset the 10 secondi countdown, but will not stop it. What must I do to actually stop it? Well, I'm trying with KDE live (Beta TC2) and pressing a key (e.g. A), actually stops the countdown. 2) Press 'tab' on the row you want to customize. How to get to the row I want to customize? With, 'row' I mean 'menu item'. Just move with the arrows key, highlight, for example, 'Start Fedora Live' and press tab. 3) You should now be able to erase 'rhgb' and 'quiet'. After all this, what must I do to finally start the boot process? Just hit the 'enter' key. //Giulio (juliuxpigface) Thanks for your help. // Giulio (juliuxpigface) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Is upgrading F20 to F22 not officially supported?
Hello beautiful testers :) While rolling myself on the mud and testing FedUp for the TestDay, I reported bug https://bugzilla.redhat.com/show_bug.cgi?id=1214150 The maintainer closed it saying that upgrading from Fedora 20 to Fedora 22 isn't officially supported. If that's true, I think we need to improve the TestDay's page. Well... At this time, we'd better remember that bit for the next release (if there will be another event related to FedUp). What do ya think? Cheerz // Giulio (juliuxpigface) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: grub -
On 24.04.2015 13:02, Giulio 'juliuxpigface' wrote: On 24/04/2015 11.13 +0200, poma wrote: On 24.04.2015 07:50, Giulio 'juliuxpigface' wrote: Il giorno gio, 23/04/2015 alle 22.58 +0200, poma ha scritto: On 23.04.2015 21:20, Giulio 'juliuxpigface' wrote: On 23.04.2015 20:23, Bob Goodwin ~ Zuni, Virginia, USA wrote: Can I simply delete rhgb quiet in order to show what's happening Of course, this is my default everywhere. during the boot process, GRUB_CMDLINE_LINUX= ? I hesitate to make a change and find that I can't boot the computer ... [bobg@box10 ~]$ cat /etc/default/grub GRUB_TIMEOUT=15 GRUB_DISTRIBUTOR=$(sed 's, release .*$,,g' /etc/system -release) GRUB_DEFAULT=saved GRUB_DISABLE_SUBMENU=true GRUB_TERMINAL_OUTPUT=console GRUB_CMDLINE_LINUX=rhgb quiet GRUB_DISABLE_RECOVERY=true Bob If you don't want to touch the bootloader's configuration, there is another easy (and non-persistent) way. You could stop Grub's countdown, hit 'e', erase 'rhgb quiet' and then boot (Ctrl+X, if I remember right). //Giulio (juliuxpigface) Giulio, how can the same thing be done with the Extlinux? 1) Press a button in order to stop the countdown. This is a segment of my Extlinux configuration: ui menu.c32 menu title Extlinux timeout 10 label Fedora ... ... If I press e.g. an A key, it will only reset the 10 secondi countdown, but will not stop it. What must I do to actually stop it? Well, I'm trying with KDE live (Beta TC2) and pressing a key (e.g. A), actually stops the countdown. I tried, but cannot possibly do it like that. Can you tell me what is the version? I think that all the Live ISOs provide the same functionality. But... Wait... Actually, I was wrong with one of my previous answers... I've just tried more carefully ExtLinux inside Beta KDE and there the countdown stops when I hit the arrow keys. As you said, if we hit 'A' it resets the 10 seconds. So... Sorry, I did a mystake :). 2) Press 'tab' on the row you want to customize. How to get to the row I want to customize? With, 'row' I mean 'menu item'. Just move with the arrows key, highlight, for example, 'Start Fedora Live' and press tab. AHA, that could be it! 3) You should now be able to erase 'rhgb' and 'quiet'. After all this, what must I do to finally start the boot process? Just hit the 'enter' key. Uhh, how did I miss that. //Giulio (juliuxpigface) Thanks for your help. // Giulio (juliuxpigface) Many thanks. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Is upgrading F20 to F22 not officially supported?
Hello beautiful testers :) While rolling myself on the mud and testing FedUp for the TestDay, I reported bug https://bugzilla.redhat.com/show_bug.cgi?id=1214150 The maintainer closed it saying that upgrading from Fedora 20 to Fedora 22 isn't officially supported. If that's true, I think we need to improve the TestDay's page. Well... At this time, we'd better remember that bit for the next release (if there will be another event related to FedUp). What do ya think? Cheerz I upgraded via fedup from 20 to 22 but I did add --nogpg to the command line. Plasma 5 desktop, it's still a little rough but almost everything updated. I didn't realize it was unsupported. I actually imported the right keys and did the upgrade. It worked flawlessly for me too. The fact is... Does anybody know if this is really unsupported? Is there an 'official statement' or so? 1) If yes, dnf should be able to automatically import the keys and I should reopen the bug. 2) If not, then we are fine and the bug I reported should remain close as it is now. Thanks! // Giulio (juliuxpigface) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: grub -
On 23.04.2015 20:23, Bob Goodwin ~ Zuni, Virginia, USA wrote: Can I simply delete rhgb quiet in order to show what's happening Of course, this is my default everywhere. during the boot process, GRUB_CMDLINE_LINUX= ? I hesitate to make a change and find that I can't boot the computer ... [bobg@box10 ~]$ cat /etc/default/grub GRUB_TIMEOUT=15 GRUB_DISTRIBUTOR=$(sed 's, release .*$,,g' /etc/system-release) GRUB_DEFAULT=saved GRUB_DISABLE_SUBMENU=true GRUB_TERMINAL_OUTPUT=console GRUB_CMDLINE_LINUX=rhgb quiet GRUB_DISABLE_RECOVERY=true Bob If you don't want to touch the bootloader's configuration, there is another easy (and non-persistent) way. You could stop Grub's countdown, hit 'e', erase 'rhgb quiet' and then boot (Ctrl+X, if I remember right). //Giulio (juliuxpigface) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: grub -
Il giorno gio, 23/04/2015 alle 22.58 +0200, poma ha scritto: On 23.04.2015 21:20, Giulio 'juliuxpigface' wrote: On 23.04.2015 20:23, Bob Goodwin ~ Zuni, Virginia, USA wrote: Can I simply delete rhgb quiet in order to show what's happening Of course, this is my default everywhere. during the boot process, GRUB_CMDLINE_LINUX= ? I hesitate to make a change and find that I can't boot the computer ... [bobg@box10 ~]$ cat /etc/default/grub GRUB_TIMEOUT=15 GRUB_DISTRIBUTOR=$(sed 's, release .*$,,g' /etc/system -release) GRUB_DEFAULT=saved GRUB_DISABLE_SUBMENU=true GRUB_TERMINAL_OUTPUT=console GRUB_CMDLINE_LINUX=rhgb quiet GRUB_DISABLE_RECOVERY=true Bob If you don't want to touch the bootloader's configuration, there is another easy (and non-persistent) way. You could stop Grub's countdown, hit 'e', erase 'rhgb quiet' and then boot (Ctrl+X, if I remember right). //Giulio (juliuxpigface) Giulio, how can the same thing be done with the Extlinux? 1) Press a button in order to stop the countdown. 2) Press 'tab' on the row you want to customize. 3) You should now be able to erase 'rhgb' and 'quiet'. //Giulio (juliuxpigface) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Fedora 22 Workstation Beta Release Candidate 1
We don't think it's 'AMD users', because we've tested other systems with AMD graphics adapters and they work fine. But it *may* be 'hybrid graphics laptops', which would be something of a problem because there's a lot of those. So can I ask the list: can anyone who has a laptop with hybrid graphics (one with two adapters, one Intel, one higher-powered AMD or NVIDIA) boot the F22 Beta RC1 Workstation live image and let us know if they successfully reach a desktop? Thanks! It'd be good to have more data on how widespread this problem is. My laptop is equipped with two Amd cards (4200m+5650m). I've just tried Fedora-Live-Workstation-x86_64-22_Beta-1.iso on a USB-stick. I don't reach the desktop, the session apparently stucks with the message A start job is running for Wait For Plymouth Screen to Quit. startx on another TTY makes me correctly jump to a Gnome session. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Setting the keyboard layout rather late during F22-Beta installation
Hi all testers, Running actually a test install of F22 beta (Fedora-Workstation-netinst-x86_64-22_Beta.iso). I forgot to define my keyboard layout, so I tried to modify it during the install process actually running. Therefore I clicked on the keybord button (US/top/right of the graphical installer window), but nothing happens. So my question: Is this a bug, or have I to wait until the system is completely installed, and then to catch up this point? Kind regards Joachim Backes -- Fedora release 22 (Twenty Two) Kernel-4.0.0-0.rc6.git2.1.fc22.x86_64 Joachim Backes joachim.bac...@rhrk.uni-kl.de https://www-user.rhrk.uni-kl.de/~backes Hi Joachim. I'm pretty sure that the label you clicked is isn't editable at all. I'd bet it's there just to remember what layout you chose, in order to make you more conscious while entering passwords. Layout should be changed before launching the effective installation process (the one where you can add an user and modify root's password). Alternatively, you may switch it after the completion. Regards // Giulio (juliuxpigface) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: liveusb-creator and cp - non-destructive method
Hi guys. I've been trying to create a USB stick with the GUI 'liveusb ---reset-mbr'. The ISO is Fedora-Live-KDE-x86_64-22_Beta-TC6.iso and the USB stick is a new one (I'm almost sure it is sane). There are two final results: 1) The 'dd method' seems to work fine and creates a bootable device 2) The 'cp method' seems to work fine, but then, after booting the stick, I receive the message 'Missing Operative System' Is that an intended behavior? Have you ever experienced this issue? By the way, there is a similar bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1175514 But I'm sure I didn't set up an overlay. Kind regards. // Giulio (juliuxpigface) Well, after a hour or so of testing I found that it probably was something related to the way I formatted the USB stick's partition. I checked with KDE's and Mate's ISO: the 'cp' method worked and created bootable devices. I also did some tests with (and without) custom labels nor boot's flag. I was not able to reproduce the issue at all. The tool behaved as it should; so for me the case QA:Testcase_USB_stick_Live LiveUSB-creator finally passes. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
liveusb-creator and cp - non-destructive method
Hi guys. I've been trying to create a USB stick with the GUI 'liveusb ---reset-mbr'. The ISO is Fedora-Live-KDE-x86_64-22_Beta-TC6.iso and the USB stick is a new one (I'm almost sure it is sane). There are two final results: 1) The 'dd method' seems to work fine and creates a bootable device 2) The 'cp method' seems to work fine, but then, after booting the stick, I receive the message 'Missing Operative System' Is that an intended behavior? Have you ever experienced this issue? By the way, there is a similar bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1175514 But I'm sure I didn't set up an overlay. Kind regards. // Giulio (juliuxpigface) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: QA:Testcase_desktop_updates (notifications) failure on KDE
Giulio 'juliuxpigface' wrote: Hi guys, I've just reported the bug https://bugzilla.redhat.com/show_bug.cgi?id=1206760 encountered while I was testing the behavior of a freshly-installed Beta-TC5 with KDE. As you surely know, this is described by part of QA:Testcase_desktop_updates and is one of the cases listed under Release-blocking desktops: x86 / x86_64. What am I exactly supposed to do now? Should I propose it as a blocker or freeze exception? Yes, it's a blocker, but hopefully it won't come to that (the proposed updater replacement just got stable autokarma in -testing). -- Rex Hi Rex, thank you for your answers (both here and on bugzilla). I apologize for the questions, but as I keep saying I'm new and I'm still learning. 1) Is there anything further I should do with the bug-report? Are other steps required or it's ok as it is now? 2) Then; sorry but I didn't understand... Should I mark the failure as a blocker, even though the bug it's now solved? Kind regards. // Giulio (juliuxpigface) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F22: nautilus will not allow desktop icons if using session type Gnome on Wayland
Hi Joachim, I think it's not a bug, the warning is clear enough. I'd say that this feature is not ready yet, but the developers are aware of it and know it's missing. The message is like a placeholder that warns users, but it's not a real error/exception. But hey, this is just my opinion and experienced users may know something I don't :)... Regards // Giulio (juliuxpigface) On 03/28/2015 08:07 AM, Adam Williamson wrote: On Sat, 2015-03-28 at 07:34 +0100, Joachim Backes wrote: Changed my session type to Gnome on Wayland. After relogging in, I see no more desktop icons. Killing nautilus and starting in a gnome-terminal, I see the following message: ** (nautilus:4636): Warning **: Desktop icons only supported on X11. Desktop not created. Will this mean that nautilus will not run completely on Gnome/Wayland? Well, I mean, it means what it says. It can't display icons on Wayland. I'm not sure what else you're asking? Is this a bug or a feature? Additionally, will this mean that nautilus will be never running under wayland? Joachim Backes -- Fedora release 22 (Twenty Two) Kernel-4.0.0-0.rc5.git4.1.fc22.x86_64 Joachim Backes joachim.bac...@rhrk.uni-kl.de https://www-user.rhrk.uni-kl.de/~backes -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
QA:Testcase_desktop_updates (notifications) failure on KDE
Hi guys, I've just reported the bug https://bugzilla.redhat.com/show_bug.cgi?id=1206760 encountered while I was testing the behavior of a freshly-installed Beta-TC5 with KDE. As you surely know, this is described by part of QA:Testcase_desktop_updates and is one of the cases listed under Release-blocking desktops: x86 / x86_64. What am I exactly supposed to do now? Should I propose it as a blocker or freeze exception? Anyway, more testing (especially from experienced users) is obviously welcome! Thank you in advance. Kind regards. // Giulio (juliuxpigface) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Fedora 22 Beta blocker bug status #1
Testers, please test and karma these updates: https://admin.fedoraproject.org/updates/libedit-3.1-11.20141030cvs.fc22 https://admin.fedoraproject.org/updates/FEDORA-2015-4398 (you can up- karma that one if networking works in the TC4 installer) https://admin.fedoraproject.org/updates/fedora-release-22-0.14 Hi Adam (and others). I'd like to ask you some questions: 1) Have you got a kickstart for building a custom 'boot.iso' with the updated libedit-3.1-11.20141030cvs.fc22? It seems like it's a simple case to test (just need to navigate through the GUI in Anaconda), but I really have no idea about how I can build an appropriate ISO. 2) Ok, this is fine, I will test a TC4 installation this evening and give my karma if networking works in Anaconda. 3) I have really no idea on how I can test the third case. Updating my Rawhide and experiencing no evident issues is enough? Sorry for the silly questions, but as I said, I'm new to this world so I can't understand everything. Kind regards // Giulio (juliuxpigfacE) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Beta TC4 Desktop TestCases: where should I post results?
Hi all guys. First of all, thank you for the welcome and the kind words. Let's prepare some work for tomorrow's evening... I'd like to perform some tests on my KVM against Beta TC4 Desktop. I'm just a bit unsure about the right place which holds the results; actually I found two pages. https://fedoraproject.org/wiki/Test_Results:Fedora_22_Beta_TC4_Summary#Desktop https://fedoraproject.org/wiki/Test_Results:Fedora_22_Beta_TC4_Desktop?rd=Test_Results:Current_Desktop_Test#Test_Matrix What is the difference between the two pages? Where should I write my results? I'm pretty sure the first is the preferred one (because other users have inserted their work there). Am I right? Thank you in advance. // Giulio (juliuxpigface) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Booting directly to runlevel 5 prevents from login prompt on the tty's
Hi Joachim, although my Fedora 22 is not fully updated (will do it as soon as possible), I experience exactly the same issue. It sounds like a bug but, for a report, I wonder what is the right component we could choose... Does anybody have a clue? Regards //Giulio (juliuxpigface) Hi all testers, I'm running f22 with *all* updates. Since yesterday, if I boot directly to runlevel 5, I no more get a login prompt any tty (CtrlAltF...). The graphical session is running fine. What I see on the tty's is only a message: --- snip -- a start job is running for wait for plymouth boot screen to quit (...min...s / no limit). --- snap -- Rebooting to runlevel 3 works fine, login prompt on all tty's. Anybody sees this too? Kind regards Joachim Backes -- Fedora release 22 (Twenty Two) Kernel-4.0.0-0.rc5.git1.3.fc22.x86_64 Joachim Backes joachim.bac...@rhrk.uni-kl.de https://www-user.rhrk.uni-kl.de/~backes -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
