Hi,
In preparation for the upcoming release of X2Go Client 4.0.1.2, a new nightly build of the Windows binary is available for download under:
http://code.x2go.org/releases/binary-win32/x2goclient/previews/4.0.1.2/
Right now the current plan for 4.0.1.2's release is "We've stopped making changes. If no showstopper bugs or regressions are reported, we'll release 4.0.1.2 on Friday." So while we want all bugs reported on http://bugs.x2go.org/ , it is especially important that users report any regressions since the last stable version of X2Go Client for windows, 4.0.0.3, before Friday 2013-12-13.
There have been several commits since pre02 was built. However, the changes are so small that we do not intend to release another preview build before 4.0.1.2 is officially released. Half of the commits are related to Fedora & EPEL packaging anyway.
More information about this build:
It is still compatible with Windows XP! It bundles VcXsrv 1.14.2.1 (2013-07-26) because all later versions of VcXsrv (starting with 1.14.3, released 2013-09-20) are incompatible with Windows XP.
The X2Go Project will evaluate options for upgrading VcXsrv after X2Go Client 4.0.1.2 is released. The general consensus is that X2Go Client should continue to support Windows XP until at least when Microsoft stops supporting XP in April 2014. Like before, users can configure X2Go Client to use a different X server by specifying the X Server in Options -> Settings -> X-Server settings.
It is built from commit 31b6e2a55ac9328c96ae4f61f18a1a3f4dbf9b6b (2013-12-10 UTC)
The version of nx-libs is 3.5.0.21-lite
It is built according to the instructions here: http://wiki.x2go.org/doku.php/wiki:development:build-howto-mswin:x2goclient
Bug #230 "x2goclient on Windows does not show up in Control Panel/Programs" has been fixed.
All other existing windows-specific bugs are probably still present.
For a high-level changelog of what has been fixed/improved in 4.0.1.2 as of this build, see: http://code.x2go.org/gitweb?p=x2goclient.git;a=blob;f=debian/changelog;h=190...
-Mike DePaulo X2Go Contributor
Am 11.12.2013 01:43, schrieb Michael DePaulo:
In preparation for the upcoming release of X2Go Client 4.0.1.2, a new nightly build of the Windows binary is available for download under:
http://code.x2go.org/releases/binary-win32/x2goclient/previews/4.0.1.2/
Right now the current plan for 4.0.1.2's release is "We've stopped making changes. If no showstopper bugs or regressions are reported, we'll release 4.0.1.2 on Friday." So while we want all bugs reported on http://bugs.x2go.org/ , it is especially important that users report any regressions since the last stable version of X2Go Client for windows, 4.0.0.3, before Friday 2013-12-13.
I just tried out x2goclient-4.0.1.2-pre02 and I'm a little disappointed.
There's no improvement on the sound issue (Flash videos sound "choppy"), yet there's no additional download option where one could download a copy of x2goclient-4.0.1.2-pre02-setup that is set to use the old pulseaudio. :-( Showstopper for me, can't roll that out to my customers.
Even with the newer Xserver that is included in x2goclient-4.0.1.2-pre02-setup, Chromium and Chrome still crash at random intervals. To be exact, they're not crashing themselves, they're crashing the X server. Pausing and resuming a session lets you continue where you stopped, yet, this is an instability that users won't put up with since they quit Windows 98/Millennium for good. It's only when X2Go is involved that these crashes occur - if you export the display with ssh (from PuTTY) instead of using x2goclient.exe, Chromium and Chrome behave well. Not a showstopper (customers are using Iceweasel so far), but something where I had hoped to see some improvement with the new Xserver. :-(
The two items above are connected in a way: Flash sound isn't "choppy" in Chromium/Chrome, so if we'd get Chromium/Chrome to work, I could try to migrate my users away from Iceweasel to avoid the sound issue. On the other hand, if you are able to fix the sound issue, I don't see a need to migrate to Chromium/Chrome.
New Eye Candy #1: The taskbar icon suddenly changes into the seal icon once the connection is established. Please add a checkbox/config file entry to disable this. I'm sure it will confuse users who have previously used published application mode and look for the "Accelerated X" icon that has just vanished. I'm kind of disappointed that we're adding silly eye candy when there still are serious bugs to fix.
New Eye Candy #2: Upon connection, an info bubble pops up, containing a *totally cryptic session name* and disappearing after five seconds or so. No non-technical user can make use of that message, seriously. And even technical users will have a hard time memorizing a cryptic session name within 5 seconds. Please, also add an option to disable this popup, and seriously consider changing the displayed info to something more userfriendly like "Connection to host <host>, session <sessionname> established as user <user>." It's okay to add the cryptic string somewhere where techies can find it if they need it, maybe in an About-Box or so, but please - think of the chil^W ordinary non-technical end user. And again, I'm kind of disappointed that we're adding silly eye candy when there still are serious bugs to fix.
@Mike&Mike (or is that Mike²?): I'm guessing this should go into the bugtracker, somehow. Please advise on how it should be tagged and I'll turn items 1, 2, 4, and 5 into four new bugtracker entries.
-Stefan
Hi Stefan,
On Mi 11 Dez 2013 14:50:02 CET, Stefan Baur wrote:
Am 11.12.2013 01:43, schrieb Michael DePaulo:
In preparation for the upcoming release of X2Go Client 4.0.1.2, a new nightly build of the Windows binary is available for download under:
http://code.x2go.org/releases/binary-win32/x2goclient/previews/4.0.1.2/
Right now the current plan for 4.0.1.2's release is "We've stopped making changes. If no showstopper bugs or regressions are reported, we'll release 4.0.1.2 on Friday." So while we want all bugs reported on http://bugs.x2go.org/ , it is especially important that users report any regressions since the last stable version of X2Go Client for windows, 4.0.0.3, before Friday 2013-12-13.
I just tried out x2goclient-4.0.1.2-pre02 and I'm a little disappointed.
There's no improvement on the sound issue (Flash videos sound
"choppy"), yet there's no additional download option where one could
download a copy of x2goclient-4.0.1.2-pre02-setup that is set to use
the old pulseaudio. :-( Showstopper for me, can't roll that out to
my customers.Even with the newer Xserver that is included in
x2goclient-4.0.1.2-pre02-setup, Chromium and Chrome still crash at
random intervals. To be exact, they're not crashing themselves,
they're crashing the X server. Pausing and resuming a session lets
you continue where you stopped, yet, this is an instability that
users won't put up with since they quit Windows 98/Millennium for
good. It's only when X2Go is involved that these crashes occur - if
you export the display with ssh (from PuTTY) instead of using
x2goclient.exe, Chromium and Chrome behave well. Not a showstopper
(customers are using Iceweasel so far), but something where I had
hoped to see some improvement with the new Xserver. :-(The two items above are connected in a way: Flash sound isn't
"choppy" in Chromium/Chrome, so if we'd get Chromium/Chrome to work,
I could try to migrate my users away from Iceweasel to avoid the
sound issue. On the other hand, if you are able to fix the sound
issue, I don't see a need to migrate to Chromium/Chrome.New Eye Candy #1: The taskbar icon suddenly changes into the seal
icon once the connection is established. Please add a
checkbox/config file entry to disable this. I'm sure it will confuse
users who have previously used published application mode and look
for the "Accelerated X" icon that has just vanished. I'm kind of
disappointed that we're adding silly eye candy when there still are
serious bugs to fix.New Eye Candy #2: Upon connection, an info bubble pops up,
containing a *totally cryptic session name* and disappearing after
five seconds or so. No non-technical user can make use of that
message, seriously. And even technical users will have a hard time
memorizing a cryptic session name within 5 seconds. Please, also add
an option to disable this popup, and seriously consider changing the
displayed info to something more userfriendly like "Connection to
host <host>, session <sessionname> established as user <user>." It's
okay to add the cryptic string somewhere where techies can find it
if they need it, maybe in an About-Box or so, but please - think of
the chil^W ordinary non-technical end user. And again, I'm kind of disappointed that we're adding silly eye
candy when there still are serious bugs to fix.@Mike&Mike (or is that Mike²?): I'm guessing this should go into the bugtracker, somehow. Please
advise on how it should be tagged and I'll turn items 1, 2, 4, and 5
into four new bugtracker entries.-Stefan
Thanks for testing all that.
Please send individual mails to submit@bugs.x2go.org
User a proper subject line.
Put
""" Package: x2goclient Severity: wishlist Version: 4.0.1.2
"""
into that first lines of each mail and add the text passage of the
corresponding item below.
Mike
DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148
GnuPG Key ID 0x25771B31 mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
On Wed, Dec 11, 2013 at 9:29 AM, Stefan Baur <newsgroups.mail2@stefanbaur.de> wrote:
Am 11.12.2013 15:20, schrieb Mike Gabriel:
[my test results]
Please send individual mails to submit@bugs.x2go.org
Done, as promised. :-)
-Stefan
Hi Stefan,
I would like to say that "I feel your pain." I agree with you that not only are 1, 2 and 3 legitimate bugs/issues with X2Go Client, but so are 4 and 5.
However, as the new maintainer of the X2Go Client package for Windows, I do not believe that any of these bugs and issues are worth delaying the 4.0.1.2 release to fix. Maybe if 1,2 and 3 were regressions against 4.0.0.3, I would reconsider. However, they are existing bugs.
Fortunately, the x2go bug tracker exists not just to documents bugs and how they will be fixed in future versions, but also to document workarounds for current versions. I will try to identify workarounds for you and I will post them on the bugtracker. I encourage you to do this also.
Also, note that I fixed bug #230 specifically because it was easy for me to fix and because the risk of a regression is very low. All I had to edit was the NSIS script. I will need to brush up on C++ before I can fix most x2goclient bugs.
-Mike DePaulo X2Go Contributor
Am 11.12.2013 17:31, schrieb Michael DePaulo:
However, as the new maintainer of the X2Go Client package for Windows, I do not believe that any of these bugs and issues are worth delaying the 4.0.1.2 release to fix. Maybe if 1,2 and 3 were regressions against 4.0.0.3, I would reconsider. However, they are existing bugs.
4 and 5 are new, though, unless I was blind and not paying attention when trying out the last few x2goclient.exes.
[...]
Also, note that I fixed bug #230 specifically because it was easy for me to fix and because the risk of a regression is very low. All I had to edit was the NSIS script. I will need to brush up on C++ before I can fix most x2goclient bugs.
Ah, the missing uninstaller. That part I didn't even try - I'm using X2Goclient in portable mode.
-Stefan
On Wed, Dec 11, 2013 at 11:37 AM, Stefan Baur <newsgroups.mail2@stefanbaur.de> wrote:
Ah, the missing uninstaller. That part I didn't even try - I'm using X2Goclient in portable mode.
Actually, I just realized that #1 (flash sound is choppy) is actually a regression against x2goclient 4.0.0.3 because there are x2goclient 4.0.0.3 packages with the old pulseaudio. And yes, I have observed this bug myself.
I will look into providing a build of x2goclient 4.0.1.2pre02 with the old pulseaudio. I am hoping it will not require any changes to the source code for x2goclient. Note that providing such a build was not listed in these instructions I followed: http://wiki.x2go.org/doku.php/wiki:development:build-howto-mswin:x2goclient
-Mike
Am 11.12.2013 17:47, schrieb Michael DePaulo:
I will look into providing a build of x2goclient 4.0.1.2pre02 with the old pulseaudio. I am hoping it will not require any changes to the source code for x2goclient. Note that providing such a build was not listed in these instructions I followed: http://wiki.x2go.org/doku.php/wiki:development:build-howto-mswin:x2goclient
That's probably because the documentation was either written before the "fork/workaround" was developed, or because whoever wrote the instructions didn't expect the problem to last. ;-)
-Stefan
Stefan,
I posted this workaround reply to the bug tracker, but it does not seem to be showing up. So here is the exact text I posted:
Please test and follow this workaround with x2goclient-4.0.1.2pre02 (for windows) until a 4.0.1.2pre02 package with the old pulseaudio is made (most likely in several hours):
- Install x2goclient 4.0.1.2pre02 if you haven't already. It will by default be installed to "C:\Program Files\x2goclient\" on 32-bit, and "C:\Program Files (x86)\x2goclient\" on 64-bit.
- Rename the installation location's "pulse" subfolder to "pulse-1.1"
- Download http://code.x2go.org/releases/binary-win32/x2goclient/with-old-pulseaudio-0.... but do not install it.
- Open that .exe file in 7-zip or peazip as an archive and extract the $_OUTDIR\pulse\ folder from it. Do not extract it directly to the installation location's folder. Instead, extract it to someplace where you have write permissions, such as your "My Documents" so that windows UAC file virtualization does not interfere. (There's other ways to get this "pulse" folder too. E.g, installing it on a spare machine and copying the folder. Temporarily uninstalling x2goclient 4.0.1.2pre02 and installing 4.0.0.3.interims, etc.)
- Copy the "pulse" folder to the x2go installation folder.
I quickly tested this workaround on an x2goserver VM running ubuntu 12.04.x 32-bit (with the latest updates and the quantal HWE) and it did fix this bug for me. (This bug was present when I did not perform the workaround.) My client system is windows 8.1 64-bit.
On Wed, Dec 11, 2013 at 11:51 AM, Stefan Baur <newsgroups.mail2@stefanbaur.de> wrote:
Am 11.12.2013 17:47, schrieb Michael DePaulo:
I will look into providing a build of x2goclient 4.0.1.2pre02 with the old pulseaudio. I am hoping it will not require any changes to the source code for x2goclient. Note that providing such a build was not listed in these instructions I followed:
http://wiki.x2go.org/doku.php/wiki:development:build-howto-mswin:x2goclient
That's probably because the documentation was either written before the "fork/workaround" was developed, or because whoever wrote the instructions didn't expect the problem to last. ;-)
-Stefan
Am 11.12.2013 18:18, schrieb Michael DePaulo:
I posted this workaround reply to the bug tracker, but it does not seem to be showing up. So here is the exact text I posted:
Weird. But thanks for the forward ...
Please test and follow this workaround with x2goclient-4.0.1.2pre02 (for windows) until a 4.0.1.2pre02 package with the old pulseaudio is made (most likely in several hours): ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
... though waiting a few hours, especially when most of these hours are nighttime in my time zone, sounds like the easier approach. ;-)
I can't promise I'll get around to test a new version tomorrow, anyways, and it's not like the old ones currently in use by my customers are going to expire and cease working any time soon. ;-)
By the way, since you're new to the project, maybe you can bring some fresh ideas to the table - the whole sound issue has been stuck for quite a while. Not onl is pulseaudio creating choppy sound when playing Flash videos, it's also less than ideal for transmitting sound over low-bandwidth WAN links (I'm not a coder, but I believe I remember one of the coders involved mentioning that pulseaudio always pushes the original bit and sample rate "down the pipe" and doesn't adapt to the available bandwith like the graphics part of X2Go does, where you can change bit depth, compression, etc.). So if you have an idea on what we could replace pulseaudio with, shoot! :-) Just remember, we need client software for Linux, Windows and Mac OS. My main concern would be playback, but you shouldn't forget that there's also the faint chance that somebody wants to use the microphone on the client and forward its sound to an application on the server.
-Stefan
I sent an email to 263@bugs.x2go.org several days ago, trying to add information to bug #263. But when I browse the information for #263, my email does not show up.
What did I do wrong?
On Wed, Dec 11, 2013 at 3:44 PM, John Williams <jwilliams4200@gmail.com> wrote:
I sent an email to 263@bugs.x2go.org several days ago, trying to add information to bug #263. But when I browse the information for #263, my email does not show up.
What did I do wrong?
It seems like there's a delay of about 5 minutes before your reply shows up.
I do see your reply right now. It's details are: From: John Williams <jwilliams4200@gmail.com> To: 263@bugs.x2go.org Subject: Windows x2go-client versions after 3.99.2 frequently hang while trying to resume sessions Date: Sun, 8 Dec 2013 23:40:37 -0800
On Wed, Dec 11, 2013 at 2:18 PM, Michael DePaulo <mikedep333@gmail.com> wrote:
On Wed, Dec 11, 2013 at 3:44 PM, John Williams <jwilliams4200@gmail.com> wrote:
I sent an email to 263@bugs.x2go.org several days ago, trying to add information to bug #263. But when I browse the information for #263, my email does not show up.
What did I do wrong?
It seems like there's a delay of about 5 minutes before your reply shows up.
I'm talking about the 3 day delay between when I emailed to 263@bugs.x2go.org and now. My email still has not shown up on the bug report web page:
http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=263
Or am I wrong in assuming my email is supposed to be appended to that page?
Hi John,
On Do 12 Dez 2013 01:06:06 CET, John Williams wrote:
On Wed, Dec 11, 2013 at 2:18 PM, Michael DePaulo
<mikedep333@gmail.com> wrote:On Wed, Dec 11, 2013 at 3:44 PM, John Williams
<jwilliams4200@gmail.com> wrote:I sent an email to 263@bugs.x2go.org several days ago, trying to add information to bug #263. But when I browse the information for #263, my email does not show up.
What did I do wrong?
It seems like there's a delay of about 5 minutes before your reply shows up.
I'm talking about the 3 day delay between when I emailed to 263@bugs.x2go.org and now. My email still has not shown up on the bug report web page:
http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=263
Or am I wrong in assuming my email is supposed to be appended to that page?
Yes, it should get appended. The CRON job for processing incoming
mails runs every 5-15minutes (or so). Three days sounds peculiar. Will
check.
Mike
--
DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148
GnuPG Key ID 0x25771B31 mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
On Thu, Dec 12, 2013 at 1:50 PM, Mike Gabriel <mike.gabriel@das-netzwerkteam.de> wrote:
Hi John,
On Do 12 Dez 2013 01:06:06 CET, John Williams wrote:
On Wed, Dec 11, 2013 at 2:18 PM, Michael DePaulo <mikedep333@gmail.com> wrote:
On Wed, Dec 11, 2013 at 3:44 PM, John Williams <jwilliams4200@gmail.com> wrote:
I sent an email to 263@bugs.x2go.org several days ago, trying to add information to bug #263. But when I browse the information for #263, my email does not show up.
What did I do wrong?
It seems like there's a delay of about 5 minutes before your reply shows up.
I'm talking about the 3 day delay between when I emailed to 263@bugs.x2go.org and now. My email still has not shown up on the bug report web page:
http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=263
Or am I wrong in assuming my email is supposed to be appended to that page?
Yes, it should get appended. The CRON job for processing incoming mails runs every 5-15minutes (or so). Three days sounds peculiar. Will check.
I downloaded the mbox file associated with bug 263, and my email is there.
But it does not show up on the bug webpage:
http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=263
Perhaps that is the way it is supposed to work? If so, it is inconvenient, because I would have to download the mbox file for any bug that I wanted to look at all the comments for. It would be better if everything were visible on the web page.
Am 12.12.2013 23:12, schrieb John Williams:
On Thu, Dec 12, 2013 at 1:50 PM, Mike Gabriel
I'm talking about the 3 day delay between when I emailed to 263@bugs.x2go.org and now. My email still has not shown up on the bug report web page:
Are you talking about this one?
From: John Williams <jwilliams4200@gmail.com> To: 263@bugs.x2go.org Subject: Windows x2go-client versions after 3.99.2 frequently hang while trying to resume sessions Date: Sun, 8 Dec 2013 23:40:37 -0800
Because I can see it on the web page (and already could back when you first complained about it being invisible).
If that is the one you are talking about, my guess is that you have a caching proxy somewhere between you and the bugs.x2go.org server, or your browser's cache/refresh settings are b0rked.
Check the modification date of the web page for comparison, here, I'm seeing "Montag, 9. Dezember 2013 08:48:01" when I right-click and select "page information" (or whatever that option might be called in English) in Firefox.
-Stefan
On Thu, Dec 12, 2013 at 2:18 PM, Stefan Baur <newsgroups.mail2@stefanbaur.de> wrote:
Am 12.12.2013 23:12, schrieb John Williams:
On Thu, Dec 12, 2013 at 1:50 PM, Mike Gabriel
I'm talking about the 3 day delay between when I emailed to
263@bugs.x2go.org and now. My email still has not shown up on the bug report web page:
Are you talking about this one?
From: John Williams <jwilliams4200@gmail.com> To: 263@bugs.x2go.org Subject: Windows x2go-client versions after 3.99.2 frequently hang while trying to resume sessions Date: Sun, 8 Dec 2013 23:40:37 -0800
Because I can see it on the web page (and already could back when you first complained about it being invisible).
If that is the one you are talking about, my guess is that you have a caching proxy somewhere between you and the bugs.x2go.org server, or your browser's cache/refresh settings are b0rked.
Yes, that is the one I am talking about. I do not see how I could possibly have a caching proxy in there, since I certainly did not configure anything like that.
And I tried hitting refresh several times and it did not make a difference.
Check the modification date of the web page for comparison, here, I'm seeing "Montag, 9. Dezember 2013 08:48:01" when I right-click and select "page information" (or whatever that option might be called in English) in Firefox.
Just a minute ago the web page stopped working for me. Maybe something Mike Gabriel did?
Now http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=263 shows me only this:
An error occurred. Error was: Bad bug log for Bug 263. Unable to read records: bad line 'X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on' in state incoming-recv at /usr/share/perl5/Debbugs/Log.pm line 262, line 6534.
Am 12.12.2013 23:23, schrieb John Williams:
Yes, that is the one I am talking about. I do not see how I could possibly have a caching proxy in there, since I certainly did not configure anything like that.
Well, I don't know where you are and who your provider is. If you're at a public library, a university, a company, chances are the IT department installed a caching proxy. Also, some providers add caching proxies, especially when you're using a mobile internet connection.
And I tried hitting refresh several times and it did not make a difference.
I've seen Firefox have "hiccups" like that before. Try: likely open a new tab or browser window)
- Shift-Reload (keep the shift button pressed down while clicking on the reload button - note that you need to click, Ctrl-R + Shift doesn't work any more)
- Ctrl-Reload (same as above, with Ctrl instead of Shift, will most
- Ctrl-Shift-Reload (as above, with both pressed down)
- Switching to "Porn Mode" a.k.a. Private Browsing (Shift-Ctrl-P) and loading the page there
- Creating a new, additional Firefox user profile
- Using a different browser
Check the modification date of the web page for comparison, here, I'm seeing "Montag, 9. Dezember 2013 08:48:01" when I right-click and select "page information" (or whatever that option might be called in English) in Firefox.
Just a minute ago the web page stopped working for me. Maybe something Mike Gabriel did?
Now http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=263 shows me only this:
An error occurred. Error was: Bad bug log for Bug 263. Unable to read records: bad line 'X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on' in state incoming-recv at /usr/share/perl5/Debbugs/Log.pm line 262, line 6534.
Yup, it's b0rked now. Mike was experimenting with it (See the TEST mail he sent) and something went wrong, as it seems.
-Stefan
On Thu, Dec 12, 2013 at 2:33 PM, Stefan Baur <newsgroups.mail2@stefanbaur.de> wrote:
Am 12.12.2013 23:23, schrieb John Williams:
Yes, that is the one I am talking about. I do not see how I could possibly have a caching proxy in there, since I certainly did not configure anything like that.
Well, I don't know where you are and who your provider is. If you're at a public library, a university, a company, chances are the IT department installed a caching proxy. Also, some providers add caching proxies, especially when you're using a mobile internet connection.
I am using a cable modem connection. As I said, I do not see how any caching proxy could be in there. I would certainly have noticed it on other web pages if the ISP was somehow screwing with my http packets.
I've seen Firefox have "hiccups" like that before. Try:
- Shift-Reload (keep the shift button pressed down while clicking on the reload button - note that you need to click, Ctrl-R + Shift doesn't work any more)
- Ctrl-Reload (same as above, with Ctrl instead of Shift, will most likely open a new tab or browser window)
- Ctrl-Shift-Reload (as above, with both pressed down)
- Switching to "Porn Mode" a.k.a. Private Browsing (Shift-Ctrl-P) and loading the page there
- Creating a new, additional Firefox user profile
- Using a different browser
I am actually using Google Chrome at the moment, but Internet Explorer and Firefox both show the same web page.
On Do 12 Dez 2013 23:33:18 CET, Stefan Baur wrote:
Am 12.12.2013 23:23, schrieb John Williams:
Yup, it's b0rked now. Mike was experimenting with it (See the TEST
mail he sent) and something went wrong, as it seems.
I have injected Johns mail manually and there were some weird signs in
the mail header. Not sure where they came from.
#263 has now been unb0rked again...
Mike
--
DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148
GnuPG Key ID 0x25771B31 mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
On Thu, Dec 12, 2013 at 2:51 PM, Mike Gabriel <mike.gabriel@das-netzwerkteam.de> wrote:
I have injected Johns mail manually and there were some weird signs in the mail header. Not sure where they came from.
#263 has now been unb0rked again...
Thanks. What were the "weird signs"? I just sent it via gmail, so I don't know what they could be.
By the way, can that bug be taken out of the "More information needed" category now? I think I provided all requested information, even if the original reporter did not respond. As you can see, several people have been suffering from this bug, and it has existed for quite a while now. In my opinion, it should be classified as "Serious bugs".
-
John Williams -
Michael DePaulo -
Mike Gabriel -
Stefan Baur