Hmm, sorry about this (I think
A number of users were complaining about this but it turns out it was more
about cursor movement than clicks
(or so combo of the cursor moving then a click on new position after timeout.
In any event it was never intended to prevent cursor movement while typing
So
log out is 800% slower than usual (pre 13.10), now around 10 sec.
On nvidia hardware, 8400m gs, doesn't matter if nouveau or nvidia, (currently
3.10 kernel, 319 drivers), current, newer or older kernels inc. raring's,
lightdm or gdm, ect., 10 secs on/with all combos.
Didn't happen early on in 1
Also to note - on same hardware using ubuntu-gnome image log outs are as
normal for here - 1 - 1.5 sec.'s
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.net/bugs/1191426
Title:
logo
At least here on previously affected machine this is longer an issue,
log outs are back to about 1 sec. or so
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.net/bugs/1191426
Title:
Can also confirm the 2 patches fix all 3 scrolling bug here, (applied to
1.14.3-5ubuntu1 source, trusty
(this bug, the jerky scrolling bug & scrolling in an unfocused window
Haven't noticed any unintended consequence as of yet
--
You received this bug notification because you are a member of Ub
sounds very much like this bug thiugh the size of the box was reported to be
much smaller
Only happens with google-chrome, chromium
bug 941586
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.launch
Seeing same on the current nvidia, 295.33-0ubuntu1
Same scenario, good for 4 - 8 restarts/boots, then fails for good.
Additionally cannot switch to any tty other than 7, only a black screen is
produced
** Summary changed:
- nvidia-graphics-drivers (295.20-0ubuntu1), is causing failed restarts &
*** This bug is a duplicate of bug 941066 ***
https://bugs.launchpad.net/bugs/941066
** This bug has been marked a duplicate of bug 941066
Dash is totally broken when disabling the blur effect
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
Sam_ - this seems fixed in unity-5.10 - there is no more black on scrolling
Not to say you'll like it - the no-blur Dash is lightly tinted based on the
average background color
I dislike it for the almost opposite reason - too much shows thru here & there
is no way to adjust the opacity of the D
Just to follow up -
using fresh beta installs
This issue remains & occurs as described on a 32 bit install, 3 good cycles
then will break shortly after - the 290.XX drivers were last good ones
However on a 64 bit install it never occurs, shutdowns/restarts &
switching tty's are solid
--
You
re-broken in 14.10 with compiz 1:0.9.11+14.10.20140606-0ubuntu1, at least on a
laptop with usb mouse -
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1330198
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://
Public bug reported:
With 2:2.99.914-1~exp1ubuntu1 a normal boot produces a login where -
black desktop background
no unity panel
a non-functional launcher
If I boot to recovery > resume then do get an ubuntu session but using lvmpipe.
ie.
$ /usr/lib/nux/unity_support_test -p
OpenGL vendor str
After downgrading & restarting, normal boot -
~$ /usr/lib/nux/unity_support_test -p
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) Haswell Mobile
OpenGL version string: 3.0 Mesa 10.2.5
Not software rendered:yes
Not blacklisted:
** Description changed:
- With 2:2.99.914-1~exp1ubuntu1 a normal boot produces a login where -
+ With 2:2.99.914-1~exp1ubuntu1 a normal boot produces a login where -
black desktop background
no unity panel
a non-functional launcher
+ nothing can be done
- If I boot to recovery > resume t
** Summary changed:
- 2:2.99.914-1~exp1ubuntu1 breaks 3d support on some intel hardware
+ 2:2.99.914-1~exp1ubuntu1 breaks unity on some intel hardware
** Also affects: unity
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
w
*** This bug is a duplicate of bug 1357746 ***
https://bugs.launchpad.net/bugs/1357746
** This bug has been marked a duplicate of bug 1357746
unity fails to load with xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu1
--
You received this bug notification because you are a member of Ubuntu
Can also be noted that a gnome-flashback > compiz session is likewise affected
though the symptoms are slightly different
(- nothing happens for a while, then booted back to greeter.
It also returns to expected with a downgraded xserver-xorg-video-intel package
If there is any specific means to p
** Description changed:
Logs into a session with
black desktop
no unity panel
a non functional launcher
Nothing can be done in the session except go to a tty
If I downgrade back to xserver-xorg-video-intel_2.99.910-0ubuntu1 then
- all is well & unity loads as expected
+ all is we
To clear up -
1. This bug was filed by running apport -cli from a tty, saving the report,
then filing that report from a recovery boot
(if there is a better way to use apport from a tty tell me.
2. The kernel version is *irrelevant*, compiz fails with any kernel inc.
going back to 3.13.x when x
** Also affects: nouveau
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1357746
Title:
Compiz fails to load with xserver-xorg-vid
If I either blacklist nouveau or remove the xserver-xorg-video-nouveau package
then everything works as expected with the current xserver-xorg-video-intel
package.
This also *seems* to make restarts & shutdowns more reliable & makes going to a
tty not be liable to cause some sort of looping kern
fixed with latest xserver* 1.0.11
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1357746
Title:
Compiz fails to load with xserver-xorg-video-intel
2:2.99.914-1~exp1ubuntu1
I meant 1.16.x & 2.99.914-1~exp1ubuntu2/3
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bu
gpu-manager log from an ubuntu session
** Attachment added: "gpu-manager-ubuntu.log"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1501041/+attachment/4479225/+files/gpu-manager-ubuntu.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subsc
journalctl from a gnome session
** Attachment added: "gnome-journalctl.log"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1501041/+attachment/4479224/+files/gnome-journalctl.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xo
glxinfo log from an ubuntu session
** Attachment added: "glxinfo.log"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1501041/+attachment/4479226/+files/glxinfo.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ub
Public bug reported:
Please note that this bug is being filed on a recent 15.10 Ubuntu image
install but from a gnome session
In a nutshell -
Once nividia drivers are installed & used from nvidia-prime there is no longer
a visible display in unity-greeter nor in an ubuntu session once logged in
journalctl from an ubuntu session
** Attachment added: "no-display-journalctl.log"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1501041/+attachment/4479223/+files/no-display-journalctl.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subs
Ex. of stdout from playing a vid in cli player in an ubuntu session with
nvidia(vdpau), no errors
(obviously I only here sound as there is no visible display
Playing: 1.mp4
(+) Video --vid=1 (*) (h264)
(+) Audio --aid=1 --alang=und (*) (aac)
AO: [pulse] 44100Hz stereo 2ch float
Using hardware d
Installed fine in 14.04.3 (using hwe vivid stack), both the lib & -dev packages
Also allowed desmume to install & open
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in
** Summary changed:
- No visible display in ubuntu session when using nvidia drivers via
nvidia-prime
+ No visible display in ubuntu session when using nvidia drivers via
nvidia-prime until screen goes to sleep, then waked up
** Description changed:
Please note that this bug is being filed o
What happens in an ubuntu session is -
After logging in, no display. If the session is left inactive until display is
put to sleep, then awakining it thru keyboard or mouse brings back a visible
display. (default is 5 min. of inactivity
A simple startup script via startup applications demons
Also affects Xubuntu
** Also affects: xfce4-session (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.launchpad.net/bugs/1501041
Title:
No visi
** Description changed:
- Please note that this bug is being filed on a recent 15.10 Ubuntu image
- install but from a gnome session
+ ** this appears to be that the display is blanked/asleep at greeter & login.
+ Forcing or waiting for screen to blank/sleep then waking up restores display
+ See c
Demonstration 2
If the autostart script was in place then disable
Alter the sleep time of unity-greeter from 300 to 6 (sec) in
/usr/share/glib-2.0/schemas/com.canonical.unity-greeter.gschema.xml
(at bottom of file, assumes 6 sec is enough time to enter password, if not
increase 6 to something su
** Also affects: xorg-server (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1501041
Title:
No visible display in ubuntu session when u
** Also affects: lightdm (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1501041
Title:
No visible display in ubuntu session when using
** Tags added: lubuntu xubuntu
** Tags removed: amd64
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1501041
Title:
No visible display in ubuntu session when using nvidia drivers via
n
** Changed in: ubuntu-drivers-common (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: nvidia-graphics-drivers (Ubuntu)
Status: Triaged => Invalid
** Changed in: lightdm (Ubuntu)
Status: Confirmed => Invalid
** Changed in: unity-greeter (Ubuntu)
Status: Confir
A "regression in the intel driver" doesn't seem to explain why this was not an
issue in a gnome session, nor to the fact that -
xset dpms force off
xset dpms force on
returned display both in greeter & session
(and nvidia driver loaded & worked fine, with or without a visible display.
you
Not really fixed so opening again
** Changed in: ubuntu-drivers-common (Ubuntu)
Status: Fix Released => Confirmed
** Changed in: lightdm (Ubuntu)
Status: Invalid => Confirmed
** Changed in: xorg-server (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notifica
** Summary changed:
- No visible display in ubuntu session when using nvidia drivers via
nvidia-prime until screen goes to sleep, then waked up
+ No visible display in non gnome sessions when using nvidia drivers via
nvidia-prime until screen goes to sleep, then waked up
--
You received this b
Well then hopefully you can get it so this change to modesetting can be
reverted & one isn't forced to get screen to sleep then awake.
My whole point was that this report is claiming that the switch from Intel to
Nvidia fails which is not true is any respect.
It's purely a matter of no visible
** Tags added: xenial
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1501041
Title:
No visible display in non gnome sessions when using nvidia drivers via
nvidia-prime until screen goes
** Changed in: xorg-server (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1528667
Title:
Xorg crashed with SIGABRT in RRCrtcDetachScanoutPixmap()
T
** Also affects: xserver-xorg-video-intel
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1532343
Title:
Xorg crashed with SIGABRT in draw_curre
Sorry to report that see same crash with the patch
Tried with both ubuntu & gnome sessions. (shouldn't matter & didn't but
recent mesa issue makes me test both just in case.
On 01/14/2016 01:19 PM, Robert Hooker wrote:
> Chris Wilson from Intel has passed along a patch that may fix it and
> asked
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/929475
Title:
nvidia-settings crashed with SIGSEGV
To manage notifications about this bug go to:
https
*** This bug is a duplicate of bug 929384 ***
https://bugs.launchpad.net/bugs/929384
** This bug has been marked a duplicate of bug 929384
nvidia drivers broken by the recent libc update
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvi
** Package changed: utouch-geis (Ubuntu) => xserver-xorg-input-synaptics
(Ubuntu)
** Description changed:
- Not sure if proper source but when downgrading can't duplicate at will.
- (dr to libutouch-geis1_2.2.3-0ubuntu1, though haven't given a long test
- to inadvertent occurrences
+ Not sure if
Chase - I have this version installed
1.5.0+git20120210-0ubuntu2
Am actually at a bit of a loss as to possible package, initially thought
the utouch libs but after downgrading both the geis & frame1 to 2
versions back was able to eventually cause
Atm have everything up to date & am running with
Additional to note - I was curious if the g-c-c 'tap to click' was
listed in synclient -l so I re-enabled in g-c-c, ran it in a terminal &
will simply scrolling the list the cursor got caught. After a short wait
it released..
--
You received this bug notification because you are a member of Ubunt
Sorry to spam this - starting to think a mouse "click" has nothing to
do with this
By default TapAndDragGesture is set to 1 which here allows 2 & 3 taps
to register (2 tap to open, 3 tap to highlight
So what's happening is a quick 2 tap & cursor move is 'grabbing' , this
lasts till I stop acti
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/934770
Title:
Inadvertant mouse movem
The locked drag is accounting for some of this & yes, users can exit with a
single tap when dragging something.
(though in the past I believe most users of the typical single finger
touchpads would just simply hold button one for extended drags
What it, lthe ocked drag being enabled, isn't acc
On 02/21/2012 02:30 PM, Sebastien Bacher wrote:
>> What it, lthe ocked drag being enabled, isn't accounting for is the
> constant 'locked highlighting' in browsers& text files ala the 2nd
> video
>
> why not? if you click and dnd you select which seems to be what you
> describe?
>
In the context o
This bug wasn't initially just about locked drags nor intended user
actions. It was and still should be considering the poor behavior that
the current settings will produce for common users like myself who have
a basic synaptics touchpad
In that case there are continual unintended highlighting,
Public bug reported:
It's possible that this is an extreme corner case, (my hardware), 8400m
chipsets in general or a bit more widespread.
So i'm opening this report in case it's one of the latter 2
It occurs like this:
After the install or upgrading to the .20 drivers shutdowns/restarts works
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.launchpad.net/bugs/940564
Title:
nvidia-graphics-drivers (295.20-0ubuntu1), is causing failed restarts
& shutdowns
To manage notifications about
This 1st occurred with the upgrade of unity-greeter to unity-greeter
0.2.1-0ubuntu1 though I believe the issue has been identified as being
in lightdm
Unfortunately it's not that straightforward to test reverting back to
that version due to dep changes with g-s-d, ect.
(if one was to install the
Decided to revisit this on a new 2 day old Beta1 install
Was using the .10 drivers from the get go, fully updated regularly, no
restart/shutdown issues.
Updated nvidia-current tonight to the .20, just like clockwork after 3 normal
restarts over the course of an hr. or the 4th one failed.
Again h
Public bug reported:
Quite simply because otherwise performance in the default unity/compiz session
is awful. There is very visible tearing when moving windows, switching
workspaces ect, ect.
Can't see why you'd leave it up to the users to enable thru xorg.conf
ProblemType: Bug
DistroRelease:
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1019131
Title:
vsync should be enabled by default for nvidia
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+sourc
Public bug reported:
As described, won't install on 12.10 A2 unless changed, then installs,
works fine
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: nvidia-current 302.17-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-2.2-generic 3.5.0-rc4
Uname: Linux 3.5.0-2-generic i686
NonfreeKernelModul
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.launchpad.net/bugs/1020219
Title:
control file has depend on "xorg-video-abi-11", should be "xorg-video-
abi-12"
To manage notifications about th
marking invalid as see new build going on now
** Changed in: nvidia-graphics-drivers (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.launchpad.net/bugs/102021
The 304.43 release should resolve this, hopefully also includes the Xorg
crash on 3d (unity, gnome-shell
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.launchpad.net/bugs/1037896
Title:
Starting
With a little 'help' Add. drivers, (ubuntu-drivers-common) will quite
happily list & install nvidia-current or nvidia-current-updates on a
fresh 12.10 install
** Attachment added: "Screenshot from 2012-09-03 03:36:41.png"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1
I have to disagree - they work fine, have seen no recent complaints & can use
them here with no issue as are many others.
(for reasons totally unrelated to nvidia-current performance.compatibility i
choose to use nouveau
The package list for nvidia-current has this for Depends
Depends: x11-comm
*** This bug is a duplicate of bug 1043518 ***
https://bugs.launchpad.net/bugs/1043518
** This bug has been marked a duplicate of bug 1043518
live cd is unusable due to video degradation with the splash boot option
enabled
--
You received this bug notification because you are a member of
Can report vsync is auto-enabled on nvidia-8400m (dell
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.net/bugs/1019131
Title:
vsync is disabled by default in nouveau
To manage noti
With todays updated the driver provided by proprietary-video-improvements PPA
is working fully w/ glx, xv and full use of compiz
Will hopefully be able to do a fresh A2 install next week and just use the
lucid packages
--
[lucid] nvidia-glx can't work with new xorg 7.5
https://bugs.launchpad.ne
What I have noticed with the new package updates is that libgl1-mesa-dev
is installing a broken link '/usr/lib/libGL.so'
While it hasn't affected anything obvious in use, it certainly has in
some source builds.
Rebuild of vlc 1.1 and 1.0.4, which previously worked now fail on -lGL
While a GL-LI
Public bug reported:
libgl1-mesa-glx installs libGL.so.1 and libGL.so.1.2 to /usr/lib/mesa
but the link libgl1-mesa-dev installs to /usr/lib is broken
Came up while doing rebuilds of vlc1.1 and 1.0.4 which now fail on -lGL
Removing and creating a new link resolved the vlc builds and allowed v
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/37665538/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/37665539/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/37665540/Dependencies.txt
** A
See it's been fixed in new libgl1-mesa-dev package
--
libgl1-mesa-dev installs a broken link in /usr/lib
https://bugs.launchpad.net/bugs/505359
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in ubuntu.
sorry- see an update just now to libgl1-mesa-dev has squared that away
--
[lucid] nvidia-glx can't work with new xorg 7.5
https://bugs.launchpad.net/bugs/494166
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-173 in ubuntu.
Well yes there still can be an issue when building sources off of.
A series of builds of vlc 1.0.4, vlc 1.1-git and mplayer showed
vlc 1.1 is fine as things stand
Both vlc 1.0.4 and mplayer, while finding the headers, will fail to link
to libGL.so
The fix there (as things stand) is to create a n
In regards to the release notes ( don't see how to file a bug there
"then configure your xorg.conf with:
sudo nvidia-config"
That's actually caused some confusion, should be
sudo nvidia-xconfig
--
[lucid] nvidia-glx can't work with new xorg 7.5
https://bugs.launchpad.net/bugs/494166
You rec
"@Doug
Fixed, thanks."
I hope I didn't mistake 'release notes' for "known issues" here, where some
have be going from ubuntu forums, ect.
http://www.ubuntu.com/testing/lucid/alpha2#Known%20issues
By the way from fresh installs or even booting to live cd env, it's
working quite well as instructe
Public bug reported:
Binary package hint: xserver-xorg-input-synaptics
After the upgrade today of this and the other xorg/xserver packages there is no
function in synaptic touchpad
(the mouse keys and external (usb mouse) work fine
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: xserver-
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in ubuntu.
https://bugs.launchpad.net/bugs/724051
Title:
upgrade to 1.3.99+git20110116.0e27ce3a-0ubuntu4 breaks touchpad
attaching evtest (not sure if any use) and the xinput, well no need, nothing
happens, ie.
doug@doug-XPS-M1330:~$ xinput test "SynPS/2 Synaptics TouchPad"
that's it
** Attachment added: "evtest"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/724051/+attachment/186
What is a bit weird - did a reboot, re-ran evtest and got this
doug@doug-XPS-M1330:~$ sudo evtest /dev/input/event7
Input driver version is 1.0.1
Input device ID: bus 0x19 vendor 0x0 product 0x6 version 0x0
Input device name: "Video Bus"
Supported events:
Event type 0 (Sync)
Event type 1 (Key)
Public bug reported:
the new nvidia-current is causing a 300% increase in memory use at login as
compared to previously and or as currently with nouveau 3d drivers.
While not a big deal on machines with 2+GB ram on older machines with 1 GB it
does represent a bit of an issue.
The increases are p
** Attachment added: "mesa3d_1GB.log"
https://bugs.launchpad.net/bugs/725434/+attachment/1872379/+files/mesa3d_1GB.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in ubuntu.
https://bugs.launchpad.net/bugs/725434
** Attachment added: "nvidia_3GB.log"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/725434/+attachment/1872402/+files/nvidia_3GB.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in ubuntu.
h
** Attachment added: "nvidia_1GB.log"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/725434/+attachment/1872400/+files/nvidia_1GB.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in ubuntu.
h
** Attachment added: "mesa3d_3GB.log"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/725434/+attachment/1872401/+files/mesa3d_3GB.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in ubuntu.
h
>If you uninstall nvidia and go back to nouveau, does the memory go
back down to the low levels?
Yes - the 2 mesa3d "1GB" logs attached are reflective of both prior to
installing nvidia-current and removing nvidia-current and returning to
mesa3d drivers (the "mesa3d_1GB log orig. attached to repo
Went ahead and did an A2 install, reverted xserver to 1.9, installed
nvidia-current 260.19.21-0ubuntu2
(only upgrade was to the kernel to get away from the udev - kernel panic that
was quite likely with the hardware here.
Memory use at login was pretty much normal, both for mesa3d and then with
This is the grouping that after install causes the increased mem at login
(current xserver, nvidia-current, ect.
Don't have time to ck. reverting individually and can't be sure if there is any
other relationship to upgrades previous to this group. (wasn't a group that
seemed clearly obvious
confirmed here that the libcairo2 upgrade is causing the mem increase w/
nvidia
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in ubuntu.
https://bugs.launchpad.net/bugs/725434
Title:
something causes a significant 'ac
** Attachment added: "a3mem_cairo-revert-1GB"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/725434/+attachment/1886363/+files/a3mem_cairo-revert-1GB
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-driv
** Summary changed:
- something causes a significant 'across the board' memory use increase with
-nvidia loaded
+ something (libcairo2) causes a significant 'across the board' memory use
increase with -nvidia loaded
--
You received this bug notification because you are a member of Ubuntu-X,
wh
Just to see did go ahead and package/install the current 1.10.2 source
without gl enabled, it brought the mem use at log in back to the
expected amount. (246 vs 602MB, unity login on this machine, slightly
greater diff on the affected p4 1GB
As it stands now, machines w/ 2GB or more doesn't muc
I've been using the cairo -1.10.2 redone with '--enable-gl' removed and
adjusted symbols for 4 or 5 days now and can say absolutely no issues seen
And as noted before mem use is now as expected
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Jeremy Bicha wrote
> Any unity/compiz memory leaks are different issues and should be a new bug ...
bug #720446
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.launchpad.net/bugs/725434
Title:
Nv
*** This bug is a duplicate of bug 768178 ***
https://bugs.launchpad.net/bugs/768178
The orig. reporter here is using an fx 5200 - adjusted the dupe to the
proper bug for THAT card and the 173.XX nvidia drivers
** This bug is no longer a duplicate of bug 771788
nVidia driver activated an
Well , 11.10 has gone back today to using the --enable-gl option in cairo, so
this again is a concern for nvidia users , particularly 1GB machines
Add in the still active small per use mem leaks in unity/compiz and these
machines will quickly become unusable.
** Tags added: oneiric
** Tags remov
101 - 200 of 220 matches
Mail list logo
