[Desktop-packages] [Bug 1163404] Re: xerver-xorg-core 2:1.13.3-0ubuntu3 breaks bumblebee
Yes, because we changed the config files of Bumblebee to cover this case, but the upstream bug in X.org still exists. ** Package changed: xorg-server (Ubuntu) = xorg-server -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1163404 Title: xerver-xorg-core 2:1.13.3-0ubuntu3 breaks bumblebee Status in X.Org X server: Confirmed Bug description: Since this version, Bumblebee fails to start a secondary xserver on the NVIDIA card, with either nouveau or any flavors of the nvidia graphics driver. Is this an issue on the Bumblebee side, and then how to fix it, or is this changes made by Ubuntu that causes this problem (indeed they do, but the question is about who has to fix this)? Maarten Lankhorst answered this when contacted by email: If you want to load the nvidia module you need to specify it explicitly in your configuration. Intel failed to be detected before because of a bug. You were probably already running a xserver with intel. Before it would just fail entirely because the intel card was already in use, now it still detects the intel card through udev. As a workaround I suppose you could append something like -seat bla, in which case the intel device will not be found through udev, unless you had the ID_SEAT property for that device set to bla too. However, I haven't been able to make the seat option to work either since in fact this is equivalent to what we do with loading X using custom conf files. I'm providing logs for the non-working case, and will ask someone to add those for the working one (can't revert to 2b1 at the moment). To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1163404/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1163404] Re: xerver-xorg-core 2:1.13.3-0ubuntu3 breaks bumblebee
This appears to have been fixed at some point. Testing with current packages is not showing the problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1163404 Title: xerver-xorg-core 2:1.13.3-0ubuntu3 breaks bumblebee Status in xorg-server package in Ubuntu: Confirmed Bug description: Since this version, Bumblebee fails to start a secondary xserver on the NVIDIA card, with either nouveau or any flavors of the nvidia graphics driver. Is this an issue on the Bumblebee side, and then how to fix it, or is this changes made by Ubuntu that causes this problem (indeed they do, but the question is about who has to fix this)? Maarten Lankhorst answered this when contacted by email: If you want to load the nvidia module you need to specify it explicitly in your configuration. Intel failed to be detected before because of a bug. You were probably already running a xserver with intel. Before it would just fail entirely because the intel card was already in use, now it still detects the intel card through udev. As a workaround I suppose you could append something like -seat bla, in which case the intel device will not be found through udev, unless you had the ID_SEAT property for that device set to bla too. However, I haven't been able to make the seat option to work either since in fact this is equivalent to what we do with loading X using custom conf files. I'm providing logs for the non-working case, and will ask someone to add those for the working one (can't revert to 2b1 at the moment). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1163404/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1163404] Re: xerver-xorg-core 2:1.13.3-0ubuntu3 breaks bumblebee
Seems to be a bug in upstream X.org, that Ubuntu patches uncovered: https://bugs.freedesktop.org/show_bug.cgi?id=63576 ** Bug watch added: freedesktop.org Bugzilla #63576 https://bugs.freedesktop.org/show_bug.cgi?id=63576 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1163404 Title: xerver-xorg-core 2:1.13.3-0ubuntu3 breaks bumblebee Status in “xorg-server” package in Ubuntu: Confirmed Bug description: Since this version, Bumblebee fails to start a secondary xserver on the NVIDIA card, with either nouveau or any flavors of the nvidia graphics driver. Is this an issue on the Bumblebee side, and then how to fix it, or is this changes made by Ubuntu that causes this problem (indeed they do, but the question is about who has to fix this)? Maarten Lankhorst answered this when contacted by email: If you want to load the nvidia module you need to specify it explicitly in your configuration. Intel failed to be detected before because of a bug. You were probably already running a xserver with intel. Before it would just fail entirely because the intel card was already in use, now it still detects the intel card through udev. As a workaround I suppose you could append something like -seat bla, in which case the intel device will not be found through udev, unless you had the ID_SEAT property for that device set to bla too. However, I haven't been able to make the seat option to work either since in fact this is equivalent to what we do with loading X using custom conf files. I'm providing logs for the non-working case, and will ask someone to add those for the working one (can't revert to 2b1 at the moment). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1163404/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1163404] Re: xerver-xorg-core 2:1.13.3-0ubuntu3 breaks bumblebee
Workaround: https://github.com/Bumblebee- Project/Bumblebee/issues/367#issuecomment-16102053 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1163404 Title: xerver-xorg-core 2:1.13.3-0ubuntu3 breaks bumblebee Status in “xorg-server” package in Ubuntu: Confirmed Bug description: Since this version, Bumblebee fails to start a secondary xserver on the NVIDIA card, with either nouveau or any flavors of the nvidia graphics driver. Is this an issue on the Bumblebee side, and then how to fix it, or is this changes made by Ubuntu that causes this problem (indeed they do, but the question is about who has to fix this)? Maarten Lankhorst answered this when contacted by email: If you want to load the nvidia module you need to specify it explicitly in your configuration. Intel failed to be detected before because of a bug. You were probably already running a xserver with intel. Before it would just fail entirely because the intel card was already in use, now it still detects the intel card through udev. As a workaround I suppose you could append something like -seat bla, in which case the intel device will not be found through udev, unless you had the ID_SEAT property for that device set to bla too. However, I haven't been able to make the seat option to work either since in fact this is equivalent to what we do with loading X using custom conf files. I'm providing logs for the non-working case, and will ask someone to add those for the working one (can't revert to 2b1 at the moment). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1163404/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1163404] Re: xerver-xorg-core 2:1.13.3-0ubuntu3 breaks bumblebee
Setting BusID in nouveau and nvidia xorg.conf file solves this. However, this is not normal, since isolateDevice should have the same effect. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1163404 Title: xerver-xorg-core 2:1.13.3-0ubuntu3 breaks bumblebee Status in “xorg-server” package in Ubuntu: Confirmed Bug description: Since this version, Bumblebee fails to start a secondary xserver on the NVIDIA card, with either nouveau or any flavors of the nvidia graphics driver. Is this an issue on the Bumblebee side, and then how to fix it, or is this changes made by Ubuntu that causes this problem (indeed they do, but the question is about who has to fix this)? Maarten Lankhorst answered this when contacted by email: If you want to load the nvidia module you need to specify it explicitly in your configuration. Intel failed to be detected before because of a bug. You were probably already running a xserver with intel. Before it would just fail entirely because the intel card was already in use, now it still detects the intel card through udev. As a workaround I suppose you could append something like -seat bla, in which case the intel device will not be found through udev, unless you had the ID_SEAT property for that device set to bla too. However, I haven't been able to make the seat option to work either since in fact this is equivalent to what we do with loading X using custom conf files. I'm providing logs for the non-working case, and will ask someone to add those for the working one (can't revert to 2b1 at the moment). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1163404/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1163404] Re: xerver-xorg-core 2:1.13.3-0ubuntu3 breaks bumblebee
So some detailed informations: we use -isolateDevice on the nvidia card, and set AutoAddGPU to false. This is working everywhere else, and has been working on Ubuntu up to 1.13.3-0ubuntu3. Adding BusID is making things work, but normally, our setup is doing already more than that, and BusID shouldn't be needed when isolateDevice and AutoAddGPUs are set... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1163404 Title: xerver-xorg-core 2:1.13.3-0ubuntu3 breaks bumblebee Status in “xorg-server” package in Ubuntu: Confirmed Bug description: Since this version, Bumblebee fails to start a secondary xserver on the NVIDIA card, with either nouveau or any flavors of the nvidia graphics driver. Is this an issue on the Bumblebee side, and then how to fix it, or is this changes made by Ubuntu that causes this problem (indeed they do, but the question is about who has to fix this)? Maarten Lankhorst answered this when contacted by email: If you want to load the nvidia module you need to specify it explicitly in your configuration. Intel failed to be detected before because of a bug. You were probably already running a xserver with intel. Before it would just fail entirely because the intel card was already in use, now it still detects the intel card through udev. As a workaround I suppose you could append something like -seat bla, in which case the intel device will not be found through udev, unless you had the ID_SEAT property for that device set to bla too. However, I haven't been able to make the seat option to work either since in fact this is equivalent to what we do with loading X using custom conf files. I'm providing logs for the non-working case, and will ask someone to add those for the working one (can't revert to 2b1 at the moment). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1163404/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1163404] Re: xerver-xorg-core 2:1.13.3-0ubuntu3 breaks bumblebee
I tested with the nvidia-313-updates package on my new P150EM and got the same results. Backleveling xserver -xorg-core works around the problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1163404 Title: xerver-xorg-core 2:1.13.3-0ubuntu3 breaks bumblebee Status in “xorg-server” package in Ubuntu: Confirmed Bug description: Since this version, Bumblebee fails to start a secondary xserver on the NVIDIA card, with either nouveau or any flavors of the nvidia graphics driver. Is this an issue on the Bumblebee side, and then how to fix it, or is this changes made by Ubuntu that causes this problem (indeed they do, but the question is about who has to fix this)? Maarten Lankhorst answered this when contacted by email: If you want to load the nvidia module you need to specify it explicitly in your configuration. Intel failed to be detected before because of a bug. You were probably already running a xserver with intel. Before it would just fail entirely because the intel card was already in use, now it still detects the intel card through udev. As a workaround I suppose you could append something like -seat bla, in which case the intel device will not be found through udev, unless you had the ID_SEAT property for that device set to bla too. However, I haven't been able to make the seat option to work either since in fact this is equivalent to what we do with loading X using custom conf files. I'm providing logs for the non-working case, and will ask someone to add those for the working one (can't revert to 2b1 at the moment). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1163404/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1163404] Re: xerver-xorg-core 2:1.13.3-0ubuntu3 breaks bumblebee
Me too, here's my Xorg.8.log. Maybe now I know what the bug is I can try the 310 drivers again. ** Attachment added: Xorg.8.log https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1163404/+attachment/3618284/+files/Xorg.8.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1163404 Title: xerver-xorg-core 2:1.13.3-0ubuntu3 breaks bumblebee Status in “xorg-server” package in Ubuntu: Confirmed Bug description: Since this version, Bumblebee fails to start a secondary xserver on the NVIDIA card, with either nouveau or any flavors of the nvidia graphics driver. Is this an issue on the Bumblebee side, and then how to fix it, or is this changes made by Ubuntu that causes this problem (indeed they do, but the question is about who has to fix this)? Maarten Lankhorst answered this when contacted by email: If you want to load the nvidia module you need to specify it explicitly in your configuration. Intel failed to be detected before because of a bug. You were probably already running a xserver with intel. Before it would just fail entirely because the intel card was already in use, now it still detects the intel card through udev. As a workaround I suppose you could append something like -seat bla, in which case the intel device will not be found through udev, unless you had the ID_SEAT property for that device set to bla too. However, I haven't been able to make the seat option to work either since in fact this is equivalent to what we do with loading X using custom conf files. I'm providing logs for the non-working case, and will ask someone to add those for the working one (can't revert to 2b1 at the moment). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1163404/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1163404] Re: xerver-xorg-core 2:1.13.3-0ubuntu3 breaks bumblebee
** Attachment added: Xorg log for nvidia https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1163404/+attachment/3615200/+files/Xorg.8.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1163404 Title: xerver-xorg-core 2:1.13.3-0ubuntu3 breaks bumblebee Status in “xorg-server” package in Ubuntu: New Bug description: Since this version, Bumblebee fails to start a secondary xserver on the NVIDIA card, with either nouveau or any flavors of the nvidia graphics driver. Is this an issue on the Bumblebee side, and then how to fix it, or is this changes made by Ubuntu that causes this problem (indeed they do, but the question is about who has to fix this)? Maarten Lankhorst answered this when contacted by email: If you want to load the nvidia module you need to specify it explicitly in your configuration. Intel failed to be detected before because of a bug. You were probably already running a xserver with intel. Before it would just fail entirely because the intel card was already in use, now it still detects the intel card through udev. As a workaround I suppose you could append something like -seat bla, in which case the intel device will not be found through udev, unless you had the ID_SEAT property for that device set to bla too. However, I haven't been able to make the seat option to work either since in fact this is equivalent to what we do with loading X using custom conf files. I'm providing logs for the non-working case, and will ask someone to add those for the working one (can't revert to 2b1 at the moment). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1163404/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1163404] Re: xerver-xorg-core 2:1.13.3-0ubuntu3 breaks bumblebee
** Attachment added: Xorg log for nvidia - working case https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1163404/+attachment/3615762/+files/Xorg.8.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1163404 Title: xerver-xorg-core 2:1.13.3-0ubuntu3 breaks bumblebee Status in “xorg-server” package in Ubuntu: Confirmed Bug description: Since this version, Bumblebee fails to start a secondary xserver on the NVIDIA card, with either nouveau or any flavors of the nvidia graphics driver. Is this an issue on the Bumblebee side, and then how to fix it, or is this changes made by Ubuntu that causes this problem (indeed they do, but the question is about who has to fix this)? Maarten Lankhorst answered this when contacted by email: If you want to load the nvidia module you need to specify it explicitly in your configuration. Intel failed to be detected before because of a bug. You were probably already running a xserver with intel. Before it would just fail entirely because the intel card was already in use, now it still detects the intel card through udev. As a workaround I suppose you could append something like -seat bla, in which case the intel device will not be found through udev, unless you had the ID_SEAT property for that device set to bla too. However, I haven't been able to make the seat option to work either since in fact this is equivalent to what we do with loading X using custom conf files. I'm providing logs for the non-working case, and will ask someone to add those for the working one (can't revert to 2b1 at the moment). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1163404/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1163404] Re: xerver-xorg-core 2:1.13.3-0ubuntu3 breaks bumblebee
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg-server (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1163404 Title: xerver-xorg-core 2:1.13.3-0ubuntu3 breaks bumblebee Status in “xorg-server” package in Ubuntu: Confirmed Bug description: Since this version, Bumblebee fails to start a secondary xserver on the NVIDIA card, with either nouveau or any flavors of the nvidia graphics driver. Is this an issue on the Bumblebee side, and then how to fix it, or is this changes made by Ubuntu that causes this problem (indeed they do, but the question is about who has to fix this)? Maarten Lankhorst answered this when contacted by email: If you want to load the nvidia module you need to specify it explicitly in your configuration. Intel failed to be detected before because of a bug. You were probably already running a xserver with intel. Before it would just fail entirely because the intel card was already in use, now it still detects the intel card through udev. As a workaround I suppose you could append something like -seat bla, in which case the intel device will not be found through udev, unless you had the ID_SEAT property for that device set to bla too. However, I haven't been able to make the seat option to work either since in fact this is equivalent to what we do with loading X using custom conf files. I'm providing logs for the non-working case, and will ask someone to add those for the working one (can't revert to 2b1 at the moment). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1163404/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
