*** This bug is a duplicate of bug 541511 ***
https://bugs.launchpad.net/bugs/541511
Maybe you didn't hold shift down early enough Vilius? Works for me. I
can then choose from two kernels. I choose the earlier one, and not the
recovery mode options. Choosing a recovery mode option means I then
*** This bug is a duplicate of bug 541511 ***
https://bugs.launchpad.net/bugs/541511
The problem appears to have been resolved with the latest kernel available via
'proposed updates' lucid-proposed. It least - it has for me, so now I have
undone as many of the workarounds as I can recall app
*** This bug is a duplicate of bug 541511 ***
https://bugs.launchpad.net/bugs/541511
Spoke too soon (see #80). Cheese Webcam Booth crashes the system with my
particular webcam - whereas it didn't with the workarounds (eg xx.x .20 kernel
and 'mainline' kernel - or was that 'mainstream', I for
Sorry - commented in the duplicate bug... Latest proposed update
(lucid-proposed) seems to fix the main problem of non-bootability due to black
screen; but it does not fix the (associated?) problem of Cheese Webcam Booth
crashing the system. At least Lucid Linux version xx.x.22 is now usable wit
*** This bug is a duplicate of bug 541511 ***
https://bugs.launchpad.net/bugs/541511
Yes that's my experience with the mainline kernel. Wish I knew what it
was, though. Information on what it represents seems hard to come by if
you are not a fully fledged geek.
--
[i855] 10.04 rc boots into
Or... Hat tip to Alban #54 over at
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
intel/+bug/568779 ... but slightly modified because it's now rc6. If you
have some kind of Lucid desktop, you won't need 1-4, so start at 5.
Alban wrote:
"1. After power on your PC, press shift (keep
Woops! My error - where you see 'rc5' still in 8. above, replace
with 'rc6'
--
MASTER: [i855] GPU lockup (apport-crash)
https://bugs.launchpad.net/bugs/541511
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
@Thoer (#162 etc/usw).
Many, many thanks for that effort.
Slight bug initially evident on my i8xx machine, in that application (eg
Firefox) may open without showing the app bar at the top containing its
minimize, maximize and close symbols, and closing under file-close still
leaves the app showi
@Brian Rogers (#145) - I may be misunderstanding the word 'distro', but
Peppermint Linux (otherwise ugh-for-me) is not affected (kernel 2.6.32-22, if I
remember correctly) and rcs 5,6.7 of Mainline Lucid version is also not
affected - at least, they work fine with my i855 display.
@Steve Langase
Public bug reported:
DK
ProblemType: Crash
Architecture: i386
Chipset: i855
Date: Tue Mar 9 19:24:45 2010
DistroRelease: Ubuntu 10.04
DkmsStatus: Error: [Errno 2] No such file or directory
DumpSignature: bde775a3c9602485047915eeabf64f1f
ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/40635202/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/40635203/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/40635204/Dependencies.txt
** A
Public bug reported:
Binary package hint: xserver-xorg-video-intel
No further information
ProblemType: Crash
Architecture: i386
Chipset: i855
Date: Wed Mar 10 11:55:22 2010
DistroRelease: Ubuntu 10.04
DkmsStatus: Error: [Errno 2] No such file or directory
DumpSignature: f7711baaec99d519329573a73
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/40693180/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/40693181/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/40693182/Dependencies.txt
** A
I'm also experiencing this exact bug.
Upgrading from 16.10 to 17.04 did not display the problem, but fresh install of
Ubuntu 17.04 does
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654918
Title:
Regret to inform that an upgrade from 16.04 is also displaying the bug.
Reduced to using Google DNS on ipv4 (8.8.8.8) in order to work around it
David
On 14 Apr 2017 14:11, "David Oser" <1654...@bugs.launchpad.net> wrote:
I'm also experiencing this exact bug.
Upgrading fr
Actually there seem to be two related or unrelated issues. One seems to be
purely DNS and the other Network Manager... Dunno. My original issue was
Network Manager. Now ok for no reason i can see. The more sticky one with
my latest upgrade was no problem linking to my WiFi but no internet when
lin
Yup... Me, I'm reverting back to 16.10
D
On 17 Apr 2017 15:51, "harry brijs" wrote:
> i installed from iso file
> internet is avail upon goodwill of the system
> or whatever.
> It comes but most of the time it does not stay.
> I did not yet correlate this behaviour
> 2
>
> --
> You received this
Fortunately I had retained 17.04 full installation on a USB stick.
Downloaded new update via Google DNS on IPV4, then deleted 8.8.8.8 and
tested. Seems to be working. So far so good Thanks for the heads-up
hrvooje!
Best
David
On 18 April 2017 at 07:09, hrvooje <1654...@bugs.launchpad.net> wrot
n my
main (newer uefi) machine until the issue is fully resolved.
On 18 April 2017 at 10:22, David Oser wrote:
> Fortunately I had retained 17.04 full installation on a USB stick.
> Downloaded new update via Google DNS on IPV4, then deleted 8.8.8.8 and
> tested. Seems to be working. So f
Temporary workaround which seems to work most of the time (though,
'timing' - as you are suggesting - sometimes is an issue, requiring a
couple of 'sudo apt update' attempts in Terminal to successfully resolve
all repositories) enter 8.8.8.8 (Google's DNS) into the relevant
'alternate DNS' in I
OK - complete solution/workaround is to be found here... But you must read
the whole lot before doing anything at all because the last edit makes the
first part redundant...
http://www.hecticgeek.com/2017/04/ubuntu-17-04-systemd-dns-issues/
The issue involves systemd within which the developers hav
Thanks Yu Lou - in the end I did a fresh install. That was OK.
David
On 19 Nov 2016 02:00, "Yu Lou" <1633...@bugs.launchpad.net> wrote:
> I have a dual system of Ubuntu and Windows 7 and encountered the same
> problem after in place upgrade from 16.04 to 16.10. I tried boot-repair
> before but it
I'm sorry @hrvooje - it worked for me.
But I have now risked upgrading my main laptop from 16.10 to 17.04 and it
appears to be working perfectly without the necessity for tweaks or
workaronds or alternative of 8.8.8.8 , etc, etc. I guess the latest in-situ
upgrade contained its own bugfix.
David
O
Thanks Michka
I had tried the boot-repair option, to no avail.
But this time I made sure I had the latest version (I do) by completely
removing boot-repair and reinstalling, including repository, and tried
'advanced' option. 'Successful' but didn't solve the problem.
Then I tried default version of
Thanks Alex
I had tried 'boot-repair' to no avail, although success was reported.
But I tried your solution twice by using dev/sda1 (the current efi FAT32
boot partition) and /dev/sda2 ( the main ext4 partition). Neither solved
the problem although there were no error messages only 'successful' rep
I have tried 'boot-repair' in normal and advanced mode and have tried
reinstalling grub via sudo grub-install /dev/sda1 (then sda2, and finally
simply sda). All of these approaches have reported 'success' in bash/terminal
etc - but none have actually solved my problem.
Actually I'm wondering whe
As other replies Joseph. The only thing I didn't try was an upstream
kernel. But in the end I've just done a completely fresh install - so
someone else will need to try the upstream kernel approach.. But I'm
intrigued that two people found their solution via a new grub install,
while I didn't
David
@Brian Rogers
Many thanks - I'd just like to report that your patch
(linux-image-2.6.34-v9patch-generic) appears to be working perfectly for me,
with my i855 HP Compaq Nx5000. I'm not trying anything fancy regarding video -
but can report that the system now starts normally, no freeze during boo
@Brian Rogers
Edit to above - no Ubuntu splash on subsequent restarts (any visual effects
setting), though there was on the first - but I wasn't getting the splash with
the Mainline kernel, either, so I don't miss it anyway.
Best
David
--
MASTER: [i855] GPU lockup (apport-crash)
https://bugs.la
29 matches
Mail list logo
