Public bug reported:
Upon running updates ( which included many related to systemd - so
that's my best guess as to the right package - feel free to reclassify )
I can't get an external monitor to actually receive a signal from my
laptop anymore. I've tried both displayport and HDMI with no luck.
Yes, the bug was filed right after the failure. I plugged in the
monitor cable and ran ubuntu-bug after nothing had happened ( with the
cable still plugged in ).
I just tried running "sudo apt-get install --reinstall systemd" and
rebooting and the issue is still there.
I would be very surprised
I should add that I've been running on vivid for about a month now - so
there could be some weirdness happening with all of the updates (
including the initial move to systemd ). I'm going to try a clean
installation and see if I can still reproduce this to make sure that I'm
not wasting anyone's
OK - On a completely clean installation of Vivid with up-to-date
packages the issue still persists.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1438306
Title:
External monitors receive no signal
However - it appears that HDMI is now working - only the display port is
not.
** Summary changed:
- External monitors receive no signal
+ External monitors receive no signal over DisplayPort
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
Ugh - really funky hardware issue. Sorry for the inconvenience.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1438306
Title:
External monitors receive no signal over DisplayPort
To manage notifica
** Changed in: xorg-server (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1438306
Title:
External monitors receive no signal over DisplayPort
To manage notific
Hey Don -
When your computer boots up, go ahead and make sure an Ethernet cable is
plugged in. Then hold down control and alt and press "F1" - you'll be prompted
to login with the user account you created. Then run this command exactly:
sudo apt-get install linux-headers-generic
It will promp
And my Unity version:
$ apt-cache policy unity
unity:
Installed: 7.2.2+14.04.20140714-0ubuntu1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1305586
Title:
Lock screen is unusable when some windo
This also happens in Chromium.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1305586
Title:
Lock screen is unusable when some windows have a keyboard/mouse grab
To manage notifications about this b
I'm still seeing this issue when Google Chrome is the last open ( and
focused ) application upon suspend. When I typed my password in it
didn't work - so I did the "switch account" hack and logged in - and
found my password sitting in the Chrome address bar.
I've installed the latest proposed upd
This looks similar to this bug:
https://bugs.launchpad.net/unity/+bug/1305586
However - I've found that another issue is that whatever application has
held on to the cursor, you will end up typing your password directly
into. Google Chrome and Chromium seem to be the two most popular
culprits.
-
This seems to happen most frequently with Google Chrome and Chromium -
or at least, they're two easy culprits to identify. :)
Seems related to the following:
https://bugs.launchpad.net/unity/+bug/1305586
I'm not sure if the fix in that bug is what caused this or if another
issue arose elsewhere.
Confirmed that it occurs with both UXA and SNA - tested with xorg-edgers
PPA on raring.
xserver-xorg-video-intel:
Installed: 2:2.20.18-0ubuntu1
Candidate: 2:2.20.18-0ubuntu1
Version table:
*** 2:2.20.18-0ubuntu1 0
500 http://us.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages
Ryzom is what I installed to make this start as well - now the crash
reports show up any time I start up the computer. The only way I've
found to get rid of them is a fresh install ( obviously works ) -
reporting the error seems to crash and just tries to report it again.
--
You received this bu
I fixed this by re-enabling unity and open GL within CCSM - however it
seems that every key binding except for those to launch and close the
dash has been lost.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
Sorry - I take that back - I had simply not re-enabled some of the
included default plugins ( such as desktop wall ). Re-enabling them
seemed to do the trick.
Interestingly enough - re-enabling the workspaces feature within
Settings -> Appearance didn't work, as I had to manually do it through
CC
Seems to be only related to nvidia-experimental, however there's a lot of
little fixing required to get back to where you should be:
1) Remove nvidia-experimental-
2) Reboot and login ( should put you at a Desktop w/o Unity )
3) Launch CCSM - I needed to create a desktop shortcut to do so... i.e.:
Yes - this worked fine in 11.04 - as far as we can tell the issue
appears to be with LightDM ( which was not present in 11.04 ).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/873495
Title:
LightDM f
This bug seems to happen for me both during the Installer and Live
Session - but also post installation. I'm not sure if it has anything
to do with my graphics setup - I'm on nVidia and using proprietary
graphics.
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
" Is configuring to suspend, closing power configuration, opening it
again, setting to never ... able to solve the issue ?"
That doesn't work for me - I've tried just about every combination of
opening and closing the power settings.
--
You received this bug notification because you are a member
Also affects nvidia proprietary xserver.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/880948
Title:
Window relocates to other display after resize.
To manage notifications about this bug go to:
ht
I tested 3.2.0-25.40 on a duplicate bug and it worked.
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/906269
I also just verified that Google Maps ( the WebGL version ) works
without issue in Chrome with that same kernel.
--
You received this bug notification because you
That fixes it for me!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/906269
Title:
[sandybridge-m-gt2+] GPU lockup render.IPEHR: 0x7a02
To manage notifications about this bug go to:
https://bug
Just tested 3.2.0-25-generic from precise-proposed and it worked as
well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/906269
Title:
[sandybridge-m-gt2+] GPU lockup render.IPEHR: 0x7a02
To ma
You will have to submit them to REVU. Go on IRC and join #ubuntu-motu
and they can direct you to someone who will walk you through it.
Additionally, you can check out:
https://wiki.ubuntu.com/MOTU
On 9/4/06, Jordy Potman <[EMAIL PROTECTED]> wrote:
> I have recently rebuild the following debian-m
Public bug reported:
The MythTV version .19 has been released officially for over 6 months
and includes tons of new features as compared to the currently supported
version .18 in ubuntu repos. This isn't a case so much of having the
bleeding-edge release as supporting what is currently stable and
** Bug 52659 has been marked a duplicate of this bug
--
Update to .19
https://launchpad.net/bugs/32169
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
*** This bug is a duplicate of bug 32169 ***
** This bug has been marked a duplicate of bug 32169
Update to .19
--
MythTV Version .19 Support
https://launchpad.net/bugs/52659
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Mario: have you made any progress on creating these packages? I'm
willing to step in and start building them packages so that they can be
tested and released. I think it's important that this be included in
Edgy at the very least, if not for updating dapper repos (since they
will be "officially
Mario: have you made any progress on creating these packages? I'm
willing to step in and start building them packages so that they can be
tested and released. I think it's important that this be included in
Edgy at the very least, if not for updating dapper repos (since they
will be "officially
Sorry for the duplicate comment. Hit refresh on accident.
I'll talk to mdz (previous maintainer) and see if I can start to headup
building fresh .19 packages for the repos.
--
Update to .19
https://launchpad.net/bugs/32169
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.
mdz, I was just about to go find you on IRC to talk about this...
thanks for the heads up. If you need to ask or tell me something I'm
usually in #ubuntu-motu and #ubuntu-devel in terms of dev channels as
FunnyLookinHat.
--
Update to .19
https://launchpad.net/bugs/32169
--
ubuntu-bugs mailing l
I'm gonna bump this bug with pretty much the same problem.
I have a SATA and IDE drive. And although the SATA is defined as hd0
grub keeps reverting it back to hd1... I installed to hd0 though so it
should have recognized that.
I have a feeling this issue has to deal with converting the hda ->
Sorry, I can't say for sure. I don't have Xubuntu installed currently
and don't have any spare hardware to do do so. We can probably close
this bug as stale.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
*** This bug is a duplicate of bug 60319 ***
https://bugs.launchpad.net/bugs/60319
--
Update to .20
https://bugs.launchpad.net/bugs/32169
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.u
Public bug reported:
Suspend seems to work correctly, but when I open the laptop back up
resume results in a black screen. Interestingly, I can switch to TTY1
and see LightDM, and TTY3 and get a console... switching back to TTY2
shows me the black screen.
I can pull logs from a relevant place if
37 matches
Mail list logo
