Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Thanks for taking the time to report this bug and helping to make Ubuntu
better. Your bug report is more likely to get attention if it is made in
English, since this is the language understood by the majority of Ubuntu
developers. Additionally, please only mark a bug as "security" if it
shows evid
I am also seeing this on a similar system - Lenovo Thinkpad X260 - and
for me this occurs when I boot with the laptop docked with two external
monitors connected. If I boot without it docked then it boots fine - but
when docked Xwayland seems to always crash on startup.
--
You received this bug n
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
https://bugs.launchpad.net/bugs/1779983
Title:
new nvidia driver causes system failure
To manag
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1779622
Title:
issue is regarding boot hanging between work
To manage notifications ab
I can see from the attached logs there are file-system errors (likely
due to incomplete shutdowns in the past) but I am surprised by the
presence of XFS and QNX file-system drivers both being loaded - can you
describe this system in more details - also any details you can provide
about the crash wo
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately we can't fix it, because your description
didn't include enough information. You may find it helpful to read 'How
to report bugs effectively'
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd
*** This bug is a duplicate of bug 1784883 ***
https://bugs.launchpad.net/bugs/1784883
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1784883, so it is being marked as such. Please look
*** This bug is a duplicate of bug 1784883 ***
https://bugs.launchpad.net/bugs/1784883
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a
*** This bug is a duplicate of bug 1784883 ***
https://bugs.launchpad.net/bugs/1784883
Please try to avoid creating duplicate bug reports for the same issue.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launch
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately we can't fix it, because your description
didn't include enough information. You may find it helpful to read 'How
to report bugs effectively'
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately we can't fix it, because your description
didn't include enough information. You may find it helpful to read 'How
to report bugs effectively'
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd
Thank you for using Ubuntu and taking the time to report a bug. Your
report should contain, at a minimum, the following information so we can
better find the source of the bug and work to resolve it.
Submitting the bug about the proper source package is essential. For
help see https://wiki.ubuntu.
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Thank you for using Ubuntu and taking the time to report a bug. Your
report should contain, at a minimum, the following information so we can
better find the source of the bug and work to resolve it.
Submitting the bug about the proper source package is essential. For
help see https://wiki.ubuntu.
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
I reviewed vulkan-loader version 1.1.101.0-2_amd64 as checked into
disco. This shouldn't be considered a full security audit but rather a
quick check of maintainability.
- No CVE history in our database
- vulkan-loader provides support for loading the main vulkan library,
handling layer and driv
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
More info here: http://nvidia.custhelp.com/app/answers/detail/a_id/3109
--
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/979307
Title:
/dev/nvidia* is world writable
To manage
@Chase - any chance this may get fixed (and hence reenabled) for
clickpads which don't have a physical right button (such as all the ones
on Apple laptops?) As it is a shame to be so close to having good
support for such devices now only to have it removed. I agree that
maintaining two / three fing
I see this sometimes on Jaunty - 2.6.28-12-generic #43-Ubuntu SMP Fri
May 1 19:31:32 UTC 2009 x86_64 GNU/Linux with nvidia-glx-180 - I can
semi-regularly reproduce it using OpenOffice or sometimes vim or
emacs... this is with compiz enabled. Haven't yet had a chance to see if
I can reproduce it usi
Attached output of lspci -vvnn on my machine (MacBook Pro 5,1 with
Nvidia 9600M GT)
** Attachment added: "Output of lspci -vvnn"
http://launchpadlibrarian.net/27490454/lspci.txt
--
display corruption with nvidia driver
https://bugs.launchpad.net/bugs/281519
You received this bug notification
@Per Angstrom - I am seeing exactly the same corruption on my MacBook
Pro 5,1, with an NVIDIA 9600M GT GPU running latest Lucid with Nvidia
195.36.03 - I noticed that Nvidia have released an updated driver
195.36.08 (ie .03 -> .08) - I will try and test this later when I get
home.
@Bryce: Are you
Just noticed 2 other comments confirming similarly back in bug #488720 -
ie. comments 19, 20 and 21 in that bug report suggest that reverting to
the old 190.53 driver should fix this - will also test this and report
back.
--
[lucid regression] random graphics effects after resume from suspend to
@Noel: It is the latest stable release -
http://www.nvnews.net/vbulletin/showthread.php?t=122606 - 190.53 is the
old stable release.
Nothing in particular makes me think it could help solved this except
maybe 'Fixed a bug that caused screen corruption after an application
released a GLX_NV_present
Downgrading to nvidia-current_190.53-0ubuntu14 unfortunately doesn't fix
this for me - see attached screen shot and notice white blocks behind
panel and docky windows.
At this stage since the release notes say:
Because of the new alternatives system used for nvidia driver packages,
the nvidia ins
Isn't this just a dupe of bug #423694
--
[i965gm] "Session active, not inhibited, screen idle" notification after screen
blacks out during normal operation
https://bugs.launchpad.net/bugs/451194
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserv
I think this affects me too on latest Karmic since my screen backlight
never goes off even though I have set gnome-power-manager to put it to
sleep after 5 minutes - running latest Karmic updates on NVIDIA 9600M GT
with proprietary nvidia-glx-185 drivers installed from official ubuntu
repo. Any cha
This seems to be a serious regression to me - bug #426765 (which seems
to be a dup on this) suggests that commit
http://cgit.freedesktop.org/xorg/xserver/commit/?id=c1d901d723c3bee523736eacc15b44a7dff484fe
needs to be applied to xorg-server to fix this - so I suggest this bug
should be marked valid
Is this a dup of #413168
--
DPMS events reset event timer causing gnome-power-manager to exit idle state
almost immediately after a blank event
https://bugs.launchpad.net/bugs/426765
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in u
This occurs intermittently for me - sometimes I boot successfully and X
starts automatically, sometimes I need to do CTRL-ALT-F7 to get it to
come up..(and sometimes my machine rarely gets stuck and X doesn't come
up at all...)
--
X doesn't start automatically any more after installing restricted
@Bryce: I am pretty sure the Ubuntu xorg-server is still missing one of
the fundamental upstream patches to fix this issue - as Ive said on a
number of other bug reports which report this issue still, the following
patch is still needed:
http://cgit.freedesktop.org/xorg/xserver/commit/?id=c1d901d7
I've uploaded a patched version of xorg-server to my PPA which should
fix this if you want to test it:
https://launchpad.net/~alexmurray/+archive/ppa
--
Karmic upgrade not shutting off backlight after time
https://bugs.launchpad.net/bugs/413168
You received this bug notification because you are
Yep, I've also got the same patch applied in my PPA and can confirm this
fixes the screen blanking.
--
Screen randomly goes off in karmic
https://bugs.launchpad.net/bugs/397839
You received this bug notification because you are a member of Ubuntu-X,
which is the registrant for xserver-xorg-driver
*** This bug is a duplicate of bug 413168 ***
https://bugs.launchpad.net/bugs/413168
I've uploaded a patched version of xorg-server to my PPA which should
fix this if you want to test it:
https://launchpad.net/~alexmurray/+archive/ppa
--
[karmic] display doesn't go to DPMS sleep
https://bug
This patch was recently applied to xorg-server in Ubuntu ( (see
https://bugs.launchpad.net/ubuntu/+source/gnome-power-
manager/+bug/413168/comments/19) and it is waiting approval by release
team I think - https://lists.ubuntu.com/archives/karmic-
changes/2009-September/009738.html
--
Apply screen
Just wanted to say Nvidia works fine for me under Karmic with compiz on
my MacBook Pro 5,1:
lspci -v:
2:00.0 VGA compatible controller: nVidia Corporation G96 [GeForce 9600M GT]
(rev a1)
Subsystem: Apple Computer Inc. Device 00a9
Flags: bus master, fast devsel, latency 0, IRQ 23
I've started getting this in the last few days recently.. not too sure
what (ie xorg-server or maybe gnome-power-manager) has changed
recently... was working great until this.
--
"Session active, not inhibited, screen idle" notification after screen blacks
out during normal operation
https://bug
@Milos - the patched version of xorg-server in my PPA has been
superseded by the official Ubuntu package, so there is no need to use my
PPA (hence why it doesn't offer any upgrade because the version in the
official PPA is newer). For me this issue is fixed by the official
package in the Ubuntu rep
Might be worthwhile testing the just released prerelease Nvidia
driver195.36.15 since it may fix the crash on resume and the fan
problems as well, from
http://www.nvnews.net/vbulletin/showthread.php?t=148947
Fixed a bug that caused the X server to crash when rendering occurred while the
X server
Have noticed that now I don't get corruption after resuming (after a fix
to pm-utils I think) but instead X crashes upon resuming, leaving me
staring at the gdm login screen.
Just noticed Nvidia just released an updated driver: 195.36.15 which may
fix this second issue, from
http://www.nvnews.net/
195.36.15 was just released which should fix this:
http://www.nvnews.net/vbulletin/showthread.php?t=148947
--
fan speed issue in 195.36.08 and 195.36.03 (may potentially destroy the GPU)
https://bugs.launchpad.net/bugs/533224
You received this bug notification because you are a member of Ubuntu-
@mbawsa: The 195.36.15 driver which I linked to above fixes the gpu fan
issue and so should be safe, as is the 190.53 driver.
--
[lucid regression] random graphics effects after resume from suspend to RAM
https://bugs.launchpad.net/bugs/510004
You received this bug notification because you are a
** Summary changed:
- Please, update to nvidia 195.36.14 driver to fix fan problems!
+ Please, update to nvidia 195.36.15 driver to fix fan problems!
** Description changed:
the current nvidia driver in lucid is 195.36.08 problem reported by
- developers of nvidia to fan control, update releas
*** This bug is a duplicate of bug 546393 ***
https://bugs.launchpad.net/bugs/546393
Looks like this was fixed before Maverick final was released (see bug
#546393)
** Changed in: xserver-xorg-video-nouveau (Ubuntu)
Status: New => Fix Released
** This bug has been marked a duplicate of
I can confirm the fix resolves this bug for me - thanks Daniel, nice
work. This was really bugging me since I use 3-finger click to paste all
the time so its great you fixed it.
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Status: Triaged => Confirmed
--
You received this bug noti
Ahh thanks for the heads up on bug statuses - sorry bout that.
--
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/754000
Title:
3 finger touch interferes with 3 finger click
@quequotion - I would say this is more likely a race condition between
the loading of the nvidia kernel module and the starting of X / gdm -
basically I think what is happening is that the module is loaded but X /
gdm starts up before it has finished initialising the hardware and hence
the X nvidia
*** This bug is a duplicate of bug 459639 ***
https://bugs.launchpad.net/bugs/459639
** This bug is no longer a duplicate of bug 532436
nvidia driver sometime does not load at boot
** This bug has been marked a duplicate of bug 459639
X server starts randomly in failsafe when starting fr
*** This bug is a duplicate of bug 459639 ***
https://bugs.launchpad.net/bugs/459639
This looks like a duplicate of bug #459639 marking as such to clear
things up
** This bug has been marked a duplicate of bug 459639
X server starts randomly in failsafe when starting from cold boot
--
nv
Public bug reported:
Binary package hint: xserver-xorg-video-nouveau
Maverick beta desktop livecd (amd64) fails to boot unless 'nomodeset' is
specified on my MacBook Pro 5,1. Boot hangs with a flashing console
cursor straight after the boot options menu from the livecd.
Also once installed boot
** Attachment added: ".proc.driver.nvidia.cards.0.txt"
https://bugs.launchpad.net/bugs/631513/+attachment/1549584/+files/.proc.driver.nvidia.cards.0.txt
** Attachment added: ".proc.driver.nvidia.registry.txt"
https://bugs.launchpad.net/bugs/631513/+attachment/1549585/+files/.proc.driver.n
** Changed in: xorg-server (Ubuntu)
Assignee: (unassigned) => Leonidas S. Barbosa (leosilvab)
--
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/2101897
Title:
no windows open in Xorg af
68 matches
Mail list logo
