I was also having this problem on a System 76 laptop using Wayland with a hidpi
screen (3200x1800) and scaling set to 150%. I was able to fix it by doing:
gsettings set org.gnome.desktop.interface scaling-factor 1
https://askubuntu.com/questions/1073568/preventing-window-resizing-
after-resume
-
I took the default Lucid kernel, applied this patch
http://www.spinics.net/lists/linux-ide/msg37898.html, built it and this
fixed this problem for me.
--
sata_via hard resetting link / freeze: exception Emask 0x12 SAct 0x0 SErr
0x1000500 action 0x6
https://bugs.launchpad.net/bugs/422994
You rece
Java is working in both chrome and firefox for me after installing the
updates.
Here's the output from Firefox 'about:plugins' in case you are still
interested:
IcedTea NPR Web Browser Plugin (using IcedTea6 1.8 (6b18-1.8-4ubuntu3))
File: IcedTeaPlugin.so
Version:
The IcedTea NPR We
I tried this PPA, but it still isn't working for me. It does look like
this PPA installs
/usr/lib/jvm/java-6-openjdk/jre/lib/amd64/IcedTeaPlugin.so. The default
one only installed the i386 version. I'm attaching a strace log of
chrome starting up. You can see it finding the plugin, but it won't loa
Here's dmesg from 2.6.33-rc8 with the pci=use_crs
** Attachment added: "2.6.33-rc8 dmesg with pci=use_crs"
http://launchpadlibrarian.net/39379731/dmesg-2.6.33-rc8.txt
--
[HD 3650] Startup failure "Idle timed out, resetting engine..."
https://bugs.launchpad.net/bugs/341681
You received this bu
Here's dmesg from 2.6.33-rc8 without the pci=use_crs option.
** Attachment added: "2.6.33-rc8 dmesg without pci=use_crs"
http://launchpadlibrarian.net/39379719/dmesg-2.6.33-rc8-no-use_crs.txt
--
[HD 3650] Startup failure "Idle timed out, resetting engine..."
https://bugs.launchpad.net/bugs/34
This fixed it for me as well.
You rock, man.
--
[HD 3650] Startup failure "Idle timed out, resetting engine..."
https://bugs.launchpad.net/bugs/341681
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b
One thing I forgot to mention is that these attempts to launch X are
with the ATI proprietary driver. It exhibits nearly the same behavior as
the radeon driver. The only difference is that if I use the ATI
proprietary driver, it doesn't sit at a blank screen forever when I have
4GB in the machine,
** Attachment added: "X.org.log with 4g"
http://launchpadlibrarian.net/35337185/4g-xorg.log
--
[HD 3650] Startup failure "Idle timed out, resetting engine..."
https://bugs.launchpad.net/bugs/341681
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Attachment added: "lspci -v with 4GB"
http://launchpadlibrarian.net/35337163/4g-lspci.log
--
[HD 3650] Startup failure "Idle timed out, resetting engine..."
https://bugs.launchpad.net/bugs/341681
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
** Attachment added: "cat /proc/mtrr with 4GB"
http://launchpadlibrarian.net/35337132/4g-mtrr.log
--
[HD 3650] Startup failure "Idle timed out, resetting engine..."
https://bugs.launchpad.net/bugs/341681
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
** Attachment added: "2g-xorg.log"
http://launchpadlibrarian.net/35337092/2g-xorg.log
--
[HD 3650] Startup failure "Idle timed out, resetting engine..."
https://bugs.launchpad.net/bugs/341681
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
** Attachment added: "cat /proc/mtrr on 2gb"
http://launchpadlibrarian.net/35337053/2g-mtrr.log
--
[HD 3650] Startup failure "Idle timed out, resetting engine..."
https://bugs.launchpad.net/bugs/341681
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
On the off chance anyone is paying attention who knows anything about
this stuff, here's some more data.
I'm uploading 6 files. Three each for my laptop with 2GB main memory
installed and 4GB installed. One is cat /proc/mtrr, one is lspci -v, and
the last is a copy of Xorg.log.
Also I found a pr
I tried it with the Karmic Alpha 2 CD and that seems to have fixed the
problem.
--
[i855] When X starts, screen starts black, fades in sort of organic fashion to
white, then fades to black. Repeats.
https://bugs.launchpad.net/bugs/343390
You received this bug notification because you are a membe
I've got the same problem. Tried all the solutions mentioned, but the
only thing that works is taking out 2GB of the 4GB of main memory. I'm
game for trying any patches or tests if anyone has any ideas.
--
[HD3650] Startup failure "Idle timed out, resetting engine..."
https://bugs.launchpad.net/b
Of course the VESA driver kept producing a flickering screen at
1024x768, so I downloaded the 2.4.2 version of the intel driver (2.4.1
is the version that was installed on there through the package system),
built, and installed it. That seems to have fixed the problem.
--
When X starts, screen st
** Attachment added: "xorg.conf"
http://launchpadlibrarian.net/23892979/xorg.conf
** Description changed:
This is XUbuntu 8.10.
+
+ The graphics card is an Intel 855GM.
The screen was working fine from the original 8.10 install disk until I
let it update (some 170 updates). After th
** Attachment added: "Xorg log."
http://launchpadlibrarian.net/23892946/Xorg.0.log
--
When X starts, screen starts black, fades in sort of organic fashion to white,
then fades to black. Repeats.
https://bugs.launchpad.net/bugs/343390
You received this bug notification because you are a membe
** Attachment added: "lspci -vvnn output"
http://launchpadlibrarian.net/23892933/lspci.txt
--
When X starts, screen starts black, fades in sort of organic fashion to white,
then fades to black. Repeats.
https://bugs.launchpad.net/bugs/343390
You received this bug notification because you are
Public bug reported:
This is XUbuntu 8.10.
The graphics card is an Intel 855GM.
The screen was working fine from the original 8.10 install disk until I
let it update (some 170 updates). After the update, when X would come up
it would come up black and then sort of fade to white in blobs then
par
I have a similar problem when I directly attach my machine to my AT&T
DSL. It works fine on Windows, but here's what I get in 'daemon.log':
Jun 30 15:49:26 safir NetworkManager: Retrieved the following IP4
configuration from the DHCP daemon:
Jun 30 15:49:26 safir NetworkManager: address 99.
Normally I never use Nautilus, but I was talking someone through
creating permissions on a folder over the phone and we kept getting
stuck because I kept telling him to give read/write permissions to the
folder, when really what I should have been saying is 'create and
delete' which is what it says
Public bug reported:
1. Places -> Home folder.
2. File -> Create folder.
3. Type 'foo' for the name of the folder and hit enter.
4. Right click on folder named 'foo' and choose Properties.
5. Click on 'Permissions' tab.
6. Change 'File Permissions' for 'Others' to 'Read/Write'.
7. Click on 'Close'
Did you wait 3 minutes on the test with one disc detached? I think that
by default, there is a three minute timeout before it gets to the place
where Ken's patch is.
--
cannot boot raid1 with only one disk
https://bugs.launchpad.net/bugs/120375
You received this bug notification because you are a
I've forgotten about how this works exactly, but if you take a look in:
/usr/share/initramfs-tools/scripts/local
If you look for the comment
# We've given up, but we'll let the user fix matters if they canomment:
The bit inside the while loop with the panic is the part that gets
executed if ther
I haven't messed around with the problem in Gutsy, but what Daniel said
above about the difference between Fiesty and Gusty is not correct.
Fiesty was also launching mdadm as devices were discovered from udev and
that is exactly the problem. Both are pretty much the same, just the
code has moved ar
I've only tried it on fiesty. I don't have a gutsy machine handy. You
have the 'mdadm' package installed, right? If so, then they must have
moved stuff around. You could try this:
find / -type f -print0 | xargs -0 grep MD_DEGRADED_ARGS
That will search the whole file system for the a file with
MD
So, there is something wrong with that patch. Actually it seems to be
working great, but when I disconnect a drive to fail it, it boots up
immediately instead of trying mdadm after the timeout. So I'm guessing
that the mdadm script is getting called without the from-udev parameter
somewhere else.
So, there is something wrong with that patch. Actually it seems to be
working great, but when I disconnect a drive to fail it, it boots up
immediately instead of trying mdadm after the timeout. So I'm guessing
that the mdadm script is getting called without the from-udev parameter
somewhere else. B
I've got a different way to fix this. After reading Bug #75681, it
became clear why they have MD_DEGRADED_ARGS in there. They have that
because /scripts/local-top/mdadm gets called every time a device marked
raid gets called, but they only want mdadm to build the array once all
the devices have com
There is a problem with the solution outlined by Scott James Remnant
above. (https://bugs.launchpad.net/ubuntu/+source/initramfs-
tools/+bug/75681/comments/84)
What happens when one of the raid devices has failed and it isn't
getting detected? Take Scott's example a raid with (sda1 and sdb1):
> T
*** This bug is a duplicate of bug 120375 ***
https://bugs.launchpad.net/bugs/120375
** This bug has been marked a duplicate of bug 120375
cannot boot raid1 with only one disk
--
boot hangs with missing RAID device
https://bugs.launchpad.net/bugs/123888
You received this bug notification
I have a machine with a Intel 82845G with the same problem.
I was able to fix this by changing the setting for the amount of shared memory
for the card from 1024K to 8192K in the BIOS.
On mine, you boot into the BIOS, go to the 'Devices' menu, choose 'Video
Setup', then change 'Shared System M
Public bug reported:
1. Start an ftp server in a Japanese language environment:
LANGUAGE="ja_JP:ja:en_GB:en"
LANG="ja_JP.UTF-8"
wu-ftpd -s
2. Choose 'Connect to Server" from the Places menu. Create a connection
to your ftp server using "FTP with LOGIN".
3. Double click on the newly created folde
35 matches
Mail list logo
