i don't think it's a solution that everybody changes the mirror to the
ONE main.
please recheck today au.archive.ubuntu.com. Given the way mirror syncing
works it may take a couple of hours for it to retrive the latest
packages.
--
Failed to fetch - Size mismatch after latest security updates
ht
Ted your mirror is not up to date.
% policy libswscale1d
libswscale1d:
.
.
3:0.cvs20070307-5ubuntu7.3 0
^^^
500 http://de.archive.ubuntu.com hardy-updates/main Packages
500 http://archive.ubuntu.com hardy-updates/main Packages
--
Failed to fetch -
hi
no everything is fine now.
--
Failed to fetch - Size mismatch after latest security updates
https://bugs.launchpad.net/bugs/343918
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b...@lists.ubuntu.c
Public bug reported:
Binary package hint: libavutil1d
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
The following packages will be upgraded:
ffmpeg [3:0.cvs20070307-5ubuntu7.1+medib
stellarium 0.7.1 (stellarium_0.7.1-1ubuntu3_i386.deb - Dapper) works
here just fine.
So shall we close this bug then?
--
user hasn´t answered since 2006-03-25 | problem with stellarium
(0.6.2-3ubuntu1)--- Fatal signal: Segmentation Fault (SDL Parachute Deployed)
https://launchpad.net/bugs/6355
I have tested stellarium (0.7.1-1ubuntu3 - dapper) but it won´t run here
because my monitor is just too small (only 800x600).
Maybe some else will try this version, or i will do so after vacation.
If this version runs fine then i suggest to close this bug because OP
hasn´t answered for almost 4 m
** Summary changed:
- problem with stellarium (0.6.2-3ubuntu1)--- Fatal signal: Segmentation Fault
(SDL Parachute Deployed)
+ user hasn´t answered since 2006-03-25 | problem with stellarium
(0.6.2-3ubuntu1)--- Fatal signal: Segmentation Fault (SDL Parachute Deployed)
--
user hasn´t answered si
> from Jordan Mantha at 2006-03-17
> Just a FYI, not a real fix:
> There is a new Debian maintainer for Scilab. I contacted
> him and asked about Scilab 4.0 . He said that he is
> working on it and it should be packaged soon.
As of today:
http://packages.debian.org/unstable/math/scilab
scilab
** Summary changed:
- lyx doesn't support utf-8 locales very well
+ Upstream and Wishlist | lyx doesn't support utf-8 locales very well
** Description changed:
-
- It's possible to enter international characters in lyx using breezy's
standard locale settings (*-utf8), but the following two exa
No one added a comment.
I close this bug with "fix released"
** Changed in: numlockx (Ubuntu)
Status: In Progress => Fix Released
--
"numlockx on" doesn´t work at Gnome login (Breezy)
https://launchpad.net/bugs/3290
--
universe-bugs mailing list
universe-bugs@lists.ubuntu.com
https://lis
jup can be closed.
If no one a has something to add i´ll do it myself during the week.
--
"numlockx on" doesn´t work at Gnome login (Breezy)
https://launchpad.net/bugs/3290
--
universe-bugs mailing list
universe-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/universe-bugs
i have upgarded to dapper and problem is gone.
all now works as aspected for me (with same hardware).
I had choosen to start with a complete new gnome profile.
So that´s maybe important.
--
"numlockx on" doesn´t work at Gnome login (Breezy)
https://launchpad.net/bugs/3290
--
universe-bugs maili
I saw in dapper we have a new version.
# apt-cache show numlockx
Package: numlockx
Priority: optional
Section: universe/x11
Installed-Size: 88
Maintainer: Martin-Éric Racine <[EMAIL PROTECTED]>
Architecture: i386
Version: 1.1-3ubuntu1
Can someone, who is on dapper, please check if it gone with th
a side note:
The numlock LED turns off even when i turn it on manually after some time.
--
"numlockx on" doesn´t work at Gnome login (Breezy)
https://launchpad.net/malone/bugs/3290
--
universe-bugs mailing list
universe-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/universe-bug
Ohh well i am happy i am not the only one.
Output from hwinfo:
55: PS/2 00.0: 10800 Keyboard
[Created at input.120]
Unique ID: nLyy.TBWTwSuMeW2
Hardware Class: keyboard
Model: "AT Translated Set 2 keyboard"
Vendor: int 0x0211
Device: int 0x0001 "AT Translated Set 2 keyboard"
Device
** Changed in: oooqs (Ubuntu)
Status: Unconfirmed => Rejected
--
oooqs-kde tries to install openoffice.org1
https://launchpad.net/malone/bugs/3045
--
universe-bugs mailing list
universe-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/universe-bugs
at breezy times openoffice.org (>> 1.0.99+1.1rc) was/is the stable version
--
oooqs-kde tries to install openoffice.org1
https://launchpad.net/malone/bugs/3045
--
universe-bugs mailing list
universe-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/universe-bugs
it´s fixed in dapper.
in breezy:
# apt-cache show oooqs-kde
openoffice.org (>> 1.0.99+1.1rc)
--
oooqs-kde tries to install openoffice.org1
https://launchpad.net/malone/bugs/3045
--
universe-bugs mailing list
universe-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/universe-bu
in Dapper:
Source: oooqs
Depends: ${shlibs:Depends}, openoffice.org (>> 2.0.0) | openoffice.org-calc |
openoffice.org-draw | openoffice.org- impress | openoffice.org-draw |
openoffice.org-base | openoffice.org-writer
Conflicts: openoffice.org (<< 2.0.0)
# apt-cache show openoffice.org
Package
Public bug report changed:
https://launchpad.net/malone/bugs/3290
Comment:
I have to admit it deons´t work.
After some time after login the numlock LED in gnome turns off.
But if i open gedit, i am able to enter numbers.
any ideas?
what information can i provide?
--
universe-bugs mailing list
u
Public bug report changed:
https://launchpad.net/malone/bugs/3290
Comment:
OK I tried to figure it more out:
Staus of Numlock LED:
in grub on
right after (linux start) off
when "generall Console Fonts" appeares on screen on
gdm on
splash on (turn
Public bug report changed:
https://launchpad.net/malone/bugs/3290
Comment:
hmm The LED is on right after power on (BIOS setting).
But yes i will check it. Thanks for input.
--
universe-bugs mailing list
universe-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/universe-bugs
Public bug report changed:
https://launchpad.net/malone/bugs/3290
Comment:
out of the curios. I accidently hit the numpad keys right after login and they
work.
Although the Numpad LED is of!
As I described earlier, after hit numlock twice also the LED is on.
--
universe-bugs mailing list
univer
Public bug report changed:
https://launchpad.net/malone/bugs/3290
Comment:
No.
I´ve:
if [ -x /usr/bin/numlockx ]; then
/usr/bin/numlockx on
fi
exit 0
at the end of both of them.
But as I told earlier. Numpad works but not the first time i log into Gnome
24 matches
Mail list logo