Changeing the mirror to the main mirror from the update-manager did
work, but somehow the german mirror still appears broken.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/798023
Title:
apt-get upda
Reported upstream.
** Bug watch added: GNOME Bug Tracker #589614
http://bugzilla.gnome.org/show_bug.cgi?id=589614
** Changed in: gdm
Importance: Undecided => Unknown
** Changed in: gdm
Status: New => Unknown
** Changed in: gdm
Remote watch: None => GNOME Bug Tracker #589614
--
g
Hm, I am actually not sure anymore if GNOME is the right place to report
it. I couldn't find the gdm.conf-custom file in the GNOME gdm sources
(maybe I just don't find it, but maybe it is not there). Could it be,
that gdm.conf-custom and especially the documentation therein is instead
added by Debi
There is no bug in gdm, but only a confusing option
(CustomCommandNo_Restart_ which _exits_ gdm when false) that should be
renamed or at least documented in the config file properly (it is
documented right now, but somewhat confusing). Maybe this is an upstream
bug.
** Summary changed:
- gdm cras
Sorry for my report, it was out of confusion between /etc/ldap.conf and
/etc/ldap/ldap.conf. I think their names are rather unfortunate, but
this is another issue.
Mika
--
gnutls regression: failure in certificate chain validation
https://bugs.launchpad.net/bugs/305264
You received this bug noti
Public bug reported:
The formatting of the Ubuntu Security Notices (usn) rss feed at
http://www.ubuntu.com/usn/rss.xml is broken.
It looks as if all the whitespace and paragraphs are removed, this is
especially annoying if you want to "scan" the text if the Ubuntu versions in
use are affected
** Attachment added: "our ldap.conf"
http://launchpadlibrarian.net/28369422/ldap.conf
--
gnutls regression: failure in certificate chain validation
https://bugs.launchpad.net/bugs/305264
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "output of ldapsearch -x -ZZ -d7"
http://launchpadlibrarian.net/28369454/ldapsearch_-x_-ZZ_-d7
--
gnutls regression: failure in certificate chain validation
https://bugs.launchpad.net/bugs/305264
You received this bug notification because you are a member of Ubuntu
Bugs,
I guess we are having the same problem authenticating against a sun open
directory server. I use intrepid-proposed on my client:
r...@client:~# dpkg-query -W -f='${Package} ${Version} ${Source} ${Status}\n' |
egrep 'slapd|ldap|gnutls'
gnutls-bin 2.4.1-1ubuntu0.3 gnutls26 install ok installed
ldap
I guess this is only a wishlist bug anymore.
** Changed in: gdm (Ubuntu)
Status: Incomplete => New
--
gdm crashes on execution of Custom Command
https://bugs.launchpad.net/bugs/315484
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
In Jaunty gdm just exits and says something like "System is restarting" or
similar. I guess in hardy and intrepid it is exiting also, but not displaying
any message.
I'm perfectly cool with this behaviour (that gdm just exits and displays some
message unless you set CustomCommandNoRestartN=True)
The latest version of the bioinformatics template from
http://www.oxfordjournals.org/our_journals/bioinformatics/for_authors/submission_online.html
does not require mathtime anymore (the lines are commented out).
So, just use the latest version of "upstream" when writing your bioinformatics
docu
mathtime is not distributed anymore, due to license problems (if I understood
the bug report in Debian correctly - see
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=425460 ).
There are some workarounds suggested (using belleek, see
/usr/share/doc/texlive-doc/fonts/belleek/README in intrepid),
Okay, this is what I did:
Install Ubuntu intrepid from the alternate CD, apt-get update && apt-get
dist-upgrade, the debugging repository from the wikisite enabled, apt-get
update && apt-get dist-upgrade again, installed the dbg-symbols for gdm.
Reboot, then I edited the gdm.conf-custom to inclu
Sorry, but I could not produce any crash reports - flipped "enabled" in
/etc/default/apport to be 1 and rebootet, then 'crashed' gdm by issuing a
CustomCommand and after that checked /var/crash for files - it was completely
empty. apport-cli (as root) said
No pending crash reports.
So either I
Thanks for your efforts, Leann.
--
[intrepid] PCMCIA network-card working in hardy does not work
https://bugs.launchpad.net/bugs/278350
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
** Attachment added: "Syslog of gdm (with debug) restarting and then crashing"
http://launchpadlibrarian.net/21056169/syslog-fails
--
gdm crashes on execution of Custom Command
https://bugs.launchpad.net/bugs/315484
You received this bug notification because you are a member of Ubuntu
Bugs, w
** Attachment added: "/etc/gdm/gdm.conf-custom file without workaround -
crashes"
http://launchpadlibrarian.net/21056149/gdm.conf-custom-fails
--
gdm crashes on execution of Custom Command
https://bugs.launchpad.net/bugs/315484
You received this bug notification because you are a member of U
** Attachment added: "Working /etc/gdm/gdm.conf-custom file with custom command"
http://launchpadlibrarian.net/21056126/gdm.conf-custom-works
--
gdm crashes on execution of Custom Command
https://bugs.launchpad.net/bugs/315484
You received this bug notification because you are a member of Ubu
Public bug reported:
Binary package hint: gdm
Hi,
found a problem that arouse recently with both Gutsy and Intrepid (worked some
day last year in gutsy):
When configuring a custom command in /etc/gdm/gdm.conf-custom in the
[customcommand] section via CustomCommand[0-9]=/some/command (tested wi
Public bug reported:
Binary package hint: debian-installer
I installed with the Jaunty Jackalope Alpha 2 i386 alternate CD and selected
"Free Software only", and "Expert Mode". I was then asked, if I wanted to
include backported software, I opted for yes.
When I investigated my sources.lst file
Sorry, I wanted to say: "...I would decrease priority."
--
[intrepid] PCMCIA network-card working in hardy does not work
https://bugs.launchpad.net/bugs/278350
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Like adament said, this patch went into the 2.6.28er kernel and is now in
Jaunty Jackalope alpha 2. In Jaunty Jackalope Alpha 2 the card works like
before, no problems at all.
Fortunately, the debian-installer uses a .28er kernel, too. This means, Jaunty
Jackalope is fully usable with the Netgea
Hi,
thanks for the pointer to the thread. I think I won't compile my own
kernel anyway, but it would be nice, if this would go into the .28
kernel, because it is quite annoying - nowadays every single Linux
distro uses a .26 or .27 kernel and they all fail...
Let's hope this will be fixed.
--
[
Same problem with lenny and a 2.6.26er kernel. Unfortunately I failed
epic in reporting the bug to debians bts (reportbug to debian inside
ubuntu does not work, chrooting into a debian does not work, I copied
the conf-file of a debian reportbug over my ubuntu reportbug, reportbug
works but fails to
** Also affects: debian
Importance: Undecided
Status: New
--
[intrepid] PCMCIA network-card working in hardy does not work
https://bugs.launchpad.net/bugs/278350
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs m
I get the same bug for intrepid final. So I guess I will not update from
8.04.
** Summary changed:
- [intrepid-beta/RC] PCMCIA network-card working in hardy does not work
+ [intrepid] PCMCIA network-card working in hardy does not work
** Description changed:
- exakt version of the kernel: 2.6.2
** Attachment added: "intrepid RC debian-installer uname -a"
http://launchpadlibrarian.net/18882729/intrepid_d-i_uname-a.log
--
[intrepid-beta/RC] PCMCIA network-card working in hardy does not work
https://bugs.launchpad.net/bugs/278350
You received this bug notification because you are a mem
** Attachment added: "intrepid RC debian-installer /var/log/syslog"
http://launchpadlibrarian.net/18882718/intrepid_d-i_syslog
--
[intrepid-beta/RC] PCMCIA network-card working in hardy does not work
https://bugs.launchpad.net/bugs/278350
You received this bug notification because you are a m
** Attachment added: "intrepid RC debian-installer lspcmcia -vv"
http://launchpadlibrarian.net/18882713/intrepid_d-i_lspcmcia-vv.log
--
[intrepid-beta/RC] PCMCIA network-card working in hardy does not work
https://bugs.launchpad.net/bugs/278350
You received this bug notification because you a
** Attachment added: "intrepid RC debian-installer lspci -vvnn"
http://launchpadlibrarian.net/18882681/intrepid_d-i_lspci-vvnn.log
--
[intrepid-beta/RC] PCMCIA network-card working in hardy does not work
https://bugs.launchpad.net/bugs/278350
You received this bug notification because you are
** Attachment added: "intrepid RC debain-installer"
http://launchpadlibrarian.net/18882663/intrepid_d-i_lsmod.log
--
[intrepid-beta/RC] PCMCIA network-card working in hardy does not work
https://bugs.launchpad.net/bugs/278350
You received this bug notification because you are a member of Ubun
Hi,
tested again with the same hardware the Ubuntu Intrepid RC (from the
i386-alternate CD) and got the same errors.
Additionally I now tried to install with network access, but the
debian-installer has the same Kernel and therefore the debain-installer gets
similar errors - I attach the output
** Summary changed:
- [intrepid-beta] PCMCIA network-card working in hardy does not work
+ [intrepid-beta/RC] PCMCIA network-card working in hardy does not work
--
[intrepid-beta/RC] PCMCIA network-card working in hardy does not work
https://bugs.launchpad.net/bugs/278350
You received this bug n
Dunbrokin, yours seems to be another bug.
Because:
1. you - at least sometimes - see your interface through ifconfig.
2. your card uses another driver than mine
3. the driver reports problems due to 32bit I/O, are you running a 64 bit
version? - if yes the problem could be the driver not beeing c
Filed the bug upstream.
** Bug watch added: GNOME Bug Tracker #46
http://bugzilla.gnome.org/show_bug.cgi?id=46
** Also affects: evolution via
http://bugzilla.gnome.org/show_bug.cgi?id=46
Importance: Unknown
Status: Unknown
--
evolution assigned-task view has no print
Public bug reported:
Binary package hint: evolution
If you click on a task in the task-view you get a new window with only the
details of this one task. Good.
But this window lacks a print button. Actually, thats where I need a print
button. Of course I can /close/ the window and print from the
Yes, it is loaded automatically on boot time and it is used by the modules
pcmcia_core and pcmcia (as lsmod shows). I really don't know much about the
linux driver system, but to me it looks as if pcnet_cs fails to be somehow
bound to the pcmcia card.
In dmesg you can see, that pcnet_cs (or some
Hi,
shortly: it doesn't happen anything.
long version:
I describe what I do, just in case I misunderstood you.
I boot intrepid, log in and run
sudo modprobe pcnet_cs
No output at all, dmseg|tail does not reveal any messages since boottime.
No other log in /var/log that I checked has any messages.
It just came to my mind that this might matter as well (I almost forgot it
because it is so everyday for me...):
I am booting the kernel with the kerneloption pci=irqmask=0x0e98. That is
because neither pci=biosirq nor without any pci-options wrok. Both fail to
detect the harddrive and the cd-ro
** Attachment added: "HARDY_WORKS_uname-a.log"
http://launchpadlibrarian.net/18231874/HARDY_WORKS_uname-a.log
--
[intrepid-beta] PCMCIA network-card working in hardy does not work
https://bugs.launchpad.net/bugs/278350
You received this bug notification because you are a member of Ubuntu
Bugs
** Attachment added: "HARDY_WORKS_proc_version_signature.log"
http://launchpadlibrarian.net/18231850/HARDY_WORKS_proc_version_signature.log
--
[intrepid-beta] PCMCIA network-card working in hardy does not work
https://bugs.launchpad.net/bugs/278350
You received this bug notification because y
** Attachment added: "HARDY_WORKS_lspcmcia-vv.log"
http://launchpadlibrarian.net/18231845/HARDY_WORKS_lspcmcia-vv.log
--
[intrepid-beta] PCMCIA network-card working in hardy does not work
https://bugs.launchpad.net/bugs/278350
You received this bug notification because you are a member of Ubu
** Attachment added: "HARDY_WORKS_lspci-vvnn.log"
http://launchpadlibrarian.net/18231837/HARDY_WORKS_lspci-vvnn.log
--
[intrepid-beta] PCMCIA network-card working in hardy does not work
https://bugs.launchpad.net/bugs/278350
You received this bug notification because you are a member of Ubunt
** Attachment added: "HARDY_WORKS_dmesg.log"
http://launchpadlibrarian.net/18231555/HARDY_WORKS_dmesg.log
--
[intrepid-beta] PCMCIA network-card working in hardy does not work
https://bugs.launchpad.net/bugs/278350
You received this bug notification because you are a member of Ubuntu
Bugs, wh
** Attachment added: "uname-a.log"
http://launchpadlibrarian.net/18231542/uname-a.log
--
[intrepid-beta] PCMCIA network-card working in hardy does not work
https://bugs.launchpad.net/bugs/278350
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: "proc_version_signature.log"
http://launchpadlibrarian.net/18231535/proc_version_signature.log
--
[intrepid-beta] PCMCIA network-card working in hardy does not work
https://bugs.launchpad.net/bugs/278350
You received this bug notification because you are a member of Ubunt
** Attachment added: "lspcmcia-vv.log"
http://launchpadlibrarian.net/18231528/lspcmcia-vv.log
--
[intrepid-beta] PCMCIA network-card working in hardy does not work
https://bugs.launchpad.net/bugs/278350
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
** Attachment added: "lspci-vvnn.log"
http://launchpadlibrarian.net/18231518/lspci-vvnn.log
--
[intrepid-beta] PCMCIA network-card working in hardy does not work
https://bugs.launchpad.net/bugs/278350
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
** Attachment added: "dmesg.log"
http://launchpadlibrarian.net/18231503/dmesg.log
--
[intrepid-beta] PCMCIA network-card working in hardy does not work
https://bugs.launchpad.net/bugs/278350
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
*** This bug is a duplicate of bug 256054 ***
https://bugs.launchpad.net/bugs/256054
Hi,
I don't think the bug is a duplicate of bug #256054, because:
1. I tried the workaround described at bug #256054, that means I disabled the
NetworkManager completely. It isn't loaded anymore (does not ap
*** This bug is a duplicate of bug 256054 ***
https://bugs.launchpad.net/bugs/256054
I looked quickly what the driver axnet_cs (that is proposed by pnet_cs)
is for: it is for spcial AXIS-based cards. I did not find any hints that
the Netgear FA411 card is based on this chipset. I would rather
** Attachment added: "outputs"
http://launchpadlibrarian.net/18225359/outputs
--
[intrepid-beta] PCMCIA network-card working in hardy does not work
https://bugs.launchpad.net/bugs/278350
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
exakt version of the kernel: 2.6.27-4-gerneric (Ubuntu
2.6.27-4.6-generic)
I am testing Intrepid on a fairly old Laptop without build-in network
card, thus I use a Netgear FA411 Fast Ethernet PCMCIA network card.
Under hardy it works like a charm (with every version of kernel
Public bug reported:
Binary package hint: debian-installer
Using Ubuntu Alternate i386 (20080930.4) Intrepid-Beta Iso on an old machine
(233 Mhz, 160 Mb RAM) it takes a lot of time to install. I don't have any
problems with that, but as I inspected on the terminal (via alt+f4) what was
happeni
55 matches
Mail list logo
