hi there.
I managed to fix this by installing the nvidia-prime package and tweaking the
bumblebee config files a little.
this is weird though since on previous versions of ubuntu the installation of
the nvidia-prime package used to break bumblebee, but the same thing that
breaks it apparently
there is a workaround to this.
install the nvidia-prime package and type
"sudo prime-select intel" this will force the intel GPU.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1508573
also see:
http://ubuntuforums.org/showthread.php?t=2297755
every reboot results in having the following contents in
/etc/X11/xorg.conf
Section "ServerLayout"
Identifier "layout"
Screen 0 "nvidia"
Inactive "intel"
EndSection
the intel section also displays "none" as acceleration
Public bug reported:
removing the nvidia-driver and /etc/X11/xorg.conf and manually launching
lightdm from the command-line solves it.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: bumblebee 3.2.1-9
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic
Public bug reported:
here's the gdb backtrace info.
gdb nautilus
GNU gdb (GDB) 7.6.1-ubuntu
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO
** Description changed:
here's the gdb backtrace info.
-
gdb nautilus
GNU gdb (GDB) 7.6.1-ubuntu
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and
is present again in 13.10
banshee crashes with:
Debug info from gdb:
Could not attach to process. If your uid matches the uid of the target
process, check the setting of /proc/sys/kernel/yama/ptrace_scope, or try
again as the root user. For more details, see /etc/sysctl.d/10-ptrace.conf
ptrace:
something strange happened.
i switched the display manager to KDM (dpkg -configure)
after a reboot and logging in using KDM it started to ask all kinds of
passwords for unlocking keyrings etc.
so I concluded that wasn't a huge success so I switched it back to lightdm and
strangely the bug
Public bug reported:
I've got a strange thing going on with my computer,
after boot I get a working lightdm that logs in my sister's account (without
password), can launch a guest session. but when I try to loging on my own
account (with password) I get a black screen followed by the lightdm
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/993799
Title:
lightdm freezes when logging in with password
Status in “lightdm” package in Ubuntu:
New
Bug description:
I've got a
lightdm.log is added as attachment,
because I can only submit 1 attachment each time here is the ~/.xsession-errors
Xsession: X session started for niek at do mei 3 17:17:39 CEST 2012
localuser:niek being added to access control list
openConnection: connect: Bestand of map bestaat niet
cannot
update: today i've shifted my pc 10 inches and placed one antenna onto
the metal frame of my desk, and the other one layed down on the floor,
for some reason i was able to manage a stable 1,4MB/s connection for
over an hour after that speed dropped again maybe 20 inches will do
it?
--
You
12 matches
Mail list logo
