2009/7/17 Julien Langer
> I'm also not getting any VGA output when booting with "linux"
> "linux16" works fine though.
> I'm using vesafb on an nvidia geforce 8800GT
Sorry, forgot to mention that this happens with grub-pc 1.96+20090709-1
>
> -Julien
>
>
I'm also not getting any VGA output when booting with "linux"
"linux16" works fine though.
I'm using vesafb on an nvidia geforce 8800GT
-Julien
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Package: metacity
Version: 1:2.26.0-1
Severity: grave
Justification: renders package unusable
Currently metacity is uninstallable due to the following postinst error:
update-alternatives: error: alternative x-window-manager.1.gz can't be slave of
x-window-manager: it is a master alternative.
--
Package: texlive-base
Version: 2007.dfsg.1-3
Severity: grave
Justification: renders package unusable
I get the following error when upgrading to -3:
setting up texlive-base (2007.dfsg.1-3) ...
Running mktexlsr. This may take some time... done.
Building format(s) --all.
This may take some t
Package: texlife-base
Version: 2007.dfsg.1-3
Severity: grave
Justification: renders package unusable
I get the following error when upgrading:
etting up texlive-base (2007.dfsg.1-3) ...
Running mktexlsr. This may take some time... done.
Building format(s) --all.
This may take some time...
Package: nvidia-glx
Version: 173.14.09-2
Severity: grave
Justification: renders package unusable
Hi,
since the last nvidia update my xserver doesn't start anymore:
(II) Loading sub module "wfb"
(II) LoadModule: "wfb"
(WW) Warning, couldn't open module wfb
(II) UnloadModule: "wfb"
(EE) Failed to
Package: d4x
Version: 2.5.7.1-4
Severity: grave
Justification: renders package unusable
d4x crashes with the following messages on startup:
mcop warning: user defined signal handler found for SIG_PIPE, overriding
Creating link /home/julien/.kde/socket-moeff.
can't create mcop directory
-- Syste
I finally discovered what was causing this.
A custom splash screen that I had installed years ago... I didn't even
knew anymore that it was a custom splash screen :)
The strange thing is that gnome-session displays that image but than
freezes. And the old gnome-session version works fine with this
On Di, 2007-05-29 at 08:48 +0200, Josselin Mouette wrote:
> Le mercredi 23 mai 2007 à 23:52 +0200, Julien Langer a écrit :
> > > Could you send us your .gnome2/session file? Does it help if you move
> > > it
> > > away?
> > >
> > I did not have a sess
On Do, 2007-05-24 at 09:27 +0200, Josselin Mouette wrote:
> Is the only difference between your attempts the gnome-session
> version?
> The only change between -1 and -2 is in the session saving code, not
> in
> startup code.
>
> As both were uploaded on different architectures, this may be a pro
On Mi, 2007-05-23 at 22:06 +0200, Josselin Mouette wrote:
> Le mercredi 23 mai 2007 à 19:36 +0200, Julien Langer a écrit :
> > With gnome-session 2.18.0-2 gnome refuses to start. It hangs during
> the
> > startup with the splash screen.
> > Also most other X software canno
Package: gnome-session
Version: 2.18.0-2
Severity: critical
Justification: breaks the whole system
With gnome-session 2.18.0-2 gnome refuses to start. It hangs during the
startup with the splash screen.
Also most other X software cannot be started while gnome-session is
hanging.
It seems like gnom
ow if it is that
useful.
I tried to compile mldonkey with debugging symbols by adding
--enable-debug to the configure switches in the debian/rules file and
recompiled but there are still no debugging symbols.
On Wed, 2006-07-19 at 12:24 +0200, Samuel Mimram wrote:
> Hi,
>
> Julien Langer
Package: mldonkey-server
Version: 2.7.7-4
Severity: grave
Justification: renders package unusable
Since version 2.7.7-4 the mldonkey-server always crashes on startup with
the following message:
*** glibc detected *** corrupted double-linked list: 0x0850c210 ***
This does not happen with version 2
On So, 2006-03-26 at 16:01 +0200, Rene Engelhard wrote:
> Julien Langer wrote:
> > Seems like this error was caused by an old version of
> > openoffice.org-gnome.
> > I upgraded the openoffice.org-gnome package from 2.0.1-5 to 2.0.2-2 and
> > now everything works
Seems like this error was caused by an old version of
openoffice.org-gnome.
I upgraded the openoffice.org-gnome package from 2.0.1-5 to 2.0.2-2 and
now everything works fine again.
Maybe ooo should conflict with old versions of openoffice.org-gnome or
force an upgrade of this package.
--
To UNS
Package: openoffice.org
Version: 2.0.2-2
Severity: grave
Justification: renders package unusable
Since my last upgrade (from 2.0.2-1 to 2.0.2-2 I guess), ooo crashes with
the following messages:
Fatal exception: Signal 11
Stack:
/usr/lib/openoffice/program/libuno_sal.so.3[0xb7540557]
/usr/lib/ope
Package: lirc-modules-source
Version: 0.7.1pre1-2
Severity: grave
Justification: renders package unusable
I applied the patch from #294689 to build the module for kernel 2.6
However the built module can't be loaded:
root[/usr/src]# modprobe lirc_serial
FATAL: Error inserting lirc_serial (/lib/mod
18 matches
Mail list logo
