[Bug 967410] Re: Windows clients cannot connect to shared printers
This bug is somewhat a deal breaker for 12.04 for me. A search on Google will likely show up an array of deal break bugs for Samba 3.6.x. I've been hoping for a fix to come over the last few weeks, but on looking at the upstream release notes, there doesn't seem to be a fix in the pipeline for this, although the most recent update to samba has many, many bug and security fixes. Perhaps Andrew Tridgell is busy fire fighting at the moment with the 3.6 series. I understand substantial sections have been re-written and obviously not yet mature code. Perhaps distributions need to do their own code quality control, and perhaps make choices whether to include the latest versions if too buggy. I'd suggest the previous 3.5 series of Samba should be included in 12.04 repositories, and available by default at least until samba 3.6 is more mature. I wish I had the time, knowledge and resources to help Andrew Tridgell in his programming efforts on Samba. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/967410 Title: Windows clients cannot connect to shared printers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/967410/+subscriptions -- 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 967410] Re: Windows clients cannot connect to shared printers
This bug is somewhat a deal breaker for 12.04 for me. A search on Google will likely show up an array of deal break bugs for Samba 3.6.x. I've been hoping for a fix to come over the last few weeks, but on looking at the upstream release notes, there doesn't seem to be a fix in the pipeline for this, although the most recent update to samba has many, many bug and security fixes. Perhaps Andrew Tridgell is busy fire fighting at the moment with the 3.6 series. I understand substantial sections have been re-written and obviously not yet mature code. Perhaps distributions need to do their own code quality control, and perhaps make choices whether to include the latest versions if too buggy. I'd suggest the previous 3.5 series of Samba should be included in 12.04 repositories, and available by default at least until samba 3.6 is more mature. I wish I had the time, knowledge and resources to help Andrew Tridgell in his programming efforts on Samba. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/967410 Title: Windows clients cannot connect to shared printers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/967410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 930447] Re: Unable to start Ubuntu 12.04 live CD with syslinux loader on Pentium M x86 Laptop due to bug in PAE kernel, initramfs or syslinux
Including a PAE only kernel with the default ISO significantly and unnecessarily limits scope for installation of 12.04, and going forward, Ubuntu generally. Many good spec machines don't have PAE. A notable example being Centrino laptops. Within weeks (or days) of a distribution being released, a new kernel is generally available for update. Perhaps the sensible approach would be for the package manager to install the latest PAE kernel on first update IF the CPU supports PAE. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/930447 Title: Unable to start Ubuntu 12.04 live CD with syslinux loader on Pentium M x86 Laptop due to bug in PAE kernel, initramfs or syslinux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/930447/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969937] Re: package libmysqlclient16 5.1.61-0ubuntu0.10.04.1 failed to install/upgrade: trying to overwrite '/usr/lib/libmysqlclient.so.16.0.0', which is also in package mysql-cluster-client-5.1
bug #967410 appears to have nothing to do with this bug ** This bug is no longer a duplicate of bug 967410 Windows clients cannot connect to shared printers -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-dfsg-5.1 in Ubuntu. https://bugs.launchpad.net/bugs/969937 Title: package libmysqlclient16 5.1.61-0ubuntu0.10.04.1 failed to install/upgrade: trying to overwrite '/usr/lib/libmysqlclient.so.16.0.0', which is also in package mysql- cluster-client-5.1 0:7.0.9-1ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-dfsg-5.1/+bug/969937/+subscriptions -- 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 967410] Re: Windows clients cannot connect to shared printers
Me too, And the IPP implementation is unreliable for me. This means there is no print option at all over SMB. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/967410 Title: Windows clients cannot connect to shared printers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/967410/+subscriptions -- 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 993781] Re: printing can nolonger athenticate between boxen on my lan under Precise
*** This bug is a duplicate of bug 967410 *** https://bugs.launchpad.net/bugs/967410 ** This bug has been marked a duplicate of bug 967410 Windows clients cannot connect to shared printers -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/993781 Title: printing can nolonger athenticate between boxen on my lan under Precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/993781/+subscriptions -- 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 969937] Re: package libmysqlclient16 5.1.61-0ubuntu0.10.04.1 failed to install/upgrade: trying to overwrite '/usr/lib/libmysqlclient.so.16.0.0', which is also in package mysql-cluster-client-5.1
bug #967410 appears to have nothing to do with this bug ** This bug is no longer a duplicate of bug 967410 Windows clients cannot connect to shared printers -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969937 Title: package libmysqlclient16 5.1.61-0ubuntu0.10.04.1 failed to install/upgrade: trying to overwrite '/usr/lib/libmysqlclient.so.16.0.0', which is also in package mysql- cluster-client-5.1 0:7.0.9-1ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-dfsg-5.1/+bug/969937/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 967410] Re: Windows clients cannot connect to shared printers
Me too, And the IPP implementation is unreliable for me. This means there is no print option at all over SMB. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/967410 Title: Windows clients cannot connect to shared printers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/967410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 993781] Re: printing can nolonger athenticate between boxen on my lan under Precise
*** This bug is a duplicate of bug 967410 *** https://bugs.launchpad.net/bugs/967410 ** This bug has been marked a duplicate of bug 967410 Windows clients cannot connect to shared printers -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/993781 Title: printing can nolonger athenticate between boxen on my lan under Precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/993781/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 897120] [NEW] apache2-suexec-custom changes permissions on suexec binary
Public bug reported: I have a server where the group ID for the suexec binary is set to other than www-data. Whenever an update occurs, all web sites with scripting which depend on suexec break. This can happen at any time as I have automatic updates enabled. Once I receive complaints, I must log in and re-set the GID on /var/lib/apache2/suexec I consider the group ID on the suexec binary as a system setting. This system setting is wiped on update. Please change the package scripts so that they preserve the ownership and permissions on suexec. Description:Ubuntu 10.04.3 LTS Release:10.04 apache2-suexec-custom: Installed: 2.2.14-5ubuntu8.7 Candidate: 2.2.14-5ubuntu8.7 ** Affects: apache2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 in Ubuntu. https://bugs.launchpad.net/bugs/897120 Title: apache2-suexec-custom changes permissions on suexec binary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/897120/+subscriptions -- 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 897120] [NEW] apache2-suexec-custom changes permissions on suexec binary
Public bug reported: I have a server where the group ID for the suexec binary is set to other than www-data. Whenever an update occurs, all web sites with scripting which depend on suexec break. This can happen at any time as I have automatic updates enabled. Once I receive complaints, I must log in and re-set the GID on /var/lib/apache2/suexec I consider the group ID on the suexec binary as a system setting. This system setting is wiped on update. Please change the package scripts so that they preserve the ownership and permissions on suexec. Description:Ubuntu 10.04.3 LTS Release:10.04 apache2-suexec-custom: Installed: 2.2.14-5ubuntu8.7 Candidate: 2.2.14-5ubuntu8.7 ** Affects: apache2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/897120 Title: apache2-suexec-custom changes permissions on suexec binary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/897120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 462169] Re: nmbd dies on startup when network interfaces are not up yet
Hi Steve. I observed that my Ubuntu 10.04 system would wait for an indefinite period at start-up if there was no available non-loopback interface available. I presumed this was a bug related to the upstart job for nmbd. -- nmbd dies on startup when network interfaces are not up yet https://bugs.launchpad.net/bugs/462169 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba 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 462169] Re: nmbd dies on startup when network interfaces are not up yet
I have performed a controlled experiment and can't replicate the behaviour, so it must have been a mis-diagnosis. Sorry. -- nmbd dies on startup when network interfaces are not up yet https://bugs.launchpad.net/bugs/462169 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba 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 462169] Re: nmbd dies on startup when network interfaces are not up yet
Hi Steve. I observed that my Ubuntu 10.04 system would wait for an indefinite period at start-up if there was no available non-loopback interface available. I presumed this was a bug related to the upstart job for nmbd. -- nmbd dies on startup when network interfaces are not up yet https://bugs.launchpad.net/bugs/462169 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 462169] Re: nmbd dies on startup when network interfaces are not up yet
I have performed a controlled experiment and can't replicate the behaviour, so it must have been a mis-diagnosis. Sorry. -- nmbd dies on startup when network interfaces are not up yet https://bugs.launchpad.net/bugs/462169 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 462169] Re: nmbd dies on startup when network interfaces are not up yet
Based on the above, perhaps the upstart script for samba / nmbd has a bug as the script will stop the system from booting if no net adapters come up. A preferred behaviour would be for nmbd to fail to start but let the machine boot. Better still, if nmbd could have the same behaviour that smbd has, an that is to start and wait for a suitable adapter to come up. -- nmbd dies on startup when network interfaces are not up yet https://bugs.launchpad.net/bugs/462169 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba 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 462169] Re: nmbd dies on startup when network interfaces are not up yet
Based on the above, perhaps the upstart script for samba / nmbd has a bug as the script will stop the system from booting if no net adapters come up. A preferred behaviour would be for nmbd to fail to start but let the machine boot. Better still, if nmbd could have the same behaviour that smbd has, an that is to start and wait for a suitable adapter to come up. -- nmbd dies on startup when network interfaces are not up yet https://bugs.launchpad.net/bugs/462169 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 462169] Re: nmbd dies on startup when network interfaces are not up yet
There was bogus adapter information in /etc/network/interfaces . I removed that. Consequently, my computer failed to boot as the samba / nmbd script was waiting for a network event which would never happen. The only adapter listed in /etc/network/interfaces was lo, which would not generate the necessary trigger to start samba. Consequently, Init hung on waiting for the eth up event to start smbd and nmbd. I noticed bridging events in the /etc/init directory, then discovered bridging functions are now 'formalised' in /etc/network/interfaces. I moved my configuration to there, then removed my original script from init. So my bridging now works properly, and via the formal method. Since upstart could now bring my interfaces up, this has solved that problem. So this is not a bug with samba, or the scripts because if the formal route to bridging is adopted, all works well. This has, however, created another problem unrelated to this bug; DHCPd will not start. Apparently, upstart is trying to start DHCPd before the network interfaces are up. But that is OT here. -- nmbd dies on startup when network interfaces are not up yet https://bugs.launchpad.net/bugs/462169 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba 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 580319] Re: dhcp3-server launches before upstart brings all interface, thus failing to start
Perhaps the best way to fix this is to make a /etc/init/dhcp3-server.conf file for upstart,, and remove /etc/rc2.d/Sxxdhcp3-server. -- dhcp3-server launches before upstart brings all interface, thus failing to start https://bugs.launchpad.net/bugs/580319 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dhcp3 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 462169] Re: nmbd dies on startup when network interfaces are not up yet
There was bogus adapter information in /etc/network/interfaces . I removed that. Consequently, my computer failed to boot as the samba / nmbd script was waiting for a network event which would never happen. The only adapter listed in /etc/network/interfaces was lo, which would not generate the necessary trigger to start samba. Consequently, Init hung on waiting for the eth up event to start smbd and nmbd. I noticed bridging events in the /etc/init directory, then discovered bridging functions are now 'formalised' in /etc/network/interfaces. I moved my configuration to there, then removed my original script from init. So my bridging now works properly, and via the formal method. Since upstart could now bring my interfaces up, this has solved that problem. So this is not a bug with samba, or the scripts because if the formal route to bridging is adopted, all works well. This has, however, created another problem unrelated to this bug; DHCPd will not start. Apparently, upstart is trying to start DHCPd before the network interfaces are up. But that is OT here. -- nmbd dies on startup when network interfaces are not up yet https://bugs.launchpad.net/bugs/462169 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 580319] Re: dhcp3-server launches before upstart brings all interface, thus failing to start
Perhaps the best way to fix this is to make a /etc/init/dhcp3-server.conf file for upstart,, and remove /etc/rc2.d/Sxxdhcp3-server. -- dhcp3-server launches before upstart brings all interface, thus failing to start https://bugs.launchpad.net/bugs/580319 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 462169] Re: nmbd dies on startup when network interfaces are not up yet
Myself and a friend have both had to use Samba with IP addresses, until I found that by restarting nmbd, name resolution works again. (Ubuntu 10.04). My machine automatically logs in. I don't use the network manager applet; I have DHCPd running on my server and use bridging. Perhaps nmbd needs to start and continue irrespective of whether there are broadcast capable interfaces, and link to the interfaces when up. I'll work around this bug by writing a script to start nmbd late in the boot process. -- nmbd dies on startup when network interfaces are not up yet https://bugs.launchpad.net/bugs/462169 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba 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 462169] Re: nmbd dies on startup when network interfaces are not up yet
Myself and a friend have both had to use Samba with IP addresses, until I found that by restarting nmbd, name resolution works again. (Ubuntu 10.04). My machine automatically logs in. I don't use the network manager applet; I have DHCPd running on my server and use bridging. Perhaps nmbd needs to start and continue irrespective of whether there are broadcast capable interfaces, and link to the interfaces when up. I'll work around this bug by writing a script to start nmbd late in the boot process. -- nmbd dies on startup when network interfaces are not up yet https://bugs.launchpad.net/bugs/462169 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 580926] Re: D-Link DWA-140 B2 can't find any AP
I confirm installing the propsed linux-firmware for lucid fixes the bug for me using an rt2870-based chip. -- D-Link DWA-140 B2 can't find any AP https://bugs.launchpad.net/bugs/580926 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 541511] Re: MASTER: [i855] GPU lockup (apport-crash)
I updated my Toshiba M100 to Lucid 10.04 today. Crashes catatonic. Tried acpi=off and tried making an xorg file with vesa set as the driver No success. Followed acpi=off instructions as mentioned earlier. No success. Then followed sudo apt-add-repository ppa:brian-rogers/graphics-fixes sudo apt-get update sudo apt-get dist-upgrade But linux-image-2.6.34-52-generic not available So tried booting. No success. Then discovered and installed linux-image-2.6.34-v9patch-generic Again no success. Reversed the acpi=off i had set previously, and removed the xorg.conf file. I can now boot to a desktop. Tried then rebooting with the vanilla kernel. river halts. Go back to V9 kernel. Boots to desktop. Seems to make no difference whether the driver in xorg.conf is set to vesa or intel. xorg detects my machine as double-headed. Presumably one is the external monitor socket. With the v9 patch kernel, acpi=off will apparently break the driver. -- MASTER: [i855] GPU lockup (apport-crash) https://bugs.launchpad.net/bugs/541511 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 239722] Re: xorg fails to correctly detect Satellite pro 4600 and 6000 screen resolution
Tested with Tosh 4600 and can confirm still a problem with 9.10 final. -- xorg fails to correctly detect Satellite pro 4600 and 6000 screen resolution https://bugs.launchpad.net/bugs/239722 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 403745] apport-collect data
Architecture: i386 DistroRelease: Ubuntu 9.04 Package: network-manager 0.7.1~rc4.1.cf199a964-0ubuntu2 PackageArchitecture: i386 ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=en_GB.UTF-8 LANGUAGE= Uname: Linux 2.6.28-15-generic i686 UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev sambashare scanner src video www-data WpaSupplicantLog: -- Amoi three skypephone S2 modem not recognised 0.7 https://bugs.launchpad.net/bugs/403745 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 403745] apport-collect data
Architecture: i386 DistroRelease: Ubuntu 9.04 Package: network-manager 0.7.1~rc4.1.cf199a964-0ubuntu2 PackageArchitecture: i386 ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=en_GB.UTF-8 LANGUAGE= Uname: Linux 2.6.28-15-generic i686 UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev sambashare scanner src video www-data WpaSupplicantLog: -- Amoi three skypephone S2 modem not recognised 0.7 https://bugs.launchpad.net/bugs/403745 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 403745] apport-collect data
Architecture: i386 DistroRelease: Ubuntu 9.04 Package: network-manager 0.7.1~rc4.1.cf199a964-0ubuntu2 PackageArchitecture: i386 ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=en_GB.UTF-8 LANGUAGE= Uname: Linux 2.6.28-15-generic i686 UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev sambashare scanner src video www-data WpaSupplicantLog: -- Amoi three skypephone S2 modem not recognised 0.7 https://bugs.launchpad.net/bugs/403745 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 403745] Re: Amoi three skypephone S2 modem not recognised 0.7
Followed the above instructions but get: n...@nick-desktop:~$ apport-collect 403745 Logging into Launchpad... Downloading bug... Bug title: Amoi three skypephone S2 modem not recognised 0.7 Collecting apport information for source package network-manager... Uploading additional information to Launchpad bug... short text data... attachment: Dependencies.txt... Error connecting to Launchpad: HTTP Error 500: Internal Server Error You have to allow Change anything privileges. I have enabled change anything privileges. ** Changed in: network-manager (Ubuntu) Status: Incomplete = New -- Amoi three skypephone S2 modem not recognised 0.7 https://bugs.launchpad.net/bugs/403745 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 277085] Re: Can't enable Hyper-Threading
I said the following: On an HP d530, I experience this bug. Even after using ht=on on kernel command line, HT is not enabled on latest 8.10 kernel 2.6.28-15-generic. I meant to say 9.04 not 8.10. I shall load a CD with the latest 9.10. If I find HT can be enabled, I will make a further comment here. -- Can't enable Hyper-Threading https://bugs.launchpad.net/bugs/277085 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 277085] Re: Can't enable Hyper-Threading
On an HP d530, I experience this bug. Even after using ht=on on kernel command line, HT is not enabled on latest 8.10 kernel 2.6.28-15-generic. j...@john-desktop:~$ uname -r 2.6.28-15-generic j...@john-desktop:~$ cat /proc/cpuinfo | grep 'ht' flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe up pebs bts cid xtpr j...@john-desktop:~$ cat /etc/issue Ubuntu 9.04 \n \l j...@john-desktop:~$ dmesg | grep -i 'hyper' [0.004280] CPU: Hyper-Threading is disabled j...@john-desktop:~$ dmesg | grep -i 'ht' [0.00] Kernel command line: root=UUID=539bf5e6-9967-4e75-927a-ba9c3e2aa958 ro ht=on xforcevesa quiet splash [0.484001] Brought up 1 CPUs j...@john-desktop:~$ cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 15 model : 2 model name : Intel(R) Pentium(R) 4 CPU 2.66GHz stepping: 9 cpu MHz : 2659.980 cache size : 512 KB fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 2 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe up pebs bts cid xtpr bogomips: 5319.96 clflush size: 64 power management: ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- Can't enable Hyper-Threading https://bugs.launchpad.net/bugs/277085 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 277085] Re: Can't enable Hyper-Threading
I have taken the CPU out of the system and found it is an SL6PE. http://www.cpu-world.com/sspec/SL/SL6PE.html Although the CPU shows the HT flag, it actually does not support hyperthreading. I installed an SL6S5. Since installing, hyperthreading is enabled whether or not I add ht=on in the kernel boot parameters. It appears the ht flag in /proc/cpuinfo is not a reliable way to determine whether a CPU supports hyperthreading. I'll mark the bug as invalid. ** Changed in: linux (Ubuntu) Status: Confirmed = Invalid -- Can't enable Hyper-Threading https://bugs.launchpad.net/bugs/277085 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 403745] Re: Amoi three skypephone S2 modem not recognised 0.7
** Summary changed: - Amoi three skypephone S2 modem not recognised ?0.7? + Amoi three skypephone S2 modem not recognised 0.7 -- Amoi three skypephone S2 modem not recognised 0.7 https://bugs.launchpad.net/bugs/403745 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 403745] Re: Amoi three skypephone S2 modem not recognised ?0.7?
** Attachment added: dmesg.txt http://launchpadlibrarian.net/29430766/dmesg.txt -- Amoi three skypephone S2 modem not recognised ?0.7? https://bugs.launchpad.net/bugs/403745 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 403745] [NEW] Amoi three skypephone S2 modem not recognised ?0.7?
Public bug reported: Binary package hint: network-manager The three skypephone S2 made by Amoi does not register as a modem under network manager. The S2 does support USB modem, and comes with a windows driver. The ini file for the windows driver has a proprietary CDC modem driver is mentioned. I can attach this if copyright permits. It includes init strings etc. dmesg shows detection of a USB CD Rom drive from the phone, but does not show detection of any serial ports unless I run modprobe usbserial vendor=0x1614 product=0x0407. If I do this, it appears four serial ports are detected. Output of dmesg included, showing detection of ports after the modprobe command. Expected behaviour: connect phone, network manager pops up to show config options, or gives option to connect via mobile wireless (generally works very well for much hardware! - Thanks!) Actual behaviour: no response to connecting phone. Kernel driver fails to load for CDC or usbserial modem interface. Phone USB ID: Vendor=1614 Device=0407 Tested on 9.10 Alpha 3. Same as 9.04. Attachments to follow: lshal.txt lsusb-v-d1614.0407.txt dmesg.txt ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- Amoi three skypephone S2 modem not recognised ?0.7? https://bugs.launchpad.net/bugs/403745 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 403745] Re: Amoi three skypephone S2 modem not recognised ?0.7?
** Attachment added: lshal.txt http://launchpadlibrarian.net/29430735/lshal.txt -- Amoi three skypephone S2 modem not recognised ?0.7? https://bugs.launchpad.net/bugs/403745 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 403745] Re: Amoi three skypephone S2 modem not recognised ?0.7?
** Attachment added: lsusb-v-d1614.0407.txt http://launchpadlibrarian.net/29430751/lsusb-v-d1614.0407.txt -- Amoi three skypephone S2 modem not recognised ?0.7? https://bugs.launchpad.net/bugs/403745 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 255651] Re: floppy disk drive not detected (module not loaded) in Intrepid and Jaunty
Regarding the last comment, I believe the machine has an FX chipset. In which case, I suppose it is so old as to not be worth investigating. I found the auto-loading works for the i810 based machines. -- floppy disk drive not detected (module not loaded) in Intrepid and Jaunty https://bugs.launchpad.net/bugs/255651 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 272970] Re: Floppy drive doesn't work from file manager
I can confirm this bug with 9.10 with a floppy drive, with a pre-release version as of 8th July 2009. The floppy issue is not related to bug #255651 as it persists if floppy is added to /etc/modules. Steps to replicate: Boot machine. Floppy Drive isn't shown in nautilus. lsmod | grep floppy shows no results. try mount /media/floppy Gives result: either mount: can't find /media/floppy in /etc/fstab or /etc/mtab OR mount: special device /dev/fd0 doesn't exist. So to overcome these scenarios, add line to fstab: /dev/fd0 /media/floppy0 auto rw,user,noauto 0 0 add line to /etc/modules: floppy reboot the above is related to bug #255651 However, the following is unrelated to that bug: Now that we have a module installed in the kernel and an appropriate fstab line, we can issue the command mount /media/floppy the floppy contents will appear when floppy is clicked in nautilus. Click the unmoiunt icon in Nautilus, the floppy unmounts. There is no way to mount the floppy in nautilus. Clicking on floppy drive will not cause the disc to mount. Unless the user reverts to the command line and issues a mount command, the user will not be able to use the floppy disc with nautilus. The user can unmount the floppy within nautilus. I expect nautilus would have a method to issue a system mount command for the floppy as the user. ** Summary changed: - Floppy drive doesn't work from file manager + Nautilus will not mount floppy 9.10 ** Package changed: ubuntu = nautilus (Ubuntu) ** Changed in: nautilus (Ubuntu) Status: Incomplete = Confirmed -- Nautilus will not mount floppy 9.10 https://bugs.launchpad.net/bugs/272970 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 255651] Re: floppy disk drive not detected (module not loaded) in Intrepid and Jaunty
I can confirm this bug in 9.10 prerelease as of 8th July 2009. Does not autodetect flopp. Necessary to add floppy to /etc/modules. -- floppy disk drive not detected (module not loaded) in Intrepid and Jaunty https://bugs.launchpad.net/bugs/255651 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 394528] [NEW] Epson sx200 sx205 scanner not detected by sane
Public bug reported:
Binary package hint: libsane
The scanner section of the Epson sx200 and SX205 all-in-one
printer/copier/scanner is not automatically recognised in either 9.04 or
the latest update to 9,10.
The scanner can be made to work by following instructions by Kaho, written on
31/12/08 on page:
http://ubuntuforums.org/showthread.php?t=932547highlight=sx200page=2
Actions to repeat bug:
Fresh install of 9.04 or 9.10.
Plug multifiunction device into Ubuntu. Ubuntu recognises printer section
automatically.
Go into Applications-Graphics-Xsane Image scanning program
Note dialog No devices available.
Expected results: Plug device into Ubuntu. Use Xsane straight away
without modifying config.
Diagnostics:
enter sane-find-scanner as user at command prompt. note line:
found USB scanner (vendor=0x04b8, product=0x0849) at libusb:001:003
type scanimage -L at command prompt. returns
No scanners were identified. If you were expecting something different...
To get scanner working, Follow series of commands by Kaho on ubuntuforums (as
noted above)
add these lines to /etc/sane.d/epson.conf
usb 0x4b8 0x849
usb /dev/usbscanner0
usb /dev/usb/scanner0
and add these lines to /etc/udev/rules.d/45-libsane.rules
# Epson Stylus SX200
SYSFS{idVendor}==04b8, SYSFS{idProduct}==0849, MODE=664, GROUP=scanner
Reboot machine.
Go into Applications-Graphics-Xsane Image scanning program
Note scanner works.
Libsane installed on 9.04
1.0.19-23ubuntu7
Libsane installed on 9.10 (prerelease)
1.0.20-4ubuntu2
** Affects: sane-backends (Ubuntu)
Importance: Undecided
Status: New
--
Epson sx200 sx205 scanner not detected by sane
https://bugs.launchpad.net/bugs/394528
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 394528] Re: Epson sx200 sx205 scanner not detected by sane
Kaho apparently used an SX205. Mine is an SX200. The USB IDs appear identical, and behaviour of the scanner identical. -- Epson sx200 sx205 scanner not detected by sane https://bugs.launchpad.net/bugs/394528 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 187175] Re: [hardy] Screens and Graphics Preferences fails to detect monitor
** This bug is no longer a duplicate of bug 178061 *** Error: couldn't find any ServerLayout sections -- [hardy] Screens and Graphics Preferences fails to detect monitor https://bugs.launchpad.net/bugs/187175 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 137247] Re: libpam-keyring broken on autologins
On a fresh install of 9.04, I set up a wireless network. Set my account to auto-login. Whenever I start machine, I get a dialog that nm-applet wants access to keyring, enter password. I want the machine to start up, take me to the desktop, and connect to the network without troubling me for passwords. There were no obvious ways to make the machine behave as I wanted. I had to go to Launchpad, search for bugs, read several bug reports until I found a method of working around the default behaviour by following the steps Doug Holton followed, above. The default behaviour is certainly buggy to me. I expect to set up a wireless network connection and have it auto- connect without asking for a password, whether or not I have auto-login enabled. And if it doesn't auto-connect, it should be simple and intuitive for the user to make it auto-connect. -- libpam-keyring broken on autologins https://bugs.launchpad.net/bugs/137247 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 239722] Re: xorg fails to correctly detect Satellite pro 4600 and 6000 screen resolution
** Summary changed: - xorg fails to correctly detect Satellite pro 4600 screen resolution + xorg fails to correctly detect Satellite pro 4600 and 6000 screen resolution ** Description changed: Binary package hint: xorg On previous versions of Ubuntu, dpkg-reconfigure allowed me to specify monitor resolution etc. With hardy, this feature appears to have been removed. I believe that will encourage better detection code, and more usable front ends for less technical users. Nevertheless, I am right now left with 800x600 on my Toshiba Satellite Pro 4600, which has a native resolution of 1024x768 with only option to manually edit xorg.conf. Steps to show bug: Install a fresh copy of Ubuntu Hardy 8.04 on a Toshiba Satellite pro laptop. Observe the GUI gives maximum resolution of 800x600. Expected: Resolution should include 1024x768 native screen resolution. This resolution has shown to work where screen resolution set manually. lspci error_report ; cat /var/log/Xorg.0.log error_report [lspci] 00:00.0 Host bridge [0600]: Intel Corporation 82815 815 Chipset Host Bridge and Memory Controller Hub [8086:1130] (rev 11) Subsystem: Toshiba America Info Systems Device [1179:0001] 01:00.0 VGA compatible controller [0300]: Trident Microsystems CyberBlade/XP [1023:9910] (rev 63) Subsystem: Toshiba America Info Systems Device [1179:0001] + + + This bug is also apparent on SP 6000. lspci -vvnn snippet from SP6000: + 01:00.0 VGA compatible controller [0300]: Trident Microsystems CyberBlade XPAi1 [1023:8820] (rev 82) + Subsystem: Toshiba America Info Systems Device [1179:0001] + See massage from 17 Jan 09 for full details -- xorg fails to correctly detect Satellite pro 4600 and 6000 screen resolution https://bugs.launchpad.net/bugs/239722 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 220490] Re: Screen resolution misdetection
*** This bug is a duplicate of bug 239722 *** https://bugs.launchpad.net/bugs/239722 ** This bug has been marked a duplicate of bug 239722 xorg fails to correctly detect Satellite pro 4600 and 6000 screen resolution -- Screen resolution misdetection https://bugs.launchpad.net/bugs/220490 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 239722] Re: xorg fails to correctly detect Satellite pro 4600 screen resolution
I notice the same bug is apparent with the Toshiba Satellite pro 6000 with the latest Alpha 3 version of 9.04. Native resolution is 1024x768 but the default resolution is 800x600 maximum resolution via the GUI is 800x600. I will probably need to alter xorg.conf like I have had to on the Tosh SatPro 4600 to get full resolution. I have included outputs for ddcprobe, dmidecode, lspci -vvnn, Xorg.0.log in the attached .tgz file for the Toshiba Satellite Pro 6000 running Alpha-3 9.04. ** Attachment added: Tosh SatPro 6000 outputs of lspci-vvnn, ddcprobe, Xorg.0.log, dmidecode http://launchpadlibrarian.net/21296030/satpro6000.tgz -- xorg fails to correctly detect Satellite pro 4600 screen resolution https://bugs.launchpad.net/bugs/239722 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 239722] Re: xorg fails to correctly detect Satellite pro 4600 screen resolution
I notice this has been moved to xorg-video-trident. I am not certain that this bug belongs to trident, as it appears to be a detection problem rather than a driver problem. It is possible to make the 4600 work at 1024x768 by modifying xorg.conf. -- xorg fails to correctly detect Satellite pro 4600 screen resolution https://bugs.launchpad.net/bugs/239722 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 239722] Re: xorg fails to correctly detect Satellite pro 4600 screen resolution
Using Jaunty 18 December build, same effect. 800x600 max resolution. lspci -vvnn attached ** Attachment added: tosh4600lspci-vvnn http://launchpadlibrarian.net/20578565/tosh4600lspci-vvnn ** Changed in: xorg (Ubuntu) Status: Invalid = Confirmed -- xorg fails to correctly detect Satellite pro 4600 screen resolution https://bugs.launchpad.net/bugs/239722 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 1] Re: Microsoft has a majority market share
Endolith, Ubuntu is based on Debian. Debian focus on getting a distro to what they consider finished before release. Unfortunately, without the discipline a release schedule provides, debian has proven releases may slip to three or more years apart. With Debian stable, most of the time, you would find yourself one major release behind flagship desktop programs such as Openoffice or Firefox. Sometimes two releases behind. With Ubuntu, the release schedule gives you most of the benefits of Debian, with a far more rapid release schedule. So yes, we are paying a penalty for the release schedule, but it is up to the individual user to choose what is right for them. You don't have to update to every Ubuntu release. To manage this, you could: 1) Use Debian stable. Very long release schedule, but well-tested prior to release. 2) Stick to long term release versions of Ubuntu. These tend to be released faster than Debian stable, but also tend to be better tested and more thoroughly bug-fixed than intermediate releases, and you have fewer upgrades to cause potential problems. -- Microsoft has a majority market share https://bugs.launchpad.net/bugs/1 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 118168] Re: Crontab accepts files with no newline before EOL/EOF. Cron ignores file
Hello Colin Being new to general-release code modifications, I suppose I have a starting point of taking a minimally-invasive approach; to take an approach least likely to introduce bugs. Eg if ported to Windows or OSX with different EOL conventions. \r \r\n That isn't to say I have any reason to believe the solution you and technomancy mentioned will introduce any bugs in Ubuntu, so I guess a consensus is growing around file modification. I'll take a look at that. -- Crontab accepts files with no newline before EOL/EOF. Cron ignores file https://bugs.launchpad.net/bugs/118168 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 118168] Re: Crontab accepts files with no newline before EOL/EOF. Cron ignores file
** Changed in: cron (Ubuntu) Assignee: (unassigned) = Nick_Hill (nick-nickhill) Status: Triaged = In Progress -- Crontab accepts files with no newline before EOL/EOF. Cron ignores file https://bugs.launchpad.net/bugs/118168 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 118168] Re: Crontab accepts files with no newline before EOL/EOF. Cron ignores file
I have created a patch for crontab.c which adds a warning if there is no newline at the end of the file. I have followed the original author's example of generating a diagnostic if any file function breaks. Please consider integrating upstream. ** Attachment added: Add warning if there is no newline at end of file, resulting in crontab being ignored. http://launchpadlibrarian.net/17195330/crontab.c.diff -- Crontab accepts files with no newline before EOL/EOF. Cron ignores file https://bugs.launchpad.net/bugs/118168 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 118168] Re: Crontab accepts files with no newline before EOL/EOF. Cron ignores file
Perhaps this version would be better. Adds extra lines to make warning clearer. ** Attachment added: Slightly clearer warning for missing new line at EOF http://launchpadlibrarian.net/17195340/crontab.c.diff -- Crontab accepts files with no newline before EOL/EOF. Cron ignores file https://bugs.launchpad.net/bugs/118168 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 239722] Re: xorg fails to correctly detect Satellite pro 4600 screen resolution
Samuli, thank you for filing the additional information. I missed the request for additional info. ** Changed in: xorg (Ubuntu) Status: Incomplete = New -- xorg fails to correctly detect Satellite pro 4600 screen resolution https://bugs.launchpad.net/bugs/239722 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 221894] Re: installing ltsp-server-standalone fails cant find xubuntu-artwork-usplash
I can confirm this bug has been fixed in 8.04.1. -- installing ltsp-server-standalone fails cant find xubuntu-artwork-usplash https://bugs.launchpad.net/bugs/221894 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 111123] Re: i2o DPT RAID driver broken. Known bug in 2.6.20. Patch available.
I have tried an I2o device on an Ubuntu 8.04.1 and have not been able to reproduce the bug. It therefore appears the upstream patch has found it's way into the Ubuntu 2.6.24 kernel. -- i2o DPT RAID driver broken. Known bug in 2.6.20. Patch available. https://bugs.launchpad.net/bugs/23 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 111123] Re: i2o DPT RAID driver broken. Known bug in 2.6.20. Patch available.
Not reproducible in 2.6.24. Fix appears to have found it's way from upstream into Ubuntu stock kernel. ** Changed in: linux (Ubuntu) Status: Incomplete = Fix Released -- i2o DPT RAID driver broken. Known bug in 2.6.20. Patch available. https://bugs.launchpad.net/bugs/23 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 263133] [NEW] [8.10 alpha 4] usplash progress bar shown multiple times
Public bug reported: Binary package hint: brdesktop-artwork-usplash 8.10 alpha 4 desktop iso Expected: one progress bar. Actual: Four progress-bar style images appear on Ibex tribe 4 bootup screen. Graphics card: Intel 82865G integrated. ** Affects: brdesktop-artwork (Ubuntu) Importance: Undecided Status: New -- [8.10 alpha 4] usplash progress bar shown multiple times https://bugs.launchpad.net/bugs/263133 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 263133] Re: [8.10 alpha 4] usplash progress bar shown multiple times
** Attachment added: usplash.jpg http://launchpadlibrarian.net/17181615/usplash.jpg -- [8.10 alpha 4] usplash progress bar shown multiple times https://bugs.launchpad.net/bugs/263133 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 263133] Re: [8.10 alpha 4] usplash progress bar shown multiple times
The apparent break in the main progress bar is an artifact from camera shake. There are four progress bars visible, one working. -- [8.10 alpha 4] usplash progress bar shown multiple times https://bugs.launchpad.net/bugs/263133 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 221894] Re: installing ltsp-server-standalone fails cant find xubuntu-artwork-usplash
I haven't seen any reports that this bug actually exists in intrepid, and I have tested intrepid and not managed to repeat bug so also marking intrepid Fix Released. ** Changed in: ltsp (Ubuntu Intrepid) Status: Confirmed = Fix Released -- installing ltsp-server-standalone fails cant find xubuntu-artwork-usplash https://bugs.launchpad.net/bugs/221894 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 261794] [NEW] LTSP thin client hangs 3-4 minutes at boot-up clocksource tsc unstable
Public bug reported: Actual behaviour: Boot Toshiba satellite pro 4600 (BX chipset, P3) as a thin client. Very slow boot to log-in screen. Takes around 4 minutes to get log-in screen. edit /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default change splash to nosplash, remove quiet from kernel boot line then observe booting laptop again. Laptop shows [ 17.438728] e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex waits 3-4 minutes then shows: [ 17.782386] Clocksource tsc unstable (delta = -3291491518 ns) Interestingly, although 3 or more minutes have passed, the kernel appears to have only clocked 343.6ms. This could point to a problem with kernel interaction with hardware. However, there is no such delay when the machine boots on the stock Ubuntu hardy kernel from hard drive, so this may not belong directly with Ubuntu kernel bugs. edit /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default again, adding acpi=off . The laptop now boots in reasonable time. cd /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/ cp default my-mac-address then revert default to how it was. This provides a solution. Using current up-to-date default packages for ltsp. ltsp-server-standalone: Installed: 5.0.40~bzr20080212-0ubuntu7 Candidate: 5.0.40~bzr20080212-0ubuntu7 Version table: *** 5.0.40~bzr20080212-0ubuntu7 0 500 http://ubuntu.virginmedia.com hardy-updates/main Packages 100 /var/lib/dpkg/status 5.0.40~bzr20080212-0ubuntu6 0 500 http://ubuntu.virginmedia.com hardy/main Packages ** Affects: ltsp (Ubuntu) Importance: Undecided Status: New -- LTSP thin client hangs 3-4 minutes at boot-up clocksource tsc unstable https://bugs.launchpad.net/bugs/261794 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 1] Re: Microsoft has a majority market share
Hello Shane Before your post, I didn't believe for one moment Bernhard Koenig's proposed solution to this bug was serious. I thought it was a genuine ironic joke. As an ironic joke, it is sublime. As an earnest piece, somewhat flawed. -- Microsoft has a majority market share https://bugs.launchpad.net/bugs/1 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 195159] Re: The new time zone / city choosing is annoying
In 8.04.1 I can confirm selecting a city is difficult on some computers, easier on others. Seemingly dependent on graphics processing ability. Scrolling whilst zoomed in doesn't usually work for me, Very snatchy movement, and imprecise. Frustrating. I usually revert to wading through the long list of cities and select using the combo-box (drop-down list). The city selection system on versions previous to Hardy always worked well for me. -- The new time zone / city choosing is annoying https://bugs.launchpad.net/bugs/195159 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 1] Re: Microsoft has a majority market share
Harsh Singh; It was unnecessary to re-post the whole of Nulled message. Apart from that, it doesn't make much sense to me. For example, paragraph 3 talks about a homiogenous computer environment. There is no such word as homiogenous. There is homogeneous and heterogeneous, but substituting either word still makes no sense to me. I could go on, but this isn't really a place to plainly agree, disagree or dissect what someone has said. That is best for a debating chamber. Let's concentrate the discussion on what we can do to help more people have a good experience of and to appreciate the virtues of free software. -- Microsoft has a majority market share https://bugs.launchpad.net/bugs/1 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 239722] Re: xorg fails to correctly detect Satellite pro 4600 screen resolution
** Attachment added: lspci and Xorg.0.log output. http://launchpadlibrarian.net/15257471/error_report -- xorg fails to correctly detect Satellite pro 4600 screen resolution https://bugs.launchpad.net/bugs/239722 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 239722] [NEW] xorg fails to correctly detect Satellite pro 4600 screen resolution
Public bug reported: Binary package hint: xorg On previous versions of Ubuntu, dpkg-reconfigure allowed me to specify monitor resolution etc. With hardy, this feature appears to have been removed. I believe that will encourage better detection code, and more usable front ends for less technical users. Nevertheless, I am right now left with 800x600 on my Toshiba Satellite Pro 4600, which has a native resolution of 1024x768 with only option to manually edit xorg.conf. Steps to show bug: Install a fresh copy of Ubuntu Hardy 8.04 on a Toshiba Satellite pro laptop. Observe the GUI gives maximum resolution of 800x600. Expected: Resolution should include 1024x768 native screen resolution. This resolution has shown to work where screen resolution set manually. lspci error_report ; cat /var/log/Xorg.0.log error_report ** Affects: xorg (Ubuntu) Importance: Undecided Status: New -- xorg fails to correctly detect Satellite pro 4600 screen resolution https://bugs.launchpad.net/bugs/239722 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 1] Re: Microsoft has a majority market share
From discussing on IRC and between friends, it seems uncontroversial to suggest 8.04 has more bugs than we'd like. Far more than we'd like for an LTS. Many of them being regressions. Not to mention beta Firefox. At the same time, there are perhaps millions using Ubuntu, and I often have opportunities to be the first bug reporter (sometimes for show stoppers), despite being busy, and not focusing on finding Ubuntu bugs. 10 friends are Ubuntu users. None file bugs unless shepherded by me, where I give them real-time directions on how to actually report bugs in Ubuntu. I therefore propose a thought experiment; take 10 average half-computer- literate people who have encountered Ubuntu before, so already have a rough idea of how to launch an application, and know where to find the administration menu. Point out to each in turn something which is clearly not functioning the way it should. Very few of them, unless previously primed will ask out loud, or ask themselves How do we tell Ubuntu about this?. Therefore, users of Ubuntu must be primed to report bugs. This should be a clear part of the Ubuntu design; prime users to report bugs! Stage two of the thought experiment: Ask each user in turn to inform Ubuntu about the bug. Maybe 10-30% will have found Launchpad before giving up. Probably from typing Ubuntu bug in google. 70-90% of these previously primed people will likely have completely lost their way before getting to the BTS. For stage three, we need to imagine the original sample size was much larger. So we'll talk in terms of percentages. Of this 10% left, who found their way to Launchpad, who have already been primed from personal contact, many are likely to get lost in Launchpad, finding their way out of the Ubuntu page, searching projects on Launchpad, rather than searching bugs in Ubuntu. We are probably down to 3-5% of primed people by now even having successfully performed a search for their bug on Launchpad. Stage 4. Of that 3-5%, if the bug has not already been filed, I estimate perhaps 0.5-1% will actually report a bug, and not be put off by 1) not being able to identify with a good degree of confidence, which package the bug is supposed to be filed against and 2) Having to register / have a valid email address etc. I therefore suggest that with the current BTS arrangement, maybe half to one percent of 'ordinary computer users' personally primed, will successfully file any bug. If not primed, perhaps one in 1000 or 1 in 5,000. The number of bugs considered of good quality and as a basis of a fix will be much smaller still. I would welcome a debate on how to make the Ubuntu bug tracking user interface, right away along the line from detecting a bug to triage, inclusive to 'ordinary computer users'. I'll kick off by suggesting: 1) When a user account is created, by default, beg users to file bugs, and point them to the BTS 2) The Ubuntu bug tracking system should have only Ubuntu, Kubuntu, Edubuntu or other siblings which share the same packages - there should be no way for users to get lost in other projects on the same bug tracking system. 3) The root of the Ubuntu bug tracking system should actually be at an easy to remember URL such as http://bugs.ubuntu.com/ . (This URL does currently re-direct to https://launchpad.net/ubuntu/+bugs). 4) The hardest part - make it much easier for users to identify which package the bug is related to. I am an experienced user and find this step challenging. Maybe a clear decision tree, with unambiguous, easy questions, or some graphical system. 5) When a bug is marked as a duplicate, the title of the bug should remain searchable (at least for months) as a 'common user' may identify a bug using different words to those used by the developer. -- Microsoft has a majority market share https://bugs.launchpad.net/bugs/1 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 218256] Re: Hardy 8.04 hangs on boot with Broadcom BCM4301 Wireless mini-PCI card. b43legacy-phy0:Broadcom 4301 WLAN found
BjDelta, When my system hangs on default Hardy, the actual chip is 4301 according to markings on chip, so the reported number is correct. However, the driver parameters or register set may be mis-selected. -- Hardy 8.04 hangs on boot with Broadcom BCM4301 Wireless mini-PCI card. b43legacy-phy0:Broadcom 4301 WLAN found https://bugs.launchpad.net/bugs/218256 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 184446] Re: bcm5755m controller prevents Dell D531 from booting Gutsy
BCM4301 blocks boot on Hardy. bug218256 May or may not be related. -- bcm5755m controller prevents Dell D531 from booting Gutsy https://bugs.launchpad.net/bugs/184446 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 218256] Re: Hardy 8.04 hangs on boot with Broadcom BCM4301 Wireless mini-PCI card. b43legacy-phy0:Broadcom 4301 WLAN found
Given that three sources have verified this bug, and there is enough information to validate, this passes as confirmed. This is a complete killer for those with built-in BCM4301 mini-PCI cards, (which are fairly common in older P3 / Athlon M laptops), Their computers will simply stop booting on upgrade to 8,04. I can loan a BCM4301 mini-PCI card to a developer working on this issue. ** Changed in: linux (Ubuntu) Status: New = Confirmed -- Hardy 8.04 hangs on boot with Broadcom BCM4301 Wireless mini-PCI card. b43legacy-phy0:Broadcom 4301 WLAN found https://bugs.launchpad.net/bugs/218256 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 221894] Re: installing ltsp-server-standalone fails cant find xubuntu-artwork-usplash
I have tested and found the same problem. Given that nobody without knowledge of undocumented parameters can use ltsp-build-client for it's intended purpose, I believe this to be a bug, and I believe it should remain a bug until either: 1) ltsp-build-client scripts no longer depend on universe packages or 2) ltsp-build-client gives informational warning telling users the build will fail without the parameter, and why or 3) The package the ltsp-build-client scripts are a member of moves to universe and, by default, enables the universe component in the client environment ** Changed in: ltsp (Ubuntu) Status: Invalid = Confirmed -- installing ltsp-server-standalone fails cant find xubuntu-artwork-usplash https://bugs.launchpad.net/bugs/221894 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 218256] Re: Hardy 8.04 beta CD hangs on boot at b43legacy-phy0: Broadcom 4301 WLAN found
Swapped card from a BCM4301 to a BCM4306. System does not hang with BCM4306. ** Summary changed: - Hardy 8.04 beta CD hangs on boot at b43legacy-phy0: Broadcom 4301 WLAN found + Hardy 8.04 hangs on boot with Broadcom BCM4301 Wireless mini-PCI card. ** Summary changed: - Hardy 8.04 hangs on boot with Broadcom BCM4301 Wireless mini-PCI card. + Hardy 8.04 hangs on boot with Broadcom BCM4301 Wireless mini-PCI card. b43legacy-phy0:Broadcom 4301 WLAN found ** Description changed: Binary package hint: hal - Boot Hardy 8.04 beta on a laptop. Laptop hangs with progress bar frozen. + Boot Hardy 8.04 beta CD on a laptop. Laptop hangs with progress bar + frozen. Boot laptop again, at option screen press F6 delete quiet and change splash to nospash to show boot details. User will see: [142.93849] b43legacy-phy0:Broadcom 4301 WLAN found as the final boot message when machine hangs. Dismantle laptop and remove Broadcom mini-PCI card. Laptop boots normally with 8.04 CD. Broadcom card is known working with Windows XP, and card does not prevent 7.10 cd from booting. The test machine is a Toshiba Satellite Pro 4600 800Mhz P3 I815 chipset. -- Hardy 8.04 hangs on boot with Broadcom BCM4301 Wireless mini-PCI card. b43legacy-phy0:Broadcom 4301 WLAN found https://bugs.launchpad.net/bugs/218256 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 218256] [NEW] Gutsy 8.04 beta CD hangs on boot at b43legacy-phy0: Broadcom 4301 WLAN found
Public bug reported: Binary package hint: hal Boot Gutsy 8.04 beta on a laptop. Laptop hangs with progress bar frozen. Boot laptop again, at option screen press F6 delete quiet and change splash to nospash to show boot details. User will see: [142.93849] b43legacy-phy0:Broadcom 4301 WLAN found as the final boot message when machine hangs. Dismantle laptop and remove Broadcom mini-PCI card. Laptop boots normally with 8.04 CD. Broadcom card is known working with Windows XP, and card does not prevent 7.10 cd from booting. The test machine is a Toshiba Satellite Pro 4600 800Mhz P3 I815 chipset. ** Affects: hal (Ubuntu) Importance: Undecided Status: New -- Gutsy 8.04 beta CD hangs on boot at b43legacy-phy0: Broadcom 4301 WLAN found https://bugs.launchpad.net/bugs/218256 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 218256] Re: Hardy 8.04 beta CD hangs on boot at b43legacy-phy0: Broadcom 4301 WLAN found
** Summary changed: - Gutsy 8.04 beta CD hangs on boot at b43legacy-phy0: Broadcom 4301 WLAN found + Hardy 8.04 beta CD hangs on boot at b43legacy-phy0: Broadcom 4301 WLAN found ** Description changed: Binary package hint: hal - Boot Gutsy 8.04 beta on a laptop. Laptop hangs with progress bar frozen. + Boot Hardy 8.04 beta on a laptop. Laptop hangs with progress bar frozen. Boot laptop again, at option screen press F6 delete quiet and change splash to nospash to show boot details. User will see: [142.93849] b43legacy-phy0:Broadcom 4301 WLAN found as the final boot message when machine hangs. Dismantle laptop and remove Broadcom mini-PCI card. Laptop boots normally with 8.04 CD. Broadcom card is known working with Windows XP, and card does not prevent 7.10 cd from booting. The test machine is a Toshiba Satellite Pro 4600 800Mhz P3 I815 chipset. -- Hardy 8.04 beta CD hangs on boot at b43legacy-phy0: Broadcom 4301 WLAN found https://bugs.launchpad.net/bugs/218256 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 218256] Re: Hardy 8.04 beta CD hangs on boot at b43legacy-phy0: Broadcom 4301 WLAN found
Install 8.04 with Broadcom mini-PCI removed. Re-boot with card inserted. Booting hangs in same place as with CD. Will next remove card, run updates, then try again. -- Hardy 8.04 beta CD hangs on boot at b43legacy-phy0: Broadcom 4301 WLAN found https://bugs.launchpad.net/bugs/218256 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 218256] Re: Hardy 8.04 beta CD hangs on boot at b43legacy-phy0: Broadcom 4301 WLAN found
Run upates on system. Made no difference. System hangs on boot with Broadcom card connected. -- Hardy 8.04 beta CD hangs on boot at b43legacy-phy0: Broadcom 4301 WLAN found https://bugs.launchpad.net/bugs/218256 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 192930] Re: Numeric keypad no longer works in Hardy
I am experiencing the same effect with Hardy Heron with my main user account after migrating from Gutsy. When more people migrate using update manager, this could be a big problem. ** Changed in: xserver-xorg-input-keyboard (Ubuntu) Status: Invalid = Confirmed -- Numeric keypad no longer works in Hardy https://bugs.launchpad.net/bugs/192930 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 192930] Re: Numeric keypad no longer works in Hardy
I have 2 sessions running. The attached Xorg.0.log is from the first session, which is my 'nick' user account, which has been through many previous distribution releases. The attached Xorg.20.log is from a newer 'ryan' user account (created in Gutsy) which does not show this problem. I have tried changing keyboard settings in Gnome to ACPI and 105 key (intl) PC. UK layout. Whether or not the NumLock light is on, the numeric keypad does not return numerals. Number 5 is equivalent to clicking the left mouse button. I am using a standard desktop PC with standard 104/5 key UK keyboard. ** Attachment added: xorg.log for non-working and working sessions. http://launchpadlibrarian.net/12330195/numeric-keypad-hardy-heron.tgz -- Numeric keypad no longer works in Hardy https://bugs.launchpad.net/bugs/192930 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 192930] Re: Numeric keypad no longer works in Hardy
I have cleared out cruft in my home directory; hidden files and folders beginning with period (.) which appear to be redundant. After this clear-out, the problem has resolved itself. I have a copy of all files in the home directory, so I might set things the way they were, to determine which configuration file causes the problem. -- Numeric keypad no longer works in Hardy https://bugs.launchpad.net/bugs/192930 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 137604] Re: Black Bar Across Screen with gutsy i810
The move to -invalid was for xorg which presumably contains the client libraries and is unrelated to the problem. xserver is related to the i810 driver causing the problem, so has not been marked invalid. -- Black Bar Across Screen with gutsy i810 https://bugs.launchpad.net/bugs/137604 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 140421] Wide black bar accross screen for i810 with latest Gutsy - Regression
Public bug reported: Binary package hint: xserver-xorg-video-i810 Install Gutsy tribe 5 on i810 based Toshiba i810 based desktop. No black bar visible. Update system to latest gutsy #aptitude update #aptitude dist-upgrade After performing update, and starting system, a black bar, 256 pixels wide, appears on screen 256 pixels from top of screen. Appears at same number of pixels from top, irrespective of resolution. Tested at: 640x480 800x600 1024x768 1280x1024 1440x1050 To verify that a hardware error had not appeared when I updated, I re- installed Gutsy on another hard drive. Swapping hard drives back and forth, the problem only appears with the most recent updated Gutsy (post-tribe 5). I will provide 1) Pictures demonstrating with and without black bar. 2) Output from my hwinfo script detailing as much hardware and log file information from system showing fault, and system not showing fault. Please get back to me if you need any more info. ** Affects: xserver-xorg-video-i810 (Ubuntu) Importance: Undecided Status: New -- Wide black bar accross screen for i810 with latest Gutsy - Regression https://bugs.launchpad.net/bugs/140421 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 140421] Re: Wide black bar accross screen for i810 with latest Gutsy - Regression
Hardware info for updated installation showing problem ** Attachment added: Tar file containing hardware and log info for latest update - showing fault http://launchpadlibrarian.net/9305342/hwinfo-gutsy-tribe5-updated-notworking-17_sep_1305pm-i810.tar.gz -- Wide black bar accross screen for i810 with latest Gutsy - Regression https://bugs.launchpad.net/bugs/140421 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 140421] Re: Wide black bar accross screen for i810 with latest Gutsy - Regression
System before update. Tribe 5 OK. ** Attachment added: Tar file containing hardware and log info for tribe 5 without update - no fault visible http://launchpadlibrarian.net/9305345/hwinfo-gutsy-tribe5-not_updated-working-i810.tar.gz -- Wide black bar accross screen for i810 with latest Gutsy - Regression https://bugs.launchpad.net/bugs/140421 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 140421] Re: Wide black bar accross screen for i810 with latest Gutsy - Regression
The band doesn't appear on screen shots. I have photographed screen. ** Attachment added: Picture of screen showing problem http://launchpadlibrarian.net/9305328/i810-band-on-screen.jpg -- Wide black bar accross screen for i810 with latest Gutsy - Regression https://bugs.launchpad.net/bugs/140421 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 140421] Re: Wide black bar accross screen for i810 with latest Gutsy - Regression
Gutsy without updates ** Attachment added: Picture of screen - same system Gutsy Tribe 5 without most recent updates http://launchpadlibrarian.net/9305330/i810-not-updated-gutsy-tribe5-working.JPG -- Wide black bar accross screen for i810 with latest Gutsy - Regression https://bugs.launchpad.net/bugs/140421 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 137604] Re: Black Bar Across Screen with gutsy i810
I have modified the bug title so others searching for i810 and gutsy will find it. If you are using a screen with 1024x768 resolution, then it will cover 1/3rd of your screen. However, the band is actually 256 pixels wide, and always starts 256 pixels from the top of the screen, whatever resolution you use. ** Summary changed: - Black Bar Across Screen with latest Xorg Update + Black Bar Across Screen with gutsy i810 -- Black Bar Across Screen with gutsy i810 https://bugs.launchpad.net/bugs/137604 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 45646] Re: Uses up too much memory when starting partitioner, kills nautilus
Under Gutsy tribe 5, system with 256Mb RAM, Ubiquity hangs on installing system Detecting file systems. This appears to happen when the swap space on the device being re- partitioned is disabled, leaving too little virtual memory for Ubiquity to continue. I see a similar behaviour with a drive without partition defined, therefore no virtual memory. Adding an additional 128Mb solves the problem. The memory issue makes Ubiquity unusable on systems with 256Mb or less RAM. -- Uses up too much memory when starting partitioner, kills nautilus https://bugs.launchpad.net/bugs/45646 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 37108] Gutsy Xsane fixed.
From my update of gutsy just now, the problem I reported on 070829 has been fixed. Perhaps from a fix in libgtk2.0. -- Xsane crashes, images are blank https://bugs.launchpad.net/bugs/37108 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 37108] Gutsy regression xsane broken with Epson scanner
Turn on Epson CX5400 all-in-one scanner/printer Run xsane from menu. Dialog appears Seaarching for scanner. Dialog disappears, nothing reappears. Turn off scanner. Run xsane from menu. Dialog appears Searching for scanner then dialog No devices available. Turn on scanner. run xsane from command line: [EMAIL PROTECTED]:/var/crash$ xsane (xsane:12126): Gtk-CRITICAL **: gtk_widget_get_style: assertion `GTK_IS_WIDGET (widget)' failed (xsane:12126): Gtk-CRITICAL **: gtk_style_copy: assertion `GTK_IS_STYLE (style)' failed Segmentation fault (core dumped) Crash report from /var/crash (minus core dump) attached. If you need a core dump, please ask. Xsane and scanner functioned correctly on Feisty. ** Attachment added: debug dump from /var/crash http://launchpadlibrarian.net/9044335/usr_bin_xsane.1000-nocore.crash.gz -- Xsane crashes, images are blank https://bugs.launchpad.net/bugs/37108 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 128616] Re: Real time clock will not set with Nvidia 6100 chipset
Gutsy hwclock now operates as expected with the Nvidia 6100 chipset. --directisa no longer necessary. I will change the status as fixed released. ** Changed in: linux-meta (Ubuntu) Status: New = Fix Released -- Real time clock will not set with Nvidia 6100 chipset https://bugs.launchpad.net/bugs/128616 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 102018] Re: [Needs-packaging] lbxproxy
I agree LBX is integral to the X11 suite, and should be available on all good distribution package managers. -- [Needs-packaging] lbxproxy https://bugs.launchpad.net/bugs/102018 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 128616] Re: Real time clock will not set with Nvidia 6100 chipset
Hello Robbie On my Nvidia 6100 chipset, the --directisa switch seems to work. # hwclock --directisa --systohc I'd say there is a bug somewhere given we need a --directisa switch. The API to write and read the system clock should be consistent at the software level irrespective of hardware. So although for me there is a workaround, it is still a bug. Robbie, There is a script within http://launchpadlibrarian.net/8592461/hwinfo.tar.gz called hardwareinfo.script. Run it then post the output tar.gz which will give all the hardware info from the tools I could find. This will help a developer characterise your bug. -- Real time clock will not set with Nvidia 6100 chipset https://bugs.launchpad.net/bugs/128616 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1] Re: Microsoft has a majority market share
Pitwalker; Nobody with a little computer experience, and a rough understanding of the installer language should risk loosing data unless they choose to ignore a warning that they should understand.. The program which installs Ubuntu from the live CD is called Ubiquity. If the warnings are not clear to you, please file a bug against ubiquity and provide an example of how the installer can universally communicate the risk of data loss, and instruct the user on how they can prevent loss of valuable data. In general, the easier it is to loose large amounts of data, the clearer the warnings need to be. However, ultimately, any user who has valuable data must either make backups or loose it (hardware failures and user errors will always eventually eat data which is not backed up). -- Microsoft has a majority market share https://bugs.launchpad.net/bugs/1 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 119423] Re: Suspend to RAM (Sleeping) not working on DELL Latitude D520
STR problems are often caused by a hardware driver either blocking status change to STR, or a hardware driver failing to re-initialise on return from STR. Depending on your BIOS, I found a useful method to debug this is to disable as much on-board hardware (usually through the BIOS screen) as you can. Then try to go into/ recover from STR. You can also try rmmod modulename for various hardware drivers. This will remove the driver from the current running kernel. The driver should then load properly after next reboot. Once you have identified the hardware/ driver preventing STR, it will be much easier to fix the bug. -- Suspend to RAM (Sleeping) not working on DELL Latitude D520 https://bugs.launchpad.net/bugs/119423 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 128934] evolution outlook web access only works on port 80
Public bug reported: Binary package hint: evolution I have found it necessary to run exchange / outlook web access (OWA) on port 81 so that port 80 may be redirected to a web server. There may also be instances where connections to multiple exchange servers are required through the same IP address. This will require port re-mapping for OWA/Exchange. Outlook and OWA web services are usable when assigned to port 81, and presumably other random port numbers. Evolution does not appear to function when pointed to OWA on ports other than 80. Steps to reproduce bug: 1) Determine evolution works correctly with default setup; Configure Exchange to listen to port 80. Create account on Evolution, pointing to outlook web access url. Verify Evolution connects to OWA services. 2) Verify bug: Delete previously created account from Evolution. Set exchange server to listen to port 81. Create account on Evolution, pointing to outlook web access url eg http://myexchangeserver.com:81/exchange Click verify, enter password. Verification appears to complete OK. When Evolution attempts to connect to exchange server, a dialog box appears saying Error while Scanning folders in /servver/var/spool/mail/nick/. Could not scan folder `/servver/var/spool/mail/nick': No such file or directory 3) Verify exchange is working properly. by a) Pointing a web browser to the port 81 URL, check web access functions. Point outlook to exchange URL. Verify outlook functions. It appears the backend to evolution connecting to exchange is hard-wired to connect to port 80. The back end should connect to whatever port is specified in the OWA URL. ** Affects: evolution (Ubuntu) Importance: Undecided Status: New -- evolution outlook web access only works on port 80 https://bugs.launchpad.net/bugs/128934 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 128959] Re: pointer disappears after logout/login with NV driver; Nvidia 6100 chipset
Ubuntu Gutsy tribe 3 Kernel 2.6.22-8-386 Full hardware inventory (and script used to generate inventory) attached. ** Attachment added: hwinfo.tar.gz http://launchpadlibrarian.net/8592461/hwinfo.tar.gz -- pointer disappears after logout/login with NV driver; Nvidia 6100 chipset https://bugs.launchpad.net/bugs/128959 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 128959] pointer disappears after logout/login with NV driver; Nvidia 6100 chipset
Public bug reported: Binary package hint: xserver-xorg-driver-nv Start machine from cold. Mouse pointer visible and usable. Log out of session, pointer invisible in GDM. log back in again, pointer invisible. Roll-over and click events still respond to mouse. Re-start computer. Log in. Select switch user. Log into second user. Mouse pointer usable. Log out of second user. Pointer invisible on log-in screen. Pointer also invisible after logging in. Select switch user for a second time. Log in as second user. Mouse pointer INVISIBLE. In summary, the second time you try to log in on a virtual terminal (Ctrl+alt+Fx) the pointer has disappeared. When the pointer vanishes, it always does so before entering username/password. I'd say this is an important bug given users can't log and use X-windows a second time without rebooting the computer. ** Affects: xserver-xorg-driver-nv (Ubuntu) Importance: Undecided Status: New -- pointer disappears after logout/login with NV driver; Nvidia 6100 chipset https://bugs.launchpad.net/bugs/128959 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
