Having the Same Issue (E6510) with 3.0.15, Display does not turn on if
booted in Docking Station with Lid closed.
If the lid is open at boot time and closed at display manager login
screen it works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
Works for me also. Am still experiencing a problem with the docking
station but this seems unrelated (Monitor does not turn on if Laptop
lid is closed while starting in the docking station)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
I am experiencing the same issue here on an Dell Latitude E6510.
The last kernel in oneiric-updates does not work either.
** Attachment added: "lspci.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/906672/+attachment/2685261/+files/lspci.txt
--
You received this bug notification b
I stumbled upon the same problem, using the share in question worked
fine until the upgrade to karmic koala. The first meassure i used was
to disable locking, which resolved the "file exists" problem, but still
created files don't appear after the cache flush, creating folders is
working correctly
The problem is now gone after doing a dist-upgrade on 7th of October,
please close this bug...
** Changed in: linux (Ubuntu)
Status: New => Fix Released
--
Changing to another VT is not possible (Intel Mobile 945GM/GMS/GME)
https://bugs.launchpad.net/bugs/437531
You received this bug noti
** Attachment added: "AlsaDevices.txt"
http://launchpadlibrarian.net/32514148/AlsaDevices.txt
** Attachment added: "AplayDevices.txt"
http://launchpadlibrarian.net/32514149/AplayDevices.txt
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/32514150/BootDmesg.txt
** Att
Public bug reported:
Bootup is successfull, X-Server runs with correct resolution, so the
modesetting seems to work fine.
When switching from X11 to another VT the X Screen Content Freezes and nothing
else happens, when switching back there is a short flicker of a black screen
and X Continues
I Suggest to close it, because i havent actually been able to repeat it
myself. (Btw, is it possible for me to close my own report, its not,
right?)
--
[apport] configure.py crashed on first start after installing the lyx-qt package
https://bugs.launchpad.net/bugs/95087
You received this bug noti
I was definately not out of disc space, i restarted Lyx directly after the
crash and it worked (as i said in my original posting), but it sure doesnt look
nice if the program crashes after installation...
Any other things to check? I didnt try to purge and reinstall it, to see if the
problem is
** Attachment added: "Dependencies.txt"
http://librarian.launchpad.net/6902446/Dependencies.txt
** Attachment added: "ProcMaps.txt"
http://librarian.launchpad.net/6902447/ProcMaps.txt
** Attachment added: "ProcStatus.txt"
http://librarian.launchpad.net/6902448/ProcStatus.txt
** Attachm
Public bug reported:
Binary package hint: lyx
Steps to reproduce:
Feisty fawn, up to date on march 23th 2007.
1. Install lyx with synaptic
2. Start Lyx
3. Crash on first startup
Problem is not severe, the next startup worked.
ProblemType: Crash
Architecture: i386
Date: Fri Mar 23 14:55:10 2007
11 matches
Mail list logo
