Re: [Bug 278350] Re: [intrepid] PCMCIA network-card working in hardy does not work
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. -- [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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 315484] Re: gdm crashes on execution of Custom Command
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 include: [customcommand] CustomCommand0=/usr/bin/yes Reboot again, at the point gdm asks for credentials, I followed the instructions at https://wiki.ubuntu.com/Backtrace -> "Already running programs" to obtain a backtrace. Hope this helps. ** Attachment added: "Backtrace of gdm failing with CustomCommand0=/usr/bin/yes" http://launchpadlibrarian.net/21773129/gdb-gdm.txt -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 305264] Re: gnutls regression: failure in certificate chain validation
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-auth-client 0.5.2 install ok installed
ldap-auth-config 0.5.2 ldap-auth-client install ok installed
ldap-utils 2.4.11-0ubuntu6.2 openldap install ok installed
libcurl3-gnutls 7.18.2-1ubuntu4.3 curl install ok installed
libgnutls26 2.4.1-1ubuntu0.3 gnutls26 install ok installed
libldap-2.4-2 2.4.11-0ubuntu6.2 openldap install ok installed
libnss-ldap 260-1ubuntu2 install ok installed
libpam-ldap 184-4ubuntu2 install ok installed
The rest is attached:
ldap.conf
output of gnutls-cli -p636 --x509cafile CAFILE srv.obf.obf.ob
output of ldapsearch -x -ZZ -d7
If you need anything else, please ask.
** Attachment added: "output of gnutls-cli -p636 --x509cafile CAFILE
srv.obf.obf.ob"
http://launchpadlibrarian.net/28369414/gnutls-cli_-p636_--x509cafile_CAFILE_srv.obf.usc.at
--
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.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 305264] Re: gnutls regression: failure in certificate chain validation
** 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, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 305264] Re: gnutls regression: failure in certificate chain validation
** 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 393006] [NEW] usn rss feed hardly readable
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 / which CVEs are closed. It would be nice if the feed would get the whitespace as it is on the webpage http://www.ubuntu.com/usn/ . Thanks, Mika ** Affects: ubuntu Importance: Undecided Status: New -- usn rss feed hardly readable https://bugs.launchpad.net/bugs/393006 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 305264] Re: gnutls regression: failure in certificate chain validation
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278350] Re: [intrepid-beta] PCMCIA network-card working in hardy does not work
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 compatible with 64 bit kernel. Actually, the I/O timing problems the driver predicts do happen, thus this could be the issue Therefore, maybe it is better if you report another bug. Remember to _attach_ in your bug report the files generated by the following comands: uname -a > uname-a.log cat /proc/version_signature > proc_version_signature.log sudo lspci -vvnn > lspci-vvnn.log (those are 2 v's not a w) dmesg > dmesg.log sudo lspcmcia -vv > lspcmcia-vv.log That means, that you have to attach five different files. Additionally, you say, that the card worked under kde 4.1 - unfortunately, hardware-issues are usually independent from the window manager / desktop suite and therefore you should maybe add the information, wich distro/version you were running (hardy?), the best would be to attach the output of dmesg -a > dmesg-a.log.workedBefore It would be really kind if you could take the time to gather these information and add it do a new bug report. Hopefully some developers can then fix the bug, so that you and everybody else with a similar hardware configuration can enjoy intrepid final. Thanks, Mika -- [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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278350] Re: [intrepid] PCMCIA network-card working in hardy does not work
** 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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278350] Re: [intrepid] PCMCIA network-card working in hardy does not work
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 connect to my smtp-server (auth issue), I use blank as smtp-server as suggested, reportbug is happy - but no bug report shows up and I don't get the confirmation. I send the bug-report by hand via claws-mail and my smtp-server, same result. i don't like debian's bts) so that I can't provide a link to the bug report there. Interestingly, debian's debian-isntaller works, as it uses the 2.6.24er kernel - so a debian lenny can actually be installed, but not used afterwards. -- [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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278350] Re: [intrepid-beta/RC] PCMCIA network-card working in hardy does not work
** 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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278350] Re: [intrepid-beta/RC] PCMCIA network-card working in hardy does not work
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 of the usual logs inside the debian-installer (switching to a console via alt+F2). As far as I can see there is nothing new about these logs. Actually quite nasty is, that you now fail completely when you try to use the minimal install CD, as no network connection works during installation. ** Attachment added: "intrepid rc debian installer" http://launchpadlibrarian.net/18882630/intrepid_d-i_dmesg.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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278350] Re: [intrepid-beta/RC] PCMCIA network-card working in hardy does not work
** 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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278350] Re: [intrepid-beta/RC] PCMCIA network-card working in hardy does not work
** 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 a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278350] Re: [intrepid-beta/RC] PCMCIA network-card working in hardy does not work
** 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 are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278350] Re: [intrepid-beta/RC] PCMCIA network-card working in hardy does not work
** 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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278350] Re: [intrepid-beta/RC] PCMCIA network-card working in hardy does not work
** 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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278350] Re: [intrepid] PCMCIA network-card working in hardy does not work
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.27-4-gerneric (Ubuntu + exakt version of the kernel: 2.6.27-4-generic (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 that was ever present in hardy), no problems, works after suspend/resume and hibernate/resume, everything's fine. But under Intrepid it doesn't work. To be more specific: the driver refuses to drive the card claiming somebody else is responsible, but no other driver shows up, so the cards stays undriven. The symptoms: the card's leds are on, ifconfig reports only loopback device, the gnome tool in the upper right-hand corner does not see a device. I have the output of lspcmcia -vv under hardy and intrepid as well as the output of dmesg under both attached, the most interesting lines I cite: lspcmcia -vv hardy: Socket 1 Device 0:[pcnet_cs] (bus ID: 1.0) lspcmcia -vv intrepid: Socket 1 Device 0:[-- no driver --] (bus ID: 1.0) dmesg hardy: [ 90.051734] pccard: PCMCIA card inserted into slot 1 [ 102.844908] cs: IO port probe 0x100-0x3af: clean. [ 102.847719] cs: IO port probe 0x3e0-0x4ff: clean. [ 102.849158] cs: IO port probe 0x820-0x8ff: clean. [ 102.850492] cs: IO port probe 0xc00-0xcf7: clean. [ 102.853025] cs: IO port probe 0xa00-0xaff: clean. [ 103.286116] cs: memory probe 0xa000-0xa0ff: clean. [ 103.294603] pcmcia: registering new device pcmcia1.0 [ 103.308750] cs: IO port probe 0x100-0x3af: clean. [ 103.311598] cs: IO port probe 0x3e0-0x4ff: clean. [ 103.313037] cs: IO port probe 0x820-0x8ff: clean. [ 103.319870] cs: IO port probe 0xc00-0xcf7: clean. [ 103.322501] cs: IO port probe 0xa00-0xaff: clean. [ 104.536688] eth0: NE2000 Compatible: io 0x320, irq 3, hw_addr 00:40:f4:24:70:ec dmesg intrepid: [ 50.771501] pccard: PCMCIA card inserted into slot 1 [ 52.287586] input: PS2++ Logitech TouchPad 3 as /class/input/input2 [ 52.374044] cs: IO port probe 0x100-0x3af: excluding 0x200-0x207 0x220-0x22f 0x300-0x307 0x378-0x37f 0x388-0x38f [ 52.376950] cs: IO port probe 0x3e0-0x4ff: clean. [ 52.378348] cs: IO port probe 0x820-0x8ff: clean. [ 52.388953] cs: IO port probe 0x100-0x3af: excluding 0x200-0x207 0x220-0x22f 0x300-0x307 0x378-0x37f 0x388-0x38f [ 52.391827] cs: IO port probe 0x3e0-0x4ff: clean. [ 52.393223] cs: IO port probe 0x820-0x8ff: clean. [ 52.394451] cs: IO port probe 0xc00-0xcf7: clean. [ 52.396832] cs: IO port probe 0xa00-0xaff: clean. [ 52.398230] cs: memory probe 0xa000-0xa0ff: clean. [ 52.407451] cs: IO port probe 0xc00-0xcf7: clean. [ 52.409796] cs: IO port probe 0xa00-0xaff: clean. [ 52.416103] pcmcia: registering new device pcmcia1.0 [ 54.255498] pcnet_cs: this is an AX88190 card! [ 54.255529] pcnet_cs: use axnet_cs instead. attached the complete outputs. If you need further information - ask. -- [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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 277052] [NEW] [intrepid-beta] all en_XX locales being generated
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 happening during the installation process I saw, that it was generating every single [EMAIL PROTECTED] locale. Actually it shouldn't, because I only ticked (in expert mode btw) [EMAIL PROTECTED], [EMAIL PROTECTED] and [EMAIL PROTECTED] and it was taking an awful lot of time generating all these [EMAIL PROTECTED], [EMAIL PROTECTED] etc. locales. I was using the expert mode, nolapi noapic, pci=irqmask=0x0e98, keyboard-layout 105 (Intel) key - germany - nodeadkeys and a Finnish location and time zone. The standard locale was set to be [EMAIL PROTECTED], the terminal was also set to UTF-8. I had only the CD and no network access, thus denying network access when prompted. I would have expected it to install and generate [EMAIL PROTECTED] and, if on the CD, also [EMAIL PROTECTED] and [EMAIL PROTECTED] Instead it installed all flavors of [EMAIL PROTECTED] and silently skipped the other languages. Later on (after installing, in GNOME via an information box in the upper right-hand corner) I was warned, that the locales were not installed completely and I could fix it now if I had internet access. I don't know, which flavor of [EMAIL PROTECTED] it actually used, because I don't know, how much of the specific locales is translated, but at least some man-pages seamed to be [EMAIL PROTECTED] (that is, they used american english) ** Affects: debian-installer (Ubuntu) Importance: Undecided Status: New -- [intrepid-beta] all en_XX locales being generated https://bugs.launchpad.net/bugs/277052 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 280037] [NEW] evolution assigned-task view has no print button
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 all-tasks view, but that isn't very intuitive. If I want to print something, I open it and press the print button somewhere in the menu. That's how it should work. Using Ubuntu 7.10. Thanks. ** Affects: evolution (Ubuntu) Importance: Undecided Status: New -- evolution assigned-task view has no print button https://bugs.launchpad.net/bugs/280037 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 280037] Re: evolution assigned-task view has no print button
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 button https://bugs.launchpad.net/bugs/280037 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278350] Re: [intrepid-beta] PCMCIA network-card working in hardy does not work
** 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278350] [NEW] [intrepid-beta] PCMCIA network-card working in hardy does not work
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 that was ever present in hardy), no problems, works after suspend/resume and hibernate/resume, everything's fine. But under Intrepid it doesn't work. To be more specific: the driver refuses to drive the card claiming somebody else is responsible, but no other driver shows up, so the cards stays undriven. The symptoms: the card's leds are on, ifconfig reports only loopback device, the gnome tool in the upper right-hand corner does not see a device. I have the output of lspcmcia -vv under hardy and intrepid as well as the output of dmesg under both attached, the most interesting lines I cite: lspcmcia -vv hardy: Socket 1 Device 0: [pcnet_cs] (bus ID: 1.0) lspcmcia -vv intrepid: Socket 1 Device 0: [-- no driver --] (bus ID: 1.0) dmesg hardy: [ 90.051734] pccard: PCMCIA card inserted into slot 1 [ 102.844908] cs: IO port probe 0x100-0x3af: clean. [ 102.847719] cs: IO port probe 0x3e0-0x4ff: clean. [ 102.849158] cs: IO port probe 0x820-0x8ff: clean. [ 102.850492] cs: IO port probe 0xc00-0xcf7: clean. [ 102.853025] cs: IO port probe 0xa00-0xaff: clean. [ 103.286116] cs: memory probe 0xa000-0xa0ff: clean. [ 103.294603] pcmcia: registering new device pcmcia1.0 [ 103.308750] cs: IO port probe 0x100-0x3af: clean. [ 103.311598] cs: IO port probe 0x3e0-0x4ff: clean. [ 103.313037] cs: IO port probe 0x820-0x8ff: clean. [ 103.319870] cs: IO port probe 0xc00-0xcf7: clean. [ 103.322501] cs: IO port probe 0xa00-0xaff: clean. [ 104.536688] eth0: NE2000 Compatible: io 0x320, irq 3, hw_addr 00:40:f4:24:70:ec dmesg intrepid: [ 50.771501] pccard: PCMCIA card inserted into slot 1 [ 52.287586] input: PS2++ Logitech TouchPad 3 as /class/input/input2 [ 52.374044] cs: IO port probe 0x100-0x3af: excluding 0x200-0x207 0x220-0x22f 0x300-0x307 0x378-0x37f 0x388-0x38f [ 52.376950] cs: IO port probe 0x3e0-0x4ff: clean. [ 52.378348] cs: IO port probe 0x820-0x8ff: clean. [ 52.388953] cs: IO port probe 0x100-0x3af: excluding 0x200-0x207 0x220-0x22f 0x300-0x307 0x378-0x37f 0x388-0x38f [ 52.391827] cs: IO port probe 0x3e0-0x4ff: clean. [ 52.393223] cs: IO port probe 0x820-0x8ff: clean. [ 52.394451] cs: IO port probe 0xc00-0xcf7: clean. [ 52.396832] cs: IO port probe 0xa00-0xaff: clean. [ 52.398230] cs: memory probe 0xa000-0xa0ff: clean. [ 52.407451] cs: IO port probe 0xc00-0xcf7: clean. [ 52.409796] cs: IO port probe 0xa00-0xaff: clean. [ 52.416103] pcmcia: registering new device pcmcia1.0 [ 54.255498] pcnet_cs: this is an AX88190 card! [ 54.255529] pcnet_cs: use axnet_cs instead. attached the complete outputs. If you need further information - ask. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- [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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278350] Re: [intrepid-beta] PCMCIA network-card working in hardy does not work
*** 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 say, it ist not. So maybe the error is, that pcnet_cs falsely detects an AXIS card. -- [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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278350] Re: [intrepid-beta] PCMCIA network-card working in hardy does not work
*** 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 appear in boot log, or whatever the name of the output ist, that you get when you give nosplash at boot prompt) and 'ps aux | grep net' does not show any running instances (of course after a reboot after disabling the NetworkManager). Although NetworkManager can't do anything anymore, the dmesg-output is the same (not exactly, NetworkManager does not appear in dmesg, but it didn't appear around the PCMCIA-probes before, anyway, as I point out later), eth0 does not appear in ifconfig-output, and lspcmcia-vv gives exactly the same output. Or in short: It didn't change anything. 2. The problem arises far earlier than NetworkManager is being loaded. The problem arises during the stage in booting process when the hardware drivers are being loaded. That is before any runlevel. After that, when entering runlevel 2, roughly, ifup is excuted (without any special impact, as /dev/eth0 does not exist) and way after that (when entering runlevel 5), NetworkManager is executed and /could/ indeed interfere with any settings, if there would even be a network device. But there is none, and there are no special settings, it would just work fine with DHCP, if NM would set any device to that, but there is no networking device (virtually, physically it is sitting there blinking). Furthermore, before removing NetworkManager I could access NetworkManager and it was reporting "No ethernet device" or something like this. That means I can confirm that NetworkManager did not find any devices and can therefore not mess the configuration of these. So I would say this is not a duplicate of bug #256054. -- [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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278350] Re: [intrepid-beta] PCMCIA network-card working in hardy does not work
** 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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278350] Re: [intrepid-beta] PCMCIA network-card working in hardy does not work
** 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 you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278350] Re: [intrepid-beta] PCMCIA network-card working in hardy does not work
** 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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278350] Re: [intrepid-beta] PCMCIA network-card working in hardy does not work
** 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, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278350] Re: [intrepid-beta] PCMCIA network-card working in hardy does not work
** 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, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278350] Re: [intrepid-beta] PCMCIA network-card working in hardy does not work
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-rom drive, although they are both standard IDE (or at least claim to be). I read about the pci=irqmask=0x0e98 option that it is required for this notebook, and actually you won't get far without (it won't boot), this is known for this laptop at least since 2001. I don't use other kernel boot parameters, only ro, pci=irqmask=0x0e98 and nosplash. ** Attachment removed: "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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278350] Re: [intrepid-beta] PCMCIA network-card working in hardy does not work
** 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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278350] Re: [intrepid-beta] PCMCIA network-card working in hardy does not work
** 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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278350] Re: [intrepid-beta] PCMCIA network-card working in hardy does not work
** 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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278350] Re: [intrepid-beta] PCMCIA network-card working in hardy does not work
** 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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278350] Re: [intrepid-beta] PCMCIA network-card working in hardy does not work
** 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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278350] Re: [intrepid-beta] PCMCIA network-card working in hardy does not work
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. Thus I reboot and try this time sudo modprobe -v --first-time pcnet_cs to get at least some output. I get FATAL: Module pcnet_cs already in kernel. To check that, I reboot and say lsmod | grep pcnet_cs (output see attachment, four lines) and then I sudo modprobe. After loading the driver manually lsmod looks the same (lsmod|grep pcnet_cs gives the same four lines, I diffed them, it is exactly the same, as in the attachment) In ifconfig the network interface does not show up. I don't know if there is a way to manually bind a driver to a pcmcia- card (at least pccardctl does not have this function), if there is a way, I'd give it a try. ** Attachment added: "lsmod_grep_pcnet_cs.log" http://launchpadlibrarian.net/18234445/lsmod_grep_pcnet_cs.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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278350] Re: [intrepid-beta] PCMCIA network-card working in hardy does not work
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 somebody else with the name 'cs') even probes IO ports on boot time. So it is loaded in the kernel. Thanks for your efforts so far, Chris. -- [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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278350] Re: [intrepid] PCMCIA network-card working in hardy does not work
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 Netgear FA 411. However, the bug is still present (and I guess will not be solved) in Intrepid. Unless somebody backports a .28 kernel to Intrepid, Intrepid will remain unusable with machines with a Netgear FA 411. As the upcoming Jaunty release will not be affected anymore and 8.10 is not an LTS release, I 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278350] Re: [intrepid] PCMCIA network-card working in hardy does not work
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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 314462] [NEW] [Jaunty]installing with "free software only" and backports enables unfree backports
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, I noted, that from the backport-repository, not only 'main universe', but actually 'main restricted universe multiverse' was enabled. If now somebody backports some newer version of some nonfree software, I could install it via synaptic or apt-get, not nowing it to be unfree. The sources.lst file should only reference 'main universe' as sources if I choose 'Free Software only', also with backported software. Similar problems with the CD and -security as a source are described and fixed in #220805, I guess the same fixes described there could just be used to fix -backports. Thanks, Mika ** Affects: debian-installer (Ubuntu) Importance: Undecided Status: New -- [Jaunty]installing with "free software only" and backports enables unfree backports https://bugs.launchpad.net/bugs/314462 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 315484] Re: gdm crashes on execution of Custom Command
** 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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 315484] [NEW] gdm crashes on execution of Custom Command
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 with own shell script, and with /usr/bin/yes) gdm crashes when the command is picked from the actions-menu. It shows the ubuntu splash screen, but nothing happens. Attached the syslog with debugging enabled for gdm. However, the command is executed (/usr/bin/yes used one full CPU). There is an easy workaround: If you enable the CustomCommandNoRestart option via adding CustomCommandNoRestart[0-9]=true (default is false) to gdm.conf-custom, gdm does not crash anymore. If you need more information, a backtrace, tests on vanilla Ubuntu installations or whatever, don't hesitate to ask Thanks, Mika ** Affects: gdm (Ubuntu) Importance: Undecided Status: 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 315484] Re: gdm crashes on execution of Custom Command
** 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, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 315484] Re: gdm crashes on execution of Custom Command
** 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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 315484] Re: gdm crashes on execution of Custom Command
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 made some mistake following your instructions, or gdm does not really crash cleanly but just locks up everything. ** Changed in: gdm (Ubuntu) Status: Invalid => 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278350] Re: [intrepid] PCMCIA network-card working in hardy does not work
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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 305080] Re: [regression from tetex] missing fonts/packages in texlive
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), but I don't know, if they work. It seems that the metrics are still missing. However, I will comment again, if I make any progress. ** Also affects: texlive-base (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=425460 Importance: Unknown Status: Unknown -- [regression from tetex] missing fonts/packages in texlive https://bugs.launchpad.net/bugs/305080 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 305080] Re: [regression from tetex] missing fonts/packages in texlive
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 documents and everything's fine. I guess the original bug is somewhat solved (at least the part dealing with mathtime), as the bioinformatics template does not require the template anymore. I tested to compile the test document provided (as in "I tried to reproduce the bug with the latest version of the template and its test document) and it worked. So it is working "out of the box" again, if you use the latest bioinformatics template. So this problem is solved. Still other documents using mathtime.sty need to be updated, but if I get the Debian bug report right, there are licensing issues with it and therefore upstream (texlive) decided not to include it anymore (or has never included it, just a workaround, I'm not really sure. However, now it does not work anymore and they broke it by intend). So /this/ problem is a wontfix, just fix your documents (hints in /usr/share/doc/texlive-doc/fonts/belleek/ and the debian bug). -- [regression from tetex] missing fonts/packages in texlive https://bugs.launchpad.net/bugs/305080 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 315484] Re: gdm CustomCommandNoRestart documentation confusing
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 crashes on execution of Custom Command + gdm CustomCommandNoRestart documentation confusing ** Description changed: 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 with own shell script, and with /usr/bin/yes) gdm crashes when the command is picked from the actions-menu. It shows the ubuntu splash screen, but nothing happens. Attached the syslog with debugging enabled for gdm. However, the command is executed (/usr/bin/yes used one full CPU). There is an easy workaround: If you enable the CustomCommandNoRestart option via adding CustomCommandNoRestart[0-9]=true (default is false) to gdm.conf-custom, gdm does not crash anymore. If you need more information, a backtrace, tests on vanilla Ubuntu installations or whatever, don't hesitate to ask Thanks, Mika + + == Update == + Without CustomCommandNoRestart gdm exits upon execution of the custom command. I guess the idea is, that all custom commands deal somehow with Restarting the machine or similar where it is a good idea to exit gdm. + However, in Intrepid and Gutsy there is no hint that gdm has exited - this hint can be seen in Jaunty (it says something along the lines of "The system is being shut down"). + Thus I propose to clarify the documentation, see my comment below. -- gdm CustomCommandNoRestart documentation confusing https://bugs.launchpad.net/bugs/315484 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 315484] Re: gdm CustomCommandNoRestart documentation confusing
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 Debian? -- gdm CustomCommandNoRestart documentation confusing https://bugs.launchpad.net/bugs/315484 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 315484] Re: gdm CustomCommandNoRestart documentation confusing
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 -- gdm CustomCommandNoRestart documentation confusing https://bugs.launchpad.net/bugs/315484 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 315484] Re: gdm crashes on execution of Custom Command
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), but maybe we could enhance the documentation in /etc/gdm/gdm.conf. At the moment it reads: > # Custom command gdm/system restart option. Setting it to true will not > # restart gdm after command execution. The default commands (reboot, shut > # down) all reboot the system by default which is why the default setting > # is true. But gdm does not /restart/, but exits. So my idea would be: > # Custom command gdm stop option. Setting it to true will not > # stop gdm after command execution. The default commands (reboot, shut > # down) all reboot the system by default which is why the default setting > # is false. (additionally the "the default setting is true" is somewhat misleading, as the default setting of CustomCommandNoRestartN is false. Maybe we should even say: "...which is why the default behaviour is to stop gdm.") Greets, Mika -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 315484] Re: gdm crashes on execution of Custom Command
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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 798023] Re: apt-get update fails with error 416 Requested Range Not Satisfiable
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 update fails with error 416 Requested Range Not Satisfiable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/798023/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
