Montblanc, thank you for reporting this bug to Ubuntu. Saucy reached EOL on
July 17, 2014.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Is this an issue on a supported release?
** Changed in: xorg (Ubuntu)
Importance: Undecided = Low
**
Raynold C. Peterson, thank you for reporting this and helping make Ubuntu
better. Thank you for reporting this bug to Ubuntu. Saucy reached EOL on July
17, 2014.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Is this an issue in a supported release?
Sorry to take so long getting back to this. The affected PC is usually
used as my media center but I've now been able to move it into my
testing suite so hopefully once 14.04.2 milestone testing is out of the
way I'll be able to respond more quickly and efficiently.
Regarding the screen
wentworth, thank you for reporting this and helping make Ubuntu better. Thank
you for reporting this bug to Ubuntu. Saucy reached EOL on July 17, 2014.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Is this an issue in a supported release?
** Tags
Public bug reported:
After locking the screen or suspending my computer, I cannot re-login.
Though my password is correct (there ist no verification problem shown),
the login screen does not disappear, but requests my password again.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xorg
** Tags added: bios-outdated-a05
--
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/1279586
Title:
Screen corruption Unity bar slothful
To manage notifications about this bug go to:
I was encountering some issues installing 14.04.1 which I'll get into
later, but for now I moved on to testing 14.04.2, this one installed w
/Ubuntu-GNOME 14.04.2 LTS Trusty Tahr - Release amd64 (20150203), and
while 3.16.0-30-generic was affected I pulled 3.16.0-31-generic from
trusty-proposed
** Tags added: bios-outdated-1903
--
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/949958
Title:
Full screen video corruption on nvidia betwen lightdm and desktop
To manage notifications about
Thanks for taking your time to report this issue and help making Ubuntu
better.
I see that the current version in Vivid is 1:7.4.0-2ubuntu2 which
indicates it has some Ubuntu-specific patches. Someone will likely have
merge those with the latest package from Debian.
--
You received this bug
*have to merge
Sorry about the missing word
** Tags added: upgrade-software-version vivid
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/1421601
Title:
Please update
David Oxland, thank you for reporting this and helping make Ubuntu better.
Saucy reached EOL on July 17, 2014.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Is this an issue in a supported release?
** Changed in: xorg (Ubuntu)
Importance:
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2015-0255
--
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/1420643
Title:
X.Org Server 1.17.1 Released To Fix
** Changed in: slim (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xdm in Ubuntu.
https://bugs.launchpad.net/bugs/891793
Title:
Login with USB key or smart card
To manage notifications about this bug go
@ Tim Lunn,
This is totally unrelated, but to be certain that Vivid is working
properly w/3.18.0-13-generic I've been using it to post all of these
messages and on the last boot apport presented me with a gdm error so I
accepted the automated reporting which is bug #1421991. Poorly written
for
It turns out that both 14.04 and 14.04.1 are affected by this bug. I had
to look in the installer log to see what version I'd begun with (and
have been running on that box as my stable OS) = Ubuntu 14.04 LTS
Trusty Tahr - Alpha i386 (20140129). So I was undoubtedly able to
install Trusty at that
** Summary changed:
- İntel g41 ekran dalgalanma sorunu
+ Ubuntu 14.10 [drm:i915_stolen_to_physical] *ERROR* conflict detected with
stolen region
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
Ajuntament, thank you for reporting this and helping make Ubuntu better. Saucy
reached EOL on July 17, 2014.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Is this an issue in a supported release?
** Tags added: bios-outdated-1.26
** Changed in:
Hồng Quân, could you please capture the crash via
https://help.ubuntu.com/community/DebuggingSystemCrash ?
** Changed in: xorg (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
Andrew Piziali, is this still an issue for you?
** No longer affects: linux-kernel-64 (Ubuntu)
** Tags added: bios-outdated-1.19
** Changed in: xorg (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
Lance, this is getting a little confusing to follow, can you file separate bugs
for the corruption and lockups above.
The original nouveau.config=NvMSI=0 bug should be fixed in vivid now? is it
fixed in trusty 14.04.2?
--
You received this bug notification because you are a member of Ubuntu-X,
** Tags added: bios-outdated-4891
** Tags removed: bios-outdated-4891
** Tags added: bios-outdated-4801
--
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/1267562
Title:
Windows open as blank
I just got this error after playing Django unchained (the DVD) with
VLC:
```text
VLC media player 2.2.0-pre2 Weatherwax (revision 2.2.0-pre1-15-g5178b24)
VLC version 2.2.0-pre2 Weatherwax (2.2.0-pre1-15-g5178b24)
Compiled by buildd on kapok.buildd (Sep 5 2014 01:57:42)
Compiler: gcc version
Deny D., Raring reached EOL on January 27, 2014.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
If this problem is reproducible with a supported release, please file a
new report following https://wiki.ubuntu.com/DebuggingProcedures .
** Changed in:
Sandy Patterson, thank you for reporting this and helping make Ubuntu better.
Saucy reached EOL on July 17, 2014.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Is this an issue in a supported release?
** Tags added: needs-full-computer-model
**
cyberalex4life, thank you for reporting this and helping make Ubuntu better.
Please execute the following command, as it will automatically gather debugging
information, in a terminal:
apport-collect 1245371
When reporting bugs in the future please use apport by using 'ubuntu-bug' and
the name
i can;t do anything with this os!
** Changed in: flightgear (Ubuntu)
Assignee: (unassigned) = sidlwebb (sidlwebb)
--
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/1079011
Title:
stellarium
Just tried going the other way, just setting
[XDMCPServer]
enabled=true
on the 'workstation' computer and attempting to login from the server.
got exactly the same result.
Something else is missing and I'm not sure what that is.
--
You received this bug notification because you are a member
No. I have not seen this failure during the last eight weeks where, as
mentioned earlier, I am no longer using the direct rendering function of
my video card.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
I am having this problem on a desktop machine. I have to click three
times in a row to register a mouse click. Xubuntu fully upgraded. I
have a genuine Microsoft mouse so that it is fairly generic. I am using
an NVidia graphics card. xdiagnose shows no errors
I am finding that
Hi Tim,
As far as I can tell ATM the only difference in most of these
crashes/freezes/screen-corruptions is the frequency with which they
occur and the screen color depending on what point during boot and/or
operation the freeze occurs.
Like this is the pic I included with original bug report:
E: Unable to correct problems, you have held broken packages.
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by
held packages.
E: Unable to correct dependencies
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by
held packages.
E: Unable to
31 matches
Mail list logo
