[Bug 1224254] Re: xrandr Xerrors with the nvidia binary drivers (optimus)
Hello Brian Using the proposed package fixes the XReply bug. I now experience other bugs from other display related packages. I set up my display incorrectly at first so they just might be reports of that. I'll reboot and see if they remain. Otherwise the theme is correct, the keyboard layout holds and key combinations work again. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1224254 Title: xrandr Xerrors with the nvidia binary drivers (optimus) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-desktop/+bug/1224254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1224254] Re: xrandr Xerrors with the nvidia binary drivers (optimus)
An update: No other crashes after rebooting. Booting with a secondary display attached causes it to fail miserably though. Attaching the display after the xsession is up and running works as it should. I'll play around with the xorg,conf and see if I can sort it out. I don't think it has anything to do with this package. (Probably just a mistake in xorg.conf from my part) Thanks again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1224254 Title: xrandr Xerrors with the nvidia binary drivers (optimus) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-desktop/+bug/1224254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1225405] Re: gdm fails to connect to screen after installing nvidia-319 drivers
The problem was that .xinitrc/.xsessionrc was not run when using gdm so adding the lines xrandr --setprovideroutputsource modesetting NVIDIA-0 xrandr --auto in /etc/gdm/Init/Default fixed the problem, but lead to other errors later. (I reported them as different errors as they aren't related to gdm - as far as I can tell) If someone can just please close this bug report please -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1225405 Title: gdm fails to connect to screen after installing nvidia-319 drivers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1225405/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1224254] Re: [xrandr]: gnome-settings-daemon crashed with signal 5 in _XReply()
My laptop has an optimus graphics card. I don't have nvidia-prime installed. I condifured it manually since nvidia-prime doesn't configure it for gdm only for lightdm. and the problem persists, so it's not specifically to do with nvidia- prime. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1224254 Title: [xrandr]: gnome-settings-daemon crashed with signal 5 in _XReply() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1224254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1242275] [NEW] Extreme load times after installing and setting up nvidia-319
Public bug reported: 1) I'm using Ubuntu GNOME 13.10 2) Latest Packages (Okt 20) 3) I expected it load normally 4) lots of things broke: - It took extremely long to load (before installation it was extremely quick) - GTK themes is broken (Look like classic X almost) Thing that are borken that I didn't check before installation: - Shortcut keys don't work How to reproduce: After a clean installation of Ubuntu GNOME 13.10 I installed vim (to edit text files) and nvidia-319 I set xorg.conf as specified by nvidia I added the lines xrandr --setprovideroutputsource modesetting NVIDIA-0 xrandr --auto to the top of the /etc/gcm/Init/Default file (nvidia said xinitrc, but that is not run when running gdm) reboot and then problems appear ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 319.32 Wed Jun 19 15:51:20 PDT 2013 GCC version: gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu8) ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Oct 20 10:26:59 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: nvidia-319, 319.32, 3.11.0-12-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:5105] NVIDIA Corporation GK104M [GeForce GTX 675MX] [10de:11a7] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:5105] InstallationDate: Installed on 2013-10-19 (1 days ago) InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Release amd64 (20131017) MachineType: CLEVO P15xEMx MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=391583ce-8803-4e00-8321-60d9b764 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/19/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Not Applicable dmi.board.name: P15xEMx dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: CLEVO dmi.chassis.version: Not Applicable dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/19/2012:svnCLEVO:pnP15xEMx:pvrNotApplicable:rvnCLEVO:rnP15xEMx:rvrNotApplicable:cvnCLEVO:ct10:cvrNotApplicable: dmi.product.name: P15xEMx dmi.product.version: Not Applicable dmi.sys.vendor: CLEVO version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Sun Oct 20 10:21:03 2013 xserver.configfile: /etc/X11/xorg.conf xserver.errors: Failed to load /usr/lib/xorg/modules/libglamoregl.so: /usr/lib/xorg/modules/libglamoregl.so: undefined symbol: _glapi_tls_Context Failed to load module glamoregl (loader failed, 7) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.14.3-3ubuntu2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1242275 Title: Extreme load times after installing and setting up nvidia-319 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1242275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1232770] Re: [printers]: gnome-control-center crashed with SIGSEGV in g_slist_copy_deep()
*** This bug is a duplicate of bug 1160655 *** https://bugs.launchpad.net/bugs/1160655 Hi The bug report that you linked to is private so I can't look at the other bug report. (Also why it didn't show up when searching for similar bugs before posting this one) Regards -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1232770 Title: [printers]: gnome-control-center crashed with SIGSEGV in g_slist_copy_deep() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1232770/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1225405] [NEW] gdm fails to connect to screen after installing nvidia-319 drivers
Public bug reported: Ubuntu version: 13.10 Gnome SW version: updated using ftp.wa.co.za Sep 14 15:00 local time from the development branch (happens with earlier version aswel) HW: Roccat P502 4AB Laptop Expected: GDM login prompt appears Happened: Depending on things I tried the splash screen stays on, the display turns of after splash screen, displays a window that can only do text (Not a console - when this happens Xserver ussually crashed) More info: I am using Ubuntu 13.10 Gnome. After installing nvidia-319 drivers the gdm doesn't start properly. If I remove the nvidia drivers it works again. If I install nvidia-prime it connects to the screen when starting up with ligthdm (but there is graphical glitches), but does not connect with gdm. Neither gdm or xserver reports any error in their log which are related with video systems.fo ** Affects: gdm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1225405 Title: gdm fails to connect to screen after installing nvidia-319 drivers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1225405/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 851824] Re: Wireless won't boot up for Acer 1830T-68U118
I still have this problem. ** Changed in: linux (Ubuntu) Status: Expired = Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/851824 Title: Wireless won't boot up for Acer 1830T-68U118 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/851824/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 851824] [NEW] Wireless won't boot up for Acer 1830T-68U118
Public bug reported: I am new at using Unbutu here so please help. When I boot up my Acer using Unbutu Linux from USB stick, the laptop won't connect to wireless. Under Windows, the wireless hardware (light) will turn on automatically. Along with the wireless driver, this hardware is activated by a software program called Launch Manager. So under Linux, it would not be activated. It did see the correct wireless LAN driver, however. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/851824 Title: Wireless won't boot up for Acer 1830T-68U118 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/851824/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 562092] Re: [Lucid] cdrom drive not recognized automatically
Had similar problem with my cdrom drive. Found the reason and solution to my problem here: http://ubuntuforums.org/showthread.php?t=1025786 Solved my problem by removing the the udf from my /etc/fstab where my cdrom was mounted from: /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0 to /dev/scd0 /media/cdrom0 iso9660 user,noauto,exec,utf8 0 0 then remount your cdrom (e.g. mount /media/cdrom0) Lucid is mounting with udf option in fstab. Mounting the filesystem as iso9660 doesn't observe file permissions. Mounting as UDF does. Unfortunately, many disk burning applications leave -1 in the uid and gid permissions of their udf filesystems. This causes a permission problem in Linux. The only way to read CD's as a user is by mounting UDF filesystems on cdrom as iso9660. Makes sense -- [Lucid] cdrom drive not recognized automatically https://bugs.launchpad.net/bugs/562092 You received this bug notification because you are a member of Ubuntu Bugs, which is a bug assignee. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
