[Bug 262631] Re: AGP speed not detected properly (work only with 64 bit kernel)
I changed Aperture size to 32Mb in Bios and card started to work fine. Thank Andy I think there is a problem with screen size in 'text mode'. I will try to explicit add some vga option to the kernel. If you need any other test please let me know. Anyway I#'m going to try TV-Output next. -- AGP speed not detected properly (work only with 64 bit kernel) https://bugs.launchpad.net/bugs/262631 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 262631] Re: AGP speed not detected properly (work only with 64 bit kernel)
I have the same problem. I'm using 8.10 with updated kernel (i686 version). I'm attaching outputs of: - egrep radeon|agp /var/log/Xorg.0.log - dmesg |grep agp - lspci and - my xorg.conf (separate file) └─(:18:36:%)── egrep radeon|agp /var/log/Xorg.0.log ──(śro,gru31)─┘ (II) LoadModule: radeon (II) Loading /usr/lib/xorg/modules/drivers//radeon_drv.so (II) Module radeon: vendor=X.Org Foundation (II) RADEON(0): [agp] Mode 0x1f004a0a [AGP 0x8086/0x2570; Card 0x1002/0x4150] (II) RADEON(0): [agp] 32768 kB allocated with handle 0x0001 (EE) RADEON(0): [agp] Could not bind (EE) RADEON(0): [agp] AGP failed to initialize. Disabling the DRI. (II) RADEON(0): [agp] You may want to make sure the agpgart kernel module is loaded before the radeon kernel module. └─(:18:37:%)── dmesg |grep agp ──(śro,gru31)─┘ [ 15.015593] Linux agpgart interface v0.103 [ 15.323518] agpgart-intel :00:00.0: Intel 865 Chipset [ 15.593827] agpgart-intel :00:00.0: AGP aperture is 16M @ 0xfd00 [ 33.782646] agpgart-intel :00:00.0: AGP 3.0 bridge [ 33.782682] agpgart-intel :00:00.0: putting AGP V3 device into 8x mode [23762.534523] agpgart-intel :00:00.0: AGP 3.0 bridge [23762.534558] agpgart-intel :00:00.0: putting AGP V3 device into 8x mode └─(:18:47:%)── lspci ──(śro,gru31)─┘ 00:00.0 Host bridge: Intel Corporation 82865G/PE/P DRAM Controller/Host-Hub Interface (rev 02) 00:01.0 PCI bridge: Intel Corporation 82865G/PE/P PCI to AGP Controller (rev 02) 00:1d.0 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #1 (rev 02) 00:1d.1 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #2 (rev 02) 00:1d.2 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #3 (rev 02) 00:1d.3 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #4 (rev 02) 00:1d.7 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB2 EHCI Controller (rev 02) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev c2) 00:1f.0 ISA bridge: Intel Corporation 82801EB/ER (ICH5/ICH5R) LPC Interface Bridge (rev 02) 00:1f.1 IDE interface: Intel Corporation 82801EB/ER (ICH5/ICH5R) IDE Controller (rev 02) 00:1f.2 IDE interface: Intel Corporation 82801EB (ICH5) SATA Controller (rev 02) 00:1f.3 SMBus: Intel Corporation 82801EB/ER (ICH5/ICH5R) SMBus Controller (rev 02) 01:00.0 VGA compatible controller: ATI Technologies Inc RV350 AP [Radeon 9600] 01:00.1 Display controller: ATI Technologies Inc RV350 AP [Radeon 9600] (Secondary) 02:02.0 Multimedia audio controller: Cirrus Logic CS 4614/22/24/30 [CrystalClear SoundFusion Audio Accelerator] (rev 01) 02:08.0 Ethernet controller: Intel Corporation 82562EZ 10/100 Ethernet Controller (rev 01) ** Attachment added: xorg.conf http://launchpadlibrarian.net/20833622/xorg.conf -- AGP speed not detected properly (work only with 64 bit kernel) https://bugs.launchpad.net/bugs/262631 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 262631] Re: AGP speed not detected properly (work only with 64 bit kernel)
Some update: My Xorg working but not Compiz. I have ATI Radeon 9600 with Pentium4 2.40 on unkown (to me) Motherboard. I also check Fedora10 and it work fine. There are no xorg.conf in Fedora so I'm attaching Xorg.0.log file ** Attachment added: Xorg.log from Fedora10 http://launchpadlibrarian.net/20833865/Xorg.0.log -- AGP speed not detected properly (work only with 64 bit kernel) https://bugs.launchpad.net/bugs/262631 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 262631] Re: AGP speed not detected properly (work only with 64 bit kernel)
And Xorg.log from Ubuntu 8.10 ** Attachment added: Xorg.0.log http://launchpadlibrarian.net/20833880/Xorg.0.log -- AGP speed not detected properly (work only with 64 bit kernel) https://bugs.launchpad.net/bugs/262631 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 250440] Re: Text consoles doesn't work for ATI Rage 128 Pro Ultra TF + LG Flatron L1953S
Hey Teej I switched (full re-installation rather then upgrade) to 8.10 and the autoconf Xorg works fine for the X server, but still not for text console. I resolve the issue by setting vga option in kernel. Therefore it's not a Xorg problem. My grub entry for ubuntu is: title Ubuntu root (hd0,5) kernel (hd0,0)/vmlinuz root=/dev/sda1 vga=0x318 initrd (hd0,0)/initrd.img (I'm using grub from Fedora 10). BTW. The seem issue affects Fedora, I also needed to add vga option. I also raised some problem with Xorg setting in bug 243952. -- Text consoles doesn't work for ATI Rage 128 Pro Ultra TF + LG Flatron L1953S https://bugs.launchpad.net/bugs/250440 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 304947] Re: Tilda crushing during start
Thanks for quick response. The file as requested. Anything else? I'm rather poweruser so don't hesitate to ask for more complicated actions. ** Attachment added: tilda.strace.txt http://launchpadlibrarian.net/20214751/tilda.strace.txt -- Tilda crushing during start https://bugs.launchpad.net/bugs/304947 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 304947] Re: Tilda crushing during start
I installed Fedor 10 and Tilda worked ok from it. Later I started tilda from my wife account it it worked fine. So it can be related to my config. Which files should I check? -- Tilda crushing during start https://bugs.launchpad.net/bugs/304947 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 304947] Re: Tilda crushing during start
tilda -c bash works fine. My default shell is zsh. ** Summary changed: - Tilda crushing during start + Tilda crashing if user's shell is zsh ** Description changed: - I cannot start Tilda from clean Ubuntu 8.10 installation. Please check - the attachment to see output from Terminal. + I cannot start Tilda from nearly clean Ubuntu 8.10 installation. when + the shell is zsh. ** Tags added: crash zsh ** Tags removed: crush ** Also affects: zsh Importance: Undecided Status: New -- Tilda crashing if user's shell is zsh https://bugs.launchpad.net/bugs/304947 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 241796] Re: sshd doesn't start properly because dhcp client doesn't get ip address
Another workaround is to set in sshd_config to ListenAddress 0.0.0.0 -- sshd doesn't start properly because dhcp client doesn't get ip address https://bugs.launchpad.net/bugs/241796 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 304947] [NEW] Tilda crushing during start
Public bug reported: I cannot start Tilda from clean Ubuntu 8.10 installation. Please check the attachment to see output from Terminal. ** Affects: ubuntu Importance: Undecided Status: New ** Tags: crush -- Tilda crushing during start https://bugs.launchpad.net/bugs/304947 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 304947] Re: Tilda crushing during start
** Attachment added: tilda.log http://launchpadlibrarian.net/20191849/tilda.log -- Tilda crushing during start https://bugs.launchpad.net/bugs/304947 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 301891] Re: Users without valid login are not presented in Face list, but can login and start shell
I can understand that GDM do not allow people to login in if they have no valid shell, but at the moment you can do this, moreover you can start shell! It's not a consistent behaviour of GDM (or saying more Gnome), what is a bug. (I changed the description to better describe the problem). BTW. It might make some confusion if you are using NIS to login. You have valid login but you don't login to one of the system because shell of your choice is not there. ** Summary changed: - Users without valid login are not presented in Face list + Users without valid login are not presented in Face list, but can login and start shell ** Tags added: login passwd setting shell user -- Users without valid login are not presented in Face list, but can login and start shell https://bugs.launchpad.net/bugs/301891 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 241796] Re: sshd doesn't start properly
I reopen the bug. The bug against installer is not so important. I make clean installation of U8.10 and could somebody from the openssh or network-manager teams can explain who decided that sshd should start before dhcp client finish (and actually start) process of retrieving ip address? relevant lines from a) auth.log: Nov 25 00:38:26 madryt sshd[4999]: debug1: Bind to port 22 on 192.168.1.65. Nov 25 00:38:26 madryt sshd[4999]: error: Bind to port 22 on 192.168.1.65 failed: Cannot assign requested address. Nov 25 00:38:26 madryt sshd[4999]: debug1: Bind to port 22 on 127.0.1.1. Nov 25 00:38:26 madryt sshd[4999]: Server listening on 127.0.1.1 port 22. Nov 25 00:38:26 madryt sshd[4999]: debug1: Bind to port 22 on 127.0.0.1. Nov 25 00:38:26 madryt sshd[4999]: Server listening on 127.0.0.1 port 22. b) daemon.log: Nov 25 00:38:36 madryt dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4 Nov 25 00:38:36 madryt dhclient: DHCPOFFER of 192.168.1.65 from 192.168.1.254 Nov 25 00:38:36 madryt dhclient: DHCPREQUEST of 192.168.1.65 on eth0 to 255.255.255.255 port 67 Nov 25 00:38:36 madryt dhclient: DHCPACK of 192.168.1.65 from 192.168.1.254 Nov 25 00:38:36 madryt NetworkManager: info DHCP: device eth0 state changed preinit - bound Nov 25 00:38:36 madryt NetworkManager: info Activation (eth0) Stage 4 of 5 (IP Configure Get) scheduled... Nov 25 00:38:36 madryt NetworkManager: info Activation (eth0) Stage 4 of 5 (IP Configure Get) started... Nov 25 00:38:36 madryt NetworkManager: info address 192.168.1.65 Nov 25 00:38:36 madryt NetworkManager: info prefix 24 (255.255.255.0) Nov 25 00:38:36 madryt NetworkManager: info gateway 192.168.1.254 Nov 25 00:38:36 madryt NetworkManager: info nameserver '192.168.1.254' Nov 25 00:38:36 madryt NetworkManager: info domain name 'lan' ** Changed in: openssh (Ubuntu) Status: Invalid = New -- sshd doesn't start properly because dhcp client doesn't get ip address https://bugs.launchpad.net/bugs/241796 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 241796] Re: sshd doesn't start properly
related to bug 267929 ** Changed in: network-manager (Ubuntu) Sourcepackagename: openssh = network-manager ** Summary changed: - sshd doesn't start properly + sshd doesn't start properly because dhcp client doesn't get ip address ** Tags added: dhcp network network-manager settings sshd -- sshd doesn't start properly because dhcp client doesn't get ip address https://bugs.launchpad.net/bugs/241796 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 250440] Re: Text consoles doesn't work for ATI Rage 128 Pro Ultra TF + LG Flatron L1953S
8.10 still doesn't work I think that passing some option for the kernel resolve the issue. -- Text consoles doesn't work for ATI Rage 128 Pro Ultra TF + LG Flatron L1953S https://bugs.launchpad.net/bugs/250440 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 243952] Re: Xorg with the default refresh rate looks ulgy (ATI Rage 128 + LCD)
I'm not entirely sure if it can be change to resolve, but display seems to be properly set after installation of 8.10. (I install 8.10 from scratch rather than perform update). I'm using GNOME rather than Crystal FVWM. I think you can set is as Resolved and I would change it if I found other problems. -- Xorg with the default refresh rate looks ulgy (ATI Rage 128 + LCD) https://bugs.launchpad.net/bugs/243952 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 301891] [NEW] Users without valid login are not presented in Face list
Public bug reported: Binary package hint: gdm If the user don't have a valid login are not presented in the GDM login list. You can login, but you have to type the user name what is very annoying as there are no way to type user name after click on the one of the faces. It's quite instersting that you can start GNOME terminal without valid shell! How to repeat Edit /etc/passwd and set user shell to something not existing. (In my case I have zsh with wasn't present after re installation). ** Affects: gdm (Ubuntu) Importance: Undecided Status: New ** Tags: face list -- Users without valid login are not presented in Face list https://bugs.launchpad.net/bugs/301891 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 62755] Re: Tilda crash after launching it
I should add this line: zsh: segmentation fault tilda -- Tilda crash after launching it https://bugs.launchpad.net/bugs/62755 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 62755] Re: Tilda crash after launching it
It seems that I have the same problem with Tilda from 8.10. I cannot start Tilda from the menu and from a terminal, but from a terminal I at least have had got some output. The standard error output is in attached file. ** Attachment added: Error output of tilda's start http://launchpadlibrarian.net/19918374/tilda.log -- Tilda crash after launching it https://bugs.launchpad.net/bugs/62755 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 267929] Re: The installer cannot set proprer network access
I make clean installation of U8.10 and could somebody from the openssh or network-manager teams can explain who decided that sshd should start before dhcp client finish (and actually start) process of retrieving ip address? relevant lines from a) auth.log: Nov 25 00:38:26 madryt sshd[4999]: debug1: Bind to port 22 on 192.168.1.65. Nov 25 00:38:26 madryt sshd[4999]: error: Bind to port 22 on 192.168.1.65 failed: Cannot assign requested address. Nov 25 00:38:26 madryt sshd[4999]: debug1: Bind to port 22 on 127.0.1.1. Nov 25 00:38:26 madryt sshd[4999]: Server listening on 127.0.1.1 port 22. Nov 25 00:38:26 madryt sshd[4999]: debug1: Bind to port 22 on 127.0.0.1. Nov 25 00:38:26 madryt sshd[4999]: Server listening on 127.0.0.1 port 22. b) daemon.log: Nov 25 00:38:36 madryt dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4 Nov 25 00:38:36 madryt dhclient: DHCPOFFER of 192.168.1.65 from 192.168.1.254 Nov 25 00:38:36 madryt dhclient: DHCPREQUEST of 192.168.1.65 on eth0 to 255.255.255.255 port 67 Nov 25 00:38:36 madryt dhclient: DHCPACK of 192.168.1.65 from 192.168.1.254 Nov 25 00:38:36 madryt NetworkManager: info DHCP: device eth0 state changed preinit - bound Nov 25 00:38:36 madryt NetworkManager: info Activation (eth0) Stage 4 of 5 (IP Configure Get) scheduled... Nov 25 00:38:36 madryt NetworkManager: info Activation (eth0) Stage 4 of 5 (IP Configure Get) started... Nov 25 00:38:36 madryt NetworkManager: infoaddress 192.168.1.65 Nov 25 00:38:36 madryt NetworkManager: infoprefix 24 (255.255.255.0) Nov 25 00:38:36 madryt NetworkManager: infogateway 192.168.1.254 Nov 25 00:38:36 madryt NetworkManager: infonameserver '192.168.1.254' Nov 25 00:38:36 madryt NetworkManager: infodomain name 'lan' -- The installer cannot set proprer network access https://bugs.launchpad.net/bugs/267929 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 267929] Re: The installer cannot set proprer network access
I reopened bug 241796 as it seems to be more relevant, but I guess that resolve this bug resolve that one too. I'm not entirely understand the whole new NetworkManager idea, so there might be another way of fixing it. ** Also affects: openssh Importance: Undecided Status: New ** Also affects: network-manager Importance: Undecided Status: New ** Summary changed: - The installer cannot set proprer network access + The installer cannot set proper network access -- The installer cannot set proper network access https://bugs.launchpad.net/bugs/267929 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 241796] Re: sshd doesn't start properly
I reopen the bug. The bug against installer is not so important. I make clean installation of U8.10 and could somebody from the openssh or network-manager teams can explain who decided that sshd should start before dhcp client finish (and actually start) process of retrieving ip address? relevant lines from a) auth.log: Nov 25 00:38:26 madryt sshd[4999]: debug1: Bind to port 22 on 192.168.1.65. Nov 25 00:38:26 madryt sshd[4999]: error: Bind to port 22 on 192.168.1.65 failed: Cannot assign requested address. Nov 25 00:38:26 madryt sshd[4999]: debug1: Bind to port 22 on 127.0.1.1. Nov 25 00:38:26 madryt sshd[4999]: Server listening on 127.0.1.1 port 22. Nov 25 00:38:26 madryt sshd[4999]: debug1: Bind to port 22 on 127.0.0.1. Nov 25 00:38:26 madryt sshd[4999]: Server listening on 127.0.0.1 port 22. b) daemon.log: Nov 25 00:38:36 madryt dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4 Nov 25 00:38:36 madryt dhclient: DHCPOFFER of 192.168.1.65 from 192.168.1.254 Nov 25 00:38:36 madryt dhclient: DHCPREQUEST of 192.168.1.65 on eth0 to 255.255.255.255 port 67 Nov 25 00:38:36 madryt dhclient: DHCPACK of 192.168.1.65 from 192.168.1.254 Nov 25 00:38:36 madryt NetworkManager: info DHCP: device eth0 state changed preinit - bound Nov 25 00:38:36 madryt NetworkManager: info Activation (eth0) Stage 4 of 5 (IP Configure Get) scheduled... Nov 25 00:38:36 madryt NetworkManager: info Activation (eth0) Stage 4 of 5 (IP Configure Get) started... Nov 25 00:38:36 madryt NetworkManager: info address 192.168.1.65 Nov 25 00:38:36 madryt NetworkManager: info prefix 24 (255.255.255.0) Nov 25 00:38:36 madryt NetworkManager: info gateway 192.168.1.254 Nov 25 00:38:36 madryt NetworkManager: info nameserver '192.168.1.254' Nov 25 00:38:36 madryt NetworkManager: info domain name 'lan' ** Changed in: openssh (Ubuntu) Status: Invalid = New -- sshd doesn't start properly because dhcp client doesn't get ip address https://bugs.launchpad.net/bugs/241796 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 241796] Re: sshd doesn't start properly
related to bug 267929 ** Changed in: network-manager (Ubuntu) Sourcepackagename: openssh = network-manager ** Summary changed: - sshd doesn't start properly + sshd doesn't start properly because dhcp client doesn't get ip address ** Tags added: dhcp network network-manager settings sshd -- sshd doesn't start properly because dhcp client doesn't get ip address https://bugs.launchpad.net/bugs/241796 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 267929] Re: The installer cannot set proper network access
** Changed in: openssh Status: New = Invalid ** Changed in: openssh Status: Invalid = New -- The installer cannot set proper network access https://bugs.launchpad.net/bugs/267929 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 243952] Re: Xorg with the default refresh rate looks ulgy (ATI Rage 128 + LCD)
lspci output ** Attachment added: ati.log http://launchpadlibrarian.net/19655729/ati.log -- Xorg with the default refresh rate looks ulgy (ATI Rage 128 + LCD) https://bugs.launchpad.net/bugs/243952 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 243952] Re: Xorg with the default refresh rate looks ulgy (ATI Rage 128 + LCD)
The latest Xorg.0.log. Anything else? I'm still on LTS. I found some workarounds, but default refresh is wrong. I found RefreshRate on LCD panel general problem. This is off topic.: In my old works we had many Samsung SyncMaster 19'' (I don't remember the exact number) which were recognize as SyncMaster (CRT). We didn't use Ubuntu, but remember to have a problem with SLED 10; RHEL 3,4,5; Debian 4.0. - Sorry for OT, but we are much closer to Xorg than me. ** Attachment added: Xorg.0.log http://launchpadlibrarian.net/19655826/Xorg.0.log -- Xorg with the default refresh rate looks ulgy (ATI Rage 128 + LCD) https://bugs.launchpad.net/bugs/243952 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 270901] [NEW] The time between clicking logout and appering the panel/window is very long
Public bug reported: Ubuntu 8.04.1 LTS + standard Gnome/GDM @ AMD Athlon(tm) 64 Processor 3200+ and nVidia Corporation nForce 430 motherboard (SATA + ATA HDD) It takes around 1 minute to appear the logout setting window after clicking the logout button (on GNOME panel). It seems to be a problem only for main computer user, who is autologin user. Between click and window appears GUI is frozen. Gnome and any of applications don't react on any action (mouse click, keyboard), however it's possible to switch to text console. Top doesn't show anything suspicious there is a lot of memory and CPU power, HDD also looks quite. Which log would you like to see? ** Affects: meta-gnome2 (Ubuntu) Importance: Undecided Status: Invalid ** Tags: gnome logout -- The time between clicking logout and appering the panel/window is very long https://bugs.launchpad.net/bugs/270901 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 270901] Re: The time between clicking logout and appering the panel/window is very long
Thank Pedro, Is there any easy way to find the bug mentioned in your comment? I would like to trace a bug. -- The time between clicking logout and appering the panel/window is very long https://bugs.launchpad.net/bugs/270901 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 269112] Re: Cannot change permission and delete some files from Trash
Thanks Sebasian, but could you add the link to 'the proper' bug please? -- Cannot change permission and delete some files from Trash https://bugs.launchpad.net/bugs/269112 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 269112] [NEW] Cannot change permission and delete some files from Trash
Public bug reported: Binary package hint: gnome-applets My father had a strange problem. He couldn't delete few files from his Trash. First we figured out that he didn't have 'write' rights to them, even if he saved them from a mail. My first suggestion was to change permissions, but he couldn't (using Nautilus). Today I had a chance to sit in front of dad's computer, I found that suggestion 44037 worked fine (of course I need to make chmod -R +w ~/.local/share/Trash/files/*). [link to suggestion] https://answers.launchpad.net/ubuntu/+question/44037 ** Affects: gnome-applets (Ubuntu) Importance: Undecided Status: New ** Tags: nautilus trash -- Cannot change permission and delete some files from Trash https://bugs.launchpad.net/bugs/269112 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 241796] Re: sshd doesn't start properly
Please feel free to close the bug. I created another bug report against installer (bug 267929). -- sshd doesn't start properly https://bugs.launchpad.net/bugs/241796 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 267929] [NEW] The installer cannot set proprer network access
Public bug reported: Binary package hint: base-installer After installation my /etc/network/interfaces is: auto lo iface lo inet loopback but I have ethernet access (with dhcp). The eth0 interface is set properly, but it appends after starts of ssh server what lead to bug 241796. I was using 8.04 from LXF DVD. My ssh bug: [https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/241796] [EMAIL PROTECTED]:~$lspci 00:00.0 Host bridge: Intel Corporation 82865G/PE/P DRAM Controller/Host-Hub Interface (rev 02) 00:01.0 PCI bridge: Intel Corporation 82865G/PE/P PCI to AGP Controller (rev 02) 00:1d.0 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #1 (rev 02) 00:1d.1 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #2 (rev 02) 00:1d.2 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #3 (rev 02) 00:1d.3 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #4 (rev 02) 00:1d.7 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB2 EHCI Controller (rev 02) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev c2) 00:1f.0 ISA bridge: Intel Corporation 82801EB/ER (ICH5/ICH5R) LPC Interface Bridge (rev 02) 00:1f.1 IDE interface: Intel Corporation 82801EB/ER (ICH5/ICH5R) IDE Controller (rev 02) 00:1f.2 IDE interface: Intel Corporation 82801EB (ICH5) SATA Controller (rev 02) 00:1f.3 SMBus: Intel Corporation 82801EB/ER (ICH5/ICH5R) SMBus Controller (rev 02) 01:00.0 VGA compatible controller: ATI Technologies Inc Rage 128 Pro Ultra TF 02:02.0 Multimedia audio controller: Cirrus Logic CS 4614/22/24/30 [CrystalClear SoundFusion Audio Accelerator] (rev 01) 02:08.0 Ethernet controller: Intel Corporation 82562EZ 10/100 Ethernet Controller (rev 01) [EMAIL PROTECTED]:~$ifconfig eth0 Link encap:Ethernet HWaddr 00:07:e9:70:1c:4d inet addr:192.168.1.65 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::207:e9ff:fe70:1c4d/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:86001 errors:0 dropped:0 overruns:0 frame:0 TX packets:58436 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:114960333 (109.6 MB) TX bytes:6177398 (5.8 MB) loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:184 errors:0 dropped:0 overruns:0 frame:0 TX packets:184 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:9200 (8.9 KB) TX bytes:9200 (8.9 KB) [EMAIL PROTECTED]:~$lsb_release -rd Description:Ubuntu 8.04.1 Release:8.04 ** Affects: base-installer (Ubuntu) Importance: Undecided Status: New ** Tags: dhcp eth0 installer network setting -- The installer cannot set proprer network access https://bugs.launchpad.net/bugs/267929 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 241796] Re: sshd doesn't start properly
Please feel free to close the bug. I created another bug report against installer (bug 267929). -- sshd doesn't start properly https://bugs.launchpad.net/bugs/241796 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 241796] Re: sshd doesn't start properly
I wrote a patch for /etc/init.d/ssh which make scrpit waiting for a eth0
interface:
#My patch
check_for_eth() {
eth=0
while [ $eth -eq 0 ]
do
if [ `ifconfig | grep -c addr:192.168.1.66` -eq 0 ]
then
sleep 10
else
eth=1
fi
done
}
After applying it I found that the system froze during start. I checked
/etc/network/interfaces and figured out that eth0 hadn't been set in the file!!!
After adding eth0 (with patch in /etc/init.d/ssh) system start fine
Current /etc/network/interfaces is very standard:
auto lo eth0
iface lo inet loopback
iface eth0 inet dhcp
--
sshd doesn't start properly
https://bugs.launchpad.net/bugs/241796
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 241796] Re: sshd doesn't start properly
I wrote a patch for /etc/init.d/ssh which make scrpit waiting for a eth0
interface:
#My patch
check_for_eth() {
eth=0
while [ $eth -eq 0 ]
do
if [ `ifconfig | grep -c addr:192.168.1.66` -eq 0 ]
then
sleep 10
else
eth=1
fi
done
}
After applying it I found that the system froze during start. I checked
/etc/network/interfaces and figured out that eth0 hadn't been set in the file!!!
After adding eth0 (with patch in /etc/init.d/ssh) system start fine
Current /etc/network/interfaces is very standard:
auto lo eth0
iface lo inet loopback
iface eth0 inet dhcp
--
sshd doesn't start properly
https://bugs.launchpad.net/bugs/241796
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 217215] Re: HP LJ 1018 regression in hardy
And again. This time I turned printer after starting machine (indeed just before printing). The queue in cups website and in lpq looked fine (job was waiting). I think next I tried following step - restart cups - restart printer - restart computer (printer turn on) - re-establish printer in cups It didn't help. I gave up and turned computer printer off. Today during initialization of system printer finally started to print. Do you think it might mean that firmware has been updated??? -- HP LJ 1018 regression in hardy https://bugs.launchpad.net/bugs/217215 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 241796] Re: sshd doesn't start properly
I change loglevel of sshd, restart the machine and I think I've got him! The problem is start sequence, the sshd starts before dhcp finishes procedure of getting IP address from router (the standard BT broadband router). Please compare following lines from /var/log/auth: Jul 22 21:35:05 madryt sshd[5612]: debug1: Bind to port 22 on 192.168.1.66. Jul 22 21:35:05 madryt sshd[5612]: error: Bind to port 22 on 192.168.1.66 failed: Cannot assign requested address. Jul 22 21:35:05 madryt sshd[5612]: debug1: Bind to port 22 on 127.0.0.1. Jul 22 21:35:05 madryt sshd[5612]: Server listening on 127.0.0.1 port 22. and /var/log/syslog: Jul 22 21:35:13 madryt dhclient: DHCPREQUEST of 192.168.1.66 on eth0 to 255.255.255.255 port 67 Jul 22 21:35:13 madryt dhclient: DHCPACK of 192.168.1.66 from 192.168.1.254 Jul 22 21:35:13 madryt avahi-daemon[5633]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.66. Jul 22 21:35:13 madryt avahi-daemon[5633]: New relevant interface eth0.IPv4 for mDNS. Jul 22 21:35:13 madryt avahi-daemon[5633]: Registering new address record for 192.168.1.66 on eth0.IPv4. Jul 22 21:35:13 madryt kernel: [ 137.075467] [drm] Initialized drm 1.1.0 20060810 Jul 22 21:35:13 madryt kernel: [ 137.125180] ACPI: PCI Interrupt :01:00.0[A] - GSI 16 (level, low) - IRQ 21 Jul 22 21:35:13 madryt kernel: [ 137.125543] [drm] Initialized r128 2.5.0 20030725 on minor 0 Jul 22 21:35:13 madryt kernel: [ 137.127323] agpgart: Found an AGP 2.0 compliant device at :00:00.0. Jul 22 21:35:13 madryt kernel: [ 137.127364] agpgart: Putting AGP V2 device at :00:00.0 into 1x mode Jul 22 21:35:13 madryt kernel: [ 137.127389] agpgart: Putting AGP V2 device at :01:00.0 into 1x mode Jul 22 21:35:13 madryt NetworkManager: debug [1216758913.209118] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/pci_1002_5446_drm_r128_card0'). Jul 22 21:35:13 madryt NetworkManager: info DHCP daemon state is now 4 (reboot) for interface eth0 Jul 22 21:35:13 madryt NetworkManager: info Activation (eth0) Stage 4 of 5 (IP Configure Get) scheduled... Jul 22 21:35:13 madryt NetworkManager: info Activation (eth0) Stage 4 of 5 (IP Configure Get) started... Jul 22 21:35:13 madryt dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.host_name Jul 22 21:35:13 madryt dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_domain Jul 22 21:35:13 madryt dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_servers Jul 22 21:35:13 madryt NetworkManager: info Retrieved the following IP4 configuration from the DHCP daemon: Jul 22 21:35:13 madryt NetworkManager: infoaddress 192.168.1.66 Jul 22 21:35:13 madryt NetworkManager: infonetmask 255.255.255.0 Jul 22 21:35:13 madryt NetworkManager: infobroadcast 192.168.1.255 Jul 22 21:35:13 madryt NetworkManager: infogateway 192.168.1.254 Jul 22 21:35:13 madryt NetworkManager: infonameserver 192.168.1.254 Jul 22 21:35:13 madryt NetworkManager: infodomain name 'home' Jul 22 21:35:13 madryt dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.interface_mtu Jul 22 21:35:13 madryt NetworkManager: info Activation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled... Jul 22 21:35:13 madryt NetworkManager: info Activation (eth0) Stage 4 of 5 (IP Configure Get) complete. Jul 22 21:35:13 madryt NetworkManager: info Activation (eth0) Stage 5 of 5 (IP Configure Commit) started... Jul 22 21:35:13 madryt dhclient: bound to 192.168.1.66 -- renewal in 32709 seconds. Jul 22 21:35:13 madryt kernel: [ 137.252041] NET: Registered protocol family 10 Jul 22 21:35:13 madryt kernel: [ 137.253010] lo: Disabled Privacy Extensions Jul 22 21:35:13 madryt avahi-daemon[5633]: Withdrawing address record for 192.168.1.66 on eth0. Jul 22 21:35:13 madryt avahi-daemon[5633]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.1.66. Jul 22 21:35:13 madryt avahi-daemon[5633]: Interface eth0.IPv4 no longer relevant for mDNS. Jul 22 21:35:13 madryt avahi-daemon[5633]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.66. Jul 22 21:35:13 madryt avahi-daemon[5633]: New relevant interface eth0.IPv4 for mDNS. Jul 22 21:35:13 madryt avahi-daemon[5633]: Registering new address record for 192.168.1.66 on eth0.IPv4. -- sshd doesn't start properly https://bugs.launchpad.net/bugs/241796 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 241796] Re: sshd doesn't start properly
Few more lines from /var/log/syslog: Jul 22 21:35:10 madryt NetworkManager: info Activation (eth0) Beginning DHCP transaction. Jul 22 21:35:10 madryt NetworkManager: info Activation (eth0) Stage 3 of 5 (IP Configure Start) complete. Jul 22 21:35:10 madryt NetworkManager: info DHCP daemon state is now 12 (successfully started) for interface eth0 Jul 22 21:35:12 madryt NetworkManager: info DHCP daemon state is now 1 (starting) for interface eth0 Jul 22 21:35:12 madryt kernel: [ 136.070878] NET: Registered protocol family 17 Activation of eth0 started 5 seconds after sshd attempt to use it (if I understands logs properly). -- sshd doesn't start properly https://bugs.launchpad.net/bugs/241796 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 241796] Re: sshd doesn't start properly
I change loglevel of sshd, restart the machine and I think I've got him! The problem is start sequence, the sshd starts before dhcp finishes procedure of getting IP address from router (the standard BT broadband router). Please compare following lines from /var/log/auth: Jul 22 21:35:05 madryt sshd[5612]: debug1: Bind to port 22 on 192.168.1.66. Jul 22 21:35:05 madryt sshd[5612]: error: Bind to port 22 on 192.168.1.66 failed: Cannot assign requested address. Jul 22 21:35:05 madryt sshd[5612]: debug1: Bind to port 22 on 127.0.0.1. Jul 22 21:35:05 madryt sshd[5612]: Server listening on 127.0.0.1 port 22. and /var/log/syslog: Jul 22 21:35:13 madryt dhclient: DHCPREQUEST of 192.168.1.66 on eth0 to 255.255.255.255 port 67 Jul 22 21:35:13 madryt dhclient: DHCPACK of 192.168.1.66 from 192.168.1.254 Jul 22 21:35:13 madryt avahi-daemon[5633]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.66. Jul 22 21:35:13 madryt avahi-daemon[5633]: New relevant interface eth0.IPv4 for mDNS. Jul 22 21:35:13 madryt avahi-daemon[5633]: Registering new address record for 192.168.1.66 on eth0.IPv4. Jul 22 21:35:13 madryt kernel: [ 137.075467] [drm] Initialized drm 1.1.0 20060810 Jul 22 21:35:13 madryt kernel: [ 137.125180] ACPI: PCI Interrupt :01:00.0[A] - GSI 16 (level, low) - IRQ 21 Jul 22 21:35:13 madryt kernel: [ 137.125543] [drm] Initialized r128 2.5.0 20030725 on minor 0 Jul 22 21:35:13 madryt kernel: [ 137.127323] agpgart: Found an AGP 2.0 compliant device at :00:00.0. Jul 22 21:35:13 madryt kernel: [ 137.127364] agpgart: Putting AGP V2 device at :00:00.0 into 1x mode Jul 22 21:35:13 madryt kernel: [ 137.127389] agpgart: Putting AGP V2 device at :01:00.0 into 1x mode Jul 22 21:35:13 madryt NetworkManager: debug [1216758913.209118] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/pci_1002_5446_drm_r128_card0'). Jul 22 21:35:13 madryt NetworkManager: info DHCP daemon state is now 4 (reboot) for interface eth0 Jul 22 21:35:13 madryt NetworkManager: info Activation (eth0) Stage 4 of 5 (IP Configure Get) scheduled... Jul 22 21:35:13 madryt NetworkManager: info Activation (eth0) Stage 4 of 5 (IP Configure Get) started... Jul 22 21:35:13 madryt dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.host_name Jul 22 21:35:13 madryt dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_domain Jul 22 21:35:13 madryt dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_servers Jul 22 21:35:13 madryt NetworkManager: info Retrieved the following IP4 configuration from the DHCP daemon: Jul 22 21:35:13 madryt NetworkManager: infoaddress 192.168.1.66 Jul 22 21:35:13 madryt NetworkManager: infonetmask 255.255.255.0 Jul 22 21:35:13 madryt NetworkManager: infobroadcast 192.168.1.255 Jul 22 21:35:13 madryt NetworkManager: infogateway 192.168.1.254 Jul 22 21:35:13 madryt NetworkManager: infonameserver 192.168.1.254 Jul 22 21:35:13 madryt NetworkManager: infodomain name 'home' Jul 22 21:35:13 madryt dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.interface_mtu Jul 22 21:35:13 madryt NetworkManager: info Activation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled... Jul 22 21:35:13 madryt NetworkManager: info Activation (eth0) Stage 4 of 5 (IP Configure Get) complete. Jul 22 21:35:13 madryt NetworkManager: info Activation (eth0) Stage 5 of 5 (IP Configure Commit) started... Jul 22 21:35:13 madryt dhclient: bound to 192.168.1.66 -- renewal in 32709 seconds. Jul 22 21:35:13 madryt kernel: [ 137.252041] NET: Registered protocol family 10 Jul 22 21:35:13 madryt kernel: [ 137.253010] lo: Disabled Privacy Extensions Jul 22 21:35:13 madryt avahi-daemon[5633]: Withdrawing address record for 192.168.1.66 on eth0. Jul 22 21:35:13 madryt avahi-daemon[5633]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.1.66. Jul 22 21:35:13 madryt avahi-daemon[5633]: Interface eth0.IPv4 no longer relevant for mDNS. Jul 22 21:35:13 madryt avahi-daemon[5633]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.66. Jul 22 21:35:13 madryt avahi-daemon[5633]: New relevant interface eth0.IPv4 for mDNS. Jul 22 21:35:13 madryt avahi-daemon[5633]: Registering new address record for 192.168.1.66 on eth0.IPv4. -- sshd doesn't start properly https://bugs.launchpad.net/bugs/241796 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 241796] Re: sshd doesn't start properly
Few more lines from /var/log/syslog: Jul 22 21:35:10 madryt NetworkManager: info Activation (eth0) Beginning DHCP transaction. Jul 22 21:35:10 madryt NetworkManager: info Activation (eth0) Stage 3 of 5 (IP Configure Start) complete. Jul 22 21:35:10 madryt NetworkManager: info DHCP daemon state is now 12 (successfully started) for interface eth0 Jul 22 21:35:12 madryt NetworkManager: info DHCP daemon state is now 1 (starting) for interface eth0 Jul 22 21:35:12 madryt kernel: [ 136.070878] NET: Registered protocol family 17 Activation of eth0 started 5 seconds after sshd attempt to use it (if I understands logs properly). -- sshd doesn't start properly https://bugs.launchpad.net/bugs/241796 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 250440] [NEW] Text consoles doesn't work for ATI Rage 128 Pro Ultra TF + LG Flatron L1953S
Public bug reported: When try to switch from Xorg to text console by Ctrl+Alt+[1-6] keys' combination doesn't work. I got an monitor 'error message' out of sync 82.5 kHz/ 132 Hz. I have: - ATI Technologies Inc Rage 128 Pro Ultra TF - LG Flatron L1953S More problems with this couple reported in bug I243952 ** Affects: ubuntu Importance: Undecided Status: New -- Text consoles doesn't work for ATI Rage 128 Pro Ultra TF + LG Flatron L1953S https://bugs.launchpad.net/bugs/250440 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 243952] Re: Xorg with the default refresh rate looks ulgy (ATI Rage 128 + LCD)
I've attached requested information. Please review the report once more. Thanks for your time, Wawrzek ** Changed in: xorg (Ubuntu) Status: Incomplete = New -- Xorg with the default refresh rate looks ulgy (ATI Rage 128 + LCD) https://bugs.launchpad.net/bugs/243952 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 243952] Re: Xorg with the default refresh rate looks ulgy (ATI Rage 128 + LCD)
Xorg starts in: resolution 1280x1024 (fine) refrash rate 60 -should be 75 Keep in mind that I'm rather power user so , so please do not hesitate to ask any further question even if they are involving significant changes in the system. -- Xorg with the default refresh rate looks ulgy (ATI Rage 128 + LCD) https://bugs.launchpad.net/bugs/243952 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 243952] Re: Xorg with the default refresh rate looks ulgy (ATI Rage 128 + LCD)
** Attachment added: Xorg.log http://launchpadlibrarian.net/15800962/Xorg.0.log -- Xorg with the default refresh rate looks ulgy (ATI Rage 128 + LCD) https://bugs.launchpad.net/bugs/243952 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 243952] Re: Xorg with the default refresh rate looks ulgy (ATI Rage 128 + LCD)
Output of Xrandr added in the first message and below: [EMAIL PROTECTED]:~$xrandr Screen 0: minimum 320 x 240, current 1280 x 1024, maximum 1280 x 1024 default connected 1280x1024+0+0 0mm x 0mm 1280x1024 60.0 75.0* 1024x768 75.0 60.0 70.0 800x600 75.0 60.0 72.0 65.0 56.0 720x400 70.0 640x480 75.0 60.0 73.0 1280x960 60.0 1280x800 60.0 1152x864 75.0 1280x768 60.0 896x672 60.0 960x600 60.0 832x624 75.0 840x525 60.0 700x525 75.0 70.0 60.0 640x512 75.0 60.0 720x450 60.0 640x400 60.0 576x432 75.0 640x384 60.0 512x384 75.0 70.0 60.0 416x312 75.0 400x300 75.0 72.0 60.0 56.0 320x240 75.0 73.0 60.0 -- Xorg with the default refresh rate looks ulgy (ATI Rage 128 + LCD) https://bugs.launchpad.net/bugs/243952 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 243952] Re: Xorg with the default refresh rate looks ulgy (ATI Rage 128 + LCD)
** Attachment added: Output of ddcprobe http://launchpadlibrarian.net/15800648/ddcprobe.log -- Xorg with the default refresh rate looks ulgy (ATI Rage 128 + LCD) https://bugs.launchpad.net/bugs/243952 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 243952] [NEW] Xorg with the default refresh rate looks ulgy (ATI Rage 128 + LCD)
Public bug reported: I have: - ATI Technologies Inc Rage 128 Pro Ultra TF - LG Flatron L1953S The default setting make Xorg looks ugly. After some investigation I found that it is dur to refresh rate set to 60 Mhz. Reseting it to 75 make everything looks much better. (I'm using fvwm-crystal so please do not advice any gnome settings). I've set the package to xserver-xorg, but it can be also something wrong with ati drivers. Why the default setting are so bad? What should I do to force Xorg starting with given refresh rate? BTW. I've just run dpkg-reconfigure xserver-xorg and I'm going to see what happens (I tried to use Framebuffer as suggested by system). Old xorg.conf in attachment and output of xrandr below. [EMAIL PROTECTED]:~$xrandr Screen 0: minimum 320 x 240, current 1280 x 1024, maximum 1280 x 1024 default connected 1280x1024+0+0 0mm x 0mm 1280x1024 60.0 75.0* 1024x768 75.0 60.0 70.0 800x60075.0 60.0 72.0 65.0 56.0 720x40070.0 640x48075.0 60.0 73.0 1280x960 60.0 1280x800 60.0 1152x864 75.0 1280x768 60.0 896x67260.0 960x60060.0 832x62475.0 840x52560.0 700x52575.0 70.0 60.0 640x51275.0 60.0 720x45060.0 640x40060.0 576x43275.0 640x38460.0 512x38475.0 70.0 60.0 416x31275.0 400x30075.0 72.0 60.0 56.0 320x24075.0 73.0 60.0 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: ati lcd settings xorg -- Xorg with the default refresh rate looks ulgy (ATI Rage 128 + LCD) https://bugs.launchpad.net/bugs/243952 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 243952] Re: Xorg with the default refresh rate looks ulgy (ATI Rage 128 + LCD)
** Attachment added: xorg.conf http://launchpadlibrarian.net/15675609/xorg.conf -- Xorg with the default refresh rate looks ulgy (ATI Rage 128 + LCD) https://bugs.launchpad.net/bugs/243952 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 243952] Re: Xorg with the default refresh rate looks ulgy (ATI Rage 128 + LCD)
OK. The Xorg couldn't start with FBDev. The xorg.conf file in attachment. ** Attachment added: Xorg created via dpkg-reconfigure (I chose FBDev) http://launchpadlibrarian.net/15675915/xorg.conf.fbdev -- Xorg with the default refresh rate looks ulgy (ATI Rage 128 + LCD) https://bugs.launchpad.net/bugs/243952 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 243952] Re: Xorg with the default refresh rate looks ulgy (ATI Rage 128 + LCD)
Next the new fallback config tool were started and I chose my Card and FlatPanel, but the created xorg.conf file looked awful (Virtual Screen etc.) ** Attachment added: Xorg.conf created by fallback tool http://launchpadlibrarian.net/15675995/xorg.conf.auto -- Xorg with the default refresh rate looks ulgy (ATI Rage 128 + LCD) https://bugs.launchpad.net/bugs/243952 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 217215] Re: HP LJ 1018 regression in hardy
It happened again! I canceled printing one of PDF and printer stopped to print and system started complain that it might not be connected. -- HP LJ 1018 regression in hardy https://bugs.launchpad.net/bugs/217215 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 241796] Re: sshd doesn't start properly
[EMAIL PROTECTED]:~$apt-cache policy openssh-server openssh-server: Installed: 1:4.7p1-8ubuntu1.2 Candidate: 1:4.7p1-8ubuntu1.2 Version table: *** 1:4.7p1-8ubuntu1.2 0 500 http://gb.archive.ubuntu.com hardy-updates/main Packages 500 http://security.ubuntu.com hardy-security/main Packages 100 /var/lib/dpkg/status 1:4.7p1-8ubuntu1 0 500 http://gb.archive.ubuntu.com hardy/main Packages [EMAIL PROTECTED]:~$ -- sshd doesn't start properly https://bugs.launchpad.net/bugs/241796 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 241796] Re: sshd doesn't start properly
The sshd is working fine now. I've change few things. First I figured out that I can connect to localhost by not to madryt Next I've changed order of ListenAddress in /etc/ssh/sshd_config ListenAddress 192.168.1.66 ListenAddress 127.0.0.1 After some times I understood that ssh complains about bind and found that I had made a mistake in /etc/hosts I'm not sure what was earlier probably 127.0.0.1 localhost madyt or sth. similar but now I have 127.0.0.1 localhost madryt 192.168.1.66madryt.home madryt I'm not sure if I was blind and I didn't see message about problems with bind or I change something and this message started to appear. I also don't understand why manually restart of ssh demon were resolving the issue... -- sshd doesn't start properly https://bugs.launchpad.net/bugs/241796 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 241796] Re: sshd doesn't start properly
[EMAIL PROTECTED]:~$apt-cache policy openssh-server openssh-server: Installed: 1:4.7p1-8ubuntu1.2 Candidate: 1:4.7p1-8ubuntu1.2 Version table: *** 1:4.7p1-8ubuntu1.2 0 500 http://gb.archive.ubuntu.com hardy-updates/main Packages 500 http://security.ubuntu.com hardy-security/main Packages 100 /var/lib/dpkg/status 1:4.7p1-8ubuntu1 0 500 http://gb.archive.ubuntu.com hardy/main Packages [EMAIL PROTECTED]:~$ -- sshd doesn't start properly https://bugs.launchpad.net/bugs/241796 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 241796] Re: sshd doesn't start properly
The sshd is working fine now. I've change few things. First I figured out that I can connect to localhost by not to madryt Next I've changed order of ListenAddress in /etc/ssh/sshd_config ListenAddress 192.168.1.66 ListenAddress 127.0.0.1 After some times I understood that ssh complains about bind and found that I had made a mistake in /etc/hosts I'm not sure what was earlier probably 127.0.0.1 localhost madyt or sth. similar but now I have 127.0.0.1 localhost madryt 192.168.1.66madryt.home madryt I'm not sure if I was blind and I didn't see message about problems with bind or I change something and this message started to appear. I also don't understand why manually restart of ssh demon were resolving the issue... -- sshd doesn't start properly https://bugs.launchpad.net/bugs/241796 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 217215] Re: HP LJ 1018 regression in hardy
I don't know what I've changed by printers work fine! -- HP LJ 1018 regression in hardy https://bugs.launchpad.net/bugs/217215 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 217215] Re: HP LJ 1018 regression in hardy
I have the same/very similar problem. hp-check -t in attachment and dmesg below: [ 152.397590] process `skype' is using obsolete setsockopt SO_BSDCOMPAT [ 296.722264] audit(1214002129.774:4): type=1503 operation=inode_permission requested_mask=::rw denied_mask=::rw name=/dev/tty pid=6055 profile=/usr/sbin/cupsd namespace=default [ 303.934480] usb 1-2: usbfs: USBDEVFS_CONTROL failed cmd hpijs rqt 161 rq 1 len 1 ret -110 [ 314.161753] audit(1214002147.210:5): type=1503 operation=inode_permission requested_mask=::rw denied_mask=::rw name=/dev/tty pid=6073 profile=/usr/sbin/cupsd namespace=default [ 320.949601] usb 1-2: usbfs: USBDEVFS_CONTROL failed cmd hpijs rqt 161 rq 1 len 1 ret -110 [ 404.674692] audit(1214002237.718:6): type=1503 operation=inode_permission requested_mask=::rw denied_mask=::rw name=/dev/tty pid=6100 profile=/usr/sbin/cupsd namespace=default [ 411.561670] usb 1-2: usbfs: USBDEVFS_CONTROL failed cmd hpijs rqt 161 rq 1 len 1 ret -110 [ 436.083451] ppdev0: registered pardevice [ 436.129169] ppdev0: unregistered pardevice [ 436.293052] ppdev0: registered pardevice [ 436.340679] ppdev0: unregistered pardevice [ 439.892904] ppdev0: registered pardevice [ 439.940438] ppdev0: unregistered pardevice [ 573.151141] audit(1214002406.218:7): type=1503 operation=inode_permission requested_mask=::rw denied_mask=::rw name=/dev/tty pid=6177 profile=/usr/sbin/cupsd namespace=default [ 579.723816] usb 1-2: usbfs: USBDEVFS_CONTROL failed cmd hpijs rqt 161 rq 1 len 1 ret -110 [ 654.554255] audit(1214002487.630:8): type=1503 operation=inode_permission requested_mask=::rw denied_mask=::rw name=/dev/tty pid=6200 profile=/usr/sbin/cupsd namespace=default [ 661.257135] usb 1-2: usbfs: USBDEVFS_CONTROL failed cmd hpijs rqt 161 rq 1 len 1 ret -110 [ 687.556605] audit(1214002520.638:9): type=1503 operation=inode_permission requested_mask=::rw denied_mask=::rw name=/dev/tty pid=6224 profile=/usr/sbin/cupsd namespace=default [ 694.808507] usb 1-2: usbfs: USBDEVFS_CONTROL failed cmd hpijs rqt 161 rq 1 len 1 ret -110 [ 722.476988] audit(1214002555.562:10): type=1503 operation=inode_permission requested_mask=::rw denied_mask=::rw name=/dev/tty pid=6252 profile=/usr/sbin/cupsd namespace=default [ 728.542727] usb 1-2: usbfs: USBDEVFS_CONTROL failed cmd hpijs rqt 161 rq 1 len 1 ret -110 [ 1231.580352] audit(1214003064.730:11): type=1503 operation=inode_permission requested_mask=::rw denied_mask=::rw name=/dev/tty pid=6336 profile=/usr/sbin/cupsd namespace=default [ 1238.326370] usb 1-2: usbfs: USBDEVFS_CONTROL failed cmd hpijs rqt 161 rq 1 len 1 ret -110 [ 1342.070512] audit(1214003175.234:12): type=1503 operation=inode_permission requested_mask=a:: denied_mask=a:: name=/dev/tty pid=6399 profile=/usr/sbin/cupsd namespace=default [ 1343.034480] audit(1214003176.198:13): type=1503 operation=inode_permission requested_mask=::rw denied_mask=::rw name=/dev/tty pid=6414 profile=/usr/sbin/cupsd namespace=default [ 1418.480322] audit(1214003251.654:14): type=1503 operation=inode_permission requested_mask=a:: denied_mask=a:: name=/dev/tty pid=6457 profile=/usr/sbin/cupsd namespace=default [ 1575.176816] ppdev0: registered pardevice [ 1575.225122] ppdev0: unregistered pardevice [ 1642.514163] ppdev0: registered pardevice [ 1642.560416] ppdev0: unregistered pardevice [ 1657.925346] ppdev0: registered pardevice [ 1657.974561] ppdev0: unregistered pardevice ** Attachment added: Log from hp-check -t http://launchpadlibrarian.net/15489419/hp-check.log -- HP LJ 1018 regression in hardy https://bugs.launchpad.net/bugs/217215 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 241796] [NEW] sshd doesn't start properly
Public bug reported: Binary package hint: openssh-server The sshd server doesn't start properly: [EMAIL PROTECTED]:~$ps axf | grep ssh 4885 ?Ss 0:00 /usr/sbin/sshd Restarting it helps: [EMAIL PROTECTED]:~$sudo /etc/init.d/ssh restart [sudo] password for niewod: * Restarting OpenBSD Secure Shell server sshd ...done. [EMAIL PROTECTED]:~$ps axf | grep ssh 6683 pts/0S+ 0:00 \_ grep ssh 6678 ?Ss 0:00 /usr/sbin/sshd ssh server working again. ** Affects: openssh (Ubuntu) Importance: Undecided Status: New -- sshd doesn't start properly https://bugs.launchpad.net/bugs/241796 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
