Set 1920x1080 fullscreen video mode X Error of failed request: GLXBadFBConfig
Major opcode of failed request: 154 (GLX)
Minor opcode of failed request: 34 ()
Serial number of failed request: 50
Current serial number in output stream: 49 AL lib: ReleaseALC: 1 device not closed
Any ideas?
This is because Nouveau doesn't do OpenGL 3.2. You will have the same error with the linux Intel drivers for Sandy Bridge and Ivy Bridge. Not a hardware thing, it's a driver support issue.
If I got an email like that from a vendor I was trying to reach, I wouldn't be doing service with that vendor.
One vendor that we were paying support to was trapping our entire domain's email in a spam filter - none of our emails could go through...
I see what you're saying. Just wanted to emphasize that email messages are never dropped in our system, they are always delivered. The SPF check is still part of the spam checks, but by the time we get to the "send informational message" stage we've already decided the message isn't spam. We also check the sending IP against the Backscatterer RBL, which hopefully keeps us from sending to domains that have been hijacked.
The informational message is only sent once per week to any given sender. We do have an "don't email me about this again" link in the email. Finally, we don't send the message to anyone sending from a rather large commercially-maintained list of known webmail address and ISP mail servers, which exempts a large portion of senders from ever seeing the message (these users can't do anything to fix a broken spf record).
The whole point of SPF is that if an email fails an SPF check, the email may not have come from the purported sender, and you should not treat it as genuine. You're completely undermining what SPF is for by doing this.
Yeah, if everyone did this it would be bad - zillions of polite informational messages. You make a good point.
On one hand we're a small shop with a low-traffic email server. We've had good success getting sending domains to fix their record. On the other hand, perhaps we should go back to passive mode. I'll mention it to the system administrators.
Our solution: if the message makes it past all our spam filters and the only problem is that the sender's client isn't allowed by their SPF record, we send a friendly, plain-english informational message back to the sender, then deliver their message to our users.
"Please tell your company's IT staff that your mail server isn't set up correctly. This may cause your messages to be rejected or classified as spam. Please forward the following information to your system administrator: [SPF record] [sender's IP]. Thank you!"
Usually the issue is that the sender has set up GMail to send "from" their company email without sending through the company SMTP servers, usually without authorization.
We do the same thing with broken DKIM signatures.
This has worked well for us, since senders get tired of the message and seem to get things dealt with. We considered adding a "threat" saying that if the problem wasn't fixed, we'd block the sender, but that was rightfully shot down as pretty mean.
Does it matter if we are legally prohibited from unlocking our phones to make any modifications to the software or firmware?
You are not legally prohibited from making modifications to software or firmware.
The recent law that prohibits unlocking refers only to the unlocking process that allows you to use any SIM card you want in your phone.
You are still free to jailbreak or root your devices, install the operating system of your choice, etc. None of that has anything to do with unlocking your phone.
Why is this news? Slashdot already covered F18's wacky installer.
F18 is a bleeding-edge testing distribution. People who use bleeding-edge testing distributions should expect the odd glitch. New things get tried in Fedora. Some of them are great; some of them are dubious. It's always been this way. This is surely not news.
We're using F18 here on all our desktop machines; there have been zero issues. The installer was a "WTF? Oh, got it." inconvenience the first time around.
Thanks for the kernels, AC, and you can say what you like, but people whose OS installs get screwed up tend to be louder than those for whom things just work. I wonder if he even bothered to report a bug. Probably not.
There are no "quick bursts" - it is MONITOR mode where transmitting does not work.
I know how monitor mode works. What's your point?
My point is, if you aren't actually connected to a wifi network, you would not notice that the phone has been put into monitor mode for brief periods of time. And if the phone immediately kills monitor mode when you turn on the screen and refrains from using it while you're using the device, it would not interfere with anything.
My only point is really that maybe Google can't say you were "with someone" because you were both at the same Starbucks a couple of nights a week for a month.
But if you start being in proximity with that someone in other places during the course of your day over several months, then all those previous proximity events are much more likely to have been "with that person".
You're absolutely right that Google or anyone else can't decide you are with someone just because your devices can see each other. But give them enough data points, and they will be right more often than they are wrong.
By the way, I've enjoyed reading your posts in this thread.
Not really. I go to the gym everyday at the same time, and I see the same people there everyday... That is a coincidence that we have similar schedules... I am not in a relationship with any of those people I see regularly.
...and that's easily guessed by the fact that there is a large group of people showing up at the same place on a fixed schedule. Pretty simple to write a "group activity" recognizer. And there's a gym at that address. Okay, fitness class. Now we can sort people for "fitness activity" by their attendance. Great, now we have list of people ranked by how serious they are about their personal fitness. Let's advertise supplements to the top 30%, personal training to the middle 30%, and fitness DVDs and McDonalds to the lower ranks.
And what the hell, let's suggest these people to each other on Google+. And advertise a great deal at the fitness club across town, because competition is good, right?
Voila, instant advertising targeting. And that's what Google and others are after.
Your position inside the gym means jack shit. It's all about using proximity data and location data over time to make really, really spookily accurate guesses about people.
While that is certainly a possibility, I doubt that it is currently happening because it requires putting the wifi nic into monitor mode in order to sniff for wifi packets from nodes that are not associated with the same access point or ad-hoc network.
No reason at all why this couldn't be done. It's a single command on most Linux systems with a wireless card.
The vast majority of wifi nics can not transmit when in monitor mode - thus making it useless for normal networking, which would tend to tip people off pretty quickly that something wasn't kosher.
So do it while the wifi connection is not in active use and the phone is idle in your pocket. Extra credit for enabling wifi without showing an activity indicator. No reason this couldn't be done, either. Quick bursts at idle when phone is not in active use.
If you have documented evidence of google using monitor mode on people's phones, bring it on. That is the kind of thing that needs to be widely publicized if it is happening.
I have no such evidence, but I'll be damned if I'm not going to investigate now. I'm guessing that the Google Location Services TOS that every Android phone presents at setup time might be an interesting re-read.
Not that it matters, but it doesn't work that way... (My full time job involved researching proximity algorithms)... Using Wifi as proximity, you can tell that say these 5 particular people are in a room, but you have zero idea the spatial relation of each of these 5 people to each other, without the aid of other sensors. Wifi or bluetooth will not give you spatial relationships in any meaningful manner.
The problem is that this is all happening over a long period of time, with a constant location fix. So you're right that a one-time scan of nearby devices is pretty much useless - but looking at who was near me every time I go to my favourite Starbucks over the course of a year will give you a pretty good idea of who is actually there with me.
Spatial relationships in a room less to Google than knowing who is part of my life, and who to suggest I might want to make part of my life.
Any smartphone can see all the MAC addresses of all phones and access points around it, bluetooth or WiFi (if enabled of course). With GPS positioning on most of those devices and a Giant Corporate Big Brother aggregating the results, all of us are reporting on our proximity to each other.
We all know that Google's wifi geolocation stuff works this way - by tracking which fixed wifi base stations are in range and correlating with a GPS fix. People forget that Google can also identify other phones within range of your phone, and they know which Google accounts are attached to those devices.
Google really does know who is sitting next to you on the train or in the coffee shop, who your jogging partner is, and which whore you visit when your wife leaves your general vicinity.
I bet they do some amazing automated profiling. This guy is a garbage man and works with these people, that guy likes to sit in coffee shops and this woman is usually also present, she's not his wife, so lets advertise couples vacations and cheater sites, this other woman visits a preschool every day and is probably a parent, let's suggest other parents from the same preschool as her Google+ friend...
Did a fresh F18 install on my laptop this past week.
I have to agree with a lot of the criticism of the new installer, and particularly the user interface for disk partitioning. I've been running Linux since the late 90s and I don't think I've ever been confused by a partition editor, from fdisk on up - until now.
I mean, the error message I got was "Not enough disk space to create a mountpoint". WHAT DOES THAT EVEN MEAN?!? And this while trying to get the thing to recognize my existing/home partition.
It's like someone who has never partitioned a disk before created a really bad abstract model of the process and then based the whole user interface off of their grand concept. In the process of trying to make things easy they made it hard for anyone who knows what they are doing to be specific about what should be done. A liberal sprinkling of incorrectly-used disk partitioning terms makes for a real perfect storm of confusion.
Once I got things installed, I had no problems at all. I hope to never feel that "oh shit, I hope I haven't just blown my/home away" thrill ever again though.
We have always had standardized checkstyle and jtidy rules as part of our build system. We have eclipse formatting configuration that everyone uses as well. Commits don't happen unless checkstyle is happy.
I thought everyone did this. I guess tooling is less developed in some languages, but it's not too hard to put this kind of thing into practice with a little bit of effort and buy-in.
After years and years of using a laptop as my main machine, a year ago I built myself a no-compromise workstation.
The logic was simple: I realized that when I was out and about with the laptop, I never did much heavy lifting. When I got on the Android bandwagon, the need to use a laptop as a browsing/ssh/mail device just went away.
Now, when I anticipate being a loser and writing code at Starbucks for a change of scene, I grab one of the cheap netbooks we have lying around, VNC into my desktop, and off I go. Bonus: if it gets stolen, there's nothing of value on it. Double bonus: disapproving glances from Apple users due to the anti-apple stickers on the lid.
We have a tablet for the coffee table, and it mostly gets used for recipes, Facebook, and controlling XBMC. That's it.
It's just horses for courses. No one wants a general purpose PC for round-the-house drudgery, people with smartphones don't need laptops to communicate.
It all seems to come down to two questions. "Do you need a keyboard?" and "Do you need actual CPU power?" For many folks, it seems the answer to both is mostly no.
Create a VM endpoint in the US on something like Amazon Web Services. Fire up a tunnel (vtund over ssh? openvpn? whatever) from your ship's router to your endpoint, route traffic through it, make sure your local DNS resolves through the tunnel, and call it a day. This way you won't need to tell people to mess around with VPN clients. The fewer moving parts, the better.
This is pretty simplistic though. You need to give us more details. How much bandwidth do you have to play with? What is the expected latency? How much tolerance is there for downtime? How much access control do you need? There are all kinds of additional steps that could make this kind of service more reliable.
I pay for my email now, because I want to be someone's customer, not someone's product
Fastmail is great. No ads, a decent Web UI when I want it, and a dedicated sysadmin team that does nothing but mail. All the Bayesian filtering, Sieve rules and DKIM signing you could want. Plus, I keep my conversations and business dealings out of Google's maw (although it's hard to avoid people who use GMail), and there's Yubikey authentication for when I'm on someone else's machine.
fastmail.fm (full disclosure: referral link included)
I have administered mail servers professionally before and have quite a bit of experience with it. If I'm not being paid to do it I'm sure as hell paying someone else to deal with the hassle.
Slashdot Mirror
Set 1920x1080 fullscreen video mode
X Error of failed request: GLXBadFBConfig
Major opcode of failed request: 154 (GLX)
Minor opcode of failed request: 34 ()
Serial number of failed request: 50
Current serial number in output stream: 49
AL lib: ReleaseALC: 1 device not closed
Any ideas?
This is because Nouveau doesn't do OpenGL 3.2. You will have the same error with the linux Intel drivers for Sandy Bridge and Ivy Bridge. Not a hardware thing, it's a driver support issue.
If I got an email like that from a vendor I was trying to reach, I wouldn't be doing service with that vendor.
One vendor that we were paying support to was trapping our entire domain's email in a spam filter - none of our emails could go through...
I see what you're saying. Just wanted to emphasize that email messages are never dropped in our system, they are always delivered. The SPF check is still part of the spam checks, but by the time we get to the "send informational message" stage we've already decided the message isn't spam. We also check the sending IP against the Backscatterer RBL, which hopefully keeps us from sending to domains that have been hijacked.
The informational message is only sent once per week to any given sender. We do have an "don't email me about this again" link in the email. Finally, we don't send the message to anyone sending from a rather large commercially-maintained list of known webmail address and ISP mail servers, which exempts a large portion of senders from ever seeing the message (these users can't do anything to fix a broken spf record).
The whole point of SPF is that if an email fails an SPF check, the email may not have come from the purported sender, and you should not treat it as genuine. You're completely undermining what SPF is for by doing this.
Yeah, if everyone did this it would be bad - zillions of polite informational messages. You make a good point.
On one hand we're a small shop with a low-traffic email server. We've had good success getting sending domains to fix their record. On the other hand, perhaps we should go back to passive mode. I'll mention it to the system administrators.
In other words you're generating soft bounces and making your server vulnerable to being used as an attack vector.
Nope, we do limits - one message per week per sender. So no effective attack vector.
We had the same problem.
Our solution: if the message makes it past all our spam filters and the only problem is that the sender's client isn't allowed by their SPF record, we send a friendly, plain-english informational message back to the sender, then deliver their message to our users.
"Please tell your company's IT staff that your mail server isn't set up correctly. This may cause your messages to be rejected or classified as spam. Please forward the following information to your system administrator: [SPF record] [sender's IP]. Thank you!"
Usually the issue is that the sender has set up GMail to send "from" their company email without sending through the company SMTP servers, usually without authorization.
We do the same thing with broken DKIM signatures.
This has worked well for us, since senders get tired of the message and seem to get things dealt with. We considered adding a "threat" saying that if the problem wasn't fixed, we'd block the sender, but that was rightfully shot down as pretty mean.
Does it matter if we are legally prohibited from unlocking our phones to make any modifications to the software or firmware?
You are not legally prohibited from making modifications to software or firmware.
The recent law that prohibits unlocking refers only to the unlocking process that allows you to use any SIM card you want in your phone.
You are still free to jailbreak or root your devices, install the operating system of your choice, etc. None of that has anything to do with unlocking your phone.
Why is this news? Slashdot already covered F18's wacky installer.
F18 is a bleeding-edge testing distribution. People who use bleeding-edge testing distributions should expect the odd glitch. New things get tried in Fedora. Some of them are great; some of them are dubious. It's always been this way. This is surely not news.
We're using F18 here on all our desktop machines; there have been zero issues. The installer was a "WTF? Oh, got it." inconvenience the first time around.
Thanks for the kernels, AC, and you can say what you like, but people whose OS installs get screwed up tend to be louder than those for whom things just work. I wonder if he even bothered to report a bug. Probably not.
AP Isolation makes it impossible for a mobile device to see the others. The AP simply won't report that information to you.
True... if your device is connected to a wifi network.
But a device that is NOT connected to a network and is functioning in monitor mode can see all devices broadcasting around it, including other phones.
Run kismet some time and just look at the craziness.
There are no "quick bursts" - it is MONITOR mode where transmitting does not work.
I know how monitor mode works. What's your point?
My point is, if you aren't actually connected to a wifi network, you would not notice that the phone has been put into monitor mode for brief periods of time. And if the phone immediately kills monitor mode when you turn on the screen and refrains from using it while you're using the device, it would not interfere with anything.
I see what you're saying.
My only point is really that maybe Google can't say you were "with someone" because you were both at the same Starbucks a couple of nights a week for a month.
But if you start being in proximity with that someone in other places during the course of your day over several months, then all those previous proximity events are much more likely to have been "with that person".
You're absolutely right that Google or anyone else can't decide you are with someone just because your devices can see each other. But give them enough data points, and they will be right more often than they are wrong.
By the way, I've enjoyed reading your posts in this thread.
Not really. I go to the gym everyday at the same time, and I see the same people there everyday... That is a coincidence that we have similar schedules... I am not in a relationship with any of those people I see regularly.
...and that's easily guessed by the fact that there is a large group of people showing up at the same place on a fixed schedule. Pretty simple to write a "group activity" recognizer. And there's a gym at that address. Okay, fitness class. Now we can sort people for "fitness activity" by their attendance. Great, now we have list of people ranked by how serious they are about their personal fitness. Let's advertise supplements to the top 30%, personal training to the middle 30%, and fitness DVDs and McDonalds to the lower ranks.
And what the hell, let's suggest these people to each other on Google+. And advertise a great deal at the fitness club across town, because competition is good, right?
Voila, instant advertising targeting. And that's what Google and others are after.
Your position inside the gym means jack shit. It's all about using proximity data and location data over time to make really, really spookily accurate guesses about people.
Why are you limiting this to Google?/quote>
I'm not. They're just an easy example.
While that is certainly a possibility, I doubt that it is currently happening because it requires putting the wifi nic into monitor mode in order to sniff for wifi packets from nodes that are not associated with the same access point or ad-hoc network.
No reason at all why this couldn't be done. It's a single command on most Linux systems with a wireless card.
The vast majority of wifi nics can not transmit when in monitor mode - thus making it useless for normal networking, which would tend to tip people off pretty quickly that something wasn't kosher.
So do it while the wifi connection is not in active use and the phone is idle in your pocket. Extra credit for enabling wifi without showing an activity indicator. No reason this couldn't be done, either. Quick bursts at idle when phone is not in active use.
If you have documented evidence of google using monitor mode on people's phones, bring it on. That is the kind of thing that needs to be widely publicized if it is happening.
I have no such evidence, but I'll be damned if I'm not going to investigate now. I'm guessing that the Google Location Services TOS that every Android phone presents at setup time might be an interesting re-read.
Not that it matters, but it doesn't work that way... (My full time job involved researching proximity algorithms)... Using Wifi as proximity, you can tell that say these 5 particular people are in a room, but you have zero idea the spatial relation of each of these 5 people to each other, without the aid of other sensors. Wifi or bluetooth will not give you spatial relationships in any meaningful manner.
The problem is that this is all happening over a long period of time, with a constant location fix. So you're right that a one-time scan of nearby devices is pretty much useless - but looking at who was near me every time I go to my favourite Starbucks over the course of a year will give you a pretty good idea of who is actually there with me.
Spatial relationships in a room less to Google than knowing who is part of my life, and who to suggest I might want to make part of my life.
Any smartphone can see all the MAC addresses of all phones and access points around it, bluetooth or WiFi (if enabled of course). With GPS positioning on most of those devices and a Giant Corporate Big Brother aggregating the results, all of us are reporting on our proximity to each other.
We all know that Google's wifi geolocation stuff works this way - by tracking which fixed wifi base stations are in range and correlating with a GPS fix. People forget that Google can also identify other phones within range of your phone, and they know which Google accounts are attached to those devices.
Google really does know who is sitting next to you on the train or in the coffee shop, who your jogging partner is, and which whore you visit when your wife leaves your general vicinity.
I bet they do some amazing automated profiling. This guy is a garbage man and works with these people, that guy likes to sit in coffee shops and this woman is usually also present, she's not his wife, so lets advertise couples vacations and cheater sites, this other woman visits a preschool every day and is probably a parent, let's suggest other parents from the same preschool as her Google+ friend...
I hope to never feel that "oh shit, I hope I haven't just blown my /home away" thrill ever again though.
What, the /home that you have a full backup up on an external hd or equivalent?
Of course! That one. *wink*
Did a fresh F18 install on my laptop this past week.
I have to agree with a lot of the criticism of the new installer, and particularly the user interface for disk partitioning. I've been running Linux since the late 90s and I don't think I've ever been confused by a partition editor, from fdisk on up - until now.
I mean, the error message I got was "Not enough disk space to create a mountpoint". WHAT DOES THAT EVEN MEAN?!? And this while trying to get the thing to recognize my existing /home partition.
It's like someone who has never partitioned a disk before created a really bad abstract model of the process and then based the whole user interface off of their grand concept. In the process of trying to make things easy they made it hard for anyone who knows what they are doing to be specific about what should be done. A liberal sprinkling of incorrectly-used disk partitioning terms makes for a real perfect storm of confusion.
Once I got things installed, I had no problems at all. I hope to never feel that "oh shit, I hope I haven't just blown my /home away" thrill ever again though.
We have always had standardized checkstyle and jtidy rules as part of our build system. We have eclipse formatting configuration that everyone uses as well. Commits don't happen unless checkstyle is happy.
I thought everyone did this. I guess tooling is less developed in some languages, but it's not too hard to put this kind of thing into practice with a little bit of effort and buy-in.
Push? How? Like... a global vaccination program?
Careful, we might get the anti-crypters all hot and bothered.
"But there's PROOF that encryption makes people cheat on their partners! And I have nothing to hide, anyway!"
After years and years of using a laptop as my main machine, a year ago I built myself a no-compromise workstation.
The logic was simple: I realized that when I was out and about with the laptop, I never did much heavy lifting. When I got on the Android bandwagon, the need to use a laptop as a browsing/ssh/mail device just went away.
Now, when I anticipate being a loser and writing code at Starbucks for a change of scene, I grab one of the cheap netbooks we have lying around, VNC into my desktop, and off I go. Bonus: if it gets stolen, there's nothing of value on it. Double bonus: disapproving glances from Apple users due to the anti-apple stickers on the lid.
We have a tablet for the coffee table, and it mostly gets used for recipes, Facebook, and controlling XBMC. That's it.
It's just horses for courses. No one wants a general purpose PC for round-the-house drudgery, people with smartphones don't need laptops to communicate.
It all seems to come down to two questions. "Do you need a keyboard?" and "Do you need actual CPU power?" For many folks, it seems the answer to both is mostly no.
I wonder if my kid will ever build a PC.
The Usurper
Create a VM endpoint in the US on something like Amazon Web Services. Fire up a tunnel (vtund over ssh? openvpn? whatever) from your ship's router to your endpoint, route traffic through it, make sure your local DNS resolves through the tunnel, and call it a day. This way you won't need to tell people to mess around with VPN clients. The fewer moving parts, the better.
This is pretty simplistic though. You need to give us more details. How much bandwidth do you have to play with? What is the expected latency? How much tolerance is there for downtime? How much access control do you need? There are all kinds of additional steps that could make this kind of service more reliable.
I pay for my email now, because I want to be someone's customer, not someone's product
Fastmail is great. No ads, a decent Web UI when I want it, and a dedicated sysadmin team that does nothing but mail. All the Bayesian filtering, Sieve rules and DKIM signing you could want. Plus, I keep my conversations and business dealings out of Google's maw (although it's hard to avoid people who use GMail), and there's Yubikey authentication for when I'm on someone else's machine.
fastmail.fm (full disclosure: referral link included)
I have administered mail servers professionally before and have quite a bit of experience with it. If I'm not being paid to do it I'm sure as hell paying someone else to deal with the hassle.
I've been happy with Trillian.
http://www.trillian.im/android/
The logo looks like a stick-figure Madonna with giant conical red boobs.
Now you can't unsee it.