[qubes-users] Qubes installed and booted correctly. But password does not work.
Wbat version of qubes 3.2 or 4.0? So its the scrn lck password the first luks password is fine. I thought this was fix3d but I have not changed mine is so long as i did it manuallyqubes when you cirst install have to use the username user for the first time during setup. After that you can create a different username password combo. Again this is if this was not changed in updates. I just got use to usimg uswrname user duri g install setup and chnaging later so I wohld not have noticed it being fixed. I defer to anyone that is more current on this but I would redo setup and make username user and set the password. Then after that add a different username password or just keep user as name whatever. AgaiN I difer to other that are more current on this. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/54f09f0b-d61b-4cac-af4e-f1938b5ce284%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: [qubes-project] Hosting for OpenQA instance
W dniu poniedziałek, 29 stycznia 2018 00:39:06 UTC+1 użytkownik Marek Marczykowski-Górecki napisał: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On Sun, Jan 28, 2018 at 09:38:17AM -0800, Yethal wrote: > > I have a spare machine I can donate. If any of the Qubes devs are > > Warsaw-based I can even bring it over. > > Thanks! > > We'd prefer a machine hosted somewhere, but just hardware also could be > useful - we can look for place to host it separately. What are physical > dimensions of it? Rack case, or tower, or else? > What CPU and RAM size it have? > > - -- > Best Regards, > Marek Marczykowski-Górecki > Invisible Things Lab > A: Because it messes up the order in which people normally read text. > Q: Why is top-posting such a bad thing? > -BEGIN PGP SIGNATURE- > > iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlpuXqwACgkQ24/THMrX > 1yxMsQf/V2ToVljqO92/QtUgUqPN7E7w579FOWrqedexnLYHl4Sg1KjHyvzpSMA7 > hg4vHP3DxD2r7LjEmPBQ2YJM0PlS3MBubIUcbsyclQUMvUwqPOrJnBYtHV2VA8JH > w2sDMYxzRXn2BqvZxwyudrH/msp3aH+8qxmd1yUNzPpiKXwcCw87uNv+aqh3ZUeF > uLTbpuT22/7WFvpjB50kBPPC4eCvy/eEjghviKSqLClpIbLSc/Ztq1xVBvceXTGd > uElCwGEAX1Y3Kemmsz01Qz6Vld2eGGXLzPH795EBVHtGrePPKIRTkq279mUXY3qe > kTsqKijqo22OM9pGOaZ/HHJifuSfIw== > =x9o+ > -END PGP SIGNATURE- Regular tower pc. Specs are nothing special, dual core core 2 duo and 4gb of ram but I did manage to run Qubes 3.2 on it so at least some tests should be possible on it. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/385c3acf-fec7-4867-926c-f40920fc5d28%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Qubes installed and booted correctly. But password does not work.
Got Q installed and booted, but it continues to reject the second password(the one that asks for both my name and a password) Yes, I did carefully write the password down when I created it, but it is simply not acceptable. Sup Dat? Thank you very much for reading this, and even more if you can come up with a solution that works. t...@amp-up.com -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/a2fc424d-cb9e-429d-ba4c-7533992a6135%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] how to show menu bar in qubes VM Manager
jerr...@disroot.org: > i clicked view and hide something i think > Right click inside the window, click "show menu bar" at the bottom of the list. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/f7885424-acc9-22d1-2ab3-8bb8dc9dc1db%40riseup.net. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Qubes 3.2 after patching
Hello. So, I received Xen packages, version 4.6.6-36, via dom0 --enablerepo=qubes-dom0-security-testing. I changed 1) the (xscreensaver) password and 2) LUKS passphrase. Now the questions: Can I start with 3) disk reencrypting (reinstalling Qubes 3.2., restoring from backup) and 4) generating new secrets (PGP, passwords …) now – or do I have to wait until Xen 4.6.6-36 has landed in the stable repository? Or do I start 1)–4) of Qubes' »Suggested actions after patching« anew after Xen 4.6.6-36 has landed in stable repository? And how do I know when 4.6.6-36 has landed there? (I'm always updating Qubes via dom0 with --enablerepo=qubes-dom0-security-testing enabled and never faced problems with that.) Please excuse my confusion. Thanks, r. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/p4q7t2%241cg%241%40blaine.gmane.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Qubes 3.2 installation will not boot on Dell Inspiron 7000 Gaming series laptop
I had a similar issue with installing Qubes 4 rc3 on an external drive for
triple boot on a Dell laptop. The response by "yuraeitha" in that thread ("Can
I install qubes 4.0 rc3 on an external hard drive") was very informative. My
current workaround, at least until I decide to install on the SATA drive, was
to install using legacy boot. It means that I can't boot using the grub list,
but instead have to hit F12 and choose it from the BIOS boot list as a legacy
boot up. It's an extra button push, but not a big hassle.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/5ea26d81-25a2-456f-8f85-9849727885b7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: I think I've mounted my iny internal hard drive exactly wrong...
Thanks for you help --- again. Your widget discussion is what did it. In KDE, I didn't see the widget for adding disks to VMs, but it's there in the XCFe desktop. So instead of using the widget in KDE, I did everything by hand from the command line. Since the SATA disk partitions (sda1-sda8) were in /dev in dom0, I could manually mount them (even though I get I'm not supposed to -- I'm playing with it, after all). However, those devices simply were not visible in the other VMs. But... when I logged in using the default desktop, there is was. And all of the SATA drives are available, and it works fine. So, I gotta figure out a) how to find and get the widget showing in KDE, and/or what the qvm-whatever command is for doing this, because it's clearly there and it clearly works, and there's no bug. Thanks for the pointer! billo -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/cee94946-05d7-417d-a356-ade41681735c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes 3.2 installation will not boot on Dell Inspiron 7000 Gaming series laptop
On Tue, January 30, 2018 5:14 am, freddycribb...@gmail.com wrote: > I have installed Qubes OS 3.2 to a secondary SSD in an attempt at > The UEFI entry is successfully created by the installer, but upon Dual booting Qubes isn't really recommended. Better to have a separate physical machine if possible. I'm guessing, but I think the problem might be because there is usually only one EFI partition per system, and it's the one on your primary SSD. The UEFI programmers probably only ever tested a single drive with Win10, maybe booting once from an external drive. You could switch both Oses to grub2/legacy boot and try that way. Another option might be to do a full backup of your Windows SSD and leave it enabled during the Qubes install. Select the EFI partition on your primary drive when installing Qubes. Make sure to do the full backup because it could break things. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/121b883c8955ec44a4b1662d7db7e5cb.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Do Qubes v4.0-RC3 have stronger hardware limitations?
On Tue, January 30, 2018 1:23 pm, pascal.mignot.u...@gmail.com wrote: > I've tried to install Qubes v4.0-RC3 on an HP ProBook 650 laptop. > > > The installation interface prevent me to proceed, saying that my hardware > is not compatible with Qubes v4.0. > So my question is: what additional hardware constraints have been added > between Qubes 3.2 and 4.0 to disqualify my laptop? In dom0, run "qubes-hcl-report" and provide the 5 HVM: through Remapping: lines towards the end. If you see a message about "unknown", reboot and run it again. I think 4.0 requires the first 3 lines. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/d1e726773eecff9b7330defef2779ad7.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Do Qubes v4.0-RC3 have stronger hardware limitations?
I've tried to install Qubes v4.0-RC3 on an HP ProBook 650 laptop. The installation interface prevent me to proceed, saying that my hardware is not compatible with Qubes v4.0. But the processor is a i5-4310m and according to Intel, and it supports both vtx and vtd (see https://ark.intel.com/fr/products/80373/Intel-Core-i5-4310M-Processor-3M-Cache-up-to-3_40-GHz). In despair, I tried to install Qubes v3.2, and the installation went fine (just the wifi hardware to remove in bios and manually post-install). So my question is: what additional hardware constraints have been added between Qubes 3.2 and 4.0 to disqualify my laptop? Regards. Pascal -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/0c03453a-cab0-4043-bae2-dc9842dd8498%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Qubes update to fedora 26 but dnf still using fedora 23 repo
Hi, I've upgrading my Fedora 23 template to 26 after Qubes R3.2 installation (using the instructions in the Qubes documentation). As the title said, when I use dnf, I see: [user@fedora-26 ~]$ sudo dnf upgrade Fedora 23 - x86_64 490 kB/s | 43 MB 01:29 Qubes OS Repository for VM (updates)380 kB/s | 541 kB 00:01 Fedora 23 - x86_64 - Updates628 kB/s | 25 MB 00:41 Question: the repo should not be "Fedora 26"? If yes, 1/ is it safe to change to a "Fedora 26" repository? 2/ how to do it? Thank you, Regards. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/c28de7ae-a00e-4c90-b04a-e535fae7db8a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] HELLO
HELLO > > We have gone through your website and our company is interested in your > products. > > We want to make a large order for long term import. > > Please provide us with the following information. > > Please contact us with this EMAIL:[ paulwillson...@gmail.com ] > > 1. Handling Time > > 2. Minimum Order Quantity (MOQ) > > Thank You ! > > Best Regard -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/779170817.3582277.1517316933958%40mail.yahoo.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] after update no VM 'starts' apps anymore.
On Tuesday, 30 January 2018 11:19:18 CET 'Tom Zander' via qubes-users wrote: > There were a bunch more updates in the repo 4.0 current-testing this > morning which I applied and I rebooted, but no change. > Still no icons in my systray, still not able to start any apps on any VMs. Oh, I focused into the issue. I logged into xfce for 2 seconds and the Qubes app showed up. Then logging out and logging back into KDE and stuff still works. If you don't log into xfce you get the attached error from qubes-manager. Maybe someone made a mistake and used an xfce specific thing? I'm a bit worried that the system can become so broken. That thing that logging into xfce started should likely be auto-triggered and happen, not on login, but on need. Still really looking forward to Qubes getting more stable... -- Tom Zander Blog: https://zander.github.io Vlog: https://vimeo.com/channels/tomscryptochannel -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/1826574.hMNDsBkHFt%40mail. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: my mouse is dead
May God bless it!!! :( -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/f34e9a5a-15fb-46f2-b0e2-b689649c35d5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] after update no VM 'starts' apps anymore.
On Tuesday, 30 January 2018 01:05:39 CET 'Tom Zander' via qubes-users wrote: > I can start a VM using qvm-start, but when I use qvm-run nothing happens, > it hangs forever. Even commands that don't need a X server. > For any qube of the various OSs I run. > > The Qubes icons also no longer show in my system-tray. > I can still update dom0 via yum, though. Thats a relief. > Is this a known issue? Can I expect a fix soon? There were a bunch more updates in the repo 4.0 current-testing this morning which I applied and I rebooted, but no change. Still no icons in my systray, still not able to start any apps on any VMs. does anyone know if its possible to tell qubes-dom0-update to go back to the stable version (4.0 current instead of testing)? I tried switching one of my VMs back to the previous kernel. No change. guid log states; ``` Icon size: 128x128 libvchan_is_eof Icon size: 128x128 domain dead Failed to connect to gui-agent ``` pacat logs look ok, but nothing shows up in my dom0 mixer app vchan log has repeated series of; ``` vchan closed reconnecting vchan closed ``` qrexec (after a while) has this log ``` Unable to connect to X server Unable to connect to X server eintr ``` I'll switch to my old ArchLinux OS, until Qubes gets more stable. -- Tom Zander Blog: https://zander.github.io Vlog: https://vimeo.com/channels/tomscryptochannel -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/3072269.2ckbBL5Sd1%40cherry. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] after update no VM 'starts' apps anymore.
On Tuesday, 30 January 2018 02:51:06 CET 'awokd' via qubes-users wrote: > Enable Debug mode? I always wondered what this was, anyone know what effect it has to set this to true? -- Tom Zander Blog: https://zander.github.io Vlog: https://vimeo.com/channels/tomscryptochannel -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/4033376.ZqIuirrLiM%40cherry. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Qubes 4.0-rc3 not installing on Lenovo P71
On Monday, January 29, 2018 at 10:11:12 AM UTC+8, Qubed One wrote: > Yuraeitha: > > On Sunday, January 28, 2018 at 3:13:47 AM UTC+1, joeh...@gmail.com > > wrote: > >> I burned the ISO to USB stick then started to install Qubes but got > >> the following: > >> > >> [0.093375] ACPI Error: [\SB_.PCIO.XHC_.RHUB.HS11] Namespace > >> lookup failure, AE_NOT_FOUND (20170531/dswload-210) [0.093383] > >> ACPI Exception: AE_NOT_FOUND, During name lookup/catalog > >> (20170531/psobject-252) [0.093539] ACPI Exception: > >> AE_NOT_FOUND, (SSDT:ProjSsdt) while loading table > >> (20170531/tbxfload-220) [0.098243] ACPI Error: 1 table load > >> failures, 12 successful (20170531/tbxfload-246) [2.376031] > >> Couldn't get size: 0x800e [ 137.216201] > >> dracut-initqueue[566]: Warning: Dracut-initqueue timeout - starting > >> timeout scripts [ 137.779207] dracut-initqueue[566]: Warning: > >> Dracut-initqueue timeout - starting timeout scripts [ 138.324711] > >> dracut-initqueue[566]: Warning: Dracut-initqueue timeout - starting > >> timeout scripts [ 138.852226] dracut-initqueue[566]: Warning: > >> Dracut-initqueue timeout - starting timeout scripts [ 139.395971] > >> dracut-initqueue[566]: Warning: Dracut-initqueue timeout - starting > >> timeout scripts . . . > >> > >> This went on for some time, so I switched off and wrote this > >> message. I hope there are no serious typos coz I typed this off of > >> a picture taken of the screen. > >> > >> Any hints? Thanks > > > > I'm by no means an expert on the kernel, but dracut "looks" like > > kernel errors, and "ACPI" (Advanced Configuration and Power > > Interface) looks like a firmware/kernel support mismatch, either by a > > lack of features, lack of development, firmware-bug, kernel-bug, or > > possibly an un-updated firmware. The firmware should be the > > motherboard (BIOS/UEFI). > > > > You could start looking in your BIOS/UEFI after settings that may be > > wrong and require adjustments. Is VT-d enabled? Is there a second > > "Virtualization" that needs enabling, for exaple under "Advanced --> > > CPU" UEFI settings? There can be other settings too, it's hard to > > mention them all, but those two are the most important ones, which is > > sometimes only 1 merged setting. > > > > Does your hardware support VT-d and other Qubes hardware > > requirements? Does Qubes 3.2. run on this hardware? Qubes 4 is known > > to be more strict to hardware requirements and may not work smoothly > > or may not even install if the hardware requirements or security is > > not correct. Qubes 3.2. is less an issue when missing VT-d and > > similar. This might also be a place to look and confirm. If you got > > Qubes 3.2. running on the machine, then try run in dom0 > > "qubes-hcl-report" to see if you meet the requirements. > > > > However, dracut/ACPI errors doesn't strike me as errors that appear > > if there are issues with the Qubes 4 specific requirements. > > > > You may want to try install with LegacyBIOS/Grub if you tried > > UEFI/EFI, or vice versa, whichever you did not try yet. You can also > > update your BIOS/UEFI to the newest version, however be sure you > > don't brick your machine. Make sure you know any pitfalls as it may > > make your motherboard break and become useless. > > > > The kernel contains drivers too, the most essential ones, while the > > modules contain extra drivers for the kernel. These errors could also > > be driver issues, for example you may have to edit the EFI or the > > Grub to pick a different driver before starting. Unfortunately I > > believe you need to edit the /boot/efi/EFI.cfg file on the install > > media, but you can more easily change it live on Grub by hovering > > over the install menu, and thne press "E" key to edit the install > > menu in grub. Here you can change ACPI settings, drivers, > > virtulization states, hide/unhide hardware, and so on. > > > Maybe try this: hit e at this point as directed, then add: > acpi=off > to the end of the long line that begins with: > module /vmlinuz-4... > > then boot in to the installer from there. > > > > I'm not sure if it even is a driver issue, I can't see that from the > > logs, whether it can be found there or not. But it's some clues to go > > with, and maybe you can google some up to trial and error. Just be > > careful, for example few of the ACPI settings can be dangerous to > > your hardwaree, so double-check any recommendations you find on the > > internet. > > > > Also it may be worth if you can find any ACPI settings in your > > UEFI/BIOS too. > > > > At any rate, I usually solve these kind of problems with trial and > > errors through experiments. Someone more knowledgeable might drop by > > with a better advice. For now though, some clues you can try start > > with if you did not do them already. > > Ok, I found this web page: https://www.qubes-os.org/doc/thinkpad-troubleshooting/ and got qubes working. However, WiFi and the mouse
[qubes-users] Re: Lenovo ThinkPad, won't boot
On Tuesday, January 30, 2018 at 7:24:23 AM UTC+8, Tim W wrote: > Here is a thread with steps to get uefi install of 3.2 working on the p51 > from a few weeks ago > > https://groups.google.com/forum/m/#!topic/qubes-users/4VsKdxnKHBk > > Cbeers, > > Tim Here is a page from the qubes documentation: https://www.qubes-os.org/doc/thinkpad-troubleshooting/ -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/9fb34b05-8135-47e4-af37-2c33e7883b51%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] after update no VM 'starts' apps anymore.
sudo xl console -t serial Work -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/45dfccdf-1f00-4b08-92bf-fc5950bd6298%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes / Github bugs track ??
Le mardi 30 janvier 2018 10:05:57 UTC+2, Ivan Mitev a écrit : > On 01/30/18 09:36, ThierryIT wrote: > > Hi, > > > > Why are you closing a ticket before knowing if the modification you have Thx for your explanations, very nice job :) So if I did understood well, I have to re-open a new ticket for the same problem .. Because it is not resolved. made, to correct the bug, is working ? I mean, why can't you wait for the user to add the modification and see if it is working or not ? > > Once a dev or contributor provides a fix that he/she thinks solves an > issue there is usually no reason to keep the issue open, or else the > issue tracker would be cluttered with fixed but open issues waiting to > be confirmed/closed by their reporter. > > > As exemple: ticket #3501 is closed, but even if I have followed the > > instruction, the problem is not solved, but the ticket is closed ... > Either you're now hitting a bug that has nothing to do with your > original issue or Marek thought he fixed the bug but made a mistake. If > it's the former simply open another issue. If it's the latter, I'd send > Marek a friendly email, or I would create a new issue pointing to the > wrongly solved older one. > > > How to re-open it ? > > You can't, it looks like it's a github shortcoming. Had you taken 2 secs > to websearch it, you'd have found: > > https://stackoverflow.com/questions/21333654/how-to-re-open-an-issue-in-github#21333938 > > first hit, no need to even click the link, the answer is at the top of > the search page: "you cannot re-open your own issues if a repo > collaborator closed them". -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/b7c78e18-2705-4d0d-ba0f-8329a358e042%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes / Github bugs track ??
On 01/30/18 09:36, ThierryIT wrote: Hi, Why are you closing a ticket before knowing if the modification you have made, to correct the bug, is working ? I mean, why can't you wait for the user to add the modification and see if it is working or not ? Once a dev or contributor provides a fix that he/she thinks solves an issue there is usually no reason to keep the issue open, or else the issue tracker would be cluttered with fixed but open issues waiting to be confirmed/closed by their reporter. As exemple: ticket #3501 is closed, but even if I have followed the instruction, the problem is not solved, but the ticket is closed ... Either you're now hitting a bug that has nothing to do with your original issue or Marek thought he fixed the bug but made a mistake. If it's the former simply open another issue. If it's the latter, I'd send Marek a friendly email, or I would create a new issue pointing to the wrongly solved older one. How to re-open it ? You can't, it looks like it's a github shortcoming. Had you taken 2 secs to websearch it, you'd have found: https://stackoverflow.com/questions/21333654/how-to-re-open-an-issue-in-github#21333938 first hit, no need to even click the link, the answer is at the top of the search page: "you cannot re-open your own issues if a repo collaborator closed them". -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/0a307dad-53a9-2728-8592-762f2b18fbaa%40maa.bz. For more options, visit https://groups.google.com/d/optout.
