Thanks for getting back to me.
Yes, that was the exact error message, that I recall. Although, it may have
been slightly different the first time
I observed the message. After the first time, the error message changed a
little, from memory, to the words that I described.
At the moment, the mess
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/894190
Title:
'Could not write bytes broken pipe' occurs just before log in with
Lubuntu 11.10
To manage notifications about this bug go to:
https://b
Public bug reported:
Just did the latest round of updates on 24-11-11, including a kernel
update, and got this message just before log in 'Could not write bytes
broken pipe'.
I did a clonezilla restore of Lubuntu 11.10 and then did all of the
updates again and the same problem occured. After bein
Thanks for that, I'm not sure how to use that script in comment #22 but
could easily learn, I'm sure. I have four drives in my system (Two
Windows 7 drives, testing and production, and the same for Linux) that
are all imaged via Clonezilla and Acronis, so its easy to restore my
Linux distros.
I've
Hmm, interesting. I've changed my monitor to D-sub instead of DVI
connection and this problem seems to have gone. Have only turned off and
turned on five times but it hasn't occured. It occured every time via
DVI.
My monitor is a BenQ E2200HD 22" at 1920 by 1080.
Will keep testing in Lubuntu to s
I've also got this problem, using Lubuntu 11.10 and Ubuntu 11.10
(Unity). My screen tends to go fuzzy as soon as I log in, after boot up.
It then disappears after about one minute. I'm no expert but am handy
with computers.
When I enter this into terminal:
sudo lshw -C video
I get this as my vid
No, this problem doesn't seem to exist anymore. I think the work around was
also to disable the floppy drive in the BIOS which helped too.
I am not using the same machine regularly now, after buying a new one a
few months ago.
Cheers,
LP
> Date: Sat, 23 Oct 2010 20:40:04 +
> From: marconi
I am still getting this problem, where I get a no signal message from
the monitor about once every three weeks (or possibly related to the
amount of boots in that time). After pressing crl-alt-f1 the system
shuts down the I can start up again fine. I then tend to have it occur
again within a day or
Sorry, I should have posted my machine specs: Intel Core i3, gigabyte
H55-USB3 motherboard, 4G of DDR3 RAM, Ben Q 2200HD monitor.
--
Lucid - 'no signal' message occasionally on boot
https://bugs.launchpad.net/bugs/595838
You received this bug notification because you are a member of Ubuntu
Bugs,
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/50528799/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/50528800/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/50528801/Dependencies.txt
** A
Public bug reported:
Using Lucid Lynx, i occasionally get the 'no signal' message on my
monitor during boot. it had only happened a few times in six weeks but
has now happened three times in the last few days. I have Lucid set to
log in automatically, if that is of use to bug testers.
This probl
I am also getting this problem on my Gigabyte 945GZM-S2 motherboard with
intel integrated graphics. After about fifteen seconds from boot I reach
the desktop but no menus are there. It takes about another 25 seconds
for the menus to appear. Everything is running well in Beta 1 now,
except for this
Thankyou for taking the time to look into this. I'm new to bug reporting and
looking at Beta versions of Ubuntu
and am enjoying it. I can understand that there are more important bugs to look
at. I will have a new machine in less than a year so it doesn't really matter
for me but helping out o
Sorry for the double post, not sure how that happened.
After boot, just before I get to the purple theme background I get this
notification:
mountall cannot connect to plymouth
then the default theme background appears and I can move the mouse but
no menus appear. They take about 25 seconds to a
Thanks for your help. I first noticed this problem mentioned in the Subject
during the
initial install of Lynx Beta 1 then turned off Compiz via this way below:
System>Preferences>Appearance>Visual Effects is set to None.
The problem still persists as of 30-3-10, 4pm Australian time with all of
Thanks for your help. I first noticed this problem mentioned in the Subject
during the
initial install of Lynx Beta 1 then turned off Compiz via this way below:
System>Preferences>Appearance>Visual Effects is set to None.
The problem still persists as of 30-3-10, 4pm Australian time with all o
Attached is the log you requested. Hope it helps.
---
Could you attach you /var/log/dpkg.log? That has information about
exactly what packages were updated last. You may try to downgrade some
of the packages
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/42333831/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/42333832/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/42333833/Dependencies.txt
** A
Public bug reported:
Binary package hint: xorg
Hi everyone,
Using the popular ABC iView site in Australia, fullscreen video is
pixelated and not very clear to view. Prior to the latest updates on the
29-3-10 (Australian time) video had improved quite a bit since the
release of Beta 1 but it has
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/41808687/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/41808688/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/41808689/Dependencies.txt
** A
Public bug reported:
When I boot up Lucid Lynx Beta 1, I get a brief FSCK notice (a couple of
seconds) then the them music plays within 15 seconds with just the
purple themed background. Suddenly after 25 seconds all of the menus
appear and all seems well. My motherboard is a Gigabyte 945GZM-S2 (r
21 matches
Mail list logo
