I had the exact same issue on my Lenovo T60 running Hardy. After
googling around and reading this, I ejected the blank CD I had in the
drive, and gdmsetup works.
--
gdmsetup crashes with Segmentation Fault
https://bugs.launchpad.net/bugs/290848
You received this bug notification because you are
No visible improvement.
xrandr reports the same as before:
Screen 0: minimum 320 x 200, current 1152 x 864, maximum 1360 x 1360
VGA disconnected (normal left inverted right x axis y axis)
TMDS-1 connected 1152x864+0+0 (normal left inverted right x axis y axis) 0mm x
0mm
1360x768 59.8
Still marked incomplete?
--
[intrepid] i810 video driver regression
https://bugs.launchpad.net/bugs/282609
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
If you use NIS-distributed autofs maps, you need to restart autofs as
well - *after* you've restarted NIS.
--
NIS has problems starting before the network comes up
https://bugs.launchpad.net/bugs/50430
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Brian, yes - read the bug report.
--
[intrepid] i810 video driver regression
https://bugs.launchpad.net/bugs/282609
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Attachment added: X configuration from Hardy
http://launchpadlibrarian.net/18495890/xorg.conf.hardy
--
[intrepid] i810 video driver regression
https://bugs.launchpad.net/bugs/282609
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: X log, running with failsafe config (vesa driver)
http://launchpadlibrarian.net/18495913/vesa.log
--
[intrepid] i810 video driver regression
https://bugs.launchpad.net/bugs/282609
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: X log, running with old config
http://launchpadlibrarian.net/18495893/intel.log
--
[intrepid] i810 video driver regression
https://bugs.launchpad.net/bugs/282609
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: X log, running with auto-generated minimal config
http://launchpadlibrarian.net/18495933/lowres.log
--
[intrepid] i810 video driver regression
https://bugs.launchpad.net/bugs/282609
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The failsafe configuration looks like this:
Section Device
Identifier Configured Video Device
Driver vesa
EndSection
Section Monitor
Identifier Configured Monitor
EndSection
Section Screen
Identifier Default Screen
Monitor
Public bug reported:
Binary package hint: xserver-xorg-video-intel
Lenovo ThinkCentre M55 (8811-92G) with integrated Intel 965Q graphics
chipset. Sony 1600x1200 flat panel connected to TMDS-1 with single-link
DVI-D cable.
00:02.0 VGA compatible controller: Intel Corporation 82Q963/Q965
Public bug reported:
Binary package hint: zsh
Fully up-to-date Hardy Heron as of 1008-10-07 with zsh-4.3.4-24ubuntu1
and subversion-1.5.1dfsg1-1ubuntu2~hardy2 from hardy-backports.
Subversion command completion fails:
% svn addTAB
_arguments:comparguments:303: invalid argument: ARG
This goes
as of 1008-10-07 should of course be as of 2008-10-07
--
zsh completion broken for svn 1.5
https://bugs.launchpad.net/bugs/279545
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Attachment added: _subversion.diff
http://launchpadlibrarian.net/18286954/_subversion.diff
--
zsh completion broken for svn 1.5
https://bugs.launchpad.net/bugs/279545
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I see the same thing as Juan Pablo Salazar Bertín and George Pollard. I
decided to look a little further into it:
1) I start gnome-compiz-preferences from a terminal, and nothing happens.
2) I start it again from another terminal, and the dialog pops up. At the exact
same time, in the first
I forgot to add: Gutsy, Lenovo T60, ATI X1400, fglrx, and, obviously,
Xgl and compiz.
--
gnome-compiz-preferences does not start
https://bugs.launchpad.net/bugs/118948
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Similar issue, Compiz on Gutsy, 1 row of 8 desktops.
Ctrl-Alt-Left and Ctrl-Alt-Right switch *two* desktops to the left and
right, respectively.
~/.gconf/apps/compiz/general/allscreens/options/%gconf.xml contains:
entry name=switch_to_down_desktop_key mtime=1177350989
type=string
*** This bug is a duplicate of bug 111257 ***
https://bugs.launchpad.net/bugs/111257
A little more digging shows there are actually two different issues at
play here. One of them (BadAlloc when using compiz) is indeed a
duplicate of #111257. The other (BadMatch when using fglrx) is a
I did some more digging. The problem Chris and I are seeing is
completely unrelated; it is actually a dupe of #130696, which mentions
several workarounds.
--
totem-xine crash on logo (workaround inside)
https://bugs.launchpad.net/bugs/35229
You received this bug notification because you are a
I did some more digging. The problem Chris and I are seeing is
completely unrelated; it is actually a dupe of #130696, which mentions
several workarounds.
--
totem-xine crash on logo (workaround inside)
https://bugs.launchpad.net/bugs/35229
You received this bug notification because you are a
Same as Chris Waigl. Worked fine with Feisty. The previously mentioned
workaround (scaling or removing totem_logo.png) does not work.
Furthermore, gxine fails in the exact same manner:
The program 'gxine' received an X Window System error.
This probably reflects a bug in the program.
The error
Correction, I was able to watch the first episode using mplayer. With
the gutsy-backports version, I was even able to see (but not use) the
menus. With totem-gstreamer, I was not able to see anything but an error
message about missing codecs.
--
totem-xine crash on logo (workaround inside)
I previously posted this as a followup to #35229 (a different bug with
very similar symptoms):
Same as Chris Waigl. Worked fine with Feisty. The previously mentioned
workaround (scaling or removing totem_logo.png) does not work. Furthermore,
gxine fails in the exact same manner:
The program
To be very clear, this is *not* a duplicate of #111257.
** This bug is no longer a duplicate of bug 111257
totem crashes with 'BadAlloc (insufficient resources for operation)' when
using compiz and xserver-xorg-video-intel driver
--
totem-xine and mplayer cannot play any video
I previously posted this as a followup to #35229 (a different bug with
very similar symptoms):
Same as Chris Waigl. Worked fine with Feisty. The previously mentioned
workaround (scaling or removing totem_logo.png) does not work. Furthermore,
gxine fails in the exact same manner:
The program
Same as Chris Waigl. Worked fine with Feisty. The previously mentioned
workaround (scaling or removing totem_logo.png) does not work.
Furthermore, gxine fails in the exact same manner:
The program 'gxine' received an X Window System error.
This probably reflects a bug in the program.
The error
Correction, I was able to watch the first episode using mplayer. With
the gutsy-backports version, I was even able to see (but not use) the
menus. With totem-gstreamer, I was not able to see anything but an error
message about missing codecs.
--
totem-xine crash on logo (workaround inside)
See the attached log. The first ten or so instances are from
/etc/init.d/nis in the normal startup sequence. The second-to-last
instance is from the beginning of /etc/rc.local. The final instance is
from /etc/rc.local immediately before /etc/init.d/nis is run again
(successfully).
Note that
Once again, this is *not* a NIS problem, it is a NetworkManager problem
that affects far more than NIS. I do not have -no-dbus in
/etc/default/nis.
--
NIS has problems starting before the network comes up
https://bugs.launchpad.net/bugs/50430
You received this bug notification because you are a
One thing that just occurred to me, could this be caused by
interoperability issues between NetworkManager and the specific NIC
driver being used (tg3 in my case), as in this report of a similar
problem which was fixed by switching drivers: https://bugs.launchpad.net
/network-manager/+bug/38586
The NIS failure is obviously highly visible since it does not fail
gracefully (i.e. it will not magically fix itself once the network is
up) and it prevents you from logging in, but this is not just a NIS
issue; it affects anything that requires a working network connection
and / or DNS to start
31 matches
Mail list logo
