On 2 November 2011 01:41, Michael Basse 104...@bugs.launchpad.net wrote:
why should it be a bug instead of a security-feature?
Because the policy defined in /etc/securetty for local graphical
terminals is inconsistent with the policy defined there for local text
terminals, and because the lack
Happened to me as well on Debian Squeeze, after setting 96dpi as a
default. Changing the dpi key from integer 96 to float 96.0 fixed it for
me too. Thanks, Mary.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Bug still present for me after updating to Firefox 3.6.3 (Ubuntu Hardy,
using Firefox from Ubuntuzilla repo). Adding rm
~/.mozilla/firefox/*.default/compatibility.ini to /opt/firefox/firefox
script right before run-mozilla.sh is launched works around it.
--
[MASTER] Firefox does not start with
Having trouble getting the box to boot at all with Lucid + xorg-edgers,
as xserver-xorg-video-intel requires mode switching enabled in the
kernel but leaving nomodeset=1 off the options line makes the machine
boot into a video mode that its monitor doesn't support (probably
related to bug 522488).
You're a smart man, Mark, but this decision is wrong. Moving standard
controls around without an obviously compelling reason to do so is
madness, as is encouraging your design team to ignore overwhelming user
dissatisfaction. A spiffy aubergine paint job won't sell cars whose
clutch, brake and
Same old freeze while using remote desktop viewer.
--
[i845g] Karmic stops responding a few minutes after log in
https://bugs.launchpad.net/bugs/456902
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Brian: after the last freeze, I accidentally rebooted into your patched
kernel (2.6.31-50-generic) and ran it for a while with the same packages
as in comment #200, and it also froze while I was using remote desktop
viewer. So it looks like even that kernel's horrible GUI sloth doesn't
actually
$ pkgs='libdrm-dev libdrm-intel1 libdrm-intel1-dbg libdrm-nouveau1
libdrm-nouveau1-dbg libdrm2 libdrm2-dbg xserver-xorg-video-intel
xserver-xorg-video-intel-dbg'
$ dpkg --status $pkgs | grep Version | uniq uname -rv
Version: 2.4.14-1ubuntu1
Version: 2:2.9.0-1ubuntu2.2~gomyhr1~clipsolids~karmic
Now using Karmic with Jaunty's kernel.
$ pkgs='libdrm-dev libdrm-intel1 libdrm-intel1-dbg libdrm-nouveau1
libdrm-nouveau1-dbg libdrm2 libdrm2-dbg xserver-xorg-video-intel
xserver-xorg-video-intel-dbg'; dpkg --status $pkgs | grep Version | uniq
uname -rv
Version: 1:2.4.11-2+karmic3
Version:
It died, but not exactly the same way: this time, there was a sudden
burst of disk activity during which everything went black, then no
response to mouse or keyboard. I've attached Xorg.0.log retrieved via
ssh before I rebooted; looks like X has crashed and then failed on
restart.
** Attachment
20 hours freeze free - I'm prepared to call it stable.
--
[i845g] Karmic stops responding a few minutes after log in
https://bugs.launchpad.net/bugs/456902
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
OK, here I am back in Karmic, and just making sure we're all using the
same stuff:
$ pkgs='libdrm-dev libdrm-intel1 libdrm-intel1-dbg libdrm-nouveau1
libdrm-nouveau1-dbg libdrm2 libdrm2-dbg xserver-xorg-video-intel
xserver-xorg-video-intel-dbg'; sudo apt-get install $pkgs /dev/null dpkg
Karmic froze. Now testing Jaunty.
--
[i845g] Karmic stops responding a few minutes after log in
https://bugs.launchpad.net/bugs/456902
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
$ dpkg --status libdrm-dev libdrm-intel1 libdrm-intel1-dbg libdrm-nouveau1
libdrm-nouveau1-dbg libdrm2 libdrm2-dbg xserver-xorg-video-intel
xserver-xorg-video-intel-dbg | grep Version | uniqow...@owner-desktop:~$ dpkg
--status libdrm-dev libdlibdrm-nouveau1 libdrm-nouveau1-dbg libdrm2
I haven't yet seen the familiar freeze, but I've also not really had the
opportunity to work with that box for very long at a stretch, so I'm not
prepared to swear it's stable yet.
--
[i845g] Karmic stops responding a few minutes after log in
https://bugs.launchpad.net/bugs/456902
You received
$ dpkg --status libdrm-dev libdrm-intel1 libdrm-intel1-dbg libdrm-nouveau1
libdrm-nouveau1-dbg libdrm2 libdrm2-dbg xserver-xorg-video-intel
xserver-xorg-video-intel-dbg | grep Version | uniq
Version: 2.4.11-0jaunty2
Version: 2:2.7.0-jaunty2
$ uname -rv
2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17
Now trying your new libdrm with the old driver:
$ dv=2:2.6.3-0ubuntu9; sudo apt-get install xserver-xorg-video-intel=$dv
xserver-xorg-video-intel-dbg=$dv
$ dpkg --status libdrm-dev libdrm-intel1 libdrm-intel1-dbg libdrm-nouveau1
libdrm-nouveau1-dbg libdrm2 libdrm2-dbg xserver-xorg-video-intel
Just to clarify: I've had text console switching misbehaviour both times
I've tried driver version 2:2.7.0-jaunty1. It's not a complete X freeze:
the keyboard stays responsive, I can see the monitor turning its
backlight off and on as I attempt to switch screens, and the monitor's
OSD reports
$ echo deb http://ppa.launchpad.net/brian-rogers/graphics-testing/ubuntu jaunty
main | sudo tee -a /etc/apt/sources.list.d/brian-rogers.list
$ sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 311bdf2d
$ sudo apt-get update
$ sudo apt-get install libdrm-dev libdrm-intel1
No freeze so far, but I can't switch to a text console - any attempt
gives me a black screen, after which I can't get the GUI back. Keyboard
and (presumably) mouse still fully operational - I can successfully log
in blind to a text console and issue a reboot command. Doing
/etc/init.d/gdm restart
$ sudo ppa-purge ppa:brian-rogers/graphics-testing
$ dpkg --status libdrm-dev libdrm-intel1 libdrm-intel1-dbg libdrm-nouveau1
libdrm-nouveau1-dbg libdrm2 libdrm2-dbg xserver-xorg-video-intel
xserver-xorg-video-intel-dbg | grep Version | uniq
Version: 2.4.5-0ubuntu4
Version: 2:2.6.3-0ubuntu9
$
12:2.7.0 and friends listed above just froze while looking at a Flash-
based web site, so I guess we're still looking at a driver issue, not a
mesa or libdrm2 one.
I don't have a Jaunty installer disc or any blanks here, but will burn
one before coming to work tomorrow if you think running an
In the meantime, I will grit my teeth, knees and elbows and persist with
testing linux-image-2.6.31-50-generic with a ppa-purged Karmic.
--
[i845G] Karmic stops responding a few minutes after log in
https://bugs.launchpad.net/bugs/456902
You received this bug notification because you are a
Couldn't bear working with linux-image-2.6.31-50-generic any longer. Now
running a fresh Jaunty installation. Will report any freezes.
If there's somebody else whose freeze experience matches mine wrt driver
versions in use, it would be good to put your hand up, as I won't have
access to these
Now running a fresh-from-CD Jaunty with Option AccelMethod UXA
added to the Device section in xorg.conf. Brian: if this doesn't freeze
today, what's best to do next?
--
[i845g] Karmic stops responding a few minutes after log in
https://bugs.launchpad.net/bugs/456902
You received this bug
After noticing in Xorg.0.log that 2.8.0 used UXA by default while 2.7.0
was picking EXA, I added
Option AccelMethod UXA
to the Device section in xorg.conf and reinstalled 2.7.0. This has
fixed the early freeze reported in comment #138. I will be working with
this box for the next couple of
2.7.0 just froze in the usual way, while scrolling a remote VNC window
with vinaigre.
I hadn't added your ppa to my sources.list.d; I've just been downloading
and dpkg --installing xserver-xorg-video-intel .debs. So I've just done
sudo apt-get update
sudo dpkg --force-depends --remove
OK, assuming may impair performance in certain specific scenarios
means the same thing as makes the entire desktop experience
unresponsive enough to be intolerable except for debugging purposes it
appears that your patched kernel is working as intended :-)
Will report freezes if any occur.
--
OK, I'll test that idea. There did seem to be a stability improvement
going from the stock xserver-xorg-video-intel to your
7:2.8.99.901-5-g57fc09c version, so I'll start again with that and the
libdrm2 and mesa stuff from your ppa:
$ echo deb
Got the usual freeze while scrolling a Firefox tab. Now testing:
kernel: 2.6.31-19-generic
libgl1-mesa-dri, libgl1-mesa-glx, libglu1-mesa, libosmesa6, mesa-utils:
1:7.4.1-1ubuntu6+karmic
libdrm2: 1:2.4.11-2+karmic3
xserver-xorg-video-intel: 12:2.7.0
What are the chances of a workaround kernel
** Description changed:
Acer SK20 computer (Intel 845G graphics), Acer AL1511 LCD panel. Karmic,
kernels 2.6.31-17-generic and 2.6.31-19-generic tested. Both fail to set
the panel to its native 1024x768 resolution automatically; 640x350 mode
is chosen instead, which the panel really
These boxes are all booting with nomodeset=1 kernel parameters and
1024x768 forced in xorg.conf anyway, per bug 522488.
12:2.7.0 is a doozy! Freezes in the customary fashion before even making
it to the desktop (these boxes are all set to auto-login) on four tries
out of five so far, 15 seconds
After more than 24 hours of stable running on this box,
7:2.8.0-8-g12c5aec froze while attempting to use gdebi to install
7:2.8.0-27-g926c7e7. It also froze once while attempting to launch gedit
on another identical box (I'm trying to set up a batch of elderly school
computers for cost-recovery
Mouse cursor moves, but clicks are ignored and keyboard is locked up
(caps/num lock produce no change in status LEDs, ctrl-alt-Fn doesn't
work). Disk activity continues. If a freeze is going to happen, it will
most often be right when an app is in the process of opening a new
window. I'm using
I've just installed 11:2.8.0, and if it freezes I will watch the desktop
clock for a minute and let you know.
--
[i845G] Karmic stops responding a few minutes after log in
https://bugs.launchpad.net/bugs/456902
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I now have two of these boxes on the same bench, both with 11:2.8.0
installed. The one I'm using to try to get today's work done is running
sshd, and the other one is running top on it via ssh. I have pressed
Murphy's Law into service to help these boxes freeze if they're going to
freeze, by also
Thanks, Murphy. Love your work.
11:2.8.0 froze while using Firefox to compose a Gmail. As usual the
mouse cursor remained movable (though stuck in the I-beam shape from the
compose window, this time) but no response to clicks or keyboard. The
desktop clock didn't update. The top listing on the
2.8.99.901-5-g57fc09c just froze, right as gdebi was about to install
2.8.99.901-16-g7e7db7a :-(
Rebooted, installing 2.8.99.901-16-g7e7db7a now.
--
[i845G] Karmic stops responding a few minutes after log in
https://bugs.launchpad.net/bugs/456902
You received this bug notification because you
2.8.99.901-16-g7e7db7a froze fairly quickly, as expected (playing Klondike,
fwiw).
Now trying 2.8.0-47-ge903b3e.
--
[i845G] Karmic stops responding a few minutes after log in
https://bugs.launchpad.net/bugs/456902
You received this bug notification because you are a member of Ubuntu
Bugs, which
2.8.0-47-ge903b3e froze. Trying 2.8.0-8-g12c5aec.
--
[i845G] Karmic stops responding a few minutes after log in
https://bugs.launchpad.net/bugs/456902
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
No freeze so far with 2.8.0-8-g12c5aec. Have to go now; will leave this
machine running and check it again in ~12 hours.
--
[i845G] Karmic stops responding a few minutes after log in
https://bugs.launchpad.net/bugs/456902
You received this bug notification because you are a member of Ubuntu
Acer SK20 here.
00:02.0 VGA compatible controller: Intel Corporation
82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device (rev 03)
kernel: Linux version 2.6.31-19-generic (bui...@palmer) (gcc version
4.4.1 (Ubuntu 4.4.1-4ubuntu8) ) #56-Ubuntu SMP Thu Jan 28 01:26:53 UTC
2010 (Ubuntu
Public bug reported:
Acer SK20 computer (Intel 845G graphics), Acer AL1511 LCD panel. Karmic,
kernels 2.6.31-17-generic and 2.6.31-19-generic tested. Both fail to set
the panel to its native 1024x768 resolution automatically; 640x350 mode
is chosen instead, which the panel really doesn't like
** Attachment added: attachments.zip
http://launchpadlibrarian.net/39257756/attachments.zip
--
Missing monitor quirk for Acer AL1511 results in reduced resolution
https://bugs.launchpad.net/bugs/522488
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 391215 ***
https://bugs.launchpad.net/bugs/391215
As far as I've been able to determine by experiment, the Karmic kernels
completely ignore the vga= option, and rely on EDID to work out what
resolution to use. For those of us unfortunate enough to own
*** This bug is a duplicate of bug 391215 ***
https://bugs.launchpad.net/bugs/391215
Whoops, sorry, missed duplicate status. Cross-posting a link and
additional info.
--
[Karmic] kernel = 2.6.30-10 with vga=791 tty consoles not accessible and not
showing dmesg.
As described in my careless post to a duplicate bug report at
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/391705/comments/10
this happens to me as well. Acer SK20, Intel 845 graphics so I don't
think it's just an nVidia issue.
The following lines from dmesg (attached) are interesting:
Getting the same fading effect with a fresh install of Karmic on a Dell
Dimension E520.
lspci lists the sound hardware as
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio
Controller (rev 02)
Steps to reproduce:
1. Plug headphones into the front panel.
2. Open Places-Home
OK, this isn't a bug, merely a misconfiguration. See MrQuincle's helpful
post here:
http://ubuntuforums.org/showthread.php?p=8327304#post8327304
This particular Dimension E520 is now working well after adding the
model=5stack option (it has the 5 jacks + SPDIF back panel).
--
Sound fading out
Nicolas François wrote on 2009-05-10:
Why did you included the displays from 0 to 63? (Is 63 the maximum, or
is it just meant to be mostly complete?)
I had no idea about maximums - I was just following the existing pattern
for ttyNN and vc/NN. But from what Steve Langasek wrote on 2009-08-19,
Is LDAP address book support actually provided by Gecko, then?
--
[upstream] Openoffice.org Address data sources missing
https://bugs.launchpad.net/bugs/93546
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
2009/5/9 Mantas Kriaučiūnas man...@akl.lt:
I've assigned this bug to shadow (login) packages, because according to
latest comments from Flabdablet and steve.langa...@canonical.com the
way to solve password-less local login bug by adding lines bellow to
/etc/shadow is correct
They need
On Wed, Mar 4, 2009 at 10:25 AM, Steve Langasek
steve.langa...@canonical.com wrote:
I don't know if the display names always belong to local X servers;
answering that question would go a long way to help resolve this bug.
OK. I just tested this by turning on XDMCP on the desktop box
My Hardy desktop box has five user accounts, one of which (visitor) has
no password. I can confirm that appending the following to
/etc/securetty enables visitor to log in via GDM and successfully unlock
gnome-screensaver and switch users.
# X displays
:0
:0.0
:20
:20.0
:21
:21.0
:22
:22.0
:23
For the benefit of others who find their way here via Google, here's the
smallest workaround I've found so far:
* Use dexconf to generate a minimal xorg.conf
* Edit xorg.conf and make the following changes:
- Change Driver vesa to Driver intel in Section Device
- Add the following lines between
*** This bug is a duplicate of bug 195915 ***
https://bugs.launchpad.net/bugs/195915
Not a dupe, as far as I can tell. I am seeing the specific behavior
described here re. the garbage bin applet in a fresh install of Hardy
(not a beta, the release). Unlike the bug described in #195915, this
I think this is a duplicate of bug #93546.
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/93546
--
using a LDAP database source
https://bugs.launchpad.net/bugs/152889
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Mozilla address book connectors I can see being a problem, because the
Mozilla address book format is insane. But why is LDAP address book
support missing?
--
Openoffice.org Address data sources missing
https://bugs.launchpad.net/bugs/93546
You received this bug notification because you are a
Well, I'm running Gutsy, I have openoffice.org-core 1:2.3.0-1ubuntu5.3,
and I see only
-Evolution
-Groupwise
-Evolution LDAP
-Other external data source
After sudo apt-get install openoffice.org-kde, I get
-Evolution
-Groupwise
-Evolution LDAP
-KDE address book
-Other external data source
So
Aaron, I did this:
zcat /usr/share/hplip/data/ps/testpage.ps.gz testpage.ps
sh inkjet.sh testpage.ps
lpr -o raw testpage.pcl
and my Mum's HP C3180 ejected a blank page. Gutsy, iMac G3.
Attaching testpage.ps, inkjet.sh and testpage.pcl.
** Attachment added: testpage.zip
I also did this:
scp inkjet.sh testpage.ps my.x86.gutsy.server:/home/stephen/foo
ssh my.x86.gutsy.server
sudo apt-get update
sudo apt-get install hplip
sudo apt-get install hpijs
cd foo
sh inkjet.sh testpage.ps
logout
scp my.x86.gutsy.server:/home/stephen/foo/testpage.pcl .
lpr -o raw
My filthy workaround for this issue:
cd /tmp
wget
http://archive.ubuntu.com/ubuntu/pool/main/g/gtk+2.0/libgtk2.0-0_2.10.11-0ubuntu3_powerpc.deb
dpkg -x libgtk2.0-0_2.10.11-0ubuntu3_powerpc.deb foo
cd /usr/lib/gtk-2.0/2.10.0/printbackends
sudo mv libprintbackend-cups.so
OK, it's not hpijs, it's ghostscript. This rather horrid workaround has
Mum printing again:
cd /tmp
wget
http://archive.ubuntu.com/ubuntu/pool/main/g/gs-esp/libgs-esp8_8.15.4.dfsg.1-0ubuntu1_powerpc.deb
dpkg -i libgs-esp8_8.15.4.dfsg.1-0ubuntu1_powerpc.deb
wget
Gutsy PowerPC on iMac G3, upgraded from Feisty and up to date,
experiencing this issue sporadically without ever having saved a
session. I've installed dbus-x11 and will report back here if the
problem recurs. Message text:
There was an error starting the GNOME Settings Daemon.
Some things,
The patched package I linked to in #163255 no longer fixes this issue
for me. Plus, I got sick of having to uncheck liboil0.3 in the upgrade
manager. So I've just now applied a filthy workaround: downgrade liboil
to version 0.3.9-1.2, then copy the actual library
/usr/lib/liboil-0.3.so.0.1.0
My mother's g3 iMac, working fine with Feisty, started printing blank
pages exactly as Pascal describes after the update to Gutsy. HP C3180
inkjet/scanner. Will attach appropriate debug stuff next time I have
access to the machine.
--
[gutsy] HP DJ F380 ejecting blank pages
Confirming this on a G3 iMac. Fixed for the time being using a patched
package linked from here, which doesn't annoy Update Manager so much:
https://bugs.launchpad.net/debian/+source/libvisual/+bug/72814/comments/17
Commands used to apply the temporary fix:
wget
I think the problem is that the current nvidia drivers interact with
x.org in strange and wondrous ways, and work more things out for
themselves than they used to, and take less notice of some bits of
xorg.conf than they used to. So before you give up on Feisty: start
with the stock Feisty
Sitsofe, is there anything you think can be done about this, beyond
possible inclusion of a warning about known issues on upgrade and a
link to the BinaryDriverHowto/Nvidia page in the package description?
--
[nvidia-glx] X is blank after upgrade (laptop/Geforce Go)
For the benefit of others who spent ages tracking this down: next time
something weird happens to your video display, dive straight into
/var/log/Xorg.0.log and do your best to make sense of it.
The penny dropped for me when I saw no error (EE) lines at all - as
far as X was concerned, everything
The attached xorg.conf fixed this issue on my Dell Inspiron 8200 (used
with nvidia-glx, not nvidia-glx-legacy).
Once you have basic nvidia functionality again, have a play with the
nvidia-settings tool; all sorts of nice things can be done.
** Attachment added: xorg.conf
There's a link to a working rdesktop 1.5 .deb on the Ubuntu forums:
http://ubuntuforums.org/attachment.php?attachmentid=18030d=1161587227
I've just installed this on Edgy and it works for me (note that although
it claims to be a .tar.gz, it's actually just a .tar). Forum thread
link is
I have the same problem. Edgy, rdesktop 1.4.1-1.1, nvidia-glx
1.0.8776+2.6.17.6-1. Didn't happen in Dapper. Can be made very
slightly more tolerable by turning off Show window contents while
dragging on the target Windows box (see attached screenshot); if this
is done, corruption only occurs
** Attachment added: Show window contents while dragging off
http://librarian.launchpad.net/5129166/Screenshot-1.png
--
Window dragging display corruption
https://launchpad.net/bugs/44024
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I've seen exactly the same kind of stripes when using a few other things
that put my Inspiron 8200 into 640x480 resolution (a couple of DOS-based
disk-repair utilities do this, among others) so I suspect it's actually
a Dell BIOS bug.
To work around it for Ubuntu, I added vga=792 to the kernel
75 matches
Mail list logo
